Related
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happened before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realized I had no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happened. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and your IMEI should be back!
drfr said:
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happend before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realised I have no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happend. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messsages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and you´re IMEI should be back!
Click to expand...
Click to collapse
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
deej_roamer said:
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
Click to expand...
Click to collapse
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
drfr said:
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
Click to expand...
Click to collapse
Oh I am not criticising your work, I encourage it! I just pointed my point of view!
Added to FAQ (in the lost IMEI section), i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
this is cool you could recover it by flashing stock, so i added your story to FAQ in case it happens again to anyone
Good to know.
matmutant said:
... i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
Click to expand...
Click to collapse
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
drfr said:
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
Click to expand...
Click to collapse
Gonna try this if I can find some time, even if I don't realy got any hope left after flashing the hell out of this phone..
Didn't work. I used erase all back in the days..
RestlessScreams said:
Didn't work. I used erase all back in the days..
Click to expand...
Click to collapse
Same here, tried with 4.3 and 4.4 german (my phone is)
used erase all back in the days still can see imei on fastboot getvar, imei 0 on mobile.
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
thanks mate for your effort!
Sadly fastboot oem writeimei is unsupported in moto g
---------- Post added at 11:26 AM ---------- Previous post was at 11:12 AM ----------
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
about where is SHOULD be, when u do fastboot erase all it deletes those:
modemst1
modemst2
hob
dhob
fsg
fsc
clogo
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Lost IMEI
japoina92 said:
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Click to expand...
Click to collapse
The same situation... Can somebody share the pds folder? I assume that it contains imei.
ol_st said:
The same situation... Can somebody share the pds folder? I assume that it contains imei.
Click to expand...
Click to collapse
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
recover imei moto g
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
BUMP: any news on this guys?
Nothing..
killerBRs said:
Nothing..
Click to expand...
Click to collapse
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Younboy69 said:
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
Click to expand...
Click to collapse
tehygav said:
BUMP: any news on this guys?
Click to expand...
Click to collapse
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
moto
sebastiandg7 said:
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
Click to expand...
Click to collapse
tengo un moto g hay alguna forma de restaurar imei alguna box que se dedique al cambio de imei?
First things first, I'm sorry for opening another thread on this but I feel the other ones weren't headed exactly in the correct direction.
A little background:
I was trying to downgrade my XT1541 to Lollipop since 6.0 was really bad and I got frustrated and used
Code:
fastboot erase all
The result was I erased my IMEI and I haven't been able to connect to a network carrier since. The problem can be solved by re-writing my IMEI but that's the difficult part.
What I gathered so far is I can use QPST, backup QCN, go into HEX and change IMEI there, then restore the QCN back to my device. The problem is I can't locate the IMEI in my QCN since my IMEI is now simply 0.
So in all, could someone make a backup of THEIR QCN and send it to me? I would flash it to my XT1541, locate the IMEI (since now I would know what I'm looking for), then change it back to my own.
Does that sound like something that could work? Can anyone help?
UPDATE1: Noone sent me their QCN however I did try to restore the one I backup up (which still has an IMEI=0). QPST Software Download reports
Received an invalid command from the phone.
Click to expand...
Click to collapse
I tried using Qualcomm NV Tools (from EFS Professional), which reads all the information correctly, however when attempting to write the following appears
Cannot Write: NV_UE_IMEI_I
Error: NV_ERR_BAD_SECURITY_STATE
Click to expand...
Click to collapse
So getting another QCN won't help as it seems that I can't write the IMEI (qcn) back to the device...
There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.
acejavelin said:
There are only two possibilities of fixing this... a 50/50 chance that a full factory flash will restore it (don't know how, but it does sometimes). If that doesn't work, then you need to send it to Moto for repair.
Click to expand...
Click to collapse
I have already tried with a full stock rom flash which didnt work...
zeusalmighty said:
I have already tried with a full stock rom flash which didnt work...
Click to expand...
Click to collapse
Well, unfortunately that leaves option 2... or turn it into a media play and buy a new phone.
Funny how `fastboot erase all` causes such a pain for some and not others... but once your IMEI is gone, there isn't much you can do. Moto kinda screwed the pooch on that one.
Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.
Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547
Henriquefeira said:
Try this >http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970/post61725547#post61725547
Click to expand...
Click to collapse
Thanks but the dd commands wont work since it appears the folder structure is different on the XT1541...any help?
Forever Alone said:
Hello, did u try Xposed IMEI changer? Maybe that will be a native fix for this issue.
Click to expand...
Click to collapse
Hey, couldn't get any results with the xposed module
Just one bump
One last effort, not a bump. If anyone can direct me to commercial services for repairing the IMEI i'd be very greatful. Official Motorola Service wont repair it for me btw.
Thanks
try this guys
http://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362#post68445534
If you have an unlocked bootloader, it can be pretty easy to brick your phone. If you wipe the wrong partitions, you can lose your EFS and your radio will no longer work.
To prevent against this, my suggestion is that everyone take and keep a backup. Here's how.
The EFS Partitions:
On the Mix 2S there are three partitions you should back up. modemst1, modemst2, and fsg.
modemst1 can be found at /dev/block/sdf6
modemst2 can be found at /dev/block/sdf7
fsg can be found at /dev/block/sde36
How to back them up
First, get into TWRP. TWRP and instructions for flashing it are here:
https://forum.xda-developers.com/xi...how-to-buy-unlock-root-twrp-recovery-t3786868
Once TWRP has loaded up, connect the USB cable from your phone to your computer, and, assuming you have installed ADB already, get an adb shell by going to command line and typing:
Code:
adb shell
From there, let's backup all three partitions
Code:
dd if=/dev/block/sdf6 of=/sdcard/sdf6.img
dd if=/dev/block/sdf7 of=/sdcard/sdf7.img
dd if=/dev/block/sde36 of=/sdcard/sde36.img
exit
Now, you can use adb to pull the files to your computer:
Code:
adb pull /sdcard/sdf6.img
adb pull /sdcard/sdf7.img
adb pull /sdcard/sde36.img
Keep these backups in a safe place!
Research regarding this
For those interesting in research in this, I have found the following:
• If you wipe modemst1, modemst2, and fsg your IMEI and all NV data on the modem is lost, and the radio does not work.
• You can make a backup with QPST and restore it, and it will restore your IMEI numbers, but the radio still will not work. This is something I'd like to get working very much.
• I am still trying to learn more about this, so if anyone would like to help, please send me backups of sdf6, sdf7, and sde36 of the Mi Mix 2S and let me know which spec you have. I think it may be possible to convert the limited LTE band version to the full LTE band version for example.
Thanks for starting this topic. It's really important to backup EFS...
The guide would be complete if someone really tried to backup and then restore with this method
underlines said:
Thanks for starting this topic. It's really important to backup EFS...
The guide would be complete if someone really tried to backup and then restore with this method
Click to expand...
Click to collapse
If OP doesn't mind, you could add a link to this thread on your Guide thread as well.
underlines said:
Thanks for starting this topic. It's really important to backup EFS...
The guide would be complete if someone really tried to backup and then restore with this method
Click to expand...
Click to collapse
I already did back up and restore with this method, several times. It works.
hi miuiers ;
EFS partitions backup not enough for some new models for restore QCN or EFS ..
therefore my advice for EFS backup using some box or dongle UMT , BST etc.
micro77 said:
hi miuiers ;
EFS partitions backup not enough for some new models for restore QCN or EFS ..
therefore my advice for EFS backup using some box or dongle UMT , BST etc.
Click to expand...
Click to collapse
They are not trying to edit or change the imei you wiseguy mikrop, no box needed if you have the brain, which you don't have
micro77 said:
hi miuiers ;
EFS partitions backup not enough for some new models for restore QCN or EFS ..
therefore my advice for EFS backup using some box or dongle UMT , BST etc.
Click to expand...
Click to collapse
I don't think there is anything a box does which QCN doesn't do. If it's in diag mode, all it can do is try to read the nv items and restore them.
As stated earlier, restoring the nv items directly from a QCN or otherwise in diag mode, you can't get the phone to connect to network after this. What would using a box make different about this? I don't think there are any boxes yet which support Mi Mix 2S, but if there are, let me know.
I've already experimented with some dongles (MRT for example), but I get same result as with QPST.
os_man said:
They are not trying to edit or change the imei you wiseguy mikrop, no box needed if you have the brain, which you don't have
Click to expand...
Click to collapse
hosht :/
what about oneplus or oppo ?
mister brain ?
READ AGAIN HERE ONE MORE TIME ;
@ duraaraa
"You can make a backup with QPST and restore it, and it will restore your IMEI numbers, "
"but the radio still will not work"
OR HERE;
"you can't get the phone to connect to network after this."
did you get it right now ?
---------- Post added at 01:45 AM ---------- Previous post was at 01:12 AM ----------
duraaraa said:
I don't think there is anything a box does which QCN doesn't do. If it's in diag mode, all it can do is try to read the nv items and restore them.
As stated earlier, restoring the nv items directly from a QCN or otherwise in diag mode, you can't get the phone to connect to network after this. What would using a box make different about this? I don't think there are any boxes yet which support Mi Mix 2S, but if there are, let me know.
I've already experimented with some dongles (MRT for example), but I get same result as with QPST.
Click to expand...
Click to collapse
yes you are right no box solution mix2s for now.
also qcn restore not enough for some new models.
but if you use box in EDL mode for backup EFS , sometimes only way for restore EFS , IMEI ,MEID etc.
its tested new model xiaomi phones.
micro77 said:
hosht :/
what about oneplus or oppo ?
mister brain ?
READ AGAIN HERE ONE MORE TIME ;
@ duraaraa
"You can make a backup with QPST and restore it, and it will restore your IMEI numbers, "
"but the radio still will not work"
OR HERE;
"you can't get the phone to connect to network after this."
did you get it right now ?
---------- Post added at 01:45 AM ---------- Previous post was at 01:12 AM ----------
yes you are right no box solution mix2s for now.
qcn restore not enough for some new models.
but if you use box in EDL mode for backup EFS , sometimes only way for restore EFS , IMEI ,MEID etc.
its tested new model xiaomi phones.
Click to expand...
Click to collapse
With unlocked bootloader, you can back up and restore efs by backing up and restoring fsg or modemst1 / modemst2 partition on Mix 2S. However if you do not have a backup of these partitions and yours end up wiped, there is no way to restore. This is what I'm hoping to solve.
duraaraa said:
With unlocked bootloader, you can back up and restore efs by backing up and restoring fsg or modemst1 / modemst2 partition on Mix 2S. However if you do not have a backup of these partitions and yours end up wiped, there is no way to restore. This is what I'm hoping to solve.
Click to expand...
Click to collapse
first dont need unlock for EFS backup or restore via box (easy way ) or coding ( little bit hard way ) .
just test point to phone for EDL and after you can backup or restore EFS , fsg or modemst1 / modemst2 partitions .
micro77 said:
first dont need unlock for EFS backup or restore via box (easy way ) or coding ( little bit hard way ) .
just test point to phone for EDL and after you can backup or restore EFS , fsg or modemst1 / modemst2 partitions .
Click to expand...
Click to collapse
I think maybe that's incorrect. It's not possible to enter EDL mode without unlocked bootloader. Also, with Mi Mix 2S, EDL mode seems to not work (for example MiFlash can't flash in EDL mode on it). But maybe I am wrong?
duraaraa said:
I think maybe that's incorrect. It's not possible to enter EDL mode without unlocked bootloader. Also, with Mi Mix 2S, EDL mode seems to not work (for example MiFlash can't flash in EDL mode on it). But maybe I am wrong?
Click to expand...
Click to collapse
no no you can enter EDL via test point , almost all snapdragon phones;
http://en.miui.com/thread-638042-1-1.html
micro77 said:
first dont need unlock for EFS backup or restore via box (easy way ) or coding ( little bit hard way ) .
just test point to phone for EDL and after you can backup or restore EFS , fsg or modemst1 / modemst2 partitions .
Click to expand...
Click to collapse
Ah, yes, that's right. I forgot about test point.
Still, there is no solution, as far as I know, unless you have a backup of the partitions when they are still valid.
Thanks so much I don't understand much and some terms are new to me but I much appreciate for the topic so I can at least save modem files.
Always learning.
So i got back up those partitions, by boot (not install) twrp v.8 through built in terminal and save it on /usb_otg.
Now if something happened with those partitions how to restore everything back?
Hi @duraaraa can u help me with my mix 2s. losts imei, baseband, network. but wifi, bluetooth is ok. can u edit those files with my imei number so i can restore using qpst or something? i can send it to u
duraaraa said:
I already did back up and restore with this method, several times. It works.
Click to expand...
Click to collapse
how to restore them plz? via recovorey or fastboot or else?
Same question how can we restore it ?
UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.
Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.
So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?
yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.
Have you tried flashing QCN file?
yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!
yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...
vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option
yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it
I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting modemst1, modemst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow modemst1 and modemst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!
c0d3f0rc37 said:
I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting memst1, memst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow memst1 and memst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!
Click to expand...
Click to collapse
So in essence you broke your device. You probably have lost fp scanner,wifi,nfc,rotation. I really don't know what to tell you other than msm your device back to stock. And you didn't back up persist . This partition is device specific. If you do get it fixed properly I'd leave it the hell alone.
You can't just delete critical partitions
So, there's no way to fix this? I can assume that the phone is wasted?
c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
Try and contact OnePlus and get a remote session. One of their techs will get you on correct MSM and get phone fixed.
c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
The persist partiton can only be fix by oneplus in factory or spending money for someone that has the hardware required to fix it.