Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
The Marionette said:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
Click to expand...
Click to collapse
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
hypafly said:
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
Click to expand...
Click to collapse
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
The Marionette said:
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
Click to expand...
Click to collapse
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
hypafly said:
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
Click to expand...
Click to collapse
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
So sorry to hear this.
My Moto Z has the WiFi bug too. But Bluetooth works though. It's very annoying because I've tried various fixes and different custom roms which didn't fix the problem. Maybe it's hardware? I wouldn't know. But I'm managing it for now until I get another phone.
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
How to Fix EFS over ADB
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, selectAdvanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
Edit: Those using twrp may experience efs restoration issues.
While creating the backup of EFS, you will end up with:
efs1.emmc.win (modemst1 partition raw data)
efs2.emmc.win (modemst2 partition raw data)
When restoring this EFS backup, what happened was the file name was not updated for restore, and you ended up with:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs1.emmc.win to modemst2
It should have been:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs2.emmc.win to modemst2
Twrp issue, the steps above will restore your devices.
Click to expand...
Click to collapse
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
eLaDiio said:
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
Click to expand...
Click to collapse
I appreciate the help but it sadly didn't fix anything. :/
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
eLaDiio said:
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
Click to expand...
Click to collapse
I have access to everything, everything besides the wifi, bluetooth and sim functions works.
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
eLaDiio said:
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
Click to expand...
Click to collapse
I't not a hard brick, the phone boots. Wifi, Bluetooth and SIM functions are the only things that are dead. xD
Sorry, I expressed myself badly, what I wanted to say is that your case is a strange situation, by the way, I have a full backup of my phone and if you want, I can share it so you can try flashing it and see if you can recover the wifi, although I think it could end up in a hard brick so it is risky to try it. Tell me if you're interested in flashing my backup
Related
Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
NVME
manager77 said:
Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
Click to expand...
Click to collapse
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
revjamescarver said:
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
Click to expand...
Click to collapse
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
Click to expand...
Click to collapse
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
ante0 said:
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
Click to expand...
Click to collapse
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
manager77 said:
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
Click to expand...
Click to collapse
Yep, I know that. But it didn't work on, for example, C432B145 either which was Xloader 01. So it was patched before the new bootloader was introduced
It may have the same NVME/modems. I flashed NV partitions from a BLA-L09 and mine is a L29. After this it turned into L09, and gained the IMEI/IMEI2 and serial of the donor phone. This was easily fixable in HCU though... But it's up to you. If you were up to no good it should only block the imei/imei2 on the network you use the phone on. And besides, I will probably switch to another brand soon. It seems Huawei patched something else now in latest Pie for C432 so you can't boot with a custom kernel (Built directly from their source without modifications, tried both COL and BKL source). It was fine on the build prior to this new one. I like disabling most of their kernel logging and **** which they seem to need for some reason. Can't disable all as kernel won't build then and I'm not in the mood of trying to completely remove it
Going to test signing it if avb is causing problems, it hasn't before but you never know with Huawei...
In fastboot it shows the info that's in OEMINFO. In booted mode it loads the info from modem.
But I will send you a pm in a bit.
NV partitions
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol
Click to expand...
Click to collapse
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
revjamescarver said:
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
Click to expand...
Click to collapse
"edit the information in the "donated" partition "..... where is that?
manager77 said:
"edit the information in the "donated" partition "..... where is that?
Click to expand...
Click to collapse
It's encrypted. Or should be at least. Not sure if serial is
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
geogsm_1 said:
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
Click to expand...
Click to collapse
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
manager77 said:
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
Click to expand...
Click to collapse
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
ante0 said:
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
Click to expand...
Click to collapse
My phone works in all modes: normal, fastboot, erecovery, recovery. Only problem is 0000000 imei and no services
flash via fastboot then factory reset, it work for me.
code : fastboot flash modemnvm_system modemnvm_system.img
My phone is stuck in a TWRP bootloop, meaning it doesn't boot to Android but it goes back to TWRP (It actually happened with the phone being in my pocket). I've tried restoring different backups, but none of them have any effect booting back to normal. I'm travelling at the moment so I don't have access to my computer to attempt restoring using SP Flash Tools. Any one have any ideas?
David C.
mantarkus said:
My phone is stuck in a TWRP bootloop, meaning it doesn't boot to Android but it goes back to TWRP (It actually happened with the phone being in my pocket). I've tried restoring different backups, but none of them have any effect booting back to normal. I'm travelling at the moment so I don't have access to my computer to attempt restoring using SP Flash Tools. Any one have any ideas?
David C.
Click to expand...
Click to collapse
Possibly it was from an ota update. And twrp is failing to do ota. But the command to install ota is not cleared, so it keeps trying.
If that is the case , then the solution from other mtk based devices I have had , is to clear the /misc partiton
Can be done from terminal in twrp.
I added the option to wipe /misc partition in the ported twrp I am working on. but have not tested that out.
In your case because you cannot boot to system, you cannot download it and try. So need to use first option and clear /misc with dd commands in the terminal window.
Do you want or need instruction on doing that?
If that is the problem this line of code entered into the twrp terminal window should fix it
Code:
dd if=/dev/zero of=/dev/block/platform/bootdevice/by-name/para count=1 bs=32
mrmazak said:
Possibly it was from an ota update. And twrp is failing to do ota. But the command to install ota is not cleared, so it keeps trying.
If that is the case , then the solution from other mtk based devices I have had , is to clear the /misc partiton......
Click to expand...
Click to collapse
Dude you are a life saver, I used the command line, rebooted and BAM!! back to normal. I checked the Update section and it did have one update pending, I deleted it just in case. Like I said I'm traveling for work and this left me incommunicado. Thanks again, let me know if I can buy you a drink or a cup of coffee ?
mantarkus said:
Dude you are a life saver, I used the command line, rebooted and BAM!! back to normal. I checked the Update section and it did have one update pending, I deleted it just in case. Like I said I'm traveling for work and this left me incommunicado. Thanks again, let me know if I can buy you a drink or a cup of coffee
Click to expand...
Click to collapse
Yes, best to remove the update app, or block it at least. because it will keep trying to do its update.
@mantarkus
I made a simple twrp flash install package that disables the ota apk by renaming it. This will prevent that type of problem in future. Of course You will not be able to automaticly chec for OTA, but as you found out, that would cause bootloop anyway.
look at thread here for file
https://forum.xda-developers.com/showpost.php?p=79644458&postcount=3
mrmazak said:
@mantarkus
I made a simple twrp flash install package that disables the ota apk by renaming it. This will prevent that type of problem in future. Of course You will not be able to automaticly chec for OTA, but as you found out, that would cause bootloop anyway.
look at thread here for file
https://forum.xda-developers.com/showpost.php?p=79644458&postcount=3
Click to expand...
Click to collapse
Awesome, thanks!!
I suppose the process to update safely is flashing the new ROM via SP flash tools and root as before, right?
David C.
David C.
can you explain exactly step by step on what should be done i have same issue Thank you so much
Thanks!
Just wanted to say thanks for identifying this and posting the fix
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
aSaro12 said:
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
Click to expand...
Click to collapse
Resolving Persist Issues
I have through instructions within these 2 posts, I have experienced this issue and have assisted numerous people with persist issues on XDA these solutions work.
https://forum.xda-developers.com/showpost.php?p=80544709&postcount=21
https://forum.xda-developers.com/showpost.php?p=80394181&postcount=15
your problem is similar to k20 pro problem that i had as well as so many other users.
looks like you did install FDE through magisk and it messed up your phone perminently
we've been trying to figure out a fix for the lag and freeze and wiping of the memory but its been almost 3 months without any fix.
so most likely it is unfixable
don't try to mess up anything and just send your phone to service center they will replace the motherboard . its the only available fix at the moment
I got this problem sometime when using MIUI 10, I didn't see that issue for 2 weeks after updated to MIUI 11.
Persist Issue Solution
sar78mad said:
your problem is similar to k20 pro problem that i had as well as so many other users.
looks like you did install FDE through magisk and it messed up your phone permanently
we've been trying to figure out a fix for the lag and freeze and wiping of the memory but its been almost 3 months without any fix.
so most likely it is unfixable
don't try to mess up anything and just send your phone to service center they will replace the motherboard . its the only available fix at the moment
Click to expand...
Click to collapse
It's not unfixable, it can be resolved by at least 4 different methods.
I have explained how to permanently resolve this issue with extensive instructions on at least 20 to 30 threads. Including the one above. And here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
As you can see, wasted time with no thanks given.
This issue is cause by encryption, that all there is no damage whatsoever. If you saved a Twrp backup the issue can be resolved in 2 seconds by restoring persist images.
It can also be resolved by flashing persist images from a dipper images rom, then immediately signing into your MiCloud account or by flashing a fastboot rom with XiaoMiFlash ( making sure to unclick relock bootloader) then boot and sign into MiCloud.
Another way is download all the required Dipper images Rom here :
Fastboot Rom Link : dipper_global_images_9.6.27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Filesize 2.43G
Download and unpack rom from the link above , as I mentioned on the link above, unpack twice to the desktop, ( the first time decompresses into a larger rom that also needs unpacking)
Open extracted images folder and look for “persist.img” file (it should be located in “Image” folder , see my attached screen, I keep these ready if ever needed).
Copy “persist.img” file to “/sdcard/persist.img”.
Boot into TWRP, go to Advanced/Terminal
In the terminal type the following command to convert the .img file from “sparse” to “raw” format.
PHP:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
After it’s completed, type the following command in the terminal:
PHP:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
After the flashing is completed, you can reboot into the system and start using your phone.
The next method is posted above, its an older method that uses the Kitchen app
Ideally you want the base firmware to be the same as the rom. but its not absolutely necessary, once you have flashed the persist image, immediately install a Miui Rom and sign into your account, once you are on the main desktop, reboot to Twrp and make a full backup, then copy it to your PC.
Make sure that the backup includes the persist images, modem, efs etc. As I said a full backup.
This backup will give you the peace of mind knowing, that you will never need to repeat the steps above again.
tsongming said:
Resolving Persist Issues
I have through instructions within these 2 posts, I have experienced this issue and have assisted numerous people with persist issues on XDA these solutions work.
https://forum.xda-developers.com/showpost.php?p=80544709&postcount=21
https://forum.xda-developers.com/showpost.php?p=80394181&postcount=15
Click to expand...
Click to collapse
I've seen many Xiaomi EU users facing this problem. Do you know why? After they fix persist partion, it doesn't stay for long. After few days, it again gets deleted.
alone_in_dark said:
I've seen many Xiaomi EU users facing this problem. Do you know why? After they fix persist partion, it doesn't stay for long. After few days, it again gets deleted.
Click to expand...
Click to collapse
I think it's related to dm-verity and magisk updates. I plan to make a post about it after I have researched it further and can provide sourced proof.
tsongming said:
I think it's related to dm-verity and magisk updates. I plan to make a post about it after I have researched it further and can provide sourced proof.
Click to expand...
Click to collapse
Well there are around 60 k20 pro users who got their phones useless after installing an old version of FDE (a magisk module), and no , just flashing persist wont fix the problem, so feel free to try to help us find a fix by joining to our telegram group and im sure that all 60 users will donate you alot of money if you find a permanent fix
link to telegram group : https://t.me/whateverk20pro
aSaro12 said:
Hi to all, I wrote here after trying everything from a long time. I explain better :
Sometimes, randomly, my phone mess up with the various application and give me some heavy lag and freeze, he remove some of my personal data (sometimes whatsapp files, sometimes other files, randomly) after that it stuck with a black screen or some similar and if I try to restart he stuck at the boot logo. The first time that this happened I spent a lot of time for understand what was to do this problem and after some trying I noted that this problem coincided with an error in twrp about the "persist partition" (something like unable to mount or read persist partition). So searching around the various forum I understand that I have to flash a "partition.img" for resolve the problem and that is what I do. It apparently solved the problem but my phone continue randomly to make this problem, It seems that the more time passes, the more often it will do this problem. I read that can be a memory chip problem and than the only solution is to send to the assistance and make them to resolve this. Someone of you have the same problem ? And how you managed to solve this ?
Click to expand...
Click to collapse
You speak me from the soul. I had this problem also already 3-4 times and it is 1:1 the same procedure that happens for me too. I have no clue what it is. My /data Partition does get ****ed up sometimes too
---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------
tsongming said:
It's not unfixable, it can be resolved by at least 4 different methods.
I have explained how to permanently resolve this issue with extensive instructions on at least 20 to 30 threads. Including the one above. And here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
As you can see, wasted time with no thanks given.
This issue is cause by encryption, that all there is no damage whatsoever. If you saved a Twrp backup the issue can be resolved in 2 seconds by restoring persist images.
It can also be resolved by flashing persist images from a dipper images rom, then immediately signing into your MiCloud account or by flashing a fastboot rom with XiaoMiFlash ( making sure to unclick relock bootloader) then boot and sign into MiCloud.
Another way is download all the required Dipper images Rom here :
Fastboot Rom Link : dipper_global_images_9.6.27_20190627.0000.00_9.0_global_30e0fc22ef.tgz
Filesize 2.43G
Download and unpack rom from the link above , as I mentioned on the link above, unpack twice to the desktop, ( the first time decompresses into a larger rom that also needs unpacking)
Open extracted images folder and look for “persist.img” file (it should be located in “Image” folder , see my attached screen, I keep these ready if ever needed).
Copy “persist.img” file to “/sdcard/persist.img”.
Boot into TWRP, go to Advanced/Terminal
In the terminal type the following command to convert the .img file from “sparse” to “raw” format.
PHP:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
After it’s completed, type the following command in the terminal:
PHP:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
After the flashing is completed, you can reboot into the system and start using your phone.
The next method is posted above, its an older method that uses the Kitchen app
Ideally you want the base firmware to be the same as the rom. but its not absolutely necessary, once you have flashed the persist image, immediately install a Miui Rom and sign into your account, once you are on the main desktop, reboot to Twrp and make a full backup, then copy it to your PC.
Make sure that the backup includes the persist images, modem, efs etc. As I said a full backup.
This backup will give you the peace of mind knowing, that you will never need to repeat the steps above again.
Click to expand...
Click to collapse
That it is a encryption problem, i thought already before. Are you sure that signing into MiCloud fixes this problem? it can be ofc that xiaomi added such a system, but I have no clue.
NightScap3 said:
You speak me from the soul. I had this problem also already 3-4 times and it is 1:1 the same procedure that happens for me too. I have no clue what it is. My /data Partition does get ****ed up sometimes too
---------- Post added at 10:59 PM ---------- Previous post was at 10:53 PM ----------
That it is a encryption problem, i thought already before. Are you sure that signing into MiCloud fixes this problem? it can be ofc that xiaomi added such a system, but I have no clue.
Click to expand...
Click to collapse
Signing in does fix it.....sometimes,
Other times the solution is the adb fix, which usually always works.
However, the easiest fix of all, is restoring persist from a Twrp backup, But it has to be your persist backup, flashing someone else's apparently makes matters worse.
sar78mad said:
Well there are around 60 k20 pro users who got their phones useless after installing an old version of FDE (a magisk module), and no , just flashing persist wont fix the problem, so feel free to try to help us find a fix by joining to our telegram group and im sure that all 60 users will donate you alot of money if you find a permanent fix
link to telegram group : https://t.me/whateverk20pro
Click to expand...
Click to collapse
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
However, I made a post with additional options here : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5.
I just mentioned this to someone else, do not flash someone else's persist backup, that will work temporarily and then makes matter's much worse.
On the Mi8 there are only a few versions of Twrp that will allow you to backup and restore that persist image alone. If Orange Fox is available on your device try using it. See attached image
Edit one last thing
If attempting to use the persist image extraction reflash method, the image must come from a fastboot "images' rom
tsongming said:
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
However, I made a post with additional options here : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5.
I just mentioned this to someone else, do not flash someone else's persist backup, that will work temporarily and then makes matter's much worse.
On the Mi8 there are only a few versions of Twrp that will allow you to backup and restore that persist image alone. If Orange Fox is available on your device try using it. See attached image
Click to expand...
Click to collapse
My MI 8 works since 2 days without a Problem after flashing the persist.img that i extracted from the factory image in Orange Fox terminal like explained in your posts.
Duplicate Post
---------- Post added at 02:18 AM ---------- Previous post was at 01:59 AM ----------
apf95 said:
My MI 8 works since 2 days without a Problem after flashing the persist.img that i extracted from the factory image in Orange Fox terminal like explained in your posts.
Click to expand...
Click to collapse
Yes, those steps definitely work for those of us.with Mi8's
It should work for them too as long as the use the correct images.
tsongming said:
I have had this issue myself several times and you are right simply flashing persist doesn't always fix it.
Click to expand...
Click to collapse
Did you have this problem before using Xiaomi EU rom? I am on stock rom and planning to go to EU. But a lot of users in EU forum are also facing persist problem. I am using Mi 8 for almost 1 year with Global Beta/Stable rom. Nevar faced this issue.
Maybe it's caused by TWRP or EU rom?
alone_in_dark said:
Did you have this problem before using Xiaomi EU rom? I am on stock rom and planning to go to EU. But a lot of users in EU forum are also facing persist problem. I am using Mi 8 for almost 1 year with Global Beta/Stable rom. Nevar faced this issue.
Maybe it's caused by TWRP or EU rom?
Click to expand...
Click to collapse
It's not caused by the EU rom, the EU rom is really nothing more than official Beta Miui ( Chinese version, which is 3 to 4 months ahead of the Global version) So beta Miui with Google services added and useless bloatware and ads removed.
There have been many cases of people experiencing these issues on AOSP roms as well. For example, the many reports of WIFI, Data, Cellular Services, BT not working etc.
The issue is a permissions conflict, that is mostly likely caused by continuous flashing of Root and Dm-Verity. Albeit incorrectly.
If you have Twrp and no root then flash Dm-Verity. If you plan on using Root then don't use DM-Verity, it's not needed.
When I stopped flashing DM-Verity is when I stopped experiencing issues. But as I mentioned if you don't want root ,and you definitely want TWRP then you must flash DM-Verity otherwise TWRP will be overwritten when using a stock based rom.
@alone_in_dark
Edit: If you have been using stock the whole time, you will be blown away with how improved the latest Android 10 of Miui 11 is, check it out, its awesome.
tsongming said:
Signing in does fix it.....sometimes,
Other times the solution is the adb fix, which usually always works.
However, the easiest fix of all, is restoring persist from a Twrp backup, But it has to be your persist backup, flashing someone else's apparently makes matters worse.
Click to expand...
Click to collapse
Are you talking from permanent fixes?
Which adb method? Do you mean the over TWRP Terminal?
I will btw flash now miui after I flashed persist with ur method and then flash xposed to see if my /persist breaks
NightScap3 said:
Are you talking from permanent fixes?
Which adb method? Do you mean the over TWRP Terminal?
I will btw flash now miui after I flashed persist with ur method and then flash xposed to see if my /persist breaks
Click to expand...
Click to collapse
Permanent unless you mess it up again, as I described on this thread. The Adb steps are listed on this post : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5
tsongming said:
Permanent unless you mess it up again, as I described on this thread. The Adb steps are listed on this post : https://forum.xda-developers.com/showpost.php?p=80623541&postcount=5
Click to expand...
Click to collapse
Do you know why my /data partition gets broken too when this /persist mess up from magisk happens?
NightScap3 said:
Do you know why my /data partition gets broken too when this /persist mess up from magisk happens?
Click to expand...
Click to collapse
I believe that I do.
I choose to not encrypt my phone. However, certain roms, especially experimental may encrypt your data anyway. Back in early August I kept having bootloops and persist issues.
I stopped having issues when I went back to the flashing steps that I used with my previous phone. ( Rarely if ever using Dm_verity)
Edit: Comment below concerns Stock based Rom
Dm-Verity is needed if you want to use a custom recovery such TWRP, and you do not want or need Root.
If you are planning to root the device, then do not flash Dm-Verity. Magisk already has a function which takes care of Dm-Verity and Encryption. So there is no need to flash Dm-Verity.
The problem is that too many people think that Dm-verity is needed, along with Magisk and with every update, it's not unless you are not rooted and in most cases if you are rooted Magisk will check the the boot to ensure that it is still rooted. So flashing Magisk is not always needed ethier. As an extra precaution, I remove all passwords, pattern looks, and face unlocks prior to updating a Rom. I plan to make a post about Dm-Verity soon but will not have time to get to it until Monday or Tuesday.
I hope this helps.
tsongming said:
I believe that I do.
I stopped having issues when I went back to the flashing steps that I used with my previous phone. ( Rarely if ever using Dm_verity)
Dm-Verity is needed if you want to use a custom recovery such TWRP, and you do not want or need Root.
If you are planning to root the device, then do not flash Dm-Verity. Magisk already has a function which takes care of Dm-Verity and Encryption. So there is no need to flash Dm-Verity.
Click to expand...
Click to collapse
I want TWRP only (no root). So, Do I've to flash DM-Verity each time I update rom? Will flashing DM-Verity cause problem? And can you please share your steps of flashing ROM?
Thanks
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?