Database Users

Downgrade P708g from JB to ICS?

So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance

Jstag said:
So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance
Click to expand...
Click to collapse
I did it with the same guide and I had the same problem while downgrading (Lparam 1002 Error on 4%).
Check out my solution HERE
If you are afraid of doing changes at the MIDDLE of the operation, wait for it to get stuck, tell you to restart and before restarting it do the same changes i am proposing.
Cheers,
Moul

Solution
Jstag said:
So i recently learned the L7 finally got the JB update. I decided to try it out, but i didn't like it overall.
So i have been trying to downgrade it, but no luck. I have been trying to use cmahendra's guide (http://forum.xda-developers.com/showthread.php?t=2085344), but this is meant for L9, and it keeps getting stuck on 4%, despite reinstalling drivers and following the trouble shooting on the guide.
Is there a way to downgrade to ICS, another guide maybe?
Thanks in advance
Click to expand...
Click to collapse
Here is the solution !!!...
http://www.taringa.net/posts/celula...-Jelly-Bean-a-ICS-LG-L7-P700---705---708.html

pemon said:
Here is the solution !!!...
http://www.taringa.net/posts/celula...-Jelly-Bean-a-ICS-LG-L7-P700---705---708.html
Click to expand...
Click to collapse
That's what he has been doing .... LG mobile update tool is using KDZ-Updater.exe to do this job. You should check on Update tool's folder. There you'll find KDZ Updater I've been doing that also, correctly doing the same steps as EVERY guide online about KDZ updater, but still had the same issue.
It seems though that LG has some issues on downgrading firmwares, and I posted my solution to this problem.
P.S.(For JStag) Be sure you have :
1. Installed drivers correctly
2. Disable LG Modem driver in Device Manager
3. Have USB debugging on IF you are doing this with phone turned-on. If not, better if you put battery off and enter Emergency Download Mode before starting it.
Cheers,
Moul

OK
moulwxtos said:
That's what he has been doing .... LG mobile update tool is using KDZ-Updater.exe to do this job. You should check on Update tool's folder. There you'll find KDZ Updater I've been doing that also, correctly doing the same steps as EVERY guide online about KDZ updater, but still had the same issue.
It seems though that LG has some issues on downgrading firmwares, and I posted my solution to this problem.
P.S.(For JStag) Be sure you have :
1. Installed drivers correctly
2. Disable LG Modem driver in Device Manager
3. Have USB debugging on IF you are doing this with phone turned-on. If not, better if you put battery off and enter Emergency Download Mode before starting it.
Cheers,
Moul
Click to expand...
Click to collapse
Well, the important thing here is the special for the downgrade KDZ compiled by Homer ... As you mention if you are flashing a regular KDZ throws errors ...
===========
ESPAÑOL
===========
Pues aquí lo importante es el KDZ especial para el downgrade compilado por Homero... Como tu mencionas si flasheas con un KDZ normal arroja errores...

Moto X / Droid UnBrick after OTA update

I was able to revive the phone that received the OTA and become bricks
It was also restored after downgrade firmware and receiving OTA
By clicking the link you will find various files
VERY IMPORTANT
Choose your model file and region, Otherwise, problems may occur
Always start with the lowest recovery bootloader
V30.70 -> V30.71 -> V30.B0 -> V30.B2 -> V30.B4 -> V30.B6 -> V30.B7 -> V30.B9 -> V30.BA -> V30.BC -> V30.BD -> V30.BE
some versions may not be due to the fact that the firmware is too old or did not go to the region
---------------
3 is located inside the archive folder
0_UnBrick << fastboot boot repair
1_Repair_Boot (RSD Lite) << recovery by RSD Lite GPT & BL
2_Flash_All_FW (RSD Lite) << copy the file to your Official firmware and flash by the RSD Lite
Click to expand...
Click to collapse
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
there is also a hybrid archives for those who pierced themselves 5.1 on a different model or region
eg XT*******_B7BE
they contain GPT with previous versions and new bottles V30.BE -it is very important for the owners of ATT & VZW
Please do not copy files to other file shares
the project is under constant development and refinement
Storage of files for restoration, please give the following links to it and not distribute the files
https://yadi.sk/d/Hz8MUEUThsp4f
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC

soon result in closed beta test
were tested
Moto XT1080M =firmware XT1058DE + OTA BLV30.BE -> Downgrade to XT1058BR 5.0+OTA = Brick restored to SU6-7
Moto XT1030 =firmware XT1058BR + OTA BLV30.BE -> Downgrade to XT1058BR 5.0+OTA = Brick restored to SU6-7
Moto XT1058 =firmware XT1058DE 5.1 + OTA BLV30.BE -> Downgrade to XT1058DE 5.0+OTA = Brick restored to stock
Moto XT1060DEV =firmware XT1052DE 5.1 + OTA BLV30.BE -> Downgrade to XT1060 4.4.4+OTA 212.163.3 = Brick restored to stock
Moto XT1058 Rogers 5.1 Bootloader 30.BE -> Downgrade to Stock 4.4.4 + OTA 212.144.12 = Brick restored to stock
for several days method will be finalized and available for use

Moto XT1060DEV =firmware XT1052DE 5.1 + OTA BLV30.BE -> Downgrade to XT1060 4.4.4+OTA 212.163.3 = Brick restored to stock
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
My guide is not complete without CrashXXL finding concerning 30.BE, but what can I do - he is the Master ))) All kudos go to CrashXXL!

XT 1058 Rogers 5.1 Bootloader 30.BE -> Downgrade to Stock 4.4.4 + OTA 212.144.12 = Hard Brick -> restored to stock
THANK YOU Crash!!!
Penny flew

Would be awesome to be able to downgrade lower than 4.4.4

jahrule said:
Would be awesome to be able to downgrade lower than 4.4.4
Click to expand...
Click to collapse
downgrade the firmware can not be due to aircraft parts
you are stitched motoboot above qFuse burns jumper, return it to the reverse position can not be

CrashXXL said:
downgrade the firmware can not be due to aircraft parts
you are stitched motoboot above qFuse burns jumper, return it to the reverse position can not be
Click to expand...
Click to collapse
Makes sense. Thanks again for your great work. You working on a system write protection disable you need help on let me know.

I tried to fix the Boot loop that always boot into bootloader ended up hard bricked my phone. any chance ? was on 5.1

Gigahyperprime1 said:
I tried to fix the Boot loop that always boot into bootloader ended up hard bricked my phone. any chance ? was on 5.1
Click to expand...
Click to collapse
Now the method is tested until restored 5 out of 5
also addressed the issue of its free or paid access

<3
CrashXXL said:
Now the method is tested until restored 5 out of 5
also addressed the issue of its free or paid access
Click to expand...
Click to collapse
Tks man, still waiting for it

UPD
all files

Not there yet
CrashXXL said:
UPD
all files
Click to expand...
Click to collapse
Thanks a lot for putting the time to make this work... did not have much luck yet. I still can't get to the fast boot screen - after shorting to make the com por appear I flash step 0 but the phone stays on emergency download mode. If I attempt to manually induce a fastboot (by pressing volume down and power) the phone drops the com port from windows but does not enter fast boot. After that I have to short the system to make the com port appear again.
Battery is charged (I think) as I can measure 4.2 V on the multimeter I have a XT1058BR if that matters. Any clues to what is going on ? Suggestions ?
Thanks!
M.

cneto100 said:
Thanks a lot for putting the time to make this work... did not have much luck yet. I still can't get to the fast boot screen - after shorting to make the com por appear I flash step 0 but the phone stays on emergency download mode. If I attempt to manually induce a fastboot (by pressing volume down and power) the phone drops the com port from windows but does not enter fast boot. After that I have to short the system to make the com port appear again.
Battery is charged (I think) as I can measure 4.2 V on the multimeter I have a XT1058BR if that matters. Any clues to what is going on ? Suggestions ?
Thanks!
M.
Click to expand...
Click to collapse
write what version of firmware you standing?
but rather let it link

CrashXXL said:
write what version of firmware you standing?
but rather let it link
Click to expand...
Click to collapse
I was on Blur_Version.222.21.7.ghost_row.Brasil.en.BR.zip then attempted an OTA for 222.21.15, got into a bootloop - attempted to go back to 222.21.7 with resulted in a bricked device. .15 is the final one for 5.1 in Brazil while .7 is the latest soak test (for 5.1).
While on .7 I think I still had a 4.4.4 bootloader as I installed that by flashing a capture removing the gpt.bin and motoboot.bin from the xml.
M.

cneto100 said:
I was on Blur_Version.222.21.7.ghost_row.Brasil.en.BR.zip then attempted an OTA for 222.21.15, got into a bootloop - attempted to go back to 222.21.7 with resulted in a bricked device. .15 is the final one for 5.1 in Brazil while .7 is the latest soak test (for 5.1).
While on .7 I think I still had a 4.4.4 bootloader as I installed that by flashing a capture removing the gpt.bin and motoboot.bin from the xml.
M.
Click to expand...
Click to collapse
Forgot to mention that when I try to reset the phone by pressing the volume + / - and power at the same time the phone green light blinks . Other then that , there is no sing of life coming from it. ..... I know the green light might mean low batt, but as I said before the voltage seems high enough.
M.

https://yadi.sk/d/Hz8MUEUThsp4f/MBM
first try this one MBM-NG-V30.B7.ZIP
if not start, this MBM-NG-V30.BE.ZIP
Then flash the stock using XML -> Flash_noBL.xml copy in stock Firmware

your down load links dont seam to work? i have numerous bricked boards i will try your method

thank you for the effort, im not native english spoken, my question is: this procedure and files can aply to an moto g hard bricked? since some time ago i read a post with files of a moto g wich flash in a moto x with success., thanks for the response and the work you do.

It worked!
first try this one MBM-NG-V30.B7.ZIP
if not start said:
CrashXXL you are the man! It worked!!!! Not at first, but it worked. I tried first to flash both B7 and BE files you posted w/o success. The system would not leave the emergency download mode and would not get to fast boot. Then for some random reason I decided to run the second step from s5610 tutorial
"Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat"
and then try to run the BL flash again and this time it worked ! Maybe you can explain me what happened.
In any case, once the system was on fastboot I did your step one and flashed gpt.bin and motorboat.bin . After that the system booted into android w/o any additional help . I will still flash a fresh system just in case.
Anyways, thanks really a lot for the help . I was already looking for used boards !
I actually need to thank S5610 for putting up his tutorial also.
Best for you all,
M.
Click to expand...
Click to collapse

xt1060 B7, i ran this command (qflash.exe -com7 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o) from the 0_ unbrick file and BAM fastboot! then from rsd lite i located (1_repair_boot (rsd lite)) and my once dead x now lives!
crashxxl all thanks to you!:good:

XT1562 Dual with qhusb - is it possible to unbrick?

Hi,
My Moto X Play XT1562 Dual had its bootloader unlocked, Teamwin installed, and rooted long time ago. It is at 6.0.1 something (I don't remember exactly, but it is 6.0.x).
Recently, I got messages about OTA update, and as it seemed not able to have OTA with rooted phone. So, yesterday I tried to make it clean. But I made a terrible mistake - I downloaded a zip file for Moto Droid Turbo, and flashed that zip file in Teamwin. I got some error messages (given by Teamwin) as a result. After that, I restarted the phone, and then since then, it could not come back.
Plugging in my laptop, and it is recognized as something like qhusb.
Following this link http://www.usoftsmartphone.com/t300062.html, I could install driver for that qhusb, to have it properly recognized as Qualcomm HS-USB QDLoader 9008. But running blankflash (qboot) provided in that link didn't help. The error message I got was "Unexpected packet: 4. Was expecting: 3 FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)".
Do I have any hope here?
Thank you very much for your time.

Averell said:
Hi,
My Moto X Play XT1562 Dual had its bootloader unlocked, Teamwin installed, and rooted long time ago. It is at 6.0.1 something (I don't remember exactly, but it is 6.0.x).
Recently, I got messages about OTA update, and as it seemed not able to have OTA with rooted phone. So, yesterday I tried to make it clean. But I made a terrible mistake - I downloaded a zip file for Moto Droid Turbo, and flashed that zip file in Teamwin. I got some error messages (given by Teamwin) as a result. After that, I restarted the phone, and then since then, it could not come back.
Plugging in my laptop, and it is recognized as something like qhusb.
Following this link http://www.usoftsmartphone.com/t300062.html, I could install driver for that qhusb, to have it properly recognized as Qualcomm HS-USB QDLoader 9008. But running blankflash (qboot) provided in that link didn't help. The error message I got was "Unexpected packet: 4. Was expecting: 3 FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)".
Do I have any hope here?
Thank you very much for your time.
Click to expand...
Click to collapse
if you can still boot with twrp try to flash a custom rom, if it doens't work you can still follow the thread to reflash stock MM

fablebreton said:
if you can still boot with twrp try to flash a custom rom, if it doens't work you can still follow the thread to reflash stock MM
Click to expand...
Click to collapse
The screen is pure black. No led as well.
I know no way to access to fastboot, so how can I reflash stock?
Thanks!

haev you solved your problem .. ?????????????????????

aamszia said:
haev you solved your problem .. ?????????????????????
Click to expand...
Click to collapse
No hope until now. Bricked as a brick

Use volume-up + power key.
Or else install the proper drivers and then use rsdlite to flash the latest stock rom

Its hard bricked. You'll need blank Flash files and qpst to recover from this and we still haven't got those files.

Hard brick solution [PROJECT] for moto x force(xt 1580)

I spent a lot of hours in Google after hard bricking my moto x force, but failed to find any reliable solution.pls help......
Actually I was using moto x force Of RETEU version. I had flashed the Mexican firmware in order to make it dual sim, and after that i flashed OTA update and that was my most stupid thing......after that phone has completely dead, only computer is detected as Qualcomm HS_USB 9008 in device manager.
Pls HELP ANYONE TO FIX IT.
Many many thanks in advance.
edit/update
I have managed the dump rom files from a working moto x force, that's called loader.img by the great help of some amazing and helpful Brazilian friends. So kindly request all the volunteers if they may build the necessary blank-flash file from this loader.img
Here the link for loader.img =>>
https://drive.google.com/file/d/1KC0nhQqE6XG2jkCrlkGcqkEuLVvxXeUt/view?usp=drivesdk

Nobody can, only Repair Center................. maybe
aditya.addi said:
I spent a lot of hours in Google after hard bricking my moto x force, but failed to find any reliable solution.pls help......
Actually I was using moto x force Of RETEU version. I had flashed the Mexican firmware in order to make it dual sim, and after that i flashed OTA update and that was my most stupid thing......after that phone has completely dead, only computer is detected as Qualcomm HS_USB 9008 in device manager.
Pls HELP ANYONE TO FIX IT.
Many many thanks in advance.
Click to expand...
Click to collapse

File request to fix moto x force (xt1580) to fix HARD brick.
Hi friends, I somehow hard bricked my moto x force (xt1580).
To fix it I just need a file called loader.img. that may be dump from a working moto x force using the following command
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
In fastboot mode.
Update!!!!
With a great help of some Brazilian friends,i have managed the above loader file.
But unable to create blank flash from it. So i request to all of you if you may create a blank flash file from it.here the link
https://drive.google.com/file/d/1KC0nhQqE6XG2jkCrlkGcqkEuLVvxXeUt/view?usp=drivesdk

aditya.addi said:
Hi friends, I somehow hard bricked my moto x force (xt1580).
To fix it I just need a file called loader.img. that may be dump from a working moto x force using the following command
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
In fastboot mode.
So if anyone may help then I would be highly thankful to him:
Click to expand...
Click to collapse
You should be able to flash from scratch. I bricked my previous XT1580 as well, but was able to get it back up and running (why I love Moto).
Restart in bootloader mode, and go through the flashing process. Use RETEU 5.1. This is the only stock ROM I've been able to reliably flash on the XT1580. Afterwards, you can OTA update to 6.0, install TWRP, then use TWRP to flash L!TE 7.0 ROM. This is the best ROM, bar none.
L!TE is the best option for 7.0 dual SIM functionality on all versions. On the XT1580, the second SIM will only work in 2G. Regardless of if this'll be useful to you (2G availability), this ROM is the best. Stock 7.0 slowed down my charging speed. This ROM boosted it back up to 9V/4A.
For the XT1581, best course of action action is to flash RETMXDS 6.0, flash TWRP, then flash L!TE, using TWRP.
Good luck, and let us know how it goes.

Restart in bootloader mode, and go through the flashing process. Use RETEU 5.1. This is the only stock ROM I've been able to reliably flash on the XT1580. Afterwards, you can OTA update to 6.0, install TWRP, then use TWRP to flash L!TE 7.0
Let you made remember bro my device get HARD bricked
So i am unable to boot into bootloader
Pls provide any other solutions

aditya.addi said:
Restart in bootloader mode, and go through the flashing process. Use RETEU 5.1. This is the only stock ROM I've been able to reliably flash on the XT1580. Afterwards, you can OTA update to 6.0, install TWRP, then use TWRP to flash L!TE 7.0
Let you made remember bro my device get HARD bricked
So i am unable to boot into bootloader
Pls provide any other solutions
Click to expand...
Click to collapse
Please describe what you mean by hard bricked in this instance. What shows up when you power on?
The bootloader screen should work even of the entire phone storage is wiped.
Are you able to get into TWRP?

guptapunjabi said:
Please describe what you mean by hard bricked in this instance. What shows up when you power on?
The bootloader screen should work even of the entire phone storage is wiped.
Are you able to get into TWRP?
Click to expand...
Click to collapse
It's a brick - same as mine one.
Once connected to the PC it shows qualcomm hs-usb qdloader 9008 in device manager.
It can't boot to the bootloader

TeddyBeers said:
It's a brick - same as mine one.
Once connected to the PC it shows qualcomm hs-usb qdloader 9008 in device manager.
It can't boot to the bootloader
Click to expand...
Click to collapse
I completely misunderstood, gentlemen. If this is the case, it is a cluster of a problem that's beyond my knowledge.
Hopefully, someone else may be able to give suggestions.

i have some files (blankflash) for xt1580 x force msm8994....
if someone is interested please pm me or write me on telegram @Francko76

Telegran
Cual es su telegram así lo contacto?

please friends help for the XT1580
---------- Post added at 06:27 PM ---------- Previous post was at 06:23 PM ----------
QTeknology said:
i have some files (blankflash) for xt1580 x force msm8994....
if someone is interested please pm me or write me on telegram @Francko76
Click to expand...
Click to collapse
friend can you help me with the files to make tests ami mail [email protected]
I need help

Help!!
QTeknology said:
i have some files (blankflash) for xt1580 x force msm8994....
if someone is interested please pm me or write me on telegram @Francko76
Click to expand...
Click to collapse
Help me I'm also with Hard brick prpblemas in my Moto X force 1580 ... you could send Flash Blank to my email ... please [email protected] :chorando: :chorando:

Hard Brick Solution
Hi bro
My moto x force is Dead.
and after connect to pc show qualcom......
i search all of content in site but not found any things
Please help me & other moto lovers to re enable my device

Le Pro 3 x722: soft brick and bootloader blocked

Hello xda!
I've inherited an x722 Le Pro 3, which is soft-bricked..basically works only the fastboot.
My problem is that the bootloader is locked.
So any operation related to the recovery fails with the errors:
Code:
FAILED (remote: Critical partition flashing is not allowed)
or:
Code:
FAILED (remote: oem unlock is not allowed)
Code:
# fastboot oem device-info
...
(bootloader) Device product name: [le_zl0_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
(bootloader) is_allow_unlock: 0
OKAY [ 0.110s]
finished. total time: 0.110s
I've tried the various Batyan rom, but everything fails because the bootloader is locked, and i cannot unlock it.
Do you have any hint on how to proceed in this case?
Thanks for your support!
.: Francesco

I'm guessing you took ota and you flash it with twrp.
Sorry to say their is no solution for 722 at this time.
I would check out 722 thread.

I wish the person who owned that x722 came here and read the sticky in this very sub-forum before attempting anything. I made that sticky to prevent x722 owners from bricking their devices. I see it's not working.
but everything fails because the bootloader is locked
Click to expand...
Click to collapse
Yes. The bootloader is now permanently locked. I have idea what was flashed on that phone, probably stock 26s, which includes a stock recovery that not just replaces TWRP, but perma-locks the bootloader. Why LeEco chose to do that, IDK. All I know is, F.J.V, a developer who has taken interest in this issue, has tried a number of fixes to no avail. There's still no solution. F.J.V surmises that it's either a QFIL issue (there's no QFIL for this device and the x720's QFIL doesn't work), or it's something else entirely. You should check out the unbrick thread in the x722 Development forum to see what others have done so far.

Here is a problem if bootoader is locked fashboot will not work.
Sent from my SM-A730F using xda premium

tony770101 said:
It your phone turn on ,please follow the link to bootloader unlock,and you will don't afair brick your phone, link at here...............Mod Edit: removed prohibited external link
Click to expand...
Click to collapse
Prove that it works with a video showing it. I see you're forcing people to pay to download that software. Smells like a scam. If you didn't make it, don't charge people for it. That's just awful.
How did you get a QFIL file or perma-unlock for the x722? Some Chinese forum? Or did you put it together yourself? And does it work without fastboot, as mchlbenner mentioned?

sk8223 said:
Prove that it works with a video showing it. I see you're forcing people to pay to download that software. Smells like a scam. If you didn't make it, don't charge people for it. That's just awful.
How did you get a QFIL file or perma-unlock for the x722? Some Chinese forum? Or did you put it together yourself? And does it work without fastboot, as mchlbenner mentioned?[/QUOTE
I said if your phone work at want update to 26s and unlock bootloader,it will not brick your phone.if your phone ota offical to lock oem,the phone easy to brick. Qfil file loking forward.
Click to expand...
Click to collapse

tony770101 said:
I said if your phone work at want update to 26s and unlock bootloader,it will not brick your phone.if your phone ota offical to lock oem,the phone easy to brick. Qfil file loking forward.
Click to expand...
Click to collapse
Yeah. I'm just curious as to why the poster of that link is charging people for access to those unlock tools. That's a little strange. Anyway, that QFIL ROM is for the x720 only, really, but it's applicable to the x727 since they're pretty much the same model. Won't work for the x722 because it has different hardware.
The phone only bricks if you flash update.zip through TWRP. I'm sure it'll probably brick if you try to flash even the 20D zip file through TWRP too. The only eUI ROMs that are safe to flash are the vendor ROMs. The rest require the stock recovery.

sk8223 said:
Yeah. I'm just curious as to why you're charging people for access to those unlock tools. Did you compile them yourself?
Click to expand...
Click to collapse
Yes, our engieer modified the firmware and unlock them.

tony770101 said:
Yes, our engieer modified the firmware and unlock them.
Click to expand...
Click to collapse
...what? Who are you associated with?

[/COLOR]
sk8223 said:
...what? Who are you associated with?
Click to expand...
Click to collapse
Looking forward the x722 qfil firmware ,i think unbrick the phone soon.

tony770101 said:
Yes, our engieer modified the firmware and unlock them.
Click to expand...
Click to collapse
The firmware can unlock everything you want, but you can not unlock the terminal.
This is a deception.

Can't push the stock ROM into phone as update.zip then flash stock recovery and there flash the ROM?

First thing this is a pure scam!!
Also you are not allowed to post links that cost money!!!!
Sent from my SM-A730F using xda premium

marik1 said:
Can't push the stock ROM into phone as update.zip then flash stock recovery and there flash the ROM?
Click to expand...
Click to collapse
If there's no fastboot then the phone is stuck in Qualcomm 9008 mode which requires QFIL (probably) to fix. The x720's QFIL doesn't work for the x722, and there's no QFIL for the x722 yet.
But you're right, if there's fastboot access you should be able to do those things. OP should be able to restore the phone with those Chinese soft brick files that restore 26s for the LeEco 72X series. (no need for QFIL, AFAIK). I deleted my LeEco folder filled with tools recently (since I'm selling mine) so I don't know the file names.

marik1 said:
Can't push the stock ROM into phone as update.zip then flash stock recovery and there flash the ROM?
Click to expand...
Click to collapse
It can not.
With blocked bootloader you can not update the stock recovery, or anything, even if you can enter fastboot.
Greetings.

?
how tot unbrick leeco x722 zl1 , i set qualkoom 9008 and i dint file for qfil , howww to unbrick?(

Their is no unbrick for722.
Sent from my SM-A730F using xda premium

FurymdLuka said:
how tot unbrick leeco x722 zl1 , i set qualkoom 9008 and i dint file for qfil , howww to unbrick?(
Click to expand...
Click to collapse
Only wait for x722 qfil

tony770101 said:
It your phone turn on ,please follow the link to bootloader unlock,and you will don't afair brick your phone, link at here.............Mod Edit: removed prohibited external link..................
Click to expand...
Click to collapse
Are you also known as " zhong_ft" ?
Because You just directed him to a "donation" paid solution for the X720 that solution will not work for the X722. The guy in that link is taking peoples money claiming on several websites that he can unbrick the X720 when he cannot. Its a scam period!
---------- Post added at 02:56 AM ---------- Previous post was at 02:29 AM ----------
sk8223 said:
Yeah. I'm just curious as to why the poster of that link is charging people for access to those unlock tools. That's a little strange. Anyway, that QFIL ROM is for the x720 only, really, but it's applicable to the x727 since they're pretty much the same model. Won't work for the x722 because it has different hardware.
The phone only bricks if you flash update.zip through TWRP. I'm sure it'll probably brick if you try to flash even the 20D zip file through TWRP too. The only eUI ROMs that are safe to flash are the vendor ROMs. The rest require the stock recovery.
Click to expand...
Click to collapse
Yes, as you mentioned: the poster is charging people for access to to unlocking tools that are free all throughout the internet and if If you read the comments you will not see one comment where they say it works. But there are several that say it did not work.
His rating is deceiving because the guy also posted solutions for other phones.
---------- Post added at 03:26 AM ---------- Previous post was at 02:56 AM ----------
tony770101 said:
If you need the firmware,you can pm me,i can send it to you,lol
---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------
If you phone can not entry os,you can not push anything to phone,only wait for qfil firmware.
Click to expand...
Click to collapse
Okay if your firmware can fix a bricked X722, then prove it by donating a time sensitive solution to one of the many people that have a bricked X722. If proven legit then you will have my apologies. Regardless, you are breaking rules 6, 7 and 8 of the XDA Forum Rules.
I seriously doubt that you can provide this proof unless you worked for Leeco Development and somehow managed to gain access to the tools to unlock the encrypted bootloader signatures. Tools now owned by Leshi.
BTW, I have worked for a manufacturer that developed encrypting and decrypting software, and it's not easy to create a hack on recent encryption methods. The bootloader locking encryption is there to keep unauthorized reprogramming/reconfiguring of the system and it would be extremely difficult to break enabled encryption without the inside Leeco tools which that at this point as far as I know have not been released.
BTW, I noticed that you have posted the same claim for many phones all throughout XDA, and that's interesting!
Reported!

what he said just above me I'm glad he report you scammers are bottom feeders!
Sent from my SM-A730F using xda premium