Hi, desperately in need for your guys help. Thanks.
I have a Samsung S3 running Hyperdrive. I've used company email so the memory was encrypted per company security policy. I decided to flash to a newer version of Hyperdrive yesterday and after flash with TWRP, I found that when turning on it displayed the initial logo and ask for password to boot into the system. The problem is that it does not recognize the password I put in as correct one. I am positive I used the right password. Tried to wipe, format and reinstall 4 times with the same results.
Really frustrated. And please help!
Super wipe, format internal & external sd and then flash a full stock rom with odin, see if it will boot then.
Related
Hello,
I am new here so I apologize if this has been sked before.
I had cm9 stable version installed on my phone, and it was working fine. On Thursday, I changed my lock pattern as it had no lock on, but I forgot the pattern I put in (I tend to make it complicated) and entered it wrong many times that it asked for my google account and password, but when it got to that point, it started rebooting and it got stuck on the cm robot, and whenever it gets to the google account thing, it goes back to the robot and so on. Then I flashed a stock ICS rom using Odin hoping it would fix the issue, but it got stuck on the glowing s screen. The phone isn't rooted anymore. I tried wiping cache partition but that didn't work. My biggest problem is that I didn't back my phone up and I have important files that I need. Is there a way to fix this issue?
I would really appreciate your help. Thanks!
asjk94 said:
Hello,
I am new here so I apologize if this has been sked before.
I had cm9 stable version installed on my phone, and it was working fine. On Thursday, I changed my lock pattern as it had no lock on, but I forgot the pattern I put in (I tend to make it complicated) and entered it wrong many times that it asked for my google account and password, but when it got to that point, it started rebooting and it got stuck on the cm robot, and whenever it gets to the google account thing, it goes back to the robot and so on. Then I flashed a stock ICS rom using Odin hoping it would fix the issue, but it got stuck on the glowing s screen. The phone isn't rooted anymore. I tried wiping cache partition but that didn't work. My biggest problem is that I didn't back my phone up and I have important files that I need. Is there a way to fix this issue?
I would really appreciate your help. Thanks!
Click to expand...
Click to collapse
If you have CWM installed, you can mount the sdcard in the Mounts and Storage menu, but I don't remember if that sdcard was for internel or external.
Did you try wiping Dalvik cache in Advanced menu (Also CWM)? If you do, wait 5-10min for it to boot up.
Flash Siyah kernel, boot into recovery then mount USB and backup your files.
Then just simply wipe/install the rom zip of your choice.
RhythmHack said:
If you have CWM installed, you can mount the sdcard in the Mounts and Storage menu, but I don't remember if that sdcard was for internel or external.
Did you try wiping Dalvik cache in Advanced menu (Also CWM)? If you do, wait 5-10min for it to boot up.
Click to expand...
Click to collapse
The problem with this is I lost CWM after I flashed the stock ICS rom. It's not rooted anymore
samsung nexus mobile inform about bluetooth
Samsung Neksus Mobile Bluetooth him when I've been in my Bluetooth Paring and does Trnasfer a file from your mobile When the file reaches the Dosre mobile but no files in your mobile when sixth to Resive does not Resive Pljh Suchses Help Me I've ever had in bringing Pljh Help Me kosice But of what I do is I just did a reset two Time
plz help me sir
asjk94 said:
The problem with this is I lost CWM after I flashed the stock ICS rom. It's not rooted anymore
Click to expand...
Click to collapse
boot to stock recovery and perform factory data reset.
You will lose, sms, installed apps etc but all data stored on your internal and external SD will be safe
Swyped from my Samsung Galaxy SII
TheATHEiST said:
Flash Siyah kernel, boot into recovery then mount USB and backup your files.
Then just simply wipe/install the rom zip of your choice.
Click to expand...
Click to collapse
Thank you! I will try that now and let you know if it works.
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 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
Hi everyone, I am new here but have been an active user over on Crackberry for many years.. Here's my story
I have a galaxy S4 (SGH-i377m)
Rooted via Odin.
Android 5.0.1
Just recently (since buying my Priv) I decided to flash stock marshmallow. I found gapps and the rom that was compatible.
I restarted into recovery (twrp) and made a backup, I then moved the backup recovery to my desktop computer so it wouldn't take room on my phone. I then moved my new rom, gapps, and Subeta, to my phone internal storage, wiped phone, dalvik, flashed all 3 zips but the rom failed to install. I tried everything, unfortunately formating the phone, currently have no operating system and the phone is stuck on the boot screen.
The phone is also not discoverable by my desktop so flashing the recovery wasn't possible.
I have since moved recovery from desktop to media card and flashed off the media card, that failed.
After many tries and wipes and formatting I decided to try CWM. Using CWM everything flashed but my recovery. Again, phone is stuck on boot screen.
I really don't know where to go from here.
Any help would be much appreciated!
Thanks
Brent