Z17 bricked (sort of) after magisk v18.0 update - ZTE Nubia Z17 Questions & Answers

OK so updated like I always have with no problems via the manager, everything went fine patched boot Image ect with no errors, rebooted and now it just boots straight to fastboot, anyone got any ideas to fix without flashing a new rom, I've managed to back up pics ect with terminal.

Never mind I've fixed it just flashed with different rom, shame but not all is lost.

Related

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Tried doing a clean flash of latest OOS from official post, big issues happened.

I need help.
So I tried doing a clean flash, didn't work.
I was stuck at the loading screen when booting the phone.
I was previously on latest OOS 4.X.X with Magisk and TWRP.
Somehow, my OP5 was now back on stock recovery.
I just installed TWRP back again (blu's).
Everything is encrypted (in /sdcard/). I can't seem to transfer files to my cellphone, either through
HTML:
adb push
or manually dragging and dropping files from Windows 10.
TWRP doesn't ask me for my previous PIN, and I can't seem to tranfer files... any way I can gain access/install a rom again ?
At worst if I could find a way to push my TWRP backup and recover everything....
Can I flash a ROM that's on my PC without pushing it on the cellphone ?
Any help is greatly welcome and appreciated. Thanks for your help in advance guys.
EDIT: I've wiped everything and was able to tranfer and flash the latest ROM, then flashed TWRP again without rebooting.
Upon system boot, the welcome screen showed up, but android.com.phone kept crashing and after a while a factory reset happened.
I just pushed TWRP back again and I'm kind of wondering what to do now...
EDIT2: Flashed OOS 5.0.0, then realized 5.0.1 was out. I relocked the bootloader and did the OTA update since it was a clean, not rooted install. Working good... now I need to root it again.

I'm stumped on this (Rebooting into TWRP)

I've had this happen before on other phones, usually fixed by just installing a different rom or restoring a backup. Not here.
I finally unlocked my bootloader on the XT1607 (the Motorola site just randomly worked one day), installed TWRP & the 7.1.1 Soak Test (from here). I forgot to backup 6.0.1, so I backed up the soak test which was booting and working flawlessly. I was using it for a while, but I did a factory reset inside TWRP and it randomly said "cannot mount storage" and when I rebooted, it was into TWRP. It wasn't working at all, so I got LineageOS 15.1 and flashed that. Same error, "cannot mount storage" and back to TWRP. I went into Wipe>Format Data and then reinstalled Lineage. The "cannot mount storage" error was gone, but still booting into TWRP. I tried AOSP Extended, CyanogenMod, Paranoid Android. roms with gapps, roms without, with & without supersu or magisk. Nothing worked. So then I thought that restoring my backup (of all partitions) would fix the issue. It didn't, still booting back into TWRP. I'd also like to mention that plugging the phone in still worked, I can view the files in file manager, sd card works, etc.
So, no clue what to do here. What's wrong? It all started with that simple factory reset from twrp.
edit: I found that if I boot into bootloader and press start it will go into android, but hardly a permanent solution.
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
sumit1327 said:
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
Click to expand...
Click to collapse
Heyyy, thanks man. Worked like a charm.

Stock Recovery and issues with TWRP

Sorry I'm on mobile! Poor formating and typing is all my fault
So I'm out of my mind trying to fix and find a guide to fix my issues. This is how it all started
I was running the latest magisk (20.1) and OOS (9.0.17), when I installed Vance through magisk. I didn't read the instructions all the way, so I installed the module, it worked, then I saw that you can uninstall the YouTube system apk then install Vance. I deleted the Vance on my next reboot AND uninstalled YouTube system app, and I got stuck rebooting my phone. I have TWRP installed on my phone, not flashed (I didn't know the issues with TWRP when I installed the zip through TWRP). When it got stuck booting, I flashed magisk Uninstaller and it fixed the issue. I tried to reinstall magisk 20.1, and I got the same issue, stuck at boot. So I was able to go home, and use the oneplus 6t manager found here on the forums, which roots with magisk 18.0, and, it worked! But I couldn't update to the new magisk without it freezing my boot. After some deliberation on it, I decided to wipe my phone to try and fix it, and TWRP was still installed, and all my issues still persisted. After this setback, I found fastboot rom also on xda, and got it working, did an Ota to 9.0.17 from 9.0.16. Everything was working, until I went into my recovery and it wiped my phone. I don't even know where to go from here and I need help. Any and all help would be appreciated!
Edit: I just local upgraded to android 10 oos, and it seems to be fine. I don't know yet fully because I'm not at my house!

Phone bricked

So, I've rooted my phone using magisk a while ago and its been working since that. Today I downloaded a system app uninstaller and wanted to remove chrome (ik im retarded) and then when I rebooted it bootlooped. I could go in TWRP and I wiped data, then rebooted and now I can't get in TWRP. I tried many things, now when I boot my phone it goes in fastboot instantly and I can't do anything. When I tried to flash TWRP it said error bad Image. Anyone can help ?

Categories

Resources