A couple of days ago my Huawei p7 started to shut itself down and after that it keeps rebooting.
It starts itself up and I get into the choose your language screen and then it shuts down.
When i try to get into the system recovery (using volume & power) I get the following screen:
Android system recovery <3e>
Huawei software installed failed.
Please retry!
Shutdown system now
There is no UPDATE.APP
.............................................
FAIL
And even in system recovery it keeps rebooting.
Im kinda helpless at the moment not knowing what to do.
Did this occur to anyone ? Is there a solution for this problem ?
Thanks in advance.
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
wekii said:
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
Click to expand...
Click to collapse
I've downloaded the update file and proceeded with your steps. I continued to trigger the firmware update with the factory reset.
At first it seemed to work, the phone started updating but after a couple of seconds it started to reboot itself again
I got the phone in fastboot mode and at this moment it does not restart itself !
I went on downloading Hisuite and at this moment it keeps searching for drivers on the network.
The searching for drivers is taking quite some time is this normal ?
Thank you very much for your help so far !
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked. If it's not you need to enter the next command "fastboot oem unlock 1234567812345678", where "1234567812345678" should be replaced with unlock code that is unique for your device. Instructions which explain how to obtain unlock code for your device can be found here,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
Hi,
I've got the same issue.
When I start to "force install" method, my phone doesn't boot.
It just stay in a state of "charging" but nothing append.
I flashed boot and recovery with Fastboot.
But now, when I start the phone in Fastboot&Rescue Mode, the device doesn't appear in the liste when I run adb devices.
But when I start in the "force install" mode, adb devices returns the serial of the phone (but it doesn't respond to fastboot command).
Are there other files to flash on the phone than juste recovery and boot ?
Thank's for those steps, i'll continue to try to flash again.
Edit :
Ok phone is back !
The problem came from my SD Card, I had not only the dload folder, but an other file.
Format SD Card -> dload folder -> "force install" method -> ENJOY !
Thank's a lot !
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
I followed all your steps but i get stuck at step 7. When I give the command fastboot devices it doesn't show my phone's serial number. Instead it shows a ? (question mark).
Did I do something wrong or is there a solution for this?
Thanks in advance!
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
wekii said:
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
Click to expand...
Click to collapse
Thanks for your response !
So I followed through like you said. Gave the fastboot oem get-bootinfo command and then I got (bootloader) locked. So I followed the bootloader's unlock code (official way), entered my product SN and product IMEI, used the Huawei Product ID generator followed the procedure and all I get is : Please input the correct Product ID
What did I do wrong this time ? I'm not sure if it's even possible to do this wrong. Is there another way around ?
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Pboguet said:
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I've downloaded Vroot (english version) but when i connect my phone it says not support mode
I tried to connect while in fastboot&rescue mode, because this is the only way the phone stays on without restarting.
I then tried to connect without fastboot&rescue mode. But my phone keeps rebooting. I did get a message that USB debugging is disabled. However I can't enable usb debugging because my phone won't boot up normally.
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
wekii said:
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
Click to expand...
Click to collapse
Thank you very much for all your help!
Despite following all your steps my phone keeps rebooting
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
wekii said:
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
Click to expand...
Click to collapse
Ik
After unlocking my phone I got the message unlocked in CMD.
I then flashed recovery and boot. Both times it said that the flash was succesfull, this only took a few seconds I don't know if thats normal? I then followed your last steps ( dload folder etc) and put the SD card in my phone.
It start installing but after approximetaly 25 seconds the phone shuts itself down and then reboots.
The procedure then starts again and it starts installing followed by shutting down and rebooting.
I'm sorry to hear that. Seems like it's some hardware issue.
However I still have one more idea that you can try in fastboot mode. I would recommend you to install entire firmware manually with fastboot commands.
By following previously described procedure try to extract with "Huawei Extractor" tool next images also: SYSTEM, USERDATA, CUST and CACHE.
After step number 10, try to use next commands also:
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone. Steps 11, 12 and 13 should be ignored this time.
Let me know the result
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
mbert said:
Hey,
Only TWRP 2.7.1.0 does not reboot.
Thanks in advance...
Click to expand...
Click to collapse
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Ziółek said:
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Click to expand...
Click to collapse
failed
I tried se7en and miui.
I wiped dalvik,system,data,internal,cache and custom, which only lasted about 2 seconds, but said succesful (Is that enough to delete all partitions?).
Installation of both custom roms completed succesfully and lastet several seconds (max 1 min I think).
Se7en: reboot -> huawei logo -> reboot -> language selection (in the style of stock rom?) -> reboot ...
Miui: reboot -> miui logo -> reboot -> language selection (miui style) -> reboot -> wifi selection (I skipped) -> searching for sim card -> reboot
mbert said:
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
Click to expand...
Click to collapse
To use fastboot you need to unlock bootloader first. And before flash, you need to erase partition first, for a proper job. Please read well about the fastboot procedure is a dangerous procedure
My bootloader is unlocked, but fastboot sais I don't have permission to erase partitions ...
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
.
THATS ALL WHAT I HAVE FOR MY FRIENDS.
IF I HELPED YOU THEN PLZ PRAY FOR ME. THANKS ALOT
Thank you for providing the files! I have a bricked LG LTE2 F160K, which mode should I put the phone be?
My phone can still access download mode, and when I try to start up the tool, it just says "Failed during loading flash programmer"
bro if your download mode is working then you will have to flash kdz of your modal for f160k I think its 20k. you can find the latest kdz many sites. google it lg firmware you can find it on vietnam site lgviet.com
this programe is only for qhsusb_delod mode. no download no recovery state. if you have download mode then kdz is the way to unbrick
Help! "device was not found in dload trying flash programmer" i get this error
What kind of brick you have? Its qhsusb bulk mode. Then this guide will help you
what is "ion took"??
there are no "D1L(MSM8960 RR&G)" in the selection
muzammil457 said:
What kind of brick you have? Its qhsusb bulk mode. Then this guide will help you
Click to expand...
Click to collapse
test completed but my phone didn't enter to download mode
the driver name when i connect my LG is"QHSUSB_QLOAD"
why yu no reply??
Have you installed qualcm drivers first? If no then do it if yes then in board ap choose msm8960 it will work. But if doesnt then there is 1 more 8960 selection try that
Does this method works for a sony xperia ion which has the same problem????
ahamedlaheer said:
Does this method works for a sony xperia ion which has the same problem????
Click to expand...
Click to collapse
This programe is for qualcom devices. If your experia is qualcom based then it will work. But u need to find the files to flash doe your modalm I have loaded only f160 system files.
muzammil457 said:
Have you installed qualcm drivers first? If no then do it if yes then in board ap choose msm8960 it will work. But if doesnt then there is 1 more 8960 selection try that
Click to expand...
Click to collapse
yes i install it, i tried the other msm8960 but it doesn't work
Test point to force qhsusb-dload in LG F160s
mcycharles said:
Thank you for providing the files! I have a bricked LG LTE2 F160K, which mode should I put the phone be?
My phone can still access download mode, and when I try to start up the tool, it just says "Failed during loading flash programmer"
Click to expand...
Click to collapse
Dear all,
Can some one provide me the details of test points for LG F160s i want to force it, as m phone in dead alsmost,,,
i will b very thankful
Rizwan
Why u need to do that if u r not in hard brick state?
muzammil457 said:
I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
. THATS ALL WHAT I HAVE FOR MY FRIENDS.
I have F160L.i tried same as u mention,All proceger complete but no download mode no fastboot mode no LG logo.What to do now?still on qualcomm 9008
Click to expand...
Click to collapse
Hello all
If after restore aboot phone not power on
Need restore all this file: about, Backupgpt, boot, dbi, laf, Primarygpt, recovery, rpm, tz, sdl1, sdl2, sdl3 (one by one, not MIX!!!) and after restore last sdl3 power turn on!
muzammil457 said:
I brick my lg f160k while flashing wrong kdz on it. It was in no download no recovery mode. Pc was showing qhsusb_dloade 9008. I searched alot over the internet to unbrick it but found nothing except a thread on veitnam site by a veitnamis developer. Thanks to him for this useful thread. With the help of this i unbrick my cell. It was very difficult to understand the thread while in Vietnam's language but i managed to do so with the help of google translator. I thought i should must share it on xda to English community for easy umderstading. Hit thanks if you get your phone back. And many thanks to veitnamis developer too....
1. Download the qualcom drivers and install it from given link.
https://app.box.com/s/5n42md550n4oxne04xttfz788cp0i4i3
Open device manager and ensure that you have correctly installed qualcom 9008 drivers. Remember the com port
2. Download and unzip this folder
https://app.box.com/s/zvvj2v87csuwmv93k7ztzevuiytyd0fi
You shall have a tool Boar Diag v3.99c folder and two folder named S and L.
3.IMPORTANT. You will have to choose folder S For F160K and S and for F160L and LV choose Folder L.
4. Now run the tool.
Check the 2 points on tool
1.Ap check
2.Emmc Test
In Ap chipset choose board
For F160s and F160k
D1L(MSM8960 SKDA)
FOR 160L
D1L(MSM8960 LV)
Select Com Port shown in device manager of your computer.
In TARGET DIR Choose the Folder of Named S or L according to your modal, As i told you earlier in step 3
Rest all should be unchecked
PRESS START
https://app.box.com/s/hr8y0cmzcond0jciemprl5jzr4rllggn
Now test will start and will take 10 seconds to complete
If this test run successfully AP and EMMC should show pass on tool window
5. In this step Now only uncheck
Emmc Test and then check the
Boot Image Restore and select ABOOT from drop down menu.
Only w points Checked.
Ap Check
Boot Img Restor
Rest all should be uncheck the same as in previous step.
PRESS START
https://app.box.com/s/w1r560py2bm2wwlbtch9bn7kh1bski2u
Now it will Test the AP CHECK and will write Boot image to your mobile.
It will take 10 to 15 seconds.
After successfully completion of this test you ll see download mode on your mobile. Or you may see an LG logo with a secure boot massege.
Important...
STEP 6 was not mentioned in orignal thread. I did this at my own and got my result.
6. If you dont see download mode or LG logo after completing step 5 even successfully completion shown ion tool, As in mine case on F160k. Then try step 5 with AP CHIPSET with D1L(MSM8960 RR&G)
rest same selection.
AND PRESS START.
I hope this will resolve your issue. As i did.
7. NOW ITS TIME TO FLASH LATEST KDZ FIRMWARE ACCORDING TO YOUR MoBILE Phone.
.
THATS ALL WHAT I HAVE FOR MY FRIENDS.
IF I HELPED YOU THEN PLZ PRAY FOR ME. THANKS ALOT
Click to expand...
Click to collapse
any other link for qualcomm drivers?
Link is fine. U can download it from google.
Need some Help
My phone goes to Service Mode but not in Download mode.
Should i try this method?
And how i can find out my phone is S OR K OR L originally hardware based
Waiting for your answer .
My phone is dead since 1 month
hi,
my micromax a1 was runnning marshmallow 6.0.1 when during a security patch update installation got stuck and failed to boot again. now just booting into "dead android with exclamation mark". upon pressing power button and volume up and going into recovery(Android stock recovery) menu , cant wipe partition or data as it throws error "E: failed to mount/ cache" errors..
upon trying to install with any SD card also throws same error.
then i tried to install through ADB, while connecting to PC , PC not detecting mobile in recovery mode but detecting in bootloader mode. with fastboot flash command (for installing TWRP/CWM) in bootloader mode, error coming as "sending recovery failed(unknown status code)" .
Kindly help...
same happened to me yesterday . do you find any solution ??
Hi there !
STEP 1: DOWNLOAD the FLASH TOOL from this this link :LINK TO DOWNLOAD FILE
It is almost 30 MB in Size. And EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) of your computer.
STEP 2: DOWNLOAD LOLLIPOP FLASH FILE
DOWNLOAD LINK FOR LOLLIPOP: HERE
After downloading this flash file EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) on your computer.
STEP 3: NOW INSTALL DRIVERS:
YOU NEED TO BE ON WINDOWS 7 TO INSTALL DRIVERS (WINDOWS 8 DOESN'T SUPPORT THIS DRIVER / PHONE IS NOT DETECTED)
DOWNLOAD DRIVERS from this link : HERE
EXTRACT AND INSTALL THE DRIVERS : Next next next and finish If you see an security warning ( a red coloured pop up ) choose INSTALL IT ANYWAY
IT IS RECOMMENDED YOU TO RESTART YOUR PC.
STEP 4:
Now we have Extrated /unziped 2 files. One is FLASHTOOLS and other is FLASH FILE and Extracted it or unziped it to Desktop or Somewhere.
One of it having the name SP_Flash_Tool_exe_windows_v5.1424.00 or open both folders then one of it having the flashing tool. OPEN THE FOLDER NAMED SP_Flash_Tool_exe_windows_v5.1424.00
it contains an application named fashtool.exe OPEN IT
NOW THE APPLICATION IS ASKING FOR SCATTER LOADING FILE
its a txt file which is on the extracted flash file folder
BROWSE it by clicking Button named Scatter Loading
click OPEN
STEP 5:
HERE IN THE DROPDOWN BOX, IT SAYS DOWNLOAD ONLY, CLICK ON IT AND SELECT FIRMWARE UPDATE ONLY.
IF YOU SELECT FORMAT + DOWNLOAD, THEN YOU WILL LOOSE IMEI NUMBER.
NOW CLICK DOWNLOAD BUTTON ( GREEN ARROWED BUTTON NAMED DOWNLOAD )
IN CASE YOU LOOSE IMEI NUMBER, THEN REFER HERE
STEP 6:
Now SWITCH OFF your PHONE and REMOVE BATTERY
STEP 7:
CONNECT your PC via USB CABLE
wait for the driver Detection.
THE FLASHING PROCESS WILL START AUTOMATICALLY you can See the progress in progress bar which is on bottom of flashing tool Application.
WHEN IT IS FINISHED DISCONNECT USB AND RESTART YOUR PHONE.
NOW YOU WILL GET LOLLIPOP UPDATE IMMEDIATELY.
NOW REFER HERE TO ROOT MARSHMALLOW
HIT THANKS IF HELPED
if link do not work here properly then just google 'canvas a1 stuck on startup' ... and follow link in associated with xda
Device is dead
My phone is neither switching on, nor charging.
I flashed the stock ROM due to some problem with the rooted device through SP Flash tools. It completed successfully, but the device is not switching on or charging.
KIndly help
Hello, I chose "reboot in recovery" on Pixel UI Plus A11 ROM and now ended up with bootloop on "Redmi" logo.
If I press power+down, the screen turns off and MediaTek USB Port appears in Windows Device Manager for a moment and then disappears and "Redmi" logo shows up again.
If I press Up+Down+Power at the same time, the screen turns off, after around 30 seconds the phone vibrates once and then screen is still blank. At this time, "MediaTek USB Port" device keeps reconnecting in Device Manager. I can't turn off the phone with these 3 buttons. Should I disassemble the phone and disconnect the battery?
How can I repair my phone? Please help.
Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.
getimiskon said:
Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.
Click to expand...
Click to collapse
my phone not recognized as mediatek usb port any solution??