Related
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.
Hi guys? pls help me, SM-N950N Korean version, before had frp lock I flashed combo file bootloader 3, then flashed stock 5 files with home_csc, and got boot loop, recovery information here https://ibb.co/mJRcHK
tnx in advance.
In another forums ppl are saying to install TWRP and to do format and wipe, but it is not possible to flash TWRP with OEM ON and FRP ON
Have you tried using Samsung Kies to try and restore your device? That should work
iceepyon said:
Have you tried using Samsung Kies to try and restore your device? That should work
Click to expand...
Click to collapse
Finally someone has replied thanks for your advice, I fixed 2 days ago, forgot to close the thread.
Anvar2005 said:
Finally someone has replied thanks for your advice, I fixed 2 days ago, forgot to close the thread.
Click to expand...
Click to collapse
How did you manage to fix your issue?
Anvar2005 said:
Finally someone has replied thanks for your advice, I fixed 2 days ago, forgot to close the thread.
Click to expand...
Click to collapse
how did you fix that ?
Anvar2005 said:
Hi guys? pls help me, SM-N950N Korean version, before had frp lock I flashed combo file bootloader 3, then flashed stock 5 files with home_csc, and got boot loop, recovery information here https://ibb.co/mJRcHK
tnx in advance.
In another forums ppl are saying to install TWRP and to do format and wipe, but it is not possible to flash TWRP with OEM ON and FRP ON
Click to expand...
Click to collapse
ANY samsung Stuck on Logo SOLVED by Flashing 5 File
BL
AP
CP
CSC
UserDATA
This fixed the Problem 1000000...%
Tested by Sireal (GSM Developer)
HI everyone I purchased a note 8 which was rooted using Magisk. i tried to unroot it but didnt know exactly the device model as it showed SM-N950F in the settings but when i opened it in Download mode, it showed me that device model is SM-N950N. I tried to flash stock firmware of SM-950F but it didn't work despite many efforts. Then I tried SM-950N Korean Sku version and it worked. My device was unrooted but its one IMEI is shown while other displays unknown. I can use only one sim, the other sim is not working. Any solution please.
So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...
grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader
I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...
But you don't need an unlocked bootloader to sideload an OTA....
xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.
grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!
How do I write IMEI along with baseband version back to my phone? I really don't want to risk bricking it again, that's enough stress for me in the past two days
I heard that I can only flash IMEI 2 back to it, and if I want flashing IMEI 1 as well I'd need to install a custom rom on the phone. So if that's a solution I'd love if someone could help me with it. MIUI 13 is slow and laggy af (which is the reason I bricked the phone in the first place, to install a better ROM).
But here's something, when I flash the phone's firmware through fastboot, issues start to rise (as per my experience with it so far), but through SP Flash Tool, it's alright. So I'd love to know if installing custom ROMs using the tool would be alright, if not then if recovery is required or if fastboot is fit for the job. If that's an issue I'd love if someone could give me advice when it comes to it.
Old post 1: (not my current situation)
"Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated."
Old post 2:
"It happened after manually installing engineering ROM on it, now I can only doubt it's BROM mode that's working and nothing else, but I'm not sure. SP Flash Tool doesn't want to work with the phone since I want to flash the stock rom back. I really need help please."
YLTN said:
Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated.
Click to expand...
Click to collapse
Install Engineering ROM and then write imei using available tools.
mvikrant97 said:
Install Engineering ROM and then write imei using available tools.
Click to expand...
Click to collapse
I fear that if I install the ROM, the phone might brick again
YLTN said:
I fear that if I install the ROM, the phone might brick again
Click to expand...
Click to collapse
Why?
mvikrant97 said:
Why?
Click to expand...
Click to collapse
The reason why my phone broke in the first place was due to flashing a misc.bin file after following a YouTube tutorial. It was part of a process to download twrp on the phone unofficially. Since then I started looking for ways to fix it until I finally found a post that had to do with fixing nvdata corruption (which was the error I had prior to fixing the phone) which helped.
So yeah, I don't think I can trust flashing ROMs on my phone as much as before, but I'll still try the engineering ROM thing.
mvikrant97 said:
Why?
Click to expand...
Click to collapse
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
YLTN said:
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
Click to expand...
Click to collapse
Does it shows up in device manager?
mvikrant97 said:
Does it shows up in device manager?
Click to expand...
Click to collapse
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
YLTN said:
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
Click to expand...
Click to collapse
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
YLTN said:
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
Click to expand...
Click to collapse
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
YLTN said:
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
Click to expand...
Click to collapse
Please install LIB USB drivers.
Visit this tutorial here on xda
mvikrant97 said:
Please install LIB USB drivers.
Visit this tutorial here on xda
Click to expand...
Click to collapse
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
YLTN said:
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
Click to expand...
Click to collapse
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
mvikrant97 said:
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
Click to expand...
Click to collapse
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
YLTN said:
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
Click to expand...
Click to collapse
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
Alright then, I'll follow the steps and tell you the results once I'm done.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
YLTN said:
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
Click to expand...
Click to collapse
Try flashing the ENG rom and try fixing your IMEI
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
So I ran into another issue. it tells me I need "exaid-verified.img" and that verified boot is enabled, which is not present in the ENG ROM folder.
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
Btw one more thing, I can update my phone right? Like, it won't break my phone? I'm good with MIUI 11 but I wonder if updating it would fix baseband version.
Soo, long story short, i hard bricked this phone and i definitely need good advice. Please bear with me:
I got a Poco M5s,
I wanted to install official PE on it.
I successfully unlocked bootloader (mtk client method)
I ****ed up because i flashed the recovery, but it was for the wrong MIUI version (i had A13 - SFFEUXM and PE needs A12 - RKLMIXM)
Then i compounded my mistake because i booted to fastboot over linux and flashed A12 - RKLMIXM (flashall.sh). The phone never booted after that.
Now the phone is fully unresponsive: Black screen and power/volume buttons seem to do nothing.
I tried to use SP Flash to reflash A13 - SFFEUXM, but it failed and wanted me to remove battery and retry.
I tried to disassemble the phone, specifically removing/reattaching the battery plug: no change in response & SP flash did not seem to download anything
I also tried to see if mtk client can detect the device, but worryingly, it thinks it is a Helio G90 (MT6785) instead of G95, and then fails with "DAXFlash - [LIB]: Error on sending emi: unpack requires a buffer of 12 bytes"
I'm totally disappointed at this point. Is this salvageable? What can i do?
Try this https://forum.xda-developers.com/t/recover-from-hard-brick-no-fastboot-or-recovery.4469431/
mwasikz said:
Try this https://forum.xda-developers.com/t/recover-from-hard-brick-no-fastboot-or-recovery.4469431/
Click to expand...
Click to collapse
Thank you very much! I managed to restore it with this!
I also learned a bit about "EDL mode".
One more question: Can i actually rollback to MIUI 12.5? What did i do wrong before?
jcd000 said:
Thank you very much! I managed to restore it with this!
I also learned a bit about "EDL mode".
One more question: Can i actually rollback to MIUI 12.5? What did i do wrong before?
Click to expand...
Click to collapse
I have tried to rollback to 12.5 too. Got a bootloop. So I searched online about it and found out that you need to use the latest Mi Flash tool ( I used 2020 version ). Then I tried with the 2022 version but this time I was getting a timeout error. The flash was stopping at 700 seconds. Since I have a really old and slow PC, it takes about 1200 seconds to flash. After that I have given up.
Which version of Mi Flash tool did you try? Try with the latest version if you have a relatively fast PC.
mwasikz said:
I have tried to rollback to 12.5 too. Got a bootloop. So I searched online about it and found out that you need to use the latest Mi Flash tool ( I used 2020 version ). Then I tried with the 2022 version but this time I was getting a timeout error. The flash was stopping at 700 seconds. Since I have a really old and slow PC, it takes about 1200 seconds to flash. After that I have given up.
Which version of Mi Flash tool did you try? Try with the latest version if you have a relatively fast PC.
Click to expand...
Click to collapse
I've tried various miflash versions (2017,2018,2020,2022). It always times out.
On linux, i managed to complete a flash using "flash_all.sh", but that's how i bricked it.
Hello, don't know if it is the good place for this but I have done the latest update (I have a Poco M5s with the version 13.0.10.0) and I just found the recovery flash for it (same version, Global.). I managed to unlock the phone after a few weeks of the phone being unrecognized by the pc, no matter how hard I tried to get the updated adb and android drivers. The latest Windows update included the Android drivers (which enabled me to unlock the bootloader).
I am planning to flash it using Magisk, any advice or things I should know?
Takemyjej said:
Hello, don't know if it is the good place for this but I have done the latest update (I have a Poco M5s with the version 13.0.10.0) and I just found the recovery flash for it (same version, Global.). I managed to unlock the phone after a few weeks of the phone being unrecognized by the pc, no matter how hard I tried to get the updated adb and android drivers. The latest Windows update included the Android drivers (which enabled me to unlock the bootloader).
I am planning to flash it using Magisk, any advice or things I should know?
Click to expand...
Click to collapse
user the search buttom and read
tutibreaker said:
user the search buttom and read
Click to expand...
Click to collapse
Lmao I'm sorry I finally managed to root the phone on my own.