Database Info

Soft-- Bricked after Phone Died, Please Help.

Ive looked through all the bricked threads and elsewhere and nothing seems to match my problem.
{
"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"
}
S-off. As you can see its been awhile since I have messed with my phone so forgive me. I found something that had what I needed and was stable(until now) and stuck with it.
So I connected my phone to a friends charger and it wasnt charging and it died. I got it charged and booted it up and it ran fine for about 2 minutes then apps started stopping and it rebooted, it now does this over and over. I tried the battery reset. The last apps to crash are always google play services related so I tried to flash a gaaps zip in hboot.I tried uninstalling/deleting those apps, it still crashes. I tried to wipe and restore/install in twrp recovery(which it usually says is successful). Ive tried flashing RUUs in hboot they stop after the first reboot and boot normally instead of back to hboot. It wont connect to adb(I may have done something wrong there). But whatever I do it boots up exactly how it was before. If I delete/uninstall anything it comes back, if I add something anywhere other than the external sd it disappears.
Please help I cant afford a new phone right now.
Update: Without an sd card in the phone it wont reboot but all other things are the same, apps still crash, still cant do anything to recover.
Update: I tried another sd card and it prevents the reboot, but still wont flash anything in the bootloader.
Update: I formatted my sd card and it doesn't reboot with it in now, atleast not automatically, it reboots when certain apps are opened or randomly after a long period. Apps still crash and still no luck with any flashing or recovery. I tried clearing all app caches with titanium, no change.
I think the internal and system partitions may be corrupted and stuck as is after reboot, the weird thing is I can delete things or add things and the changes stay until reboot, then its back to its original state, is that possible?

Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x

piyushkohli97 said:
Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x
Click to expand...
Click to collapse
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.

Kane5581 said:
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.
Click to expand...
Click to collapse
So u keep the ruu or flash some ROM after that?
Have you tried different RUUs?
I also recommend flashing the firmware for whichever Android version you are using.
Try firmware from this link http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
Flash firmware after RUU flashing.
I recommend the latest ruu if you flash it u will not need to flash firmware.
In previous post I told you to reset your phone from stock recovery did you try that?

Please help, I'm stuck.

Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help

{
"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"
}

Have you updated your adb and fastboot? I've heard of a lot of problems cause by people's "minimal" setups being outdated. Also, there's a good chance you can get back to working simply by flashing the stock boot.img out of the system image you've already downloaded.

I think I have updated everything properly. At least, I think so.
When I try to flash just the system.img it hangs here;

OK, update. I was able to get NFM26Q to load up but it says my internal storage is corrupt upon booting and it doesn't recognize my SIM card (on Verizon). Should I flash a different factory image file? Or try something else? Thanks for any help.

iainaaldrich said:
Hi everyone, I'm at a loss at what to do here.
I've attempted to unlock my phone which I've done successfully,flash the twrp image, and install the twrp zip but now because I'm running into issues, I just want to return to stock, I'm stuck in between. I thought if I flashed stock img from google and started over it would fix everything - but when I do flash stock img I get "not enough storage" and i cannot proceed. I've searched up and down this forum for an answer but to no avail. I'd appreciate the help
Click to expand...
Click to collapse
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.

bobby janow said:
I thought I saw that re-locking a Verizon bootloader would cause possible instability and would not be supported. I'm not sure if you're still under warranty but you might want to look into a replacement if you can't get it figured out. If you successfully relocked it then you should be ok under service.
I think at this point you might want to try a factory/reset in the stock recovery menu and see if Q loads up. Without seeing where you are and what you've done it's hard to diagnose.
Click to expand...
Click to collapse
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.

Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.

iainaaldrich said:
First thing I did was unlock the phone, second thing I did was flash the IMG for twrp, booted into twrp and flashed the zip. I couldn't get past twrp, if I restarted the phone, it would just get stuck at twrp. So, I had no OS to boot into somehow and so at this point, I flashed the stock 7.1 file from Google and now it boots into the OS with no twrp, or bootloader, but the OS boots with an error message saying the internal storage is corrupt. I can use the phone but I have no data connection, camera fails to load, etc etc. So it's pretty useless. I made the mistake of thinking it would just be as easy as a Nexus, which clearly, it's not. I think I got everything I did there. I'm just trying to figure out how to get it back to stock, like right out if the box. My mistake surely, I'm just hoping someone can explain the necessary steps to get back to point A. Thanks for your help.
Click to expand...
Click to collapse
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.

iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.

robocuff said:
First, if you haven't already done so, update your adb/fastboot setup to the latest version. I see you're using minimal adb. The latest version is 1.4.1. You can get it here. From the looks of your first screenshot I'd guess you need to update. Whatever the case, run the flashall batch file again. I don't know how long you let it sit at flashing system but I've flashed mine a couple times and it hangs on system for what seems forever. It looks like it's not doing a thing but if you wait long enough, eventually it jumps to life and continues. Give it time. How long? I don't really know. Guessing mine hung there for at least 5 minutes, maybe more.
Click to expand...
Click to collapse
Thanks, I'll try this again. The last time I tried, it just froze. But good point.

bobby janow said:
Is your bootloader unlocked at this point? Have you tried a factory/reset from the stock recovery menu if you are not. If you are you can look for instructions on how to flash a factory image manually, which includes all the necessary files such as recovery, radio, bl, vendor etc. Just don't flash 7.1.1 yet. Get the phone working first on 7.1 (X) version preferably.
Click to expand...
Click to collapse
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.

iainaaldrich said:
When I boot up it has the unlocked logo, but if I try to boot into recovery I simply get "no command" with an exclamation point above the Android logo. So I'm not able to do a factory/reset from the recovery menu. I'll try refreshing everything again but I kept getting "not enough storage" or a similar error message.
Click to expand...
Click to collapse
In recovery with the no command logo, hold down the power key and hit the vol up key. That will get you into recovery where you can do those things. Use the vol keys to go up and down in the menu. Google stock recovery in android 7.1 for screenshots and more detailed instructions if you need.

I was able to get everything back up and running by following method 2 here - manually flashing using minimal adb: http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/ and using the verizon 7.1 image from google's site, then updated to 7.1.1 on an unlocked bootloader, everything is working fine, however I am having one issue - seems as though the system flashed twice? I should have a lot more storage than this:
Is there a way to completely wipe everything and manually reflash the stock image?

Anybody know what I can do to wipe everything and start fresh? My bootloader is already unlocked. Thank you!

iainaaldrich said:
Maybe I need to lock the bootloader lock this phone again then flash stock IMG from Google for the OS?
I'm at a complete loss. I've tried almost everything I've read on XDA, and elsewhere.
Click to expand...
Click to collapse
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs

TonikJDK said:
Do not relock your bootloader. Ever.
Get your fastboot up to date, and use the flash all script that comes with the factory image.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....

iainaaldrich said:
Yeah, I'm not going to. I got it working by flashing it manually, the flash all script didn't work. How do I erase everything? Because for some reason now, my system image takes up almost all of my internal storage. It's as if, I have multiple system images on the same device...or something....
Click to expand...
Click to collapse
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs

TonikJDK said:
Is this a 128 or 32? 128 often misreports space after flash. Have to factory reset to get it back.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.

iainaaldrich said:
No, 32. It's reporting correctly, but I don't get why it's taking up so much space.
Click to expand...
Click to collapse
How much does storage say system is using?
Sent from my Pixel XL using XDA Labs

[Recovery][Official] TWRP 3.4.0-15 [T860/5][22.Jul.2020]

{
"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"
}
Official TWRP 3.4.0 for SM-T860 + SM-T865
Telegram thread
Built using OMNI source 9.0
TWRP v3.4.0
See post #2 for install steps
Changelog...
v1
Initial build
MTP, OTG and SDcard all working
Encryption not working, but being implemented later
* There is a kernel in the download folder for the T865, flashing this after booting into TWRP should give T865 full function.
v2
Added T865 support
Updated kernel to SI3
v3
Fixed img flashing
v5
Encryption support added
Fixed brightness function
v7
Now using a recovery_dtbo
v15
Updated to 3.4.0 twrp
Updated kernel and dtbo (TF2 Android 10 only)
TWRP Downloads
Download TWRP 3.4.0 folder T860
Download TWRP 3.4.0 folder T865
WETA Kernel
Telegram thread
Thanks to @geiti94 and @klabit87 for allowing me to constantly pick their brains
--------------------->
Beer fund
XDA:DevDB Information
Galaxy Tab S6 TWRP, Kernel for the Samsung Galaxy Tab S6
Contributors
Mentalmuso, mentalmuso
Source Code: [Kernel Source
Version Information
Status: Stable
Created 2019-09-30
Last Updated 2019-09-30

TWRP installation changed
Download folder.T860
Download folder.T865
WETA Kernel
* Unlock bootloader first
* Reboot recovery and reboot system now behave normally after flashing.
* No more patching in Magisk manager at all.
* Be aware, first clean boot, hangs on building cache, hard reboot after waiting about 3min and you'll boot past this
* If simply updating your existing TWRP, v9 upwards, you only need to flash the TWRP.img in recovery. No need to reflash kernel and Magisk.
Process from bone stock
1. Flash TWRP.tar in Odin
2. Reboot directly into TWRP
3. Format data, reboot recovery
4. Flash custom kernel (Android 10, this is optional)
5. Flash encryption disabler.
6. Unmount system, Flash Magisk 20.4
7. Reboot system
Process from existing TWRP
1. Flash TWRP.img to recovery
2. Reboot recovery
3. Flash Kernel zip
4. Unmount system and Flash Magisk zip
5. Reboot system
--->

WooHoo!..and THANKS! and WooHoo!

If anyone tries flashing this on the LTE device let me know if it works out fine, including booting into system and checking WiFi and everything works.

Go stuck at file analysis in Odin with my T865. Tried to download the TWRP.tar many times still got the same problem. Thanks anyway.
Sent from my SM-T865 using Tapatalk

sbluescab said:
Go stuck at file analysis in Odin with my T865. Tried to download the TWRP.tar many times still got the same problem. Thanks anyway.
Click to expand...
Click to collapse
This is quoted from a Google search.
"It's almost always the fact that you didn't have Odin up and running with all the info in ahead of time before you plug the tablet into the USB port"
I'll check the tar file when I get home, but i doubt it's the file. I could be wrong but...

Mentalmuso said:
This is quoted from a Google search.
"It's almost always the fact that you didn't have Odin up and running with all the info in ahead of time before you plug the tablet into the USB port"
I'll check the tar file when I get home, but i doubt it's the file. I could be wrong but...
Click to expand...
Click to collapse
I can flash firmware and root my T865 with Odin without any problem.
Sent from my SM-T865 using Tapatalk

My current stat. Rooted with Odin.
Sent from my SM-T865 using Tapatalk

sbluescab said:
My current stat. Rooted with Odin.
Click to expand...
Click to collapse
Ok I'll check the tar file later. You can try since you are already rooted, pulling the recovery.IMG out if the tar, and using dd to flash it in an terminal emulator if you're Keen.
Or create another recovery.tar using 7zip to flash in Odin.
It may be checking the device number and denying it

sbluescab said:
My current stat. Rooted with Odin.
Click to expand...
Click to collapse
Im uploading a different tar for you to try in Odin
Try this, it's recovery only, you will need to be pre rooted
https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB

https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB
Try this, you will need to be pre rooted, this tar doesn't include the boot.img or nulled vbmeta.img.
And I used a different tool to package the tar

Mentalmuso said:
https://nextcloud.justbeca.us/s/tDaTRQ5B5bkLpwB
Try this, you will need to be pre rooted, this tar doesn't include the boot.img or nulled vbmeta.img.
And I used a different tool to package the tar
Click to expand...
Click to collapse
Thanks. I will give it a try.
Sent from my SM-T865 using Tapatalk

Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Sent from my SM-T865 using Tapatalk

sbluescab said:
Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Click to expand...
Click to collapse
The whole time holding onto the vol up and bix button? If so I may need to supply a different kernel for the t865

sbluescab said:
Successful flash with Odin but I couldn't boot into TWRP. Stuck in this screen for about a minute then the tablet booted into the system.
Click to expand...
Click to collapse
Did it boot to a rooted system or stock?
If you could go into the telegram thread and we can chat about it in there, id like to get this sorted out for other users

Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Sent from my SM-N975F using Tapatalk

The tablet is running fine now. Magisk is working right after the tablet booted. But it just can't boot into TWRP. Tried to reboot to recovery from Magisk and manually still not working. Seems to stuck about a minute or 2 at this screen everytime I reboot or try to boot into TWRP then it just boot straight to the system.
Sent from my SM-N975F using Tapatalk

sbluescab said:
Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Click to expand...
Click to collapse
First clean boot, you need to hard reboot after 3min

sbluescab said:
The tablet is running fine now. Magisk is working right after the tablet booted. But it just can't boot into TWRP. Tried to reboot to recovery from Magisk and manually still not working. Seems to stuck about a minute or 2 at this screen everytime I reboot or try to boot into TWRP then it just boot straight to the system.
Click to expand...
Click to collapse
You can't boot to recovery from magisk. It won't work.
You need to manually reboot to recovery.
Hold down vol up and bix button until the splash screen, then let go and reapply the buttons again quickly, while the red writing is present. Keep holding them. That is how I get to recovery.
But they're may be more going on seeing as though you got a t865

sbluescab said:
Finally, I could boot into TWRP after using dd to flash it in an terminal emulator. After that I flash the encryption disabler and format data then I try to reboot into TWRP again but it did not. In stead it's booting in to the system now. Still stuck in Samsung logo now.
Click to expand...
Click to collapse
Seems like that tar file was screwed up somehow. It wouldnt flash formme either, I've repackaged it and now it does. And I boot into recovery no issues.
Are you still having trouble getting into recovery?

Fail to Boot after after Google Play system update (Boot reason : init_user0_failed)

Hello all,
I wanted to report something that happened to me yesterday:
I recieved the following notification:
{
"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"
}
I selected "RESTART NOW" and when the phone tried to restart, it failed to boot (it didnt even reach the boot animation) and went into recovery. Within recovery there was an option (I think it was called Boot reason) to show the error that prevented the phone to boot into the OS. This was the error:
I tried to pull the files but I couldn't get adb access within the 8T stock recovery. I tried to reboot the phone from recovery but it failed to boot and I was back in the recovery with the same error.
The way that I managed to boot the phone was to select to reboot into recovery (while being in the recovery), and then select to reboot the phone. That, for some reason rebooted the phone and it was able to boot into OS.
My 8T is full stock, with locked bootloader running OOS 11.0.5.6.KB05BA
Hope this is helpfull to someone.

I just received the same notification again. I am not sure if it is regarding the same update as yesterday because it was not applied, or if it is a new one. I have not tried to restart the phone.

I received the same notification but my phone restarted with no issues.
If you can back up the files from internal storage then do that and then flash OOS.

O wow. I'm glad that didn't happen to me either. I don't think you can reflash the OS. I sugget you back up everything just in case it doesn't want to restart later.

You can try manual update Google play system update from:
Security & Lock Screen --> Google Play system update
Btw, I had that notification yesterday, and for now everything is OK, and Google Play system update is "Septembar 1, 2020". Which version is yours?

I am on September 1, 2020. If I tap on it, it checks for updates and then says I need to restart to complete the update.

When I tap says, "your device is up to date"....

So I backed up the phone with the Oneplus Switch app. Copied the folder to my computer (had to zip it becaust the transfer was failing on a .jpg). Selected restart and was faced with the same issue. I restarted again from the recovery (without first rebooting to recovery as in the first post) and I saw a glimpse of the boot animation and then the phone restarted again. After that it booted into the OS and if I check for updated it says that the device is up to date.
Hopefully this will be the end of this issue.

the issue is the canary magisk and secure boot trying a different magisk version repatch boot img and boot it to flash it

I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.

bad pixel said:
I haven't rooted or unlocked the bootloader ever on this phone. My phone is full stock. Locked bootloader running OOS 11.0.6.9.KB05BA. I still get this error when I reboot my phone. Up till now, doing the reboot to recovery "trick" as in the first post, or reboot into fast boot from within recovery, then boot into recovery, then start the phone. Manages to boot the phone.
I just hope that someone can figure out what is causing this.
Click to expand...
Click to collapse
You can try to download main-component apk from APKmirror, just download latest one (Januari), innstall it, and try redownloading the system update and restart. In my case, it restart just fine. And am on Cyberpunk H2OS 11.0.6.8, BL unlocked, Rooted

see the error, you may flash the third kernel.
just flash back the original boot img, and you can install Google Play System Update successfully.
you may suck in this error screen 1-2 times when reboot with third kernel, just exit and reboot, it will boot into system normally, don't worry.

[SOLVED] Poco X3 NFC - Bootloop after Wiping & Flashing Custom ROM

Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you

DrakMC said:
Hello, today I wiped Dalvik / ART Cache, Cache and Data because I wanted to install Custom ROM.
Maybe I also accidentally wiped Internal Storage or System. Then I flashed the Custom ROM. Now after the Custom ROM flashes again, the boot animation will hang and then the phone will restart shortly. I don't know how to solve this situation. I tried to flash the MIUI using the Xiaomi Mi Flash Tool, install the ROM through Fastboot, but nothing worked.
Please anyone know what to do with this? Thank you
Click to expand...
Click to collapse
You didn't explain your Problem quite well. Does it reboot to fastboot or does it reboot to system? (aka a Bootloop). if it reboots to system, here's what to do:
Boot into a custom recovery (twrp/Orangefox) and flash the required recovery MIUI ROM mentioned in your custom ROM's thread instructions.
Flash the custom ROM/Gapps, followed by Formatting /data using the Advanced Options in the wipe menu.
Reboot.
If you can't find the format option (which is mandatory before a new boot of a custom ROM), you can use this command while in fastboot mode:
Code:
fastboot erase userdata
Formatting /data is required for Encrypted devices to reset the encryption key and avoid a Bootloop. Please refer to this thread for more Custom ROM flashing instructions. If all else fails, you could EDL flash your device through MI flash tool/Command line, this process costs money (you need an Authorized Xiaomi Account) to complete.

Thank you very much for your help!
Slim K said:
Does it reboot to fastboot or does it reboot to system? (aka a Bootloop).
Click to expand...
Click to collapse
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)

DrakMC said:
Thank you very much for your help!
It depends when. When the MIUI flashes through the Mi Flash Tool, the Poco logo is displayed and the phone restarts and the Poco logo is displayed again. All the time.
So I followed your instructions.
I would like to flash ArrowOS, but nowhere do they write what version of MIUI I need. That's why I flashed this version of MIUI through Mi Flash Tool: https://xiaomifirmwareupdater.com/miui/surya/stable/V12.0.8.0.QJGMIXM/
After I flashed MIUI using Mi Flash Tool and then I booted into TWRP and installed the downloaded ArrowOS. After installation, I went to the Wipe section and deleted the Data. Then I restarted the phone to System. The Poco logo was displayed and after a while the phone booted into TWRP. So I don't know where the problem is. (Before ArrowOS flashed, the cell phone tried to boot into the system, the Poco logo was still displayed, and then the phone restarted.)
Click to expand...
Click to collapse
Again, when I say FORMAT, I meant formatting by typing ”yes".
Also, you haven't looked at the ArrowOS thread close enough, see:
{
"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"
}
It says latest R firmware, basically V12.0.7.0.RJGEUXM. Another point I mentioned is the fact that a recovery MIUI is flashable through TWRP/Orangefox and not Fastboot/Mi flash tool, It comes in a .zip archive.
Regarding returning to stock, have you tried booting into stock recovery after fastboot flash and factory resetting? That could work.

Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
I'm using TWRP 3.5.2_10-1-surya.

DrakMC said:
Okay, I downloaded this ROM: https://xiaomifirmwareupdater.com/miui/surya/stable beta/V12.0.7.0.RJGEUXM/
I tried it to install it in TWRP and I got error 1:
View attachment 5307411
I'm using TWRP 3.5.2_10-1-surya.
Click to expand...
Click to collapse
Error 1 just means a mismatch between the underlying stock and the newly flashed ROM, just ignore it and flash ArrowOS, Format data and reboot. If it still doesn't work, then return to stock through fastboot. (I never encountered so many problems as you did)

I followed your instructions. When I turn on smartphone, the Poco logo is displayed, then the ArrowOS animation will appear and freezes. After a while, the mobile phone restarts and this is repeated over and over again. (If I flash MIUI using the Mi Flash Tool, I also have a bootloop.)

I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!

just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!

sevachcomunist4 said:
just logged to thank u, mine was bricked too since an unsuccessful downgrade try, and I forgot to disable lock option in MiFlash, so I needed to wait 1 week to unlock bootloader again. I've tried everything, but ur post have saved me. ty very much for ur help, this tip can help a lot of ppl in the future. have a great weekend!
Click to expand...
Click to collapse
You're welcome! I'm glad I could help someone! It took me about 40+ hours to resolve this issue before trying all possible methods.

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
please give me link

DrakMC said:
I finally fixed the bootloop!
It was enough to take persist.img and flash it in TWRP before flashing MIUI via Mi Flash Tool.
Thank you very much everyone for your help!
Click to expand...
Click to collapse
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.

DP FH said:
You literally saved my life bro. Why??? Flashed 30 times from fastboot and nothing. Just did what you said and phone booted smooth like a charm.
Click to expand...
Click to collapse
You are welcome. I'm glad I could help someone.
I was whole week without the phone until I've fixed it. It took me over 40 hours to fix the issue.