Yesterday I tried to update my Zuk's firmware through TWRP and when I got to the step I had to update the TWRP it seems that it failed to update and the recovery mode has been deleted. Also there is no System UI installed in my device, so my phone boots only on fastboot mode. Also, my pc doesn't recognize my device when I connect it via USB and I can't do anything with cmd or qfil. Is there any way I can install recovery and/or firmware to my device? Thanks
Related
I have rooted my phone using supersu by cwm
and after that the phone rooted and was working perfectly and yeterday i got an update from asus and a started dwonloading it but it not installed so i downloaded firmware from asus site and it not installed also so i started working using cwm and try to install using install update from zip and it not works also after that the phone didnt works the main problem that i just executed this command fastboot flash recovery 4.3.6_ww_recovery.img and 450cg doent have recovery mode and later i know that i have to disable/uninstall super su and thier require 1 gb space now i need to boot into cmw i think the recovery makes the problem after running fastboot flash update updateCWM_6.0.2.8_fix_wipe.zip this the phone restars and shows asus logo and nothing happens what will i do now after ruuing this command it not even loads droidboot
fastboot flash recovery droidboot.img
the img file is from the new firmware i have downloaded
Myn 2 stuck at asus logo ,,whats showing in ur device manager
myn is MTP USB DEVICE
got any solution
Try this : https://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
my tablet (asus me170c) was hard bricked for a long time and only usb logo showed up. using this amazing guide and using xftk tools I managed to make droidboot available but I can't boot into recovery or system. fastboot detects the device but adb doesn't. I read all similar xda treaths and downloaded about 5 or 6 roms (including raw rom) and started trying the following(but none worked:crying: ):
1-first i tried to boot into recovery and flash latest rom but sadly the tablet won't boot into recovey and SD update is not available in droidboot.
2-then i downloaded ASUS flash tool to flash raw rom but even though all drivers are installed and i can see my tablet in device manager phone flash tool doesn't detect the device :crying:
3-since there is no custom recovery for this specific model, i tried flashing me176cx unofficial twrp by fastboot: fastboot flash recovery twrp.img but it didn't flash recovey with sign_key ROS error (but boot.img and fastboot.img were flashed successfully. and i also tried flashing the raw frameware's system.img with fastboot and it was flashed successfully but nothing changed and the device is still stuck on intel logo.
4-as my last chance, I tried booting into temporary tethered twrp and it booted! but the touch screen didn't work. then I booted temporary cwm but it can't flash any of frameware zip files on external sd card even though it detects them! with erorr closed:0. and It can't load internal storage. there was also an adb sideload option in cwm and after enabling it adb finally detected device but adb sideload zip file failded with the same closed:0 error
5-I also tried Intel flash tool and it detects the device but says the firmware xml file is invalid both stock rom and raw rom have the same error.
I thought making it into fastboot will make reviving my tablet easy but it didn't.
please help, I don't know what else to do i need this tablet for reading books.
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
Try to install twrp 3.2.1.0.
delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
Try to roll back twrp 3.2.1.0-0. I couldn't install any rom with last twrp. Everything is fine until I used twrp 3.2.1.0-0.
delimavi said:
I think my zuk z2 pro is (half) bricked. It was working fine with prevous aex rom but I thought it was time to update rom.
I have copied the rom to phone and started in twrp recovery to install aosp rom and got error 7.
I have tried to get in fastboot to update twrp 3.4.0-0 and wiped data, cache, dalvik etc. Then I got the same error 7 and vendor message in twrp when I try install aosp rom.
Qfil not worked for me. Download fail: Switch To EDL FailFAiled to Swit to Emergency Download mode.
With adb I get now error: device '(null)' not found.
What can I do now after tried different steps. I don't know which is the best step and how to unbrick?
-install another twrp?
-How to transfer and install rom now, by recovery, adb/fasboot, qfil?
-Need stock firmware or doesn't matter?
My phone is rooted.
I appreciate any tips and help.
Click to expand...
Click to collapse
I replied to your double-post already in the other thread:
tiggerle666 said:
As far as I understand, you still can access fastboot mode on startup and flash new versions of twrp?
I just had a bricked phone again, it took me many hours to find out, what went wrong:
The main problem is that when you connect the phone with USB, it shows up as COM 900 and not as COM 9008.
In my case, I the different button combinations didn't work to change that mode (but sometimes it is possible look for an older post of me). If this doesn't help, you need to use a deepflash-usb cable (basically you remove the isolation of the green and black wire and hold them together) while plugging in and simulatously press power + vol down. Then your phone will switch to 9008. Now you should be able to use QFIL. In my case the installation of QFIL was broken and I just had to reinstall it (before, it always had many error messages). And you have to start the download process in QFIL very quick after you connected your phone in 9008 mode.
You don't need adb at this stage, the command "fastbood -i 0x2b4c flash recovery twrp_xyz.img" would just be enough to flash your twrp.
Hope this helps, just reply if you need anything and I'll try to help!
Click to expand...
Click to collapse
G'day folks,
I've been reading through the forums the past several days to fix an issue I have with my Moto G7 Plus.
I have successfully unlocked bootloader, have had various Roms installed and have also had OrangeFox Recovery.
What I forgot to do was flash 'copy-partions' before installing Roms. Have flashed this file now, but i think this is too late.
Current working OS: LineageOS 18.1
Recovery: Lineage 18.1
All I am needing to do is change to TWRP recovery and install Magisk. However, I am unable to flash BL or recovery. The process just hangs with 'sending.....' [twrp-xxxx.lake.img]
I have tried using 'Rescue and Smart Assistant' which successfully downloads the match firmware 'LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT-regulatory_XT195-3_JANZ-CFC.xml.zip'
however fails and throws and error: Fastboot Flash Single Partition.
I have tried using the 'Latest ADB Launcher' and trying various commands. It seems that the A/B partitioning system is not properly working.
When I load into Lineage Recovery it reports that Slot A is active.
Just to reiterate, the phone is booting into LinageOS 18.1, everything seems to be working, just not able to flash TWRP so i can then root the phone with Magisk.
Your help will be appreciated.
Thank you.
I had a similar issue when trying to flash using fastboot on a machine with USB 3 ports, I had to find a old machine with USB2.
Then on the USB2 machine I couldn't boot recovery after flashing the linageos recovery or twrp recovery, but I was able to boot twrp using 'fastboot boot twrp-3.5.2_9-0-lake.img' and then I was able to sideload from there.
MozzerW said:
I had a similar issue when trying to flash using fastboot on a machine with USB 3 ports, I had to find a old machine with USB2.
Then on the USB2 machine I couldn't boot recovery after flashing the linageos recovery or twrp recovery, but I was able to boot twrp using 'fastboot boot twrp-3.5.2_9-0-lake.img' and then I was able to sideload from there.
Click to expand...
Click to collapse
Hi, I've tried USB 2 ports, still yield same result.
Phone screen while in BL mode
'Flashing_unlocked'
Transfer Mode: USB Connected
Have tried multiple twrp.*.img files, but still no success.
I think there is an issue with Slot A/B because I didn't flash the copy-partitions.zip.
From all the posts I have read, people have bricked their phone and recovered it using various methods, but my phone is not bricked, just will not allow flashing of BL and Recovery. It is messed up.
Thank you.
I'm having the same issue. Can't load any TRWP image and I DID flash the copy partition.
WhiskyDrink said:
I'm having the same issue. Can't load any TRWP image and I DID flash the copy partition.
Click to expand...
Click to collapse
Just solved it by grabbing a USB hub.
SOLUTION: connect the phone using a USB hub
I try like @WhiskyDrink said :
When plugin the G7 Plus, MTP and ADB working, but fastboot “Sending 'boot.img'” dont worked at all...
The HUB worked for me
Regards