Database Users

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:

[GUIDE] [FIX] YUREKA (AO5510) Touchscreen Calibration Issue

​
Hurray! Finally, I fix the touch calibration issue; many many thanks to God who showed me the right path.
After suffering hard in last 15 days, even not getting any help from YU Officials, finally God bestowed upon me his blessings and provided me the hint to fix the issue.
What caused the Issue?
YU Televentures recently released a new batch of Yureka Plus (YU5510A-LP) devices with VoLTE feature. This created a storm in Yureka /Plus section of the forum. Some users even bricked after flashing the new firmware since it was totally different from the previous Yureka firmware. I got the backup of /system and /boot from a YU5510A-LP user. I deodexed the files and made a ROM out of it and flashed on my device to test whether it boots or not (a common process of ROM porting). It didn’t boot but it went beyond the boot logo and since the Kernel of YU5510-A didn’t have the correct display drivers for AO5510, I was getting strange characters on the screen. After that I rebooted to TWRP recovery. I was shocked the touch was malfunctioning. If I touch up it was working down, it was totally a mess.
This issue is much dangerous than bricking the device. Even if we brick, we may recover it by following @ricks guide, but with malfunctioning touchscreen phone is utterly useless. It can’t be fixed even after flashing the EMMC backup.
After that I reported to the YU Officials about the touch calibration issue, they didn’t provide any fix, but created a Warning thread regarding it. So sad.
They were even not ready to provide me the touch firmware of Yureka AO5510. They told me that they are also trying to find the cause of touch calibration issue and don’t have the required files. Here is the quote of the reply from YU Officials:
I am afraid that we don't have any files for fixing the issue. To make sure that such thing does not happen we internally test every case before releasing the software. In your case, you got the software from unknown sources and flashed it on your device with your own consent and understanding. Yes, we have devs but they work on cases which have higher reproducibility rate like the proximity sensor issue.
Click to expand...
Click to collapse
After that I analysed the YU5510A-LP VoLTE firmware and found that it was created by Coolpad, a Chinese Smartphone Company. So YU Televentures has imported not only the smartphone (YU5510A-LP) but also the firmware from Coolpad. That’s why it has some unknown bugs which the YU Offical Devs don’t know because they haven’t made the firmware. That’s why the devs didn’t have fix for touch calibration issue. YU is spending very less on service and devs, which very much disappointing. YU, an Indian brand made Yureka for tech freaks and that’s why so many devs engaged in it and even some noobish users like me became devs to raise the company above cheap Chinese brands. But now it’s status is deteriorating, it broke its partnership with Cyanogen and lost the support of so many great devs; and now it is left with some official noobish devs who are taking time like hell to provide a VoLTE patch for other users, this shows how irresponsible is the YU Company. And now it has already been provided by a YU Forum user. Even the Official YU OS is provided by our friend dev @AudioGod.
I hope my above words reaches to the YU Company and they take this criticizing in the right way and improve itself. I want to see this Indian Company rise beyond heights.
After lot of analysis and research I found that the cause of touch calibration issue was the kernel of YU5510A-LP ROM. It changed the TP-Firmware version and touch parameters of Yureka AO5510 (HD) according to Yureka YU5510A-LP (FHD) device and messed up the calibration.
This TP firmware is different in Yureka and Yureka Plus and it never changes after flashing any firmware (fastboot or ROM).
Yureka AO5510 : Each:GT970:0x1039:0x46
Yureka Plus YU5510 : Ofilm:GT970:0x1039:0x48
And mine was : Each:GT970:0x1039:0x47
Yureka (Plus) Touch Panel is manufactured by Goodix, a Chinese Touch Panel and Fingerprint Sensor company.
What didn’t fix the issue?
These are the things which didn't fix the calibration issue:
[/SIZE]
Flashing stock COS 12.1 ROM through recovery
Flashing COS 12.0/12.1 fastboot firmware
Flashing COS 12.0 CPB using YGDP tool (which threw an error of incompatible device before flashing)
Flashing all other partitons (=EMMC backup)
Using Annabathina’s Yureka Unbricking Tool
How did I find a Fix?
While surfing through internet I found a way to check the touch firmware version. Then I checked mine and also asked about it from other Yureka users. Then I searched about the firmware version and got an XDA Thread and also got to know about Goodix Touch Firmware and Goodix Firmware Upgrade Tool (GTP ADB Tool) from Elephone (another Chinese company) forum which I didn’t get from YU.
I read the XDA thread learned about the whole thing and created a Goodix TP Firmware/Config myself.
How to Fix Yureka AO5510 Touch Calibration Issue?
STEP 1: Download GtpAdbToolV1.7_20140424.zip and GT970_1039_AO5510-TP-Firmware.zip on your Windows PC and extract it. Go to the extracted folder of Gtp Adb Tool and run the GtpAdbTool.exe application. Then connect you YUREKA AO5510 to your PC (be sure USB debugging is enabled in your device). You will see the GTP ADB Tool window similar to the screenshot below:
​
STEP 2: Now click on the button as indicated in the screenshot below and navigate for the GT970_1039_AO5510-TP-Firmware.cfg file (that you extracted in Step 1) and select it.
​
STEP 3: Then click on the button indicated in the screenshot below to execute firmware upgrade process. Once completed, you can unplug your device and reboot. Voila touchscreen issue fixed!
​
NOTE (Important):
If the GTP ADB Tool doesn't detect your device or TP firmware, then flash any of the following ROMs:
Official Lineage OS ROMs
Hexagon ROM by @MoreSushant48
Or any other ROM
OR
Go to TWRP Recovery and mount all the partitions. Then connect your phone to the PC. It should detect.
If any of the above methods doesn’t work then try flashing
CoolUI 6.0 for YUREKA (Test build): https://www.androidfilehost.com/?fid=457095661767103935
(After flashing this ROM you may see a 'root' indication on YU LOGO, but you can fix that using Annabathina's Tool)
Important Files
GTP ADB Tool: https://www.androidfilehost.com/?fid=385035244224387037
YUREKA AO5510 TP Firmware: https://www.androidfilehost.com/?fid=385035244224387256
More information: https://www.osbusters.net/2016/10/fix-yureka-ao5510-touch-calibration-issue.html
Credits
Special thanks to @iamreal2 (XDA member) and @Ethan (Elephone forum member)
Special thanks to @darshan1205, @ricks and @Men_in_black007 who supported me in bad times
Special thanks to @manis99 for providing me YU5510A-LP VoLTE Firmware
Special thanks to @prasoon Mehra for providing me original Yureka AO5510 TP Config.
And finally thanks to me for making this fix.

Original TP Firmware Files for Different Devices
These are Original Stock Touch Panel Firmware/Configs for users who are suffering calibration issue not due to VoLTE firmware but due to other unknown causes.
YUREKA (AO5510) : https://www.androidfilehost.com/?fid=457095661767104421 (Thanks to @Prasoon Mehra)
YUREKA PLUS (YU5510) : https://www.androidfilehost.com/?fid=385035244224388338 (Thanks to @darshan1205)
Users of other YU Devices may share their working TP Firmware to help others....
Mirror Links
https://mega.nz/folder/Z4ckFbDA#bw4HnjUntLbiOLcdT-qpLQ (MEGA)

[Guide] How to Backup or Edit Touchscreen Firmware using GTP ADB Tool (For all devices with Goodix touchscreen)​For users of all devices. Backing up the current TP-firmware is useful for saving the device from any future accident.
STEP 1: Download GTP-ADB-Tool Zip on your Windows PC and extract it. Go to the extracted folder and run the GtpAdbTool.exe application. Then connect your smartphone to your PC (be sure USB debugging is enabled in your device). You will see the Gtp Adb Tool window similar to the screenshot below:
STEP 2: Now click on the Menu item as indicated in the screenshot below:
STEP 3: Now you will see a window similar to the screenshot below. Click on the indicated button to read the current TP configuration from your connected device.
STEP 4: Hereafter you will see a window similar to the screenshot below. Take a screenshot of your current window and click on the button indicated to export your current config. Save the resultant config file to your preferred place. Thereafter, if required, you can also edit the firmware by playing with the Hex values.
STEP 5: Upload the Screenshot and your exported config file and save it in a safe place. That's it.

Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.

shailesh1985 said:
Hello nitesh9,
I am also having the same issue and tried above steps.
My phone is not getting detected. in the GTP tool. My Phone is rooted and running STOCK ROM..
it is getting connected in stock rom and GTP tool recognize it in ADB mode but not detecting TP chipset and IC version.
as you instructed , I downloaded nuclearom and tried to install it via CWM_recovery but installation is getting aborted showing error "System7".
ANY OTHER IDEA TO GET THIS DETECTED. PLZ HELP.. ALSO , I REALLY APPRECIATE YOUR EFFORT SHARING THIS KNOWLEDGEBASE.
Click to expand...
Click to collapse
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.

shailesh1985 said:
Many Thanks to all of you guys.... who have put their efforts a lot.
finally I succeed to repair touch for Yureka. but in little bit different way.
GTP tool was not working in both the custom ROM mentioned above. hence I started in recovery mode and mounted everything, immediately it detected the TP IC and its version and then I flashed the config. and... its done.
Click to expand...
Click to collapse
I am glad that it worked for you...
BTW you better use TWRP Recovery to flash newer ROMs. CWM Recovery is very old and is abandoned and deprecated.

Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.

dhrtlockeroo9 said:
Hello Sir, does it works with Yureka plus device also? My devices half touch only works after updating to lollipop. Please help me. I can't use my device. Thanks in Advance, please reply as soon as possible.
Click to expand...
Click to collapse
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk

nitesh9
nitesh9 said:
Added Yureka Plus TP firmware to the second post...Use that.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.

dhrtlockeroo9 said:
Can I flash this file via fastboot I can't use my device to enable USB debugging mode because of touch malfunctioning. Please suggest me any other way to flash file sir & Thanks a lot for helping me Sir.
Click to expand...
Click to collapse
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk

Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?

dhrtlockeroo9 said:
Sorry Sir, every time when while I tried to install TWRP is stuck always & once I succeeded but Touch not works for me I don't know why? Downloaded my own device 5510A TWRP but than also it's not responding like that. Can you tell me whole process to flash TWRP with TWRP IMG file for my Yureka plus device?
Click to expand...
Click to collapse
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk

nitesh9
nitesh9 said:
Are you able to go into TWRP recovery?
If yes then mount all the partitions and then try the method.
You can also use mouse on OTG to use the phone.
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
nitesh9 said:
Flash twrp through fastboot. Or use Yuware: https://drive.google.com/file/d/0B4X6UMHVd-NKTDQxdTBqaHlLb2M/view?usp=sharing
Sent from my YUREKA using Tapatalk
Click to expand...
Click to collapse
Tried but TWRP touch also malfunctioning. I can't use it properly. ???

dhrtlockeroo9 said:
Tried but TWRP touch also malfunctioning. I can't use it properly. ???
Click to expand...
Click to collapse
Tried using OTG mouse?[emoji15]

nitesh9 said:
Tried using OTG mouse?[emoji15]
Click to expand...
Click to collapse
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.

dhrtlockeroo9 said:
iS it possible if I flashed wrong firmware than also touch malfunctioning? But I flashed CM 12.1 official ROM.
Click to expand...
Click to collapse
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk

nitesh9 said:
What is your device...Wrong may cause the issue... Fastboot error also may cause the issue. It can also be a hardware issue...
If the given method doesn't help then it must be a hardware issue. You must contact YU Service / Care.
Sent from my YU5510A using Tapatalk
Click to expand...
Click to collapse
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.

dhrtlockeroo9 said:
I Have Yureka plus 5510A device. I don't know what happed my device again hard bricked. I don't know how to recover back. I tried QFil fastboot recovery but always getting error Sahara download failed.
Click to expand...
Click to collapse
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?

nitesh9 said:
Have you Yureka Plus Stock LP Edition with VoLTE and you are trying to flash CM in it?
Click to expand...
Click to collapse
No it's KitKat version.

dhrtlockeroo9 said:
No it's KitKat version.
Click to expand...
Click to collapse
Still you are getting bricked now and then?
What are you flashing actually?

Need Nandroid backup of Moto E3 or system.img

I accidentally flashed wrog system.img in my Moto E3. Now I can only access twrp recovery and nothing else. So I request other rooted Moto E3 holders to upload a fresh Nandroid backup from their devices or if you have the correct system.img of Moto XT1706 then please upload it or share its link.

http://www.mediafire.com/file/f0o0ox...160905_ROW.zip

Can Someone Help Me?
Can Some One Please Help Me? I Need The Same System.img but for XT1700 Model Please If SomeOne Can Share It.

@vishalonxda I found this link while searching for same. My browser reported connection unsafe but I proceeded further and file started downloading. You can try and let us know if it works or not
https://firmware.center/firmware/Motorola/Moto E3 Power (Lenovo XT1706)/Stock/
Edit: Sorry I thought your device was E3 power don't download this.

sfreddy15 said:
Can Some One Please Help Me? I Need The Same System.img but for XT1700 Model Please If SomeOne Can Share It.
Click to expand...
Click to collapse
Download the XT1706 one, because every website that has XT1700 firmware on it requires a premium membership or a fee.
I'm using XT1706 firmware on my XT1700 and I can confirm it runs fine with no issues.
The only difference is now as the XT1706 is a dual SIM model, and the XT1700 is single SIM, you will have a second SIM showing in your settings that is blanked out.
I wrongly assumed the XT1706 ROM wouldn't work on a XT1700 but the third party device repairer acting on behalf of Motorola reflashed my XT1700 with XT1706 firmware after a failed OTA update.
I can confirm it does work fine with no issues what so ever.
I can also tell you the repairer downloaded the file that is linked in this very thread and flashed it.
I would not recommend doing this yourself, my dad is a senior XDA member and he wasn't sure this would work, but when your device is left in the hands of a professional, you just have to trust them I suppose.....
If you take this route, and I'm not telling you to, im just suggesting it, you need to download and extract the rom file and place the extracted file in the TWRP backup folder and flash that via twrp.
This is what was done to my device.
I know some people are going to doubt what has happened to me, but I have no reason to tell any lies, Motorola offered me a brand new E3 but I chose to have mine repaired as it's only a few weeks old.
The XT1706 E3 power is not available in Europe or the UK, and I can confirm using the Powers firmware in the UK I have no service issues and 4g connection is working perfectly for me.
I have the downloaded and extracted TWRP backup XT1706 file if you want it.
Good luck.
Hope you get sorted ?

Thanks friend I did what you suggested and it worked I used a backup of twrp and restored system from tx1706 backup and phone is running fine I appreciate your help I was crazy trying to look the xt1700 backup

sfreddy15 said:
Thanks friend I did what you suggested and it worked I used a backup of twrp and restored system from tx1706 backup and phone is running fine I appreciate your help I was crazy trying to look the xt1700 backup
Click to expand...
Click to collapse
No problem.
Glad I could help you ?

Can anyone please upload the whole stock rom twrp backup? My imei is gone n shoes as invalid imei. Please include nvram n all the other partitions.

Actually i want moto e3 power nvram.bin file as i got the error "nvram warning=0x10" so to fix it can anyone original moto user send me the file of it
Thanks for advance
bubba1601 said:
No problem.
Glad I could help ....
Click to expand...
Click to collapse

also can anyone send me the file in the link if anyone has purchased and downloaded from this "https://firmware.gem-flash.com/index.php?a=downloads&b=file&id=82943" please please anyone
thanks in advance

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.

Need blank flash for my moto g4 play

Hi guys ! I hope you'll be able to help me.
i restored my Moto G4 play to 6.0.1
Then, i updated it to 6.0.1 and after it installed the phone is no longer powering up, even plugged in USB. My computer is recognizing it as QHSUSB_bulk.
I installed a driver for it to ne recognized as a qualcomm com port.
I know that my bootloader is broken so i need a blank flash image to "reinstall" it
Can someone in this forum help me ?
My model is XT1603.
Thanks in advance !

please be aware that the partitions the op is requesting contain personal, sensitive data, like your google password, and imei, which can not be deleted with a standard recovery wipe. It is not recommended anyone who does no understand what information any partition backup contains, refrain from responding, for your own protection. with the collective partitions the op is requesting, they can have a 100% duplicate of your device, including your personal information.

You and developer if and it does not seem what I am losing is not files containing personal data to before answering question search first what is hardbrick

The file that I am requesting the file and the file of the motorola that released for moto g1 and the one to recover cell from the hardbrick

i fixed my xt1601 with this file
i am trying to post a link
blob:https:// mega.nz/ afae4b98 -8c17 -4f33 -8c3e -d334855e7dfa
i have tried lots of blank flashes and this one worked for my XT1601
remove all the spaces from link

jmak2008 said:
i am trying to post a link
blob:https:// mega.nz/ afae4b98 -8c17 -4f33 -8c3e -d334855e7dfa
i have tried lots of blank flashes and this one worked for my XT1601
remove all the spaces from link
Click to expand...
Click to collapse
do you have the blankflash ?, the link is not working