Hi,
I have this kind error after restoring nandroid backup?
Any fix advice?
I tried substractum theme, then it messed up something and everything freezes. Then i went in twrp and flashed substract recivery zip but sill everything was still strange. Then i dexided restore my 2 days old nandroid backup and I get this kind of error.
I have rooted. 5.0.4.
Right now i have this recovered nandroid backup and looks like everything is working but why this error.
I got same error when i flash kernel (structure needs cleaning), like in picture
Mairo said:
Hi,
I have this kind error after restoring nandroid backup?
Any fix advice?
I tried substractum theme, then it messed up something and everything freezes. Then i went in twrp and flashed substract recivery zip but sill everything was still strange. Then i dexided restore my 2 days old nandroid backup and I get this kind of error.
I have rooted. 5.0.4.
Right now i have this recovered nandroid backup and looks like everything is working but why this error.
I got same error when i flash kernel (structure needs cleaning), like in picture
Click to expand...
Click to collapse
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as 'ext 4'
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Edit: I've seen some people asking some more questions surrounding this issue. For newer devices with A/B partitions I'm unsure what to do in most of these cases.
'Magellon1991' posted their findings regarding the 'vendor' and 'system' partitions.
As for anything further, this is beyond my knowledge - I simply stumbled across this initial solution by trial and error and it is likely a little outdated by now.
Best of luck!
Ok. I will try it later.
Edit: looks like it fixed problem. So thaks BenisMusical!
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Thanks so much for posting this. Only fix I found that actually worked
Work in ZX1
Shaneee said:
Thanks so much for posting this. Only fix I found that actually worked
Click to expand...
Click to collapse
But not at once. First, the format of the "system" and "vendor" sections, after restoring only the "system" and "vendor", and then the "image and image systems and image vendor", and then restoring the OEM, otherwise it was a bootlope without OEM
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Same issue occuring for me. I have tried restoring multiple backups but same error every time. I can boot into the system by flashing the rom file and then restoring the data. But why cant i restore TWRP backup??
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Awesome post, thanks a lot.
It worked perfectly.
This was lifesaver!
I did what BenisMusical recommended. Additionally I have to flash the last image. Without there was the boot loop...
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Logged in just to say thank you. Did what you told down to the letter, and I got my data back. Thanks again!
i have a error failed to mount cust (structure need cleaning)
how to fix this?
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Benis,
I'm a Crisis Counselor.
I need my rooted Note 9 for house visits.
I am SOL without my phone 'cause I can't navigate/make phone calls.
I am in your debt. Anything you need, I will get you...
Actually, I can't go that far, but I want to give you a heartfelt THANK YOU, and a firm, anti-COVID, handshake.
Thanks Pal.
Didn't work for me sadly. I use Treble and I just restored data, flashed the original vendor zip and system.img (Not the one from the backup - as well as magisk) and it worked again.
BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as 'ext 4'
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Edit: I've seen some people asking some more questions surrounding this issue. For newer devices with A/B partitions I'm unsure what to do in most of these cases.
'Magellon1991' posted their findings regarding the 'vendor' and 'system' partitions.
As for anything further, this is beyond my knowledge - I simply stumbled across this initial solution by trial and error and it is likely a little outdated by now.
Best of luck!
Click to expand...
Click to collapse
absolute legend worked for me
Related
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
Ok so I am currently running the newest version of MIUI. I just got it a few hours ago and I want to go back to my old ROM (codename android) to back up all of my apps to titanium backup. I make 2 nandroid backups before I installed MIUI. Every time I go into clockworkmod and try to restore one of the backups. I get an error saying "error while restoring /system." Is there anything that I am doing wrong? I tried wiping data/cache/dalvik and then installing the ROM, but I get an error saying "some symlinks failed." Any help with this? I need all of my apps back.
Titanium will allow you to restore apps from a nandroid backup. You could also pull them out yourself -- the nandroid script stores them in a tarball.
efrant said:
Titanium will allow you to restore apps from a nandroid backup. You could also pull them out yourself -- the nandroid script stores them in a tarball.
Click to expand...
Click to collapse
Ok, I will do that. But I also need to know how to get back to my old ROM?
maxbakerman said:
Ok, I will do that. But I also need to know how to get back to my old ROM?
Click to expand...
Click to collapse
Just redownload it and flash it, no? After that you can use TB to extract your apps, or you could even just restore /data in CWM -- if I remember correctly, it should allow you to restore each partition individually. So if you are having problems restore the nandroid as a whole (because it fails on /system) just restore /data and /boot.
efrant said:
Just redownload it and flash it, no? After that you can use TB to extract your apps, or you could even just restore /data in CWM -- if I remember correctly, it should allow you to restore each partition individually. So if you are having problems restore the nandroid as a whole (because it fails on /system) just restore /data and /boot.
Click to expand...
Click to collapse
It wont let me flash it. That's my problem. I get an error saying "some symlinks failed." And also whenever I try to just restore /data or /system it fails
maxbakerman said:
It wont let me flash it. That's my problem. I get an error saying "some symlinks failed." And also whenever I try to just restore /data or /system it fails
Click to expand...
Click to collapse
what recovery/version are you using?
sent from my i9250
bk201doesntexist said:
what recovery/version are you using?
sent from my i9250
Click to expand...
Click to collapse
cwm 6.0.1.0
use old cwm.
sent from my i9250
So i exchanged my phone out today but I kept a backup of the nandroid backup on my computer. After placing it back on the phone it says "error restoring /system", then stops. I have two other older images and they both say "error restoring /data" and stop. Anyone know how I can fix this?
I am wiping data/cache/dalvik before performing this
EDIT: now it seems I cant get my phone to boot up anymore. It just get's stuck on the galaxy note II screen. This was done with a brand new phone.
Jinra321 said:
So i exchanged my phone out today but I kept a backup of the nandroid backup on my computer. After placing it back on the phone it says "error restoring /system", then stops. I have two other older images and they both say "error restoring /data" and stop. Anyone know how I can fix this?
I am wiping data/cache/dalvik before performing this
Click to expand...
Click to collapse
So you try backup from your old phone file to new phone ? I want to know the answer too.
simplelife said:
So you try backup from your old phone file to new phone ? I want to know the answer too.
Click to expand...
Click to collapse
yes, but it errors when i try to restore, i have tried 3 different images
Jinra321 said:
yes, but it errors when i try to restore, i have tried 3 different images
Click to expand...
Click to collapse
Can you tell me why you need to do that? 3 backup images , you nandroid backup from stock recovery or CWM ?
simplelife said:
Can you tell me why you need to do that? 3 backup images , you nandroid backup from stock recovery or CWM ?
Click to expand...
Click to collapse
it's rooted with CWM. i only need 1 image, but none of them work
Jinra321 said:
it's rooted with CWM. i only need 1 image, but none of them work
Click to expand...
Click to collapse
Maybe the old image not compiable with your new phone.For me, i will stop doing that before i damage my phone
Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.
devcager said:
Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.
Click to expand...
Click to collapse
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?
dirtygoldfish said:
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?
Click to expand...
Click to collapse
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114
devcager said:
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.
Pirateghost said:
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.
Click to expand...
Click to collapse
In fact I do not know what BLOB folder is so I suppose I did not delete it. i did not even give my names to the backups. Sooo... what shall I do? I mean, I have wiped out the ROM and now getting everything back from scratch but I think I won't be able to make backups Thanks
Try the non touch versions of cwm or twrp.
Sent from my i9250
bk201doesntexist said:
Try the non touch versions of cwm or twrp.
Sent from my i9250
Click to expand...
Click to collapse
Thanks, man! That helps. Pushing thanks button
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