Related
100% stock Nexus 7
The device is stuck on the boot animation. Is there any way to fix it or backup data + reinstall?
snqtslyf said:
100% stock Nexus 7
The device is stuck on the boot animation. Is there any way to fix it or backup data + reinstall?
Click to expand...
Click to collapse
Boot to recovery, wipe cache partition. If that doesn't fix it, you'll have to factory reset from recovery. Data will be lost.
---------- Post added at 09:34 PM ---------- Previous post was at 09:23 PM ----------
And if factory reset doesn't work, boot to bootloader, fastboot OEM unlock, and flash a factory image.
Just do a factory reset from TWRP ^^ Install TWRP though! It will not remove internal storage!
KawaiiAurora said:
Just do a factory reset from TWRP ^^ Install TWRP though! It will not remove internal storage!
Click to expand...
Click to collapse
Unlocking the bootloader to install TWRP will wipe all data.
Oh.. I think you can sideload an image via fastboot I think. Maybe you can copy stuff from there
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
i dont know if this helps for you, but:
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
kaufikauf said:
i dont know if this helps for you, but:
http://forum.xda-developers.com/google-nexus-5/help/twrp-password-t2511049
Click to expand...
Click to collapse
Yea I saw that as I was searching for possible solutions. I was really hoping to wiping data
ryman222 said:
Yea I saw that as I was searching for possible solutions. I was really hoping to wiping data
Click to expand...
Click to collapse
just to get it exactly:
you just updatet TWRP? Nothing else?
How did you updatet?
kaufikauf said:
just to get it exactly:
you just updatet TWRP? Nothing else?
How did you updatet?
Click to expand...
Click to collapse
Correct, fastboot flash recovery recovery.img
ryman222 said:
Correct, fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Im really not sure about this,
but it could be that you have to install SuperSu and then it works
Can you boot your phone normally?
kaufikauf said:
Im really not sure about this,
but it could be that you have to install SuperSu and then it works
Can you boot your phone normally?
Click to expand...
Click to collapse
Yea boots fine runs like it always did. I might just completely wipe and see what happens.
I would try to install the new SuperSu first, if this doesnt work you can wipe later.
By the way it would be great if you post your results here, seems to be problem for older versions too.
kaufikauf said:
I would try to install the new SuperSu first, if this doesnt work you can wipe later.
By the way it would be great if you post your results here, seems to be problem for older versions too.
Click to expand...
Click to collapse
Installed, no luck.
Wiping now will report back...
EDIT: It did need to be formatted and reset.
When making a backup with twrp, what folder should be backed up? Boot, system, system IMG, vendor, vender IMG, data, cache? I need a back so I can restore current setup if I don't like this "Android N" beta update.
Before installing Android N, everything worked normally. Now it wants a password every time. Tried everything. I want to get my backup, but if I wipe data, it wipes the backup. If i transerf the backup to the phone after wiping (still in twrp), I am stuck on the Google logo. LOL
Edit: Now flashed twrp 3.0.0-1, looks fine. Copying backup to the phone.
ryman222 said:
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
ryman222 said:
I can't decrypt to mount with twrp. This worked for months prior to today after I updated to version 3.0.0.0. Now I cannot get in to flash anything. I have no password on boot or password at all and I have tried "default_password". No luck. Any suggestions?
SOLVED: Hit cancel at the password screen, then go into Wipe and then do a factory reset by swiping. Then go back into Wipe and press the 'Format data' button. You have to type 'Yes', and it will take a few seconds. After that everything should work normally.
Click to expand...
Click to collapse
The only way to save your data is to change the default password instance to an actual password and then flash TWRP
CitySlicka said:
When making a backup with twrp, what folder should be backed up? Boot, system, system IMG, vendor, vender IMG, data, cache? I need a back so I can restore current setup if I don't like this "Android N" beta update.
Click to expand...
Click to collapse
Only,
-Boot
-System
-Data
I do also cache recovery efs but not needed.
*Don't ever restore system image or vendor image.*
Works like a charm!
dontbeweakvato said:
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
The only way to save your data is to change the default password instance to an actual password and then flash TWRP
Click to expand...
Click to collapse
Thanks a ton @dontbeweakvato. This worked flawlessly, also posted your text in some other forums where people are still looking for answers You saved my data, thanks
didnt work for me
This is the only way works for my Nexus 6P.
https://www.youtube.com/watch?v=zpYVDJgusLo
will this wipe my rom
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
found something on a N6 thread that says wipe user data and it should work .
kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.
murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?
I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Gaby_64 said:
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Click to expand...
Click to collapse
Does TWRP print anything about "successfully decrypting /data with default password" in the console when it starts?
Go WIPE > ADVANCED WIPE > check the box next to "Data" > REPAIR OR CHANGE FILE SYSTEM. What does it say the file system of /data is?
Edit: Did you format /data before or after the issue happened? Never mind, you have to have formated /data afterwords if you were trying different ROMs.
ext4
i dont see the console
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
troy5890 said:
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
Click to expand...
Click to collapse
i tried as both f2fs(performance is worth it) and ext4
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Doc Ames said:
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Click to expand...
Click to collapse
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
troy5890 said:
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
Click to expand...
Click to collapse
May I ask, why are you using that version of TWRP?
Choose an username... said:
May I ask, why are you using that version of TWRP?
Click to expand...
Click to collapse
It's the only version that will boot up successfully when flashed through fastboot.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
It's the only version that will boot up successfully when flashed through fastboot.
Click to expand...
Click to collapse
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Choose an username... said:
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Click to expand...
Click to collapse
I tried but it ended up not flashing successfully
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
I tried but it ended up not flashing successfully
Click to expand...
Click to collapse
all hail axon7tool then :v
Choose an username... said:
all hail axon7tool then :v
Click to expand...
Click to collapse
Looks like I'll give that a try, thank you
Sent from my ZTE A2017U using XDA-Developers Legacy app
So I just bought this Tablet and I wanted to Root it, but I immediately noticed that in trying to flash anything, this verification thing gotme stuck in a bootloop. I looked further into it, and I need to patch dm-verity out, however, the latest .zip I tried is for Android 6 it seems, as when I tried to flash it and then let TWRP make modifications, it still got stuck in the Verification Error bootloop.
Now I flashed the original system to it again through Download Mode, and that fixed the bootloop. However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks
yanniclord said:
However, I then went into Odin, flashed TWRP, went into TWRP, tried to do as it said in the guide where it says I need to "Wipe Data", but when I try to do that it says "Failed to mount '/data' (Invalid Argument)". So what now? And does anyone here have a dm-verity patch for this tablet that supports Android 7? Thanks
Click to expand...
Click to collapse
Which guide?
ashyx said:
Which guide?
Click to expand...
Click to collapse
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?
yanniclord said:
This one
https://forum.xda-developers.com/ga...ab-tablets-t3552509/post70924135#post70924135
Oh, I recognize your name, didn't you also make the no-dm-verity script?
Click to expand...
Click to collapse
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
Click to expand...
Click to collapse
These instructions are a tad simpler.
To disable forced encryption, disable dmverity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using the FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
ashyx said:
Bit of an eye attack, but it seems you didn't follow the instructions at 5e.
It specify states NOT to wipe the data partition, but to FORMAT.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
These instructions are a tad simpler.
]To disable forced encryption, disable dmverity and mount internal storage:[/B]
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Click to expand...
Click to collapse
Hmm alright, I actually tried that before but it worked this time after I reinstalled the Stock Firmware multiple times and did multiple resets as well, thanks
So do you have a no-dm-verity.zip for Android 7 for me? Or does the one from the thread work?
Oh and, I want to flash Magisk, so shall I flash Magisk first and then no-dm-verity? I am pretty sure that is correct assumed of me.
EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
EDIT 2: As far as I remember, doesn't Magisk disable dm-verity to begin with when it flashes itself?
yanniclord said:
EDIT: Thanks for the no-dm-verity zip, will try it and I will also try Magisk Thanks for all the help, has been a while with Samseong devices for me :/
Click to expand...
Click to collapse
Will work on Android 7 too.
If you flash Magisk you shouldn't need the patch.