I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
mcwildcard said:
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
Click to expand...
Click to collapse
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Rirere said:
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Click to expand...
Click to collapse
Therein lies the problem though, for whatever reason my PC won't recognise the nexus 10, despite the drivers being installed from the ADK etc.
Because of that, I can't use fastboot or anything PC based. I suspect it's because the device is spoofed as a Galaxy Nexus.
The device is currently unrooted too, so that also limits my options.
My data isn't really a problem, I'm happy to wipe everything, it's all backed up on my NAS anyway.
Isn't there any sort of physical reset button anywhere that will force a factory reset?
Managed to get the drivers working on my gf's laptop, not sure why my PC wasn't playing ball, but this is all fixed now.
Ta!
Related
I got my ouya the day it launched. Set it up. Found out that it required a Credit Card, not happy. Blah blah i properly rooted it and installed superuser and busybox, nova and several apps. Worked fine. also set up wireless ADB. tried to set up CWM Recovery, both manual and one click. with adb over wifi and wired adb. noticed that adb would always revert to Wifi, causing it not to finish setup as ouya did not connect to wifi outside of being booted. did my best to get rid of wireless adb, taking it out of the build prop and pushing it back in, etc. Nothing worked. so i did a factory reset. added busy box and superuser. worked fine for a little. then su quit working and so i redid a factory reset, and now my Ouya wont go past the WiFi Setup, even after rebooting, making sure it was connected, still managed to connect through ADB -____- and if i click continue on the wifi setup, it says "controller connected, connect more later.. etc etc" and so i continue and it goes back to the wifi and does a loop!
Any Ideas? Any way to do a full reset like flashing a tar.gz on odin with stock firmware? Please help im not happy with my ouya already. almost ready to return it.
OreBoySwaggin said:
I got my ouya the day it launched. Set it up. Found out that it required a Credit Card, not happy. Blah blah i properly rooted it and installed superuser and busybox, nova and several apps. Worked fine. also set up wireless ADB. tried to set up CWM Recovery, both manual and one click. with adb over wifi and wired adb. noticed that adb would always revert to Wifi, causing it not to finish setup as ouya did not connect to wifi outside of being booted. did my best to get rid of wireless adb, taking it out of the build prop and pushing it back in, etc. Nothing worked. so i did a factory reset. added busy box and superuser. worked fine for a little. then su quit working and so i redid a factory reset, and now my Ouya wont go past the WiFi Setup, even after rebooting, making sure it was connected, still managed to connect through ADB -____- and if i click continue on the wifi setup, it says "controller connected, connect more later.. etc etc" and so i continue and it goes back to the wifi and does a loop!
Any Ideas? Any way to do a full reset like flashing a tar.gz on odin with stock firmware? Please help im not happy with my ouya already. almost ready to return it.
Click to expand...
Click to collapse
As far as I know right now there is no way to do a full reset. Try plugging it into ethernet before turning it on and see if it goes through everything. It sounds like you're having wifi issues, which was happening prior to the last 2 updates, and it's having a hard time connecting.
Right now trying to install CWM is very much experimental and advanced, so the fact that something messed up after trying that is not OUYA's fault. Why did you install CWM anyway? There is very little reason to do so right now unless you' like to try all the new stuff while it's still in Alpha. Plenty of people working with CWM have bricked their OUYA.
You can contact ouyasupport and get it fixed through them, I'm pretty sure, but it involves sending it into them.
It kind of sounds like you may have broken the OUYA recovery and when you tried to do the factory reset it didn't actually work. I can't know for sure without messing with it myself, though, and I"m not an advanced user when it comes to CWM, so maybe someone else can help you better.
Yes, there is a way to do a real reset and return it back to "like new" condition. The thing is, since Ouya doesnt have a way to enter recovery/bootloader mode in the event that the flashing goes wrong, there's a decent chance that you can make things worse by trying it. Having said that, here's how you can do it -
# go to bootloader
adb reboot bootloader
# launch cwm
fastboot boot clockworkmod.img
# use cwm's menu and select "install from sideload", then push a factory flashable zip with
adb sideload factory_ouya.zip
then wait 5 minutes, hope your power doesnt go out and make sure the dog doesnt trip over the cable. because 1 little mistake and its a brick.
ksd
JLCollier2005 said:
As far as I know right now there is no way to do a full reset. Try plugging it into ethernet before turning it on and see if it goes through everything. It sounds like you're having wifi issues, which was happening prior to the last 2 updates, and it's having a hard time connecting.
Right now trying to install CWM is very much experimental and advanced, so the fact that something messed up after trying that is not OUYA's fault. Why did you install CWM anyway? There is very little reason to do so right now unless you' like to try all the new stuff while it's still in Alpha. Plenty of people working with CWM have bricked their OUYA.
You can contact ouyasupport and get it fixed through them, I'm pretty sure, but it involves sending it into them.
It kind of sounds like you may have broken the OUYA recovery and when you tried to do the factory reset it didn't actually work. I can't know for sure without messing with it myself, though, and I"m not an advanced user when it comes to CWM, so maybe someone else can help you better.
Click to expand...
Click to collapse
Well when i do the factory reset it does go to recovery and goes through resetting, so i know that that works, i guess i will try Ethernet. i plan on installing CWM because i want to make my own ROM and Kernel as to the best of my ability, since there isn't really any options that work. if the Ethernet option doesn't work i might just return this and buy something else. I'm glad i haven't bought anything.
Ethernet?
gianptune said:
Yes, there is a way to do a real reset and return it back to "like new" condition. The thing is, since Ouya doesnt have a way to enter recovery/bootloader mode in the event that the flashing goes wrong, there's a decent chance that you can make things worse by trying it. Having said that, here's how you can do it -
# go to bootloader
adb reboot bootloader
# launch cwm
fastboot boot clockworkmod.img
# use cwm's menu and select "install from sideload", then push a factory flashable zip with
adb sideload factory_ouya.zip
then wait 5 minutes, hope your power doesnt go out and make sure the dog doesnt trip over the cable. because 1 little mistake and its a brick.
Click to expand...
Click to collapse
Well there is through adb, but adb will not work for me as unless i can turn off the network adb it will be network- only mode. So even in bootloader mode adb trys though the network.... wait maybe ethernet will help? Stupid 5 minutes between posts... well i plugged in the ethernet but it still goes to the WELCOME -Controller Connected screen
Broken?
Well it appears that Ouya Launcher and Ouya OOBE are not working, i started getting FC errors, and adb is still only working through wifi, i managed to reboot into the bootloader, but i couldnt control the Ouya, so no CWM if best buy will let me return this, here i go because i dont like this very much.
Returned it
Biked to Best Buy to return it. Had 3 minutes left til they closed, but hey! i got my $100 back! i'll just see what money ill get at my garage sale on friday and probably ill buy a new phone since my current Tmo S2 is a pos! What phone should i get from tmo or should i wait? I know the S4 is the best. Preferably a phone with LTE
Would appreciate any advice, please.
My daughter's Nexus 7 Wifi (grouper/nakasi) is bootlooping.
[Yesterday, an app wouldn't install from Play Store (error code -24); went to go to Settings, to clear Play Store cache, but Settings wouldn't open. Rebooted, now it's bootlooping]
The device is still locked, so I'm obviously very limited in what I can do. Is there any way at all I can recover things, without having to do a wipe?
Failing that, I'd like to at least save her app data, and SD contents, before a wipe.
I've tried clearing /cache from (stock) Recovery, no change.
I can connect with adb, but only when in Recovery sideload. I can't connect with adb when it's bootlooping.
I can't flash a factory image, with wipe disabled, since it's still locked.
I tried to sideload an update, but the update fails, since they're all from->to, and it is already on the latest 4.4.2.
I tried mtpfs, but it won't mount.
Anything else I can try, please, before resorting to wiping, and losing all her app data and any pics she may have taken?
Since your N7's bootloader is locked and is on stock recovery, your hands are pretty much tied. I can't think of any solution then a unlocking and fastboot flashing a stock image.
But maybe someone with more knowledge comes by and can help you.
So, I did a wipe/reset from Recovery, which re-formatted /data & /cache.
And it still won't boot... I wonder what is wrong?
What is the recommended procedure now? Would that be to oem unlock then flash a factory image, and oem lock?
Just to follow-up - it was just less than 1 year old, so I rang Google, who did an RMA over the phone, and are sending me a replacement.
They no longer have stock of wifi-only, so are sending a 3G model. Not that I need that. I have heard that this model uses more battery even when there's no SIM in it. Hope not.
Can't fault the service.
Not sure quite what's happened, I'm assuming a hardware flash issue, but if anyone has any ideas how to fix this, do chip in.
Using nexus 7 (unlocked, but stock and unrooted) when it crashed. Since crash, it looks decidedly read only. It'll boot and you can do a limited number of things, but then it's liable to crash again. Nothing you do is stored, so if you uninstall an app, or change a setting, it'll be back to how it was before after reboot.
Used fastboot to wipe the partitions, but nothing has any effect. Doing a factory reset doesn't wipe user data. Wiping user data from fastboot does nothing. Flashing another recovery does not work, and the stock recovery remains. I can boot twrp using fastboot.
Is this just a hardware fault and I'm stuffed?
Thanks for any and all help,
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...
In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk
Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.
rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty
https://twrp.me/faq/datamedia.html
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Yo. I got the same tablet bro. Been trying to figure out a custom recovery for her. A stock ROM would be great to have and I haven't been able to find one anywhere. Might I inquire as to where you found yours? It would be a huge relief to know I can fix it if I break it lol.
encryption
If you download the Lenovo MOTO smart assistant from Lenovo support it has a resque option. I also used that to root my tb-x104f. It downloads the original everything and if you take the boot image from the file it downloads and replace it in one that has been modified from magisk it will rescue it and you will have root also thatd what I did with mine
same problem here, reflashed with stock rom. and not resloved
frankieuk said:
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Click to expand...
Click to collapse
Did you fix this issue?
I am having the same problem.
Thanks
Same problem here (my error reads "Decryption unsuccesful", but I think it's the same as yours).
After a few tries, I believe that it is a problem with the internet connection. After the factory reset, if I skip the wifi connection step, it starts normally. And it is completely usable. I can load pdf documents or apks by the usb from a computer and it runs correctly. But whenever I try to set the wifi connection, it updates something and it causes the tablet that the next time I turn it off, I find the error on the picture when turning on. It asks for a password and no matter which password you enter, then it delivers this message.
In resume, right now it is a completely functional tablet if you NEVER connect it to the internet and load anything you need via usb or bluetooth.
I tried to reset it with Lenovo Smart Assistant, but the result is the same.
I am looking for custom roms to try if it's something about the stock rom, but I haven't found any. Can anyone reccomend me a rom for Lenovo E10 X104F 2GB?
Solution: (Worked for me)
Format Data as F2FS in TWRP. (Advanced Wipe)
Then reboot and wait.