Related
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
rollerdyke44 said:
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
Click to expand...
Click to collapse
I do it right
wipe
Then install rom
There rom works
Some do not work to restart always get stuck
I wonder why
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
If nothing else works flash a factory image ☺
sachin.parmar100 said:
If nothing else works flash a factory image
Click to expand...
Click to collapse
What you seem I do not understand?
haimmalka said:
What you seem I do not understand?
Click to expand...
Click to collapse
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
sachin.parmar100 said:
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I understood but I ask why this is happening
Some of the works
And some do not work restart
I want to know what the problem is
Probably kernel issue.
Aerowinder said:
Probably kernel issue.
Click to expand...
Click to collapse
Explain what this means?
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
Google it
dicecuber said:
Google it
Click to expand...
Click to collapse
Hahaha
I looked it up on Google
I went back to the same state device always do a restart
Until it worked fine now again it came back to do it] =
I was looking google what he means I get here:
http://kernels.franco-lnx.net/Nexus5/5.0/
Then again it returned to constantly restart the device
Now there is a direction to know how it happens?
How to fix it?
I do not remember what I did that worked
Tip know at least that's how it happens:crying:
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
sachin.parmar100 said:
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
Click to expand...
Click to collapse
I think that's a problem for the solution of the fire makes it
I order the same day repair lab
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
_MetalHead_ said:
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
Click to expand...
Click to collapse
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
haimmalka said:
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
Click to expand...
Click to collapse
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
_MetalHead_ said:
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
Click to expand...
Click to collapse
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
haimmalka said:
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
Click to expand...
Click to collapse
But have you restored to 100% stock by flashing a factory image using fastboot?
_MetalHead_ said:
But have you restored to 100% stock by flashing a factory image using fastboot?
Click to expand...
Click to collapse
I do not understand exactly what you record
I can not understand English I use Google Translate
Thank you you try to help
You need to tell me what to do to try ..
I just try it
Guide me step by step what to do
If you ask yes I have fastboot
Files
flash-all
image-hammerhead-ktu84p
bootloader-hammerhead-hhz11k
radio-hammerhead-m8974a-2.0.50.2.22
image-hammerhead-krt16m
cache
boot
bootloader-hammerhead-HHZ11d
userdata
system
recovery
I press
flash-all
Command window opens install it
It does not help
I also make it a manual command that does not help
I try a lot of versions
This is repeated restart problem ]=
Hey guys!
This is urgent!!
Since I've rerooted my android with magisk, I've had a problem. Sometimes when I want to install an application of the internet, it won't install. It will download,yes, but when I want to install it into my phone, it prompts me to open it in another app or share it. When I click that, it says there was an error. But the thing is, it shouldn't even ask me that. Normally I should be able to directly install the app but it won't. This problem doesn't happen always, but it occurs now and then and more frequently lately..someone please help me and tell me why exactly this is happening?? I can't install any apps like this.
thanks
my device is also rooted with magisk,i never had any profile.May be problem is safety net, use safety net fix module and restart the device
bilalrajput said:
my device is also rooted with magisk,i never had any profile.May be problem is safety net, use safety net fix module and restart the device
Click to expand...
Click to collapse
I already installed the universal safety net fix module and I pass safety net...
Nkauneh said:
I already installed the universal safety net fix module and I pass safety net...
Click to expand...
Click to collapse
i think you are using Eu firmware,if thats the case ,try rjmixm firmware instead of rjeuxm to fix this issue
bilalrajput said:
i think you are using Eu firmware,if thats the case ,try rjmixm firmware instead of rjeuxm to fix this issue
Click to expand...
Click to collapse
Ah yes I am indeed using EU firmware. The EEA one.. So I should flash the global stock firmware on my phone??
Nkauneh said:
Ah yes I am indeed using EU firmware. The EEA one.. So I should flash the global stock firmware on my phone??
Click to expand...
Click to collapse
YES,
bilalrajput said:
YES,
Click to expand...
Click to collapse
Alll right thank you!!!
Nkauneh said:
Alll right thank you!!!
Click to expand...
Click to collapse
You are welcome
bilalrajput said:
You are welcome
Click to expand...
Click to collapse
I switched to the GLOBAL Rom now, but I still have the same problem. Instead of the app/file opening, it asks me to share. Or says that there are no apps to share this???
Nkauneh said:
I switched to the GLOBAL Rom now, but I still have the same problem. Instead of the app/file opening, it asks me to share. Or says that there are no apps to share this???
Click to expand...
Click to collapse
U MUST have done something wrong becausse i am still on rjmixm android 11 firmware with root and no issues at all,how are you rooting?
bilalrajput said:
U MUST have done something wrong becausse i am still on rjmixm android 11 firmware with root and no issues at all,how are you rooting?
Click to expand...
Click to collapse
I download the stock Rom of rjmixm and extract the boot.img.
Then I install Magisk manager and click on" select and patch file". I choose the boot.img and click on "let's go". After magisk patches it, it got renamed to something like "boot_patchedVmK" or whatever. I copy it to my computer and flash it via command - - > flash boot boot_patcherVmK...img". After successful flashing of the patched boot.img onto my phone, I restart it. Then my phone is rooted.
Nkauneh said:
I download the stock Rom of rjmixm and extract the boot.img.
Then I install Magisk manager and click on" select and patch file". I choose the boot.img and click on "let's go". After magisk patches it, it got renamed to something like "boot_patchedVmK" or whatever. I copy it to my computer and flash it via command - - > flash boot boot_patcherVmK...img". After successful flashing of the patched boot.img onto my phone, I restart it. Then my phone is rooted.
Click to expand...
Click to collapse
i did the same but all applications are installed easily.No issues at all.I think issue is something else
Nkauneh said:
I switched to the GLOBAL Rom now, but I still have the same problem. Instead of the app/file opening, it asks me to share. Or says that there are no apps to share this???
Click to expand...
Click to collapse
I'd experienced this same "Share" issue.
Go to Settings - Developer Options and check to see if the "Turn on MIUI optimisation" is ENABLED.
I found that fixed the "Share" issue for me.
eFrisky said:
I'd experienced this same "Share" issue.
Go to Settings - Developer Options and check to see if the "Turn on MIUI optimisation" is ENABLED.
I found that fixed the "Share" issue for me.
Click to expand...
Click to collapse
Thank you soo much, this worked. I have been having this issue and it's been so frustrating that I decided to move to unlock my bootloader.
Omg it fixed it. Thank you so much!!
eFrisky said:
I'd experienced this same "Share" issue.
Go to Settings - Developer Options and check to see if the "Turn on MIUI optimisation" is ENABLED.
I found that fixed the "Share" issue for me.
Click to expand...
Click to collapse
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
I replaced the System partition in the AP firmware of the T733 Stock rom with the Lineage 20 GSI built by AndyYan. Someone is willing to test it?
Does it boot?
Typhoon_Master said:
Does it boot?
Click to expand...
Click to collapse
I don't know. R u willing to test it?
I will try
How did it work out?
Send Anywhere
Send whatever you want, wherever you want
sendanywhe.re
File deleted. Ill try it out if you want me to still.
Since i just bricked my ROM this would be a good time for me to try aswell. ;-)
I have tested LineageOS 20 TD by AndyYan (specifically lineage-20.0-20230218-UNOFFICIAL-arm64_bvN) and it worked.
Edit: Changed Light to TD.
dhruv22592 said:
I have tested LineageOS 20 Light by AndyYan (specifically lineage-20.0-20230218-UNOFFICIAL-arm64_bvN) and it worked.
Click to expand...
Click to collapse
Have you tried flashing any version of gapps with it?
dhruv22592 said:
I have tested LineageOS 20 TD by AndyYan (specifically lineage-20.0-20230218-UNOFFICIAL-arm64_bvN) and it worked.
Edit: Changed Light to TD.
Click to expand...
Click to collapse
Did the Pen also work?
Typhoon_Master said:
Did the Pen also work?
Click to expand...
Click to collapse
It works, but a cursor appears and the button on the S-Pen does not work.
Another thing to fix is the brightness slider; by opening the settings app and navigating to 'Phh Treble Settings' -> 'Samsung Features' -> 'Set backlight scale/max backlight level' and setting the value to 255.
(The brightness slider works normally in the AOSP gsi, but for the LineageOS gsi, you need to fix it.)
lewmur said:
Have you tried flashing any version of gapps with it?
Click to expand...
Click to collapse
Hello,
No, I didn't try it since TWRP would complain about it, stating that the 'Size of the image is larger than the target device'
dhruv22592 said:
Hello,
No, I didn't try it since TWRP would complain about it, stating that the 'Size of the image is larger than the target device'
Click to expand...
Click to collapse
I've seen this problem occur on other Samsung tablets and people have found ways to resize the system partition. I asked a few months back if anyone knew how to do it for this device but got no response. Not much use to me without gapps.
Yeah i would also need the button on the pen.
dhruv22592 said:
I have tested LineageOS 20 TD by AndyYan (specifically lineage-20.0-20230218-UNOFFICIAL-arm64_bvN) and it worked.
Edit: Changed Light to TD.
Click to expand...
Click to collapse
what version of TWRP did you use or how did you flash it? I'll try it.
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM, I modified some things like the Adreno Drivers to version 615 worked perfect, the next day I updated via OTA with OrangeFox and everything was still 100% after 2 days I was editing a video and it crashed It got stuck and didn't respond, then when it restarted it didn't start the ROM (it stayed in the POCO logo)... It goes into recovery but it takes at least 30 seconds to go in, I saw that I got 3 new partitions that weren't there (System_EXT, Product, ODM,) does not recognize the storage (the Micro SD does) the VAYU has dynamic partition, but my VAYU says that it has not tried to recover by My flash. it flashed ok but it didn't work. gives an error called (Block device required)
Click to expand...
Click to collapse
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
joke19 said:
Other recovery like twrp, relocked bootloader? Block device required? You use Google? There are many threads about this error
Click to expand...
Click to collapse
I already tried different recoveries, and nothing, I can't find information about the problem, I don't know if it's a hardware problem or if it has to be repaired, I didn't expect that, I had been with the VAYU for 9 months and I've changed everything and nothing had happened to me. my bootloader is unlocked
Flash stock fw with fastboot
cuynu said:
Flash stock fw with fastboot
Click to expand...
Click to collapse
I already tried it, with my flash
linuxinho said:
I already tried it, with my flash
Click to expand...
Click to collapse
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
joke19 said:
You use Google? In the morning I had read something over flash stock recovery and sideload... XDA and the net have many threads
Click to expand...
Click to collapse
I don't use google, I use the rom clean without gapps, I never use google services
Search for your error with Google
linuxinho said:
I don't use google, I use the rom clean without gapps, I never use google services
Click to expand...
Click to collapse
joke19 said:
Search for your error with Google
Click to expand...
Click to collapse
there is no information about the error, on the internet
linuxinho said:
there is no information about the error, on the internet
Click to expand...
Click to collapse
Okay
joke19 said:
Okay
Click to expand...
Click to collapse
I think I'll have to take it to a specialized technician
Use original fastboot rom from xiaomi. That's fixed my issues.
eliasnico said:
Use original fastboot rom from xiaomi. That's fixed my issues.
Click to expand...
Click to collapse
did you have the same error as mine?
A similar issue happened to me on stock ROM as well. I'm wondering if the boot partition is just dead and requires service?
linuxinho said:
my POCO X3 PRO was in the ArrowOS A13 ROM
Click to expand...
Click to collapse
Ok, although I don't understand why would you even use 13... but ok...
linuxinho said:
modified some things like the Adreno Drivers to version 615 worked perfect,
Click to expand...
Click to collapse
First mistake. You THOUGHT it worked perfect. Can you confirm that with dmesg and logcat? Absolutely no errors or crashes related to the gpu? Come on, man!
linuxinho said:
after 2 days I was editing a video and it crashed It got stuck and didn't respond,
Click to expand...
Click to collapse
How come, since it works perfectly?! I often encode, recode, cut and edit video on my unmodded ArrowOS 11 Poco X3 Pro, and have no issues. Unbelievable!
99 percent of Poco bricks on this forum are caused by inept people tinkering with parts of firmware they should not tinker with. Well, besides indian Poco versions, those were abysmal.
I had this issue also, i fixed it by flashing xiaomi.eu fastboot rom, used batch file (present in rom zip) for clean install.
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/xiaomi.eu_multi_POCOX3Pro_V13.0.4.0.SJUMIXM_v13-12-fastboot.zip/download
<Moderator Edit>: Deleted quote since I deleted the quoted post.
One can express such things in a different, non hurting way, remaining objective and not senseless aggressive. Finaly we all have made +/- stupid things in the past und hoped to get help from experts
<Moderator Note>: Thread cleaned.
Everyone, please always follow XDA Developers Forum Rules , especially in this instance, Rule 2.3:
2.3 Flaming / Lack of respect: XDA is about sharing, and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Whenever anyone breaks any of our rules, please use the Report button in the lower right corner of their post and let us know so that we may address it, and at the same time please don't respond to the posts that break our rules - only report them. Thank you!