Related
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
m01y1i00 said:
Hi Sorry to say, I have " Exactly" the same problem and have also reached the same place, I asked on these forums without success. in the end I sent it back to HTC and they want £200 to repair it or £29.00 diagnostic fee. I have asked them to send it back and will have to pay the £29.00. If it is within warrantee send it back.
Click to expand...
Click to collapse
Thanks for your fast reply.
I will get in contact with them and see what they will say. My phone is under warranty so i will pay only for shipping charges.
I bought it from a german eshop and i am from Cyprus.
The problem is, the official distributor for HTC here in Cyprus is Greece and i had a bad experience with them. I sent an old HTC One X 4 years before which had a board issue, and after waiting for a month they sent it back and guess what. It had the same problem. So i got in contact with the US website, described the problem and mentioned also the "official distributors" in Cyprus and Greece and how their "service" was and they told me i will have a brand new phone here in Cyprus within a week (which became a reality).
So before i experience the same issues i will clear everything from here (if anybody know a successful solution) and then communicate with HTC how to resolve this.
Thanks again for your reply!
Is this a general/common problem on htc? I am worried
Spike97 said:
Is this a general/common problem on htc? I am worried
Click to expand...
Click to collapse
I'd be lying if I'd say that I haven't read about the issue several times, already. However, you need to be aware of the fact that most of the time only people with problems are creating threads whereas people who have no issues at all won't do the same for praising the phone.
In other words: Yes, this problem does exist but no, not everyone faces it. I know many users whose M9 is still working fine.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
Click to expand...
Click to collapse
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
i have the same problem. Where can i get a rom.zip
Bootloop
gmayer1212 said:
i have the same problem. Where can i get a rom.zip
Click to expand...
Click to collapse
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
kwaichang said:
Take the new OTA Nougat, separate those three files on your sd card
Install it with fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
and it will be working takes 5-10 minutes to restart
Click to expand...
Click to collapse
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a locked bootloader and a firmware/system-mismatch won't be able to install any OTAs unless that person flashes a RUU for fixing the mismatch*. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
* Users with an unlocked bootloader need to fix the mismatch, as well, but at least they have twrp backups as an alternative solution for the problem.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Flippy498 said:
Please don't give such advice. If the firmware isn't matching the system version users will face bugs and lags or the phone won't even boot. (The latter happens for example if you try to use an Android M system with an Android L firmware.) Besides a user with a firmware/system-mismatch won't be able to install any OTAs unless that persons flashes a RUU for fixing the mismatch. The catch is there is no publicly available Android N RUU for every variant of the M9, at the moment. And with S-ON you aren't able to use older RUUs. That means people might have to contact Llabtoofer's RUU Service (which isn't for free!) if they followed your recommendation.
@gmayer1212 & @htcm9guy: You may want to read the ReadMe thread. It's pinned above the normal threads here in this section.
Click to expand...
Click to collapse
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
kwaichang said:
Sorry for that. Mine was also hanging in bootloop but unlocked S-on T-mobile Germany
Click to expand...
Click to collapse
Don't get me wrong, I don't want to discourage you from helping others. It's just important that you know which variant of the M9 the user with the problems owns in such cases. Just recommending to flash random stock files only causes more problems than it solves.
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Hello,
i have the same problem but in some ways different. My M9 was running nearly fine until yester der evening. I just plugged the power supply and suddenly black screen, bootloop. But the really big problem is i don't come in any different stable mode than bootloader. If i try to get into download or recovery mode, the silver htc-logo appears for less than a secound, short vibration and reboot - and this is in loop also.
So for me i don't se a way to factory reset or reinstall any RUU or anything else?
Is it destroyed? :crying:
I was complete S-Off before, running on the last firmware with ViperOneM9 6.1.0.
Thans for your support,
Bond
That sounds like the dead nand issue. It's a hardware failure (c.f. the FAQ of the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
If your phone is under warranty, it has a stock rom, and bootloader is still locked, then send it to HTC after contacting them via chat.
They will replace either the board or the device.
This is whhat they did for me.
DE2IS said:
HTC One M9, no branding, official software, locked and S-ON.
one month ago my phone got (for no apparent reason) serious software problems, so spend a lot of time on the internet to find a solution. in the end, i downloaded the correct stock rom, put it on a sd card and reinstalled stock android via the download mode. it worked out really well, my phone was running like new.
but 2 days ago i pick up my phone and realize it's stuck in a bootloop. (again for no apparent reason) using the right button combinations, i am able to get into the bootloader.
when i try to flash the stock rom with the exact same method that worked last time, it says "start ui_updating" and gets caught in the bootloop again. (i dont think i did anything wrong because the exact same procedure worked last time)
when i enter recovery mode, i get the infamous red triangle. using the right buttons, i can still access the recovery mode from there. now, when i try to factory reset from here, i get the following errors: E: failed to mount /preload (invalid argument).. try emmc mount E: Cant find device node for mount point again E: mount /cache fail, format it and mount again ----- about 5 more similar errors after those 3.
I tried to flash recovery img with fastboot but i get an error similar to:
9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE
I guess this is because my phone doesn't have usb debugging enabled or it doesn't have an unlocked bootloader.
I also tried to unlock the bootloader but after running the command: fastboot oem get_identifier_token i don't get the token so i can post it to htcdev and unlock my bootloader.
Anybody help or had the same issue and fixed it?
Thanks in advance
Click to expand...
Click to collapse
is your phone recongized - what shows "fastboot devices"
pear-i said:
Just to chime in --- same problem happened to me yesterday.
Phone has been working fine --- then yesterday phone went unstable so I reset and got caught in bootloop.
After doing a factory reset and many tries -- got it to boot to android, only to get bombarded by google play service errors -- most likely wrong version of google play services for android?? I manually installed google play services apk... Reset and after many tries was able to boot again -- system was smooth. But did a quick reset to check whether problem was fixed and now i'm back in boot loop.
I wonder if there's a problem with a recent google apps update over playstore that's killing boot?
Click to expand...
Click to collapse
I too wonder the same - recently had the bootloop issue with my M9, just when it was updating apps from the Playstore... quite suspicious...
My HTC M9 is also in boot loop
htcm9guy said:
I also have a bootloop issue with Locked and S-ON... Care to let me know how you managed to get it working the 1st time?
Where to find the corrent stock ROM and the method you did to get it working..
Click to expand...
Click to collapse
It happened at last Saturday, when I've just tried to perform a regular reset to my HTC M9 (from the regular device's menu).
I can't enter to download mode (fail), wipe cache and wipe all (factory reset) didn't help.
Is there any chance to fix it at home? Or just to buy a new phone?
And, does this issue can occur in other devices, HTC or any other brand?
Please advise.
(Can't upload a picture of my device, since I'm a new user...)
Thanks!
As far as I know there's nothing you can do. There are no reports of successful diy repairs of a dead nand M9.
Theoretically this issue can happen with any phone. However, it looks like the probability of its occurence on a M9 increased a lot during the last months.
I´m also stuck in bootloader mode
recovery mode / download mode endup with red text:
"failed to boot to download mode"
***Software status: Modified***
***LOCKED***
***S-ON***
***Security Warning***
Cannot get the token as fastboot oem commands end up empty or unknown command.
I think USB-debbugging is "off"
How can i get S-OFF
or how can i get token
Thanks.
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
So, here's what happened. I had my Redmi note 8 unlock it's bootloader a year back and installed a custom rom corvus os. And since I the custom rom didn't came with the MI stock camera app and with lots of bugs and issues, I decided to re-flash it's stock rom instead(the latest MIUI). So, yesterday I tried to flash the stock rom using the Mi Flash Tool, while putting my Note 8 at fastboot mode. But then when I clicked on the "flash" button, It came with an error saying
[18:14:01]:1 973598ec 5.1235443s error:Writing 'imagefv' FAILED (remote: 'Check CRC failed')
This is the message on the log file.
After that I tried to restart my phone and fix this issue but what happened after that is that my phone just totally went dead. Like, there's not even the light indicator when I try to chrage my phone, can't boot into recovery, can't turn on, can't enter fastboot or EDL mode. (I've also heard that Xiaomi also locked EDL on their devices smh).
I've been desperate ever since to fix my phone. And I've been searching, reading and analyzing solutions but only came to conclusions that I should give it to Xiaomi servicing center. But the problem is that there is currently a lockdown around our area (of where I'm from) and idk when it's be lifted.
If anyone knows any way, solution or any advice or fixes, please help me.
You can still flash EDL via patched firehose binary.
I have a bricked Redmi Note 5 Pro. Stock firmware, locked bootloader, did literally nothing that would cause this. Just updated firmware (it happened few years ago, just now decided to try and repair it), and after update It's stuck in Mi-Recovery 3.0, with options only for "Reboot", "Wipe Data" and "Connect with MIAssistant", with red text at the bottom "This MIUI version can't be installed on this device" (see photo). Tried everything form this menu, nothing solves the problem. I can boot into fastboot but can't use it as the bootloader is locked and debugging is off. I can go into EDL mode but can't flash as I need to log in into Mi Account, and my sister (this phone was hers) forgot the password and even the account which was connected to this device. I was looking for MiFlash that bypasses authorization but can't find any that is not marked as malware (anyone knows of any that is safe?). At was past the warranty and I've tried to ask few phone-repair shops but the said that is unrepairable.
Any ideas what I can check or try next to solve this problem?
BTW. Does anyone knows why all of this happened? As I already said, never did anything with OS, only updated it which caused brick. My only idea is, as this phone was bought not from official store, that it might be a phone that was bought cheaper in china, then flashed with modified global OS and after update it was replaced with official global OS which bricked the phone. No idea if something like this is possible.
Edit [Sep 19, 2021]: I got somewhere. Used Firehose file to flash whyred global image without authenitcation. Got into system. I can at least go into fastboot and it's detected correctly in windows. Now I'm trying to get root, flash TWRP and any non-stock OS. Couldn't flash directly via fastboot because of anti-rollback check. Tried to do "fastboot boot twrp_rn5pro.img" which resulted in FAIL in console (status read failed - too many links) and "The system has been destroyed - click the power button to shutdown".
Edit2 [Sep 19, 2021]: Looks like my bootloader is still locked and that's why I can't flash custom recovery. But when I look in the phone settings it says that my phone is already unlocked. Checking in fastboot via PC says otherwise. Enabled OEM unlocking, but fastboot still says "FAILED (remote: Token Verify Failed, Reboot the device". Can't unlock it using MiUnlock cause they say that I need to set my account as available to unlock in unlock status on my device, but I can't do it as my device says that it's already unlocked.
Edit3 [Sep 20, 2021]: I've tried other tool: XiaoMiTool V2 (by Francesco Tescari). As the option "My device works normally I want to mod it" didn't work I chose "My device is bricked I want to unbrick it". Selected option without unlocking bootloader (wouldn't work). And it actually auto-detected that it's chinese phone and flashed chinese OS (MIUI 10.3 Stable). At the boot I got a prompt that this device is locked and I need to log into my Mi account (the one I logged in in the last ROM - from first Edit), after logging in it let me go through setup (luckily there was English). But phone still says that it's unlocked while it's still locked in fastboot. So in the end it didn't got me anywhere, but at least I know that orginally it was a chinese phone.
Edit4 [Sep 20, 2021]: Finally solved the problem! Used this tutorial. Did everything like shown on video and at the end I have MIUI 12 with unlocked bootloader (this time it's actually unlocked - checked with fastboot). Managed to flash TWRP using dummy.img and flashing to recovery. Couldn't boot from img, but vol+ + power did the job. With working recovery I can do everything else I wanted to do.
I had the same issue, which I also managed to fix. I thought I'd share what I did here.
My phone was bricked with access to MIUI recovery and Fastboot. My phone was locked, however my phone was not linked to my Mi account, and so I couldn't unlock it using the Mi Unlock tool. The only way to get into EDL mode was via the testpoint method. It's not as scary as people may think.
Many of the YouTube videos on testpoint show that you have to touch the two terminals while pushing the cable into the phone. Several times I was able to activate EDL mode without doing both at the same time - i.e. I could just connect the cable and touch the two terminals (I used a paper clip) and the phone would enter EDL mode. I think it might have had something to do with me pressing the power button. In my case, I had to have the battery disconnected from the circuit to get into EDL mode.
I used the Xiaomi Flash tool. Always remember to select not to relock the bootloader. I think it's stupid that relocking is the default option and that the radio buttons are at the bottom of the program and sometimes not visible on a laptop. That's how I got into this mess in the first place!
One of the things that I think causes the "MIUI version" problem is attempting to install the incorrect stock ROM. The phones may be fussy about which stock ROM they will accept. In my case, I thought the phone was a global version, then worked out that it was probably a Chinese version.
I replaced the firehose files in all the ROMs I attempted flashing with the ones supplied on XDA. The Xiaomi Flash tool reported success several times, but when starting up the phone it would go into recovery with the "MIUI version" message. I tried about six different MIUI ROMs with the testpoint method, both global and Chinese, before stumbling on the one that worked (after replacing the firehose files): whyred_images_V11.0.2.0.PEICNXM_20191023.0000.00_9.0_cn
When I got back into MIUI, I linked the phone to my MI account and then attempted flashing the latest LineageOS (which was what I was trying to do in the first place), using the Lineage recovery. The phone wasn't accepting the Lineage recovery, so I flashed OrangeFox-R11.0-Stable-whyred. I had to boot to Orangefox in order to flash it. You copy the Orangefox zip file to your phone using your computer when you have MIUI up and running, then you enter Fastboot and run the following command from your computer:
fastboot boot recovery.img
From Orangefox, you then select the Orangefox zip file on your phone and swipe to install.
Once that was done, I rebooted to recovery and did a wipe of the phone. It wasn't enough for me to wipe Dalvik/ ART Cache and Cache (as recommended), I had to also wipe System, Vendor and Data. (I tried just the first two and the LOS installation was corrupt, even though it was reported as being successful.) I then copied LOS to a micro SD card, inserted it into the phone and mounted it, before flashing LOS by navigating to the zip file on the SD card, selecting it and selecting wipe to install.
Finally success!
I think the key with the testpoint method is to keep trying ROMs until you stumble on the one that works. If the Xiaomi Flash tool reports success, I think it means you are doing something right. I also wonder if a lot of people who have the "MIUI version" issue have a phone with the Chinese ROM and don't realise it.
Hope this helped someone!
by any chances how do you unlock bootloader if you just bypass the mi account?
yoshukii19 said:
by any chances how do you unlock bootloader if you just bypass the mi account?
Click to expand...
Click to collapse
No hacking ... Why did you bypass mi account???
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
the reason is I got my phone Redmi Note 5 Pro on fb marketplace by swapping my old phone, when I'm using it there's no mi account logged in on my phone then I tried to install the latest MIUI 12 by flashing it on MiFlash but I didn't notice that I didn't change the setting on clean all so it locked my bootloader, after I manage to fix the issue about my phone because it doesn't open and it only boot on recovery with a message "This MIUI...." and make it boot by flashing cn official rom, it says that my phone is locked and I need to logged in the old mi account, I already ask the previous owner but he said he doesn't have an access on that account, even the number and email are already lost
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Aurora333 said:
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Click to expand...
Click to collapse
Why did you quote me?!?
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
You must have the firmware requested by the OP, flashed it if necessary.
See this rom below where everything is explained.
https://forum.xda-developers.com/t/rom-13-official-pixelos-aosp-unified-11-09-2022.4237791/
Other TWRP/OF.
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/willow/
Regrettably, my telephone is now hard-bricked. Recovery and Fastboot modes also not possible, so back to stock-ROM is no longer possible either. Only a flashing screen, and - when trying to enter fastboot mode, only short showings of the word fastboot, but no response in MiFlash. I think that a new phone is unavoidable.
Meanwhile, I've tried to enter EDL mode. Troed various fastboot commands, but no response from the telefone. Ultimately, I've tried to open the backcover (in order to reach the so-called "test points"), but that's easier said than done.
Website
is pretty clear, I know where to find those test points, but I'm lacking a 'heat gun', demonstarted in the youtube film. I tried it with a hairdryer, but that proved ineffective, moreover, the hairdryer stopped working (overheating?). Still need to check a possible fuse in the hardryer. Anyway, I'm awaiting a Redmi Note 11...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
But what went wrong in the first place?
The flashing instructions quoted
Flashing Instructions
Clean flash (coming from a different ROM):
• Flash recovery (links above)
• Download ROM from the link above
• Download Magisk v23.0 or newer (optionally)
• Reboot to recovery
• Format data (if encrypted)
• Wipe system, vendor, cache, dalvik, data
• Flash latest android 11 global stable firmware (link above)
• Flash ROM zip
• Reboot and voila!
It mentions "flash recovery". The only method to install TWRP that I know, is through fastboot commands (fastboot flash recovery twrp.img, after having renamed the latest twrp image file), and then "fastboot reboot" while keeping Power + Volume Up pressed.
Prior to this, I had placed the firmware-, ROM- and Magisk-files on the phone.
After installing TWRP and Magisk, I wiped cache and Dalvik.
Then, when tried to flash the ROM, apparently that was wiped too. I think that it would have been better to reboot the phone after installation of TWRP and Magisk, then transfer the firmware and rom-files to the phone, and then boot into recovery again.
Anyway, that was not what I did...
Right after installation of TWRP and Magisk, having seen that the files to be flashed, were no longer there, I tried to install the firmware- and ROM-files with 'adb sideload' commands from TWRP. The flashing process seemd to go well, but booting to system proved disastrous...
A 'lesson learned' - at least for me: do not proceed if you - for some reason - can't follow the instructions. but break off, so that you can still reflash the stock-rom!
Sometimes, flashing the firmware with the Twrp does not work and you have to flash the complete rom with Miflash.
For EDL mode you will not have the necessary authorization.
See my PM.
gjongbloed said:
But what went erong in the first place?
Click to expand...
Click to collapse
1st
2nd
what brick your phone is relocking the bootloader
never do that on a redmi note 8 !
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
gjongbloed said:
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
Click to expand...
Click to collapse
Redmi note 8t(Willow).
Anyway, even if you had done it, it wouldn't have changed anything,except that you would have relocked the bootloader, since this model is intended for the global market with roms, Global, EEA, Russian, no CN roms.
Situation at present (4-11-2022): I have succeeded in opening the telephone in order to make the 'test points' approachable and to disconnect the battery. In the 'device manager', I've seen 'Qualcom' appearing on one of the com-ports. To continue, I now have to await a 24 hours break after too many times of opening my Mi-account during earlier attempts of flashing with the MiFlash tool .
.....
Well, 24 hours later, I've come to the conclusion that my brick definitively remains a brick. Tried again and again, but each time received an error "Cannot receive hello packet. MiFlash is trying to reset status.". And that's it...
Meanwhile, I had the impression that I might have better results with the Qualcomm tool QPST. The telephone - in EDL mode - was observed in QPST Configuration all right, but the flashing with QFIL failed with a consistent error: Unable to read packet header.
I've seen many reported occurrences of this error in various XDA fora, but nowhere a conclusive remedy. I'm out of options now...
Now, I get the information that the file that I want to flash, is too large. If only there could be a smaller file, only to restore the part of the os, through which to activate the fastboot and recoverymodes...
Well, after many tries, searching for solutions for the various Sahara fails that I encountered while using QFIL, I found a solution that really worked:
[GUIDE] How to unbrick RN8 (won't boot only backlight turns on for a second) using EDL
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8 original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/ many thanks to dxD7 who provided...
forum.xda-developers.com
I could use the patched firehose file also on an older Global EEA version of the stock-ROM, and then everything worked fine... It took a while, updating the phone to the latest version, but that doesn't matter...
Well... the phone is working again with MIUI Global 12.5.5.0 (RCXEUXM).
Working, but... both IMEI's are null, therefore SIM cards are no longer recognized, which means that I can't use the dial function and can't use a mobile network. WiFi is working.
Moreover, the bootloader is locked again, but I can't unlock it with MiFlash Unlock, because this procedure requires connection via a mobile network. And without an unlocked bootloader, any possibility to root the phone, flash a repaired qcn file (with proper IMEI's), try out custom ROMs or whatever, is blocked...
Any option left? (Fastboot and EDL mode still possible).
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
gjongbloed said:
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
Click to expand...
Click to collapse
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Cristina.D.M said:
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Click to expand...
Click to collapse
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
gjongbloed said:
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
Click to expand...
Click to collapse
WoW, It is boomshell, Now I do know what is "One is never too old to learn".
Thanks ever so much for your reply.