So I was on mm with unlocked bootloader and i tried to update to nougat through the stock recovery but no luck (error status 7 or something like that) and i was like ehh screw it fastbooted twrp and flash supersu. that's when everything went side ways. bootlooped right after i clicked reboot system. it apeard a message saying that something DRM i didn't may atenction to it and something in red right before the asus image. can anyone help me out?
You skipped a step, you need to flash the no-verity file. You'll still have that DRM bootup screen but it'll be with yellow text.
https://forum.xda-developers.com/showthread.php?t=3569926
I have no idea how I managed to get into this situation.
My A2017G was on Oreo 8.1 RR with a treble partition. Since I wasn't happy with that I want to go back to the newest stock rom.
So i followed this Guide [GUIDE] [A2017G] Return to Stock from Custom ROM - Updated.
I flashed the bootstack, then I flashed the stock system and the result was a dfu brick. Meanwhile i have an Axon 7 teared down into pieces, so I'm able to flash with MiFlash.
I tried to flash these roms until now:
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS
A2017G_B09_NOUGAT_FULL_EDL
A2017G_B10_NOUGAT_FULL_EDL
ZTE_A2017GV1.2.0B10_Stock_System_by_raystef66 (+ ZTE_A2017GV1.2.0B10_BootStack_by_raystef66)
(I also tried to flash the "Remove Bootloader Unlock Warning" zip afterwards...)
My only chance to get into the TWERP Recovery is to replace an original recovery.img with the twerp one and flashing with the test point method.
All of them result in a dfu brick or stuck in the Axon7 logo screen after the animation (if i force a shutdown, it will result in a dfu brick too).
I'm out of any ideas since every single try result in a broken device. Does anyone has a suggestion what to do now?
No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.
I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default
tdm said:
No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.
Click to expand...
Click to collapse
keep this in mind, not all G users can do the cable procedure. He's just one more on a pretty big list. It's okay to suggest that unbricking without disassembly is possible but it's nowhere near 100% (or even 50% i'd say) effectivity. Same with FTM mode, people reported that they could get there after draining the battery, well it didn't work for everyone
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
Warcon said:
I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default
Click to expand...
Click to collapse
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done
Choose an username... said:
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done
Click to expand...
Click to collapse
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?
Warcon said:
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?
Click to expand...
Click to collapse
You have no fastboot, because N builds don't have it by default. If you select fastboot it simply boots into system. (in your case it attempts to, so it ends up in the same situation).
Try to install LOS14.1 maybe, since it's just modem, bootstack and ROM. I have zero hope that it'll work but it may as well do the trick. I have no idea why this is happening to you but it's just plain weird, I mean EDL should reflash most partitions
flashed TWRP 3.2.3
made a full edl backup
whiped data, system, cache, dalvik
flashed bootstack_O_b12
flashed oreo modem
flashed lineage-15.1-20180810
flashed pico gapps
it works now
Got an H910 which has been fine for the longest time. It was running LOS17.1 with nothing else besides magisk installed. It was also the official release.
A week ago i decided I wanted LOS18.1 instead, but I got multiple E1001 errors unable to modify System partition.
Someone suggested I went back to stock and root again or something, so i flashed Kitkat zip and have since been stuck on an endless loop of "no command" recovery mode.
my device is still being picked up as US996, but despite all my attempts I can't seem to be able to flash anything. LGUP always succeeds but the second the devide reboots the "erasing.." screen is shown for a split second before going into an endless loop of turning on and off the screen with "no command", and still showing as US996.
in theory fastboot was already unlocked but I don't think it's the case anymore after the kitkat file thing.
I'm currently out of ideas. Am I missing something?
Any help would be appreciated.
Hzlph said:
Got an H910 which has been fine for the longest time. It was running LOS17.1 with nothing else besides magisk installed. It was also the official release.
A week ago i decided I wanted LOS18.1 instead, but I got multiple E1001 errors unable to modify System partition.
Someone suggested I went back to stock and root again or something, so i flashed Kitkat zip and have since been stuck on an endless loop of "no command" recovery mode.
my device is still being picked up as US996, but despite all my attempts I can't seem to be able to flash anything. LGUP always succeeds but the second the devide reboots the "erasing.." screen is shown for a split second before going into an endless loop of turning on and off the screen with "no command", and still showing as US996.
in theory fastboot was already unlocked but I don't think it's the case anymore after the kitkat file thing.
I'm currently out of ideas. Am I missing something?
Any help would be appreciated.
Click to expand...
Click to collapse
Did you flash the nougat kdz in the dirtysanta root guide? I had a kernel crash problem and started over to fix, but I didn't flash a KitKat ROM in LGUp
I have a Huawei P10 Lite WAS-LX1. I had its bootloader unlocked in a phone repair shop (by shorting testpoint).
Now it always greets me with the message "Your device has been unlocked and can't be trusted".
I can load the boot into the bootloader and I can flash TWRP (I tried 3.4.0 and 3.3.1 from DarkJoker360 and also the one from Pretoriano80).
I am also able to flash system images, for example LineageOS from DarkJoker360.
At first that seemed to work to some extent: the new system kept crashing but at least it was booting.
I tried again and again and at some point I wiped everything but the sdcard using TWRP (that is, including the vendor partition). I suspect that's what I did wrong, because presently I can no longer boot into the ROM I am flashing. Instead, the phone waits for a few seconds, then vibrates once and restarts. The second time, it boots into "Huawei eRecovery" (where I can "Download latest version and recovery", "Wipe data/factory reset", "Reboot" or "Shutdown"). I am afraid of attempting to go back to the stock ROM as I wouldn't want the bootloader to become locked again.
Since I can still boot into both the bootloader and the recovery, I have hope I can recover. But I don't know how.
Does anyone understand what happened (and could explain)?
Also, does anyone know how I could boot into the ROM again?
Never mind. I went back to stock. Also, the bootloader became locked again during the process, so I will not try again.
So I wanted to install lineage OS for this Nokia 6 phone, but in the process of installing something went wrong. Suddenly I couldn't boot into the system (which was expected), and I also couldn't go to recovery either. Not twrp, not even the stock recovery. I can still go to the bootloader with fastboot tho and issue commands. I also tried re-flashing the firmware on the phone, but that doesn't help. Is my phone bricked? How can I fix this? Thanks.
Edit: The bootloader is unlocked.