Related
Hi guys,
I've been running custom AOKP rom and decided to return back to stock.
I have the rogers version of the M8, and intended to flash a stock TWRP backup of someone's rogers save.
I made the poor decision of relocking and unlocking the bootloader again, leaving me without a functional OS and with only fastboot and TWRP recovery available to me. As a result, I can't get the rogers backup folder onto my phone ( I don't have a miscro SD), and the only other option I see is to manually push each file in the stock TWRP recovery with ADB to my phone, but I'm horrible with anything that involves command lines.
Any suggestions to get me out of this situation would be great. My end goal is to get the stock ROM / kernel running so I can get OTA's.
Edit: Solved by doing an advanced wipe and format in TWRP, and I flashed a stock Rogers nandroid
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
redpoint73 said:
Just adb push or adb sideload a stock rooted ROM to your phone. Just a single command line.
If you want OTAs, you will also need stock recovery. But my recommendation is that OTAs have no place on a modded device.
Click to expand...
Click to collapse
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Those two lines are repeated a couple times in the error screen.
It looks like I need to flash some form of backup but am not sure which one will hard reset my phone to stock from this scenario.
Flashnova said:
I've tried flashing a ROM and unfortunately I get stuck on the boot animation.
Click to expand...
Click to collapse
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Flashnova said:
Attempting to wipe my phone through TWRP before the zip install yields a failure:
E: Unable to mount '/data'
E: Unable to mount internal storage
Click to expand...
Click to collapse
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
redpoint73 said:
Which ROM? How did you try to flash it (how did you get it on the phone, did you adb sideload?)/
Select "Mount" in TWRP main screen and make sure data is checked (cache should also e checked by default). If so, and still getting this error, di you by chance try to factory reset in bootloader (not TWRP)?
Click to expand...
Click to collapse
I flashed dirty unicorns 4.4.4. I had a 2gb SD card which managed to get it to the phone (the 2gb isn't enough to move the system backup).
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Flashnova said:
I can't check Mount in the settings and it remains unchecked, and yes, I did hit the factory reset in the bootloader thinking that it would help me (I assume this was another bad decision).
Click to expand...
Click to collapse
Yes, that was a bad decision. But probably not one that you could have known about. Doing a factory reset in bootloader on a modded M8 corrupts the internal memory. This is your main problem right there.
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
In the future only do a factory reset within the OS (in Settings) or in recovery, not in bootloader.
If you've gone through this much, I'd highly recommend getting comfy with a few command line commands. These may very well save you some time and additional headache (speaking from experience).
After recently running into issues with my newly purchased Roger's M8, I needed to restore to stock as well. Honestly, I followed these instructions to the T and it got me out scrape-free.
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods (in TWRP, Restore, Select the pushed backup file).
Good luck, and as long as you've got recovery/hboot looking back at you, you should be fine.
redpoint73 said:
If you have a Windows PC, connect the phone, go to Device Manager and find the phone. Then select the option to format the memory.
Click to expand...
Click to collapse
I'm not too sure where that option is located, would you know how to get there?
esuohe said:
But, note Step #6 may require you to "adb push" your unzipped folder. And that's it.
Once you've ADB'd the massive nandroid backup, you should be out of the woods
Click to expand...
Click to collapse
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Flashnova said:
I'm not too sure where that option is located, would you know how to get there?
Click to expand...
Click to collapse
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Flashnova said:
After pushing the folder to my device I receive "protocol failure", so the push isn't working unfortunately.
Click to expand...
Click to collapse
You aren't going to be able to write to the memory when its still corrupt.
redpoint73 said:
On Win7, go to Start Menu, use the search function at the bottom that says "Search programs and files" and type "Device Manager".
Or go to Start Menu>Control Panel>Hardware and Sound; and under "Devices and printers" you will see Device Manager.
Click to expand...
Click to collapse
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Flashnova said:
Device manager does not provide a format option. Perhaps you mean disk manager? If I do format it will I have to somehow reinstall the android system?
Click to expand...
Click to collapse
I've often read it described as Device Manager. Can't personally say from experience as I've never actually had to do it myself, but seen this described on XDA quite a few times. If the option comes up in Disk Management, that should be fine, too.
Formatting internal storage should not affect the Android OS, as its a separate partition (note how Windows is only reading the internal storage as around 25 GB of the total 32 GB). But you have to re-install a ROM anyway, as you presently do not have one installed.
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?
Dear XDA, I could really use your help.
I have a stock LG Nexus 5x (bullhead/7.1.1) which recently started to fail to boot properly as it never loads past the coloured animations on startup and often stops. This sounds like it may be the boot-loop problem.
I have not rooted the phone, unlocked the boot-loader or flashed any recoveries. I have not enabled USB debugging and can't now because it won't boot.
I am looking at my options to recover the data from this phone.
I can get to the fastboot screen (where the fastboot command line tools see the device, but adb does not). I can proceed to the recovery screen and have tried clearing the cache with no luck.
I am considering trying:
Booting a fastboot recovery image
(eg fastboot boot recovery TWRP.img)
Applying a rescue OTA image
Will these methods void the phones warranty?
Will these methods even work (given the bootloader is locked)?
Can the images be recovery images like TWRP or does it have to be some stock/non-custom image?
Does the rescue OTA require adb/usb-debugging to be operational?
Will the data on the phone still be intact using these methods?
As I am cautiously working may way through this to firstly recover my data, secondly recover my phone., any advice would be greatly appreciated.
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
https://developers.google.com/android/ota
Sent from my Nexus 5X using XDA-Developers Legacy app
Commodore 64 said:
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
Click to expand...
Click to collapse
Unfortunately I had not set-up any syncing/backup process on the phone. In the future I will.
Although I don't recall what encryption settings were originally configured, I didn't have to enter a password in the middle of boot, and was only prompted to swipe in. So I think it wasn't encrypted.
So I attempted to sideload an OTA image via:
adb sideload bullhead-ota-n4f26i-06953aec.zip
then rebooted, however the phone still does not successfully boot any further. I must have really broken this one!
Are there any data recovery methods if a factory reset is applied? if I take it in to a repair agent under-warranty, do they typically wipe your data anyway?
Also, do I need to remove this OTA image if I am to return it for repair under warranty?
In a futile/desperate attempt to try to further recover my data, I have attempted to load my Nexus 5X into the stock recovery mode, then experimented with adb when using the 'apply update from adb' option. This exposed a subset of adb commands which appeared to work (eg adb devices, adb sideload etc). I was hoping to be able to run adb shell or adb pull remote local and recover some data... however I only encountered errors.
./adb shell
error: closed
./adb pull /storage/emulated/ /backup
adb: error: connect failed: closed
I assume this is expected (due to the stock recovery adb limitations, but thought it was worth a shot). I am considering exploring the fastboot options (eg fastboot boot recovery recovery.img) I suspect these are also likely to fail/wipe data. Has anyone got any suggestions/ideas or am I just wasting my time?
This just happened to me yesterday, and I got the single file I needed off the phone today. I fought with the thing for hours yesterday. First you have to clear the cache and sideload a new bullhead zip file (as documented elsewhere). That isn't all, though. After several tries, I noticed that I got farther along in the boot if I let the phone sit for a while. So, on the theory that there's a loose solder connection somewhere and/or heat buildup, I put the phone in the freezer for a few hours (not my idea; found it on reddit). This worked, but only if I also tapped the back of the phone with my knuckle before booting. As I said, success today and I'm all smiles. I hope this helps someone else.
The phone, by the way, is bricked as far as I can tell. And my backups are going to be a lot more comprehensive from here on.
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..
Hi,
I'm using a Poco F3 with latest stable Xiaomi.eu 12.5.3.0. With older phones, I could avoid having a pattern/password while still using the finger print sensor by deleting the file at "data/system/locksettings.db". Since it is something I have done many times with other Android phones, I didn't expect it could be a problem, but after deleting the file, the data folder is encrypted and I have no way to decrypt it.
After deleting the file and booting into MIUI as usual, all my apps says "wait until your device is fully rebooted before opening apps". I can open system apps like the clock or the weather, but that's it.
Things I've tried:
Factory reset from the device settings. After pressing the button, the screen gets black and after 2 seconds it gets back on the settings menu.
Change the security settings. Both changing the pattern, the password or leaving it without security. It only affects how the device is locked, but nothing else.
Using adb, I have no permission to see the data folder and the sdcard folder says it does not exists.
From TWRP, if I had set any kind of lock while in Android, it will ask for it (such a pattern or password). But whatever I input, it always says "Failed to decrypt user 0". I can cancel the input and enter normal TWRP but with the data folder encrypted.
I've tried to Wipe>Format Data, with the following error message:
Code:
/system/bin/make_f2fs -d1 -f -0 encrypt -0 quota -0 verity -w 4096 /dev/block/sda35 27865079 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Filed to mount '/data' (Device or resource busy)
In Wipe>Advanced Wipe>Repair or Change File System (to the Data partition). If I try to repair it gives me error 255 again. If I try to Change File System to F2FS, again "Error chaning file system".
I cannot flash Xiaomi.eu again from TWRP because I cannot move the file to the phone through adb "permission denied".
What other options do I have?
Thanks in advance for the help.
flashing stock miui theres a fastboot flash userdata that might do the trick.
guillermo1996 said:
Hi,
I'm using a Poco F3 with latest stable Xiaomi.eu 12.5.3.0. With older phones, I could avoid having a pattern/password while still using the finger print sensor by deleting the file at "data/system/locksettings.db". Since it is something I have done many times with other Android phones, I didn't expect it could be a problem, but after deleting the file, the data folder is encrypted and I have no way to decrypt it.
After deleting the file and booting into MIUI as usual, all my apps says "wait until your device is fully rebooted before opening apps". I can open system apps like the clock or the weather, but that's it.
Things I've tried:
Factory reset from the device settings. After pressing the button, the screen gets black and after 2 seconds it gets back on the settings menu.
Change the security settings. Both changing the pattern, the password or leaving it without security. It only affects how the device is locked, but nothing else.
Using adb, I have no permission to see the data folder and the sdcard folder says it does not exists.
From TWRP, if I had set any kind of lock while in Android, it will ask for it (such a pattern or password). But whatever I input, it always says "Failed to decrypt user 0". I can cancel the input and enter normal TWRP but with the data folder encrypted.
I've tried to Wipe>Format Data, with the following error message:
Code:
/system/bin/make_f2fs -d1 -f -0 encrypt -0 quota -0 verity -w 4096 /dev/block/sda35 27865079 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Filed to mount '/data' (Device or resource busy)
In Wipe>Advanced Wipe>Repair or Change File System (to the Data partition). If I try to repair it gives me error 255 again. If I try to Change File System to F2FS, again "Error chaning file system".
I cannot flash Xiaomi.eu again from TWRP because I cannot move the file to the phone through adb "permission denied".
What other options do I have?
Thanks in advance for the help.
Click to expand...
Click to collapse
U can try to flash a stock ROM using MiFlash tool and flash xiaomi.eu ROM again.
Also you can use a USB OTG to flash from twrp
Alin45 said:
U can try to flash a stock ROM using MiFlash tool and flash xiaomi.eu ROM again.
Click to expand...
Click to collapse
I thought I couldn't downgrade to stock rom because of Anti Rollback restrictions, but it did work and solved the problem. Thanks for the help!
arifqur said:
Also you can use a USB OTG to flash from twrp
Click to expand...
Click to collapse
Didn't think of that, unfortunately flashing from TWRP does not format the data partition, so it didn't solve the problem.