Hello i have out of the loop for quite some time, and i flashed TWRP at some point in the past. but now i wanted to update to 7.1.1 and i can't when i try to use the official zip from german zte is says that the update failed. and when i try to get into recovery there is nothing or boot loop i tryed axon7toolkit and unbrick through EDL option but MiFlash fails to detect my phone. and i tried reinstaling drivers twice. Any idea how to get out of it? Btw i can use the phone just fine. But i would really like to move to Nougat
EDIT: for some uknown reason axon7tool on the nth try managed to flash the recovery. Before that i opened zading and his install WCID drivers and rebooted and that helped so SOLVED
Related
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
hello,
as the title says, my phone bricked while trying to go back to stock rom. this is what i did: i had a well working meticulus custom rom + the meticulus twrp recovery on my phone. thing is i need the google apps and they are not supported on meticulus roms. so i tried to go back to rom, downloaded a stock rom and tried to flash it with dragging it onto my sdcard and installing it from there. so this is when it bricked, the huawei logo appears at the start but it stays and nothing will install.
i tried to reinstall the adb drivers, no success. i can only use the bootloader but i can only flash a recovery, after trying to boot into the recovery via fastboot boot recovery.img it won´t do a thing. also the recovery is stock recovery all of a sudden (erecovery). and there i only have the option to "download latest version and recovery" but that gives an error aswell.
i´ve tried to reinstall drivers, no luck. when i do a fastboot devices it shows my device but when i do adb devices it doesn´t show up anything. so the usb driver is somewhat corrupted. my computer detects the phone when in fastboot only.
i´ve tried to reinstall the drivers a hundred times, i can´t get the phone to work anymore.
i would really appreciate it if someone helps me out.
While trying to install TWRP via JasmineTool, completely missed the part on first run and now I got the dreaded Your Device is Corrupt error.
I can't go into recovery, it just reboots. I had backups of what I had on the device and I can go back to EDL mode via first DFU Mode, then use ZTE Terminal Software Framework . I can re-flash the backups, it looks successful, but still same issue
I tried to flash b15 or b17 recovery and boot img files, they fail with unknown error.
Any suggestions?
I am making progress... As I found out in another thread, the error is about rebooting and I was not being patient after selecting Recovery (it reboots, then error, then you wait and it boots into TWRP).
So now trying to flash Lineage, we'll see
All good... I am back in business
A little while ago I downgraded my phone. Today I tried to install magisk with a custom rom and TWRP. It didn't work now when I boot my phone it gets into fastboot I have tried formatting it with TWRP and reinstalling the rom but it doesn't fix it. Are there any solutions (downloading to stock via erecovery doesn't work but I can easily open the erecovery menu.
Fastboot says
Android reboot reason:
bootloader 1
no
NA
reboot_enter_fastboot_common_func
I think there is something wrong with the vendor
Solution:I used the dload trick to download stock firmware
Problem 2:I reinstalled TWRP with a custom rom now my phone keeps restarting and not opening the custom rom.
try this rom
https://forum.xda-developers.com/ma...havoc-os-huawei-honor-hi6250-devices-t3813738
Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode