[Zenfone 5z] Are there some stock images? Does anyone still have deleted TWRP? - Asus Zenfone 5Z Questions & Answers

Does anyone have deleted experimental 5z twrp? I need it for backuping /system. Or is there some stock image to flash? Would like to try lineage based on treble but without any way of going back its very risky.

Mister_Magister said:
Does anyone have deleted experimental 5z twrp? I need it for backuping /system. Or is there some stock image to flash? Would like to try lineage based on treble but without any way of going back its very risky.
Click to expand...
Click to collapse
You can always go back with fastboot... Actually you don't need to flash again.
This device is a a/b device meaning it has two partitions for a boot, system, bootloader and other partitions.
If you want to go back, you just switch for a to b or b to a
The data partition is not doubled.
Try it out.... Download fastboot and reboot into bootloader.
Check the screen for the active slot (a or b).
Say slot a is the current slot, type
fastboot set_active b
To switch to slot b. The reboot and see what happens. You should boot into the previous firmware version.
That is how you can develop and completely mess up boot, system and vendor and still use you phone a few seconds later. (Well as long as you don't touch the data partition).
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
Oh and stock images are available from the Asus support website.
Just download the correct version and extract the images from there.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

scanno said:
You can always go back with fastboot... Actually you don't need to flash again.
This device is a a/b device meaning it has two partitions for a boot, system, bootloader and other partitions.
If you want to go back, you just switch for a to b or b to a
The data partition is not doubled.
Try it out.... Download fastboot and reboot into bootloader.
Check the screen for the active slot (a or b).
Say slot a is the current slot, type
fastboot set_active b
To switch to slot b. The reboot and see what happens. You should boot into the previous firmware version.
That is how you can develop and completely mess up boot, system and vendor and still use you phone a few seconds later. (Well as long as you don't touch the data partition).
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
Oh and stock images are available from the Asus support website.
Just download the correct version and extract the images from there.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
That means I can have 2 OS in a and b partition.?

hamzain said:
That means I can have 2 OS in a and b partition.?
Click to expand...
Click to collapse
Sort of. You have only one data partition. But you can switch between two OS versions (for instance two different versions of the stock rom) without having to wipe.
Switching between stock or omni for instance will require a wipe of data.
Verstuurd vanaf mijn SM-T813 met Tapatalk

scanno said:
Sort of. You have only one data partition. But you can switch between two OS versions (for instance two different versions of the stock rom) without having to wipe.
Switching between stock or omni for instance will require a wipe of data.
Verstuurd vanaf mijn SM-T813 met Tapatalk
Click to expand...
Click to collapse
Thank you for your reply.
One more problem that I'm facing is (and trust me I have Googled it extensively but unable to find a solution), I'm unable to parse or write system into partition-b. I have downloaded the latest PE9.0 GSI and when I try to fastboot flash, it says cannot write (unknown error). I have another updated fastboot binaries, when I run fastboot flash in that, it says completed, but I'm unable to boot when I select partition-b, when I switch it to partition-a, it boots into ZenUi
Please help.

hamzain said:
Can someone please reply?
Click to expand...
Click to collapse
What did you exactly do? What image did you try to flash to what partition. The phhusson treble images are xz compressed and need to be extracted first before you flash.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

scanno said:
What did you exactly do? What image did you try to flash to what partition. The phhusson treble images are xz compressed and need to be extracted first before you flash.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
I extracted the image file from the .xz file.
As my active partition is 'a', I set the active partition to b and flashed the system.img through fastboot. It write the system and says finished, then reboot. And doesn't boot up. Then I reboot into bootloader and set active partition to a, it boots into ZenUI.
In the next attempt, I rooted my phone with magisk patched boot method. I successfully rooted and was able to install magisk modules. Then again I tried to flash PixelExperience9.0 in system_b, it doesn't boot up, when I flashed it to system_a, the phone boots up, it asked me password saying data is encrypted, when I enter my screen PIN, I get a message that pin is correct but data needs to be erased, after data erase it again got stuck in bootloop.

hamzain said:
I extracted the image file from the .xz file.
As my active partition is 'a', I set the active partition to b and flashed the system.img through fastboot. It write the system and says finished, then reboot. And doesn't boot up. Then I reboot into bootloader and set active partition to a, it boots into ZenUI.
In the next attempt, I rooted my phone with magisk patched boot method. I successfully rooted and was able to install magisk modules. Then again I tried to flash PixelExperience9.0 in system_b, it doesn't boot up, when I flashed it to system_a, the phone boots up, it asked me password saying data is encrypted, when I enter my screen PIN, I get a message that pin is correct but data needs to be erased, after data erase it again got stuck in bootloop.
Click to expand...
Click to collapse
Try another GSI
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

Related

E:failed to mount /system (Invalid argument ) can't mount '/system ' (Invalid argumen

Just yesterday i received this error message. on my sprint galaxy note 2E:failed to mount /system (Invalid argument) can't mount '/system '(Invalid argument)I've searched i tried to take my phone to the repair facility they wouldn't touch cause it has a tiny crack on the top lense
...i called sprint tech support they couldn't help me i called Samsung and they couldn't help me that i have to send the phone in and can take 2weeks. I searched various forums and found mixed answers on how to fix this problem alot of it i don't understand cause I've never rooted a phone or used odin or any of that stuff. I'm a disabled veteran soi don't have the cash to dish out for a new phone
is there anybody can help me by showing me step by step on how to fix this problem. Any help or input would be gladly appreciated for thisvet
First try to wipe data/recovery by putting your phone in recovery mode (hold menu + vol down then power on while still holding)
Second, in case first does not work, you will have to use odin. Find firmware that fits your phone and flash one or two times (I had to do this on Gio because I had CM10.1)
Third, in case above does not work, you can try out some custom rom like CM, AOSP, PA, AOKP, etc.
You have flashing guide on almost every subforum for any model. Flash cwm with fastboot (fastboot flash recovery recovery.img or whatever), put appropiate zip for your phone on sdcard and go select install zip from sdcard (e.g. cm10.1-unofficial-note.zip), wipe data, cache, dalvik cache and reboot.
Gesendet von meinem MT11i mit Tapatalk 2
I tried wipe data and reset and factory reset and still will not boot
ReznorNInchNails said:
First try to wipe data/recovery by putting your phone in recovery mode (hold menu + vol down then power on while still holding)
Second, in case first does not work, you will have to use odin. Find firmware that fits your phone and flash one or two times (I had to do this on Gio because I had CM10.1)
Third, in case above does not work, you can try out some custom rom like CM, AOSP, PA, AOKP, etc.
You have flashing guide on almost every subforum for any model. Flash cwm with fastboot (fastboot flash recovery recovery.img or whatever), put appropiate zip for your phone on sdcard and go select install zip from sdcard (e.g. cm10.1-unofficial-note.zip), wipe data, cache, dalvik cache and reboot.
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
Then your only choice is to flash your phone since it is, hopefully, just software fault. Maybe your filesystem got damaged (corrupted). Anyway, you can try odin or flash some of zips, search your model on xda (note II android development)
Here's excerpt
http://forum.xda-developers.com/showthread.php?t=2147373
If you want to flash custom rom then first flash appropiate recovery (cwm, twrp, it should be mentioned in rom thread).
Gesendet von meinem MT11i mit Tapatalk 2
Thank you so much for all the info........its still a lil complicated for me is there anyway u can simplifit further by steps am truly sorry for the inconvenience and trouble
ReznorNInchNails said:
Then your only choice is to flash your phone since it is, hopefully, just software fault. Maybe your filesystem got damaged (corrupted). Anyway, you can try odin or flash some of zips, search your model on xda (note II android development)
Here's excerpt
http://forum.xda-developers.com/showthread.php?t=2147373
If you want to flash custom rom then first flash appropiate recovery (cwm, twrp, it should be mentioned in rom thread).
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
Ok, here's a video guide
https://www.youtube.com/watch?v=xTUW1_L5fmU&feature=youtube_gdata_player
Gesendet von meinem MT11i mit Tapatalk 2
Thanks will try that in the morning........well let you know if it works thanks for being patient and all the info
veterannoob said:
Thanks will try that in the morning........well let you know if it works thanks for being patient and all the info
Click to expand...
Click to collapse
tried the unbricking it and didn't work gave me a fail error
/system cannot be mounted? My solution that worked perfectly.
The E:Failed to mount /system problem, that is, that the system does not have the ability to actually mount the all-important /system dir, was totally solved (FOR ME) by simply deleting a previously created Boot Slot in SafeStrap 3.75.
Check your slots. If you HAVE NOT created any stocks, and, just have your "stock slot" created (hope to God you do Then I personally think that you'll have bigger fish to fry.
However.... Deleting all other slots except Stock Slot, was the solution for me.
Not that I can boot my machine. I still can't (bummer) but I don't give up too easily.
Hope this helps your system mount problem.
I have suspicians about why my machine can't boot, relating to Slot 1's System partition size being zero, but that's another thread, right?
Ok then, hope this dumb, no-programmer n00bie helped.
David
Same error here
bodycode said:
The E:Failed to mount /system problem, that is, that the system does not have the ability to actually mount the all-important /system dir, was totally solved (FOR ME) by simply deleting a previously created Boot Slot in SafeStrap 3.75.
Check your slots. If you HAVE NOT created any stocks, and, just have your "stock slot" created (hope to God you do Then I personally think that you'll have bigger fish to fry.
However.... Deleting all other slots except Stock Slot, was the solution for me.
Not that I can boot my machine. I still can't (bummer) but I don't give up too easily.
Hope this helps your system mount problem.
I have suspicians about why my machine can't boot, relating to Slot 1's System partition size being zero, but that's another thread, right?
Ok then, hope this dumb, no-programmer n00bie helped.
David
Click to expand...
Click to collapse
David,
I have the same message on my Sony Xperia M.
I tried to fastboot a CM11 again, but always receive the message "unable to mount /system".
How do I delete these boot slots?
Regards,
joaobot
How do I find these slots you are talking about my friend?
bodycode said:
The E:Failed to mount /system problem, that is, that the system does not have the ability to actually mount the all-important /system dir, was totally solved (FOR ME) by simply deleting a previously created Boot Slot in SafeStrap 3.75.
Check your slots. If you HAVE NOT created any stocks, and, just have your "stock slot" created (hope to God you do Then I personally think that you'll have bigger fish to fry.
However.... Deleting all other slots except Stock Slot, was the solution for me.
Not that I can boot my machine. I still can't (bummer) but I don't give up too easily.
Hope this helps your system mount problem.
I have suspicians about why my machine can't boot, relating to Slot 1's System partition size being zero, but that's another thread, right?
Ok then, hope this dumb, no-programmer n00bie helped.
David
Click to expand...
Click to collapse
Hi David,
I solved this problem recently.
I downloaded a stock firmware (.ftf file) and flashed it.
It will restore everything!
Good luck!
---------- Post added at 03:31 PM ---------- Previous post was at 03:29 PM ----------
otto68 said:
How do I find these slots you are talking about my friend?
Click to expand...
Click to collapse
Hi @otto68
I don't know anything about these slots either.
I just flashed a stock fimware and it worked.
Can you give the link of that ftf file?
Verstuurd vanaf mijn SM-T805 met Tapatalk
veterannoob said:
I tried wipe data and reset and factory reset and still will not boot
Click to expand...
Click to collapse
hello roith remember me
Mount /system error.
My android phone has low rom in phone storage amd i want to upgrade rom i used hk rom editor and kingo root . And when i format manually it only shows andoid picture which disappear and appear in 1 sec.and when i try to tapp power button 7 times it says Mount /system error. And i tried all combination what to do plzzz tell me
I've managed to retore my Samsung Galaxy GT-P5110 to original condition . Initially shows message about being unable to mount system and can't go any further than charging initiation logo. Downloaded PIT file using Odin and tada ..work as charm
All you have to do to fix the can't mount system error 5o install official toms and stuff is you format and go to advanced and check the first 3 available at the top then go back and click on system and click repair file
hii could any one tell me where i can find stock rom for samsung verizon stratosphere 2 model number SCH-I415
i GOT THE SSAME PROBLEM......
Format all partitions except external.. You can just do the system and I recommend data partitions.. Repair the partition in twrp recovery.. Convert the partition to fat or exact.. Then convert again to ext4.. That should fix it easier..

Dead Device

I have an issue that I cannot for the life of me fix. Last night my wife’s phone received the OTA update and her phone would not restart after that. Total B.S. move on ASUS’s part not to pull that update knowing the issues people were having. But anyways, here’s the rundown. I can boot into bootloader mode but I cannot get into stock recovery. I can, through a certain method get into CWM recovery and I can see the external SD, but I get errors when I try to flash an update or another entire OS. I’ve tried to bypass signature verification also and still cannot get anything to install. ADB will not sideload because it does not find my device, but the method of getting into CWM recovery is done through ADB so I’m confused there. Never have I had such a tough time restoring a bricked device. Samsung, no problem. Huawei, no problem. This POS I’m about ready to throw in the pool and call it a day. Does anyone have any suggestions?
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
I'll try that when I get home
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing will flash through adb
meciu99 said:
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
Click to expand...
Click to collapse
Still doesnt work. E: error in external sd blah blah blah, same as everything else.
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Hank87 said:
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I've wiped cache multiple times. What steps did you go through?
Use the adb fastboot, command "fastboot erase cache"
Sent from my ASUS_Z00AD using Tapatalk
You need the stock recovery as the same version of the firmware you're sideloading, flash the recovery through fastboot.
I was finally able to restore everything. Stock recovery, OS etc… Here’s what I did.
Using ADB and following the procedures here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 and using fastboot, flashed the recovery.img, boot.img and droidboot.img in that order. That gave me stock recovery back. Then I sideloaded with ADB the latest FULL firmware from here https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
It was the only version that did not error out in some form or another. Everything is back to normal.

Oneplus 3 decryption and stock recovery problem HELP!!!

I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....
antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?
0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.
kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go
candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.

Can't boot to recovery [Oxygen 4.0.3, TWRP 3.0.3.0]

I'm running Oxygen OS 4.0.3 and have TWRP 3.0.3.0. Today I try to boot to recovery to clear dalvik and cache, and what I saw was the first menu when I can chose what to do - Start, reboot recovery, bootloader or to turn off the phone - same as this one https://www.google.pl/search?q=onep...iw=412&bih=652&dpr=2.63#imgrc=l-lNa3Sp9dxa9M:When I chose to go to the recovery the phone just going to be dark and go back to the same menu over and over again.
Last think I do before I last successfully reboot to recovery was changing the build.prop file whither the line "ro.opa.eligible_device=true" in order to get the Google assistant 2 days ago. Today after failure with going to recovery I change back the file but still can't go further then that first menu.
This menu still shows that I have unlocked bootloader and the root is working good for me, and checking root apps is showing I still have it. (don't know if that information is needed).
I have the Official TWRP app, where is the option to flash TWRP but I don't know if that solutions would work or if it's save to not brick the phone.
I'll be glad for any help.
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Great post:
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
LE
After flashing a rom, reflash recovery. You can flash recovery from recovery. Touch Instal > go where it's the recovery is > image > Recovery. Swipe to flash. Reboot to recovery to check if it works.
Some roms flash official recovery, that's why.
Reflash TWRP 3.0.4.1 . After flashing do not reboot via vol keys, instead use CMD command only, type this in cmd fastboot boot twrp.img , replace twrp with name of your recovery file and then u will boot direct into recovery
singh_21 said:
Reflash TWRP 3.0.4.1 . After flashing do not reboot via vol keys, instead use CMD command only, type this in cmd fastboot boot twrp.img , replace twrp with name of your recovery file and then u will boot direct into recovery
Click to expand...
Click to collapse
So I need to reflash that TWRP by connection phone to PC, and where it will ask chose to flash it on my recovery partition? Won't that wipe all my data?
Thanks I will check it after I back home
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Ludzik1993 said:
So I need to reflash that TWRP by connection phone to PC, and where it will ask chose to flash it on my recovery partition? Won't that wipe all my data?
Thanks I will check it after I back home
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
Click to expand...
Click to collapse
I hope you know how to flash twrp.img via cmd in pc. After you done with flashing twrp.img, you write the command i wrote earlier, and u will boot in recovery.
As you are using OOS, you wont be having any issues with partition, Data will not be lost.
Data is lost when you unlock the bootloader.
singh_21 said:
I hope you know how to flash twrp.img via cmd in pc. After you done with flashing twrp.img, you write the command i wrote earlier, and u will boot in recovery.
As you are using OOS, you wont be having any issues with partition, Data will not be lost.
Data is lost when you unlock the bootloader.
Click to expand...
Click to collapse
I only did it once when I was first time unlocking bootloader, and I was using the tool made for this. But I will try my best.
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
singh_21 said:
I hope you know how to flash twrp.img via cmd in pc. After you done with flashing twrp.img, you write the command i wrote earlier, and u will boot in recovery.
As you are using OOS, you wont be having any issues with partition, Data will not be lost.
Data is lost when you unlock the bootloader.
Click to expand...
Click to collapse
Work exactly as you say [emoji4] Thanks for being here and help! Take care
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
TWRP
Can someone give me the link to Recovery file for oxygen 4.0.3 for one plus 3
Latest official TWRP, that's v3.1.0.0.
As alternative, consider latest blu_spark TWRP.
Lol u may just be going into a loop, when u reboot ur phone the message comes up to press power button to skip or press volume up or down to choose the option u want so when u click recovery, it will reboot and give u that same message, just leave it alone this time or press the power button and u will go into recovery
I can't believe these people are sending u on a wild goose chase

[Guide] How to Remove Device Encryption to Flash Custom ROMs

The Issue
The device does not allow to use the newly flashed Custom ROM as it is Encrypted thereby asking for Password every time the phone boots up and wiping Data Partition with a Custom Recovery also does not work.
The Solution
Step 1 - Type anything as Password when the device asks for it after booting up. Be Quick as the device will shut down if you don't type anything within a few seconds.
Step 2 - Check whether it says Decryption was successful but the data is corrupted and also instructs to do a factory reset by tapping the Reset button. If Yes then go to the next step as the subsequent steps will resolve the issue. If No then this guide can not help you.
Step 3 - Do not touch that Reset button and reboot the device to Recovery by long pressing the Power button and then pressing Power and Volume Down simultaneously and choosing to go to Recovery from the Fastboot/Bootloader Menu.
Step 4 - Now connect the phone to your PC and transfer everything from your internal storage (if you didn't do it before flashing the Custom ROM) using MTP as the next steps will wipe the internal storage. Eject your SD Card from the device.
Step 5 - Download the Platform Tools from the link : [url]https://drive.google.com/open?id=1LEcF5iAjRdno2_aPKv9DYdOYtviC5xB7[/URL] and after extracting the folder place it in the C drive.
Step 6 - Install Motorola Device Manager from the link : [url]https://drive.google.com/open?id=12k2joSx5G08oourGlYLdtLEdTuOC9CVb[/URL] on your PC.
Step 7 - Download the Stock Recovery from the link : [url]https://drive.google.com/file/d/1_gogMT_GgSvg6FKpe2q4Z51gh22ftUdt/view[/URL] and place it in the platform-tools folder.
Step 8 - Assuming that your phone is still connected to the PC go to the Fastboot/Bootloader menu on the device by using Reboot to Bootloader option from the Recovery.
Step 9 - Go to the platform-tools folder on the C drive of your PC and open a Command Prompt window there by holding Shift key while Right clicking on the mouse and choosing the option. Enter the command fastboot devices to ensure that your phone is connected to the PC.
Step 10 - Enter the command fastboot flash recovery recovery.img to flash the Stock Recovery on the phone.
Step 11 - Reboot the device and enter anything as Password when the device asks for it. Now tap the Reset button to do Factory Reset. The phone will reboot to Stock Recovery and ask you to perform Factory Reset. Choose Yes to proceed and it will take a few seconds to do so. Voila!!! Your phone is successfully Decrypted and now you can boot into the Custom ROM you flashed.
Step 12 - As the phone is already Decrypted there is no need to keep the Stock Recovery. You can flash the Custom Recovery of your choice by going to the proper website and following the instructions to flash it on your device.
N.B : It took me a couple of hours to figure out the solution to this issue when I faced it and I wrote this guide so that it will help people who face the same issue in future. A Thanks! is much appreciated .
I work with "format data" in twrp
kuzo said:
I work with "format data" in twrp
Click to expand...
Click to collapse
That didn't work in my case.
Otherwise it's the easiest way to do so.
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
I did it at least four or five times and was unsuccessful.
The phone was only booting up normally with Stock ROM but always asked for Password if any custom ROM was flashed.
Then only I came up with the idea I posted here and was successful to remove the encryption.
data on the phone will not be deleted?
whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Step 7: ". . . the next steps will wipe the internal storage. Eject your SD Card from the device."
You should expect that data will be deleted.
whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Yes!
Step 10 will wipe the Internal Storage and the SD Card too if it is still in the device.
It's a safe practice to eject the SD Card before doing any operations.
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
io_gh0st said:
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
Click to expand...
Click to collapse
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted. Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted.
Click to expand...
Click to collapse
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
Wolfcity said:
Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
io_gh0st said:
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
Click to expand...
Click to collapse
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Edit: Check screenshots in the next post
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Click to expand...
Click to collapse
Sorry, wrong screenshots.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
io_gh0st said:
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
Click to expand...
Click to collapse
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
io_gh0st said:
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
Click to expand...
Click to collapse
Exactly. Here's the latest one:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Sent from my Moto G5 Plus using XDA Labs
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
itcanbdone said:
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
Click to expand...
Click to collapse
@Zackptg5 seems to have changed his side a bit, here's the actual link:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Do I need to select "Format Data" under "Wipe" to decrypt it? On TWRP, I see Wipe -> Format Data. If yes, do I need to remove SD card that has my system backup and custom ROM? Thanks.
---------- Post added at 03:14 AM ---------- Previous post was at 03:02 AM ----------
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
Are you referring to the "Format Data" tab under "Wipe" (that is, Wipe -> Format Data next to Advanced Wipe)? If yes, do I need to take out a SD card where I have a backup and custom ROM? Thanks.

Categories

Resources