Lenovo L38111 booting problem - Android Q&A, Help & Troubleshooting

Hi there!
I have purchased a LENOVO L38111 smartphone which had its default ROM that I was trying to replace with another one. I've opened the Bootloader then I put TWRP on it. I've made a full backup with the TWRP in case an issue comes up, I could switch back to original system. I've installed Pixel Experience ROM following the instructions which was pretty pleasing to me, I've used it for a while. However, once I started the Waze app then I realised that the GPS is not working. I thought I have a full backup in the TWRP, a restore which was running appropriately, it got displayed that restoring was successful, restart.
Since then, it does not turn on, the screen is black. I've tried to restore my phone with the Qualcomm QPST program. I've installed QPST on PC, I've installed Qualcomm driver as well. If I connect the phone to PC with an USB cable, the USB Qdloader 9008 (COM8) driver gets displayed in tool manager, once I start QPST Configuration, then it says Q/QCP-XXX at the Active phone, however, in State, the progress signal goes up to approximately 20%. When I start QFIL, I choose the port (HS-USB Qdloader 9008 (COM8)), then the files from the default ROM but it says:
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Is it because the opened bootloader?
Do you have any idea what I can do?
Thank you in advance!

Related

Star x26i bricked? SPmultiPortFlashDownloadProject

Hello
Last week I became my Star x26i. Its quite a very good phone, but because of WiFi and Battery issues i tried to update it to a newer version, like in this tutorial :
http://forum.xda-developers.com/showthread.php?t=1680338
So I used a program, calles SPmultiPortFlashDownloadProject
Everything went fine, but after the program erased the emmc Windows tried to install a new driver and failed. The program stopped and now the phone cant boot anymore (understandable with an formatted eemc...) The Pc detects the phone anyway, first as an unknown device and after installing a new chipset driver as "MediaTek DA USB VCOM Port (COM6)" If I try to reflash with the same program it gives me following issue like on this picture: http://imageshack.us/f/856/erroroly.png/ (Error: No Bootrom USB Port was found! COM6 is not a Bootrom (preloader) USB Port. Auto polling Number0.
Are there any Chances to rescue this device or is it totally bricked? Thanks in advance...

G3 Won't Boot

My G3 powered off and stopped booting today. It was connected to a laptop via an old frayed usb cable, and it suddenly shut off.
It was then that the power button stopped working and I saw the QHS usb loader device of death (Windows new device notification)
Intermittently I have seen the QHS USB 9008 device when connecting to my PC, but not always.
I tried to run the QCDiag tool, but it said failed to flash.
Any tips?
Is it possible a connection is loose? Wondering if I can open the phone up and fix it.
It was working mostly fine prior to this, with occasional issues of the SIM being undetected.
Did you try the following program?
"BoardDiag3.99c.zip" in the OP of this thread [FIX] Unbrick LG G3 stuck in Qualcomm HS-USB QDLoader 9008 mode?
It is certainly possible that the connection is unreliable. I always use the original USB cable, and preferably with a USB 2.0 port that's directly off of a PC motherboard rather than through a USB hub. Also, you might need a special driver. You can get it from here http://www.androidbrick.com/download/qdloader-hs-usb-driver/. Install the correct (32 or 64-bit, depending on which version of Windows you're running) driver with the phone disconnected from the PC, then reboot the PC, connect the phone and give Windows up to 10 minutes to install the driver. Every time you choose a different USB port after that, it'll have to load (not install) the driver again (that's standard for all USB devices. Then try the BoardDiag program again.
Also, if you can get this far, it's preferable to only use the BoardDiag software to flash a few very specific partitions rather than the entire 10B TOT. After flashing these partitions, then you can flash the 10B TOT with the regular TOT flashing software.
Use the screenshots in this thread as a guide for which partitions:
Unbrick lg g3 qhsusb_bulk, qualcomm 9008 workking 100% by board ver 2.9a.
Yes, I tried this tool but it said failed to flash after clicking on Start.
If I open up the device, is there anything I can check for?
ipaq_power said:
Yes, I tried this tool but it said failed to flash after clicking on Start.
If I open up the device, is there anything I can check for?
Click to expand...
Click to collapse
I've never opened up the G3 (further than removing the back/battery). The only reason I've heard of doing so regarding QHSUSB mode is if you have to force it into QHSUSB_BULK 9008 mode, but you'd have to Google for that - there are diagrams for two pins you need to short to get it into that mode but it sounds like you're there already so that might not be necessary.
Did you install the drivers I linked to (while the phone's disconnected from the PC?), reboot the PC, connect the phone to a USB 2.0 port and give the PC up to 10 minutes to load the drivers you installed?
I also highly recommend using an original good cable, so you might have to buy one from LG. It's possible that any very high-quality USB cable will work, but it's recommended to use the original (in good condition). I wouldn't use a USB cable with frayed wires at all. Next thing you know there'll be a short and possibly your PC, your PC's USB ports, and/or your phone or your phone's MicroUSB port will be blown.
Yeah the drivers were installed properly.
I tried to run the LG Smart Boot diagnostic tool, but the phone did not stay on for long enough to execute the checks.
It briefly connected to the tool before powering off again.
I have received a replacement phone, but it came with firmware version 35B.
ipaq_power said:
Yeah the drivers were installed properly.
I tried to run the LG Smart Boot diagnostic tool, but the phone did not stay on for long enough to execute the checks.
It briefly connected to the tool before powering off again.
I have received a replacement phone, but it came with firmware version 35B.
Click to expand...
Click to collapse
What do you want to be on, and do you want to be rooted or unrooted?
If you want to be unrooted on the latest ROM, just flash the 47A KDZ in @annoyingduck 's stickied return to stock thread in the General section, or if you have an activated Verizon SIM, take the two OTAs 35B->46A and 46A->47A.
If you want to be rooted, flash the 10B TOT using the .DLL that was extracted from the 35B KDZ, root using the Stump app, use TWRP Manager from the Play Store to put TWRP on, then flash the bootstack and ROM you want.

Hisense c20 bricked after root.

Hello all.
I have hit a problem with my Hisense c20. I rooted using kingoroot and everything seemed to work fine. SuperUser was installed and working as it should. The phone then ran flat so I plugged it in and booted but it just hung on the SMART powered by android screen. So I restarted again into recovery mode and cleared system cache. Rebooted again but same thing. So tried again but with the wipe user data option. Still just hangs there. I then decided to try flash a stock rom via needrom. I followed the instructions but cannot seem to get the phone to be visible as a com port on Windows 7 64 bit. I have tried different cables and USB ports and reinstalled drivers countless times. Please could anyone assist me on getting this phone to be seen as a com port so I can flash it with QFIL.
Kind regards
Ryan
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Need a file *qcn. or backup NV backup ?
Who has the opportunity to give?
[email protected]
[email protected]
RuanRex said:
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Click to expand...
Click to collapse
Hi Ruan. You haven't found a custom recovery?

How to can i unbrick my Old Samsung Galaxy Phone?

hello,
i have this old Samsung galaxy young GT-S6312 Running JB 4.1.2 . i was using it as my secondary phone. and yesterday it just stopped Working. when i pulled it out my pocket it was switched off and when i tried to on it, it would go to the very beginning of Samsung animation(i could only see animation for like a half of second ) and then it would crash. i tried to boot into recovery but it crashed there too and then then it stopped Working.
phone is just dead now, no display no charging animation(Battery is fine i checked it on another phone) power & Vol buttons does nothing.
Now When i connect it To my PC with battery Nothing happens however when i connect it without battery i can hear a loop of plugin and plugout sound (windows 7) and in device manager i can see qualcomm hs-usb qdloader 9008 (com10) and device manager keeps on refreshing like a device is being plugged in and plugged out.
is it HardBrick or the phone is just dead?
--edit--
phone is rooted
CWM recovery & Xposed Framwork is installed
r2dak said:
hello,
i have this old Samsung galaxy young GT-S6312 Running JB 4.1.2 . i was using it as my secondary phone. and yesterday it just stopped Working. when i pulled it out my pocket it was switched off and when i tried to on it, it would go to the very beginning of Samsung animation(i could only see animation for like a half of second ) and then it would crash. i tried to boot into recovery but it crashed there too and then then it stopped Working.
phone is just dead now, no display no charging animation(Battery is fine i checked it on another phone) power & Vol buttons does nothing.
Now When i connect it To my PC with battery Nothing happens however when i connect it without battery i can hear a loop of plugin and plugout sound (windows 7) and in device manager i can see qualcomm hs-usb qdloader 9008 (com10) and device manager keeps on refreshing like a device is being plugged in and plugged out.
is it HardBrick or the phone is just dead?
--edit--
phone is rooted
CWM recovery & Xposed Framwork is installed
Click to expand...
Click to collapse
x.ak**** said:
Like all my comments above to encourage me to help you.
Okay so first of all I will let you know why a phone gets bricked-
>Corrupted Rom
>Some system files got deleted
>Rooting
>Modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
MY CASE
I always keep two phones with me like one for my experiments and one as a backup. In this case I'll be talking about my LYF WIND 3 that got bricked.
>Actually I was trying to install TWRP onto that phone but first I had to root it, and due to the upgraded android security, I wasn't able to do via KingoRoot so I tried I-ROOT and it did the job but instead of kingo-superuser I got some ****ty superuser so i tried granting permission to the actual SUPERUSER and while doing so I accidentally double rooted my phone (First with I-ROOT and then with KingoRoot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
>The second time I was trying to replace the boot animation and logo but did something wrong so the same situation arose again.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CURE
So my phone uses a Qualcomm CPU so i just guessed I'll flash it again.
*After Intense Googling*
I found this software QFIL (Qualcomm Flash Image Loader)
I downloaded this file and the drivers for my device. *Google it you'll find for yours too*
Then I downloaded the Stock Rom for my device *Google it again*
Now I just went over to Flat Build in that software and loaded the firehose file and the rawprogram.0 and Patch.0
Now I had just put my device in Download Mode (Volume Keys and Power Key)
Connected via USB and it detected it and then just clicked on DOWNLOAD
It takes about 5 minutes.
After this your phone gets good as new (Unroot, Full Reset)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Click to expand...
Click to collapse
Drop a like on my replies and Download the correct QPST drivers along with the correct firmware for your device.
Sent from my One Plus 5T using XDA-Developers Legacy app
x.ak**** said:
Drop a like on my replies and Download the correct QPST drivers along with the correct firmware for your device.
Sent from my One Plus 5T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hello i was also looking for a solution when i found QFIL Method already tried it. there are two problems im having with it
1. phone is unresponsive so i cant boot into download mode
2. phone just keeps on plugin and unpluging itself so QFIL can not put a lock on it and gives following error
Code:
2018-04-14 23:53:13.007 23:53:12: ERROR: function: rx_data:247 Error occurred while reading from COM port
2018-04-14 23:53:13.007
2018-04-14 23:53:13.007 23:53:12: ERROR: function: sahara_main:924 Sahara protocol error
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015 23:53:12: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015
2018-04-14 23:53:13.015 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
2018-04-14 23:53:13.023 Finish Download

NO QHSUSB_bulk in device manager

I'm trying to install stock rom in my OPPO A57 as it went dead and doesnt turn on. While going through the process i had to install Qualcomm USB drivers . After installing the drivers, there was no connection as it didnt showed up in my device manager. Went through several fix videos on youtube. Many of those tutorial videos showed to update the QHSUSB_bulk (found in device manager) with the qualcomm drivers. Unfortunate thing is there is no QHSUSB_bulk in device manager. How do i install the drivers? why QHSUSB-bulk is not showing in device manager? Help please asap.
toposexxum said:
I'm trying to install stock rom in my OPPO A57 as it went dead and doesnt turn on. While going through the process i had to install Qualcomm USB drivers . After installing the drivers, there was no connection as it didnt showed up in my device manager. Went through several fix videos on youtube. Many of those tutorial videos showed to update the QHSUSB_bulk (found in device manager) with the qualcomm drivers. Unfortunate thing is there is no QHSUSB_bulk in device manager. How do i install the drivers? why QHSUSB-bulk is not showing in device manager? Help please asap.
Click to expand...
Click to collapse
By any chance do you have another computer, if you do, try on that one. If not tho, try replacing the USB cable or check if the micro USB port to see if it is damaged somehow, it is always important to check those things first.
I personally own the device and have never faced a issue and even went ahead and installed CM 13.0 on it.
Pleaaaaas
Help me for root my device
S7
I'm going to give u info that you rarely find about this issue.
many users didn't realize that that port will only be active for a very short time. Pressing Power+vol up+vol down at the same time SHOULD ONLY BE DONE AFTER you have load all necessary files into QFIL or DownloadTool, it should the last thing u do.
It is ok to let the device connected to your pc while setting up qfil etc, but your phone must be in shutdown mode.
now open device manager, then press all three buttons at the same time, release aftee you see device manager is showing sign of detection of the qualcomm port, do not wait more than 4 seconds to press DOWNLOAD. And click DOWNLOAD on the QFIL app. I suggest using QFIL v1.0.0.2
after that your phone will reboot normally. QFIL will look like it's still not finish, but it actually had finished flashing so you can close it.

Categories

Resources