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.
Related
Ok i need help with my device.
I got a s6 edge SMG925I a while ago, yesterday an update (i guess its called OTA) popped up and i installed it. after the installation was completed but now i'm not registered on network, and i can't detect my SIM card.
Note: my IMEI is NOT blocked.
So far all my efforts were for nothing.
All the info i got so far by searching
Problems:
Not registered on network
when typing *#06# it only show S/N
About device it shows IMEI: Unknown
did not back up the efs folder (but i GUESS the folder is still there and somehow the new stock can't access it)
Android ver. 6.0.1(marshmallow)
Possible cause:
EFS Folder corrupted
Bad Stock installation
Already tried:
Rooting (i wasnt able to root)
Installing latest stock rom
installing the old rom
QPST to change IMEI
Please help me guys
EDIT:
I figured out what happened, my efs got deleted somehow, i got no backup, is there a way around this? help me please
brunao90 said:
Ok i need help with my device.
I got a s6 edge SMG925I a while ago, yesterday an update (i guess its called OTA) popped up and i installed it. after the installation was completed but now i'm not registered on network, and i can't detect my SIM card.
Note: my IMEI is NOT blocked.
So far all my efforts were for nothing.
All the info i got so far by searching
Problems:
Not registered on network
when typing *#06# it only show S/N
About device it shows IMEI: Unknown
did not back up the efs folder (but i GUESS the folder is still there and somehow the new stock can't access it)
Android ver. 6.0.1(marshmallow)
Possible cause:
EFS Folder corrupted
Bad Stock installation
Already tried:
Rooting (i wasnt able to root)
Installing latest stock rom
installing the old rom
QPST to change IMEI
Please help me guys
Click to expand...
Click to collapse
How about a simple reset from the settings menu? But I am pretty sure, if you somehow deleted the IMEI imformation, your chances are not the best. You'd have to find a way, to get write thatbinfo back. What you could do is ask someone else to backup that partition for you and change the values according to your phone ( IMEI, serial number,...) Then flash this partition info back. Good luck!
Sent from my SM-G925F using XDA Free mobile app
CM recovery
brunao90 said:
Ok i need help with my device.
I got a s6 edge SMG925I a while ago, yesterday an update (i guess its called OTA) popped up and i installed it. after the installation was completed but now i'm not registered on network, and i can't detect my SIM card.
Note: my IMEI is NOT blocked.
So far all my efforts were for nothing.
All the info i got so far by searching
Problems:
Not registered on network
when typing *#06# it only show S/N
About device it shows IMEI: Unknown
did not back up the efs folder (but i GUESS the folder is still there and somehow the new stock can't access it)
Android ver. 6.0.1(marshmallow)
Possible cause:
EFS Folder corrupted
Bad Stock installation
Already tried:
Rooting (i wasnt able to root)
Installing latest stock rom
installing the old rom
QPST to change IMEI
Please help me guys
Click to expand...
Click to collapse
i think you can install CM recovery (TWRP) then you can process the backup of your old rom from the recovery.
just enter in recovery mode then you'll find "restore" choose all the files ( i think there will be like this: System, Cashe, Efs, Boot...) then hit Restore botton, and wait for it to boot up hope this helps you bro
N00BY0815 said:
How about a simple reset from the settings menu? But I am pretty sure, if you somehow deleted the IMEI imformation, your chances are not the best. You'd have to find a way, to get write thatbinfo back. What you could do is ask someone else to backup that partition for you and change the values according to your phone ( IMEI, serial number,...) Then flash this partition info back. Good luck!
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
Ok, the reset didn't work, is there a way to write it back? it can be done?
g3nius85 said:
i think you can install CM recovery (TWRP) then you can process the backup of your old rom from the recovery.
just enter in recovery mode then you'll find "restore" choose all the files ( i think there will be like this: System, Cashe, Efs, Boot...) then hit Restore botton, and wait for it to boot up hope this helps you bro
Click to expand...
Click to collapse
Thank you, i'll try that now
edit: it didn't work, its kinda obvious the backup file was empty
try
brunao90 said:
Ok, the reset didn't work, is there a way to write it back? it can be done?
Thank you, i'll try that now
edit: it didn't work, its kinda obvious the backup file was empty
Click to expand...
Click to collapse
sorry to hear that try to install the 4 files rom with PIT file hope that will work
g3nius85 said:
sorry to hear that try to install the 4 files rom with PIT file hope that will work
Click to expand...
Click to collapse
Sorry for the noob question but how do i do that?
By the way, I managed to figured out what happened.
Long story short, my efs got deleted somehow and now its lost forever. What should i do?
brunao90 said:
Sorry for the noob question but how do i do that?
By the way, I managed to figured out what happened.
Long story short, my efs got deleted somehow and now its lost forever. What should i do?
Click to expand...
Click to collapse
You need someone to write a new cert in your phone and fix the imei.
FakeSmile said:
You need someone to write a new cert in your phone and fix the imei.
Click to expand...
Click to collapse
Ok but i don't know anyone who can do this, u got any advice?
brunao90 said:
Ok but i don't know anyone who can do this, u got any advice?
Click to expand...
Click to collapse
Try to get the efs partition holding the information from someone else, change it to your IMEI, serial,... And flash that partition to your phone and you should be good. I guess you'd have to use a hex editor to get that done. I am not rooted, so I can't back it up for you.
Sent from my SM-G925F using XDA Free mobile app
I have a G900T that I was a running Skiesrom CFW for about a month until I noticed it stopped detecting the sim card, getting constant reboots and restarts instead of powering down. I went to stock with odin thinking it would fix it but it did not. Any suggestions and opinions would greatly be appreciated. Thanks.
Happened to me too once when i flashed wrong rom using odin which lead me to Nil Baseband version and IMEI
Did u check them if they are ok
Install a SD card checking (SD Insight is the one I use) and check your SD card. There are thousands of fakes around that report they have much more storage than they actually do. They work fine at first until they fill up and you start trying to store data in locations that don't actually exist.
Sam7777777 said:
Happened to me too once when i flashed wrong rom using odin which lead me to Nil Baseband version and IMEI
Did u check them if they are ok
Click to expand...
Click to collapse
It looks like that may be the problem. It says unknown for both. Will try to fix and hope it works. Thanks.
fresco194 said:
It looks like that may be the problem. It says unknown for both. Will try to fix and hope it works. Thanks.
Click to expand...
Click to collapse
Not as easy as I though.
Have service mode also gone blank? u can check it using #*9090#
if yes, then your phone has kinda gone far from the normal damage state imo, as normal restore things like odin etc. doesn't help
Check Device Serial Number, if that's fine
IDK your Knowledge level but
Read this post till the End before attempting to do anything
I had recovered my phone from the following scenerio
1. Baseband - Unknown
2. IMEI - Nil
3. Service mode - Blank with horizontal lines
4. No Sim detection
5. Random reboots and restart instead of Power off
BUT
6. Seriel Number - Ok (Original)
In my case i wasn't able to get back imei baseband, no matter what i do, restoring efs backup, trying diffrent baseband, stock restore everything using odin diffrent Rom versions too but
nothing worked
I followed the steps given in thread mentioned below to recover my device, This thread and file/s mentioned in there are for Note 3 only
but i used the Note 3 file on S5 with SM-G900T PIT file,
Don't use PIT file from NOTE 3 (Thread)
Everything is back to normal except Service Mode is partially recovered, still i have it that way
(writing Note 3 file on S5 , i guess, the reason for broken service mode)
Here's the thread
https://forum.xda-developers.com/showthread.php?t=2567133
I had followed it till adb commands only, as far as i remember, didn't follow seriel number editing etc.
I'd recommend to follow the thread only if have have tried other ways to get around the issue and you are sure your phone is unrecoverable by any other means
bcuz Nowadays unknown baseband and nil imei happens too me sometimes but going stock ALWAYS gets them back
i'd recommend you to Backup your IMEI (EFS) Folder in current state (Most probably it is not corrupted) and store in somewhere safely and to be on a safer side backup bootloader too (Bootloader not needed but...you never know if you are not much of a developer)
Backup in multiple formats and with multiple tools (I always wanna play safe), Flashfire also backsup EFS
You can also backup whole folder manually too, your choice
For bootloader backup
i used following ADB command as Root
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
I don't know if this will work for you, Don't hold me responsible if your device gets even worse, just trying to help ; )
Lemme Know if any clarification is needed
Sam7777777 said:
Have service mode also gone blank? u can check it using #*9090#
if yes, then your phone has kinda gone far from the normal damage state imo, as normal restore things like odin etc. doesn't help
Check Device Serial Number, if that's fine
IDK your Knowledge level but
Read this post till the End before attempting to do anything
I had recovered my phone from the following scenerio
1. Baseband - Unknown
2. IMEI - Nil
3. Service mode - Blank with horizontal lines
4. No Sim detection
5. Random reboots and restart instead of Power off
BUT
6. Seriel Number - Ok (Original)
In my case i wasn't able to get back imei baseband, no matter what i do, restoring efs backup, trying diffrent baseband, stock restore everything using odin diffrent Rom versions too but
nothing worked
I followed the steps given in thread mentioned below to recover my device, This thread and file/s mentioned in there are for Note 3 only
but i used the Note 3 file on S5 with SM-G900T PIT file,
Don't use PIT file from NOTE 3 (Thread)
Everything is back to normal except Service Mode is partially recovered, still i have it that way
(writing Note 3 file on S5 , i guess, the reason for broken service mode)
Here's the thread
https://forum.xda-developers.com/showthread.php?t=2567133
I had followed it till adb commands only, as far as i remember, didn't follow seriel number editing etc.
I'd recommend to follow the thread only if have have tried other ways to get around the issue and you are sure your phone is unrecoverable by any other means
bcuz Nowadays unknown baseband and nil imei happens too me sometimes but going stock ALWAYS gets them back
i'd recommend you to Backup your IMEI (EFS) Folder in current state (Most probably it is not corrupted) and store in somewhere safely and to be on a safer side backup bootloader too (Bootloader not needed but...you never know if you are not much of a developer)
Backup in multiple formats and with multiple tools (I always wanna play safe), Flashfire also backsup EFS
You can also backup whole folder manually too, your choice
For bootloader backup
i used following ADB command as Root
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200MB.img bs=4096 count=50000
I don't know if this will work for you, Don't hold me responsible if your device gets even worse, just trying to help ; )
Lemme Know if any clarification is needed
Click to expand...
Click to collapse
All of your scenarios is exactly what is going on with mine to the "T". Service mode is blank and I do get a serial number but blank IMEI. Even my phone powered on on it's own from being completely shut down for a while. I tried flashing PIT with odin to tried to re-partition but it would not flash. Gives me a secured failed in download mode. I will look into your suggestion. Thanks.
fresco194 said:
All of your scenarios is exactly what is going on with mine to the "T". Service mode is blank and I do get a serial number but blank IMEI. Even my phone powered on on it's own from being completely shut down for a while. I tried flashing PIT with odin to tried to re-partition but it would not flash. Gives me a secured failed in download mode. I will look into your suggestion. Thanks.
Click to expand...
Click to collapse
Unfortunately I did'nt get very far. I tried to odin flash a clean rom with a pit file and I get: Secure Check Fail : PIT:crying:
fresco194 said:
Unfortunately I did'nt get very far. I tried to odin flash a clean rom with a pit file and I get: Secure Check Fail : PIT:crying:
Click to expand...
Click to collapse
I don't remember exactly what was my scenerio about ODIN failure
It's been months since i went through the process
but vaguely i remember i changed the correct PIT file, took that from below drive link
https://drive.google.com/file/d/0BzyeAt2hy6XeLWdrTHNNQ0dDUlE/view
make sure u r using the correct file and latest odin .tar which is the link below
https://www.androidfilehost.com/?fid=457095661767125212
Another guy was also having this problem but i don't remember much.
Sam7777777 said:
I don't remember exactly what was my scenerio about ODIN failure
It's been months since i went through the process
but vaguely i remember i changed the correct PIT file, took that from below drive link
https://drive.google.com/file/d/0BzyeAt2hy6XeLWdrTHNNQ0dDUlE/view
make sure u r using the correct file and latest odin .tar which is the link below
https://www.androidfilehost.com/?fid=457095661767125212
Another guy was also having this problem but i don't remember much.
Click to expand...
Click to collapse
:good::laugh:You are the man!!:highfive: It was the PIT file. Even though the one I had said G900T it was not correct. Did you go through the adb stuff also?
fresco194 said:
:good::laugh:You are the man!!:highfive: It was the PIT file. Even though the one I had said G900T it was not correct. Did you go through the adb stuff also?
Click to expand...
Click to collapse
Yes, till ADB only, cuz my serial number was correct already, and i noticed my phone was back after that, as far as i remember
Sam7777777 said:
Yes, till ADB only, cuz my serial number was correct already, and i noticed my phone was back after that, as far as i remember
Click to expand...
Click to collapse
I think I'm going to give up. Thanks anyway. Really appreciated.
fresco194 said:
I think I'm going to give up. Thanks anyway. Really appreciated.
Click to expand...
Click to collapse
You are just one step away, if u hv time
make sure you have allowed adb to run as root (supersu app), check supersu app, if adb requested permisiion and thats falsly disallowed
Setup working ADB connection, test it
allow adb shell to run as root
run following commands one by one
adb devices
adb shell
su
when u type su and hit enter, it should ask you for supersu permission on ur phone interface
Grant the permission
Also
have Busybox installed in your device
Usb debugging (obviously)
that's coming in my mind right now
Good Luck, if you try
Sam7777777 said:
You are just one step away, if u hv time
make sure you have allowed adb to run as root (supersu app), check supersu app, if adb requested permisiion and thats falsly disallowed
Setup working ADB connection, test it
allow adb shell to run as root
run following commands one by one
adb devices
adb shell
su
when u type su and hit enter, it should ask you for supersu permission on ur phone interface
Grant the permission
Also
have Busybox installed in your device
Usb debugging (obviously)
that's coming in my mind right now
Good Luck, if you try
Click to expand...
Click to collapse
Success!!! My phone is back up and running fine. Had a little scare after I rebooted it was going into download mode and saying "could not do normal boot" but I just re-flashed recovery in odin and re flashed rom and everything is working with my IMEI and serial. Thanks again for your help.
fresco194 said:
Success!!! My phone is back up and running fine. Had a little scare after I rebooted it was going into download mode and saying "could not do normal boot" but I just re-flashed recovery in odin and re flashed rom and everything is working with my IMEI and serial. Thanks again for your help.
Click to expand...
Click to collapse
Good to hear this
:victory:
Service Mode recovered too?
Sam7777777 said:
Good to hear this
:victory:
Service Mode recovered too?
Click to expand...
Click to collapse
It says DIAG CONFIG on the first line and not supported on second line.
fresco194 said:
It says DIAG CONFIG on the first line and not supported on second line.
Click to expand...
Click to collapse
As expected
but that's okey as long as phone's core functionality is working
Anyways
Have Fun !
Sam7777777 said:
As expected
but that's okey as long as phone's core functionality is working
Anyways
Have Fun !
Click to expand...
Click to collapse
Agreed. Thanks.
bootloop- softbrick- battery might be bad too, had that happen- replaced battery bootloop stopped.
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 :"(
I need these files please if somebody can share:
- modemst1 - modemst2 - fsg
Due to a kake ROM now I have corrupted my EFS partition and need those files to bring alive my device. Please help.
I have found MEE7 files in the web but I guess don't have to use on my phone.
Please, somebody with MEG7 can help me? I will be very glad to buy him a beer.
Hey there! I'm not currently at home now, but I can give you a direct link to NEGMIFA Rom(for Global Version phones), you can extract files you need by yourself.
Download_V9.5.11.0.NEGMIFA (as you can see, its an old version)
OR you can download_fastboot_ROM, and flash it with MiFlashTool, it should solve your problems.
Have a nice day.
P.S. If you cant download something by any reason, I'll make a mirror on googledrive or other filehost in an hour or two when I get at home.
I read somewhere that modemst1 and modemst2 contain IMEI so the rom doesn't have those files.
Fsg is also related to IMEI
Well, as far as I understand your phone not working at all, correct me if I wrong. So my algorithm to make it work is to flash it first(fastboot), doesnt matter with or without your IMEI(I think it'll be 0000), then you can search on xda or whatever, there was a bunch of threads with IMEI "problems", I'm sure you can find the right one.
Have a nice day.
Dunaldo said:
Well, as far as I understand your phone not working at all, correct me if I wrong. So my algorithm to make it work is to flash it first(fastboot), doesnt matter with or without your IMEI(I think it'll be 0000), then you can search on xda or whatever, there was a bunch of threads with IMEI "problems", I'm sure you can find the right one.
Have a nice day.
Click to expand...
Click to collapse
Hi Dunaldo, thanks for your time.
Currently my phone is working on official miui 10 developer rom, it was bricked until I could open the bootloader and install twrp.
Now, the problems I have are:
1.- Baseband "UNKNOW"
2.- When I digit *#06# on the dialer: "UNABLE TO GET IMEI"
So I was reading a lot in the forums, and ,my conclusion is: I have corrupted the EFS partition or probably I lost it, then I need first to solve the "baseband" problem, for that I need the modemst1 - modemst2 - fsg files of my exactly device model and then I can get back mi unique IMEI.
By the way do you have the MEG7 model?
And thanks for your suggestion about flashing fastboot rom, I will try once more, don't think will resolve the efs problem but I'll try anyway.
I have the same problem & i have used the files ur looking for but everytime i restart the phone my baseband again becomes unknown ?? if u want i can give u the file link tomorrow but its no use
Search Qcn file in google for your model . restore it using QPST and write your imei thats all tested MEI7 works perfectly
Any solution?
Heros King said:
I have the same problem & i have used the files ur looking for but everytime i restart the phone my baseband again becomes unknown if u want i can give u the file link tomorrow but its no use
Click to expand...
Click to collapse
Hi,heros
Did u find a solution for this problem?
I tried qpst and qfil and imei is restored but if i restart again ,baseband become unkown again.
If u find anything please help me out i've been stuck in this for almost 3 months
download QualcommIMEIRebuilder and replace yuore ime and inject in qcn file. and use qcfire flash qcn file.
thanks
Dunaldo said:
Hey there! I'm not currently at home now, but I can give you a direct link to NEGMIFA Rom(for Global Version phones), you can extract files you need by yourself.
Download_V9.5.11.0.NEGMIFA (as you can see, its an old version)
OR you can download_fastboot_ROM, and flash it with MiFlashTool, it should solve your problems.
Have a nice day.
P.S. If you cant download something by any reason, I'll make a mirror on googledrive or other filehost in an hour or two when I get at home.
Click to expand...
Click to collapse
thank you . you save my device
mansoor_hana said:
thanks
thank you . you save my device
Click to expand...
Click to collapse
Hey there! I hope you are doing well. Could you please tell me the process? I am be so glad if I can recover this phone. I have similar issues like you.
After unlock, i always do a full backup of all block partitions. It saves many issues
I flash rom my V30 i checked ChipErase in LGUP now my phone IMEI is 0 and empty Serial number (SN) ? I remember my IMEI and SN but i can write it. Please helpme write it to phone !
lehuyla said:
I flash rom my V30 i checked ChipErase in LGUP now my phone IMEI is 0 and empty Serial number (SN) ? I remember my IMEI and SN but i can write it. Please helpme write it to phone !
Click to expand...
Click to collapse
Why did you use Chip Erase? That's what Chip Erase does. It wipes out IMEI. In none on the Instructions for WTF or Frankenstein does it say to use Chip Erase on LGUP.
You'll have to Google how to do that. On XDA we can't talk about how to change IMEI.
ChazzMatt said:
Why did you use Chip Erase? That's what Chip Erase does. It wipes out IMEI. In none on the Instructions for WTF or Frankenstein does it say to use Chip Erase on LGUP.
You'll have to Google how to do that. On XDA we can't talk about how to change IMEI.
Click to expand...
Click to collapse
i already make chip erase 2 time but the IMEI
stay the same no problem
v300s
seloka180 said:
i already make chip erase 2 time but the IMEI
stay the same no problem
v300s
Click to expand...
Click to collapse
You're crazy or very lucky. Chip Erase WILL delete IMEI. That is what it does.
Straight from the manual:
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
All I know is every one who reports they used chip erase in the Frankenstein thread wiped their IMEI. It's not part of ANY instructions in this forum, so any one who does it in on their own.
Here's the remainder of the explanation:
REFURBISH： You will lost all user data（KDZ or TOT）
2) UPGRADE: Keep data and update your phone（KDZ or TOT）
Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0. (Such as LG H345, LG MS345)
4) PARTITION DL：flash the single Parition or selected paritions onto your phone.
This feature can solve “unkown model” issues. This feature can be used to bypass google frp by flashing specific tot firmware.
5) DUMP：Dump all paritions of your phone as backup.,
AT&T and Spring LG phone users who may need this feature to dump the firmware from a working phone as back up and use Patition DL to restore phones.
6) FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extention.
Click to expand...
Click to collapse
try restore modem image via partition backup restore if you don't have one, try to pull from other V30 or other lg phone you have. Don't expect your phone will be normal as before, it's just some experiment that I suggest since you don't have any answer yet.
If you have a twrp EFS backup use that to restore. If not then you likely won't be able to restore it
https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2 try this.
Make sure you still have the box for legit imei.
and instead of 815, replace with your phone model number e.g 930, 931, or 932...
immns said:
https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2 try this.
Make sure you still have the box for legit imei.
and instead of 815, replace with your phone model number e.g 930, 931, or 932...
Click to expand...
Click to collapse
this is the program that I messed up my device with it (hard brick) after i restore edited efs partition .
it cost me about 30 $ to boot it with medusa box in repair shop.
So I became not afraid to break it so much that I did chiperase several times and did not even lose Imei.
seloka180 said:
this is the program that I messed up my device with it (hard brick) after i restore edited efs partition .
it cost me about 30 $ to boot it with medusa box in repair shop.
So I became not afraid to break it so much that I did chiperase several times and did not even lose Imei.
Click to expand...
Click to collapse
Please, no one else do that. You will lose IMEI. Only this one person says they have not lost IMEI using Chip Erase in LGUP, especially our Dev Patched LGUP.
ChazzMatt said:
Please, no one else do that. You will lose IMEI. Only this one person says they have not lost IMEI using Chip Erase in LGUP, especially our Dev Patched LGUP.
Click to expand...
Click to collapse
maybe because my device is repaired ?
I think I lost IMEI using one of the TWRP version switching to another LS998. My backup of the first was on a different TWRP version I didn't recognize the feature/version difference. So my old device backup of everything didn't have the same partitions as the new phone TWRP was capable. I wiped everything on the new device and restored everything SMH... Everything worked well except I went ahead and erased data because encryption. But later when I was checking for Gpay I realized my IMEI was 0. Lame. Obviously I still have the IMEI I even double checked it against the numbers captured by Android Find Device (not everyone knows that's there) but no way to restore it it seems.
Now I have a terrorist phone, as they call it, I guess. Anyway everything still works etc coming back from airplane mode takes a restart most times, and Gpay contactless payments cards stopped adding. FYI I guess for others. Still rocking my V30. Like my neighbor Chazmatt I might just buy another one lol one day and keep this one as the family backup. Otherwise I'm still using it full time.
2 day search Google, I repaired my phone imei but SN still emplty, i used Kingtool software. Every one can fix it if lose imei !
https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2
Just for info: I have used the qualcomm nv tools from above (and set the port check test) and it worked for me!
Now I got my IMEI back!!! yipiieh
ChazzMatt said:
Please, no one else do that. You will lose IMEI. Only this one person says they have not lost IMEI using Chip Erase in LGUP, especially our Dev Patched LGUP.
Click to expand...
Click to collapse
lg g8 h870ds done the same and lost IMEI, any one can help?
vincentset said:
lg g8 h870ds done the same and lost IMEI, any one can help?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2
HueyT said:
https://forum.xda-developers.com/showpost.php?p=73489308&postcount=2
Click to expand...
Click to collapse
hey it says your phone is not rooted, so what can I do?
vincentset said:
hey it says your phone is not rooted, so what can I do?
Click to expand...
Click to collapse
Can't fix anything without rooting phone first
I did exactly the same thing my fix came with looking in the hidden menu *#546368#*998#
stinka318 said:
I did exactly the same thing my fix came with looking in the hidden menu *#546368#*998#
Click to expand...
Click to collapse
Elaborate:laugh:
HueyT said:
Elaborate:laugh:
Click to expand...
Click to collapse
It depends on what model you have on the hidden menu *#546368#* then the number of your model then # go to sev menu look for mid in there you can put original imei number in if know or geniate a new one......