Develop Bugs

[Q] Do I ALWAYS have to flash a new boot image when installing a rom?

Hello,
I'm coming from a HTC Desire, and when reading the guides how to install roms on the HOX, the neccesity to flash a separate boot.img for every rom via fastboot was new to me.
Is this always the case? And lets say I have a stable 4.0.4 installation and want to mess around with CM10 - I get that have to flash the CM10 boot.img before installing the ROM, but would I then also have to re-flash my old boot.img before rstoring my old nandroid backup, or is the boot image included in the backup?
Thanks aheasd for an answer,
saxelfur

i guess yes.. you have to re-flash the boot.img of the rom that you are restoring...

faiz02 said:
i guess yes.. you have to re-flash the boot.img of the rom that you are restoring...
Click to expand...
Click to collapse
Okay, thanks - so I suppose right now there is now way to restore a backup from a different rom on the go. Oh well, I should be able to live without that

saxelfur said:
Okay, thanks - so I suppose right now there is now way to restore a backup from a different rom on the go. Oh well, I should be able to live without that
Click to expand...
Click to collapse
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.

panooos said:
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.
Click to expand...
Click to collapse
Great, even better!

panooos said:
You do not have to flash the boot.img before restoring a nandroid backup...Y
ou restore everything, boot.img included.
Click to expand...
Click to collapse
Not true; if you're restoring a backup which used a different boot.img than the one you already have installed, you need to manually flash the boot.img from your nandroid backup in fastboot.
The reason we have to use fastboot to flash the boot.img is that, thanks to HTC's security policies, it is not possible to write to the boot partition from recovery. Hence when you flash a ROM the boot.img isnt written, and has to be manually flashed. This also means that when you restore a backup in recovery it is still unable to write to the boot partition, so the boot.img from your backup is not written and must also be flashed manually.

hopscotchjunkie said:
Not true; if you're restoring a backup which used a different boot.img than the one you already have installed, you need to manually flash the boot.img from your nandroid backup in fastboot.
The reason we have to use fastboot to flash the boot.img is that, thanks to HTC's security policies, it is not possible to write to the boot partition from recovery. Hence when you flash a ROM the boot.img isnt written, and has to be manually flashed. This also means that when you restore a backup in recovery it is still unable to write to the boot partition, so the boot.img from your backup is not written and must also be flashed manually.
Click to expand...
Click to collapse
Really? I once flashed a kernel and could not pass the loading screen...everything got fixed as soon as i restored my backup...

Lucky for you. But these guys are correct. The only way to flash boot is through fastboot.
Recovery restore cannot restore a boot.img
Sent from my HTC One X using xda app-developers app

panooos said:
Really? I once flashed a kernel and could not pass the loading screen...everything got fixed as soon as i restored my backup...
Click to expand...
Click to collapse
Yep. Boot partition simply isn't writable from recovery (without s-off). There's no difference between recovery trying to write a boot.img from a zip on /sdcard and recovery trying to write a boot.img from a folder on /sdcard (if there was we would just need to modify recovery to treat new flashes as restores to get around the problem).
I'm not saying it won't work if you don't; if you're switching between Sense ROMs or restoring an earlier version of the ROM you're using then there's a good chance that the ROM will still boot and run fine, but you'll be running with the kernel & ramdisk you had before the restore.

Always learning sth new... Ty
Sent from my HTC One X using xda app-developers app

Well shoot. How do I get the boot.img from the stock rom that came with it. It wasn't exactly in standard .zip format for me to extract the .img......

If you did a nandroid backup it's there in plain sight.

Resetting counter without Triangle away

Hello guys, I'm a user of Moon ROM and when I tried to upgrade to v10 .. It was upgraded successfully .. through AROMA installation I backed up EFS, It was backed up into a folder .. not a tar or IMG file, And I found out that I lost my IMEI, and I couldn't find out how to restore the " folder " EFS backup .. So I tried various ways, In the end I tried to make an IMG file of that folder by ImgBurn and then restored it using this script
I got into a FOREVER boot loop, I tried to unroot, i tried to go back to stock firmware, I tried to reflash v9 Moon ROM and v10 again, I tried everything .. Also getting failed to mount /efs in recovery.
It's just killing me and I actually lost hope
So I was wondering if there's a way to reset my counter so I can send it to warranty.
Since I can't boot up to use Triangle away, Any solution ?

Cheet0z said:
Hello guys, I'm a user of Moon ROM and when I tried to upgrade to v10 .. It was upgraded successfully .. through AROMA installation I backed up EFS, It was backed up into a folder .. not a tar or IMG file, And I found out that I lost my IMEI, and I couldn't find out how to restore the " folder " EFS backup .. So I tried various ways, In the end I tried to make an IMG file of that folder by ImgBurn and then restored it using this script
I got into a FOREVER boot loop, I tried to unroot, i tried to go back to stock firmware, I tried to reflash v9 Moon ROM and v10 again, I tried everything .. Also getting failed to mount /efs in recovery.
It's just killing me and I actually lost hope
So I was wondering if there's a way to reset my counter so I can send it to warranty.
Since I can't boot up to use Triangle away, Any solution ?
Click to expand...
Click to collapse
Sorry, but, you pretty much screwed your EFS partition by doing serious mistakes.
First of all, that script is backing up/restoring as RAW image that is taken by DD
I never tried to backup EFS using TWRP. But probably it's taking the file(s) in /EFS partition, not taking a RAW image.
So you tried to create a raw image from TWRP's EFS files using ImgBurn and restored it using DD (that script does that). Big mistake.
All you had to do was restoring EFS back using TWRP
However I think you can still restore EFS if you still have the EFS backup taken by TWRP?
If yes
Find a EFS raw image of Note 2 from somewhere (from a friend or internet...)
It has to be taken by DD (script also will work)
Then restore it using that script
Then enter into TWRP and restore your EFS which you took using TWRP before.

[email protected] said:
Sorry, but, you pretty much screwed your EFS partition by doing serious mistakes.
First of all, that script is backing up/restoring as RAW image that is taken by DD
I never tried to backup EFS using TWRP. But probably it's taking the file(s) in /EFS partition, not taking a RAW image.
So you tried to create a raw image from TWRP's EFS files using ImgBurn and restored it using DD (that script does that). Big mistake.
All you had to do was restoring EFS back using TWRP
However I think you can still restore EFS if you still have the EFS backup taken by TWRP?
If yes
Find a EFS raw image of Note 2 from somewhere (from a friend or internet...)
It has to be taken by DD (script also will work)
Then restore it using that script
Then enter into TWRP and restore your EFS which you took using TWRP before.
Click to expand...
Click to collapse
Thanks in advance, So let me get this straight .. I have to look for a EFS img backup from a friend or from internet and restore it then restore the folder backup that I took using AROMA ?
should he be using the same ROM/baseband/kernel/etc or even from my country ?

Cheet0z said:
Thanks in advance, So let me get this straight .. I have to look for a EFS img backup from a friend or from internet and restore it then restore the folder backup that I took using AROMA ?
should he be using the same ROM/baseband/kernel/etc or even from my country ?
Click to expand...
Click to collapse
As long as the device model matches like n7100, it should work. It doesn't has to be same ROM/baseband/kernel.

[email protected] said:
As long as the device model matches like n7100, it should work. It doesn't has to be same ROM/baseband/kernel.
Click to expand...
Click to collapse
Actually I don't have any friends with a Note II, And I read previously that not a lot of people would share there IMEI, so can I ask You for it please ?

Cheet0z said:
Actually I don't have any friends with a Note II, And I read previously that not a lot of people would share there IMEI, so can I ask You for it please ?
Click to expand...
Click to collapse
For the same reason, no, I won't give you mine either.

[email protected] said:
For the same reason, no, I won't give you mine either.
Click to expand...
Click to collapse
*sigh*
What to do then

Would this method work ?
I came across it while googling for an EFS backup.

Cheet0z said:
*sigh*
What to do then
Click to expand...
Click to collapse
Find a friend
Cheet0z said:
Would this method work ?
I came across it while googling for an EFS backup.
Click to expand...
Click to collapse
Your EFS partition corrupted because of your writing improper image.
That's why you can't get your EFS partition mounted.
You still need a raw image of EFS partition of Note 2, then restore your EFS backup properly.

[email protected] said:
Find a friend
Your EFS partition corrupted because of your writing improper image.
That's why you can't get your EFS partition mounted.
You still need a raw image of EFS partition of Note 2, then restore your EFS backup properly.
Click to expand...
Click to collapse
Ok a guy was nice enough and gave me his IMG backup ..
Now I'm stuck at how to restore it !
I mean I can't use the script because it needs the phone to be booted up and android debugging on.

Cheet0z said:
Ok a guy was nice enough and gave me his IMG backup ..
Now I'm stuck at how to restore it !
I mean I can't use the script because it needs the phone to be booted up and android debugging on.
Click to expand...
Click to collapse
Don't do anything. I'm going to make CWM update zip for you. I'm a bit busy right now.

Put your efs.img file into the root folder of the zip file
Then flash it via CWM or TWRP
Then restore you original EFS files

Backup IMEI or forget about it?

I wanted to get all of your opinion on backing up the IMEI.
My situation is, I had rooted last year with the s3 toolkit. 1st rom I flashed was paranoid android then now i'm always flashing Task's AOKP. I'm currently on an older release of his rom (5-21-13) and i've probably flashed it a dozen times without any problems.
My question is, should I continue flashing this rom even though I have not backed up my IMEI or EFS folder or should I flash back to stock right away then, backup IMEI/EFS and continue flashing task's rom? Are the chances high of losing IMEI even though i've flashed the same rom for at least a year now?
I have an AT&T SGH-I747 with baseband DLK3.
In addition, if I were to flash back to stock, can I just use this? http://forum.xda-developers.com/showthread.php?t=2161667
Unfortunately the download link is no longer there so would anyone have a copy?
Also, would this be the best / easiest way to backup the IMEI as of right now? http://forum.xda-developers.com/showthread.php?t=1804117
Thank you!:cyclops:

promidgetmafia said:
I wanted to get all of your opinion on backing up the IMEI.
My situation is, I had rooted last year with the s3 toolkit. 1st rom I flashed was paranoid android then now i'm always flashing Task's AOKP. I'm currently on an older release of his rom (5-21-13) and i've probably flashed it a dozen times without any problems.
My question is, should I continue flashing this rom even though I have not backed up my IMEI or EFS folder or should I flash back to stock right away then, backup IMEI/EFS and continue flashing task's rom? Are the chances high of losing IMEI even though i've flashed the same rom for at least a year now?
I have an AT&T SGH-I747 with baseband DLK3.
In addition, if I were to flash back to stock, can I just use this? http://forum.xda-developers.com/showthread.php?t=2161667
Unfortunately the download link is no longer there so would anyone have a copy?
Also, would this be the best / easiest way to backup the IMEI as of right now? http://forum.xda-developers.com/showthread.php?t=1804117
Thank you!:cyclops:
Click to expand...
Click to collapse
I don't know about backing up your IMEI but if you want to switch back to stock 4.1.1 I recommend using this instead: http://forum.xda-developers.com/showthread.php?t=2363882
It worked like a charm when I was on LK3

always have a backup... as for me i have a copy in my 2 emails, dropbox, work hdd and home hdd... fixing qualcomm imei its much easy and anyone could fix them, in exynos cpu the history its diferent...
backup it with EFSpro, even the tool have option to fix qualcomm imei... read about them, its easy...
Sent from my GT-I9500 using xda app-developers app

carlosm15 said:
always have a backup... as for me i have a copy in my 2 emails, dropbox, work hdd and home hdd... fixing qualcomm imei its much easy and anyone could fix them, in exynos cpu the history its diferent...
backup it with EFSpro, even the tool have option to fix qualcomm imei... read about them, its easy...
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately EFSpro will only let me do the option under backup on EFS Professional to backup the tz, efs, modemst1, and modemst2. Qualcomm crashes due to me currently being on AOSP. Looks like you must be on stock in order to use that. Any tools that will work for other roms besides stock?

carlosm15 said:
always have a backup... as for me i have a copy in my 2 emails, dropbox, work hdd and home hdd... fixing qualcomm imei its much easy and anyone could fix them, in exynos cpu the history its diferent...
backup it with EFSpro, even the tool have option to fix qualcomm imei... read about them, its easy...
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
AshishPyala said:
I don't know about backing up your IMEI but if you want to switch back to stock 4.1.1 I recommend using this instead: http://forum.xda-developers.com/showthread.php?t=2363882
It worked like a charm when I was on LK3
Click to expand...
Click to collapse
If I were to go back to stock it would simply be to backup the IMEI then flash back to AOSP right away. It looks like that restores stock everything (stock kernel, stock rom, and stock recovery)
I would like to keep my recovery but flash stock rom for AT&T S3 through TWRP so I can keep my recovery.

I backed up my imei because the more posts I read, the more it seemed like having a backup would be crucial if you wanted to restore and be successful.
Since that stock rom that I linked to was no longer active, I searched my old backups and found a stock CWM nandroid backup I made after I rooted. I was on TWRP so I flashed the recovery back to CWM via rom manager. Restore the stock nandroid I made then backed up my IMEI.
Switched back to TWRP and made a nandroid backup of the stock rom with twrp so I don't have to mess with recoveries in the future.
Flashed my 5-21 nandroid that was Task's AOSP then just updated to his latest 9-10 release.
All is great and I have a full NV backup.
Thank you all for the suggestions.

promidgetmafia said:
I backed up my imei because the more posts I read, the more it seemed like having a backup would be crucial if you wanted to restore and be successful.
Since that stock rom that I linked to was no longer active, I searched my old backups and found a stock CWM nandroid backup I made after I rooted. I was on TWRP so I flashed the recovery back to CWM via rom manager. Restore the stock nandroid I made then backed up my IMEI.
Switched back to TWRP and made a nandroid backup of the stock rom with twrp so I don't have to mess with recoveries in the future.
Flashed my 5-21 nandroid that was Task's AOSP then just updated to his latest 9-10 release.
All is great and I have a full NV backup.
Thank you all for the suggestions.
Click to expand...
Click to collapse
Could you walk me through on how to have a full NV backup? Also how would I restore it if I ever needed to? I wanna know just in case I ever lose my imei.

AshishPyala said:
Could you walk me through on how to have a full NV backup? Also how would I restore it if I ever needed to? I wanna know just in case I ever lose my imei.
Click to expand...
Click to collapse
Download a terminal app(root required one) then type su enter reboot nvbackup.
To restore it's su reboot nvrestore.
!!!!!!DO NOT RESTORE BEFORE YOU BACKUP!!!! You will overwrite nv with empty data possibly losing imei forever.

!
thepoetlives89 said:
Download a terminal app(root required one) then type su enter reboot nvbackup.
To restore it's su reboot nvrestore.
!!!!!!DO NOT RESTORE BEFORE YOU BACKUP!!!! You will overwrite nv with empty data possibly losing imei forever.
Click to expand...
Click to collapse
Thanks homie!

Need help to unbrick my Nexus 5X

Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!

adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.

rpalmon said:
Just press the volume down and power button at the same time. Should get you into TWRP and then transfer the file you want to install the ROM on and flash it. That should do it. Hopefully this helps.
Click to expand...
Click to collapse
I did flash the factory image from fastboot successfully without errors but it doesn't boot. Do you mean a custom rom? Im afraid that may do things worse.

adbPush said:
Hi! My first post here (and not a pleasant one).
I bricked my phone by trying to sideload the android 7 september ota update.
I had root and TWRP recovery installed and I thought it would be ok to sideload the update from TWRP thinking that will erase system and recovery. But what I faced was adb sideload to stop to about 30% on pc and the options to go back or reboot system on TWRP.
So being afraid of a brick I didn't reboot and I flashed a nandroid backup (didn't have a vendor backup). After it finished I rebooted system to find out that the phone goes up to 4 dots and reboots.
The next thing I did was to flash a factory image. I flashed both the september and august images by running flash-all.sh with success (no errors) but still the device is in bootloop.
The last thing I tried was this: http://forum.xda-developers.com/nexus-5x/help/fix-nougat-bricked-phones-n6-thread-t3449640
but made things worse and then I could reach up to Google logo. So I flashed back the factory image of Android N August and I can reach again the 4 dots.
The odd thing is that when I flash TWRP I see a supersu folder in /. Do you think it affects anything? But system, boot, cache, sdcard, recovery, vendor are formatted during flashing the factory images.
I have the 32gb model and unlocked bootloader.
This drives me crazy since it's a soft brick and I should be able to recover from this.
Any help will be much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.

sfhub said:
If you have your userdata backed up, I suggest you flash everything including letting it factory reset your userdata.
Keep in mind your nandroid backups are on userdata, so move those off the phone first.
One other thing, when you restored nandroid backup, did you use TWRP 3.0.2-1 and did you restore EFS partition? There was a bug in TWRP where it would crash your phone because it overwrote an EFS partition with the contents of another EFS partition due to incorrect filenames.
Click to expand...
Click to collapse
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?

adbPush said:
Yes i used TWRP 3.0.2-1 to restore EFS. Was the bug to that version? Is there any way to fix it?
EDIT: I downloaded and installed twrp 3.0.2-2 and when I try to restore the efs it says "efs2 no such file or directory". The previous version of twrp doesn't semm to have backed up this partition. I only find efs1 in the backup folder. @sfhub can you plz help me? How am I going to find the second partition of efs. Can you plz provide me a backup?
Click to expand...
Click to collapse
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543

sfhub said:
There is some info about this over on the TWRP thread.
Essentially if you write all zeros into the efs partitions, the phone will recreate the data (if you instead of non-zero data, it will think things are corrupted)
I suggest you read very carefully erverything you can about recovering from the TWRP EFS bug. This post will get you started, but I suggest you read the original thread from the 6p forum that is referenced in this post. I haven't done this myself nor have I read that carefully so don't want to give you bad advice and make your situation worse.
http://forum.xda-developers.com/nex...h-recovery-t3230471/post68595543#post68595543
Click to expand...
Click to collapse
Thank you very much! I'll read it first thing tomorrow and I'll let you know what happened.

@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.

adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Glad to hear you got things fixed.

I think i have done the same to my EFS Partition
adbPush said:
@sfhub thank you so much!!!! That was it! The dd commands fixed my problem. I didn't know that the EFS partitions could be reconstructed by the system. I thought I was done. Thank you for indicating the TWRP bug. I was not aware of it. I couldn't understand what could have possibly went wrong since everything was flashed successfuly from the factory images.
Click to expand...
Click to collapse
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.

saadabbasi said:
Can you please share the exact command you used for nexus 5x as the link above is for nexus 6p.
Click to expand...
Click to collapse
They are the exact same commands as for 6P:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Question Does anyone have persist.img?

HI all, so I accidentally flashed the persist.img from my oneplus 7 pro onto my oneplus 9 pro, and the fingerprint sensor won't work anymore. Does any one have a persist.img backup that I could have to fix my phone please and thanks.

Just backup your and use the msm to restore everything.
Why were you touching persist in the first?

harpin14789 said:
Just backup your and use the msm to restore everything.
Why were you touching persist in the first?
Click to expand...
Click to collapse
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.

dej1i said:
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.
Click to expand...
Click to collapse
You should have a backup on the other slot if you remember which slot you flashed the wrong persist to. Then you can restore that. How did you not take a backup of your persist

Here is my persist. Flash at your own risk

harpin14789 said:
Here is my persist. Flash at your own risk
Click to expand...
Click to collapse
Thank you!!

dej1i said:
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.
Click to expand...
Click to collapse
hm, msm tool would definitely flash a new persist, it repartitions the phone and flashes completely back to stock, so that's odd that it didn't work for you.

harpin14789 said:
Here is my persist. Flash at your own risk
Click to expand...
Click to collapse
It won't do anything for him. Persist partition is encoded to be specific to device.

Bummer.
I just backed up my persist and modem partitions today using Wanam's Partition Backup.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
I'd share but it sounds like it wont help.
I'm TMO if it matters.

Persist.img

Burt Squirtz said:
It won't do anything for him. Persist partition is encoded to be specific to device.
Click to expand...
Click to collapse
That's what I told him as well, but he still seemed to want to try so I let him try and see. I don't think msm seems to help either. Might need to send phone to device to get it restored.