So i have a day old red magic 3s that i tried to update, and now it just reboots to the blue screen with the recovery option. I try selecting recovery, but it never boots into recovery. Any ideas? I just got the phone, and now this?
How did you try to update it?
bignazpwns said:
How did you try to update it?
Click to expand...
Click to collapse
I used the update package from Red Magic website. It failed at 40%, rebooted, and now I only get to the blue screen that has serial #, and reboot to recovery, reboot to emergency recovery, and edr. I tried recovery, but it reboots to same screen. I tried edr, the screen turns off. I think I have a major issue. Any idea what happened?
You could try flashing with fastboot and see if that helps. There's guides on how to do it. The update zip will have the files. If that doesn't work I would just RMA it since you have a warranty.
If those don't work the only real option is to flash from a EDL programmer.
I have flashed all those files from the site to a phone and had no issues. So if it failed at 40% you could have an issue that might be hardware related.
Could try QFIL.
Be careful with QFIL tho.
bignazpwns said:
You could try flashing with fastboot and see if that helps. There's guides on how to do it. The update zip will have the files. If that doesn't work I would just RMA it since you have a warranty.
If those don't work the only real option is to flash from a EDL programmer.
I have flashed all those files from the site to a phone and had no issues. So if it failed at 40% you could have an issue that might be hardware related.
Could try QFIL.
Click to expand...
Click to collapse
I tried the fastboot flashing. I still only get to the bootloader screen. I contacted Red Magic, they wont accept a RMA, because i unlocked bootloader. They said warranty is void. I dont have any idea what QFIL is. I see there is some tool for the red magic 3. Would that work?
Enjoy your new paperweight OP! LMFAO. This phone is unrepairable without the nubia unbrick tool.
bignazpwns said:
Be careful with QFIL tho.
Click to expand...
Click to collapse
@bignazpwns could you help me out with QFIL? I have the program, but need the proper files. Thank you.
Yamvmax1 said:
@bignazpwns could you help me out with QFIL? I have the program, but need the proper files. Thank you.
Click to expand...
Click to collapse
Private message inbound
bignazpwns said:
Private message inbound
Click to expand...
Click to collapse
None of what you linked for me would help. I think we need the unbrick program. There is 4 or 5 of us now. Do you have it? Thank you.
Yamvmax1 said:
@bignazpwns could you help me out with QFIL? I have the program, but need the proper files. Thank you.
Click to expand...
Click to collapse
I also need the files?
Red Magic 3S unbrick tool here in the forums
https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207
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.
Can someone explain this
bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
I've not experienced this.
Are you rooted / bootloader unlocked?
Do you have any idea what caused it?
Were you able to recover?
If so, what did you have to do?
bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
Did you do anything to the bootloader by flashing any files? Did you unlock the bootloader? If the answer is yes then you might have an issue with flashed files.
If no and you have not touched the device then you might have a rare error. If you have a carrier phone with Verizon you might want to try their "repair assistant" which is the same as what is mentioned on the phone screen. It seems to have a repair function. You will have to connect the phone via USB to your computer. Download the assistant from here. https://www.verizonwireless.com/support/knowledge-base-209211/
If you don't have a Verizon moto x4 or you have another carrier then either still give the software a shot or take it to a Motorola service centre.
Can pretty much confirm the same with an old moto z force post on the Lenovo forums. If you have Verizon downloading the software will solve the problem.
I know that I was trying to flash to stock and that was the result, rsd can see the device but when I flash it it says failed to switch to fastboot
Yea bootloader has been unlocked for weeks and started acting up and I was trying to clear it and start over and no I can't get it to flash spar_chunks
Any ideas
Notice you mentioned RSD failing to switch to fastboot... I assume you tried reflashing the GPT/bootloader directly from fastboot?
If you hit volume up/down from the screen you posted, does it go through the other fastboot screens?
No i get the quausb or whatever that is in my comp for deviecs now...and no screen mow and yes the parition was compermised by error on my part
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
sk3lt said:
Hi,
After trying to flash I was like you can see in the image "nv data corrupted", does anyone know how to solve it?
Click to expand...
Click to collapse
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
otonieru said:
"Trying to flash" , what exactly did you flash ?
How do you flash it ?
Why dont you flash TWRP followed by ROM of any choice ?
NV normally contained in EFS partition, which can be backed up and flash from TWRP and QPST.
But again, your description is far from clear for us to help you.
Click to expand...
Click to collapse
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
sk3lt said:
I already flashed with twrp and miflash with stock rom and xiaomi.eu the flash is finished successfully but the nv data corrupted always comes back. Any idea how can I solve this?
Click to expand...
Click to collapse
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
otonieru said:
When you flash using TWRP, did you actually managed to boot into system ? Or it stuck in recovery ?
Where did the nv corrupted notification appear when u were using TWRP ?
Prior to facing this issue, what you actually did ? I mean, did this phone work before ? Before you start getting this error, what you did, what you install, what you flash, what you delete ? Or did it just suddenly happen with nothing modified ?
Click to expand...
Click to collapse
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
sk3lt said:
Boot up to the Android logo and then return to recovery.
I flashed a room and lost the imei, I tried to recover with a qcn I found but I must have done something wrong.
Click to expand...
Click to collapse
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
otonieru said:
You gonna need to ask someone to backup their QCN, take out the imei info, give it to you, and flash it using QPST.
Click to expand...
Click to collapse
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
sk3lt said:
I can't use qpst, because I can't activate usbdebug and the diag port.
Is it possible to give me a hand?
Click to expand...
Click to collapse
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
sk3lt said:
I flashed an altered rom, without success I got a brick I'm without recovery and without fastboot I just have a black screen and it's only recognized by the PC in 9008 mode, you have any idea how I can solve it?
Click to expand...
Click to collapse
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
tsongming said:
This is absolutely not a issue, that requires using Qpst
You simply need to wipe data and follow the on screen prompts. (You will lose all data on your phone.) However the phone will work again.
Click to expand...
Click to collapse
tsongming said:
Sorry that you are having these issues, But my comment was based on the photo that was posted on the OP. Typically formatting is the resolution. If you no longer have that screen available, you should contact an authorised repair center to fix it for you.
Otherwise If the phone is bound to your account, you could try what is listed here: https://www.mobilerdx.com/2019/02/xiaomi-mi-8-test-point-boot-xiaomi-mi-8-into-edl-9008-mode.html
Scams or Actual Fixes?
I have recently read about supposed hacks that according to a couple of Chinese BBS sites, has worked for some that require buying a specialised Jtag programming tool which cost about $60, that you use along with altered versions of following files: prog_emmc_firehose_8909.mbn.elf, mi8 persist image, rawprogram0, frp and a patch file. All of which that can all be obtained from here: https://romprovider.com/2019/09/mi-account-remove-xiaomi/ ( UMT Download)
Supposedly Chimera is another option: https://chimeratool.com/en/docs Again I have not used any of these tools with the mi8, I am merely sharing what I read about recently.
By the time you have spent the money acquiring the tools, it seems that you are better off just mailing the phone off to be repaired by an official repair center. Here is a web page that provides a list of official repair centers : https://www.pinoytechnoguide.com/2014/06/xiaomi-service-centers.html
Good Luck and try anything mentioned above at your own risk.
Edit: Have you tried the Flashall.bat method?
That should work since you are seeing the com port.
Click to expand...
Click to collapse
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
sk3lt said:
Hello, thank you for your answer, the mother is not linked to my account I disconnected to do the experiments. in my country i don't have a xiaomi assistance center, i get the error missmatching image and device.
There is no other way to unbrick without buying these tools so expensive that you mentioned
Click to expand...
Click to collapse
use testpoint method, and flash it using QFIL.
otonieru said:
use testpoint method, and flash it using QFIL.
Click to expand...
Click to collapse
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
sk3lt said:
I always get this error.
I already managed to unbrick with a firmware eng eng.
but then when flash with stock rom stays the same again nv data corrupted.
Any solution to solve this nv data corrupted?
Click to expand...
Click to collapse
root cause of your issue is that you play with wrong qcn and messed up the nv,
wince you cant plugged to qpst, you need someone to make EFS backup for you torestore from twrp
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
How can I do this? Can you help me please?
jokerm90 said:
You can restore phones imei if your bootloader is unlocked but only 2nd sim slot will work
Click to expand...
Click to collapse
How can I do this? Can you help me please?
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
sk3lt said:
How can I do this? Can you help me please?
Click to expand...
Click to collapse
You need backup EFS and Modem via TWRP first(better with OrangeFox). After you need Magisk first and some manipulation with QCN file via QPST. I will write it later
MohamedYousri said:
Dear All,
While trying to install MIUI 12 Beta , I Lost my IMEI
Installed ENG Firmware which allowed my to edit the IMEI using the Maui META ver 10.1816.0.01 but due to corrupted NV Data the phone isn't booting
Anyone can backup and share the NV Data file ?! i found one online but unfortunately it has a password and can't unrar it.
Your support is much appreciated to guide throw fixing this issue.
Click to expand...
Click to collapse
Maui Meta is for MTK cpu phones. You need QPST
Note 8 Pro is MTK Device
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.