I CANNOT restore the firmware partition. I am getting error: extractTarFork() process ended with error : 255 but other stuffs goes well.well now i rebooted without restoring firmware and no problem.but please tell me whether twrp corrupted or manipulated original firmware or it remained untouched and can i backup it again.
Help! Please!
Camlin3 said:
I CANNOT restore the firmware partition. I am getting error: extractTarFork() process ended with error : 255 but other stuffs goes well.well now i rebooted without restoring firmware and no problem.but please tell me whether twrp corrupted or manipulated original firmware or it remained untouched and i can backup it again.
Help! Please!
Click to expand...
Click to collapse
Same here
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
Even I restored and got error,so agin restored with untick firmware and phone booted and everything was fine unexpectedly..lol!can some1explain what is happening with firmware partition
Pranbellam said:
Same here
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
Even I restored and got error,so agin restored with untick firmware and phone booted and everything was fine unexpectedly..lol!can some1explain what is happening with firmware partition
Click to expand...
Click to collapse
same happened to me with alka twrp hey , are you saying u got it fixed by unticking firmwere and everything was fine ?
#BATMAN# said:
same happened to me with alka twrp hey , are you saying u got it fixed by unticking firmwere and everything was fine ?
Click to expand...
Click to collapse
1st I restored with ticking everything and failed while restoring firmware but I was scared bcos firmware was wiped ,but then I again I restored with untick firmware and restored successfully and rebooted and was very happy to see everything working after booted! But my question is when firmware got formatted then how is all like sim and fingerprint working!plz answer me
Pranbellam said:
1st I restored with ticking everything and failed while restoring firmware but I was scared bcos firmware was wiped ,but then I again I restored with untick firmware and restored successfully and rebooted and was very happy to see everything working after booted! But my question is when firmware got formatted then how is all like sim and fingerprint working!plz answer me
Click to expand...
Click to collapse
My guess is, its a bug in the recovery. Didn't encounter this in the official recovery. About your second question, i think that even though we unticked it, it still restores the firmware.
Archit9169 said:
My guess is, its a bug in the recovery. Didn't encounter this in the official recovery. About your second question, i think that even though we unticked it, it still restores the firmware.
Click to expand...
Click to collapse
Official twrp doesn't give option to backup and restore firmware right? Then so we shld untick firmware every time while restoring bcos or else we get error 255 .
Pranbellam said:
Official twrp doesn't give option to backup and restore firmware right? Then so we shld untick firmware every time while restoring bcos or else we get error 255 .
Click to expand...
Click to collapse
Official recovery gives the option to restore firmware and backup. As for you question, just untick firmware everytime you restore. As for me i don't restore anything, i do clean install.
Archit9169 said:
Official recovery gives the option to restore firmware and backup. As for you question, just untick firmware everytime you restore. As for me i don't restore anything, i do clean install.
Click to expand...
Click to collapse
Thanx ..but I like miui so I want to go back to stock if I don't like the rom which I flashed and my doubt is verified thnx so I'll never tick firmware while restoring.
I use official TWRP and i have backup/restored many times my phone with all partitions ticked without any issue. Config in my sig.
is official twrp give option to restore all partitions
zinconnu said:
I use official TWRP and i have backup/restored many times my phone with all partitions ticked without any issue. Config in my sig.
Click to expand...
Click to collapse
hi,official twrp never give option to full backup/restore ,i am talking about alka twrp
Camlin3 said:
hi,official twrp never give option to full backup/restore ,i am talking about alka twrp
Click to expand...
Click to collapse
But it's enough to backup current ROM settings, right?
Related
Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
clown85 said:
Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
Click to expand...
Click to collapse
try philz recovery.
sriram231092 said:
try philz recovery.
Click to expand...
Click to collapse
It says in all the steps E:failed archive external sd
is it a problem to rstore from external sd card? so shall I just try to put it on internal?
Worth trying if you have no backup of it .
jje
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
clown85 said:
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
Click to expand...
Click to collapse
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Endiej said:
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Click to expand...
Click to collapse
My phone works just fine. The problem is to flash the cm10.1 nandroid backup successful to get my internal sd memory back.
btw I tried to copy the backup to internal sd but then it says md5 sum mismatch god damn it..... I just wanna have my internal sd card files back. grrrrrrrr
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
slaphead20 said:
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
Click to expand...
Click to collapse
I guess Im just ****ed... I tried moving it with aroma and then it says error again. its just possible for me to restore the nandroid with cwm which I originally had and just from external sd and even then the logfile says everything is fine just restoring system is an error. that sucks cuz I cant boot the phone then to get access to my internal space via usb
or is there another possibility to restore internal card to get access????
Have you changed recovery versions between creating the backup and trying to restore it?
slaphead20 said:
Have you changed recovery versions between creating the backup and trying to restore it?
Click to expand...
Click to collapse
of course not.
its just weird that I can restore everything exept for this cm10.1 backup. I made already a stock jb backup and I could easily restore this one :S but it doesnt help me anymore.....
Endiej said:
CWM doesn't work without root access
Click to expand...
Click to collapse
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
clown85 said:
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
Click to expand...
Click to collapse
You can try.
Sent from my GT-I9300 using Tapatalk 2
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
clown85 said:
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
Click to expand...
Click to collapse
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
rootSU said:
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
Click to expand...
Click to collapse
No it doesnt boot if I try ro restore the backup I end up seeing Samsung Galaxy S3 screen and thats it....
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
clown85 said:
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Click to expand...
Click to collapse
What is "The above problem"? If it restores and boots, its fine.
clown85 said:
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
Click to expand...
Click to collapse
Nandroid backup takes
boot.img (kernel)
system.img (ROM)
userdata.img (Your stuff)
Its okay. Somehow I got the data restored with advanced restoring which didnt work with 6.0.2.7 but with 3.2.
close here.
thanx for your help
today my battery went down to zero and then my phone stuck on the menu screen.
i rebooted but then my phone got stucked on the samsung galaxy 3 logo.
i tryed to wipe files and catche but it didnt helped,
i tryed to install the ROM again but it didnt helped...
i can get to the recovery and download mode, but my phone still stuck on the stuped logo...
what to do?
sry if i have spelling mistakes...
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
thx but...
boomboomer said:
You have corrupted one or more partitions, try a factory reset after flashing your custom rom again.
If that doesn't work then use Odin to flash a stock firmware, then factory reset.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
sorry but what "flash a stock firmware means?"
how do i do that?
do you have links?
ty!
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Go read the sticky thread in general forum, you are missing basic information.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
ok so i should download the firmware achieve from my area
then i just flash original ROM?
this is the instruction page: http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
then im done?
i need to change the recovery thing too?
or i can just start from procces 4?
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
orial10 said:
i did what u told me
i used odin to flash
then it stucked on samsung logo
so i went to the recovery, and i wiped the things
but it didnt helped, it still stucked on the samsung logo..
i noticed some red lines in the recovery that says
"failed to mount /efs(invalid argument"
what is that means?
Click to expand...
Click to collapse
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
dxppxd said:
Means you screwed the efs partition when flashing an incompatible modem with your efs version.
If you flashed a 4.1.2 firmware and got that error, try and flash a mg4 or above modem to see if it gets solved. Or flash a 4.3 firmware altogether.
Read rootSU post on efs, it's a must.
Of you ever backed up your efs or used twrp recovery to make a nandroid backup (which also backs up efs) you might get it back by restoring it.
Otherwise, a patched kernel, modem or ariza patch would be the last available choice before sending to repair.
Click to expand...
Click to collapse
can you explain or give me some links how to do that?
orial10 said:
can you explain or give me some links how to do that?
Click to expand...
Click to collapse
I mean, go to the stickies in the general section and read. They're there for a reason, including steps before rooting, flashing, information on the efs partition, and pretty much everything else you could have done to avoid the situation you're facing right now.
Hi GUys,my samsung galaxy grand2 duos(SM-G7102) is stuck in bootloop after restoring nandroid backup.The backup got restored successfully but my phone got stuck in bootloop
I'm using CWM 6.0.4.8.... i'm seen somewhere that you have to flash boot.img in your nandroid backup using adb after restoring,is that true....
OS: LP 5.1.1 cm 12.1
I've flashed project skynet earlier,but took nandroid backup before that,so no change in os. I just wanna restore ........HELP ME OUT GUYS....:fingers-crossed:
use twrp
if your phone gets stuck at the screen which shows device name and model number, it means you should change your bootloader.
go to cwm>restore> advanced restore from sdcard01(you can find custom restore option there. check whether you have bootloader backup. if yes, then restore bootloader. if its not working, then it means the backup files are corrupted.
next option is dowloading stock rom and flashing.
See this thread to download stock Rom easier
JitDevHacker said:
if your phone gets stuck at the screen which shows device name and model number, it means you should change your bootloader.
go to cwm>restore> advanced restore from sdcard01(you can find custom restore option there. check whether you have bootloader backup. if yes, then restore bootloader. if its not working, then it means the backup files are corrupted.
next option is dowloading stock rom and flashing.
See this thread to download stock Rom easier
Click to expand...
Click to collapse
nope... i don't think so.. This happens everytime i try to restore.Now i've flashed cm12.1 and it works ..
@rd said:
nope... i don't think so.. This happens everytime i try to restore.Now i've flashed cm12.1 and it works ..
Click to expand...
Click to collapse
maybe the problem is with recovery. Try flashing twrp
Sent from my SM-G7102 using Tapatalk
JitDevHacker said:
if your phone gets stuck at the screen which shows device name and model number, it means you should change your bootloader.
go to cwm>restore> advanced restore from sdcard01(you can find custom restore option there. check whether you have bootloader backup. if yes, then restore bootloader. if its not working, then it means the backup files are corrupted.
next option is dowloading stock rom and flashing.
See this thread to download stock Rom easier
Click to expand...
Click to collapse
JitDevHacker said:
maybe the problem is with recovery. Try flashing twrp
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
can u direct me to any link.I tried one from the forum and it was a failure
TWRP by Aapav
Problem was with recovery... Now with twrp restore works fine... Phew...
I had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
AsuraDas said:
I had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
Click to expand...
Click to collapse
Are you using the latest firmware for your phone?
muradulislam said:
Are you using the latest firmware for your phone?
Click to expand...
Click to collapse
Yes
u did wipe every thing before u flash stock ? u should fully wipe ur device . ( data, system cache , dalvik and internal memory ) all this should be wiped then u can flash each img throw TWRP to same partition , try again should work with stock then u can go back to CM !.
Yes through twrp and fastboot. Also when trying to flash using update.app I am on stock recovery
while wiping u got any error ? of success with 0 errors ?
No errors that, I don't think
When I try to wipe using stock recovery (factory reset) it always fails. Although I can wipe cache
AsuraDas said:
When I try to wipe using stock recovery (factory reset) it always fails. Although I can wipe cache
Click to expand...
Click to collapse
Try using dload after flashing stock recovery through bootlaoder.
I did, I just feels like I have tried every combination and every trick to get this up and running. IDK it seems like the cm13 update messed up a partition and only cm13 works and only partially works because 4g and wifi are not working at all. :'(
AsuraDas said:
I did, I just feels like I have tried every combination and every trick to get this up and running. IDK it seems like the cm13 update messed up a partition and only cm13 works and only partially works because 4g and wifi are not working at all. :'(
Click to expand...
Click to collapse
Well that could mean there is a problem with your EFS partition. But I don't know how an OTA could have messed it up. How did you update CM13? Did you use CyanDelta?
It was OTA which was flashed through TWRP recovery
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
only sollution is trial and error,,
just make it a two way..
if you have stock recovery, try rollback package and install lollipop
and if youve twrp, download a lollipop firware backup and just rostore..
any one of those will get you on emui3 and you can start it fresh again..
gud luck
xskull03 said:
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
Click to expand...
Click to collapse
having issue with EFS without a backup for it is like breaking ur device , installing stock will always fail .
if EFS not recognized or missing the only solutions is service center only .
and if ( only ) if the phone works he will not be able to get any network to work .
xskull03 said:
In About Phone check to see if Baseband and IMEI numbers are shown. If not then something must be wrong with your EFS partition.
Going to stock through Huawei updater is the only way to fix this IMO, unless you have made a backup of your EFS partition earlier.
Try the Huawei update using another firmware since the one you have may be corrupted.
Click to expand...
Click to collapse
No imei numbers are shown, and I have tried to go through Huawei updater but I just can't seem to get it to work
md1008 said:
No imei numbers are shown, and I have tried to go through Huawei updater but I just can't seem to get it to work
Click to expand...
Click to collapse
service center , EFS is missing or damaged u can't connect ur phone to network any more .
AsuraDas said:
I had CM13 official build installed, all was well until I had OTA update which I have done many times on that phone as well as others. After update I was unable to login as my password/pin no longer worked. Factory reset solved that problem and when it booted back I was unable to read sim card or connect to wifi or even Bluetooth. Trying to flash stock resulted in failing. I tried using dload which results in fail. as well as extracting update.app and using fastboot which does flash however stuck on boot loop. If I install a stock rom through twrp it hangs at flash screen. If I flash cm13 it boot but I am unable to use 4g/wifi or anything.
Click to expand...
Click to collapse
Can I know which version of stock ROM you are On before flashing custom ROM ?
So I contacted Honor support and they said since I unlocked bootloader that my warranty is void. I asked if they have out of warranty repair and they said they do not. Seems like my phone is now an iPod Classic with a touch screen since I can't even use wifi or Bluetooth. If anyone has any suggestions on how to fully restore this phone I am all ears
AsuraDas said:
So I contacted Honor support and they said since I unlocked bootloader that my warranty is void. I asked if they have out of warranty repair and they said they do not. Seems like my phone is now an iPod Classic with a touch screen since I can't even use wifi or Bluetooth. If anyone has any suggestions on how to fully restore this phone I am all ears
Click to expand...
Click to collapse
I am not sure but if there is a twrp backup on the internet for your phone, flash that using twrp...
I have made three nandroid backups in TWRP but whenever I try to restore them, I get an error.
Code:
extractTarFork() process ended with ERROR: 255
Here's an image: http://i.imgur.com/As7O6LL.jpg
I have attached a log file. So someone please look at it and tell me what's causing the error when I'm trying to restore my backup. After this error occurred I accidentally wiped cache/dalvik. Sorry about that.
I have a Redmi Note 4 (SD variant) mido. TWRP version is 3.1.0-0 by abhishek987. Current ROM is AEX 4.2 and my phone has more than 35GB available. Someone please help me.
hi
i am facing same problem, did you find a solution?
---------- Post added at 10:21 AM ---------- Previous post was at 10:21 AM ----------
hi
i am facing same problem, did you find a solution?
rv5750 said:
I have made three nandroid backups in TWRP but whenever I try to restore them, I get an error.
Code:
extractTarFork() process ended with ERROR: 255
Here's an image: http://i.imgur.com/As7O6LL.jpg
I have attached a log file. So someone please look at it and tell me what's causing the error when I'm trying to restore my backup. After this error occurred I accidentally wiped cache/dalvik. Sorry about that.
I have a Redmi Note 4 (SD variant) mido. TWRP version is 3.1.0-0 by abhishek987. Current ROM is AEX 4.2 and my phone has more than 35GB available. Someone please help me.
Click to expand...
Click to collapse
Do not restore "firmware" & "bootloader", rest is ok as far as I read.
Lieutenantdaan said:
hi
i am facing same problem, did you find a solution?
Click to expand...
Click to collapse
#3
Do not restore "firmware" & "bootloader", rest is ok as far as I read.
Click to expand...
Click to collapse
Lieutenantdaan said:
hi
i am facing same problem, did you find a solution?
---------- Post added at 10:21 AM ---------- Previous post was at 10:21 AM ----------
hi
i am facing same problem, did you find a solution?
Click to expand...
Click to collapse
Look at @dedebekri's reply below yours.
dedebekri said:
Here's an image: http://i.imgur.com/As7O6LL.jpg
I have attached a log file. So someone please look at it and tell me what's causing the error when I'm trying to restore my backup. After this error occurred I accidentally wiped cache/dalvik. Sorry about that.
I have a Redmi Note 4 (SD variant) mido. TWRP version is 3.1.0-0 by abhishek987. Current ROM is AEX 4.2 and my phone has more than 35GB available. Someone please help me.
Do not restore "firmware" & "bootloader", rest is ok as far as I read.
Click to expand...
Click to collapse
So, every time I have to restore a TWRP backup I should not restore firmware and bootloader? Does this only apply to Redmi Note 4? The reason I'm asking this is because I had a Samsung Galaxy Grand 2 previously, in which I didn't need to do this for successfully restoring a TWRP backup. Thanks.
Same problem, I tried restoring the backup without bootloader and firmware as mentioned above, and the problem still persists ,my phone doesnt recognize fingerprint scanner and sim, please help!
I backup only system, data, boot and no problem, both with miui and other roms.... Just my 2 cents....
Inviato dal mio Redmi Note 4X utilizzando Tapatalk
scoundrel753 said:
Same problem, I tried restoring the backup without bootloader and firmware as mentioned above, and the problem still persists ,my phone doesnt recognize fingerprint scanner and sim, please help!
Click to expand...
Click to collapse
Same problem here. Please if anyone finds the solution post it here
scoundrel753 said:
Same problem, I tried restoring the backup without bootloader and firmware as mentioned above, and the problem still persists ,my phone doesnt recognize fingerprint scanner and sim, please help!
Click to expand...
Click to collapse
flash the firmware again. you would find its link in any of the mido rom's section
Hello everyone. I found this discussion because I also find this problem. I followed your advice and resetting a backup did not select firmware and bootloader. When I restore the backup, after the system has restarted, it does not recognize the unlock sequence of the display. I always use the same sequence! Redmi notes 4 snapdragon variants.
cuciu70 said:
Hello everyone. I found this discussion because I also find this problem. I followed your advice and resetting a backup did not select firmware and bootloader. When I restore the backup, after the system has restarted, it does not recognize the unlock sequence of the display. I always use the same sequence! Redmi notes 4 snapdragon variants.
Click to expand...
Click to collapse
itas acommon problem. use twrp's file explorer and go to data/system/ and delete two files with extention '.key' and three files with word 'locksettings'in their full name. reboot. now your screen shouldn't have any lock.
Soluiton
I solved my problem by flashing the stock rom on mi flash.
hello friends here another fallen, but two problems remained after applying the solution of post # 3,
1. only recognizes the face unlocking (multipro) the lock by pin does not work
2. I run out of signal and wifi does not work
I know that this is solved by mounting the stock version again but I do not know if it is possible to rescue the backup I made, and help me with a solution in points 1 and 2 before sending the device to miflash before losing my backup and starting all over again , sorry for my bad English
greetings from Ecuador
i am also facing the same problem, i accidently restored the firmware file and now i can not go past bootloop.
if i delete firmware file using twrp then it boots up but there is no signal, no wifi, no fp, . but with firmware file it wont go past bootloop.
i have tried fastboot method, edl method everything i can find on internet but still the problem is there?
please anybody have any solution?
Go here...Here is your solution.
scoundrel753 said:
Same problem, I tried restoring the backup without bootloader and firmware as mentioned above, and the problem still persists ,my phone doesnt recognize fingerprint scanner and sim, please help!
Click to expand...
Click to collapse
I suffered from problem...But his perfectly worked for me!
U Must Not Restore Bootloader, EFS and Firmware Partition while Restoring STock. And By the way, SYstem and Data Partition is Enough. And to revert to MiUi, always Flash Fastboot ROM instead of relying on TWRP Backup.
If U messed Up Sensors, Better Flash Fastboot ROM and Then Go with Ur Choice.