I don't flash any stock rom since Q3 2016 and now i need newer base to flash latest customs. What is best stock rom that i can flash via QPST? I mean which one is most actually (i know there is oreo but it's hard to find no modded version)
Deep flash cable
I needed to make a deep flash cable. It was impossible to get into EDL. I had installed stock ROM while the drive was encrypted and the new install was installed in it just fine, but the pattern was only a piece you needed to decrypt. The rest was in the OS I wiped. So I had to use the cable to get into edl.
Instead of EDL flash cable use this trick
Connect your phone to your PC in EDL mode:
Youtube Video: v=DexLELi04XY
Title: EDL MODE Lenovo Z2 | Lenovo z2132
(sorry, can't post link)
Related
Hey guys,
so this my problem:
I got the Mix 2 with the Chinese ROM. With the XiaoMiTool by Francesco Tescari I updated to the Global ROM V9.1.2.0 because I didn't want to wait to unlock the bootloader. This worked but I only had the choice to set China as my region. Since this was a common problem with updating the ROM without unlocking the phone I unlocked it and waited for 3 days to unlock.
Today I installed TWRP and installed the ROM xiaomi.eu_multi_MIMix2_7.11.16_v9-7.1. After this I was stuck with the Mi bootup logo. In TWRP I deleted cache, system, data. This worked EXCEPT for system. I thought updating TWRP to the newest version would help solve this issue. But since I'm new to this I didn't update it within TWRP but just installed the newer version via the commandfastboot flash recovery twrp.img. The result is that I can not get in recovery mode anymore. The only option is fastboot mode or the regular Mi logo endless boot.
What I tried so far: EDL flash method via adb/MiFlash but both don't work. The XiaoMiTool won't work too. The Mi PC Suite won't recognise the phone. When I use the edl.cmd the phone will go black for 2-3s and then return to fastboot.
I guess the problem at this point is that usb debugging is not turned on since TWRP installed the EU ROM and I could never get in it to enable the debug mode.
I couldn't find a solution to solve the boot up problem and can't seem to install/flash a new ROM at this point.
So what can I do? Do I need that special usb cable? Will the EDL points help me?
Maybe/Hopefully you can help me out.
EDIT:
When I turn on the phone it will directly go into fastboot mode. A normal start is not possible anymore?!...
EDIT 2:
I am now running the latest Global Rom this guide did it for me: en.miui. com/thread-1351514-1-1. html
Good to hear you got it up and running.
derpaherp said:
Hey guys,
so this my problem:
I got the Mix 2 with the Chinese ROM. With the XiaoMiTool by Francesco Tescari I updated to the Global ROM V9.1.2.0 because I didn't want to wait to unlock the bootloader. This worked but I only had the choice to set China as my region. Since this was a common problem with updating the ROM without unlocking the phone I unlocked it and waited for 3 days to unlock.
Today I installed TWRP and installed the ROM xiaomi.eu_multi_MIMix2_7.11.16_v9-7.1. After this I was stuck with the Mi bootup logo. In TWRP I deleted cache, system, data. This worked EXCEPT for system. I thought updating TWRP to the newest version would help solve this issue. But since I'm new to this I didn't update it within TWRP but just installed the newer version via the commandfastboot flash recovery twrp.img. The result is that I can not get in recovery mode anymore. The only option is fastboot mode or the regular Mi logo endless boot.
What I tried so far: EDL flash method via adb/MiFlash but both don't work. The XiaoMiTool won't work too. The Mi PC Suite won't recognise the phone. When I use the edl.cmd the phone will go black for 2-3s and then return to fastboot.
I guess the problem at this point is that usb debugging is not turned on since TWRP installed the EU ROM and I could never get in it to enable the debug mode.
I couldn't find a solution to solve the boot up problem and can't seem to install/flash a new ROM at this point.
So what can I do? Do I need that special usb cable? Will the EDL points help me?
Maybe/Hopefully you can help me out.
EDIT:
When I turn on the phone it will directly go into fastboot mode. A normal start is not possible anymore?!...
EDIT 2:
I am now running the latest Global Rom this guide did it for me: en.miui. com/thread-1351514-1-1. html
Click to expand...
Click to collapse
hey - how did you get mi unlock to work? im having this problem: mi unlock tool 2.3.803.10. it won't show the mi mix 2 as connected with xiaomi drivers, only with google drivers it will show as connected and then let me click unlock. however, it stops at 50% and shows error "couldnt verify device unkown error (-1)". ive logged on to i.mi.com and located the device through find device. does anyone have any pointers how i can unlock, because i want to switch to global dev rom and miui updater wont let me update through system with error "android version is different".
best, alastair
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Solution
Chin_hebbar said:
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Click to expand...
Click to collapse
I've used MiFlash Tool, and the problem was fixed. Sahara Error occurs when you take to much time to flash after booting to EDL, you only have few seconds to flash util the port is closed for writing. QFIL takes around 20 to 25 seconds in caching the files so use MiFlash and It'll flash. Best way to do it is:
1. Install and setup MiFlash for flashing.
2. Open MiFlash and select your Firmware's folder.
3. As soon as you connect the phone refresh miflash and hit flash.
If everything goes well you'll flash will be successful else try again.
I tried doing as fast as a could too on mi flash and it would come up as trying to connect to com4 port something in the status and would eventually come back to same error in the picture.
Chin_hebbar said:
I tried doing as fast as a could too on mi flash and it would come up as trying to connect to com4 port something in the status and would eventually come back to same error in the picture.
Click to expand...
Click to collapse
I need to flash Baseband for Oreo. Please guide me
windows 10 problem
Chin_hebbar said:
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Click to expand...
Click to collapse
I face this problem in windows 10.
first uninstall zuk drivers and qfill and disable driver signature enforcement (Google it how to do it) then install zuk drivers and qfill use original cable and your phone will get flashed
Balaji Sriram said:
I need to flash Baseband for Oreo. Please guide me
Click to expand...
Click to collapse
Follow the instruction from this post
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-baseband-flashing-guide-t3715121
Do not listen to anyone telling you to use miflash, only use qfil otherwise you WILL encounter other issues because qfil is the only way to reach the deeper partitions that mi is unable to... Other issues may range from no volte, calling or signal problems etc its just easier to do it right the first time.
Hi all! I ask your help! I have Moto z2 Force on 8.0 Oreo and I installed custom recovery twrp-3.2.1-1-nash.img and foolishly chose Slot-B and then I reboot the phone. Now when connected to a computer, it is defined as Qualcomm HS-USB QDLoader 9008 . How can I bring it back to life?! Help please! :crying:
After many attempts, it was possible to flash blankflash_from_NDX26.183-15_17. Phone reboot in fastboot and then full flash stock firmware.
yakutza said:
After many attempts, it was possible to flash blankflash_from_NDX26.183-15_17. Phone reboot in fastboot and then full flash stock firmware.
Click to expand...
Click to collapse
Samething happened to me but instead of selecting slot b my rom didnt install well so my phone is hardbrick any idea if this file will help me revive my Moto z2 force Tmobile version?
PoisonDash2 said:
Samething happened to me but instead of selecting slot b my rom didnt install well so my phone is hardbrick any idea if this file will help me revive my Moto z2 force Tmobile version?
Click to expand...
Click to collapse
This happened to me on t-mobile yesterday and I managed to solve it by downloading this: (T-Mobile only) https://drive.google.com/file/d/1fM5KLheeMYcs3yF7InOzHq6yGCOmrrbk/view
Extract the zip and while your phone is connected to your pc and booted in bootloader mode, run flash_all.bat, boot (don't flash) TWRP, install TWRP with the TWRP zip found here: https://dl.twrp.me/nash/twrp-installer-nash-3.2.1-1.zip.html
Then reboot to your newly installed TWRP recovery, factory reset, flash rom, reboot bootloader and run "fastboot -w".
After that you should boot up fine. Fastboot -w might not be necessary but I had to do it, otherwise I would boot but I would get an error message "android.process.media has stopped" without it.
Hello Friend!
Do you know if there is a solution for Moto Z2 Play? The update for Android 8 came automatically and I accepted. After a few days, he caught up and got into HardBrick! Neither the BootLoader options (power + volume (-)) are working !!
When I put it in the charger it will flash a white LED
Sorry, I'm using Google Translate
Will71000 said:
Hello Friend!
Do you know if there is a solution for Moto Z2 Play? The update for Android 8 came automatically and I accepted. After a few days, he caught up and got into HardBrick! Neither the BootLoader options (power + volume (-)) are working !!
When I put it in the charger it will flash a white LED
Sorry, I'm using Google Translate
Click to expand...
Click to collapse
If its get detect as QHUSB_BULK in conputer and installing Qualcomm drivers get it to Qh_usbloader 9008 under COMports then theres no way ti revive ur phone. Theres no Blank Flash files yet available for Moto Z2 Play
Dear members, this is my first post and the problem is very complicted, so please bear with the long post
Device details:
LeEco Le1s (x500)
MTK6795 chipset
3 GB + 32 GB
Background:
I downgraded my ROM from 19s to 14s with SP Flash tool and the phone booted normally. I went through the initial setup, unlocked Developer mode and USB debugging. Then I opened the adb toolkit on Win 7 x86 machine to unlock bootloader and install twrp custom recovery at single go (instead of letting phone rebot after bootloader unlock and then proceeding with recovery flashing).
Now phone went to soft brick, to overcome which I needed to flash userdata with sp flash tool (I have done this in past also following a tutorial, the same files were used this time). But flashing process resulted in BROM error and I was not successful.
So, I re-flashed the original 14s rom via SP flash tool to get the things back to working, but phone didn't boot properly and bootloop situation was still there. I again reflashed the same ROM and this timephone entered red light of death mode, and didn't boot up after flashing original rom.
Now, I again googled this problem and found that we need to format flash with bootloader. Here the problem complicated further.
As soon as I formatted the flash and the bootloader, laptop stopped detecting the phone via usb cable. Now I can't flash any rom using SP flash tool as the phone is not detectable.
I have reinstalled my windows 7 32 bit operating system and reinstalled all the drivers for MTK smartphone. I have another Le1s phone running on 19s version of EUI marshmallow with stock recovery and locked bootloader which is detecting fine without problems.
Please guide me how can I resolve the problem.
Also guide if the other phone can anyhow help in this matter in terms of software backup for SP flash tool (I couldn't find a way of backing stock rom using SP flash tools.
Problem summary:
1) Flash with bootloader formatted
2) Phone is not detectable on Windows 7 32 bit OS and latest SP flash tools
3) Red LED turns on when phone connected to charger or laptop via usb cable,nothing on LCD display
4) Can't reach bootloader or recovery either
Help will be really appreciated. You all know the value of data stored on smartphones.
Thanks in advance!!
i am searching for a program and working drivers for my rmx3363 real me gt master edition to flash the stock firmware while in EDL mode (qualcom) because after i installed android 13 (rUI 4) it started to not to boot and when it is plugged in my PC it is just recognized as qualcon EDL
First you dont flash any firmware under version y instaled that is importante like ( rui3). Unplugin the battery and plug it then powr on the phone. (all this process just for not will losing the mather board because the stock firmware (ofp file) rui 4 not yet ixist). I has the same prob but it works now. But via another astuce (it hard)
yeah i did that mistake of trying to switch from RUI 4 to RUI 2 lol. Now i have a hardbricked phone. There is the F.06 firmware that i could possibly flash with QPST since the phone is only accesible from EDL but 19GB maann. Probably my best bet is to act stupid tommorow. Lesson learned, hopefully others dont do this silly mistake