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
Related
Hi.
I was trying to flash LiquidSmooth ROM, installed TWRP recovery, formatted /data and /cache to F2FS and installed the rom, an custom kernel by mourta and PA Gapps.
The phone stucked in LiquidSmooth bootlogo. I tried to boot in recovery unsuccessfully (my Vol - key is kinda broken), the command adb reboot recovery didn't work.
After many tries, I could flash the LG Stock rom, the Kdz program didn't finish the process and the phone rebooted, don't know why.
Tried many other times to flash.
To sum up, I could flash the original firmware, the phone is booting up normally and aparently is working properly, the problem is: I still can't go to recovery to restore my old rom. (The adb reboot recovery comand just reboot the phone). So, I can't root it or flash another custom recovery.
I wish you guys can help me. Sorry if I written something wrong or if the text is too long, I haven't finished my English course yet.
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
ViniLima said:
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
Click to expand...
Click to collapse
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
ssgabriel said:
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
Click to expand...
Click to collapse
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
ViniLima said:
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
Click to expand...
Click to collapse
I figued out about the error: "Error: more than one device and emulator."
It's an incompatibility with Bluestacks, after close it, it works, but I had to turn off the phone and couldn't flash.
And about fastboot, I could acess this too (Didn't knew that I needed to be on Bootloader mode). But I can't flash the recovery, it says that my bootloader is locked (using fastboot reboot bootloader).
It isn't, or at least wasn't before it all happen. Using ADB command to reboot in bootloader mode (adb reboot oem-unlock I guess), I can flash the .img of clockwork mod and TWRP without error messages, but I still can't boot into it by adb reboot recovery.
Thanks for trying. Today I could acess Android original recovery by hardware keys and install another recovery and ROM.
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
teamwin recovery coming but its getting hang i tried the touch & switch not working.
im unable go back to my stock either to install gapps what should do
please help .........
device xepria sp
CJCHERO said:
teamwin recovery coming but its getting hang i tried the touch & switch not working.
im unable go back to my stock either to install gapps what should do
please help .........
device xepria sp
Click to expand...
Click to collapse
You get an error when installing app from playstore?
And about recovery,
Get "twrp-3.0.2-rXX-fota-huashan.zip" from here.
Extract it,
Flash the .img via fastboot mode,
Reboot your device, it'll boot directly into TWRP.
Flash the "twrp-3.0.2-rXX-fota-huashan.zip" again from there, this will install TWRP in the FOTA partition.
Then flash another ROM/ Restore any backup.
Zenith said:
You get an error when installing app from playstore?
And about recovery,
Get "twrp-3.0.2-rXX-fota-huashan.zip" from here.
Extract it,
Flash the .img via fastboot mode,
Reboot your device, it'll boot directly into TWRP.
Flash the "twrp-3.0.2-rXX-fota-huashan.zip" again from there, this will install TWRP in the FOTA partition.
Then flash another ROM/ Restore any backup.
Click to expand...
Click to collapse
Bro
I flashed cm 13 but when boots into recovery Twrp comes It gets stuck no touch n switch working.
Is a problem with cm 13 nighty .
I would really appreciate a very detailed story. Even if it is a tiny part of it which people often omit..
A detailed story may actually help others to analyse your current situation better Myself included
I was on MUI9 Nougat 7.1.2. Unlocked my bootloader properly. Wanted to try out Google Camera. So I searched the forum, found TWRP 3.0.3 Installer. Installed the TWRP successfully. Then I thought of installing the new TWRP, so flashed TWRP 3.2.1 from the previous TWRP. When I booted back to Recovery, saw the Encryption Error. I never set any password. Got tensed. Searched the forums again for solution. Found that I have to format the data. So formatted the data, flashed LazyFlasher. Did not know what else to do, tried booting and got stuck in Bootloop. I only have Internal Storage. And have one OTG Pendrive in case it comes handy. Downloaded Dot OS 7.1.2 and tried to install it from the OTG by booting back to TWRP, failed, it said Corrupt ZIP, but the zip file was ok. So started the process again, rebooted back to TWRP, wiped everything and this time tried to flash an old MIUI9 Recovery ROM through it, it still gave the same error, Corrupt ZIP. So basically what I have left is that I can boot into TWRP and also Fastboot is working well. But dont know how to get past this Bootloop. Someone please help. Really urgent. So tensed. :crying:
do you flash miui rom in twrp or miflash? try to flash the miui rom with miflash and see if ur phone booted up or not.
Deleted
Deleted
Thanks bro. Never mind. Somehow managed to flash DotOS Nougat version through TWRP 3.0.3. Now bro please tell me one thing. I wont stay at DotOS, I dont like it, just flashed it to get through the bootloop. So now I have downloaded MIUI9 8.3.22 Developer Recovery ROM. Still having TWRP 3.0.3, BL Unlocked, ADB working, Fastboot working, USB Debugging everything taken care off. Just tell me steps to flash the Developer ROM now so that I dont go into bootloop again. Please. Thanks in advance.
ummm kinda easy actually, download the miflash software, open it, it should have the select, refresh, and flash menu. click select, and navigate to your rom file (u need to download the fastboot rom version! not the recovery version, should be easy to find in google. the format should be .tgz change it to rar, extract it, it will shows another rar extract it again, it should be folder now) that folder is your rom file. now enter fastboot mode, plug ur phone, and click refresh. it will shows some number and alphabet. if the number and alphabet appears, click flash! and wait! and ur phone will boot itself
sorry for **** english
1. Go to twrp...
2. Wipe (cache, data, dalvik/cache, system)
3. flash miui 9 dev 8.3.22
4. flash lazyflasher...
Reboot..
It will take more then 5 min to start (first boot usually take that much time)
Your phone boot normally....
If you are facing TWRP Recovery Issue then update TWRP
Link :- https://drive.google.com/drive/folders/17YW09XpEHq7xgBAriwA-mgtEG0pckop2?usp=sharing
V3.2.1-5 is latest one...
Hit thanks
From my Redmi 4X using Tapatalk VIP
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