Related
Could someone help me with this issue?
I unlocked the bootloader of my p768 a while ago, and then I sent it to the carrier service, because it was having some signal problems.
I read that, once you unlock your bootloader, you can't lock it again, so, when I got it back, it was kind of restored and today I tried to flash Clockworkmod (.img file) and when I tried to reboot it, it said "Security Error", I followed this guide:
http://forum.xda-developers.com/showthread.php?t=2470248
And when I connected the phone to the computer, and it says that the device already has the most recent version.
What do I do? Any suggestions?
Thanks
speakerstick said:
Could someone help me with this issue?
I unlocked the bootloader of my p768 a while ago, and then I sent it to the carrier service, because it was having some signal problems.
I read that, once you unlock your bootloader, you can't lock it again, so, when I got it back, it was kind of restored and today I tried to flash Clockworkmod (.img file) and when I tried to reboot it, it said "Security Error", I followed this guide:
http://forum.xda-developers.com/showthread.php?t=2470248
And when I connected the phone to the computer, and it says that the device already has the most recent version.
What do I do? Any suggestions?
Thanks
Click to expand...
Click to collapse
Hi @speakerstick
You need to update the recovery in the LG mobile support tool and then it should work.
Look in the top right screen and select "Support Tool Options Menu" and then select "Upgrade Recovery"
xdrc45 said:
Hi @speakerstick
You need to update the recovery in the LG mobile support tool and then it should work.
Look in the top right screen and select "Support Tool Options Menu" and then select "Upgrade Recovery"
Click to expand...
Click to collapse
I've tried, but when it says it's uploading it to the phone it suddenly disconnects and I have to do the same process again, but the same thing happens.
What do I do?
Thanks
speakerstick said:
I've tried, but when it says it's uploading it to the phone it suddenly disconnects and I have to do the same process again, but the same thing happens.
What do I do?
Thanks
Click to expand...
Click to collapse
Are you using the stock cable? If not, do so.
Have you made sure nothing else (NOTHING ELSE BUT THE NECESSARY) is connected to the other USB ports? Unplug stuff.
Do you have the drivers needed? Uninstall, redownload, reinstall.
Have you tried on another USB port?
Do you have any idea, based on the logs the program generates, about what might be wrong?
I've done it! I finally was able to do it. I uploaded it with the battery, I know the guide says you shouldn't but it worked, now... Does anyone know how to re-root the device? I unlocked the bootloader a while ago and then I sent it to service, but how do I "root" the phone again?
Thanks!
speakerstick said:
I've done it! I finally was able to do it. I uploaded it with the battery, I know the guide says you shouldn't but it worked, now... Does anyone know how to re-root the device? I unlocked the bootloader a while ago and then I sent it to service, but how do I "root" the phone again?
Thanks!
Click to expand...
Click to collapse
That's great.. Glad you got it working.
You can re-root it easily with "Cydia Impactor" You can get it from here - http://www.cydiaimpactor.com
xdrc45 said:
That's great.. Glad you got it working.
You can re-root it easily with "Cydia Impactor" You can get it from here - http://www.cydiaimpactor.com
Click to expand...
Click to collapse
So I'll be able to install CWM by the fastboot method? or what do I do?
Thanks
speakerstick said:
So I'll be able to install CWM by the fastboot method? or what do I do?
Thanks
Click to expand...
Click to collapse
Maybe you should try doing it the same way when you first unlocked the bootloader? Just a thought....lol.
Sent from my LG-P769 using Forum Fiend v1.2.7.
Hi, my Redmi note 3 Pro was working just fine on MoKee rom but I wanted to change for LineageOS 14.1, so I did it. So I flashed the firmware to have the latest then flashed everything fine. My phone worked fine on LineageOS til I install adaway, my phone asked for a reboot and I had black screen after typing my Sim Card PIN. I did multiple fresh install, different rom, Stock and Custom, android N, always the same problem. I also tried different version of TWRP, still the black screen of death. I also tried ZCW_TWRP but it was still the same. I formatted partition manually using fastboot and still the same problem.
Then I did nothing different, Wipe of everything necessary using TWRP, installed LineageOS 14.1 and it worked just like this, totally random. Yesterday, I was trying to copy some music on my SD card when my phone froze in the middle of the process. Of course, I had to reboot it and now he is freezing on boot with this beautiful black screen of death just after I enter my Sim Card PIN.
I tried to flash the Radon Kernel to see if something was going to change but it stayed the same. I am thinking it is because of the firmware since I didn't have any problem before I flash it.
Pls guys tell me you have a solution. It seems like it's a random bug occuring for no obvious reason and disappearing like if nothing just happened.
Thanks you all for reading and I hope you'll have some solutions for me
ddescham said:
Hi, my Redmi note 3 Pro was working just fine on MoKee rom but I wanted to change for LineageOS 14.1, so I did it. So I flashed the firmware to have the latest then flashed everything fine. My phone worked fine on LineageOS til I install adaway, my phone asked for a reboot and I had black screen after typing my Sim Card PIN. I did multiple fresh install, different rom, Stock and Custom, MM and N, always the same problem. I also tried different version of TWRP, still the black screen of death. I also tried ZCW_TWRP but it was still the same. I formatted partition manually using fastboot and still the same problem.
Then I did nothing different, Wipe of everything necessary using TWRP, installed LineageOS 14.1 and it worked just like this, totally random. Yesterday, I was trying to copy some music on my SD card when my phone froze in the middle of the process. Of course, I had to reboot it and now he is freezing on boot with this beautiful black screen of death just after I enter my Sim Card PIN.
I tried to flash the Radon Kernel to see if something was going to change but it stayed the same. I am thinking it is because of the firmware since I didn't have any problem before I flash it.
Pls guys tell me you have a solution. It seems like it's a random bug occuring for no obvious reason and disappearing like if nothing just happened.
Thanks you all for reading and I hope you'll have some solutions for me
Click to expand...
Click to collapse
Try reverting to latest global dev rom in fastboot (clean all), unlock and flash los again.
JLius said:
Try reverting to latest global dev rom in fastboot (clean all), unlock and flash los again.
Click to expand...
Click to collapse
I tried it already, didn't work. My phone kept freezing on boot. Exact same problem.
ddescham said:
I tried it already, didn't work. My phone kept freezing on boot. Exact same problem.
Click to expand...
Click to collapse
Then you'll probably need a new phone
JLius said:
Then you'll probably need a new phone
Click to expand...
Click to collapse
My phone work now, but I don't know for how long. SInce it's a random bug.
ddescham said:
My phone work now, but I don't know for how long. SInce it's a random bug.
Click to expand...
Click to collapse
Can't be a bug when you clean flashed miui.
ddescham said:
My phone work now, but I don't know for how long. SInce it's a random bug.
Click to expand...
Click to collapse
It's surely some eMMC issue
bro,try removing sim card lock.
just try it.Can it be your solution!!
Androbots said:
It's surely some eMMC issue
Click to expand...
Click to collapse
How do I fix that then?
dean [email protected]# said:
bro,try removing sim card lock.
just try it.Can it be your solution!!
Click to expand...
Click to collapse
No, it's not. If the solution was that simple, I wouldn't be asking there. I tried booting it without any Sim card and the result was the exact same.
bro,you flashed which firmware after you got all this problem, please describe the full name
dean [email protected]# said:
bro,you flashed which firmware after you got all this problem, please describe the full name
Click to expand...
Click to collapse
I flashed the firmware of the miui_HMNote3ProGlobal_7.6.7. Found the Zip here on XDA. And this version is recommended for custom ROM which is my case. I tried to flash another version of the firmware but I still have the same issue anyway.
bro,the firmware you flashed is I think have some problems,I visited the page from where you downloaded this firmware on xda and a lot of people are having sim card problems. so,try contacting maintainer of that firmware to get solution.
dean [email protected]# said:
bro,the firmware you flashed is I think have some problems,I visited the page from where you downloaded this firmware on xda and a lot of people are having sim card problems. so,try contacting maintainer of that firmware to get solution.
Click to expand...
Click to collapse
I don't have problem with my sim card... I have a black screen of death WITH and WITHOUT sim card in >.> Also, I told you I flashed a different firmware and I still have the same problem.
ddescham said:
I don't have problem with my sim card... I have a black screen of death WITH and WITHOUT sim card in >.> Also, I told you I flashed a different firmware and I still have the same problem.
Click to expand...
Click to collapse
Flash firmware from lineage os thread
ook bro ,so I don't know your problem solution
Androbots said:
Flash firmware from lineage os thread
Click to expand...
Click to collapse
If you are talking about that thread https://goo.gl/t5SVYv , I tried there solution and there firmware gave me the same issue too.
dean [email protected]# said:
ook bro ,so I don't know your problem solution
Click to expand...
Click to collapse
Thanks for trying.
ddescham said:
If you are talking about that thread https://goo.gl/t5SVYv , I tried there solution and there firmware gave me the same issue too.
Thanks for trying.
Click to expand...
Click to collapse
milankumarn said:
Mi logo blinks when i press the power button.
Click to expand...
Click to collapse
Flash stock emmc file that u can obtain from latest official miui ROM via fastboot.
- Boot into fastboot (connect device to pc),
- Open cmd on adb fastboot (on adb folder press and hold shift+right click then click open command windows here),
- Type fastboot flash aboot "drag and drop emmc file to ur command line" then press enter.
Hope it works.
Capt. John Yossarian said:
Flash stock emmc file that u can obtain from latest official miui ROM via fastboot.
- Boot into fastboot (connect device to pc),
- Open cmd on adb fastboot (on adb folder press and hold shift+right click then click open command windows here),
- Type fastboot flash aboot "drag and drop emmc file to ur command line" then press enter.
Hope it works.
Click to expand...
Click to collapse
I already flashed latest MIUI ROM in fastboot mode and the phone was still having the same issue. Black screen after I enter my Pin code or after 5 seconds of running, while starting android and everything.
ddescham said:
I already flashed latest MIUI ROM in fastboot mode and the phone was still having the same issue. Black screen after I enter my Pin code or after 5 seconds of running, while starting android and everything.
Click to expand...
Click to collapse
Emmc file, not rom.
Capt. John Yossarian said:
Emmc file, not rom.
Click to expand...
Click to collapse
When you flash a ROM, you flash the emmc as well.
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
MyNameIsRage said:
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
Click to expand...
Click to collapse
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only ? All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too ?
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
MyNameIsRage said:
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
Click to expand...
Click to collapse
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!! ?????
addymishra said:
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!!
Click to expand...
Click to collapse
lol, god bless our redmi note 4.
MyNameIsRage said:
lol, god bless our redmi note 4.
Click to expand...
Click to collapse
Yes!
addymishra said:
Yes!
Click to expand...
Click to collapse
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Jimmy_979 said:
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Click to expand...
Click to collapse
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
addymishra said:
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
Click to expand...
Click to collapse
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
Haha thats great congrats! Tip for custom rom installation is to follow install guide carefully and don't ever touch root partition lol! I've stopped flashing roms now... I'm on miui now permanently with bootloader locked lol
MyNameIsRage said:
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Click to expand...
Click to collapse
Haha @MyNameIsRage I'm thinking so ???
I m stuck in this same problem
But i never tried qflash
Wellll
I buy new op5t but i still wnt back to rn4
Will tell ya guys tonight nd please help me with proper procrdure
I downloaded everything but wich file have to flash
Or any video out there?
Saved my rn4
Thank u all
Thnx alot
my phone keeps rebooting
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
Pls bro am going Tru this same problem flashed through recovery flashed through fastboot but it keeps rebooting pls help me out with the exact steps u used to fix urs
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
I am in same problem on mido. Can you help me how to get in edl mode because QFIL Not detecting PORT.
Also my adb not detecting the device so i cant use adb commands.
But i can flash Stock ROM using MI Flash Tools.
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
hey guyz i have the same problem , please help me i tried all written in the replies but faces the same problem in the QFIL.
please reply, i'm dead :"(
Hello dear fellow mido users. I am trying to solve a problem here and I would very much appreciate your help on this:
I am running latest MIUI Stable Global flashed from fastboot, I have IMEI, but I don't have mobile signal. WiFi & BT works fine.
How I got here:
Bricked the phone about half a year ago
Ressurected it a week ago via connecting the pins in the back and flashing via edl.
I have unlocked it officially, as I had it unlocked before.
I have flashed TWRP & latest official RR, but it bootlooped, because my /persist partition was freaked out, so I reflashed it from the extracted fastboot ROM and I booted.
However, both my IMEIs dissappeared, and I only had the first IMEI from the back of my phone. So I calculated the second IMEI per a tutorial (from a Czech site) and restored both IMEIs via the Qualcomm QPST xqcn file, verified both IMEIs are showing up on my phone and are valid as per online IMEI checkers.
However, the signal didn't work, so I reflashed another mido device's IMEI (I have my original IMEIs backed-up) and flashed latest MIUI fastboot ROM, still no signal.
And here I am, and I am asking you for help..
If anyone can help me or at least point me in the right direction I will be eternally grateful :angel:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
JouzaCZ said:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
Click to expand...
Click to collapse
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
crok.bic said:
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
Click to expand...
Click to collapse
Thank you so much for your reply. I just checked, the cable wasn't disconnected, but I dis-and-reconnected it just to make sure. Still no signal.
I should mention I reflashed my original IMEI and verified that its valid once again. I am attaching links to pictures of the back of my phone disassembled if anyone can spot something wrong: PHOTOS.
Still hoping for a solution.
JouzaCZ said:
Still hoping for a solution.
Click to expand...
Click to collapse
Okay, starts to be interesting. Did you play with the band selection? Probably the band has been changed to US?
Hope you have Magisk (root) - if not please flash Magisk.
I presume ADB is already installed.
Put the phone to airplane mode.
From a PC open a cmd and issue adb shell
or start a terminal emulator on your phone
Then issue these commands in the shell
su
pm clear com.android.providers.telephony
settings put global preferred_network_mode 10
settings put global preferred_network_mode1 10
settings put global preferred_network_mode2 10
Remove airplane mode.
Restart.
Check again.
If still not works:
Start phone in fastboot mode
Issue these commands from PC cmd:
fastboot devices << just to make sure you phone is recognised
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
It will restart.
Check again.
Anyway, if you issue *#*#INFO#*#* or better known as *#*#4636#*#* in the dialer then selecting Phone 1 or Phone 2 (according to the SIM slot you want to check) in the top right or lower left there is a band-select menu (not in MIUI but in other custom ROMs) so there you are able to select the correct band if you want (that would mean you flash any custom ROM from TWRP or any custom recovery for a couple of minutes, go to dialer and look around)
crok.bic said:
Ping
Click to expand...
Click to collapse
Tried everything you said in order, still doesn't work. In normal fastboot, fastboot erase modemst1 results in this image isn't allow download. So I used mfastboot and it worked, however still no signal. When I try to switch the band in the options menu, there are two options: Automatic and United States. When clicked, both result in: Set [United States/Automatic] Unsuccessful.
And I just noticed it erased my IMEI again... Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
JouzaCZ said:
Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
Click to expand...
Click to collapse
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
crok.bic said:
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
Click to expand...
Click to collapse
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
JouzaCZ said:
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
Click to expand...
Click to collapse
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
crok.bic said:
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
Click to expand...
Click to collapse
Okay, I followed the first tutorial and successfully restored both IMEIs, still not working. I noticed, while flashing the xQCN file, it gives me a message about the model number of the phone not matching the model number of the xqcn file. Is that normal?
Last resort is to follow the second tutorial and redo everything.
JouzaCZ said:
gives me a message about the model number of the phone not matching the model number of the xqcn file
Click to expand...
Click to collapse
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
crok.bic said:
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
Click to expand...
Click to collapse
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
JouzaCZ said:
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
Click to expand...
Click to collapse
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
crok.bic said:
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
Click to expand...
Click to collapse
fastboot getvar product: mido
adb devices: 7e03cac30903 device
JouzaCZ said:
fastboot getvar product: mido
Click to expand...
Click to collapse
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
crok.bic said:
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
Click to expand...
Click to collapse
Pasting from a thread I made back when I bricked the phone:
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
Click to expand...
Click to collapse
JouzaCZ said:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Click to expand...
Click to collapse
Do you have this backup you made with RedWolf?
JouzaCZ said:
including the Firmware and EFS partitions, basically every partition
Click to expand...
Click to collapse
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
Do you have this backup you made with RedWolf?
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
JouzaCZ said:
Pasting from a thread I made back when I bricked the phone:
Click to expand...
Click to collapse
JouzaCZ said:
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
Click to expand...
Click to collapse
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Decent version. Specifically: 953_GEN_PACK-1.148143.1.163979.1
Also can we switch to some IM like WhatsApp so we don't have to keep pinging each other via quotes? I will post the solution/result in the thread.
My Device was on firmware version RMX2202_11.C.15 GDPR, it wasnt the latest one and software update wasn't pushing the latest ota package for my device which is RMX2202_11.C.25 GDPR.
So, i decided to rollback to RUI2.0 and update again and that might solve the problem. i unlocked my bootloader, booted on twrp, flashed rollback "RMX2202_11.A.17 GDPR" package, wipe data, boot into system.
All good till now, software update pushed me 700MB ota package, i download and installed it. Device asks for reboot i rebooted my device , device went off. DEAD no sign of life. only EDL MODE.
no recovery, no bootloader, no vibrate , no bootloop , completely DEAD. Then i took it to realme service center, they tried to flash my device , they got some error they returned my phone and said we cant repair because your device is rejecting firmware.
i attached the msm tool error. (WCSM communication failed (WCSM code: 4009 SW version of this package is not found in WCSM.)
PLEASE HELP ME!
Try to Change A computer?
DestoryG said:
Try to Change A computer?
Click to expand...
Click to collapse
i tried from different computers. 4 5 may be
Can i try with your phone ?
xuanhoang1811 said:
Can i try with your phone ?
Click to expand...
Click to collapse
Thanks for your reply.
I fixed my phone with the help of some technician online, he successfully flashed c.15 firmware using oplus flash tool v4.1.0.
Thank god and thanks to technician, my phone came back to life again.
But still my phone's software update is not pushing ota package. If you have solution please suggest me.
XxMinixX said:
View attachment 5766719
Click to expand...
Click to collapse
Mine still stuck at 11.c.05 i use this phone for about 3 months but still no updates
XxMinixX said:
Mine still stuck at 11.c.05 i use this phone for about 3 months but still no updates
Click to expand...
Click to collapse
i am able to update my phone to the latest ota. i can help you if you want
Ashim Adhikari said:
Thanks for your reply.
I fixed my phone with the help of some technician online, he successfully flashed c.15 firmware using oplus flash tool v4.1.0.
Thank god and thanks to technician, my phone came back to life again.
But still my phone's software update is not pushing ota package. If you have solution please suggest me.
Click to expand...
Click to collapse
Can you recommend me your technician? My GT is stuck in boot loop. Technician here says it has no recovery or something similar, and is still waiting for a recovery file for GT for it to be fixed. Thanks!
vlmapalo said:
Can you recommend me your technician? My GT is stuck in boot loop. Technician here says it has no recovery or something similar, and is still waiting for a recovery file for GT for it to be fixed. Thanks!
Click to expand...
Click to collapse
his website is MOD EDIT: URL REMOVED | READ AND FOLLOW XDA FORUM RULES
Ashim Adhikari said:
his website is https://www.kreatifintech.com/
Click to expand...
Click to collapse
paid service advertising, you have been reported
Ashim Adhikari said:
his website is MOD EDIT: URL REMOVED | READ AND FOLLOW XDA FORUM RULES
Click to expand...
Click to collapse
All this thread maked for advertise some indian guys)))