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 (Everybody knows )
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!!
can explain how you were able to solve it?
facing a similar issue would ne helpful.
thanks.
Related
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you
Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
on my phone TWRP shows no files on in any folder. can you pls help?
krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method
Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.
Hi
Please i need help
I want to unlock bootloader and flash TWRP & Magisk on my realme 2 pro 4/64, after i flash all items, my phone was bootlop
Then i tried to relock bootloader, after that, my phone cannot boot and only showed this message.
"the current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
how can i fix it?
note : i attached images of the problem, thats not my pictures, i save from the pther person who have the same problem. but i can find the best solution
thank you very much
flash stock recovery through fastboot. Then again install twrp custom recovery through fastboot. Then install stock zip rom by flashing through twrp. You can get stock recovery and stock rom from the following link.
https://forum.xda-developers.com/realme-3-pro/how-to/guide-to-stock-rom-stock-recovery-t3940604
fix
kisutbener said:
Hi
Please i need help
I want to unlock bootloader and flash TWRP & Magisk on my realme 2 pro 4/64, after i flash all items, my phone was bootlop
Then i tried to relock bootloader, after that, my phone cannot boot and only showed this message.
"the current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it"
how can i fix it?
note : i attached images of the problem, thats not my pictures, i save from the pther person who have the same problem. but i can find the best solution
thank you very much
Click to expand...
Click to collapse
have you fixed?how
Bootloop please help asap!!
I was trying to install custom rom but I didn't took back up and wiped every thing on internal memory and also flashed stock recovery of realme 2 pro LOCKED the bootloader also I was hoping that I would be able to install stock rom by realme . But now am stuck at bootloop only realme logo appers
Basically I only have stock recovery on my phone and nothing else in the internal no OS installed bootloader is also locked so am not able to install twrp recovery to please help me install any rom .I am stucked due to lockdown no Service center is open. Please help asap??? I can't leave without my phone in this lockdown
davsagar4 said:
I was trying to install custom rom but I didn't took back up and wiped every thing on internal memory and also flashed stock recovery of realme 2 pro LOCKED the bootloader also I was hoping that I would be able to install stock rom by realme . But now am stuck at bootloop only realme logo appers
Basically I only have stock recovery on my phone and nothing else in the internal no OS installed bootloader is also locked so am not able to install twrp recovery to please help me install any rom .I am stucked due to lockdown no Service center is open. Please help asap I can't leave without my phone in this lockdown
Click to expand...
Click to collapse
Possible 100% solution, but it's paid.(800 inr)
In my case I'm fully locked (by vol down and power,vol up and power,both up down and power) i only see error..(no fastboot windows)
So to overcome this you need to pay someone some money (i paid 800,for oppo special I'd and password for 1 time),and download a compatible firmware (rom) and msm download tool in pc make sure you also have team viewer, as damn oppo won't allow you to flash firmware for free ad there is no crack for msmtool...hope this helps.. i also did this process during lockdown and learned a moral:-never relock bootloader
Qfil and other processes doesn't worked for me?
Don't wast time in crackes etc there is no official crack of realme 2 pro firmware bcoz there is always a different tool for each rom???..
I waited to fix this for 27 days.
davsagar4 said:
I was trying to install custom rom but I didn't took back up and wiped every thing on internal memory and also flashed stock recovery of realme 2 pro LOCKED the bootloader also I was hoping that I would be able to install stock rom by realme . But now am stuck at bootloop only realme logo appers
Basically I only have stock recovery on my phone and nothing else in the internal no OS installed bootloader is also locked so am not able to install twrp recovery to please help me install any rom .I am stucked due to lockdown no Service center is open. Please help asap
Click to expand...
Click to collapse
He_man_r35 said:
Possible 100% solution, but it's paid.(800 inr)
In my case I'm fully locked (by vol down and power,vol up and power,both up down and power) i only see error..(no fastboot windows)
So to overcome this you need to pay someone some money (i paid 800,for oppo special I'd and password for 1 time),and download a compatible firmware (rom) and msm download tool in pc make sure you also have team viewer, as damn oppo won't allow you to flash firmware for free ad there is no crack for msmtool...hope this helps.. i also did this process during lockdown and learned a moral:-never relock bootloader
Qfil and other processes doesn't worked for me?
Don't wast time in crackes etc there is no official crack of realme 2 pro firmware bcoz there is always a different tool for each rom???..
I waited to fix this for 27 days.
Click to expand...
Click to collapse
hey can you provide me that person's contact info?
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile
Okay, Let me explain exactly what I did here... I first flashed Twrp using SP flash tool which worked without too much problem. Then I attempted to install the latest super su zip which told me the boot.img was already patched and it could not find a ramdisk... So I moved on and flashed the latest Magisk zip which flashed no problem. Rebooted the device and it came up with a red boot state telling me it would boot in 5 sec. It did not boot at all. Turned off the tablet and rebooted into twrp again. I then flashed the OTA update system.img, boot.img, and re-flashed twrp from twrp itself instead of the SP flash tool. It booted into twrp no problem, however now it said it could not mount the system partition. I did a full data wipe, factory reset, rebooted into twrp again. Same issue. So I attempted to re-flash the firmware with SP flash tool. Did not notice i had it set to format and download and not only download. It said formatting for maybe 2 sec and gave me an error. Now the device will not turn on at all... no screen whatsoever, no recovery, etc... I have had no luck getting the asus flash tool to even recognize a com port however SP flash tool seems to be able to flash the device no problem. I extracted the .raw firmware file I have for the latest firmware, modified the scatter file to allow flashing all partitions, and I did a full firmware flash of the device using SP flash tool. However it still does not turn on... it does nothing... So I'm assuming that I accidentally formatted over the bootloader... And I cannot find a bootloader flash file for this device anywhere... So I'm stuck with an Asus ZenBrick... Does anyone know a way to fix this issue? When I plug the device into my computer and open device manager it switches between the preloader and mtk serial port very quickly not staying on either one very long. I'm assuming this is why I cant get the asus flash tool to work and SP flash tool works off just the initial preloader. I just bought this tablet from someone and managed to hard brick it in less than a days time... Any help at all with a way to revive this device will be greatly appreciated. Thank You in advance to anyone who tries to help me fix my mess up.