Related
Hi folks,
For some stupid reason, I tried to encrypt my phone from within TouchWiz Security Settings. I entered a password for the encryption, and as soon as I clicked start, the process stopped and an error saying "com.android.systemui has stopped" has appeared. If I click OK it pops up again. Restarting the phone gives the same error, and I can't actually use the phone at all, as the error message keeps popping up even if I try to enter the correct password.
I tried reflashing the rom, wiping data, cache and so on, and the same error message pops up as soon as TouchWiz loads up. I don't know how to transfer another rom from my computer to the phone from within CWM (I don't see my phone's storage from within windows).
I thought I'd do a complete unroot, but the stock firmware available for this device is older than 4.4 (which is what I have because I'm using Enewman's SRx 4.0). Everywhere I read it says "DO NOT DOWNGRADE".
I'm not sure what to do, and I have very limited expertise in this matter.
Thank you for all your help folks!
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
audit13 said:
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
Click to expand...
Click to collapse
Yep, I was rooted and using CWM. The phone still boots to TouchWiz, but then the error comes up and I can't use the phone at all. I tried formatting the system before installing a new rom too...
So I used adb to sideload CyanogenMod, and flashed it. That seems to have helped the problem
So the in call volume in AOSP ROMs (tries carbon, quantum, cm11) is way too high. Tried reflashing any other kitkat based touchwiz ROM but immediately upon first boot I get prompted to insert the encryption password. When I do, it asks it again. Is there any way to somehow get a touchwiz ROM to work on my phone now? I alwaya do clean installs. Thanks guys
It is my understanding that encryption requires stock recovery.
What bootloader is on your phone?
Looks like I'm on the UCUFNE4. every touchwiz ROM I install asks for decryption, and all the other ROMs are installing OK..
Have you tried using Odin to flash a stock ATT KK ROM?
Edit: nevermind, looks like there is no 4.4.2 ATT ROM on sammobile.com. I assume you already tried wiping cache, dalvik, and data.
Yes I have tried to wipe everything. Even internal storage. So then I had to sideload a ROM using adb. I really appreciate your input!
It sounds to me like the data portion is still encrypted. Were you able to use fastboot commands to erase cache, data, and system before flashing a new ROM?
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
tequilaboom said:
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
Click to expand...
Click to collapse
It might be but I have never compared the two methods.
Are you able to issue fastboot commands to your phone?
I have never done fastboot but I could try using it. What should I do with fastboot?
tequilaboom said:
I have never done fastboot but I could try using it. What should I do with fastboot?
Click to expand...
Click to collapse
Boot the phone into download mode, connect the phone to the computer via USD, let it install the Samsung drivers. You will also need the necessary ADB/fastboot files from here: http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Boot to an command prompt in Win7 or Win8. Navigate to the directory where you installed the ADB/fastboot files and type this: fastboot devices and press enter. Hopefully, your device will appear.
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
tequilaboom said:
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
Click to expand...
Click to collapse
Here's a good guide:
http://forum.xda-developers.com/showthread.php?t=2225405
alright I followed the guide, but still no effect
Did the fastboot commands work?
Did you try erasing the userdata partition? Did you try formatting the userdata partition?
I apologize, I should have said that I had no success even after trying to follow the guide. I attempted to use fastboot but when trying to detect my device, nothing showed up in that command window. ADB works no problem (detects device). Again after several tries of formatting the data partition (and everything else), every touchwiz rom asks for the encryption password. However, now when I enter it, the green android with gear appears, and then the device restarts. touchwiz now asks for the decryption password once again....
So typing fastboot devices didn't list anything? Were you in download mode?
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Ran into almost the same thing last night (not using flashfire, but with the factory flash-all.bat). Forgot to clear my theme and got the system UI error with everything borked. Even had the invalid password in twrp.
I hate to say it, but I had to just flash the factory image with a wipe and start everything over. Lost all my pics and music from the few days I had the phone. I have now learned how not to update in the future.
IrocD said:
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Click to expand...
Click to collapse
What a mess hahah! It sounds like your password file got corrupt; doing all that dirty flashing is messy. If I were you I would connect the phone to a computer and get off what data you can (most stuff is cloud now days anyway). And flash a 8.1 stock factory image using fastboot on the bootloader. You can never go wrong with flash a stock factory image. Yes you loose your data, but you get a working phone haha. If your really worried about data see if you can get MTP to work and transfer it off.
Dumbass me
Yep, that was me yesterday. Genius me sideloaded the 8.1 OTA without disabling my Substratum overlays and so I was met with the "System UI Tuner has stopped" message. Then an automatic reboot to the bootloader asking me to either "Try again" or "Factory reset phone". Guess what I had to do to get my phone working again? Had to factory reset that sh*t.
Oh well, at least I made sure to unlock my bootloader this time around before setting up my phone.
But to be fair, would've been f*cked either way even if I had waited for the OTA because it's essentially the same thing as the zip file anyways. Lesson learned: disable Substratum when you update your sh*t.
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Strange. I didn't disable my Themes and I had no issues at all sideloading.
fantasy2c said:
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Click to expand...
Click to collapse
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
I only update once a month when a new patch comes out.
I set my apps to not auto update
After a new patch comes out in the first week of the month I
-disable the overlays and remove them
-update swift black and compile new overlays
-update all my apps
-adb to recovery and flash ota
-apply new overlays
- reboot and good to go
I have done it before to you can just boot TWRP as long as you have that rescues zip on your flash drive you can do it that way too
rajlulla said:
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
Click to expand...
Click to collapse
Thought I was screwed, Thank you so much for this post.
Try formatting your internal memory using TWRP. It should be "formatting", no other type of wipe will be sufficient. Then flash your favourite ROM and enjoy!
phone encrypted.
all started one day, i was 0% battery, phone shut down itself, charged, turned on, the first password of encryption is ok, the OS password of the lockscreen GIVES ME ERROR.
i wonder, WHY? i thought i can use the twrp fix to erase the password inside the OS, ok, i try:
1) removed the 5 files with the twrp file manager, rebooted, NOTHING, after the first password accepted the boot logo is FOREVER going.... stuck.
2) tried to dirty flash the same rom i have ( a resurrection remix 5.8.5 by pranay) , nothing, same result
3) tried to format wiping data, cache, dalvik, nothing.
ok so i said myself UPGRATE TO OREO ROM, i boot into twrp ( twrp asks me the password, i enter it.. and WORKS! i don't know why the SAME password no more works into the OS) and with the MTP i transfer all mi video and pictures. ok!
i flashed the NEW twrp 3.2.1 for oreo ( i had 3.1.1.), i download some custom rom oreo, 2 resurrection remix and AEX, i wipe as usual, i install the aex and all works but i do not see the option to add the FINGERPRINT, mmmhhh in the telegram group someone told me that i "need to encrypt" to make the fingerprint option APPEAR into the OS..... ok no problem, i CAN do it! i WANT to do it! i can't live without encryption for privacy reasons. i charge the phone, press on encrypt and it reboots, i see the RR logo, 10 seconds later i am int othe OS. yes... but STILL UNENCRYPTED
i try to change the rom, new formats, new roms, SAME PROBLEM. i discovered that maybe the data partition was ruined, ok i did several "repair", i did several changes to f2fs and return to ext4 .... but sometimes i got some strange errors when trying to change the filesystem TO f2fs.
then i tried to flash the STOCK ROM follwing this guide
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
i made it all correct, now i am on stock s244 rom, in this rom i can use fingerprint but the encryption password bug is STILL PRESENT, it simply does not encrypt my phone if i press to encrypt! made a lot of tests, repair, change file system of data..... NOTHING HELPED ME. ah yes...... at a precise point into the OS i see that my phone is encrypted. WHAT?
so i boot into twrp and it asks me the password i enter it, but it is WRONG. wrong? NOT POSSIBLE it is the same....the same! i tried a lot of password like password.... default_password, 123456,0000,000000 ........
to recover my twrp i used the command "fastoboot erase userdata", it worked, now i am without a "fake" encryption. i continue to do tests, sometimes my file system showed into the twrp in the wipe menu... is showed as "auto", sometimes as "emmc" ........ MMHHHHH never seen these kind of file systems! so i changed them every time to ext4!
then i tried to flash back my "old" rr rom nougat 5.8.5 , it works, in this rom i see the FINGERPRINT OPTION, but the same bug of impossible encryption at reboot.
- so i think i can try to flash the old twrp 3.1.1 because maybe the latest one is BUGGED! maybe! i flash it....keeping the OREO rom, and still can't encrypt.
- so i try to also flash the 3.1.1 twrp... and another clean instlall of RR nougat, i do all wipes every time, all precise, no dirty flash.... and with rr nougat i CAN use fingerprint but NO encryption.
i wonder ......... i use the SAME twrp image i used for months! same file! my file.
i use the SAME ROM ZIP rr 5.8.5, why in this moment i have a "different" configuration than before? filesystem is the same ext4.... but the phone still does not want to let me encrypt it! and someone must show me the REASON WHY with all oreo roms the user cannot use the fingerprint scanner ( there is no option into the os!) without to use the encryption?
I HAVE ALWAYS USED FINGERPRINT ON OTHER PHONES WITHOUT ENCRYPTION.....
now i have 2 solutions:
1) keep the RR nougat, unencrypted BUT AT LEAST with fingerprint unlock.
2) use the RR ( or any other oreo) rom but unencrypted, and WITHOUT the possibility to unlock with my finger! grrrr!!
please give me your advice, your opinion how is it possible i tested so much different configurations, mxed different twrp, different roms, changed data file system from ext4 to f2fs and the opposite, tried to "repair" file system....... appeared random ENCRYPTED twrp but with an "impossible to know" password.... i also flashed the stock rom with the fastboot command following the guide on xda i posted at the link, i feel really empty and without possibilities to fix this problem.
but as i can remember all started with the phone shut down at 0% battery! from that point my password has never been accepted anymore!!! i was LOCKED OUT from my phone, to be precise not my full phone because the password WORKED to unlock the encryption! ( i recoveredall my files!) but the OS refuses to accept the "same" password i used to unlock the encryption... it is very strange!
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
cd Downloads
Click to expand...
Click to collapse
C:\Downloads\platform-tools
Click to expand...
Click to collapse
Could be somewhat different, depends on where you have your Downloads folder.
adb devices
Click to expand...
Click to collapse
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
adb kill-server
Click to expand...
Click to collapse
adb reboot bootloader
Click to expand...
Click to collapse
Now, use:
fastboot oem unlock
Click to expand...
Click to collapse
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
fastboot flash recovery r.img
Click to expand...
Click to collapse
fastboot boot r.img
Click to expand...
Click to collapse
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
Go into "Reboot" Menu, and chose recovery
Click to expand...
Click to collapse
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Go into "Wipe" ,chose "Factory Reset", then go back and chose "Advanced Wipe", now select the data partition, and chose to change the file system. Chose "f2fs"
Click to expand...
Click to collapse
Now, go back and into the Reboot menu, Chose Recovery again.
Go into "Wipe" again, "Advanced Wipe" -> Select Data Partition only -> Chose Change File System-> Chose ext4-> Go Back into Main menu
Click to expand...
Click to collapse
Chose "Reboot"-> Chose Recovery again.
Click to expand...
Click to collapse
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Go into "Wipe" Menu again -> Chose "Format Data"-> Type yes and accept.
Click to expand...
Click to collapse
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Main Menu>Reboot>Recovery
Click to expand...
Click to collapse
Go back into the Wipe Menu->Advanced Wipe-> Select data Partition-> change file system->Chose ext4
Click to expand...
Click to collapse
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Go to Advanced Wipe->Select System Partition-> wipe it.-> Back to the Main menu
Click to expand...
Click to collapse
Now it's time to flash Stuff!
- Flash your Rom
- Depending on what Android Version you're on, flash your desired Custom Kernel which should be compatible with your Rom.
- Flash Gapps, if desired.
- Flash Magisk or SuperSu for Root, if desired.
- Wipe Dalvik and cache. Now go and reboot
Click to expand...
Click to collapse
thank u, i will test it within a few days!
just a doubt.... when u say to put the recovery image here C:\Downloads\platform-tools
i simply generally put the files i want to flash into the folder called "minimal adb and fastboot" becuase i use that way, is it ok?
and i wonder why to use this command "adb kill-server", i've never used it... and why to priorly use "adb devices" ....jus to see if the phone is read by the pc?
ok.. but i suppose the command "adb reboot bootloader" does not require to kill the adb server.... i've never read to do it.
and last thing.... how do you think that this method would save me? it seems just another option to flash the stock rom.. but i already did it followinf the guide i linked, and i also upgraded at the last OTA within the OS....
sm00th4f3 said:
Now it's time to flash Stuff!
Click to expand...
Click to collapse
thank u bro! u are MY ANGEL now it works!! u solved my problem!
realista87 said:
thank u bro! u are MY ANGEL now it works!! u solved my problem!
Click to expand...
Click to collapse
You're welcome. I had to learn how to solve this the hard way....glad that i could help you!
Rocking RR Nougat+Magma Kernel= Best Combo for now
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
realista87 said:
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
Click to expand...
Click to collapse
Some options aren't working and are still present in the rom.
Battery life on Nougat was pretty good for me. 13hours of sot daily under heavy usage.
sm00th4f3 said:
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
Could be somewhat different, depends on where you have your Downloads folder.
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
Now, use:
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Now, go back and into the Reboot menu, Chose Recovery again.
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Now it's time to flash Stuff!
Click to expand...
Click to collapse
The file is not available anymore - do you know where I may be able to find it?
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
fingerprint not showing
Lavesh05 said:
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
Click to expand...
Click to collapse
did you find a solution , I'm having the same problem
Same problem for me.... and nothing works.....
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.
tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.
Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse
What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.
@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.