Hey Guys, Welcome to Another Brand New Tool For All Le Eco Devices and Maybe For all Other MTK or Qualcomm running devices (if you know what is ADB / Fastboot and basic stuff regarding it, Then you can use it onto every single android device)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is This?
This is basically a Software for Le Devices, from which you can easily able to Unlock bootloader, flash TWRP, Root, install mods and many many things.
Is This Safe to Use?
Absolutely Yes!
Features :
View features from here
Requirements :
1. Dot Net framework must be greater than 3.5
2. Visual C++ Redistributable package
3. Any Windows version
Credits :
1. To "Rishabh Rao" Who is the original maker of this tool (check out here) - Thanks Bros:laugh:
2. To Androidlib .Net Library (Check out here)
3. To my Best AndroidCtrl and AndroidCtrlUI THE BEST and Very thanks to his creator who helped me a lot (here)
4. To All things I have used in my tool (really appreciated there work):laugh:
Some Snappies!! :cyclops:
All Views Downloads HERE :
Like my Work Do Support and Share this Tool to every Le User you Know, Hit THANKS Button too:angel:
Hi. Sorry if this has been asked before, but i am one of the small number of ppl who purchased the LeMax Pro X910 and bricked the phone while trying to install a Le Max 2 rom (was told both devices could use same rom) and now the device is in an eternal Qualcomm Qfil 9008 state, and the screen never turns on. I was told by a very knowledgeable person that the phone is probably stuck in a ramdump state. Can this tool help in such cases? Thanks for your contribution.
JohnnySJ said:
Hi. Sorry if this has been asked before, but i am one of the small number of ppl who purchased the LeMax Pro X910 and bricked the phone while trying to install a Le Max 2 rom (was told both devices could use same rom) and now the device is in an eternal Qualcomm Qfil 9008 state, and the screen never turns on. I was told by a very knowledgeable person that the phone is probably stuck in a ramdump state. Can this tool help in such cases? Thanks for your contribution.
Click to expand...
Click to collapse
Ya you can use it for flashing stock ROM...go to the root tab from the drop down list select stock ROM and browse the stock ROM from it..then connect ur phone to PC in fastboot but first unlock it by normal method use LE 2 method to do that...then click on update button ...to flash the stock ROM in fastboot
Tried it but unfortunately the tool requires the phone to be recognized via adb, and our bricked phones are in a special Qualcom QFil 9008 Loader Mode. So no luck.
JohnnySJ said:
Tried it but unfortunately the tool requires the phone to be recognized via adb, and our bricked phones are in a special Qualcom QFil 9008 Loader Mode. So no luck.
Click to expand...
Click to collapse
Oh..**** man... Sorry bro.. That my tool won't helps you coz I don't have any LE eco devices to make this tool.. All I did is with my knowledge and some Qualcomm chipsets resources.. That's it..I think I need to study more about le devices....anyways thank you for using it. ...and one sec loader mode means what ..similar to fastboot mode or bit different... Kinda..
leeco-x820-max-2-super-unbrick-guide
This tutorial solves the same problem that your smartphone has, only on the x820 model, but it can help in some way.
rcfree said:
leeco-x820-max-2-super-unbrick-guide
This tutorial solves the same problem that your smartphone has, only on the x820 model, but it can help in some way.
Click to expand...
Click to collapse
Ohh could you describe more, then i will integrate it in the toolkit.. Updates ?
Related
Hello, i whant to put 4.4.3 on N4 and with normal flash-all.bat(did it many times before on 4.4.2) and then phone was flashing booloader..waiting devices...and nothing.Phone screen is black only a sound on windows when i connect it.
How can i fix my nexus?
Edit: 1)if i shutdown with pwrbutton 10 sec and turn on via pwr+volume i hear as i connected the phone
2)if turn on normal red light a few sec..
Bricked???
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
mrao said:
Are you able to get to bootloader? Was it unlocked before you flashed the 4.4 3 image
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
krystyuc said:
1)I had PA before on it
2)Yes i was unlocked
3)Black screen...nothing.Just a beep like i connect it to pc....and a red dot a few seconds.
Click to expand...
Click to collapse
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
Just a wag, but have you tried letting it charge first?
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Yes.
Edit: If i plugit into a new pc it shows me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some serch i think it's bricked....only Jtag can fix it
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
M3drvr said:
Don't think its bricked. Try type "fastboot devices" in a command prompt in your fastboot folder. If it shows up under listed devices its not bricked. I've had this happen where just the file that makes the screen light up didn't get installed. Just have to reinstall the bootloader. No big deal.
Scratch that!
I'll buy it from you for $5
Click to expand...
Click to collapse
1)Already tryed that and the adb devices...no luck
2)Nothing is displayed on my n4 screen,absolutly black,but it's still on
3)my pc dose a sound when i connect/disconnect the phone
I found something
"Seems that while flashing that ROM you have managed to destroy parts of the Bootloader, wich finaly results in the device doing nothing. (Black Screen etc)
Partitialy you are right yes "QHS-USB Mode" means your device is hard bricked an in the so called QHS-USB Download Mode
but this mode is meant for vendors to flash bootloaders etc on the devices.
To access the device in a propper way u need some "non-public" tools wich QCOM usaly only supplies to vendors not to endusers!
Without thoose programs u will be not able to access the device in any way, even with thoose tools without the expierience and knowledge and files u need, i guess u will not be able to recover it yourself.
I do not want to risk some trouble with QCom at all so i do not can point u to the propper tools to use but i'm sure when using google u will be able to find out what tools i'm talking about.
In my mind the best way for you to recover that device is a JTAG
So my suggestion is to search for a JTAG in your region a JTAG in europe usaly is arround 30 euro but price can differ in your country"
So.....no luck till now,the phone is hardbricked.I'll send it monday to warranty,maybe they will fix it for free if not....then this is an excuse to buy N5
Hi,
For all those who have a dead Redmi Note 3 and not beed able to recover it yet, here is a simple guide which I have tried many times to bring life back to my RN3. Well, the solution is simple. I am using Win 7 64 bit edition.
First, use the SP-Flash-Tool-v5.1532.00 and install the latest stable fastboot ROM, but remember to "ENABLE" the first preloader option in SP Flash tool. When it is finished and you seen GREEN Mark in the end, Try to boot your phone by pressing power button for 10 seconds. If it boots, no need to go to next step. But if nothing happens, go to Next step.
Now download SP_Flash_Tool_exe_Windows_v5.1516.00 and install the same fastboot ROM, but remember, this time "DISABLE" the first preloader option in SP Flash tool. When it is finished and you seen GREEN Mark in the end, Try to boot your phone by pressing power button for 10 seconds. Your phone must vibrate and power ON after some seconds. Thats it. Here are some imp links if needed.
1. Install drivers and restart PC
https://mega.nz/#!DtIhzSiD!qLmplkvEQ-ZSegaGbpyMuzH198b90joNhkPkJa6hzWg
2. Download or use a OFFICIAL AND STABLE FASTBOOT ROM
http://bigota.d.miui.com/V7.1.6.0.L...HNCNCK_20160107.0000.12_5.0_cn_434e06a8a9.tgz
http://www.mediafire.com/download/zcc0vzca9o1xt5d/SP_Flash_Tool_v5.1532.zip
https://www.mediafire.com/?tpjg4jtdf7sj40t (SP_Flash_Tool_exe_Windows_v5.1516.00)
Thanks and courtesy of jamflux
http://en.miui.com/thread-221115-1-1.html
will this work dead phone bricked because of official update MIUI 7.1.13.0 LHOCNCL
vkeymi3 said:
will this work dead phone bricked because of official update MIUI 7.1.13.0 LHOCNCL
Click to expand...
Click to collapse
I hope it will work on any RN3.
Can I do the same for Redmi Note 3G?
Broken Link
Hello
The mega link doens´t work
Thanks
Leyrio said:
Hello
The mega link doens´t work
Thanks
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347767433
redmi note 3 dead
My Redmi Note 3 (Mediatek), by mistake I erased completely using SPflash tool in "format all" mode.
now its not turning on (DEAD).
Symptoms:
1. Red light for first few minutes while charging after that red light goes off.
2. when red light turns off, my PC detects phone for a second.
3. Mediatek COM port goes on and off for few seconds.
Whats next?
can I recover my phone in this condition?
if yes then how?
how to deploy bootloader/Fastboot?
how to deploy ROM on this device?
are hennesey correct ROM for mediate device?
can I do the above procedure with my phone?
Thanx Dear
Its Working ..Lots Of Thanx:good:
use SP flash tool SP_Flash_Tool_v5.1728_Win
check preloarder
WORKK 100000%
woprex said:
use SP flash tool SP_Flash_Tool_v5.1728_Win
check preloarder
WORKK 100000%
Click to expand...
Click to collapse
its work.. thanx a lot.. :good::good::good::good::
May I know how long is the process? I waited for 15 mins and nothing happen, no "green" bar..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Allah Apnake er chay uttom bodla dan koruk vai
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?
I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol
Hey all, I recently purchased a new 7TP 5G MCL and decided I'd try flashing a new ROM and rooting it before I had anything on the phone in the first place. I got the unlock token from T-mobile and successfully unlocked my bootloader - and this is where I got careless and didn't notice the difference between 7TP (HD1917 among others) and 7TP 5G (HD1925). After flashing a few recoveries/ROMs, I noticed that the wifi wasn't working. This was the first sign something was wrong.
Since then, I've tried flashing other ROMs, until I realized that the issue was that this phone had a different modem than other 7TP so it needed a ROM that was specifically compatible for this. I tried flashing a 'compatible' recovery/ROM but it doesn't seem to fix my issues.
I just checked my phone settings and it says it's an HD1917. That doesn't sound right.
I'm using the MSM tool and though I have Qualcomm HS-USB showing up in my device manager, nothing substantial is showing up in the MSM tool when I click enum. I just see 39 rows of "Index = #" (ranges from 1 to 39) and "Status of Connection = N/A". For a brief period just now, I was unable to access anything other than the bootloader - since then I was able to flash a new recovery and access it, but haven't tried anything else yet.
Any tips?
If you have the phone from T-Mobile, the 7T Pro 5G Mclaren, then it is the HD1925 (and that must be what you have since you needed the unlock token.
Where is it showing HD1917?
My guess is you flashed a ROM for the international 7T Pro and not the T-Mobile 7T Pro 5G McLaren as you suspected.
Find the thread about how to restore the phone back to stock using the MSM Tool (for HD1925, in these subforums) and see if that helps.
However, if your FP sensor and WiFi still don't work, then you corrupted your persist partition which I fear may be the case. Try the MSM tool and let's go from there.
Yeah, the thing is -- I've tried the MSM tool but nothing of note shows up when I enter EDL mode or click "Enum". My device manager does say I have Qualcomm HS-USB QDLoader9008 connected, though.
The "Device Properties" in settings (all the way at the bottom) is what's showing HD1917.
Edit: I'm trying the MSM tool for HD1925. I don't think I should be trying the one for HD1917...right?
For the record, this is what my Device Manager & MSMDownloadTool looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My lineage 18.1 bootloader recovery logs say, all over the place, "model=HD1917". Looks like this is packed into the phone.
Well, it's back to being an HD1925 again, and wi-fi is connected properly. Weird how that ended up.
I went into recovery mode, clicked a few buttons (mount/unmount system, delete data, ...) and it booted right up like this as JoeF2's lineage 11 in https://forum.xda-developers.com/t/rom-lineageos-18-1-android-11-unofficial-mar3.4192829/page-5.
Thanks for your help glad nothing was permanently broken. Now time to fully set up this phone.
zintegy said:
For the record, this is what my Device Manager & MSMDownloadTool looks like.
View attachment 5373157
Click to expand...
Click to collapse
The issue is the Qualcomm HS-USB QDLoader 9008 has an explanation point by it in device manager, which means you have the wrong drivers installed. Follow the directions in many threads regarding getting MSM tool working to properly update drivers. Then it should show up in the MSM Tool, assuming you are in EDL mode and issue enum command in MSM tool within 10 seconds of entering EDL mode or the phone will automatically exit EDL mode and reboot.
zintegy said:
Edit: I'm trying the MSM tool for HD1925. I don't think I should be trying the one for HD1917...right?
Click to expand...
Click to collapse
Yes, you need the MSM tool for the HD1925. Don't use any other versions of it, such as for the HD1917
starcms said:
Yes, you need the MSM tool for the HD1925. Don't use any other versions of it, such as for the HD1917
Click to expand...
Click to collapse
where did you fine the msm tool for Hd1925 I am searching high and low for it ?
Mitch0115 said:
where did you fine the msm tool for Hd1925 I am searching high and low for it ?
Click to expand...
Click to collapse
It's right here
[OP7TPRO TMO 5G][OOS 11.0.1.5 HD61CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com