Phone is a ginko variant Redmi Note 8, running the PixelOs rom.
It's been running fine for about 2 months now without issue until today.
This morning after using it briefly, it was placed in my pocket. About an hour later I removed it to find the screen black but lit up.
Power cycling the phone resulted in it getting to the boot screen (Google logo with loading bar) where it sits indefinitely. The bar at the bottom is animated, so it's not frozen per say.
If I try to reboot to recover(OrangeFox) it shows the Orange booting screen, and sits there.
I have tried flashing several other orangefox recovery's as well as 2 different TWRP recoveries with the same result, they display the startup screen and then hang there.
Any suggestions?
Sickify said:
Phone is a ginko variant Redmi Note 8, running the PixelOs rom.
It's been running fine for about 2 months now without issue until today.
This morning after using it briefly, it was placed in my pocket. About an hour later I removed it to find the screen black but lit up.
Power cycling the phone resulted in it getting to the boot screen (Google logo with loading bar) where it sits indefinitely. The bar at the bottom is animated, so it's not frozen per say.
If I try to reboot to recover(OrangeFox) it shows the Orange booting screen, and sits there.
I have tried flashing several other orangefox recovery's as well as 2 different TWRP recoveries with the same result, they display the startup screen and then hang there.
Any suggestions?
Click to expand...
Click to collapse
Bro I am afraid you'll have to install the whole firmware again and it will boot into MIUI. You need to flash it with the help of Mi Flash and be in the Fastboot mode and also it will erase all the data. and then you can install the custom recovery again and after installing MIUI and you can flash another ROM. Some AOSP Android 12 ROMs have this bug.
Download Firmware from here: https://mifirm.net/
Spuffyffet said:
Bro I am afraid you'll have to install the whole firmware again and it will boot into MIUI. You need to flash it with the help of Mi Flash and be in the Fastboot mode and also it will erase all the data. and then you can install the custom recovery again and after installing MIUI and you can flash another ROM. Some AOSP Android 12 ROMs have this bug.
Download Firmware from here: https://mifirm.net/
Click to expand...
Click to collapse
Managed to get it going again. I used fastboot to format the userdata partition and that seemed to fix it.
Interesting that some AOSP roms have this bug...I will have to do some research to avoid this in the future.
Sickify said:
Managed to get it going again. I used fastboot to format the userdata partition and that seemed to fix it.
Interesting that some AOSP roms have this bug...I will have to do some research to avoid this in the future.
Click to expand...
Click to collapse
Yup formatting data also helps. Glad it got fixed brother.
Sickify said:
Running the PixelOs rom
Click to expand...
Click to collapse
Of course it's PE time !
Sickify said:
I used fastboot to format the userdata partition and that seemed to fix it
Click to expand...
Click to collapse
That is an encryption problem, no need to format anything just flash DFE
Spuffyffet said:
Bro I am afraid you'll have to install the whole firmware again
Download Firmware from here: https://mifirm.net/
Click to expand...
Click to collapse
Related
I am having a really strange problem in that I cannot get any custom recovery to boot on my Oppo Find 7. I get a blank screen with twrp, cwm, etc.
When I try and flash the official recovery it goes into recovery but is only using half the screen. The left of the screen is black with half the Oppo logo, and the right has the recovery options flashing about all over the place. Am I doing something obviously wrong? or is the recovery partition corrupt?
I have used both adb and the "recovery installer" tool from this forum.
btw I can boot into the OS fine. It just seems to be a recovery issue.
edit: Solved it. Basically only nameless recovery works, the others are the wrong resolution.
roton said:
I am having a really strange problem in that I cannot get any custom recovery to boot on my Oppo Find 7. I get a blank screen with twrp, cwm, etc.
When I try and flash the official recovery it goes into recovery but is only using half the screen. The left of the screen is black with half the Oppo logo, and the right has the recovery options flashing about all over the place. Am I doing something obviously wrong? or is the recovery partition corrupt?
I have used both adb and the "recovery installer" tool from this forum.
btw I can boot into the OS fine. It just seems to be a recovery issue.
edit: Solved it. Basically only nameless recovery works, the others are the wrong resolution.
Click to expand...
Click to collapse
Hey I have the same issue, and guessed it was the resolution as well. Where did you get mentioned recovery? Thanks!
Jirapat S. said:
Hey I have the same issue, and guessed it was the resolution as well. Where did you get mentioned recovery? Thanks!
Click to expand...
Click to collapse
http://sourceforge.net/projects/namelessrom/files/recoveries/find7-universal/
Hey, thanks for the quick response. Now that I have a proper recovery, will I get the same issue when falshing the latest TWRP?
Edit: why is my screen all of a sudden all reddish? and when booting the device there seems to be white edges around what is supposed to be black boot screen?!
Did you get your phone from Amazon? Or did it came with COS 1.2.8?
As far as I know, those come with some new hardware that isn't fully supported by custom roms or recoveries.
If it's the case, you better restore the original rom and recovery and just wait until things get fixed.
I've been away from Samsung phones for a bit over a year now, so I may have just forgotten something simple, but on my Note 2, I have TWRP on it and when I flash a ROM and gapps in TWRP, everything is fine, I reboot, and it's in a boot loop kinda? The whole phone doen't continuously boot and boot and boot, but the ROM never boots, the bootanimation is just there, going along, forever. I've tried Liquidsmooth 4.0 & 3.1.
Am I missing something? I'd like to NOT run stock/stock rooted, as I was using my Note 2 for Vainglory but now it lags too much on stock and I need to run a custom rom that's fast, great battery life, and minimalistic.
does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.
cfli1688c1 said:
does it stuck at the samsung logo? if yes, try to boot into recovery and wipe data and cache.
i sometime had that happen, when i odin to stock.
Click to expand...
Click to collapse
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom
xBr4v3x said:
No, it boots into the rom but all it does is boot forever, it plays the boot animation non stop and never fully enters the rom
Click to expand...
Click to collapse
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.
zlazaar said:
Keep away from TWRP on the Note 2, it is known to cause such problems. I did my self the experience.
Instead, use Philz recovery who do his job perfectly with all roms i tried until now.
Click to expand...
Click to collapse
Still getting the same problem.
I've tried twrp& philz. No success.
Trying to use LiquidSmooth, and all I get to is the bootanimation, an infinite loop of it.
So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks so much!
camcorder123 said:
Thanks so much!
Click to expand...
Click to collapse
No problem.
I've got this same problem. Thanks for the TWRP fix!
Did you manage to get SuperSU / Root to work?
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
Thanks. It worked.
daleski75 said:
Use this recovery http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Click to expand...
Click to collapse
you are awesome, thanks so much this fixed my issue
recovery black screen and fastboot not working on computer
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.
vijaysivakula said:
HI .
I am stuck with this black screen on recovery problem. And fastboot is not working on my system. Please help.
Click to expand...
Click to collapse
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Fastboot not working
HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.
vijaysivakula said:
Fastboot not working on my office laptop. Funnily, it used to work earlier. Could someone help me with that? Or I will flash it over the weekend when i am home and revert to complete stock. The Community Build did not seem very attractive or useful in the few days I tried.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2317790
Minimal ADB and Fastboot.
Then just install drivers for your phone or do a search and you'll find it for the OnePlus 3
Worked For me too!
camcorder123 said:
So I clean flashed the newest community edition of Oxygen. Directly after I flashed it I flashed SuperSU. Everything goes well, no big error messages (I edited the updater-script for Oxygen). So I boot into Oxygen, and I can't find root. Everything is working beautifully but there's just no SuperSU. So I reboot to recovery, about to flash the zip again, but I get a black screen. Doesn't go away until I hold the power button for 15 seconds. Rebooted to fastboot, flashed TWRP recovery image. Same result, black screen when booting into recovery. Is there something I'm doing wrong? It's usable but I'd really like root....
Click to expand...
Click to collapse
Helped me too, thanks big time
LunaticWinchester said:
Helped me too, thanks big time
Click to expand...
Click to collapse
Got same issue. Notify me if there is any solutions...thx.
Thanks work like a charm!
Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?
coyotejodido said:
Sorry for reviving this thread, but I managed to solve my problem with this solution. however after a while, because of some problems I booted into recovery, and after seeing the TWRP logo the phone goes black and I can't do anything. I believe I might have killed my phone, but does anyone have some idea?
Click to expand...
Click to collapse
Plz check some of my older posts. I posted a stock recovery Link. Use that and you'll be able to boot just fine.
Sent from my ONEPLUS A3003 using Tapatalk
HermitDash said:
If your bootloader is unlocked and you can access the bootloader insteead of recovery just get fastboot working on your computer and you should be able to flash the TWRP listed above.
Click to expand...
Click to collapse
I have unlocked my bootloader. when i flashed twrp it showed a blank screen it is not tuning on after holding the power button for 20 min. please help
when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated
freddienuxx said:
when in twrp recovery its stuck/frozen cant swipe or put in pin or flash mods. any help would be appericiated
Click to expand...
Click to collapse
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.
Badger50 said:
Remove lock screen security and set it to swipe. Then boot into twrp a couple of times. If it starts working, then add your security back in.
Click to expand...
Click to collapse
ok thx gonna try now
freddienuxx said:
ok thx gonna try now
Click to expand...
Click to collapse
thank you so much that worked
freddienuxx said:
thank you so much that worked
Click to expand...
Click to collapse
Happy to help my friend :good:
After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
---------- Post added at 12:55 AM ---------- Previous post was at 12:50 AM ----------
KittyRgnarok said:
After helping one of my friends troubleshoot this on his pixel 2 xl we came to the conclusion that twrp doesnt seem to like the phone having a saved fingerprint either. disabling the fingerprint and keeping the password works. we havent tried turning it back on after the first decrypt though, will post after further testing
Click to expand...
Click to collapse
so during our initial testing we had two fingerprints which seemed to upset twrp. after a successful decrypt we added one single fingerprint and now it decrypts properly
I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?
benjmiester said:
I'm getting this suddenly even though I deleted pin and fingerprints. Maybe I need to return to stock recovery again somehow? Then flash twrp all over again. Anybody know where to get stock recovery?
Click to expand...
Click to collapse
Flash the boot.img. That's where the stock recovery now resides.
Badger50 said:
Flash the boot.img. That's where the stock recovery now resides.
Click to expand...
Click to collapse
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.
benjmiester said:
Thanks again Badger. It gives me "no command" with the mr. droid in surgery. Is that normal? It at least got rid of TWRP so I can try that again.
Click to expand...
Click to collapse
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??
Badger50 said:
What's the "Mr droid in surgery"?? What gives you no command?? Did you run fastboot flash boot boot.img ??
Click to expand...
Click to collapse
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.
benjmiester said:
Sorry, yeah I ran fastboot flash boot boot.img, do I need to boot it like the 1st step of installing TWRP? The android symbol with the red triangle and 'no command' is what I get after trying to enter recovery after flashing stock boot (to verify stock recovery was back). I don't see stock recovery though, shows that no command and Droid red triangle instead. I'm still critical unlocked from when I fastboot flashed factory image yesterday.
Click to expand...
Click to collapse
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.
Badger50 said:
Ah, now I understand. The droid dude in surgery, is the stock recovery. You have to hold power button and volume up simultaneously a couple seconds, then release volume up. It's a little tricky though. You can just fastboot twrp now if you'd like.
Click to expand...
Click to collapse
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:
benjmiester said:
So turns out the problem both before and just now when I tried flashing twrp and it was still frozen.... I forgot to flash magisk after flashing the twrp installer zip :crying::crying: It was trying to run TWRP on an unrooted system. Doh! I booted twrp a 3rd time, flashed twrp installer AND magisk. Now all is working fine.
It's the little things that always mess me up :laugh:
Click to expand...
Click to collapse
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out ?
Badger50 said:
Been there myself more times than I can remember over the last 7 years I've been hacking these things. At least you figured it out
Click to expand...
Click to collapse
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.
rsnyc said:
Badger50, you've been a great help and I hope you can come thru again for me. Maybe I'm missing something but I just finished updating my Pixel 2 XL to the June update and went to boot TWRP so I can flash Magisk and install TWRP but I get to the teamwin recovery project 3.2.1-2 splash screen and it's just frozen. I never got to flash anything. Any help is greatly appreciated.
Click to expand...
Click to collapse
Do you have screen lock security disabled?
Badger50 said:
Do you have screen lock security disabled?
Click to expand...
Click to collapse
Yes sir. I set it to swipe.
rsnyc said:
Yes sir. I set it to swipe.
Click to expand...
Click to collapse
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again
Badger50 said:
Did you let the OS boot up once? If so, then shut the phone off, and manually go into bootloader mode, then fastboot into twrp and try again
Click to expand...
Click to collapse
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.
rsnyc said:
I didn't let the phone boot up. I just flashed the update and then ran the command fastboot boot twrp... I will do that and report back.
Click to expand...
Click to collapse
No worries. Let me know :good:
Hello everyone, i got problem that i cant get into twrp(looks like motherboard problem), is there any way that i can install some custom rom through the fastboot or adb. Once again, TWRP is installed but when i want to get in it just keep black screen.
Have you tried another recovery?
What about flashing a miui fastboot rom with MiFlash?
YoSoyYoMismo said:
Have you tried another recovery?
What about flashing a miui fastboot rom with MiFlash?
Click to expand...
Click to collapse
I tried last 3 version of this one https://eu.dl.twrp.me/capricorn/ and still same bug.
And yes im already on fastboot rom but i still prefer custom because of magisk and gcam.
Have you pressed the power button when the display is black? My display always turns off as soon as it has booted into twrp.
Leni_YO said:
Have you pressed the power button when the display is black? My display always turns off as soon as it has booted into twrp.
Click to expand...
Click to collapse
Ofc i did, but remains black. Funny thing is that i can open xiaomi recovery but not twrp.
MickyZa said:
Ofc i did, but remains black. Funny thing is that i can open xiaomi recovery but not twrp.
Click to expand...
Click to collapse
Flash twrp twice, mine had same problem long ago