I encrypted MZ601 a few weeks ago, it was successfully done but when the password was asked I cannot enter it 'coz AOSP keyboard was not responding.
Then I have tried various things like:
restoring from a backup <- failed,
factory reset <- failed,
wiping the system <- successfully done but the encryption was still there,
installing cm 10 & 10.1,
tried to flash stock rom using rsd lite but this error is displayed "Failed flashing process. Unable to retrieve interface handle."
Until I have read somewhere that I need to flash the correct gapps for the cm version I have, I did it and it's now working but every time I go to play store I get "no connection".
Now, I want to remove the encryption through factory data reset (I also tried clearing credentials as it was suggested by a post I have read) but then the encryption was still there. Someone suggested that I need to fastboot the stock images but when I have entered adb reboot bootloader it says "error: device not connected" (I have even used the usb cable that came with MZ601), apart from that I also don't know what stock image should be used with MZ601 bought in Middle East.
Related
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.
Hey Guys!
I have rooted 3 other GS3's using the method listed here:
http://theunlockr.com/2013/04/02/how-to-root-the-verizon-samsung-galaxy-s-iii-running-android-4-1-2/
All other roots worked great! I was able to flash TWRP (I realize that the specific tutorial above calls for CWM instead of TWRP) and then install a CyanogenMod ROM. However, this time it did not go well.
I forgot to enable USB debugging before flashing VRALEC the first time, and when I went to run TWRP (2.7.0 for d2vzw) I realized that it did not mount the file system I thought that this was unusual and then realized that I need to enable USB debugging. I completely unrooted the phone and installed stock recovery and rom (VRBMF1, Android 4.1.2) once this was done I figured that I would go back to a personally tried and true version of TWRP (2.5.0 for d2vzw). At this point I was careful to ensure that I enabled USB debugging before proceeding with the root process.
With TWRP 2.5.0 I was prompted with a password. This befuddled me and upon some reading on the forums I came across a solution that worked for others but NOT ME. (Essentially you clear the cache and to a factory reset 3x in TWRP recovery and it will stop prompting you for the password and mount your file system correctly). For me I was unable to mount the cache for dalvic-cache to wipe it and factory reset does nothing.
I have rooted and unrooted my phone approx seven times trying different versions of TWRP, CWM, and even trying to use a seperately downloaded VRALEC file just in case if mine had an error.
I also came across this thread (below) and it did look somewhat promising however it is for android 4.2.1 and I don't want to mess up my phone any more than it already was. I am getting similar (not exactly the same) errors in my TWRP. I also made sure to use the same bootloader that I used on other 4.1.2 android systems in addition to using the d2vzw version of TWRP (It is for this reason that I am not sure that flumpster's comment applies to me). I figured that I would include this information just in case it was helpful:
http://forum.xda-developers.com/showthread.php?t=2228447
Any Ideas? I am really looking forward to trying Liquid Smooth 3.0!
Just a quick addition: I was able to use Casual's root method however I am still running into the password prompt in recovery and 3 wipes is not getting rid of that password prompt..
Thanks in advance for any help!
Hello
Really bad morning.
Woke up to find my OPO (was running COS 12.1 with TWRP), which I had plugged in to charge overnight, stuck on an android screen which said please enter your password. I entered my Google account password and then the next screen says, decryption unsuccessful. "Your password is correct but your data is corrupted. You need to factory reset your device and once you reboot you will have an opportunity to retrieve data backed up with your Google account".
I tried to reboot, just to make sure, and the same set of screens reappeared.
I tried to boot into recovery. The 'teamwin' screen kept flashing to no avail.
Entered fastboot. Flashed recovery, TWRP-2.8.7.0-bacon.
Tried to factory reset but the prompt flashed an error as follows:
'E: Could not mount /data and unable to find crypto footer' and then a series of others, but " could not mount '/data' " was repeated over and over
I'm still stuck here. How to get out of this situation?
PS: When I try to look at the mount options in recovery, the internal storage is labelled as 0 MB. This is scary.
I'm more screwed than you are. Twrp 2870 does not properly support encryption. Great to know an official release is that broken, right? Flash an older twrp, I believe 2860 or 61 are what you want. Try to reflash your cm zip. You're going to have to resetup your device but your internal sd should be fine, it says 0 mb because it's not decrypted so it can't read it. Then you should be okay... Well, except I've never seen that screen you described in the first paragraph. But that usually related to apps, not your internal sd. Good luck. I've accidentally erased all my system and data so I can't adb flash and can't flash from internal sd. My last hope before reformating everything and losing my pictures is to install via USB OTG. Which you could also do.
Good luck
Sent from my Nexus 5 using Tapatalk
Hey, I just found out that there is a way to flash a system image via fastboot! This is why I buy unlocked developer minded phones! If only OP hadn't dropped the ball on the OP2 (I actually got an invite which I didn't even use).
Anyway, go here: https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
and scroll down to "The Bad" In ORANGE text: 2. Recovering from no OS installed and no access to TWRP, fastboot does work.
Since TWRP is basically useless for us, I followed the instructions. I flashed everything EXCEPT the userdata img. AND, instead of flashing the extracted recovery, I just reflashed TWRP 2861 which I have on the PC.
Unfortunately! All my pics are gone. Pretty sure removing encryption with TWRP (before reading it was broken) did it. Try installing a good ROM via USB OTG and let me know if that saves your internal sd. I'd love to know for the future.
Hi,
last month I received an OTA update on my stock OPO Cyanogen 12.1, ever since then my settings app have disappeared (cannot access it at all, not even from safe mode)
a week ago I started receiving an OTA notification to update to the latest firmware (20MB download) (I think it's Yog4pas3jl)
anyway I was not able to update it, i would get booted back into recovery (OnePlus recovery)
*this phone does not have its USB debugging let alone developer options enabled.
in recovery I attempted to factory reset the phone (after half way attempting to unlock bootloader using Android SDK, Universal ADB and CMD)
now it appears that my phone has been "reset" but at the selecting language screen I keep getting Unfortunately CyanogenStats has stopped, and also getting Unfortunately Setup Wizard has stopped working (after tapping on language)
I can't use my phone now as I can't get past the setup wizard,
it does not appear that I am able to boot into recovery as well, please help me!
*UPDATE able to enter Cyanogen Recovery, tried wiping cache/factory reset, still stuck at Setup Wizard has stopped working. Oh no..
Try flashing a custom recovery and wipe dalvik+chache+data (doing that will not delete your sdcard). I also got such FCs in the past and that fixed it for me.
Try to flash system partition (or full firmware) via fastboot. Just follow this guide: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471, "8. How To Flash The Cyanogen OS Fastboot Images".
P.S.
You could get full firmware here: http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.