Database Users

Nexus 4 stuck at Google Logo Screen

Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?

linezero said:
Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?
Click to expand...
Click to collapse
You're sure you wiped everything except data/media? There isn't anything that could cause this, except if both PA zip and the 4.2.2 zip are somehow both bad downloads. Chech their md5 sums.
Also, post a step by step of what you did.

abaaaabbbb63 said:
You're sure you wiped everything except data/media? There isn't anything that could cause this, except if both PA zip and the 4.2.2 zip are somehow both bad downloads. Chech their md5 sums.
Also, post a step by step of what you did.
Click to expand...
Click to collapse
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the charm I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.

Shaldy said:
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the chard I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.
Click to expand...
Click to collapse
lucky you, you did it, mine n4 just crashed while normal using, cm 10.1.2, so it was android 4.2.2 and it cant boot now :< i can enter recovery, but phone is always stuck on google logo, even though i installed 4.2 stock that i sideloaded via adb (wasnt working) and then i used adb push, and its still the same... now i have to do as You, lock\relock and stock again
\\\EDIT: wug root toolkit (rootkit xD) helped, flashed 4.2.2 stock + unroot, now root and flash recovery, then pa or some other rom, cant stand lacks of clean android (4.3, and still no changing tracks with volume buttons?!) was worth to buy nexus 4 "unbrickable" android as zte blade sucessor, which is also unbrickable and undestructible

I have the same issue. I took a nandroid backup and flashed Paranoid Android 4.3. Now when I'm trying to restore the nandroid backup, my phone is stuck on 'X' screen during bootup. Logcat is stuck on
"D/dalvikvm( 481): GC_CONCURRENT freed 1501K, 10% free 15065K/16628K, paused 3ms+3ms, total 61ms"

i got that problem too
linezero said:
Before flashing the new Paranoid Android Rom (4.3 one) I decided to to do a data wipe from TWRP...well to wipe out everything including SD card. The phone booted up with the rom which was there but however after flashing the new rom or any rom now. I'm unable to boot my nexus 4. I'm always stuck at the Google screen, the one with the lock. I tried flashing a 4.2.2 rom and still had no luck. So any help with that?
Click to expand...
Click to collapse
hi, i was with that problem too, firsto of all you have to download this hings: adbht, sdk, fastboot, nexus root toolkit and the factory image of android. With those things you could be able to repair your phone the tutorial is here on this webpage

alfredoeguez97 said:
hi, i was with that problem too, firsto of all you have to download this hings: adbht, sdk, fastboot, nexus root toolkit and the factory image of android. With those things you could be able to repair your phone the tutorial is here on this webpage
Click to expand...
Click to collapse
Need help with my Nexus 4 !!
Device was unlocked and rooted. But I just want to return to the original state so I did a "Unroot Nexus 4 to Stock 4.2 on Mac!"
After step 10. When i "wipe data/factory reset" on the "Exclamation Android mascot", I couldn't do anything and got stuck at Google Logo. Couldn't flash anything and just stuck at FASTBOOT and Google Logo. Please help?
Thanks,
EJ

ewejin9394 said:
Need help with my Nexus 4 !!
Device was unlocked and rooted. But I just want to return to the original state so I did a "Unroot Nexus 4 to Stock 4.2 on Mac!"
After step 10. When i "wipe data/factory reset" on the "Exclamation Android mascot", I couldn't do anything and got stuck at Google Logo. Couldn't flash anything and just stuck at FASTBOOT and Google Logo. Please help?
Thanks,
EJ
Click to expand...
Click to collapse
Is your bootloader still unlocked?

I hope it is ok if I post here too..
I am stuck at the google screen.
Backupped everything to my computer.
Using TWRP 2.6.0.0 to full wipe.
Installing 4.3 Rom and gapps, rebooting.
Everything ok, did some app installations.
Reboot recovery.
Format data.
Reboot again.
Everything fine.
Now I installed my apps I use all the time to do a nandroid backup of my new/fresh setup.
Backup runs through, reboot system. Google screen.
Why is that?
Edit:
Nice one. Nandroid restore doesn't work.
:/ Stock image, here I come again!

Shaldy said:
I'm having the same issue here, I flashed the latest PA ROM, full wiping everything with the latest TWRP, now I'm stuck on Google logo screen.
Now I have tried rolling back to stock 4.2.2 with stock bootloader, stock recovery, stock everything. Not working!
Kinda scary. Fastboot and recovery works fine. Please advise.
EDIT: Second time is the chard I guess. I locked/reunlocked the bootloader and flashed a 4.2.2 stock image again and it booted fine, that's effing weirld.
Anyway, it looks like that some N4s don't like the new bootloader or radio image. Be careful.
Click to expand...
Click to collapse
Thank u man, u save my nexus 4

Same...
Having the same problem. After a billion fasboot formats and failed recovery attempts...uhhh, nothing.

Solution?
Fellows, I have a probable solution...worked for me:
http://forum.xda-developers.com/showthread.php?p=45394792&posted=1#post45394792

solved this by flashing stock 4.3 from Google:
https://dl.google.com/dl/android/aosp/occam-jwr66y-factory-74b1deab.tgz

The same happened to me but without doing anything . device totally stock, I rebooted it and when restarted it didn't start anymore.
From there I tried to flash it with the stock 4.4.2 ROM, didn't work. Tried with 4.4 and 4.3 but nothing. Back to 4.4.2 and nothing again.
Any suggestion?

Niddu85 said:
The same happened to me but without doing anything . device totally stock, I rebooted it and when restarted it didn't start anymore.
From there I tried to flash it with the stock 4.4.2 ROM, didn't work. Tried with 4.4 and 4.3 but nothing. Back to 4.4.2 and nothing again.
Any suggestion?
Click to expand...
Click to collapse
Tried with also a cyanogenmod ROM but nothing. The ROM is different but the result is the same... Keeps on turning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Worked the same for me rolling back to version 4.2.2
Upgrading again brings me back to bootloop.
Is there any chance to have the newest version working?

Niddu85 said:
Worked the same for me rolling back to version 4.2.2
Upgrading again brings me back to bootloop.
Is there any chance to have the newest version working?
Click to expand...
Click to collapse
Update your recovery version
Sent from my Nexus 5

jd1639 said:
Update your recovery version
Sent from my Nexus 5
Click to expand...
Click to collapse
What do you mean? Can u please give me some steps to follow?
Thanks

Niddu85 said:
What do you mean? Can u please give me some steps to follow?
Thanks
Click to expand...
Click to collapse
What custom recovery are you on? Twrp or cwm, update to the latest version
Sent from my Nexus 5

jd1639 said:
What custom recovery are you on? Twrp or cwm, update to the latest version
Sent from my Nexus 5
Click to expand...
Click to collapse
At the moment I flashed all the factory ROMs with the stock recovery via "flash-all.bat" file included . I only used TWRP 2.7.0.0 when I tried with cyanogenmod but I had the bootloop with it anyway
The only working combination at the moment is stock ROM with stock recovery but 4.2.2. I would like to upgrade again to 4.4.2 but I don't know how

Stuck on Bootloader

I feel like a super super noob here in this particular learning curve, my phone is a Samsung S5 G900T1UVU1ANE7.
It's currently stuck on the Samsung Boot screen thing and won't go any further even fully charged.
For this particular phone I want it streamlined just with no bloatware or the such tweak and optimized it's a great phone 16 MP and I wanna use it I just need to get it back working and would appreciate any help.
I have no problems answering any questions to what I've done so far or will do.
:cyclops:

Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?

Saber said:
Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?
Click to expand...
Click to collapse
Yes to both but not opposed to trying again if need be.

I would suggest first doing a odin flash with a fully stock rom just to get the phone back up and working. After that you might look into another rom, something de-bloated and maybe rooted. To do that you will likely need to flach twrp from download mode ( remember uncheck auto reboot in odin )then boot into recovery and move over the new rom / zip, wipe, then install and reboot ( dont forget gapps if its not in the rom ).
For whatever reason for me it seems like every time i install a new rom i need to first go back to factory stock rom first on my sprint s5.

Saber said:
Have you tried a factory reset (delete all data from phone) while in recovery (holding home + power + vol up while screen off)?
If that doesn't work, have you considered flashing the latest stock firmware via ODIN?
Click to expand...
Click to collapse
Just tried the above after I got TWRP on and when trying the factory reset it says E:Unable to mount ' /system'

Wdwaring said:
Just tried the above after I got TWRP on and when trying the factory reset it says E:Unable to mount ' /system'
Click to expand...
Click to collapse
Seems like the system partition got corrupted. Have you ensured that you have the latest TWRP version (3.1.0)? What happens when you try to factory reset using stock recovery (3e recovery)?

Saber said:
Seems like the system partition got corrupted. Have you ensured that you have the latest TWRP version (3.1.0)? What happens when you try to factory reset using stock recovery (3e recovery)?
Click to expand...
Click to collapse
Ok I have TWRP 3.1.0 on it now I try to install Reserection Remix rom and this is the error i get from TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The system partition is borked. How did you achieve this feat? The only way to get it back up and running is by replacing the eMMC. No matter how many times you format it, no matter how many times you pray to it to work, it's half dead. And don't even dare think about re-partitioning because you'll probably end up damaging it even more than it is now. And hello there @Saber

Wdwaring said:
I feel like a super super noob here in this particular learning curve, my phone is a Samsung S5 G900T1UVU1ANE7.
It's currently stuck on the Samsung Boot screen thing and won't go any further even fully charged.
For this particular phone I want it streamlined just with no bloatware or the such tweak and optimized it's a great phone 16 MP and I wanna use it I just need to get it back working and would appreciate any help.
I have no problems answering any questions to what I've done so far or will do.
:cyclops:
Click to expand...
Click to collapse
what happens after flashing stock via odin. is it stuck on boot, it can take upto 15min sometimes to boot after flashing stock.
ts rom install:
Backup Both Sdcards To Pc
Remove External And Format Internal Fat32
Copy Fw To Internal & Check MD5
Put Phone In Download Mode.
Start ODINv3.10 And Uncheck Auto Reboot
Flash Stock 6.0.1 MM Fw For Your Phone Model Via Odin AP Button
When Install Is Complete Remove Then Reinstall Battery.
Boot To Stock Recovery
Then Wipe Data, Caches And Factory Reset Within "Stock Recovery" To Start Fresh.
u can try this custom stock superlite rom i made for some of the #7 twrp errors, takes only a few minutes(6min max) to install and boot and a fast way to see if phone can boot, need to be on 6.0.1 bl and mdm, tested w/Twrp 3.1.0-0. rom thread in my sig
https://www.androidfilehost.com/?fid=817550096634756035

vincom said:
what happens after flashing stock via odin. is it stuck on boot, it can take upto 15min sometimes to boot after flashing stock.
ts rom install:
Check MD5
Backup Both Sdcards To Pc
Remove External And Format Internal Fat32
Copy Fw To Internal
Put Phone In Download Mode.
Start ODINv3.10 And Uncheck Auto Reboot
Flash Stock 6.0.1 MM Fw For Your Phone Model Via Odin AP Button
When Install Is Complete Remove Then Reinstall Battery.
Boot To Stock Recovery
Then Wipe Data, Caches And Factory Reset Within "Stock Recovery" To Start Fresh.
u can try this custom stock superlite rom i made for some of the #7 twrp errors, takes only a few minutes(6min max) to install and boot and a fast way to see if phone can boot, need to be on 6.0.1 bl and mdm, tested w/Twrp 3.1.0-0. rom thread in my sig
https://www.androidfilehost.com/?fid=817550096634756035
Click to expand...
Click to collapse
NOTE: There needs to be a text chat option on the page so people could possibly chat live with ppl and get walked through the process some people learn better that way. Tryn your rom here,
Actually I need to be walked through step by step, you guys already know this stuff like the back of your hand, so far I have TWRP 3.1.0 on the phone thats it, whats the next step.
Ok I went ahead and grabbed the file you recommended and installed it, it rebooted twice now and is on the Samsung word blinking might take the 15 mins referred to as it takes sometimes, we'll see what happens.
Ok, looks like it may have worked will keep everyone informed after a bit

BOOTLOOP
im not sure what i did wrong but it went like this
1 recovery mode
2. wipe data/factory reset
3. wipe cache partition
after this phone stuck on logo at start up
4. hardware keys to enter recovrey mode
5. boot to bootloader
now stuck in download mode
6. back to rec mode, repeat fac reset
now back stuck to logo at start up
pls anybody help me

Stuck at loading screen after trying to go from LineageOs 14 to stock to Lineageos

So, in short:
I wanted to try the stock ROM on my Oneplus 5 now that it got an update to Oreo. I was going from Lineageos 14.1 to OOS 5.0.1.
Tried to flash it using TWRP, didn't work. . Found out I had to use an updated TWRP specifically for Oreo. Did that, got Codeworkx's TWRP and flashed it, and then the stock ROM. Stock ROM got stuck in loading screen for 20+ minutes. After that, everything was encrypted when I looked in TWRP. So I wiped everything. Also tried using the stock recovery. No dice, couldn't even install anything from internal storage. After trying a few things I wanted to go back to LineageOS 14.1 (same build as I had before), but now that one's stuck in loading screen as well for over 20 minutes.
Here are the things I've tried:
Using different recoveries, from Codeworkx's TWRP to Blu_spark's to the original TWRP. The Original TWRP recovery does not work anymore. Gives errors when trying to do things like wipe. Installing ROMs gives errors as well.
Tried installing just the ROM, and the rom + Magisk and the rom + magisk + open gapps. Always stuck on loading screen.
I'm trying to flash the latest ROM for Oneplus 5.
I'm trying to push more stuff onto the phone using adb, but right now I'm getting the "error: closed" error message.
The only thing I can try are flashing stock rom, then stock recovery and tehn locking the bootloader, but the latter will erase everything from the internal memory, and if I can't adb sideload stuff anymore, I'm not sure what I can do with the phone...
Edit: Another weird thing I noticed:
After it's been loading for 20+ minutes, the phone shows it's at 0% charge, then when I enter recovery, it's back to 100%. The phone is connected to my computer the whole time.
Edit 2: I tried to flash an android 7.1.1 version of OOS (OOS4) to my phone, this went fine. Booted up the phone, got an "encryption unsuccesful" error. On next boot, recovery is back to stock instead of TWRP. Flashing TWRP and then doing a factory reset has no effect.
These are the errors I see when I use the normal TWRP recovery (so not codeworkx's or blu_sparks' version:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you are updating the OP5 from Nougat to Oreo and you are encrypted you need to format the data on your phone. You can do it with TWRP (the option is part of the wipe tab). That will erase everything on your phone except TWRP. If you plug your phone into a computer it will act like an external hard drive and you can simply copy and paste the ROM zip onto your phone and then flash it with TWRP.
If you are decrypted you need to flash the no verity zip for OOS to boot up.

Thanks for the reply. I managed to get lineageos 15 running on the phone without problems. Not totally satisfied with it, so if/when I flash back to LineageOs 14.1 I'll keep this in mind. Thanks!

ze550kl - lineage official infinity reboots

asus zenfone 2 laser ze550kl with 2 GB ram and 32 internal - i bought it as snapdragon 410 checked device info apps it said it's eight cores and MSM8939 615 confused
Bootloader unlocked
Got TWRP *tried twrp-3.0.2-0-Z00L and twrp-3.2.1-0-Z00L
lineage os *tried lineage-14.1-20180311 and lineage-14.1-20180318
installed successfully
infinity reboots never loads into the system, sometimes it gets to lineage os animations boot and then reboots again
any ideas

Do factory reset and then reboot

deepakt6699 said:
Do factory reset and then reboot
Click to expand...
Click to collapse
The phone never passed lineageos boot animations, I switched back to the stock rom

update
tried
AospExtended-v5.3-Z00L-20180311-0437-OFFICIAL
lineage-15.1-20171209_174211-UNOFFICIAL-Z00L
RR-N-v5.8.5-20171130-Z00L-FINAL
they are all passing twrp installing - again infinty restarts never passed rom boot animations

Format data in TWRP and retry.

okmikel said:
Format data in TWRP and retry.
Click to expand...
Click to collapse
didn't work tried a lot of times with the roms i mentioned nothing work
all keep rebooting never pass animations
maybe my device os not z00l i don't know
here's SCR of cpu-z
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

up

up

reload the current twrp
make sure you wipe/format everything
try octos n m2 (this is my go to when i want an everyday rom)
try loading the rom without any gapps packages (gapps may be the problem)
i have a z00t, not z00l but that shouldn't matter.

beenkenobee said:
reload the current twrp
make sure you wipe/format everything
try octos n m2 (this is my go to when i want an everyday rom)
try loading the rom without any gapps packages (gapps may be the problem)
i have a z00t, not z00l but that shouldn't matter.
Click to expand...
Click to collapse
thanks man <3 , downloading and will try btw every rom i tried was without gapps and everything was wipe and used two diff twrp versions ... that's wat made me so confused because all comments saying works perfectly

beenkenobee said:
reload the current twrp
make sure you wipe/format everything
try octos n m2 (this is my go to when i want an everyday rom)
try loading the rom without any gapps packages (gapps may be the problem)
i have a z00t, not z00l but that shouldn't matter.
Click to expand...
Click to collapse
the same issue asus logo and sometimes it gets to the rom logo then it keeps restarting

Rebooting Only Boots to TWRP; Not The OS

I had HavocOS working before with Magisk on my phone, but TWRP was locked from mounting the internal storage because of some forced encryption android does. To stop the forced encryption, I installed ForceDisableEncryption-Treble Initially I found it in a Pocophone F1 Video but Treble seemed to be for Android in general in my phone, and flashed PixelExperience at the same time too (with following the same wipe method: Dalvik / Art Cache; System; Data; Cache) because HavocOS was being unstable for me, and since then it has been always rebooting into recovery and not the actual ROM itself. I even tried HavocOS again, and still it did not work. So I looked around the forums to seek a fix and I found this: https://forum.xda-developers.com/showthread.php?t=2451696
I wrote the command "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" on my phone since I did not have an available computer at the time, and It weirdly stated that the directory did not exist.
EDIT: I also reflashed TWRP and just tried flashing again, same results making me panic, but I don't think the phone is dead since it still reboots to recovery.
I do not know what to do now.

Noiseredux said:
... I do not know what to do now.
Click to expand...
Click to collapse
Format the data partition.

DarthJabba9 said:
Format the data partition.
Click to expand...
Click to collapse
Still nothing. I think I corrupted the file system by changing it to EXT2 then back to EXT 4 to remove the encryption
I did that before the treble though, and my phone still booted up to the ROM, but it still encrypted itself, so I used the ForceDecryption and it's only been booting to recovery since.

Noiseredux said:
Still nothing. I think I corrupted the file system by changing it to EXT2 then back to EXT 4 to remove the encryption
I did that before the treble though, and my phone still booted up to the ROM, but it still encrypted itself, so I used the ForceDecryption and it's only been booting to recovery since.
Click to expand...
Click to collapse
Well, you might have to flash a fastboot MIUI ROM with the Mi Flash tool. Just make sure you don't accidentally lock your bootloader again.

DarthJabba9 said:
Well, you might have to flash a fastboot MIUI ROM with the Mi Flash tool. Just make sure you don't accidentally lock your bootloader again.
Click to expand...
Click to collapse
Good news! I got into MIUI 10 by the Mi Flash tool. I chose "clean all" in the software, so I think it erased everything. One problem occurred though, the MiTool was still continuing to show "Flashing" and not "success", even after booting up and everything. I closed it, hopefully it doesn't break things.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Should I try to install TWRP and PixelExperience now again?

Noiseredux said:
Good news! I got into MIUI 10 by the Mi Flash tool. I chose "clean all" in the software, so I think it erased everything. One problem occurred though, the MiTool was still continuing to show "Flashing" and not "success", even after booting up and everything. I closed it, hopefully it doesn't break things.
Should I try to install TWRP and PixelExperience now again?
Click to expand...
Click to collapse
I am also stuck on same issue with my poco F1, and I even tried flashing fastboot rom but it did not boot into system.