Hi all!
Im in a bit of an unknown scary situation for me
S6 edge, updated to nougat, rooted with the twrp Magisk method. All went fine.
Went to update the SUperSU binary from the app, and selected the twrp method.
Phone went into recovery, and started the flash. Now its been stuck for ages on "skipping MD5 check, no MD5 file found"
Buttons dont do anything (power button just shuts down the screen, and combination buttons takes screenshots), the lock screen and swype work, and the progress bar is blue and moving.....
What do I do? No idea how to restart, or exit recovery...
All the threads I checked, talk about failed rom installs, and re flashing the rom or the recovery, but I cant even get out of recovery to restart the phone or go into download mode
Any help will be greatly appreciated!
Update!
After the panic of being stuck without a phone, and waiting for the phone to run out of battery, I kept googling and found out that I can restart twrp by holding Power and Vol Down for about 10 seconds.
It rebooted back into twrp menu, I restarted into system, and all seems ok!
From what I have understood so far, magisk does not need SuperSU, is that correct?
PHEW!
Leaving this here, in case it helps someone in the future!
Related
Alright guys, I need some help.
I tried installing twrp using adp / fastboot. I thought everything was going well. Everything came up as finish, the blue bar was full for a good 10 min, so I issued the restart command, and crossed my fingers it restarted.
I stared as I hoped I didn't screw something up.... android seemed to load fine and go to the lock screen. I was relieved. :
So, I tried rebooting (PWR + Vol Down) and choose RCK to load twrp. Now it just sits there, at " Booting recovery kernal image" and dosen't go anywhere.
Any ideas?
My goal is to flash AndroWook HairyBean.
Edit
Let me add that I am a novice at this at best. As far as I know, twrp may not have even took? But once I get twrp working, I can flash Hairybean, right?
Now since it's my ONLY phone, I beg you to help me as fast as possible!
I tried to root my phone through Odin. There were two files to load. I've loaded the step1.tar, but failed to load the second one.
After I loaded the first file, my phone rebooted into recovery mode. It was looking kinda different from the normal one. Like inverted colors or something. When I tried to reboot the system, it was plain black screen with errors ike "..... has stopped". I turned off the phone, and turned it again, only to see recovery mode again.
EVERYTIME I turn on my phone, it goes to recovery mode. When I choose the reboot system option, it goes black screen with errors. If I choose to wipe everything, and then reboot it, it goes absolutely fine. Untill I turn it off, of cource. Then it goes to recovery mode again.
HELP PLEASE
Imdoneforreal said:
Now since it's my ONLY phone, I beg you to help me as fast as possible!
I tried to root my phone through Odin. There were two files to load. I've loaded the step1.tar, but failed to load the second one.
After I loaded the first file, my phone rebooted into recovery mode. It was looking kinda different from the normal one. Like inverted colors or something. When I tried to reboot the system, it was plain black screen with errors ike "..... has stopped". I turned off the phone, and turned it again, only to see recovery mode again.
EVERYTIME I turn on my phone, it goes to recovery mode. When I choose the reboot system option, it goes black screen with errors. If I choose to wipe everything, and then reboot it, it goes absolutely fine. Untill I turn it off, of cource. Then it goes to recovery mode again.
HELP PLEASE
Click to expand...
Click to collapse
Well, it doesn't seems important error. Just download stock rom for your phone and reflash it, it will works again as you wish. The problem is you've flashed wrong file that it results a soft brick.
Edit: Not a soft brick, but a software failure.
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
I installed stock Android 10 Q (from 9 P) via Odin on my galaxy tab s6 LTE, then i unlocked the bootloader and rooted with magisk (manager 7.5.1, zip 20.4) following the magisk git site installation instructions (which are a bit more complicated than from some third party sites.)
Everything ok, but then when i power off it reboots. It's not in a bootloop: it boots up normally, but if i can't power off then that's not good when I'm not using it. I tried patching again and checked i got the the same md5.
Eventually i found that if i booted to recovery mode and there i choose reboot, it reboots to unrooted, but it does power off.
To get root access again i start with the recovery key combination but let go at the splash screen before it enters stock recovery mode. This means that i have to reboot each time i want to either switch it off or have root (but not both.) It's good enough for now, so I'm posting this in case anything else has the same problem.
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.