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
Related
My note 2 is less than a month old. i had a bad flashing experience after flashing MIUI Rom for my phone on the note 2 android development thread.This was my first rom flashing on the phone. I luckily backed up my EFS.img before flashing. After flashing the rom i lost my IMEI...i had another issues with the rom hence restored nandroid backup of my phone using CWM. & since then after restoring my EFS.img each time i will get my IMEI back but if i reboot my phone for any reason the IMEI is wiped out. I have tried restoring using the command from the elevated Terminal emulator & using EFS pro tool.
Still the same...each time i have to restart my phone i will lose my IMEI.
is there any way of keeping my EFS partition or IMEI intact after each reboot . I am on stock ROM but i didnt flash it back using ODIN as i mentioned earlier i restored my nandroid backup.
Any help will be greatly appreciated...Please help
rohit83 said:
My note 2 is less than a month old. i had a bad flashing experience after flashing MIUI Rom for my phone on the note 2 android development thread.This was my first rom flashing on the phone. I luckily backed up my EFS.img before flashing. After flashing the rom i lost my IMEI...i had another issues with the rom hence restored nandroid backup of my phone using CWM. & since then after restoring my EFS.img each time i will get my IMEI back but if i reboot my phone for any reason the IMEI is wiped out. I have tried restoring using the command from the elevated Terminal emulator & using EFS pro tool.
Still the same...each time i have to restart my phone i will lose my IMEI.
is there any way of keeping my EFS partition or IMEI intact after each reboot . I am on stock ROM but i didnt flash it back using ODIN as i mentioned earlier i restored my nandroid backup.
Any help will be greatly appreciated...Please help
Click to expand...
Click to collapse
it seems that the backup u created u must have left your efs in selecting while backup thus the recovery backup is not giving your imei back rather u are doing it manually so once u get it done , I would suggest to flash fresh using odin
shhbz said:
it seems that the backup u created u must have left your efs in selecting while backup thus the recovery backup is not giving your imei back rather u are doing it manually so once u get it done , I would suggest to flash fresh using odin
Click to expand...
Click to collapse
Thanks for your reply...tried that but flashing stock rom using odin didnt help ...still the IMEI is wiped after each restart of the phone..
any other suggestions please...
rohit83 said:
Thanks for your reply...tried that but flashing stock rom using odin didnt help ...still the IMEI is wiped after each restart of the phone..
any other suggestions please...
Click to expand...
Click to collapse
flash the pit partition first using odin and then the stock it should solve the issue permanently if not take it to service center
http://forum.xda-developers.com/showpost.php?p=31801134&postcount=4
download pit from here and then flash the stock rom
if you dont want to take risk just go stock completely and use triangle away and get your status normal and count zero and give it to ss saying that the imei gets off. let them solve
shhbz said:
flash the pit partition first using odin and then the stock it should solve the issue permanently if not take it to service center
http://forum.xda-developers.com/showpost.php?p=31801134&postcount=4
download pit from here and then flash the stock rom
if you dont want to take risk just go stock completely and use triangle away and get your status normal and count zero and give it to ss saying that the imei gets off. let them solve
Click to expand...
Click to collapse
thanks again for your time & reply...before flashing the pit partition i would like to know what are the risks involved in flashing pit...do i need to backup my data on internal memory..i flashed pit on my samsung galaxy s advance a few months back to recover the complete storage space on it as it was reduced to 4 gb from 16 gb after flashing jellybean update from sammobile.com..so tell me what are the risks involved & what does flashing pit actually does on the phone..
looking forward for your reply
Issue resolved
rohit83 said:
thanks again for your time & reply...before flashing the pit partition i would like to know what are the risks involved in flashing pit...do i need to backup my data on internal memory..i flashed pit on my samsung galaxy s advance a few months back to recover the complete storage space on it as it was reduced to 4 gb from 16 gb after flashing jellybean update from sammobile.com..so tell me what are the risks involved & what does flashing pit actually does on the phone..
looking forward for your reply
Click to expand...
Click to collapse
btw...before installing stock rom via ODIN i put the phone in the download mode & as it had to restart to go into download mode the IMEI was wiped automatically as that was the issue...but i flashed stock firmware via ODIN & as the phone booted up IMEI was not there & hence i restored i using EFS pro again & i now i have checked it the IMEI stays after the phone restart...so the issue is fixed...thanks a ton for your reply & help :good::good:
Hi there,
I have spent hours trying to fix my issue that i am trying to fix and i was wondering if you guys could help me out?
A few weeks ago i went to go and plug my phone in as it was completely flat but for some reason it began some kind of boot loop where it would reach the lock screen for a few seconds and then power off again because it did not have enough power.
I left this on over night in the hope that it would charge my phone but when i tried to power it on in the morning it just got stuck at the Samsung logo. I did a quick web search and they suggested leaving your phone at the Samsung logo, clearing you cache/dalvic cache and finally resetting it. After all of the above failed i thought that maybe a a full restore in odin would work, the same thing happened when i tried to power it on.
I then went back into the stock recovery after the reset to find the error "E: failed to mount /efs (invalid argument)".
After quite some research into this i found a possible zip that may fix the issue from people having a similar issue but of coarse it diddn't work.
It seems as if the /efs folder/partition may be corrupted in some way.
I am really stuck on this now and i am reluctant to pay lots of money to someone to fix it
Do you have any ideas?
Many thanks,
Shenstone
EDIT: The phone has CWM recovery installed and i have attemped to flash the stock firmware with both Kies and Odin
Bro, maybe flash stock firmware will solve the prolem
exorcistz said:
Bro, maybe flash stock firmware will solve the prolem
Click to expand...
Click to collapse
Sorry forgot to mention that, i have flashed stock firmware with both odin and kies but both do not work, same process still occurs
Any other ideas? :/
Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...
librapt said:
Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...
Click to expand...
Click to collapse
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
See this, http://forum.xda-developers.com/showthread.php?t=2420881
shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
I use this,
http://forum.xda-developers.com/showthread.php?t=2269318
Guys i lost my imei
This was because when i flashed the latest twrp and then lower version of twrp recovery using higher version, after that i got stock recovery i again flashed twrp using odin and realised i lost my imei
I have two backups of imei one efs.img which i tried to restore using terminal emulator it was successful but i didn't get my efs back
I have one more efs backup of extension tar.gz of 61.3 kb if i extract it i get a folder of 5mb with many files how do i restore it?
Is there any other way i can get my imei back.
Please help ;(
Edit : Problem solved
Kartik pat said:
Guys i lost my imei
This was because when i flashed the latest twrp and then lower version of twrp recovery using higher version, after that i got stock recovery i again flashed twrp using odin and realised i lost my imei
I have two backups of imei one efs.img which i tried to restore using terminal emulator it was successful but i didn't get my efs back
I have one more efs backup of extension tar.gz of 61.3 kb if i extract it i get a folder of 5mb with many files how do i restore it?
Is there any other way i can get my imei back.
Please help ;(
Edit : Problem solved
Click to expand...
Click to collapse
I have same problem.
Please share the solution.
Sent from my MI 3W using XDA Premium 4 mobile app
Kartik pat said:
Guys i lost my imei
This was because when i flashed the latest twrp and then lower version of twrp recovery using higher version, after that i got stock recovery i again flashed twrp using odin and realised i lost my imei
I have two backups of imei one efs.img which i tried to restore using terminal emulator it was successful but i didn't get my efs back
I have one more efs backup of extension tar.gz of 61.3 kb if i extract it i get a folder of 5mb with many files how do i restore it?
Is there any other way i can get my imei back.
Please help ;(
Edit : Problem solved
Click to expand...
Click to collapse
Hey you should try EFS PRO for making backup of your efs because it's easy to use..???????
Sent from my GT-N7100 using XDA Forums Pro.
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
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