I am currently running 7.0 with the main phone not encrypted, i unroot and update with Odin with the home-CSA file and it updates fine and runs fine, then reroot with superuser and every time i get a boot loop.
How can i reroot without the boot loop and also how can i restore a normal boot without reflashing a twrp backup, if possible?
Please help.
lofty5 said:
I am currently running 7.0 with the main phone not encrypted, i unroot and update with Odin with the home-CSA file and it updates fine and runs fine, then reroot with superuser and every time i get a boot loop.
How can i reroot without the boot loop and also how can i restore a normal boot without reflashing a twrp backup, if possible?
Please help.
Click to expand...
Click to collapse
Hi mate
You say you update your firmware with Odin and home_csc, afterwards you re root , my questions
How you re root? you flash TWRP and then flash SuperSu?
Please explain what you mean "how can i restore a normal boot without reflashing a twrp backup"
MAX 404 said:
Hi mate
You say you update your firmware with Odin and home_csc, afterwards you re root , my questions
How you re root? you flash TWRP and then flash SuperSu?
Please explain what you mean "how can i restore a normal boot without reflashing a twrp backup"
Click to expand...
Click to collapse
I reroot by flashing twrp then installing in twrp the lastest version of su and it then boot loops.
The second part, what I mean is lets say i do this and it is now boot looping is there anyway to undo it without doing a complete twrp restore.
A way around the root boot loop is to format/factory reset first, root and then restore apps and settings with titanium, but I cba doing that every time i need to update as its to much hassle.
Only solution perhaps is to update proper format to decrypt data, root and then restore data with twrp, but surely there has to be a better way?
lofty5 said:
I reroot by flashing twrp then installing in twrp the lastest version of su and it then boot loops.
The second part, what I mean is lets say i do this and it is now boot looping is there anyway to undo it without doing a complete twrp restore.
A way around the root boot loop is to format/factory reset first, root and then restore apps and settings with titanium, but I cba doing that every time i need to update as its to much hassle.
Only solution perhaps is to update proper format to decrypt data, root and then restore data with twrp, but surely there has to be a better way?
Click to expand...
Click to collapse
Are you saying you can root factory resetted Nougat? How would you back up with Titanium if it's not rooted? lol
lofty5 said:
I reroot by flashing twrp then installing in twrp the lastest version of su and it then boot loops.
The second part, what I mean is lets say i do this and it is now boot looping is there anyway to undo it without doing a complete twrp restore.
A way around the root boot loop is to format/factory reset first, root and then restore apps and settings with titanium, but I cba doing that every time i need to update as its to much hassle.
Only solution perhaps is to update proper format to decrypt data, root and then restore data with twrp, but surely there has to be a better way?
Click to expand...
Click to collapse
Did you flash TWRP and do all the steps?
for example what do you do at step 9
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
And afterwards flashed the latest dm-verity and force encryption disabler zip.?
MAX 404 said:
Did you flash TWRP and do all the steps?
for example what do you do at step 9
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
And afterwards flashed the latest dm-verity and force encryption disabler zip.?
Click to expand...
Click to collapse
I swipe right and immediately install su as its already on the zip and then reboot, i thought the other stuff wasn't needed as su is supposed to install the dmverity thing automatically., guide says its for bootable system only as well, do i need to flash su and then those other 2 files to get the thing to boot?
I will try this tomorrow, i don't ever remember having to do those other 2 files in the past on mm.
lofty5 said:
I swipe right and immediately install su as its already on the zip and then reboot, i thought the other stuff wasn't needed as su is supposed to install the dmverity thing automatically., guide says its for bootable system only as well, do i need to flash su and then those other 2 files to get the thing to boot?
I will try this tomorrow, i don't ever remember having to do those other 2 files in the past on mm.
Click to expand...
Click to collapse
As soon as you swipe right you must install dm verity unless you install a custom rom or custom kernel , is been like that since MM
MAX 404 said:
As soon as you swipe right you must install dm verity unless you install a custom rom or custom kernel , is been like that since MM
Click to expand...
Click to collapse
Before installing su?
lofty5 said:
Before installing su?
Click to expand...
Click to collapse
it really does not matter which one first , what it matter is that is done before you reboot......so you do not go into a bootloop
MAX 404 said:
it really does not matter which one first , what it matter is that is done before you reboot......so you do not go into a bootloop
Click to expand...
Click to collapse
just gets stuck on Samsung loading screen. I tried this a few months back always same issue infinite or looping loading.
Alot of red errors and unable to mount during the install of dm verity as well if that's of any use.
I've never been able to root nougat without fully formatting to decrypt system first and then reinstalling everything.
i get failed to mount '/data' (invalid argument)
unable to mount storage
lofty5 said:
just gets stuck on Samsung loading screen. I tried this a few months back always same issue infinite or looping loading.
Alot of red errors and unable to mount during the install of dm verity as well if that's of any use.
I've never been able to root nougat without fully formatting to decrypt system first and then reinstalling everything.
i get failed to mount '/data' (invalid argument)
unable to mount storage
Click to expand...
Click to collapse
Hi
Odd mate , really odd
Is clear the issue is with your mount point but i do not know the why......
MAX 404 said:
Hi
Odd mate , really odd
Is clear the issue is with your mount point but i do not know the why......
Click to expand...
Click to collapse
A full format to decrypt data, rooting and then restoring data from a twrp backup works but its a bit long winded to be doing it every time there's an update.
Related
hey guys, I have moto g xt1033 after installing cm13 i stuck in boot loop cm13 logo..please help me out
please..i dont wanna loose my phone.
you sure it's a boot loop? I just installed mine on a GS Tab and noticed a significant amount of time for booting, which I thought was a loop also, which took much longer than usual.
Try booting into recovery mode and see if there are any error messages that will show
Do you have any kind of custom recovery?
We need more info about your device.
chacky13200 said:
Do you have any kind of custom recovery?
We need more info about your device.
Click to expand...
Click to collapse
yeah i have twrp custom recovery, toady i have wiped my cell and now my device says os is not install,
and my device is working on "fastboot device" but does not works on "adb devices" help me and thank you for reply
Abhishek_singh said:
yeah i have twrp custom recovery, toady i have wiped my cell and now my device says os is not install,
and my device is working on "fastboot device" but does not works on "adb devices" help me and thank you for reply
Click to expand...
Click to collapse
TWRP is still working?
user822 said:
TWRP is still working?
Click to expand...
Click to collapse
yeah recovery shows twrp v2.8.0.6....how may i know is that working or not??
Abhishek_singh said:
yeah recovery shows twrp v2.8.0.6....how may i know is that working or not??
Click to expand...
Click to collapse
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
user822 said:
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
Click to expand...
Click to collapse
Thank you bro thank you so much....:good::good:
hey I am still facing "adb devices" problem what can i do?
user822 said:
Then you are all set.
In the wipe menu, wipe /system and /data and /cache (this will nuke your data) to get rid of all leftovers that might have caused the bootloop.
Plug it into a PC, copy Cyanogenmod over (this time verify the sha1sum, against the one on the download website, to make sure the download is correct and did not cause the bootloop)
Install Cyanogenmod, without Gapps for the first test
Bootloop should be gone
If the bootloop happens again, you might need a newer version of TWRP, but 2.8.x.x should do the job.
Click to expand...
Click to collapse
on my moto g xt1033,
after, installing ROM CM-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon
Then i, installed Gapps = ARM_6.0_micro (opengapps.org)
then everything is fine play games, etc.
i installed super su from play store, but unable to update binary!
so boot into recovery and flash UPDATE-SuperSU-v2.46.zip
now i stuck in boot loop,
(Earlier Point)now what to do?> and after installation of rom twrp asking me for partition modification- Keep Read-Only OR Allow Modification. i select allow modification. so where i go wrong?
NOw stuck in boot loop, i can able to in Fastboot and select recovery also,
so what do i do, option 1-> wipe everything n install rom , gapps again.
option2-> without wiping install rom (like doing overwrite) on already installed rom.
and also suggest how to ROOT? which superSU.zip i flash on cm13
I have TWRP 3.0.2-0 version working fine.
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.
This problem has been solved?
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.
hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..
MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
update: it's all gucci, i've managed to figure it out.
Have you tried the patched twrp version? There is a link in google camera port thread. I havent tried but that could work.
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
not a professional but coincidentally this happened to me today while rooting and installing twrp on my s7 sm-g930L 8.0, i installed twrp 1st and was just using a supersu.zip to root it, booted straight into twrp after flashing and had the same problem you have and couldnt install the zip as it wasnt showing up and also saying 0mb, i couldnt even send the zip to it from my computer either until i pressed format in the wipe menu next to advanced wipe button , it was in a bootloop so i hit format cause i was just gonna reinstall stock firmware but i noticed all the correct mb's appeared in system data etc and i could copy/paste n install the zip, flashed it rebooted and it all works, rooted and twrp on official fw 8.0, you might have to reinstall apps and stuff after but hopefully this helps, goodluck
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
ttuleyb said:
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
Click to expand...
Click to collapse
This is just temporary the next time you flash you will see 0mb again you will need to format again.
mkl.xda said:
This is just temporary the next time you flash you will see 0mb again you will need to format again.
Click to expand...
Click to collapse
Unless you flash decrypt zip before booting after flashing
ttuleyb said:
Unless you flash decrypt zip before booting after flashing
Click to expand...
Click to collapse
Still the same. Tried it many times.
mkl.xda said:
Still the same. Tried it many times.
Click to expand...
Click to collapse
Try using superman rom and use option called disable encryption that might work,
If you just wanna root then install magisk because it works with encryption
hey guys i finally got my twrp back up and running here it is and i fixed format issue it had also supports f2fs now which is what stock uses and added a couple extra parititons it mounts and backs up
use cmd to flash twrp:
fastboot flash recovery updated-hannah-twrp-2019.img
hannah twrp:
https://drive.google.com/file/d/1ahEDJRaW6ZbpF7EgokQtQ6TEJ8yBUa9d/view?usp=drivesdk
cmd for nora:
fastboot flash recovery nora-twrp.img
nora twrp:
https://drive.google.com/file/d/12IPnevc7si2sNpxChMtPo5JJgwY4DJXh/view?usp=drivesdk
Sry i went MIA had alot happen lately so anyways im back here u go
for decryption patch a backed up boot.img with magisk beta both preserve boxes unchecked then flash in twrp as boot.img and flash zip below thanks @whodat711 for zip
https://drive.google.com/file/d/1-C4-ktJmW_oeyP1f5SAPGy3CX90mDuts/view?usp=drivesdk
then format data not wipe but format data button then type yes and press back all the way to main menu then flash masgisk 18.0.zip then reboot and it will not encrypt and u will have to start over as if phone is brand new ie. setting up google but enjoy ur decrypted e5+......
1.boot twrp and backup boot.img
2.make patched boot.img with magisk all perserve boxes unchecked while making it with magisk manager
3.flash twrp
4.flash patched boot.img and decryption zip from third link in post
5.format button in wipe section
6.flash magisk
7.reboot
Stock ROM MetroPcs xT1927-4 Hannah_T running good
skullkid383 said:
First and foremost I want to thank everyone in the twrp building group on telegram and @TwrpBuilder for the amazing guide on how to build twrp and guidance they gave to build this twrp
https://github.com/TwrpBuilder/twrpbuilder_tree_generator/wiki
So here is the twrp I built
https://drive.google.com/file/d/1aNTE6iAQQ4Ty1Zr1oM9ADb7xX_slrTzt/view?usp=drivesdk
After u flash twrp u need to edit fstab to disable force encryption then wipe phone flash latest beta magisk and ur all set
Refer to this guide for
Force encryption fstab file and how to disable force encryption thanks for this @CodyF86
https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
Click to expand...
Click to collapse
just installed your Hannah-twrp.img and it booted just fine everything works thanks
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Thank you so much for this!
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues. Thanks for your work.
Click to expand...
Click to collapse
Yes sir
jokono421 said:
Can you correct me if I'm wrong. So once I finish this process. I can go in and out of recovery with out computer. Also Then I can put apps directly into priv system with correct read and write,plus it will stick on reboots. Just wondering to .If this means I can flash custom kernals and roms with no worries other than normal issues.
Click to expand...
Click to collapse
So you can actually boot from device now yes awesome ...
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
JimmyJurner said:
Keeps trying to force encryption but fails when flashing a gsi.
Is there a way around this? No verity for this device?
Click to expand...
Click to collapse
Are u on stock with root I got easy solution for u to follow if fstab guide above is to hard
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Project89Odin said:
Hey skullkid383, thankyou for your work on this!! Twrp flashed and works NP. But I cannot decrypt. Following steps, the step you mount before pushing in twrp adb does not work, no such folder. The push goes thru fine although the mount did not. Format data worked, I can see internal storage and move things to and from PC through tether. But when I reboot its sticks on moto screen. When I flash back to patched boot for magisk the is boots to an "decryption unsuccessful" msg and asks me to reset the phone endlessly. Any help pls?
Click to expand...
Click to collapse
I'm looking into how to flash fstab in a zip cause I don't think fstab worked for some reason try patched boot.img here see if it changes anything wipe after flash https://drive.google.com/file/d/1s-nS6rLk1tnO1JVFO1emTJdGcO6mNhBk/view?usp=drivesdk
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Project89Odin said:
With this boot and wiping after fastboot and twrp installs it boots past moto logo but hangs with the decryption unsuccessful msg
Click to expand...
Click to collapse
Ok so ur fstab is not edited for some reason so do u have a old stock backup I will have u change fstab manually in stock then boot to the twrp and wipe
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Project89Odin said:
I do not, I'll have to fastboot flash everything back to revert to stock. Was rockin with no SD tonight.
Click to expand...
Click to collapse
Grrr always make backup rule number one lol ok I'm looking into getting a flashable zip made but in mean Time revert stock tell me when booted
Back up fully stock, not even twrp lol. Metropcs variant btw
Project89Odin said:
Back up fully stock, not even twrp lol. Metropcs variant btw
Click to expand...
Click to collapse
1st make a backup just in case:
Ok here we go flash twrp and magisk beta then patched boot.img boot system get a file explorer with root permissions edit fstab.qcom find it here: /vendor/etc.
just replace current one with one I'm uploading
in guide to make easier to find wipe then u should be good of course flash magisk beta after u wipe as well
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Project89Odin said:
Hmm still decryption unsuccessful. About to reflash to stock. Sorry for the slow response. I have the next several hours free to test. I don't have an SD card, so i rooted the old way, using your patched boot, then used es file explorer to replace fstab, rebooted to confirm, and fstabs permissions had changed from rw r r to rw rw so it stuck. once I format data and internal becomes visible I move magisk over, flash then reboot and get dencryption unsuccessful. Also even flashing the recovery before formatting resulted in it being lost every reboot, only after format data it stuck.
Click to expand...
Click to collapse
Ok I am going to build new one in awhile my PC screen broke idk when but until then the link to Hannah twrp is down till I fix it
Ah man, so instead of fastboot flashing everything back to stock, I figured I'd just flash stock recovery back, after the decryption unsuccessful route. Flashed stock recovery, when it booted and asked me to reset the phone instead of going to twrp this time it went to the stock recovery image of a reset...phone booted, got to looking around and holy crap I'm decrypted! flashed your twrp and now I'm rooted with twrp and decrypted!! So maybe boot twrp the first time when formatting data and decrypting so when you boot and the device asks you to reset because of decryption failure it can use stock recovery to complete the process, then flash twrp for the finish? Your incredibly helpful man, again thankyou for all of your efforts and work on this!!
Still wanna fix twrp found a issue in formatting data I wanna fix but it shall take some time to get it done link is down til then cause it's something that needs fixed first before I put it back up