So I was experimenting with some customization tools (gravitybox, some other twrp modules) and everything was fine. Then I installed a custom layer I downloaded from the Play Store on Layer Manager and now the phone boots into the stock wallpaper, the screen is flashing, yellow led constantly on, there are no buttons anywhere, I can't do anything, the only command he can do is the screen used to turn the phone off, and even with that I've tried booting into safe mode and it's the same. I wanted to make a factory reset on TWRP but I can't even boot into recovery, it just shows the MI logo and boots normally. I also tried fastboot flashing TWRP again and although it flashes well the normal boot remains. Can someone help me?
EDIT: I managed to boot into TWRP, I was doing it wrong after all. I will reflash the ROM.
SkinCoffin said:
So I was experimenting with some customization tools (gravitybox, some other twrp modules) and everything was fine. Then I installed a custom layer I downloaded from the Play Store on Layer Manager and now the phone boots into the stock wallpaper, the screen is flashing, yellow led constantly on, there are no buttons anywhere, I can't do anything, the only command he can do is the screen used to turn the phone off, and even with that I've tried booting into safe mode and it's the same. I wanted to make a factory reset on TWRP but I can't even boot into recovery, it just shows the MI logo and boots normally. I also tried fastboot flashing TWRP again and although it flashes well the normal boot remains. Can someone help me?
Click to expand...
Click to collapse
If you're able to access twrp somehow, flash the rom again and just wipe cache and dalvik cache. You won't lose any data at all.
Edit - I don't think layers can mess with your recovery. Fastboot flash recovery and try booting into it by pressing volume up and power button. If that doesn't work.. Press power button and both volume up and down and see if it boots into recovery. Once it does, just flash the rom without wiping data.
Boot into TWRP & Mount "System"
Using File Manager navigate to /system/overlays
Delete all files one by one inside overlays folder
Reboot to system
Related
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode. I can use a command to delete all my data. As they're Magisk modules, clearing the data might not unbrick my phone (I'm not sure).
Is there any way I can reboot my phone into TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
SGoraiCS said:
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode.
As they're Magisk modules, clearing the data might not save my phone. My phone's not going to turn on (I'm not sure).
Is there any way I can reboot my phone to TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
Click to expand...
Click to collapse
Two Methods.
1- Some phones actually respond to fastboot reboot recovery. This is quite natural given adb reboot recovery, but unfortunately is non-standard. I found lots of people suggesting this method so I offer it here in the hopes that it works for some, but it didn't for me.
2- Some phones will actually let you book into an image via fastboot without flashing it. This will allow you to load a recovery image without needing to reboot the phone at all. You need a copy of the recovery image on your computer, but running fastboot boot image.img should do the trick. I was able to load up TWRP using this method.
Sent from my Pixel 3 XL using Tapatalk
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
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.
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.