Develop Bugs

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.

guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine

clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?

guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU

Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"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"
}
Sent from my HTC One M9 using Tapatalk

mobile installer application popup restarting phone?

About once a week, not really sure on the frequency, (if I notice the popup) it says it rebooting the phone with two toggles on the bottom of the box. (box and lettering all in black and white) Your choice on the toggles is reboot or later. Today I push later and it it popped up twice more. But on the third time, there was not toggles and was doing a count down for reboot.
Anyway, before it rebooted, I pulled down the notifications and and found the notification and did a long press on it and then went into info. I then it looked like I was in settings with two choices there. (when on this settings, there was not back button to see were I was at in settings) To block notifications with on or off and the other doing something with quite mode. I turn off notifications and minimized the box. After it rebooted, the box was still minimized until wanted to bring it back up in the screen, it disappears. Anyone know what this is??? or know how to figure out what's doing it?
Stock Sprint Note 4 running 5.1.1 software Ok1 with hotspot hack (why I'm not running current software)

Open root browser and see if you have this folder: /carrier/ItsOn
If so, you may also have this file in dalvik (i think that's the proper location for Lollipop but you could search keyword itson) : /data/dalvik-cache/carrier @itson@[email protected]@classes.dex
If your ROM is fully stock, you may have another folder at /system/vendor/ItsOn. If so, look inside that folder for resource zip. Extract that zip and look in the folder and file install locations then browse to those in your phone's folders and delete all that correspond to that mapping.
If you have those, delete all you find and reboot. Hopefully that cures the random reboots.
If this applies, ItsOn has a bootstrapper that tries to install itself. If you have a custom kernel, it cannot complete this process but will try repeatedly to complete that failed setup process, prompting you continually reboot. If you were to factory reset, the prompts would most likely be more persistent.
If you flash a stock tar, then flash custom ROM and don't wipe internal memory, ItsOn remains unless developer has a script in place to remove that from root of your carrier folder.
Sent from my SM-N910P using Tapatalk

Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.

btb601 said:
Thanks for the info. Phone is not rooted, bone stock with the exception of the hotspot hack.
Only thing I found using File Viewer under Root (/) folder /system/vender/Itson. And it shows nothing is in there and one year old.
I believe all this started when I upgrade Lollipop about one year ago. Was rooted at the time and wanted the newer android. Then I found out I did not need to root to get the hotspot working.
Click to expand...
Click to collapse
OK. Check ItsOn status next. Goto /data/local/tmp and look for ItsOn log. It shouldn't get added on boot if you've removed it but last successful bootstrapper log will be present, unless deleted.
FWIW, I don't have random reboots on rooted phone. When I had them, ItsOn was the culprit. I usually clean install, wiping internal memory before and after stock tar but didn't coming from Lollipop.
What I noticed was that ItsOn showed in hidden menu ##data# as NetworkSystemProvider. See before and after wiping internal memory screenshots. I suspect this carried over from Lollipop. Perhaps yours did too?
{
"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"
}
Sent from my SM-N910P using Tapatalk

I could not find /data/local/tmp and look for ItsOn log, but I did get into data and the NetworkSystemProvider is there. Got into in and hit button for more settings and little window say "intent sent."
Also under more settings it says two things,
Module 1 is insmoded
Module 2 is insmoded
And at the top, it has a green icon for on button and a blacken icon for the off button. It will not let me do crap there.
Since it's stock, I have done nothing to it. Can't remember how I did the update. My guess since it was rooted, I had to flash OK1 myself but I don't see my stock download from Samsung. I have major memory issues, way more than I should at my age and I have no idea on how I did things......LOL And not even sure what Itson is, only thing I found with quick search a sprint software to add software and updates easily. That would explain the random downloads and install I did not do.
So now what, I need to root my phone to make this go away? Oh, and thanks again for your help. Don't go out or your way to dig further. I'm wanting to upgrade to MM but don't know much about it (rootable or hotspot wise).

The way I got rid of it was to wipe data and internal memory, flash marshmallow stock tar and wipe both again and flash a ROM that has it removed. Dunno but maybe it works the same way with a TWRP backup if you prefer stock with hotspot only?
I can't confirm there's another method or if that's your problem. But my random reboots are gone. FWIW, my log was inactive but had an existing log that dated months back. I only had a few random reboots until I did a factory reset to see if that would help. Once I did that, the reboots were much more frequent. Some boots were resulting in immediate request to reboot again. I had to do something at that point.
I couldn't tell you if updating to marshmallow makes it better but you could still could go back to Lollipop if it didn't.
I dunno if you need to root to make it go away but I can tell you there is hotspot mods for marshmallow. You can go back to Lollipop if you don't like marshmallow.
Sent from my SM-N910P using Tapatalk

Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.

btb601 said:
Thanks again, guess I'll give marshmallow a try here real soon. Maybe even try a custom rom, never played with any of those. But I getting to where I'll have to do something soon. I feel it's picking up the pace. Then again, new Notes will be coming out soon. We'll see what Samsung brings us. Thanks again.
Click to expand...
Click to collapse
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.

ianmb said:
I've had this happen before and the only way I was able to get rid of it was to flash a completely stock tar and let the device provision itself thru initial setup. Others have had luck with the removal of ItsOn, but this has happened on ROMS where ItsOn wasn't even present.
Click to expand...
Click to collapse
Thanks, I do just that when I decide where to go from here.

Potentially bricked? Sprint M9 unable to take OTA

Good evening folks. I am in desperate need of expert advice on this subject.
I imagine that other users have encountered this issue, and this thread may be useful in the future to the assistance of others.
I am rooted, and S-off (as of yesterday). Yesterday, I had TWRP 2.8.7 installed, with stock sense (and sprint bloatware), running android 5.0.1, on firmware 2.11.651.19
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***
*** UNLOCKED ***
htc_himawhl PVT-SOFF
CID-SPCS_001
LK-1.0.0.0000
[email protected]
OpenSDP-15.6.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2013,13:49:48(695981)
Let me describe my problem before I get into detail.
It started when I got my M9, I got it from Sprint, and instantly wanted to root it and install Cyanogenmod 13 on it.
To my mistake, I rooted the phone BEFORE I did the OTA update to Android 6.0
As we know, this is a block based system, and this introduces many difficulties.
I had been running TWRP 2.8.7, and stock sense with all my pre-loaded Sprint crap. I was unable to install cyanogenmod 13 or anything.
This led to much frustration, research, and pain as I browsed countless threads on the XDA forums, downloading many items, hoping they would fix my issue.
Now, for my issues.
The HTC RUU for my phone has never worked, and I was constantly met with ERROR 155. I attempted to re-lock the bootloader, but this made no difference.
Often, when I type in adb devices into the command prompt, I am prompted with something like "you are using a different version than the server... Daemon started.. Then devices: and then nothing. This is what I usually get:
{
"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 is obvious to me that if no device is detected, then no work may be done on the phone.
Other times, the phone will recognize, but it seems as if there is no effect on what I am trying to do.
Last night, I paid sunshine $25 to S-off my phone, hoping that it would help me. While the S-off process was extremely easy with this service, my problems are not remedied.
I saw that to restore my phone to 100% stock, that I must complete a RUU with my device, renamed to 0PJAIMG.img, and move it to the SD card.
When I did this, I was still running Stock sence, and was able to move files to my SD card/External SD card.
I went into the bootloader and the phone recognized that I had a "0PJAIMG.img" file on my phone, but I used the wrong file. I used a 75mb file with the firmware, but not all of the sprint things with sense installed. I assumed that since this was the latest firmware, it would allow me to keep Sense and my files, and allow me to take the OTA update to the latest android version
Here are images with information to the INCORRECT "0PJAIMG.img" (that I had renamed from this screenshot) I installed on my phone using the bootloader.
You can see the CORRECT file at about 2GB, and the incorrect file at 75mb.
For reference, Here is what is included in the 75mb file.
Now, I am unable to connect my phone to adb, as it shows up as in the pictures.
I have no recovery installed, so the Stock HTC (and very basic) recovery is there.
I am continuously prompted to install the INCORRECT 0PJAIMG.img that I placed on my phone, and I have no way to remove it as I know.
When I boot normally, I see the HTC One logo, and then a black screen. The screen is still on, but completely black. There is no way to exit this, other than pressing all buttons for 5+ seconds.
I do have the correct 0PJAIMG.img (2gb file), but I have no way of switching these two files, since I cannot connect.
I cannot install TWRP due to no devices showing up in the ADB interface.
When I plug my phone into my computer, I do get the "connected" noise from windows.
Please let me know if I can be more specific. I am going on a trip soon, and will take whatever lengths to get my phone working again.
I have read all relevant threads that I know of, so please avoid re-directing me to another page unless you think I have perhaps missed something.
My end-goal is to have a fully functional HTC M9 with Cyanogenmod 13 snapshot installed. I am on sprint, so I am unsure if I can even use Cyanogenmod. My alternative preference would be the D-Boyz mod to sense.

UPDATE:
I am able to install TWRP 2.8.7.1, and play with that. It seems that when restoring from my old backups, I have the same firmware and OS.
Only now, my radio is bricked.
I have attempted to re-create this, after many painstaking "optimizing apps" runs.
I am currently in a "android is starting"... process.
I will keep this thread updated with information as I progress. I hypothesize that my radio will still be broken.
I am absolutley at my wit's end with this device. I should have never upgraded from the HTC M8. I miss you baby.
I am tempted to take my phone back to sprint. I paid for the S-Off though, and would like to avoid this if possible.
All I want is android 6.0 and CG13.... I'm sick of being annoyed by the "system update is available" notification constantly.
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***

Solved by flashing the ZIP of the RUU for the latest version, placing it on the base of the Phone storage, and naming it "0PJAIMG.zip"

[ROM][Lineage 16.0 Unofficial][Pixel 2 XL/Taimen][06-09-19]

Hi all. Since I haven't gotten any word as to when there will be official support, I wanted to go ahead and share a build of Lineage OS 16.0 for our Pixel 2 XL/Taimen. It's a completely stock build. If it's working for enough people, then I'll continue to provide builds until/unless we get official support. If you find an error, please try to post logs via logcat to aid in fixing it (better yet to submit it to the Lineage OS team directly as well).
{
"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"
}
Steps for First Install:
Flash latest google image
Boot using the latest version of TWRP: https://dl.twrp.me/taimen/twrp-3.2.3-1-taimen.img.html
Wipe cache and data
Flash latest ROM .zip file
Flash the TWRP installer: https://dl.twrp.me/taimen/twrp-pixel2-installer-taimen-3.2.3-1.zip.html
Reboot to recovery
Flash OpenGapps (Android 9.0, ARM 64, probably nano): https://opengapps.org/ or MindTheGapps: https://androidfilehost.com/?fid=3700668719832237178
If desired, flash a custom kernel
If desired, flash Magisk
Reboot and hopefully enjoy
Steps for Updates:
Follow steps 4- 10 above. You can skip steps 1 - 3 (latest Google image, booting with TWRP .img, wiping) and optionally 7 (flashing Gapps).
Latest ROM, 06-09-19:
Download
Old Releases:
Old Download
I usually like to provide updates every ~2 weeks or month to keep up with security updates and/or anything else important. Thanks for trying and God bless .
Special thanks to @draymond1987, @RaymanFX, and all the other developers for their continued hard work.
View changelog up to build date
/.repo/local_manifests/roomservice.xml is attached

A quick note: If you seem to get stuck on the Gapps setup wizard, you can touch each corner of the screen, going clockwise, starting in the top left corner, to skip it. I've seen the data transfer tool have issues lately. You can uninstall it and continue afterwards.

Any known bugs?

pimpdaddy00 said:
Any known bugs?
Click to expand...
Click to collapse
I had an issue at some point where it would shut off when unplugged, but I don't know if it was just something about how my phone is setup. The other thing I encountered was the setup wizard getting stuck before (but fixed after removing the data transfer tool manually later). I'm hoping to see someone else have it working as I know at some point I was able to boot without issue, other than Magisk possibly not working without flashing another custom kernel. Getting any feedback from logs would helpfully tell me what changed and possibly where to fix it at that point.

I checked the channelog and noticed a few minor changes that seemed nice. Overall, I just hope Active Edge gets working in future ROMs lol. Though I know it's difficult. Good job on this!

Can't even get this to boot.

LLStarks said:
Can't even get this to boot.
Click to expand...
Click to collapse
Do you see the lineage OS logo and then blank screen or very shortly after? I've been facing an issue where it looks like com.qualcomm.qti.telephonyservice stops due to not loading a reference properly if I'm not charging. Thanks for letting me know you've had issues.

I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.

LLStarks said:
I could never get past the Lineage logo. Initial boots are usually long, but it would just crap out and reboot to whatever recovery I put in.
Click to expand...
Click to collapse
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722

calsurferpunk said:
Good news all! It looks like the boot issue and modem service failure is fixed. I installed it on my phone and it seems to be stable. Sorry for any/all frustration with the previous build. Hopefully all who have been waiting can use it now:
https://androidfilehost.com/?fid=11410963190603877722
Click to expand...
Click to collapse
Thanks a bunch! Flashing now!

Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
Could try flashing a different gapps package. I always used the mini

tranna said:
Currently using a Pixel 2 XL, can't seem to complete the Android Setup. The app keeps crashing after I connect to WiFi and click continue, does anyone have some advice?
Click to expand...
Click to collapse
I think I went to app info and told it to force stop. If it's on the data transfer utility, I just told it to uninstall (as it seemed to be the culprit for me). I think I either reset/restarted or continued with the pixel setup after that. Either way, just getting to the data transfer utility from within setup or on the apps list and uninstalling it was the trick for me.

Trying this out today for the first time. WiFi calling isn't working, UK EE. Got google apps nano working but had to force quit the setup a few times. Otherwise its looking really nice, thanks!

Hi again all. I just wanted to let all of you who are using this ROM know that I'm planning on updating it very soon. I've been waiting for Google to release security patches for this month, but if I don't see them soon then I'll build with the latest Lineage OS changes anyhow.

On the 2nt or 3rd post is said to tap all for corners of the screen clockwise from top left and it will skip setup, then go into apps and uninstall the data transfer tool. When you do that it will let you move forward with the setup and still let you transfer anyway you want. Hope this helps.

It's amazing! I like it! Thank you so much

Hi again. Here's the latest build of the sources as of today:
https://androidfilehost.com/?fid=11410963190603892886
Something to note is that when I installed it, I simply went to recovery, flashed the new ROM .zip, then flashed the TWRP installation zip again. After that, I rebooted to recovery and installed Magisk again.
For some reason once I booted, the google play store was missing (even though previously having installed OpenGapps along with the previous ROM version). I went back to recovery, reflashed OpenGapps, and it was back again (along with having to go through setup once again, including removing the data transfer tool). Some of the apps (mostly Google's) wouldn't open correctly until I uninstalled and reinstalled them again). My Google account also wasn't present, so I had to add it back as well.
If you come across that same problem, these steps should work, otherwise you might want to just try a fresh install (wiping the old cache and data while in recovery). For anyone who comes up with an easier solution, could you please be sure to share what you did? Everything is still working fine afterwards, but it was just annoying to have to uninstall and add things back. I didn't use the latest OpenGapps, so that might have just been my problem.

I'm unable to complete the setup, since the setup always crashes after adding a google account. It will ask me if I want to select a backup from the cloud or skip, and any option I pick will crash the setup. As a result, Pixel Launcher will not work (maybe that's another issue entirely?) other than that, rom works.

Was wondering if anyone had had any problems with the now playing? I get a pixel ambient services keeps stopping when I ask the assistant but it will tell me the song name. But now playing seams to not work at all. I did try uninstalling the ambient services and reinstall it with no change.

Question Stock F3 Global (No system modifications) stuck in a bootloop

Dear community,
An old XDA member here, who forgot everything about flashing or fixing a broken phone system.
My Poco F3 just went into an infinite bootloop, and I have no idea why is that since I didn't perform any custom modifications to the system, absolutely none!
I can access the recovery menu, which was useless as Safe Mode or any other mode didn't help, the phone can't boot.
Connecting with MIAssistant doesn't work as well, I can see the phone is connected in hidden USB devices on the PC as an Android ADB interface, but the MI software can't see it.
I can also access FASTBOOT, but I have no idea what to do with it. MIAssistant detected it but it asked to connect in normal mode?
A strange artifact is showing on the bootscreen every time, some random colors on the logo, something corrupted? I have no idea...
Is there anything I can do without wiping the phone? It's my daily driver and I need the data saved on it.
I will be monitoring this thread for the next few hours, please don't hesitate to suggest potential fixes or ask questions.
Thanks in advance.
{
"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"
}

Update:
The phone finally made it into Safe Mode, I am backing up my data, can't reboot it yet until the 125GB are on the PC.

Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.

heybaybee said:
Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.
Click to expand...
Click to collapse
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.

sos_sifou said:
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.
Click to expand...
Click to collapse
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3

johnr64 said:
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3
Click to expand...
Click to collapse
You're right, I was a bit angry, all phones can break, including iPhones and Samsungs.
Claiming warranty is a bit tricky for me, as I purchased the phone during my short stay in the UAE, and I won't be going back until next year.
Now I think there is a part of the system files that has been corrupted, because when the phone reboots, it will go into bootloop, but if it boots after some 30 to 40 minutes of bootlooping, it will stay running for a certain period of time.
If system files are corrupted, I don't think a wipe can fix it, as it deletes user data and apps, but I don't think it fixes system files used to boot the device.
Do you have a link to a step-by-step tutorial to unlock the bootloader and flash a stock ROM. I don't really need any special features from custom ROMs, other than the phone to work for the next 3 to 4 months without problems.

Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.

Dear all,
After more testing, it seems the phone doesn't have corrupted boot files, but it just can't run when the CPU is under load.
I have made several tests, when the phone is relaxed, battery saver option is ON, it doesn't reboot, but once battery saver is OFF, and I push the CPU a little using a benchmarking software or a CPU stress test, it reboots.
Thus, the problem is with the hardware, I wonder how many people are suffering from such an issue or is it isolated and only a handful devices are affected by this?

The broken boot logo makes it look like a hardware problem as well. Did you buy it new? Did you game on it or keep it at or above 40-50 degrees C for prolonged periods of time?
I've had Poco X3 Pro that would freeze when using navigation in the summer once in a while. Happened few other times as well.
Trying to flash the (newest) stock ROM may be worth trying. Maybe selling it for parts is an option.

ferreol-fr said:
Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.
Click to expand...
Click to collapse
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!

zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
I struggled a bit in the early days moving away from my LG G7,
you could try my post on the Evo-X thread,
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
following parts 1 to 1b,
you could also try Temporary Recovery using part 6.
None of this will work unless you have a unlocked bootloader and FASTBOOT working on your PC.
You could also try Miflash to install the correct drivers and see if your device is detected in FASTBOOT,
A word of warning never choose "clean all and lock" in miflash unless you are running the correct stock firmware for your device as you could end up with a BRICKED device.

zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
Are your device drivers correctly installed on the computer?
After plugging your phone into fastboot mode on your PC, look in the Windows manager if the device is installed correctly. Otherwise, go to Windows Settings-> Windows Update-> Optional Update. And see if there is any driver update that can help you.