I did a real good number on my nexus 6
I wiped and formated data in twrp thinking you can format a ROM.This type of wipe was the type (YES) Under advanced wipe causing to have No O.S Installed after a reboot .This will happen on any phone if you type YES format data and reboot thinking you'll have a clean ROM . Its a instant brick Unless you have a ROM downloaded prior to flash or have external SD card slot to put a ROM onto.
Then when I went to flash firmware stock Images with Wugfresh tool kit in fastboot mode it failed ,afterwards I OEM relocked boot loader by mistake before i ever tried to reboot the Newly flashed firmware ....thinking the factory images flashed in which they didn't completely. The OEM relock wiped phone and
I was stuck with a No O.S System and no way to OEM unlock bootlader cause I had no O.S to boot into to check mark the OEM unlock box.
This is a highly unlikely scenario for the Inability to reflash firmware if you still remain oem unlocked but Possible if you format data within twrp because it wipes O.S meaning OEM unlock box is gone unchecked
Stay away from OEM relocking Unless you have rebooted safely into a ROM or stock ROM after flashing .
:screwy: DO NOT OEM RELOCK WITHOUT FOLLOWING THE METHOD TO DO SO.
Sent from my Nexus 6 using XDA Free mobile app
androidddaaron said:
I did a real good number on my nexus 6
I wiped and formated data in twrp thinking you can format a ROM.This type of wipe was the type (YES) Under advanced wipe causing to have No O.S Installed after a reboot .This will happen on any phone if you type YES format data and reboot thinking you'll have a clean ROM . Its a instant brick Unless you have a ROM downloaded prior to flash or have external SD card slot to put a ROM onto.
Then when I went to flash firmware stock Images with Wugfresh tool kit in fastboot mode it failed ,afterwards I OEM relocked boot loader by mistake before i ever tried to reboot the Newly flashed firmware ....thinking the factory images flashed in which they didn't completely. The OEM relock wiped phone and
I was stuck with a No O.S System and no way to OEM unlock bootlader cause I had no O.S to boot into to check mark the OEM unlock box.
This is a highly unlikely scenario for the Inability to reflash firmware if you still remain oem unlocked but Possible if you format data within twrp because it wipes O.S meaning OEM unlock box is gone unchecked
Stay away from OEM relocking Unless you have rebooted safely into a ROM or stock ROM after flashing .
:screwy: DO NOT OEM RELOCK WITHOUT FOLLOWING THE METHOD TO DO SO.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just to note, when facing the "no OS installed" scenario, just download a ROM to your PC. Boot the phone to TWRP, and connect to PC. You can then drag and drop or copy and paste the ROM in your internal storage. Then flash the ROM with TWRP.
Evolution_Tech said:
Just to note, when facing the "no OS installed" scenario, just download a ROM to your PC. Boot the phone to TWRP, and connect to PC. You can then drag and drop or copy and paste the ROM in your internal storage. Then flash the ROM with TWRP.
Click to expand...
Click to collapse
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Removal of the Google account and a factory reset. Or removal of Google account and flashing a factory image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:good:
Evolution_Tech said:
Removal of the Google account and a factory reset. Or removal of Google account and flashing a factory image.
Click to expand...
Click to collapse
Unfortunately I'm talking mainly about media data .. Photos files videos ... Unless you have eraser app installed i wanna say its all recoverable even after a reset
Anyone knows gt data recovery disk digger people use for there purpose of recovering lost photos but you never know if they use it on a used phone someone has sold
Sent from my Nexus 6 using XDA Free mobile app
androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
think about it, when you format something you cant have an os installed there any more, you yoursrlf formatted it. you can't format something and keep all the os there as well.
androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
That's odd, formatting data in recovery has never formatted system for me. I've always formatted all partitions except for system to do a complete factory reset and never had an issue.
OS resides on the system partition so wiping dalvik and system will result in no os.
If you worry about data being recovered by a new owner perhaps you couod write junk data and then format the partitions several times? Not particularly versed on the characteristics of nand so you may want to look into that.
you5urf said:
That's odd, formatting data in recovery has never formatted system for me. I've always formatted all partitions except for system to do a complete factory reset and never had an issue.
OS resides on the system partition so wiping dalvik and system will result in no os.
If you worry about data being recovered by a new owner perhaps you couod write junk data and then format the partitions several times? Not particularly versed on the characteristics of nand so you may want to look into that.
Click to expand...
Click to collapse
he probably formatted everything instead of going by partition.
simms22 said:
he probably formatted everything instead of going by partition.
Click to expand...
Click to collapse
That's what I would think. I have formatted data several times on this device & it certainly doesn't wipe your system partition.
I just flash a factory image using fastboot. Fastboot itself will wipe each partition before flashing. Flashing userdata will wipe internal storage. Then reboot fully into the OS and ensure everything is working as expected. Only then is it safe to relock the bootloader.
Sent from my Nexus 6 using Tapatalk
Related
Hi i am looking to root for the 1st time i have seen how to do it, i have already unlocked bootloader for updating reasons.
My question is if i put a rom on for instance JellyBAM can i if i choose to switch between that and the stock android or would i have to re install the stock android.
I enjoy the features of the stock android on my nexus 7 (2013) but am looking to just tweak it a little but i dont want to put the factory image back on if i dont like JellyBAM as it will wipe my device again.
Thanks for any help
Joe
http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.
Username invalid said:
http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.
Click to expand...
Click to collapse
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?
joeyt90 said:
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?
Click to expand...
Click to collapse
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images
Username invalid said:
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!
joeyt90 said:
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!
Click to expand...
Click to collapse
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.
Username invalid said:
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.
Click to expand...
Click to collapse
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks
joeyt90 said:
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks
Click to expand...
Click to collapse
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.
Username invalid said:
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.
Click to expand...
Click to collapse
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe
joeyt90 said:
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe
Click to expand...
Click to collapse
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Username invalid said:
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
Click to expand...
Click to collapse
worked a treat although i now cannot stop changing things
Thanks
I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this the message? I get the same ****
Sent from my Nexus 6P using Tapatalk
csh8428 said:
I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig
Click to expand...
Click to collapse
Have you tried flashing the MDB08M vendor image after flashing the ROM? Are you wiping properly (system, data, cache, dalvik cache)? In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?
Heisenberg said:
Have you tried flashing the MDB08M vendor image after flashing the ROM?
Click to expand...
Click to collapse
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Heisenberg said:
Are you wiping properly (system, data, cache, dalvik cache)?
Click to expand...
Click to collapse
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
Heisenberg said:
In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?
Click to expand...
Click to collapse
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.
csh8428 said:
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.
Click to expand...
Click to collapse
Ok, it looks like you didn't wipe (system, data, cache, dalvik cache) before installing the ROM, so there's one problem. Also, when creating your backup you don't need to check all options, only system, data, and boot. You flash the stock vendor after flashing the ROM. I'd recommend you take a look at my guide, it should clear a few things up:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You'll also find a recovery flashable version of the vendor image in my index thread under the stock firmware section:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
I was getting the same error, but it didn't seem to affect he devices functions in any way.
Anyways I flashed the new vendor image since i installed a MMB29P ROM and didn't update it before.
Without wiping it did nothing the error was still there.
Then I wiped everything and started with vendor image, then the ROM, the kernel and SU.
NO ERROR.
Team RejectZ
How to Nandroid Back up and Restore as well as flash zips with TWRP on the Galaxy J700t1 (Metro PCS variant)
Hello , TimmetaL6669 here from Team Rejectz... It feels so good to be back.. So we have been having this little problem with the TWRP when it comes to doing a back up or flash anything because of, "system can't mount -data , failed" "system can't mount external sd card " .. or something along those lines... So after playing with it for awhile I finally figured out what the problem is... We are used to the old file system before Marshmallow... Before Marshmallow and before SE Linux Enforced the system would write directly to data or the sd card by mounting it directly... but with the new security the system writes through the system.. not by mounting thus avoiding potential malware attacks... so if the system can write to itself... so can we... This fix is more simple than I originally thought... there is no need to mount data unless you are flashing a ROM in which case we can use odin....or TWRP... you just have to know from where...So without further adue,
Pre-Requisites:
You must be Rooted usisng Mese2050's ported TWRP recovery and flashing SU binaries or by using Paco's Method.
You must have a micro SD card with at least 4 GB on it for your zips and backups
WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN
There isn't any reason to change cashe or data unless you are doing a full ROM change ..... Odin does this anyway when you odin so unless you just made an entire ROM with kernel and recovery included with STOCK cashe then DON'T WIPE CASHE OR DATA on marshmallow.. New security.. They did away with us messing with DATA or CASHE.... No need anyway for a back up or restore or to flash zips.... a good updater script for zips for marshmallow will mount the System anyway.
To Nandroid Back UP:
1. Boot into TWRP and click BACK UP. You're gonna need to switch your storage.... Switch your storage to Micro SDCard STORAGE .. because thats where we are going to be making our backup to..Then Swipe to Back up. Wait for your backup to be complete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To Nandroid RESTORE:
Boot into TWRP. Click RESTORE. This time though we have been running into the "can't mount storage/ can't mount data" issue ...So..... Instead of switching to your Micro SDCard storage, STAY IN INTERNAL STORAGE. click "go up a level". Click external SD. Find your back up and swipe to Restore.
To Flash zip Files
Again just like with the restore option we are going to stay in the internal storage and click "go up a level" click external sd card and find the zip file you want to flash from your sd card. Click install Image
Thats it. Click thanks if I helped you, Feel free to ask questions if you get stuck. Make sure that you are completely rooted first with SU and Busybox binaries in /system/bin , /system/xbin and root/sbin before you try to use TWRP. Before attempting a back up, or to use TWRP make sure you follow the instructions carefully in Mese2050's TWRP thread.
" Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery]."
Also ensure that you have "unknown sources" checked in Settings/Security tab. and also in "Developer Options" you wanna have USB debugging and OEM unlock checked too.
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case
needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case
Yeah, i do. My sd files look almost exact to bottom screenshot
Sent from my SM-J700T1 using XDA-Developers mobile app
---------- Post added 10-08-2016 at 12:04 AM ---------- Previous post was 09-08-2016 at 11:59 PM ----------
I think I had done this prior to reading this post, but I did smart install of busybox at same time, when I restarted it wasn't reading sd properly and I formatted thinking it would solve issue. Lost data on sd and still didn't fix issue. Did full clean install, normal busy box, everything golden now
Sent from my SM-J700T1 using XDA-Developers mobile app
I am a little confused. I have the SM J700T. I thought I was following Messi2050's instructions. Here's where I am so far. I have a 32gb micro sd card which I did not have installed when I setup Kies3. Kies3 was installed in the PC to install the phone drivers. Correct? I saw the drivers install when I connected the phone having Odin3 running at the same time. After the drivers installed the phone connected to Odin. Then I launched Odin 3 in order to flash a kernel which turned out to be incompatible with the J700T and got the "Kernel is not Seandroid Enforcing" error. I found a recovery image which was supposed to take me back to stock, and it seemed to work in that I could then install the Messi2050 kernel "odin-permissive-kernel-j700t-t1". The install went ok. Then I flashed the TWRP "odintwrp-3.0.2-0-j700t" which seemed to go ok, but when I disconnected the phone from the PC and rebooted into TWRP I was seeing the Enforcing error on the screen until TWRP fully booted. Anyway, I put the Micro SD card in with the SuperSU zip on it and used TWRP to install "UPDATE-SuperSU-v2.46.zip" , which kinda hung on the install until I sorta cancelled it and immediately the install finished. I rebooted and checked for root with Root Checker and after a while I got a successful report. So then I tried to do a backup of the phone as explained above in this thread.. I selected the MicroSD card to back up to and selected all the selectable partitions, but ended up with lots of can't mount data errors. Eventually I selected only system to backup and it succeeded. So now when I boot up the phone I am still seeing the Enforcing error on the initial black boot screen, but it boots normally and I have been able to use rooted tools and apps. I do not have Busybox installed yet as I believe I have to start over to clear the Enforcing error. I also did not follow Messi2050's instruction to MTP the SU file onto the phone while I am in TWRP. (Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.) I assume that means you have to have the phone connected to the PC. So how do I fully clear the Enforcing error? Here, in this thread, it says, "WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN ", so there must be something I am missing when Messi2050 says, "-if you want internal storage or data to work in TWRP: Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone! Go to [Reboot] -> [Recovery]. So somewhere in here I need to get oriented correctly. I think I have to reset the phone but I tried a factory reset but it didn't clear the Enforcing error. I would appreciate a considered response from the members who know what to do!! Thanks
@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup.
After a backup/restore using this method in this thread, do not wipe anything.
-sent from this device using this app....
OriginalShinken1 said:
@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup. After a backup/restore using this method in this thread, do not wipe anything.
So, first you use Odin to flash Messi2050's kernel, which, when you reboot gives the Enforcing warning message; then you Odin the TWRP, and then EXACTLY what do you wipe and why and how??
Does this or another step resolve the inability to do a backup of data and the other partitions? I followed the instructions in this thread, but it didn't work.
Perhaps it has to do with the first wipe? Perhaps you could explain why these errors are happening; something to do with the Marshmallo file system? How to resolve it?
Click to expand...
Click to collapse
@bromerrill
Click format data. Type yes (you'll see)
Make sure you have supersu zip on sd card just in case. Then go back to "install" and flash supersu.
Sorry pics are turned.
-sent from this device using this app....
Well it seems we still do not have a handle on this rooting process. After following the instructions and getting root twice, each time upon a reboot after a while the phone gets soft bricked. Getting the Custom binary blocked by FRP error. It could be related to turning off the developer options subsequent to getting root. If that is the case those who know need to advise those who don't not to turn off developer options! As far as this thread is concerned I don't see a clear explanation of the backup / restore procedure. There has to be something you do before using TWRP to do a backup, otherwise you get errors that you can't back up the data, etc. I appreciate the skewed pictures but that doesn't explain anything because there is no procedure explained. I wrote, "then EXACTLY what do you wipe and why and how??" which is not yet answered. How hard is it to do a step by step so all the users can get a clear understanding of the procedure??
So I’ve tried many ROMs and am on the latest version of TWRP but I keep getting stuck at the password screen after rebooting. I have tried many factory resets and complete wipes and nothing has worked. I am also getting “encryption” errors and twrp errors about decrypting data...asking for a password and then telling me my password is incorrect. Is this the end of my 6P? Thanks for any help!
Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.
notstevek said:
Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.
Click to expand...
Click to collapse
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.
notstevek said:
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.
Click to expand...
Click to collapse
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
videotape74 said:
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
Click to expand...
Click to collapse
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.
notstevek said:
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.
Click to expand...
Click to collapse
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!
videotape74 said:
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!
Click to expand...
Click to collapse
I'm sorry to hear that. So to confirm you completely reflashed to stock firmware, reflashed TWRP recovery, and it's still giving you the error? Maybe someone else has some idea of what's happening but only thing I can think of is flash memory is shot. Try maybe older version of twrp??
Something similar happened to me, I will explain my situation and how to solve it, I had the stock ROM 8.1.0 installed and out of curiosity I put a start block that starts with a password and all right up there, then install the twrp and I prepared to put a Custo ROM to be specific CRDroid and everything was installed correctly nothing unusual, the problem came to insert my SIM card and see that I had no signal review the imei and had disappeared was blank and had not made rest of the SAI so I turned pale, then started twrp and asked for the password I had put with the stock ROM and accept it I made an advanced deletion and still still without imei, I reinstalled the latest version of stock ROM home, I asked for the password ,I was. security and I removed all kinds of security, I returned. do the process of installing the Custon ROM and the imei turned MIA CONCLUSION by changing the ROM and better to disable absolutely all kinds of blocking tank can bring signal or encryption conflicts
Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.
johan.drykke said:
Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
View attachment 5668491
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.
Click to expand...
Click to collapse
Very simple. When you open TWRP, it should ask you for the PIN. You have to enter the same PIN/Pattern you use the same for unlocking the screen in Android
Use the latest official TWRP from TWRP.me
It's nothing specific to Mi 9T or Xiaomi, it's a very good protection enforced by Google couple of years ago with A10 - TWRP cannot decrypt your Internal memory data without your pin.
Just consider your phone gets lost and somebody boots to TWRP - would you like him to be able to see your photos, documents, etc
The thing is, I had pin, 1234, I flashed twrp official through fastboot, It didn't ask for it, partition is still encrypted. Whet next? I tried wiping **** out of sdcard putting image there and flashing it, PicselExp, bootloop willkomen. Nothing is working, I am glad I flashed recovery though.
Please stop moralizing, I bought this phone because I want to play with it, not to store DEFCON 2 documents on it.
EDIT1: Sorry for beeing harsh, just I think that this 'davinci' is different than other 'davinci' and for the love of God, I hate TiVoization.
johan.drykke said:
Please stop moralizing...
Click to expand...
Click to collapse
I'm not noraluzing, I wanted to help, now I don't care anymore. Google will be your friend, everything relevant can be found there
Good luck
use fastboot to flash stock ROM (fastboot ROM). then from stock removeall safety patterns, fingers, go to flashing twrp with fastboot, boot to twrp, format data, flash whatever you want
be polite or get the f...out of this forum
Hi!
I'm having a somewhat similar yet kind of different problem : long story short I was able to flash a ROM once last week, it bricked my device and the internal storage got encrypted just like that, I somehow managed to manually flash a stock ROM from ADB and now my device boots properly on a stock MIUI.
The issue is I have no lock pattern anymore and the internal storage is still encrypted so I still can't flash from recovery.
Am I doomed to rock MIUI until my device dies? At what point should TWRP ask me for a pattern?
can't you format data in recovery?
wipe everything in recovery, try to install desired ROM. Hope you have made a backup before encryption
I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.
Crikripex said:
I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.
Click to expand...
Click to collapse
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc
yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM
zgfg said:
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc
Click to expand...
Click to collapse
yaro666 said:
yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM
Click to expand...
Click to collapse
Thank you both so much for your time, help and explainations!
I finally understand what was happening, I had a hard time pinpointing exactly what made my partition encrypted but it does make a whole lot of sense.
I managed to successfully flash ArrowOS 12.1 using sideload after formating. I now know both that my system is naturally encrypted and that it is completely normal and not a result of a flashing error
Last time I flashed a ROM the newest and flashiest android was 9.0 so it's all new to me.
Thanks again!
There is a TWRP (TWRP 3.6.2+ - UNOFFICIAL | Android 12.) specially made to work with android 12 enryption. (The version from Adi is only needed for his supported roms. Otherwise always use the TWRP 3.6.2+ if not declared differently)
Could be useful if you want to OTA update your rom. Otherwise you could be forced to sideload over adb or even make a complete clean flash again.
Selfquote:
[RECOVERY][3.4.0-10][davinci]Official/Unofficial TWRP for Xiaomi Redmi K20 (Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com