Hey guys.
So last night I was trying to update the rom on my Nexus 9 from a 5.02 release of AICP to the latest one. I boot into TWRP and it asks me for my pass code, then I take a backup, clear the caches and try to install the rom (from the internal storage). I don't think it gave any error messages, but when I rebooted and it got to the screen where you enter the password (I'm guessing where it decrypts or something), it said something about an internal error and that I should contact the manufacturer - when I tried to put the password in it just says that settings crashed over and over.
I tried to restore the backup; as well as factory reset and install the new rom fresh; I keep getting /vendor mount issues, etc. I even tried deleting the system partition and installing the new one, still no dice.
So I'm basically dead in the water at the moment (with no OS at all haha), does anyone have experience with this or any ideas for what to do? All ideas appreciated and thanks in advance.
There may be other ways, but I would suggest booting into bootloader and fastboot flash the stock 5.1.1, factory image. Tutorial here > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Related
I am a noob looking to try out the touchwiz rom,
My 10.1 is encrypted and trying to remove the encryption using the menu option in settings- factory data reset - it just reboots like nothing happened and asks for the password (I wanted to turn off/get rid of the encryption). I get a box open and android icon for a brief moment at reboot.
Using ClockworkMod Recovery v4.0.0.4 the wipe/factory reset option selected and it errors on the mounting /data. Can't mount or format /data too.
This 10.1 retail has a locked bootloader and is rooted.
Anybody? So far not bricked, ,
got it
I used odin and followed instructions here- http://forum.xda-developers.com/showthread.php?t=1119492
I lost clockworkmod and it did not recognize my password on reboot, but it did let me wipe everything.
You might have to wipe user data to get rid of the encryption. But you will loose all ur data
<bump>
I'm having the same trouble - and no amount of flashing various stock or CWM recovery gets me to a point where I can actually format / remove the encrypted partition.
The device had been rooted - and then encrypted - and it wasn't until I attempted to reboot into recovery with CWM (hoping to perform a factory reset) that I got into a boot loop.
Days, and countless flashing later - I'm no closer. The one thing I find interesting: when I flash particular (CWM) recovery / images, and reboot - I actually get the 'pre-boot authentication' page, which still accepts my encryption passphrase. It's after this point - that I'm just staring at a black screen.
Perhaps nvflash might be the right tool for the job - so off to learn about THAT. Every day, a new adventure - and another twist down the rabbit hole.
Thanks in advance to anyone with some insight / links / tips to share.
encryption owns me
SnoWake4Me said:
<bump>
I'm having the same trouble - and no amount of flashing various stock or CWM recovery gets me to a point where I can actually format / remove the encrypted partition.
The device had been rooted - and then encrypted - and it wasn't until I attempted to reboot into recovery with CWM (hoping to perform a factory reset) that I got into a boot loop.
Days, and countless flashing later - I'm no closer. The one thing I find interesting: when I flash particular (CWM) recovery / images, and reboot - I actually get the 'pre-boot authentication' page, which still accepts my encryption passphrase. It's after this point - that I'm just staring at a black screen.
Perhaps nvflash might be the right tool for the job - so off to learn about THAT. Every day, a new adventure - and another twist down the rabbit hole.
Thanks in advance to anyone with some insight / links / tips to share.
Click to expand...
Click to collapse
I'm facing what I think is a similar problem on an AT&T Galaxy s3 i747 with Paranoid Android. I had to encrypt for work email, and ever since then it regularly reboots whenever I try to do something (~25 second effort)... when I do the factory reset, or try reflashing a ROM, it seems to reboot before the action completes... Can you advise how I might solve this?
I've already tried CWM to redo everything... Factory reset does not complete as it always asks for the encryption password once started again... I just want to get back to unencrypted please. Any ideas? Maybe ODIN CWM then try a new install? formatting my SD card? Thanks in advance...
Hi, I had the same problem as above.
I was unable to factory reset with CWM recovery as it couldn't flash the data partition or sd card and couldn't mount them.
However, using the stock recovery, the factory reset and formatting worked fine returning back to an unencrypted device.
My first post so be gentle ...
I recently let a colleague at work use my phone as a guinea pig for Exchange active sync which in turn enabled encryption on my device. In my haste to regain control of my phone and not be bound by the active sync policies he had imposed, I went straight to ClockworkMod and formatted all partitions on the device.
I then ADB Pushed an AOSP Rom to my phone and installed via ClockworkMod and have been using it encryption free for many months now and thought I had seen the last on the encryption .... Until yesterday when I fancied a change and wanted to try a Samsung based rom.
It seems that any Samsung based roms wont boot due to them needing a pin to which I have no idea of what it could be. Having formatted what I thought was pretty much all partitions of the phone and still finding signs of encryption leads me to think I'm missing something ... Bootloader maybe? ...
So I think my questions are ... Has anyone seen this before and how did they fix it. & Any one know where I could acquire an official bootloader and flashing instructions?
Thanks
Graham
Fixed .....
Ok... So after a lot of flashing ... obviously not in public parks! The problem is solved and below is my fix
1. Flashed the full rom from the below link. I chose the ODIN Copy
http://forum.xda-developers.com/showthread.php?t=2077844
2. After the full flash I still had the problem that even official stock ROM was prompting for the encryption pin. So I rebooted into the official Android recovery and did a factory reset and wiped cache. After doing the factory reset using the official recovery, the PIN Appeared to be removed
3. Then I downloaded the Odin version of Clockworkmod from the link below and flashed via ODIN
http://forum.xda-developers.com/showthread.php?t=1719744
4. ADB Pushed the Samsung custom Rom through Clockworkmod and flashed.
Problem Solved
Encryption is a nightmare!
Thanks for posting back your findings. I wish everyone did this.
I think the stock recovery does a full format of /data including /data/media (internal sdcard), whereas CWM etc actually use a recursive delete of files (linux command rm -rf) which leaves /data/media in tact (so a factory reset doesn't wipe out all your pictures and backups etc)
Possibly the cause .... I think either way the official recovery deleted something that CWM didn't.
This forum has helped me out loads so it's nice to be able to contribute back.
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
FrozenLord said:
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
Click to expand...
Click to collapse
I usually just hit the thanks tab but feel I have to than you personally for this post. After hours of messing about I found this post, flashed the TWRP recovery, wiped data and was able to flash and boot my xperia..
Thank you for sharing this info..
For others searching you can get the twrp recovery in this rom http://forum.xda-developers.com/showthread.php?t=2383800
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!
Dear readers,
I flashed TWRP 3.3.1, booted into it, wiped data, did factory reset, and installed decrypt for latest pie.
i rebooted into twrp to verify the decryption and indeed I was not asked for a password.
Then I booted into Pie and went through the account setup and while I was doing that some updates got installed by android.
To my horor when I booted back into TWRP it again asked for password, meaning android pie somehow encrypts the data again.
(Second time I did this whole process again I installed magisk.zip, so at least I have root.)
My question is:
How can I stop Android from encrypting again during the account setup process?
Greetings,
Mike
This happens to me too, the only real workaround I've found so far is to flash your zips (ie. magisk) before booting the first time.
I did flash stock image, flash twrp, boot into twrp, format data, flash decrypt.zip, flash Magisk.zip, and reboot. First thing it does is encrypt it again.
Then I tried same process but with no-dm-verity-encrypt.zip or something like that, and it said success, but still Pie decrypts again.
Then I tried previous firmware, (. 48 instead of 51), but same result. It is driving me nuts.
And no help from here so far.
Maybe I should go back to oreo, that worked OK with decrypt.
Greetings
Same problem wait solutions.
Alas, still no fix for this major problem.
What is the point of creating TWRP and other custom recoveries for X01AD when they can not be used for making backups, due to decryption problem?
So please someone with the skills to create a force decryption that actually works, help us out.
Thanks in advance,
Mike