Related
Hy everyone,
I'm a little desperate now. my i9500 is stuck at Samsung logo even the animation sound that not complete, i had mokee rom 4.4.2, made a restore from a previous nandroid backup, barebone prism rom V3.0 worked perfectly, installed nandroid manager and restored some access point passwords, worked perfectly so far, my phone reached 1% in battery then turned off after a while. when i wanted to reboot it, the phone freezes in Samsung logo.
Recovery: Philz touch recovery
I tried everything that i know about,
1° reboot in revocery and restore from a previous nandroid backup (NOT GOOD)
2° reboot in recovery, perform a full wipe, restore from a working previous backup (NOT GOOD)
3° reboot in recovery perform a wipe reset (NOT GOOD)
4° restore via odin in download mode last stock firmware for my phone I9500XXUEMJ8 (NOT GOOD)
5° i tried mounting all partitions for check and .... Eroor mounting /efs!
i checked efs folder with aroma file manager ... 0 files inside :crying:
i had a previous backup for EFS found in kies in .tar.gz format
i tried to restore it with several methods
http://forum.xda-developers.com/showthread.php?t=2392632
guess what ?? NOT GOOOD
i tried manually to copy files in EFS folder and changed the permission for EACH file with the same permission from the backup in my laptop then i reboot in recovery, the files still inside but when i reboot the system, the files are gone
i've read somewhere that there is two type of efs , and the efs made by some old stock rom won't work for a new one (Personally i don't know but like i said i'm desperate) so i downloaded from sammobile the FIRST rom that was in my phone and put it via odin (Re partition was never checked) then i tried the methods above ... :crying::crying::crying:
because i only have .tar.gz i tried restore it and witout rebooting the phone ===> (EFS Folder not empty YET) made a backup in .img format so that i can restore in /dev/block/mmcblk0p3 still not good
so i REALLY need your help and plz do not ask me to go to service center, warranty binary status is 1
Thanks everyone and have a good day
Was i mistaken in the section or there is really no solution for my problem ??
solution
shinka110 said:
Was i mistaken in the section or there is really no solution for my problem ??
Click to expand...
Click to collapse
you need to flash a efs partition via odin. in tar format.
the your phone will boot normally. unistall knox and only then you could put your efs backup to the phone.
nefsation said:
you need to flash a efs partition via odin. in tar format.
the your phone will boot normally. unistall knox and only then you could put your efs backup to the phone.
Click to expand...
Click to collapse
where i can get efs in .tar? i have my old efs but in a single folder.
i have a big problem, more than a simple copy paste, but with prove i don´t miss anything.
this is my original problem and i´m still stucking there.
http://forum.xda-developers.com/showthread.php?t=2665161
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
...
Click to expand...
Click to collapse
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
xclub_101 said:
On the N9005 the IMEI is no longer on the EFS partition (mmcblk0p11) but instead in some other partition - I think mainly in MS1 (mmcblk0p12) with something else (backup?) in MS2 (mmcblk0p13). There might be something else in mmcblk0p17, mmcblk0p18 and mmcblk0p19.
If you do not have any backup (including a larger "debrick backup" - search for that post) you can try to see which one of the partitions I listed above was supposed to be the backup of what; and if that fails there is a more complex procedure described somewhere in a thread on XDA - involving manually hex-editing your SN and IMEI from under the battery or the original box of the phone.
Click to expand...
Click to collapse
ok thank you - bad news
Ill try this guide: (Can this guide be used with KK 4.4.2 ?)
http://forum.xda-developers.com/showthread.php?t=2567133
What about the "unkown baseband"? How can this be fixed?
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Bro whats a twrp efs backup?
Team win recovery Project. Its a revovery and a twrp efs Backup is a Backup from the 3 efs partitions in twrp
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Will a TWRP boot ,data and system backup work as well for restoring baseband? I have the same problem -> http://forum.xda-developers.com/showthread.php?t=2796948&page=6
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
No u need an efs backup
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
So have I run out of options? Please have a look at my thread. The last few posts especially . Any help would be appreciated.
Please help sm-n900
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
just went to the above mentioned link but none of the multiupload files link work.
could you upload the NOTE 3 - Fix soft bricked.rar and the Samsung drivers.
I want to extract the NOTE 3 - Fix soft bricked.rar and modify it for use in sm-n900
Sorry I don't have these files anymore try to get them from the thread owner
Gesendet von meinem SM-N9005 mit Tapatalk
Hundsbuah said:
Ok a managed it to get all back working, incl. baseband, emei etc (but you need a twrp efs backup with all 3 efs partitions --> simply a twrp backup)
If some others have the same problem, here you go:
I think some other partition was corrupted and thats why the twrp efs restore didnt worked (just a twrp efs restore).
I did following: (you need a efs backup!!!)
Folow exactly this guide http://forum.xda-developers.com/showthread.php?t=2567133: and do all partitions, DONT! skip the efs partitions (we have a twrp backup)
Now some further steps are needed:
IMPORTANT:
1) When you put in back your battery, boot back into twrp and restore your TWRP EFS Backup!! Dont boot in the OS!!!!
2) Then reflash with odin a stock based rom without any other checkboxes (NO EFS PHONE CLEAR, NO NAND ERASE ALL!!!!), just a normal odin stock rom flash
3) Let the phone reboot into OS and YES: Baseband working again, EMEI working again
Click to expand...
Click to collapse
Hi, I have the same problem as you did, my baseband is showing unknown and the imei is showing null. This happened when I was installing a different modem via ODIN. I do have a EFS backup, however, it was done with philz recovery instead of TWRP and has 4 files ('efs.ext4.tar'; 'efs.ext4.tar.a'; 'nandroid.md5'; and 'recovery.log'). Are these the same that you would get with a TWRP?
I also have another efs backup that I did which is one file only, 'efs_20140531_122400.img'. Would I be able to use this for anything?
The phone is an N9005 on Kitkat.
Thanks for any help in advance and please let me know if you need any other info.
Cheers
--------------------------
Just to let you know,
I had tried flashing flash latest full UK NF4 system before and it didn't work. However, desperate as I was, I went again and gave it another shot and incredibly enough, it worked!!!! Phone is back together again!!!! Yeeahh!!! There goes an incredible load off my shoulders. I guess I did something in between that actually helped, we may never know.
Cheerio
Hundsbuah said:
Hi all,
i had to use "Clear Phone EFS" in Odin to get my 9005 back working - i thought: "Hey no problem i have multiple EFS backups..."
But now even if i restore my backup in TWRP or via the Windows Batch Backup Script, my Baseband and EMEI and EMEISV is still "unkown"
Can s.o tell me the steps i need to do, to rewrite my Baseband and EMEI with my available EFS backups?
What i have:
- EFS Professional
- 2 different EFS backups in TWRP
- 2 windows back tool EFS backups (i mean this script: http://forum.xda-developers.com/showthread.php?t=2447342)
- Working WIFI
- Working BT
- Stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX file(s)
- Stock N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME file(s)
- Stock N9005XXUENB7_N9005DBTENB2_DBT file(s)
- Odin + 9005 PIT Files
- Correct SerialNumber in DeviceInformation->Status
I'm on the new Bootloader and KitKat OS
Thank you very much for all your help!
Best regards,
Chris
PROBLEM SOLVED!
Look here http://forum.xda-developers.com/showpost.php?p=51152510&postcount=4
Click to expand...
Click to collapse
Hi Hundsbuah,
I upgraded my Note 3 9005 Hong Kong Version 32 GB from Jelly Bean to KitKat without taking backup of EFS and now I have IMEI Null and Baseband unknown. I found backup of other user's note3 EFS at "http://forum.xda-developers.com/showthread.php?t=2447342". So, if I tried EFS restore from above link will it resolve my IMEI null and baseband unknown issue?
Regards,
Asif
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
merlin21 said:
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
Click to expand...
Click to collapse
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Here the full Backup for the CAN-L11:
https://drive.google.com/open?id=0B134drJ4-Ed0R3VSY3A5NGpjVWc
Format /data, reboot recovery and than restore from backup. After the restore is complete make a wipe.
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
merlin21 said:
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
Click to expand...
Click to collapse
Inside the folder twrp and its subfolders there it is system.img. I'm downloading it myself.
Sent from my victara using XDA Labs
Share if you have another workarounds for me
Gesendet von meinem LG-D802 mit Tapatalk
@merlin21 yes it sounds like my problem after I tried to flash the emui5 beta.
My phone is fully working again with the backup I posted.
This is not the Chinese version, if nothing works, you can try the caz ROM. But there are massive problems with the gapps, they are not included in the rom.
Gesendet von meinem HUAWEI CAN-L11 mit Tapatalk
@ -=MoRpH=-
i just flashed the twrp.img with fastboot from xelfmade v22.12. and then rebooted twrp.
Then formated data and confirmed with yes - rebooted recovery and tried to restore your twrp. It did not restore and aborted instantly with the error message
during restoreing cust...
extractTarFork() proecess ended with ERROR: 255
what could that be?
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
That only work if the is not rooted... Idk whats up with that, but for now i use the quicksetting screenshot function.
Somehow it worked with my rooted device before. Must be the decrypted data partition?
With the recovery of your backup I could not access data or change memory from data to sd. What version do you use?
I flashed xelfmades v22 and now have rw access and could backup all partitions and restore. Root and xposed modules everything works, just the knock on screen to capture don't...
merlin21 said:
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
I have the same problem! What do you mean by "I had to use the cust from my backup" ? Sadly i dont have any data from my own backup..
can you tell me what to do to get the backup from @murph to work without error?
--solved.
P1xl said:
--solved.
Click to expand...
Click to collapse
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
rak500 said:
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
P1xl said:
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
Click to expand...
Click to collapse
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Thanks for your help my phone is saved with your method!!!
i downgraded my MLA-L03 variant with this, but now im stuck in french language with no other languages to choose from
Vinnom said:
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Click to expand...
Click to collapse
someone please make this thread sticky!!!!!!!
there are some guides in internet how to get nougat for nova and that is were I broke my phone. I was searching solutions for a week, DLed Flahsed tons of things nothing worked. this one fully worked!!!!!!!!!!!!!!!!!!!!
rak500 said:
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Click to expand...
Click to collapse
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Bunkier said:
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Click to expand...
Click to collapse
Frankly, I don't know. I had not modified the partitions prior to bricking my phone, so I think the partitioning was OK. However, I think one of the TWRP availble in this forum can format Data partition properly, which would utlimately allow you to select which File Format you want. I haven't tried it myself, and I haven't been able to do much with TWRP since I flashed Lineage unfortunately. Most of my Mods were just upgrading and I had to ADB Sideload pretty much everything since I flashed Lineage...
Sorry I couldn't be more helpful than that!
Hello guys. If you ever lost any of your wireless connectivity and sensors for flashing any other rom then I have a backup files here via twrp. I just don't know how to make them into flashable so I just compressed it in case you need it.
I've lost my sensors and wireless networks such as fingerprint, signal, Bluetooth and wifi when I restored a backuped system in twrp. I did so many things like restoring its efs, flashing its NON-HLOS.bin file, reverting back to stock to no avail. It just gave me a headache because my bootloader got unlocked again so I unlock it for the 2nd time and it succeeded.
What I did was:
Flash back twrp(persist error occured, then I cannot flash any rom)
Restored efs, and persist on my backuped ( I just remembered that I have backuped the persist)
Reboot to recovery
Flashed RR rom (as usual along with Gapps and SU)
And it succeeded
Waited to boot and I got shocked when everything on my phone was back to normal.
So I am sharing this twrp backup file for you in case you guys need it.
you are sharing your IMEI and other important things remove it or anyone can misuse it
I want to know which file is to be restored to get modem back from twrp backup folder ?
Thread closed at OPs request
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info