I'm rooted and have twrp installed, if I do a factory reset in System, Reset Options, Erase all data/Factory Reset. Will there be any issues with regards to a soft brick or will the phone boot back up to where it should as if it's a new phone?
I would highly recommend a Backup of persist and efs Partition.
If you have twrp installed you must factory reset in twrp. Doing it in settings will cause the phone not to boot, unless you flash stock recovery.
Remove any saved fingerprints and backup your persist partition before you factory reset. Otherwise your FP could potentially break and you'll have to RMA.
byAidan said:
Remove any saved fingerprints and backup your persist partition before you factory reset. Otherwise your FP could potentially break and you'll have to RMA.
Click to expand...
Click to collapse
It's already broken. I was hoping a factory reset might fix it. But being rooted and having twrp installed hopefully will not screw up the phone if I do a factory reset?
Gordietm said:
It's already broken. I was hoping a factory reset might fix it. But being rooted and having twrp installed hopefully will not screw up the phone if I do a factory reset?
Click to expand...
Click to collapse
Do you have twrp installed permanently or are you just fastbooting into it?
If you have stock recovery you can factory reset from the system like you said and you will go back to stock with no root (bootloader will still be unlocked though).
Does your fingerprint say "enrollment failed" or something similar? If so it's very unlikely you'll be able to fix it yourself without a persist partition backup unfortunately
byAidan said:
Do you have twrp installed permanently or are you just fastbooting into it?
If you have stock recovery you can factory reset from the system like you said and you will go back to stock with no root (bootloader will still be unlocked though).
Does your fingerprint say "enrollment failed" or something similar? If so it's very unlikely you'll be able to fix it yourself without a persist partition backup unfortunately
Click to expand...
Click to collapse
I have twrp installed permanently.
And my fingerprint says " fingerprint registration error".
Gordietm said:
I have twrp installed permanently.
And my fingerprint says " fingerprint registration error".
Click to expand...
Click to collapse
Yes this is not fixable by a factory reset, the only way to fix ....
1)Flash your Persist.img backup (if you have one)
2)RMA your device for repair.
I have the same issue, was going to RMA but to lazy so just reverting to good ol'.swipe.
No no updates will fix the issue unfortunately.
Duncan1982 said:
Yes this is not fixable by a factory reset, the only way to fix ....
1)Flash your Persist.img backup (if you have one)
2)RMA your device for repair.
I have the same issue, was going to RMA but to lazy so just reverting to good ol'.swipe.
No no updates will fix the issue unfortunately.
Click to expand...
Click to collapse
Ok, thanks.
Gordietm said:
Ok, thanks.
Click to expand...
Click to collapse
I had that but I was lucky and it was just magisk canary issue. After switching to stable 20.4 finger print worked again
pyry666 said:
I had that but I was lucky and it was just magisk canary issue. After switching to stable 20.4 finger print worked again
Click to expand...
Click to collapse
Switching back to stable didn't work for me. To hats why I thought a factory reset might work. I haven't tried it yet though.
Gordietm said:
Switching back to stable didn't work for me. To hats why I thought a factory reset might work. I haven't tried it yet though.
Click to expand...
Click to collapse
Dont think that it will help..I have backed up my persit.img just in case..
I have a persist IMG backup.
But how and mostly WHEN I have to load it to avoid fingerprint enrollment problem?
I suppose this must be done after removing root and before relocking bootloader. But it's only a supposition.
Thanks in advance.
Inviato dal mio SM-F700F utilizzando Tapatalk
fmotta said:
I have a persist IMG backup.
But how and mostly WHEN I have to load it to avoid fingerprint enrollment problem?
I suppose this must be done after removing root and before relocking bootloader. But it's only a supposition.
Thanks in advance.
Inviato dal mio SM-F700F utilizzando Tapatalk
Click to expand...
Click to collapse
You only need to restore it if you get the failure which is not certain.
The basic thing is you have your back up which is great, lots of people don't.
Hi,
question regarding efs backup, are these the correct partitions (found them for the OPO7pro)?
adb shell
su
dd if=/dev/block/sdf2 of=/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/modemst2.bin bs=2048
Thanks
Just did a factory reset and that didn't work. Might be a stupid question, but can I restore the persist backup from someone else's phone?
Gordietm said:
Just did a factory reset and that didn't work. Might be a stupid question, but can I restore the persist backup from someone else's phone?
Click to expand...
Click to collapse
No
Related
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
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
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
matteosaeed said:
Hi, I keep seeing that some people brick their phones due to the changes in the process. Question, Due to some battery drainage I am getting, I am trying to do a phone reset.
I currently have TWRP installed and rooted the phone using the jccuando method. What is the best way to reset the phone to factory so I can re-root again and do what I need to do without bricking? Any advice would be much appreciated!
Click to expand...
Click to collapse
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Swizzle82 said:
Definitely boot to twrp via hardware keys or a boot to recovery app.. Do not do it from the settings menu. It will put you into twrp bootloop until you boot from the hard keys anyway. Just remember to flash supersu after you factory reset before you boot or you'll have to boot back into twrp again and flash it.
Click to expand...
Click to collapse
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
matteosaeed said:
Thank you so much. So I see I can get to twrp no problem. What to do inside twrp before I bootloop or do I need to reset factory before I get to twrp? Then what to do after I am in a bootloop ?
Click to expand...
Click to collapse
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Swizzle82 said:
If you used the method I told you there should be no bootloop. Just got to the section wipe and slide the slider for a factory reset. Then afterwards press back and go to your external sd and flash supersu again then reboot it will reboot twice after you flash supersu so don't worry.
Click to expand...
Click to collapse
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
matteosaeed said:
Thank you. I actuallt just got done. I did factory reset instead and booted up fine. I took your advice and flashed supersu after the factory reset and i am all good now. I wonder the difference between factory reset and the format data. I was a little scared to factory reset so it woud not erase the rom.
Click to expand...
Click to collapse
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Cool thank you. I didnt have a problem since i backed up my apps with titanium.
Swizzle82 said:
Format data erases all user data. Factory reset erases all but internal storage. So data format is more extensive.
Click to expand...
Click to collapse
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
matteosaeed said:
Hi, did everything with no problem. I got another question and not sure if you have the answer. I was hoping to re-lock the bootloader again. Do you know of a way to do that and get the phone to boot up to the system? I am trying to avoid the bootloader reboot message after turning on the phone! Thank you for all your help!
Click to expand...
Click to collapse
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Swizzle82 said:
Do not relock unless you're pure stock no twrp or modded boot img. The annoying message will always be there.
Click to expand...
Click to collapse
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
matteosaeed said:
Cool. I tried to relock and unlock. No problem. I just want the stock recovery. Do you know if this is flash able yet ?
Click to expand...
Click to collapse
There is a new thread about how to return to stock somewhere here in the forum..
Swizzle82 said:
There is a new thread about how to return to stock somewhere here in the forum..
Click to expand...
Click to collapse
Sweet. I have been looking at the forum and everything says tarp has to be installed and running . I'll keep looking. Thank you sir .
Absolutely do not re-lock your bootloader unless you are 100% stock. If you brick the phone with a locked bootloader, you are screwed.
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
dirtyreturn said:
I used Flashfire to flash a radio.img without checking flash bootloader.
I can get into the bootloader and twrp.
When wiping the device and flashing another rom or restoring a backup my 6p does not get passed the custom rom splash screen.
I was thinking of trying to fastboot flash system/data/cache of the March update and see if it boots.
I know I messed up. don't even know if it was because I didn't check the bootloader option in Flashfire. Just my guess because everything was working fine beforehand.
Any help or ideas would be welcome.
Click to expand...
Click to collapse
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
5.1 said:
Hey... You said you wiped your device? What did you wipe in TWRP?
Try to install a ROM from TWRP. Once it's over go in wipe and do a factory reset. Reboot. It should likely fix your issue.
Good luck...
Click to expand...
Click to collapse
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Sent from my LG-E980 using Tapatalk
dirtyreturn said:
Hey thanks for the reply.
Yeah, I wiped data, system, cache. Just the standard - I still have internal storage intact.
Its just strange, I've used Flashfire before but not for flashing a radio and it worked out fine.
I am on 3.79 and used Flashfire to flash 3.78. Went to the bootloader just to check and it still shows 3.79. Just my fault . I didn't check flash bootloader in the Flashfire settings. Atleast that's what I am guessing. Things were just fine before
Click to expand...
Click to collapse
Well, if nothing work, maybe backup your internal storage and flash a factory image... Then in recovery do a factory reset afterward. Who knows. Going back to stock shouldn't hurt anyway.
Good luck...
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
v12xke said:
@dirtyreturn
I've used FF to flash only radio files to the modem partition many times without issue. You untick all but modem, and you untick inject SU and preserve recovery. Not sure what went wrong for you. As mentioned , you should be able to manually flash stock and if you're careful, you'll still have your data. All your settings will be reset, but the userdata will be there. You can even use flash-all.bat, but open it in a text editor and remove the "-w" flag so it will not wipe your userdata. The Google page where you get the full factory image will have instructions.
Click to expand...
Click to collapse
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Sent from my Nexus+6P using Tapatalk
dirtyreturn said:
Thanks. It was obviously my fault somehow.
I do remember there being only one option to tick.
Using fastboot back to stock did the trick and made me realize maybe I should hold off on using Flashfire for a bit.
Click to expand...
Click to collapse
Nah, FF is awesome and a major time-saver. Just read up on the documentation here and become familiar with it.
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
I got the same problem... I did't find the solution. Can someone help ?
k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.
Try OrangeFox-R10.0_8-Stable-davinci recovery.
flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20
Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?
flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has
I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.
hey guys, i really need your help urgently.
i just finished setting up my OP8Pro to my needs and then i restored wifi networks from my Titanium Backup from Android 8, i booted and it won't boot anymore.
i get a FATAL EXCEPTION IN SYSTEM PROCESS: WifiHandlerThread...
so now i need to reset these settings via stock recovery and i already modified my recovery to enable ADB but i can't access /data
anyone has a hint for me how to access /data and where to find the wifi config on Android 11?
it's not stored in /data/misc/wifi anymore :/
thanks a lot in advance!
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
dladz said:
You can reset WiFi within WiFi settings in settings.
But I would probably just clear data on the app you restored either in settings/apps or simply via titanium.
If it still fails then boot to recovery and wipe system.
Your storage will remain unaffected.
You could also try safe mode, power off and hold vol up and down as soon as you see the bootloader warning
Fyi I wouldn't bother restoring WiFi passwords like that, there's other ways of doing it.
Google can back these up for you for example, there are apps which can do it like swift (I think can do it)
Click to expand...
Click to collapse
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
eis0r said:
thanks for your answer but unfortunately i can't boot anymore and i can't decrypt /data anymore even after reflashing stock recovery.
what's the best way to flash via fastboot to preserve data?
thank you!
Click to expand...
Click to collapse
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
dladz said:
You'd have to grab one of the fastboot ROMs then flash.
Why can't you open recovery? Isn't your pin / password being accepted?
If it's not and fastboot installation can't be done then honestly I'd just MSM your current firmware..it's easier than fastboot tbh.
You'd need to bootloader unlock after but this is going to wipe everything anyway.
Click to expand...
Click to collapse
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
eis0r said:
my bootloader is already unlocked and i was rooted on 11.0.0... i can boot into fastboot and recovery but i'm not prompted my unlock pattern.
this was working before testing adb integrated recovery and restoring stock recovery...
Click to expand...
Click to collapse
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
dladz said:
I don't get you mate??
I'm saying that if you use the MSM tool it will lock your bootloader so you'll need to unlock it again.
In regards to your recovery if you can get to it then choose English, then wipe, then system, then wipe system.
That will get you back like I said in my previous post.
If it's not asking for your pin/password (there is no pattern)
Then you're fine
I've not used that recovery but I don't see a point in using it
Click to expand...
Click to collapse
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
eis0r said:
sorry i haven't used MSM yet so i didn't know it'll relock the bootloader but i'm more familiar with fastboot flashing so i'd like to stick with that also because i read of problems with the fingerprint reader when relocking the bootloader.
i thought i could delete reset the faulty wifi config via adb by using the adb-enabled stock recovery but i wasn't able to mount /data with it since it's encrypted and it's not asking for my pattern to decrypt it.
neither the stock recovery is asking for it now...
i don't want to lose my data hence i'm looking for a way to get it back running without completely reinstalling.
do you think it could work by only flashing system partition via fastboot?
thanks man!
Click to expand...
Click to collapse
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
dladz said:
Use the thanks button buddy
I think you've certainly got a shot at it and what's the worst that can happen?
Did you actually try to wipe system in recovery? That would be my way to go.
MSM is extremely easy but I understand not wanting to lose storage.
That being said if you're correct about decryption then it won't matter anyway
Click to expand...
Click to collapse
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
eis0r said:
well after trying lots of different things i ended up wiping system settings in stock recovery. atleast i didn't lose storage.
thanks a lot for your help tho!
Click to expand...
Click to collapse
You're very welcome mate, I've done the same a few times..it's not that much of a loss really, a lot of apps pick up where they left off and if you do have titanium then your back ups are retained.
Glad you're sorted.
PS: this would have had the same effect that installing system would have had, only this time you get a clean slate