Hopefully someone can help. There was an update on Google Play today for the Chainfire SuperSU. I ran the update, clicked the message that I needed to update the binary, chose TWRP (I'm on 2.8.7.0), and the phone rebooted. After booting, it went into recovery, tried to run something (I wish I had written it down), and rebooted again. It did this again and again, looping about 10 times before I finally held the power button. At that point, the phone tried to boot normally, but never went past the boot animation (waited about 30 minutes).
I can still get into recovery, luckily... I just don't know what I should do at this point. I am running the stock MM, just debloated.
From which SuperSU version did you run the update?
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.
andry23jsv said:
From which SuperSU version did you run the update?
Click to expand...
Click to collapse
The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.
jason2678 said:
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
Click to expand...
Click to collapse
I had tried all that. It's usually the first thing I do when I have issues like that.
Hey, i am using a note 4 . Currently my phone is in recovery mode and is boot looping. It would boot for 2 secs then reboot again. i cant exit the recovery mode at all the clear any cache or stuff. I may have misclicked the normal boot and clicked the TWRP after updating supersu. Is there a fix for it?
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Flapjack said:
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Click to expand...
Click to collapse
hi the problem is that i cant get pass the recovery mode. its there for about 2 secs then gone
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Flapjack said:
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Click to expand...
Click to collapse
Hey man tks for replying so promptly though. I think i know what went wrong. Just that i don't know how to fix it. My phone is now recovery booting through TWRP. But i don't remember having TWRP. Is there a way to change the boot to normal?
Related
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
Hi,
I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.
I decided to look for a stock ROM and flash that ROM.
I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.
Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.
I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?
After this I took these steps solve this issue:
1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)
2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.
Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.
My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.
3. Installed LG Bridge for more drivers; did not work either
4. Downloaded Uppercut, but it doenst work without LGUP.
4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing
5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.
7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.
I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.
Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.
Really hoping for a kind person to help me out and provide me solution for this issue.
Thanks in advance
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
autoprime said:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
Click to expand...
Click to collapse
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
RoyalD said:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
Click to expand...
Click to collapse
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.
Had the same issue, fixed it, thanks.
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.
RoyalD said:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
Click to expand...
Click to collapse
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...
Well, I finally solved it with lgup and uppercut... what a nightmare.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash stocl .kdz with uppercut and lg up
Saved my G6!
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Great tip @Swizzle82! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!
Hi, all
If I understand, and to sum up :
I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/
Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?
Thx
I just rebooted my phone into recovery mode using this quick reboot pro app, it worked fine, I just wanted to test out the app so I wanted to reboot. I pressed the reboot button in TWRP, I pressed system, I saw the boot logo, but it didn't boot and it just entered the TWRP. I tried to reboot again, the same thing happened. I'm basically stuck in the recovery. I didn't try wiping data and cache or anything like that, I don't want to mess up my phone more. Can someone help me out here, I don't know what to do to fix it
ntldrmissing said:
I just rebooted my phone into recovery mode using this quick reboot pro app, it worked fine, I just wanted to test out the app so I wanted to reboot. I pressed the reboot button in TWRP, I pressed system, I saw the boot logo, but it didn't boot and it just entered the TWRP. I tried to reboot again, the same thing happened. I'm basically stuck in the recovery. I didn't try wiping data and cache or anything like that, I don't want to mess up my phone more. Can someone help me out here, I don't know what to do to fix it
Click to expand...
Click to collapse
Hello there, i had the sane problem one Day, never use an App tha reboots into recovery or bootloader, it Will be stock. For the fix, You have to flash the official Samsung firmware 5.1.1 or 6.0.1 via odin And your Phone Will be Just fine.
Kostas172 said:
Hello there, i had the sane problem one Day, never use an App tha reboots into recovery or bootloader, it Will be stock. For the fix, You have to flash the official Samsung firmware 5.1.1 or 6.0.1 via odin And your Phone Will be Just fine.
Click to expand...
Click to collapse
Or just reflash twrp with odin. This will reset the reboot flag.
As said use the button combo to boot to recovery and you won't have an issue.
ashyx said:
Or just reflash twrp with odin. This will reset the reboot flag.
As said use the button combo to boot to recovery and you won't have an issue.
Click to expand...
Click to collapse
Thanks man! The phone works completely fine now
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.