So I am going to RMA my phone and I thought it would be a good idea to encrypt then factory reset. So I tried this and my phone boots up and all but it still asks for an decryption key.
What should I do?
skyguy126 said:
So I am going to RMA my phone and I thought it would be a good idea to encrypt then factory reset. So I tried this and my phone boots up and all but it still asks for an decryption key.
What should I do?
Click to expand...
Click to collapse
Enter recovery, format data, reboot to bootloader, and re-install stock via fastboot.
kibmikey1 said:
Enter recovery, format data, reboot to bootloader, and re-install stock via fastboot.
Click to expand...
Click to collapse
I just reflashed the userdata partition and it worked. Thanks anyway though!
Related
Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb
I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.
Factory reset wipe everything! Including SD card.
null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?
Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...
Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.
So I encrypted my moto 4g and all went fine. However I wanted to flash and install an app via my recovery(my device is rooted and I got custom recovery but I'm on stock rom) but It kept saying it could not access the data of the phone. I figured this was because it is encrypted. I also tried restoring an older backup from when the phone was not encrypted but that would not work either. If I do a factory wipe in recovery that won't work either. If I enter the Android settings and choose data wipe the phone starts to bootloop.
What can I do to decrypt my phone?
Did you encrypt the phone using stock recovery?
No I encrypted with the custom recovery.
Have you tried to erase cache and userdata using fastboot commands?
audit13 said:
Have you tried to erase cache and userdata using fastboot commands?
Click to expand...
Click to collapse
No I have not, haven't had time to try, I assume here are some guides about it and I will look into it when I have time.
Just wanted to say that I fixed it, had to reflash the whole device with flashboot, then I re rooted it and restored an backup.
Glad it worked out for you.
I have encrypted my N5 (custom 5.1) and now I am unable to decrypt it, factory reset or wipe it in anyway from the bootloader.
Factory reset from the system's menu pretty much reboots the phone. Attempt of any kind of wipe from the bootloader fails and does nothing either.
wat do? i don't mind a full wipe, just tell me how lol.
edit: sorry, kinda wrong subforum i guess. feel free to move my topic
Crunozaur said:
I have encrypted my N5 (custom 5.1) and now I am unable to decrypt it, factory reset or wipe it in anyway from the bootloader.
Factory reset from the system's menu pretty much reboots the phone. Attempt of any kind of wipe from the bootloader fails and does nothing either.
wat do? i don't mind a full wipe, just tell me how lol.
edit: sorry, kinda wrong subforum i guess. feel free to move my topic
Click to expand...
Click to collapse
Factory reset within Android just boots into recovery and performs a factory reset there.
It should work, but if it doesn't then flash factory images using fastboot or LG Flashtool.
Ok, I see. Nexus Root Toolkit to the rescue then I guess
Crunozaur said:
I have encrypted my N5 (custom 5.1) and now I am unable to decrypt it, factory reset or wipe it in anyway from the bootloader.
Factory reset from the system's menu pretty much reboots the phone. Attempt of any kind of wipe from the bootloader fails and does nothing either.
wat do? i don't mind a full wipe, just tell me how lol.
edit: sorry, kinda wrong subforum i guess. feel free to move my topic
Click to expand...
Click to collapse
Umm... What are you trying to do when you try to format userdata in fastboot mode? Why dont you go straight to the recovery and do a factory reset from there? What are the steps you do to achive a factory reset?
My Nexus 5 is stuck in a bootloop where it says "Optimizing app x of y" and then reboots and repeats this endlessly. I'm not particularly concerned with getting the phone working, I only care about recovering the data on the phone. All the suggestions I've seen involve factory resets which wipe the data. How can I recover my data?
Is the bootloader unlocked? Did you enable usb debugging? Tried wiping cache in recovery?
audit13 said:
Is the bootloader unlocked? Did you thanks usb debugging? Tried wiping cache in recovery?
Click to expand...
Click to collapse
I'm not sure about the bootloader or usb debugging. Is there a way to verify? I have tried wiping the cache but it had no effect.
When you boot the phone, do you see the unlocked padlock at the bottom of the screen? If not, the bootloader is locked.
audit13 said:
When you boot the phone, do you see the unlocked padlock at the bottom of the screen? If not, the bootloader is locked.
Click to expand...
Click to collapse
Unlocked padlock is there, so I guess the bootloader is unlocked.
You can try flashing twrp, boot in twrp, mount data partition, and pull off data. As with any flashing process, things can go wrong which can result in the total loss of data.
What data do you need from the phone?
I have the same problem,
but the bootloader unlocks and locks again after rebooting,
I tried to flash in different ways but I didn't have any results, I did fastboot recovery twrp.img and I managed to get into this recovery, but twrp asks me for my password(i dont have any password), and if I try to format this appear cant mount/cant open cache
Do I need to change my motherboard?
If you can run Teamwin recovery then do a backup, then copy that onto your computer, then wipe data, cache, system, dalvik cache
after this, download any kitkat rom, gapps, and flash it
boot it up, install Titanium backup anow you can recover every app from nandroid backup (menu > special backup)
then backup every app again with titanium backup (menu > batch actions > backup all user apps)
Finally you can wipe your phone again and install any rom you want and recover every app with titanium backup
Why first an kitkat rom? because you can't extract from a nandroid since android 5, but the normal titanium backups work fine
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
_MOE_ said:
I have the same problem,
but the bootloader unlocks and locks again after rebooting,
I tried to flash in different ways but I didn't have any results, I did fastboot recovery twrp.img and I managed to get into this recovery, but twrp asks me for my password(i dont have any password), and if I try to format this appear cant mount/cant open cache
Do I need to change my motherboard?
Click to expand...
Click to collapse
that seems like your filesystem is corrupt or the nand itself. Your phone is not unlocked so I think theres no solution :/ yeah replacing will help
That could be the solution, but I think that's only possible when you're unlocked: https://forum.xda-developers.com/showpost.php?p=76757221&postcount=2
If the bootloader relocks itself when the phone is rebooted, the internal memory chip is damaged and will require a motherboard replacement.
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
abati said:
Hey guys,
I have a oneplus 6red rooted with magisk and twrp running oreo 5.1.11, today I decided to enter twrp and reset my phone by whiping dalvic, cache and data.
After reboot, phone screen is totall dark but the light indicator was flashing constantly, entering twrp is no succes, twrp screen is stuck like more then 10 mins. I believe that I cant enter twrp to do something about it. I have downloaded the stock 5.1.11 which is an oreo version
Did I do really something wrong ? if yes or no please let me know how to fix this.
Click to expand...
Click to collapse
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
mikex8593 said:
Try bluespark TWRP and flash your OOS zip again and report back. Maybe a magisk flash will help too.
Click to expand...
Click to collapse
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
tabletalker7 said:
This may be a side effect of A/B partitioning and no longer having a recovery partition. Remember TWRP is a part of the boot partition now
Click to expand...
Click to collapse
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
abati said:
after whiping data, phone is stuck and twrp does nothing
Click to expand...
Click to collapse
After a whipping I wouldn't be inclined to do much either!
croques said:
After a whipping I wouldn't be inclined to do much either!
Click to expand...
Click to collapse
what do you mean, could you be more clear and specifiek ?
abati said:
what would be an alternative sollution to factory reset your phone without all the troubles i witnessed.
Click to expand...
Click to collapse
Use a fastboot rom. That will wipe EVERYTHING - and guarantee that you have a usable phone afterwards
abati said:
thnx, I entered into fastboot mode, then from my pc I when into the fastboot folder to open cmd and boot twrp from there on my device, from there I followed a tutorial how to adb sideload and flash a rom from your pc. Now its working
But I dont understand why a simpel factory whipe through twrp caused all of this, I only wiped dalvic, cache and data.
Click to expand...
Click to collapse
You probably wiped system that's why you had nothing to boot into
yldlj said:
You probably wiped system that's why you had nothing to boot into
Click to expand...
Click to collapse
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Its the easy answer, say that you wiped system or such.
If you wiped Data with Magisk installed, without flashing the stock kernel, you won't be able to boot, since Magisk stores stuff necessary to boot on Data.
Usually, people is stuck on a infinite bucle on TWRP after this, you couldn't even enter TWRP? that's new. The issue you're telling sounds like you changed slot in TWRP somehow to an unused one or something like that, never heard of that.
abati said:
i am almost sure that it was data and dalvic cahce and not system, that is what i also explained in my first post.
But how are you sure that it was system wipe ? did you factory reset your op6 multiple times without issue through twrp ?
phone is fixed btw
Click to expand...
Click to collapse
Yeah I have wiped data in twrp with no issues. TBH it just sounds like there was no system to boot into. Wiping data is just that and shouldn't make the phone unbootable. Also you fixed the issue by flashing OOS which makes me believe this also. If you want to factory reset your phone the best way is to do it through settings.