I recently acquired an lg v35 ThinQ that seems to be stuck on the fastboot loader, it only says reboot and shutdown and reboots to the fastboot recovery but wont boot up. Help!
I would recommend backing up and erasing laf_a and laf_b. Then restoring the original boot_a, boot_b, abl_a, and abl_b and starting over. If you need any of these files for the ULM version, I have them.
Error-404-Go-Home said:
I would recommend backing up and erasing laf_a and laf_b. Then restoring the original boot_a, boot_b, abl_a, and abl_b and starting over. If you need any of these files for the ULM version, I have them.
Click to expand...
Click to collapse
If you have them they would be of great help since i did not do this in the first place, just trying to fix it
I extracted these from the V350ULM10i_00_NAO_US_OP_0221.kdz using these scripts: https://github.com/ehem/kdztools
These files are for Oreo V350ULM only, they will not work with the V350AWM image (I have tried)
This method has worked for me in the past. Just flash these to their respective partitions with QFIL and it should work again (without root, of course... that requires you to modify boot_a and boot_b). If you need any more images (system_a, system_b...) from this kdz or others feel free to ask.
https://drive.google.com/drive/folders/11kWqa7k1MBSCDwP_ThN9VOT8CbsDVra0?usp=sharing
Error-404-Go-Home said:
I extracted these from the V350ULM10i_00_NAO_US_OP_0221.kdz using these scripts: https://github.com/ehem/kdztools
These files are for Oreo V350ULM only, they will not work with the V350AWM image (I have tried)
This method has worked for me in the past. Just flash these to their respective partitions with QFIL and it should work again (without root, of course... that requires you to modify boot_a and boot_b). If you need any more images (system_a, system_b...) from this kdz or others feel free to ask.
https://drive.google.com/drive/folders/11kWqa7k1MBSCDwP_ThN9VOT8CbsDVra0?usp=sharing
Click to expand...
Click to collapse
Qfil does not recognize any usb device
TheLaptopBros12 said:
Qfil does not recognize any usb device
Click to expand...
Click to collapse
the lg v35 only shows the fastboot screen
You should still be able to put it in 9008 mode by holding power + volume down + rapidly pressing volume up while plugged into a pc
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
You can open up QFIL and try over and over again until it shows up as QUALCOM USB... instead of "no port"
Error-404-Go-Home said:
You should still be able to put it in 9008 mode by holding power + volume down + rapidly pressing volume up while plugged into a pc
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
You can open up QFIL and try over and over again until it shows up as QUALCOM USB... instead of "no port"
Click to expand...
Click to collapse
I cant seem to do it.
Can't get it into 9008 mode or open QFIL?
Error-404-Go-Home said:
Can't get it into 9008 mode or open QFIL?
Click to expand...
Click to collapse
QFIL works but 9008 does not. it only gets to the fastboot menu.
You can also install ADB and use "fastboot flash abl_a path/to/abl_a.image" to flash it in fastboot mode. That only works if your bootloader is unlocked though.
Error-404-Go-Home said:
You can also install ADB and use "fastboot flash abl_a path/to/abl_a.image" to flash it in fastboot mode. That only works if your bootloader is unlocked though.
Click to expand...
Click to collapse
i dont think it is. i also tried download mode, does not work.
If you have not executed fastboot oem unlock in fastboot mode I would recommend trying it and flashing the files previously mentioned. If oem-unlock does not work, I would recommend to continue trying to get it into 9008 mode. I have previously been stuck in fastboot mode as well and I just held power and volume down, where it instantly turned off, (because fastboot mode had power off selected) then, as I kept holding the power and the volume down buttons it rebooted and I started rapidly spamming the volume up button (while still holding power and volume down). That got it into 9008 mode, I would recommend similar steps, or just try holding power and volume down while rapidly spamming volume up until it works.
---------- Post added at 08:39 PM ---------- Previous post was at 08:33 PM ----------
You can also try "fastboot flashing unlock" instead of "fastboot oem unlock"
Im In, how do i set the files in QFIL? Never done before
into 9008 mode and qfil Works and detects
I recommend reading over the
"Step 2: Partition Extraction, Modification and Bootloader Unlock"
section of this great guide
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
but the gist is
Set the "emmc" in the bottom right to "ufs"
then select "Flat build" and select the "firehose" file as a programmer (that can be downloaded from the guide)
and open up partition manager under tools in the upper left of QFIL
once you have the partition manager open, you can select a partition (ex. abl_a), click manage partiton, then click load image. Then load the respective image file.
Do that for laf_a, laf_b, abl_a, abl_b, boot_a, and boot_b
Then exit out of the partiton manager, reboot the device, and it should work
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Note: I have noticed that if you are in 9008 mode for too long, then it will error when you try to open the partiton manager saying Sahara mode FAILED or something like that. This just means that you have to hold volume down and power until it reboots and get it back into 9008 mode like before, then try to open the partition manager quicker.
Error-404-Go-Home said:
I recommend reading over the
"Step 2: Partition Extraction, Modification and Bootloader Unlock"
section of this great guide
https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
but the gist is
Set the "emmc" in the bottom right to "ufs"
then select "Flat build" and select the "firehose" file as a programmer (that can be downloaded from the guide)
and open up partition manager under tools in the upper left of QFIL
once you have the partition manager open, you can select a partition (ex. abl_a), click manage partiton, then click load image. Then load the respective image file.
Do that for laf_a, laf_b, abl_a, abl_b, boot_a, and boot_b
Then exit out of the partiton manager, reboot the device, and it should work
---------- Post added at 08:58 PM ---------- Previous post was at 08:54 PM ----------
Note: I have noticed that if you are in 9008 mode for too long, then it will error when you try to open the partiton manager saying Sahara mode FAILED or something like that. This just means that you have to hold volume down and power until it reboots and get it back into 9008 mode like before, then try to open the partition manager quicker.
Click to expand...
Click to collapse
I can't reboot, stuck in 9008 mode
Hold power and volume down to reboot
Error-404-Go-Home said:
Hold power and volume down to reboot
Click to expand...
Click to collapse
I got it.
problem though, now to says it is not secure and onlly boots to fastboot but before that it shows the link g.co/ABH
TheLaptopBros12 said:
I got it.
problem though, now to says it is not secure and onlly boots to fastboot but before that it shows the link g.co/ABH
Click to expand...
Click to collapse
and now back at square 1, now again
like this guy https://forum.xda-developers.com/lg-v35/how-to/v35-bricked-sad-t3960057
you likely did not have the right version of android for the files I gave you. There isn't much of a way to tell I guess.
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
Can you get into download mode? Try turning the phone off via fastboot mode (use volume keys to select the "Power Off" option) then hold volume down while plugging it into a computer. If that doesnt work try again holding volume up. If this gets you into download mode, then you might be able to flash the whole kdz with LGUP.
Related
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-28311_475.5300.zip
Disclosure:
Flash at own risk, not officially released.
You do not need root or anything else. This will work if you're bone stock.
The easiest way accomplish this is with an SD Card.
Once you have downloaded the OTA, copy it to your SD Card.
Power off device
Boot in Bootloader:
While device is off HOLD Vol-Down and TAP the Power Button once (do not hold the power button). Let go of Vol-Down once you see logo.
Boot into Recovery
Once in Bootloader use the Volume buttons to navigate to Recovery Mode, use Power button to select.
You will then see an Android with an ! and says no command. IGNORE THIS.
Push Vol-UP and then Power.
You will access the Recovery Menu.
Select Apply Update from SD Card.
Find your .zip and select.
It will apply update and will say finished at the bottom of the screen.
Now select Reboot System.
Wait till it boots.
Depending on your setup it can take anywhere from 2min to 30min. Be patient.
Now you have your update. Enjoy
Click to expand...
Click to collapse
If you want to do an "adb sideload"
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
If you get an error while trying update, verify your .zip file is the right size.
If for some reason you completely crap your device follow this link and scroll down to Recovery images.
https://developer.nvidia.com/develop4shield
Click to expand...
Click to collapse
timskyline86 said:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-28311_475.5300.zip
Disclosure:
Flash at own risk, not officially released.
Click to expand...
Click to collapse
Updated my US LTE version with this file and everything seems to be just fine. just beware that after flashing the Nvidia logo will remain on the screen for 3-5 minutes before finalizing the upgrade script. I must admit I did sweat a little...
Carlos
Chaleman said:
Updated my US LTE version with this file and everything seems to be just fine. just beware that after flashing the Nvidia logo will remain on the screen for 3-5 minutes before finalizing the upgrade script. I must admit I did sweat a little...
Carlos
Click to expand...
Click to collapse
HOW did you flash it?
Prfndhatrdofman said:
HOW did you flash it?
Click to expand...
Click to collapse
I put the zip in mysdcard and boot to recovery. I flashed it from there. I had previously installed CWM on my tablet....
Carlos
For stock
ADB sideload. Or SD Card
Power off device.
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
If you do it through the computer its:
Adb devices
adb sideload filename.zip
Reboot
Done just like the Nexus devices.
Flashed via PhilZ, worked like a charm.
timskyline86 said:
For stock
ADB sideload. Or SD Card
Power off device.
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
If you do it through the computer its:
Adb devices
adb sideload filename.zip
Reboot
Done just like the Nexus devices.
Click to expand...
Click to collapse
I can't believe is that easy, I'm super happy and I will be testing it once I load it in to the SM Card.
---------- Post added at 12:40 PM ---------- Previous post was at 12:29 PM ----------
I found the following information on the Nvidia developer site :
(https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt)
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
---------- Post added at 12:46 PM ---------- Previous post was at 12:40 PM ----------
timskyline86 said:
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
Click to expand...
Click to collapse
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
an0m13 said:
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
Click to expand...
Click to collapse
Steps that worked for me:
Shut down
Wait 20 seconds after shut down
Hold Vol Down
Press power button (don't hold)
an0m13 said:
I can't believe is that easy, I'm super happy and I will be testing it once I load it in to the SM Card.
---------- Post added at 12:40 PM ---------- Previous post was at 12:29 PM ----------
I found the following information on the Nvidia developer site :
(https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt)
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
---------- Post added at 12:46 PM ---------- Previous post was at 12:40 PM ----------
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
Click to expand...
Click to collapse
When the device is off, start by holding the volume down button. While holding the volume down button, just press the power button once. Keep holding volume down until you get into fastboot mode, then you can let go and do your thing.
Thanks, all it needed was a tiny tap on the power button ( I was just holding until I saw the logo)
---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------
I got in to the bootloader and then I select "Recovery mode" and all I get is a "No command" message with the android with the red exclamation sign.
an0m13 said:
Thanks, all it needed was a tiny tap on the power button ( I was just holding until I saw the logo)
---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------
I got in to the bootloader and then I select "Recovery mode" and all I get is a "No command" message with the android with the red exclamation sign.
Click to expand...
Click to collapse
Sounds like the stock recovery. Someone on GeForce forums is reporting that you can use flashify with the stock recovery, though!
From the No Command screen hold Power + Up Volume. You should see the recovery options.
My SDCard would not mount, so I had to ADB Sideload the file. After a long reboot things seem to be working just fine.
Bit of a noob question, but how do i know if my shield tab is a US LTE or EU LTE???
theRealBra_Zee said:
Bit of a noob question, but how do i know if my shield tab is a US LTE or EU LTE???
Click to expand...
Click to collapse
It's based on where you live most likely
US=America
EU=Everywhere Else
SuperPichu said:
It's based on where you live most likely
US=America
EU=Everywhere Else
Click to expand...
Click to collapse
I'm in Ghana(Africa), got the tab from an aunt in the US, so i'm guessing it's US LTE. Came with an AT&T sim card and everything
theRealBra_Zee said:
I'm in Ghana(Africa), got the tab from an aunt in the US, so i'm guessing it's US LTE. Came with an AT&T sim card and everything
Click to expand...
Click to collapse
Yeah that is probably the US one then.
khart1978 said:
From the No Command screen hold Power + Up Volume. You should see the recovery options.
My SDCard would not mount, so I had to ADB Sideload the file. After a long reboot things seem to be working just fine.
Click to expand...
Click to collapse
Did you use stock recovery?
Sideloaded about an hour ago and everything seems fine with my TMO service.
Those of you who're in the US and have flashed your LTE unit and who use T-mobile, can you give us any impressions of the alleged "fix" nvidia did for T-mobile LTE signals/coverage? Better? Worse? No difference?
I'm really struggling to decide whether or not I should wait or go ahead and install this "EU" rooted version instead. The only thing I am interested in is better T-Mobile LTE coverage. On KitKat, the LTE T-mobile signal is either non-existent or abysmal at best.
isamu99 said:
Those of you who're in the US and have flashed your LTE unit and who use T-mobile, can you give us any impressions of the alleged "fix" nvidia did for T-mobile LTE signals/coverage? Better? Worse? No difference?
I'm really struggling to decide whether or not I should wait or go ahead and install this "EU" rooted version instead. The only thing I am interested in is better T-Mobile LTE coverage. On KitKat, the LTE T-mobile signal is either non-existent or abysmal at best.
Click to expand...
Click to collapse
I'm not getting much difference in behavior.
Zuk Z1 not boots after update Cyanogen 13 nightly to snap
I downloaded Cyanogen 13 snap version moved to cm update folder. And from developer menu i activated flash recovery during update. but usb debugging was off. From update menu i clicked snap and install. Now phone not boots. Tried Volume - & Power, Volume + & Power none of them not works. Phone screen blinks every 3 secound.
C:\WINDOWS\system32>adb devices
List of devices attached
24cc9ceb unauthorized
C:\WINDOWS\system32>adb reboot bootloader
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
What can i do ?
you cant't upgrade from nightly to snap it was write in the release note you have to wipe and after flash the snap
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
you can try to delete adbkey file in C:Users/$Name/.android if adbkey.pub is missing.
and restart they should appear
tomdan95 said:
you cant't upgrade from nightly to snap it was write in the release note you have to wipe and after flash the snap
---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------
you can try to delete adbkey file in C:Users/$Name/.android if adbkey.pub is missing.
and restart they should appear
Click to expand...
Click to collapse
Phone not boots... deleting adbkey will not help
yes, it dosn't boot because there nothings to boot. upgreading from nightly to snap you have corupt system and recovery partition, you have to turn off your zuck and turn it on putting it in fastboot mode; wipe recovery partition and flash twrp, after that start the recovery twrp and from twrp wipe system and data partition and flash the snap zip in the system partition and reboot
---------- Post added at 03:11 PM ---------- Previous post was at 03:07 PM ----------
you can try to press volume + & volume - for force the fastboot mode
---------- Post added at 03:18 PM ---------- Previous post was at 03:11 PM ----------
if it dosen't work try to turned it off and keep the data cable to the computer disconnect, press: [volume down key] [Power Key] waiting to enter the fastboot mode.
---------- Post added at 03:41 PM ---------- Previous post was at 03:18 PM ----------
if all this things dosen't work last chance is install ZUI on your phone and when you have a working zui install COS or CM
for do that you have to:
0. Download the ZUI Full ROM file from here and extract to your computer. Here is the link https://mega.nz/#!fYYh0QDA!nYf0vvXpz...__vaHO_Weyg-YU
1. You need to install Qualcomm driver and ZUK Z1 driver to you PC, you can download it from this link https://mega.nz/#F!LcgDmRyC!4unf8UQqOBoZayAuv-D3Tg
2. The Qualcomm driver file shouldn't be signed so most of the windows operating system will not allow you to install, to install the Qualcomm driver you need to enable the unsigned driver installation.
If you are using windows 10 or windows 8. or 8.1 you can enable in this way. (go to the power option from the start menu hold the shift key from the keyboard and select restart option) for more information you can see this link http://www.howtogeek.com/167723/how-...igned-drivers/
If you are using windows 7 you can disable the driver signature verification from the boot menu. (when you see your computer motherboard name or pc logo just type F8 so there you can choose the option disable driver verification)
3. If you install the driver files successfully then you need to download and install the QFIL tool you can download the file from this link https://mega.nz/#!qIx0ybKC!YfeWZMHTF...8rEqDr5rEOYUc4
4.start QFIL from the QPST folder
5.Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
6. When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
7.If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
I came esta upgrade and had previously rooted and will not let me install I put the official says recovery not fail me
cm13.1 -znh2kas254 incremental
why dont you manually flash (recovery?) or update over fastboot
bobthecooldad said:
why dont you manually flash (recovery?) or update over fastboot
Click to expand...
Click to collapse
how do you update over fastboot ?? don't we need stock recovery for that ?
no, you need to first install (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118)
Now turn off your phone and hold volume up at the same time you press the power button (with the usb cable in)
To check if the device is detected, run cmd and run "fastboot", lots of text should appear if nothing does reinstall or reboot. To check for devices do "fastboot devices"
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
this is for recovery
fastboot flash recovery recovery.img
(recovery needs to be in your username drive (Windows 7-10 for example for me it is C:\users\gaming)
(credit to http://forum.xda-developers.com/showthread.php?t=2131284 for information)
Hey guys... Well I was one of the flashaholics who went ahead and tried to flash some custom roms and ended up bricking my phone which was completely bricked (NOT even FASTBOOT!) and after loads of googling I was able to get my phone working again.
WARNING
Your device is already bricked and if it goes worse than I am not responsible for it. Do at your own risk.
Requirements:
1. Windows PC with driver signature disabled.
(i). Press and hold the Shift key on your keyboard and click the Restart button.
(ii). Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
(iii). When your computer restarts you’ll see a list of options. Press F7 (the number may change on your pc) on your keyboard to select Disable driver signature enforcement.
(iv).Your computer will now restart and you’ll be able to install unsigned drivers.
2. Drivers
(i). ZUK USB driver
(ii). Qualcomm_QHSUSB_driver
(iii). ADB & Fastboot drivers
(iv). QPST
3. QPST Rom
(i). INDIAN ROM
STEPS:
1. Install the ZUK USB driver downloaded from above.
2. Install qpst downloaded from above.
FOLLOW THE ON SCREEN INSTRUCTIONS. IF IT ASK TO DOWNLOAD C++ REDISTRIBUTABLE THAN DO IT.
3. Extract the ROM on the root of the C drive.
4. Restart your PC and open QFILClick
(i) Select "Flat Build" and "Browse". Now navigate to the extracted ROM/Firmware, and select prog_emmc_firehose_8996_ddr.elf.
(ii) Select the "load xml" button. This will appear a new explorer. One of them will be needed to navigate to the file rawprogram-flash0.xml the second one will ask for patch0.xml .
(iii) Turn your phone off. Now press and hold the volume + button, while pressing the power button for 0.5 seconds and plug in the USB cable in the same moment. If it was successful your phone should appear at QPST/QFIL and you are able to press the download button. Press the download process and wait to finish.
if it fails, In QFIL Change
"Device Type" to eMMC
"Validation Mode" to 0-No validation
"Reset after Download" no needed to tick (optional)
If your phone is not detected in the QFIL then,
Close QFIL
Right click on my computer and select MANAGE, then select Device Manager
See if your device is connected as Diagnostic Port 900E
If it is shown as “QHSUSB_BULK” under Other Device
1. Right-click on QHSUSB_BULK and choose “Update Driver Software“
2. Now click on the Browse button and locate the extracted Qualcomm QDLoader drivers.
3. The installation process shall take place immediately and a system notification will appear. Just choose “Install this driver software anyway“.
4.Click the Close button and check back at Device Manager window. You will now see “Qualcomm HS-USB QDLoader 9008 (COM10)” under Ports (COM & LPT) section.
Now start QFIL and press download.
DONE!!
REFERENCES: https://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
DON'T QUOTE THE WHOLE OP
will this guide work with QPST 2.7.496?
I want to revert to stock zui
i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report
in the port its showing 900E inead of 9008 what should i do?
Dragonlord07 said:
its showing 900E
Click to expand...
Click to collapse
Try this thread: https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
device isn't showing up in device manager...what should I do?
first of all, thank you for the clear guide since the one on zukfans,eu was taken down. I am recieving an error :
Download Fail:Saha Fail:QSaharaServer Failrocess fail
the two discrepancies from the guide are that my phone shows up as (COM3) and not (COM10), and the rawprogram file is rawprogram0.xml
any help or guidance would be appreciated
edit: nvrmind, i just kept trying plugging in during the power button + volume down button boot and it finally let me download without error
locolyric said:
i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report
Click to expand...
Click to collapse
the issue is with me, did find a solution for this
---------- Post added at 07:18 AM ---------- Previous post was at 07:06 AM ----------
it says failed to load edl
what to do
---------- Post added at 07:36 AM ---------- Previous post was at 07:18 AM ----------
locolyric said:
i just successfully hard bricked my phone. i flash 2.5 rom with baseband from 2.3.042 . now i can only see the boot up zuk logo and screen turn black with notification lights on.
unable to switch it off at all.
come back later and report
Click to expand...
Click to collapse
bro i have solved it
steps i have followed
1)press volume up+volume down+power for 30 seconds (phone will show zuk logo and switches off, donot bother about that)
2)now remove the finger from power button(keep holding volume up and power buttons)
3)there u go u will see the fastboot mode
******* I have followed those steps and my phone got booted**********
error is because of locked bootloader
i have unlocked it again and using stock rom now
Dead
A make all point ... with success, but ... After Qfil end works, my zuk don't want switch on. PC doesn't see it. Please help
help me
sairam96 said:
the issue is with me, did find a solution for this
---------- Post added at 07:18 AM ---------- Previous post was at 07:06 AM ----------
it says failed to load edl
what to do
---------- Post added at 07:36 AM ---------- Previous post was at 07:18 AM ----------
bro i have solved it
steps i have followed
1)press volume up+volume down+power for 30 seconds (phone will show zuk logo and switches off, donot bother about that)
2)now remove the finger from power button(keep holding volume up and power buttons)
3)there u go u will see the fastboot mode
******* I have followed those steps and my phone got booted**********
error is because of locked bootloader
i have unlocked it again and using stock rom now
Click to expand...
Click to collapse
same here.i was on custom rom and insatlled zui2 2.0 and my phone isnt starting. only zuk symbol coes and goes.
I'm having trouble, my zuk z2 is stuck with relocked bootloader and custom recovery
I can boot to fastboot mode, reboot in EDL mode and I've had many tries to flash a new stock ROM but none progress so far
And I get Firehose errors when trying to flash a QFIL stock rom
It means my phone is hard bricked but is there any solution to that or I'm bound to buy another cellphone ?
BTW my sister has the same phone as me, is there any way I can use her phone as a backup ?
Much appreciated for the tips and help
fraucred said:
I'm having trouble, my zuk z2 is stuck with relocked bootloader and custom recovery
I can boot to fastboot mode, reboot in EDL mode and I've had many tries to flash a new stock ROM but none progress so far
And I get Firehose errors when trying to flash a QFIL stock rom
It means my phone is hard bricked but is there any solution to that or I'm bound to buy another cellphone ?
BTW my sister has the same phone as me, is there any way I can use her phone as a backup ?
Much appreciated for the tips and help
Click to expand...
Click to collapse
U must have to unlock bootloader
Then install twrp recovery
Now connect the phone to the computer
Now send any of the custom roms to phone
Now flash the custom rom
Boot into it
Then u can goto stock rom by rrbooting into edl
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
NISHUHACKER said:
same here.i was on custom rom and insatlled zui2 2.0 and my phone isnt starting. only zuk symbol coes and goes.
Click to expand...
Click to collapse
Boot into recovery n flash other custom roms n after booting u can goto stock rom , if u dont know how to just msg here
How should I proceed to unlock the bootloader once again ? I tried the fastboot mode but I've seen failures until now
I had bricked my phone when I still had access to TWRP recovery, probably with a stock - modded rom (the indian one I believe) and after that everything went down.
Thought locking the bootloader would allow me to get back to another stock rom but now I can only get to the phone through fastboot mode or 9008 COM port
sairam96 said:
U must have to unlock bootloader
Then install twrp recovery
Now connect the phone to the computer
Now send any of the custom roms to phone
Now flash the custom rom
Boot into it
Then u can goto stock rom by rrbooting into edl
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Boot into recovery n flash other custom roms n after booting u can goto stock rom , if u dont know how to just msg here
Click to expand...
Click to collapse
fraucred said:
How should I proceed to unlock the bootloader once again ? I tried the fastboot mode but I've seen failures until now
I had bricked my phone when I still had access to TWRP recovery, probably with a stock - modded rom (the indian one I believe) and after that everything went down.
Thought locking the bootloader would allow me to get back to another stock rom but now I can only get to the phone through fastboot mode or 9008 COM port
Click to expand...
Click to collapse
Downlad bootunlock.img from zuk official site
Then download minimal adb drivers
Move the download img file to minimal adb directory
Then follow the following commands
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
sairam96 said:
Downlad bootunlock.img from zuk official site
Then download minimal adb drivers
Move the download img file to minimal adb directory
Then follow the following commands
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Which is what I try to do but no success
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is my device bootloader status
PS C:\Users\xxxxx\adb> .\fastboot.exe -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device relocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.065s]
finished. total time: 0.066s
PS C:\Users\xxxxxx\adb>
fraucred said:
Which is what I try to do but no success
Here is my device bootloader status
PS C:\Users\xxxxx\adb> .\fastboot.exe -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device relocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.065s]
finished. total time: 0.066s
PS C:\Users\xxxxxx\adb>
Click to expand...
Click to collapse
Try sideload process
sairam96 said:
Try sideload process
Click to expand...
Click to collapse
How do I do that ?
fraucred said:
How do I do that ?
Click to expand...
Click to collapse
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip
It seems I need to use adb but I have the adb drivers installed, my device in fastboot mode is not listed when I use the "adb devices" command
I cannot access to the USB Debugging option either because my phone is bricked
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
sairam96 said:
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip
Click to expand...
Click to collapse
I don't have access to TWRP either, because I locked my bootloader as I explained earlier
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
sairam96 said:
Go to twrp
Advanced
Adb sideload and connect it to the pc
Now dowload update.zip from zuk development or xda development
And copy the downloaded.zip to adb directory
Now type the command adb sideload update.zip
Click to expand...
Click to collapse
I don't have access to TWRP either, because I locked my bootloader as I explained earlier
I figured it out, installed a chinese stock rom which made my bootloader set to default
After that I unlocked it, installed TWRP and I successfully installed Lineage OS
My Zuk Z2 looks completely different now
my phone was bricked , i flashed zui 2.0 , 2.3 and 2.5 with QFIL but steel bricked so i unlocked my bootloader again and flashed TWRP but i can't even enter recovery mode i got black screen with white LED :crying::crying:
My MiA1 got stuck on Main Menu yesterday. I couldn't power it off or restart as neither the power button nor the volume buttons were responding. After an hour it automatically powered off. When I booted it up again, it was stuck on AndroidOne logo. So I decided to reset my phone. When I booted in recovery mode, there's an error being displayed at the bottom. It says "Failed to clear BCB message: failed to sync /dev/block/bootdevice/by-name/misc: Operation not permitted". Anyway I started resetting the phone but even after 2 hours it was stuck on "Formatting /data...". Next I tried to flash stock rom using MiFlash tool but it takes too long to flash. I have seen videos in which it happens in 200-500 seconds. I ran MiFlash for more than 6000 seconds and then diconnected my phone. I don't understand what is the issue here.
Please note that I have never unlocked bootloader before. Phone was running on the stock rom.
first thing first after reading your post it seems your Nand chip is faulty but i'm not sure.
so MiFlash works only for Unlocked Bootloader.
first try unlocking bootloader with fastboot
then try flashing stock rom
or
you can try QFIL tool from QPST for flashing stock rom.
ranjodhricky said:
first thing first after reading your post it seems your Nand chip is faulty but i'm not sure.
so MiFlash works only for Unlocked Bootloader.
first try unlocking bootloader with fastboot
then try flashing stock rom
or
you can try QFIL tool from QPST for flashing stock rom.
Click to expand...
Click to collapse
I tried to unlock bootloader with fastboot but whenever i use the command "fastboot oem unlock" it reboots my phone. After again booting into fastboot mode, if i check the bootloader unlock status, it shows false. Is there anything I am doing wrong?
i think you haven't enabled oem unlocking in developer settings now i think there is no way to unlock bootloader and without unlocking you cant flash with MiFlash. you can try QFIL for flashing i think it will work with locked bootloader if not then you have to got service center and they will flash it for u
---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------
try flashing in edl mode restart in fastboot then enter
fastboot oem edl
phone screen goes black and led blinks then try flashing
---------- Post added at 08:39 PM ---------- Previous post was at 08:28 PM ----------
if all of the above not working try putting phone into edl mode by testpoint it will work here is the link for the image and tutorial for putting phone into edl with test point
http://gsmclinic.com/redmi-a1-xiaomi-mdi2-edl-pinout-edl-test-point/
after putting into edl flash it with MiFlash or Qfil.
but you have to open the back case of phone.
ranjodhricky said:
i think you haven't enabled oem unlocking in developer settings now i think there is no way to unlock bootloader and without unlocking you cant flash with MiFlash. you can try QFIL for flashing i think it will work with locked bootloader if not then you have to got service center and they will flash it for u
---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------
try flashing in edl mode restart in fastboot then enter
fastboot oem edl
phone screen goes black and led blinks then try flashing
---------- Post added at 08:39 PM ---------- Previous post was at 08:28 PM ----------
if all of the above not working try putting phone into edl mode by testpoint it will work here is the link for the image and tutorial for putting phone into edl with test point
http://gsmclinic.com/redmi-a1-xiaomi-mdi2-edl-pinout-edl-test-point/
after putting into edl flash it with MiFlash or Qfil.
but you have to open the back case of phone.
Click to expand...
Click to collapse
fastboot oem edl is not working. It shows:
OKAY [ 0.068s]
Finished. Total time: 0.073s
But my phone remains in fastboot mode only. I guess service center is the only I have.
you have to wait 10 to 15 second after entering the cmd sometime it takes some time to reboot into edl or you can use test point method it will works for you. i think even guys at service center also use test point to flash the firmware if you can remove the back cover you can try it.
ranjodhricky said:
you have to wait 10 to 15 second after entering the cmd sometime it takes some time to reboot into edl or you can use test point method it will works for you. i think even guys at service center also use test point to flash the firmware if you can remove the back cover you can try it.
Click to expand...
Click to collapse
Thanks for all the help that you have provided :angel:. For now, I have sent my phone to the service center. Lets see if they can work something out.