heres the premise on stock secure start up enabled . I disabled it and proceeded with rooting . installed twrp formatted system factory reset wiped system etc etc .. then I flashed rom when It booted it asked for secure start up as if I never disabled .. i put in the original code didnt work after 30 attempts encryption unsucessful ,, since then it boots straight to twrp .. now I found the problem ,,, system keeps unmounting itself ,, I tried every solutionvia the threads no avail . maybe need a kdz . i tried to repair system etc etc tried both twrp in mount system is always uncheked ,. if I check it flash rom and go back to mount . it will uncheck itself idk whats happening twrp acts as if the flash is succesful but system will be unchecked ...
Same issue here please find a [email protected]!!
christiansfreeman said:
heres the premise on stock secure start up enabled . I disabled it and proceeded with rooting . installed twrp formatted system factory reset wiped system etc etc .. then I flashed rom when It booted it asked for secure start up as if I never disabled .. i put in the original code didnt work after 30 attempts encryption unsucessful ,, since then it boots straight to twrp .. now I found the problem ,,, system keeps unmounting itself ,, I tried every solutionvia the threads no avail . maybe need a kdz . i tried to repair system etc etc tried both twrp in mount system is always uncheked ,. if I check it flash rom and go back to mount . it will uncheck itself idk whats happening twrp acts as if the flash is succesful but system will be unchecked ...
Click to expand...
Click to collapse
sounds to me that you are in the twrp looping. If you already flashed a rom, do the following factory reset on twrp, go to reboot options. press power off (do not press the reboot one otherwise you will be back into twrp). After the phone is completely off, proceed to turn it on.
Now if this didnt work, erase cache, data, dalvik, system, and insternal storage, then flash the rom again, after is flashed, do a factory reset, after that go to the reboot options and press on turn off. then proceed to turn it on. IT should initialize normally.
Both of these have helped me to get out of the twrp looping
Same Here
I rooted, modified build.props to bring back multiuser, and haven't done anything else. It's been working fine. This morning I woke to twrp and it won't boot back into normal phone. I even tried restoring from a previous backup, which finished successfully but when restarting, lands me back in twrp. I'll try the steps listed previously, though I though a restore did wipes...
ironosity said:
I rooted, modified build.props to bring back multiuser, and haven't done anything else. It's been working fine. This morning I woke to twrp and it won't boot back into normal phone. I even tried restoring from a previous backup, which finished successfully but when restarting, lands me back in twrp. I'll try the steps listed previously, though I though a restore did wipes...
Click to expand...
Click to collapse
Try this. When you are at TWRP, go to the reboot menu then press on power off (or turn off) instead of on reboot. Then turn on the device. It should work fine after that. I had that issue and after messing around for few minutes i found out this worked for me.
jinkerz9430 said:
Try this. When you are at TWRP, go to the reboot menu then press on power off (or turn off) instead of on reboot. Then turn on the device. It should work fine after that. I had that issue and after messing around for few minutes i found out this worked for me.
Click to expand...
Click to collapse
Sadly, didn't work. Not running a custom rom so after wiping everything tried a restore from backup. Powered off and back on. Just comes back into twrp.... :'( Oh, and like OP, if I go into mount, system is always unchecked. not sure if it should be but changing it just toggles back on reboot.
ironosity said:
Sadly, didn't work. Not running a custom rom so after wiping everything tried a restore from backup. Powered off and back on. Just comes back into twrp.... :'( Oh, and like OP, if I go into mount, system is always unchecked. not sure if it should be but changing it just toggles back on reboot.
Click to expand...
Click to collapse
can you try the steps i wrote in Post #3 ?
go here 3rd post
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
@Team DevDigitel has a guide
Sorry, didnt have time to fix it earlier. I just reflashed stock over my recovery. Lost root. Not sure ill reroot yet. Thanks for your suggestions though.
You just needed to do the power button plus volume down button startup to get to the factory reset procedure. You most likely had a system update downloaded to your internal memory that triggered the twrp loop. Many of us have been through this for hours and hours.
Literally takes a minute to fix.
Related
I just rooted my Galaxy S4 (model SGH-I337 AT&T) (I have not installed any ROMS either) and I went to back it up once more in recovery mode but when it went to reboot, it froze. It booted up normally but then froze when the AT&T logo is spinning. I can take the battery out and turn it on but the same thing happens. When I go to recovery mode to reboot, same thing happens. I have wiped cache partition and rebooted, same thing. I have restored my 2 backups, one failed and the other the same thing happens, I have rebooted to bootloader but that brings me to a screen saying downloading... with a android guy then the only way to get out of that is taking the battery out. I have tried wiping data/factory reset but it fails while restoring data. Nothing is working! Please help. I am very knew to rooting by the way. I have Clockworkmod recovery too by the way if that matters. Thanks in advance.
I am going out on a limb here, did you do a factory reset within the recovery? If not, try that. should boot just fine, IF, you said, you have not flashed any custom roms yet.
Good luck.
If that does not work, please search ODIN, because I am afraid that is the next step.
Thank you.
Galaxy S4 bricked
TheAxman said:
I am going out on a limb here, did you do a factory reset within the recovery? If not, try that. should boot just fine, IF, you said, you have not flashed any custom roms yet.
Good luck.
If that does not work, please search ODIN, because I am afraid that is the next step.
Thank you.
Click to expand...
Click to collapse
Thanks for replying. Yes I did a factory reset in Clockworkmod recovery many times. Froze in the same spot. Then I saw a Youtube video on how to use ODIN and it worked perfectly. ODIN said "pass" but when it rebooted, same problem! Then I wasnt able to enter recovery mode, it just froze. Now I am able to enter stock recovery but still nothing is working. Should I try ODIN again? I am almost positive I used the right firmware too. my options in recovery are Reboot system, apply update from ADB, external storage,or cache, wipe data/factory reset, wipe cache partition. thanks again for the help
now that you have flashed back to stock with odin, wipe data and reboot.
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
This may be an issue with TWRP. When I had my Galaxy S3 rooted back in the day I would have this issue, also with a Nexus tablet I rooted as well. It turns out I needed to flash a specific "fixed" version of TWRP to fix the mount/flash issue. That was a long time ago though, so this might not be the problem, but I thought I would at least tell you my experience.
Sent from my LG-LS997 using Tapatalk
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I beleive you have to do Dirty Santa over again....The steps that is.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
imucarmen said:
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
Click to expand...
Click to collapse
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
biglightbt said:
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
Click to expand...
Click to collapse
I would run the dirtysanta exploit again from the beginning. Your assumption about being stuck in read only seems correct. I'm guessing you might have chosen read only on accident one time when you booted into TWRP and now it's stuck there.
Or you could try using flashfire to flash the TWRP.img
I am having the same issue. I tried doing the DAC mod that enables high impedance as always on. Audio quit working along with the stock music app. Did a restore from after I flashed the konverged kernel. And now no r/w ability and twrp will not mount system unless I check mount as read only. I was able to reinstall supersu from the recovery. But still have the issues.
Only thing I can think of is waiting for a return to stock unrooted method to Come out and re-root.
biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Hey I was having the same problem and I fixed it myself messing around with a few things I could think of.
Here it is pasted from another thread.
Dinked around with a few ideas and got my problem fixed! Heres what I did.
1. Made a backup of system in twrp just in case.
2. Formatted system in wipe > advanced > and only checked system.
Panicked because I thought I bricked my device, wouldnt boot farther than the lg logo,
(next steps might be unnecessary but I panicked and tried them lol)
3. still had fastboot access so I repeated step 3 in the root method.
4. Reflashed boot2.img
5. Rebooted to recovery with volume- power, release power while keeping volume- at lg for a second then repress and hold power. Yes twice to get to recovery.
6. Restored system backup. (was able to fully boot now but with lag)
7. Reflashed konverged kernel.
And everything is working perfect now and I have my r/w ability and can mount system in recovery without having to select mount as read only.
---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------
You can probably just wipe your system like I said in the previous post then Just restore it. I panicked and did a bunch of extra stuff. I realized that when I did my initial backup of my system, or said that its size was about 126247251477482716MB. So I'm guessing when I did my restore (possibly what happened to yours) that it somehow messed up the system.
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.
I unlocked the bootloader, installed TWRP all went well, however upon rebooting I was back in recovery not the ROM, no big deal. I wiped data and installed a custom ROM, again all went well, however upon reboot back in recovery. Tried shutdown and restart, same thing. Tried a different ROM, same thing, starting to get worried now, as I do not seem to be able to boot except for into recovery, which I obviously do not want.
Last ditch:
Power, off, <volume> and Power -> start Same bootloader unlocked screen, then ... recovery.
Any suggestions as to what I'm doing wrong?
Thanks,
ERIC
egandt said:
I unlocked the bootloader, installed TWRP all went well, however upon rebooting I was back in recovery not the ROM, no big deal. I wiped data and installed a custom ROM, again all went well, however upon reboot back in recovery. Tried shutdown and restart, same thing. Tried a different ROM, same thing, starting to get worried now, as I do not seem to be able to boot except for into recovery, which I obviously do not want.
Last ditch:
Power, off, <volume> and Power -> start Same bootloader unlocked screen, then ... recovery.
Any suggestions as to what I'm doing wrong?
Thanks,
ERIC
Click to expand...
Click to collapse
Try to flash lazyflasher I may wrong though but that work for me
egandt said:
I unlocked the bootloader, installed TWRP all went well, however upon rebooting I was back in recovery not the ROM, no big deal. I wiped data and installed a custom ROM, again all went well, however upon reboot back in recovery. Tried shutdown and restart, same thing. Tried a different ROM, same thing, starting to get worried now, as I do not seem to be able to boot except for into recovery, which I obviously do not want.
Last ditch:
Power, off, <volume> and Power -> start Same bootloader unlocked screen, then ... recovery.
Any suggestions as to what I'm doing wrong?
Thanks,
ERIC
Click to expand...
Click to collapse
I did the same thing you did, and got stuck where you were. I believe what I had to do was wipe every partition under Advanced Wipe, then copy the ROM over, and then install the ROM.
egandt said:
I unlocked the bootloader, installed TWRP all went well, however upon rebooting I was back in recovery not the ROM, no big deal. I wiped data and installed a custom ROM, again all went well, however upon reboot back in recovery. Tried shutdown and restart, same thing. Tried a different ROM, same thing, starting to get worried now, as I do not seem to be able to boot except for into recovery, which I obviously do not want.
Last ditch:
Power, off, <volume> and Power -> start Same bootloader unlocked screen, then ... recovery.
Any suggestions as to what I'm doing wrong?
Thanks,
ERIC
Click to expand...
Click to collapse
Wich commands did You use to flash twrp?
Maybe did you flashed it in boot partition and not in recovery partition
Thanks, Trying again this and only this works seems to work.
Last ditch:
Power, off, <volume> and Power -> start Same bootloader unlocked screen, then ... Android
Anything else as in simply turning it on results in recovery. Thus it appears that the Android is correct, it seems to be that the default boot option is set to twrp and not the Android however. Selecting Power, off, <volume> and Power ->Recovery Mode goes to TWRP.
I formated, System, Data, Cache and reinstalled without any change to the way it boots.
I also tried RR 5.8.3, AOKP and both with the same result.
I flashed using fastboot recovery twrp-3.1.0-0-n3-potter.img
ERIC
Did you flashed the opt out dm verity? Read the guide carefully.
Enviado desde mi Moto G (5) mediante Tapatalk
maybr u have erased ur rom, flash stock rom
Maybe u have wiped ur stock os. go n flash stock rom n then try again
Got it working.
Restored stock and then re-fashed TWRP, since had the issue (i have 2 phones, on one the second time I flashed TRWP, but the other went fine). Repeated again on the second phone now all is well.
Thanks,
ERIC
egandt said:
Got it working.
Restored stock and then re-fashed TWRP, since had the issue (i have 2 phones, on one the second time I flashed TRWP, but the other went fine). Repeated again on the second phone now all is well.
Thanks,
ERIC
Click to expand...
Click to collapse
Hi, where can I get the stock rom, and what is the procedure to install it in fast boot? I can only boot into recovery mode as well.
Thanks
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.