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.
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.
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
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
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
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