Related
Well, received EMUI 11 after all. However, since the update I'm unable to connect my phone to my computer (fastboot, mpt, HiSuite, etc). The phone thinks it's receiving charge from a normal charger (I don't even get the different USB options when plugged to the computer). Windows always says "USB Device Not Recognized" no matter how many computers I've tried it on, how many cables I've used, how many drivers I've tried. Device manager shows it as "Unknown USB device (device descriptor request failed)". Trust me I've got the correct drivers and I know well how to troubleshoot that.
Is this happening to anybody after the update?
There's a new bootloader unlock method (https://ministryofsolutions.com/202...r-unlock-service-evr-al00-tl00-supported.html) so I need to downgrade to EMUI 9 to achieve this, so that I can use OpenKirin custom roms. Any other ways to downgrade without a PC?
Thanks!
It is possible.
It didn't work for me but now it does work.
PhoneTechShop said:
It is possible.
It didn't work for me but now it does work.
Click to expand...
Click to collapse
how did u make it work? i havent tried connecting to the PC yet, so no idea.
jbmc83 said:
how did u make it work? i haven't tried connecting to the PC yet, so no idea.
Click to expand...
Click to collapse
Connect, then select transfer files ten install hisuite you can restart windows then connect again , select transfer files, play with HDB in settings .. turn it on and usb debugging as well turn on or off.. and make sure hisuite will install app in phone too .. then it will ask for code..
PhoneTechShop said:
Connect, then select transfer files ten install hisuite you can restart windows then connect again , select transfer files, play with HDB in settings .. turn it on and usb debugging as well turn on or off.. and make sure hisuite will install app in phone too .. then it will ask for code..
Click to expand...
Click to collapse
Thanks. Right, this is when the computer detects the phone. In my case it does not, for anything in the world. Tried several computers, cables, a million drivers, all the usual windows/drivers/android settings that you need to check. I think the update has broken this feature. Can't even roll back to EMUI 10, because you need the phone to be detected by the computer. So, I'm stuck.
93starletgt said:
Thanks. Right, this is when the computer detects the phone. In my case it does not, for anything in the world. Tried several computers, cables, a million drivers, all the usual windows/drivers/android settings that you need to check. I think the update has broken this feature. Can't even roll back to EMUI 10, because you need the phone to be detected by the computer. So, I'm stuck.
Click to expand...
Click to collapse
Contact huawei. See what they say about it.
Although the link here is for the mate 10 pro its a possible fix. Youve probably read it. But in case you havent try it out.
https://thedroidguy.com/what-to-do-...ized-by-your-pc-troubleshooting-guide-1088941
Btw do you have the L29 version? Did you receive the beta emui 11?
.
93starletgt said:
Well, received EMUI 11 after all. However, since the update I'm unable to connect my phone to my computer (fastboot, mpt, HiSuite, etc). The phone thinks it's receiving charge from a normal charger (I don't even get the different USB options when plugged to the computer). Windows always says "USB Device Not Recognized" no matter how many computers I've tried it on, how many cables I've used, how many drivers I've tried. Device manager shows it as "Unknown USB device (device descriptor request failed)". Trust me I've got the correct drivers and I know well how to troubleshoot that.
Is this happening to anybody after the update?
There's a new bootloader unlock method (https://ministryofsolutions.com/202...r-unlock-service-evr-al00-tl00-supported.html) so I need to downgrade to EMUI 9 to achieve this, so that I can use OpenKirin custom roms. Any other ways to downgrade without a PC?
Thanks!
Click to expand...
Click to collapse
Don't know if I can can solve your issue but I can say that I've been on EMUI 11 and managed to go back to 10 and 9, so I don't think it's necessarily anything to do with EMUI 11. Didn't do anything special, just connected as normal.
I have Al00 Chinese version.
jbaggs said:
Don't know if I can can solve your issue but I can say that I've been on EMUI 11 and managed to go back to 10 and 9, so I don't think it's necessarily anything to do with EMUI 11. Didn't do anything special, just connected as normal.
I have Al00 Chinese version.
Click to expand...
Click to collapse
Thank you. Mine's a EVR-L29. I'm out of ideas.
Deanro said:
Btw do you have the L29 version? Did you receive the beta emui 11?
Click to expand...
Click to collapse
93starletgt said:
Thank you. Mine's a EVR-L29. I'm out of ideas.
Click to expand...
Click to collapse
Good. But you missed my other question. Did you install the beta?
93starletgt said:
Thank you. Mine's a EVR-L29. I'm out of ideas.
Click to expand...
Click to collapse
Do u have Hi suite pp installed on your phone ??
PhoneTechShop said:
Do u have Hi suite pp installed on your phone ??
Click to expand...
Click to collapse
I do. In both phone and computer.
Deanro said:
Good. But you missed my other question. Did you install the beta?
Click to expand...
Click to collapse
I had the Emui 11 Beta, then received update: 11.0.0.140(C432E3R1P3)
93starletgt said:
I had the Emui 11 Beta, then received update: 11.0.0.140(C432E3R1P3)
Click to expand...
Click to collapse
Excellent! Hope you like the update
93starletgt said:
I do. In both phone and computer.
Click to expand...
Click to collapse
Did you find the solution my friend I have the same problem
Same problem here. Whatever Emui 11 does, it changes sth in the device, that can´t be unchanged, even when you downgrade the device.
I have two P30s (ELE-L29) here and tried both of them. Device One got the Emui 11 and Emui 12 upgrade, Device Two was always in Emui 9. Device Two with Emui 9 has no problem with "cheap" usb cables, HDB or connecting to computer.
Device One however, that received the Emui 11 or above upgrades (anything including 11.0.0.159(C431E11R2P3) and above), can´t connect to the phone with "cheap" usb cables, when the OS is Emui 10 or Emui 9. BUT! It still connects, if you use high quality good cables. The cheap cables only get recognized again. when the phone has Emui 11 or 12 again. It is definitely NOT a hardware Problem. Also I tested with various cheap and high quality usb cables. Huawei changed something with the 11.0.0.159(C431E11R2P3) update; so DO NOT UPDATE your phones to that version or above. It´s not worth it, the EMUI 11 and 12 versions really suck.
I read an article about being able to run Windows 11 over KVM by enabling KVM on Android 13.
I have tried running the aarch64 version of Qemu via Termux, but I still have not been able to boot Windows 10/11.
If anyone has tried and successfully booted, please let me know how to do that!
*I am not able to enable networking, but I am able to boot Ubuntu.
You might perhaps want to take this conversation to this other thread, just to keep all Windows 11 on Pixel 6 Pro posts in one place: https://forum.xda-developers.com/t/...-run-full-fledged-windows-11-as-a-vm.4402533/
roirraW edor ehT said:
You might perhaps want to take this conversation to this other thread, just to keep all Windows 11 on Pixel 6 Pro posts in one place: https://forum.xda-developers.com/t/...-run-full-fledged-windows-11-as-a-vm.4402533/
Click to expand...
Click to collapse
Thank you very much. I had not found the conversation that already exists. I will check there.
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13
Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...
I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.
fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times
Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.
So there's this tutorial for installing windows 11 on Xiaomi Pad 5
Simple and easy way unlike past methods. And it's available for all users
How to Install Windows 11 on Xiaomi Pad 5 - Gizmochina
It’s been more than a year since the Xiaomi Pad 5 is here with all its high-end specifications consisting of Snapdragon 860 and Snapdragon 870 on respective models. Surprisingly, the Android tablet from Xiaomi can now run Windows 11 without any major bugs or flaws. As spotted on Geekbench...
www.gizmochina.com
It works using one click installer (chinese tool)
The problem is that it lack a lot of details and support is only on chinese.
Did anyone tried it?
I searched on the internet no other websites or YouTube videos
Yesterday I was about to install it and try it but the prompt box said there's a high risk of getting a bricked device and using Mi Flash Tool in fastboot won't help after updating the partitions so basically it's beyond my expertise.
I already has the ArrowOS custom ROM not MIUI.
And how can someone fix a bricked device after updating partitions.
I installed windows 11 on my xiaomi mi 8 that have a snapdragon cpu, the same as mi pad 5 and the process should be the same. When i modified partitions for installing windows 11, i was not able to reinstall android because “userdata” partition got deleted. With “parted” tool (or the same tool used for modify partitions), i deleted all windows paritions and re-created the default “userdata” one, so i was able again to install android and use mi flash tool. (Always take a screenshot or a backup of the default partition lable, in case you have to restore it)
Found a video that should be useful:
Thank you so much
The video is great but the tool is much easier (one-click installation tool)
I have no expertise in modifying partitions, so ur experience in ur mi 8 would be very valuable.
I might need to ask u some questions when things get messed up if choose to proceed with it.
Yes
Yousef Kassir said:
Thank you so much
The video is great but the tool is much easier (one-click installation tool)
I have no expertise in modifying partitions, so ur experience in ur mi 8 would be very valuable.
I might need to ask u some questions when things get messed up if choose to proceed with it.
Click to expand...
Click to collapse
yes, i can help you in this process, but it’s a bit different than xiaomi mi 8, because i did it 1 year ago, so, maybe I should be able to help only in cases of problems. If you can, post here a screenshot of the default partition lable.
EDIT: if you want to dualboot, the process is a bit different, because you will have to shrink the userdata partition, not remove it completely. This way you should be able to use flash tool even with windows installed, but I'm not sure, because I'm not familiar with this guide. But remember that with the dualboot you will have less space in both operating systems.
I'd recommend using commands instead of the automatic tool, but if you're not familiar with cmd, then you're free to do whatever you want. However, I leave the official guide (for dualboot) https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/blob/main/guide/English/1-partition-en.md
Yousef Kassir said:
So there's this tutorial for installing windows 11 on Xiaomi Pad 5
Simple and easy way unlike past methods. And it's available for all users
How to Install Windows 11 on Xiaomi Pad 5 - Gizmochina
It’s been more than a year since the Xiaomi Pad 5 is here with all its high-end specifications consisting of Snapdragon 860 and Snapdragon 870 on respective models. Surprisingly, the Android tablet from Xiaomi can now run Windows 11 without any major bugs or flaws. As spotted on Geekbench...
www.gizmochina.com
It works using one click installer (chinese tool)
The problem is that it lack a lot of details and support is only on chinese.
Did anyone tried it?
I searched on the internet no other websites or YouTube videos
Yesterday I was about to install it and try it but the prompt box said there's a high risk of getting a bricked device and using Mi Flash Tool in fastboot won't help after updating the partitions so basically it's beyond my expertise.
I already has the ArrowOS custom ROM not MIUI.
And how can someone fix a bricked device after updating partitions.
Click to expand...
Click to collapse
If you brick your device is very difficult to unbrick it. I have an POCO F3 which is bricked and it has passed over 4 months and i can't do anything to unbrick or restore the partitions. If you are new study a week or two about android partiotions in internet be experienced and after that try to port windows 11.
But if you liked tweaking and you want the maximum perfomance of your tablet take a look at my guide.
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Blitzz.666 said:
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Click to expand...
Click to collapse
Try to install It manually, It should work, try to do the steps in the video
Maxsenza151 said:
I'd recommend using commands instead of the automatic tool, but if you're not familiar with cmd, then you're free to do whatever you want. However, I leave the official guide (for dualboot) https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/blob/main/guide/English/1-partition-en.md
Click to expand...
Click to collapse
Much appreciated bro
Blitzz.666 said:
The same tool (Engage Machine Toolbox V2.1.2) Has a button to revert the partitions and make userdata last partition and delete the windows ones. Once that's done you simply reboot and will boot to android(in case it crashed in the middle of the process). If it still doesn't boot, flash with mi flash because it will work now, or use fastboot rom. Anything but clear all and lock. Do not use that option(I don't know why it's applied by default at mi flash startup+load images folder).
I just bricked my mi pad 5 last night, struggled for several hours until I managed to revert it to Android. Still haven't been able to install Windows 11 on it. I reach the point in the gizmochina tutorial where it makes the partitions, it never asks for the wim file, throws error : no uefi or windows partitions found. Haven't tried to install manually, like create partitions and flash partitions using cmd.
Click to expand...
Click to collapse
You're so correct about the clear all and lock thing, it once happened to me during installing fastboot rom cuz its the default option. The solution is just use the mi unlock tool again and it will do the job. Regarding installing windows, will u try the tool again or try manually? In both cases, if it works , please let me know id really appreciate it
I will try the manual way because i spent like 5 hours trying this tool.
5, because there is no backout plan in case something happens.
I always hate this about all tutorials out there : they assume it works 100%. If it fails, no help from anyone.
The tool throws errors like : data is not formatted(because you need to format data via recovery and then boot straight into fastboot...anything else fails), partition table failure(because the userdata is not the last partition(this happens when the partitions are made for windows install), and last error that I got was "windows or uefi partition not found"...i still haven't cracked this one.
I think I have time today to try manually. Will let you know.
Yup that's unfortunate it says if you have questions ask in the comments and there's no comment section at all. It's barely a guide.
For example: they should've mentioned that thing about formatting and booting directly to fast boot. While in the tutorial it says format then reboot then go to fastboot which is useless cuz when you first boot after formatting data you've already lost ur formatted state. Anyways I wish you good luck with manual tutorial.. the dual boot one that Maxsenza151 shared seems a good option. Waiting to hear from u
Yousef Kassir said:
Yup that's unfortunate it says if you have questions ask in the comments and there's no comment section at all. It's barely a guide.
For example: they should've mentioned that thing about formatting and booting directly to fast boot. While in the tutorial it says format then reboot then go to fastboot which is useless cuz when you first boot after formatting data you've already lost ur formatted state. Anyways I wish you good luck with manual tutorial.. the dual boot one that Maxsenza151 shared seems a good option. Waiting to hear from u
Click to expand...
Click to collapse
There is no comment section because the text is copy-paste from somewhere else.
So I did the dual boot and it works like in this tutorial :
Git : https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/
The issue is that camera and speakers do not work and the charge is amazingly slow.
I'm hoping on some driver updates in the future but for now I'm using it on Android...
Blitzz.666 said:
There is no comment section because the text is copy-paste from somewhere else.
So I did the dual boot and it works like in this tutorial :
Git : https://github.com/erdilS/Port-Windows-11-Xiaomi-Pad-5/
The issue is that camera and speakers do not work and the charge is amazingly slow.
I'm hoping on some driver updates in the future but for now I'm using it on Android...
Click to expand...
Click to collapse
Ouch, speakers and camera are important.
I'm glad it booted up, tho. Although it had issues I think you learned new stuff during this tutorial. Thanks for keeping me updated. I hope im the future there will be more driver updates and an easier method.
Yousef Kassir said:
You're so correct about the clear all and lock thing, it once happened to me during installing fastboot rom cuz its the default option. The solution is just use the mi unlock tool again and it will do the job. Regarding installing windows, will u try the tool again or try manually? In both cases, if it works , please let me know id really appreciate it
Click to expand...
Click to collapse
Just do the manual One. The Renegade Project team highly recommend to follow the GitHub guide that i sent to you. If you use your brain, you can do It, its quite simple too. Join Project Renegade telegram group and ask them.
P.S: on the renegade project website they say that you need to follow github guide because there are some importand device-specific steps!
In the photos, you can see what they say.
(There is a uninstall guide too on github)
Yousef Kassir said:
Ouch, speakers and camera are important.
I'm glad it booted up, tho. Although it had issues I think you learned new stuff during this tutorial. Thanks for keeping me updated. I hope im the future there will be more driver updates and an easier method.
Click to expand...
Click to collapse
These features Will be implemented with new driver updates. Its still in work.
Watch here the development status. https://renegade-project.tech/en/state
does/will the pogo keyboard work?
Thanks bro
Maxsenza151 said:
Just do the manual One. The Renegade Project team highly recommend to follow the GitHub guide that i sent to you. If you use your brain, you can do It, its quite simple too. Join Project Renegade telegram group and ask them.
P.S: on the renegade project website they say that you need to follow github guide because there are some importand device-specific steps!
In the photos, you can see what they say.
(There is a uninstall guide too on github)
Click to expand...
Click to collapse
I joined the telegram group, until everything works I'll install it. Now I'm good with arrowos 13, yesterday i tried to install miui 14 dev chinese rom and i bricked my pad 5 and even mi flash tool couldn't make it through. I then managed with a little help of mindows tool and then reflashed arrowos .
Yousef Kassir said:
I joined the telegram group, until everything works I'll install it. Now I'm good with arrowos 13, yesterday i tried to install miui 14 dev chinese rom and i bricked my pad 5 and even mi flash tool couldn't make it through. I then managed with a little help of mindows tool and then reflashed arrowos .
Click to expand...
Click to collapse
How did official rom brick your device lol?
Anyway i found the nabu specific telegram group https://t.me/nabuwoa
I heard that mindows can brick your pad..
Hi all!
Got me a N975f (d2s), Note 10+ that is. Used, but in really good condition. 512GB. Not cheap, but reasonably priced. It seems unlocked also, but i have to admit that i couldn't really say even if it was not. But the CSC is NEE, nordic carriers, and that usually means unlocked.
The phone has not been used for a while and was stuck at Android 10 or so. From what i know it was untouched flashing-wise. So i started with updating firmware and got it up to the latest A12 version, NEE. I thought i would then start with flashing TWRP first. Tried the method via Odin. TWRP version 3.7.0_9-0 from the TWRP site that the dev linked to. Odin version 3.14.4. Bootloader unlocked according to the first part of the instructions. I put the twrp-tar and the vbmeta-tar in their places (AP and CP in Odin respectively). The computer has been used for similar operations with Odin, altho perhaps not in a while. Odin recognizes the device and the proper 'added' message shows.
What happens when I press 'Start' is... pretty much nothing.. Odin shows message 'analyzing file' without anything else happening regardless of how long i wait. Eventually i have to press volume down and power button to restart. I tried different cables, USB-ports, Odin versions and even different computers, both previously used for flashing. I remember also fiddling with Heimdal but i am not so familiar with it so i was afraid i would break something.
I am not a developer but i have flashed quite a few devices through the years, and I don't remember getting this kind of result ever. I contacted the developer of the TWRP and he scratched his head too.
Recently i bumped into this thread, diferent device, but basically saying that updates after certain date around late januari could render that device (T290) practically unflashable.
[ROM][OFFICIAL][13] LineageOS 20.0 for the SM-T290 (gtowifi)
WARNING: Samsung rolled out a new firmware update starting roughly at the end of January 2023. This contains bootloader version 4. From what we understand with SM-T295 bootloaders, this may or may not permanently lock you out from ever flashing...
forum.xda-developers.com
I did my updating of the Note 10+ around that time also, perhaps even february.
So now i am wondering if anything of that kind might have happened with this phone also. I am considering buying another, but they're not so cheap and I don't want to risk ending up in the same situation with another one.
Has anyone heard or experienced something similar with this phone? Is there anything else that could be done?
I would be very grateful for any answer that would point me in the right direction.
Regards
@prkfsz Your post does not qualify as Development. Please read the stickies before posting.
Questions belong in the Questions and Answers section. As a courtesy I have moved your post. Please ensure your posts remain pertinent to the sections and threads you post in.
Appologies. Thank you for moving it to the right place.
I would leave it on Android 10, good as it gets.
I prefer Pie but 10 is better than 11 or 12.
I have 2 N10+'s, one running on 9, the other 10. Neither will be upgraded! They run very well as is and security is no issue at all unless you do stupid things.
blackhawk said:
I would leave it on Android 10, good as it gets.
I prefer Pie but 10 is better than 11 or 12.
I have 2 N10+'s, one running on 9, the other 10. Neither will be upgraded! They run very well as is and security is no issue at all unless you do stupid things.
Click to expand...
Click to collapse
I am sorry but I fail at seeing exactly how your post is helping me...
Update:
Still nothing. I did manage to, using Odin, flash a bit older firmware. Same Android version (A12) but from previous year, in hope that it would change something. It didn't, the phone is still not cooperative when it comes to flashing any custom binary. I flashed back to the latest firmware, nada.
In the process of trial and error I did notice that the phone refuses to switch over controll over USB-port in the USB pulldown menu, while connected to computer. Found a thread on the forum with seemingly one person in the whole world that had the same problem. Nothing there helped.
So, long story short, the phone is flashable with stock rom, but using the same gear gets nothing. Bought a new 20€ USB-cable anyway, no difference.
I consider myself not being stubborn. So i bought another Note 10+, but cheaper and with broken screen, just to see what happens. The phone is almost identical firmware-wise, and when i got it it had been updated to the second most recent firmware, and it's from this year. Same friggin' result!
WHAT THE FRICK IS GOING ON??!!
SOLUTION:
Finally... Posting this in case other people run into the same problem.
I had tried several newest versions of TWRP with the same result. But everything else seemed to work. Even if I flashed only vbmeta, it went. So I figured that it must be something with the TWRP itself that the phone is not excepting. Kept trying and eventually found that the TWRP version 3.6.2_9-1 works. Didn't try more.