[Bootloader Tool] MotoFlasher - Moto X Original Android Development

[Bootloader Tool] MotoFlasher - Moto X Original Android Development

MotoFlasher Bootloader Tool!
{
"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"
}
Why use MotoFlasher?
When Motorola Make the firsts android phones, RDSLite flash all the stuff that make your phone work but now, RDSLite only works like fastboot or directly dont work on some devices.
So, if you want to flash your bootloader, you can use MotoFlasher, that simplifies the process.
Disclaimer
Bootloader Flashing is ONLY for phones that don't boot or don't pass the fastboot, don't use if your phone works.
Features
Easy Flashing With binary files included that simplifies the process.
Support Multiples Devices.
Automatic Process, With Minimal User Interaction.
Over 1K of LineCodes that protect your phone from malfunction/ bad use of qboot/qflash tool.
You Will Find Update Info, New Things and Download on my website
MotoFlasher Website
Issue Tracker (Support)

HOW TO/ FAQ/ Request
How To: Repairing a Moto Bootloader
First, Install the Special Driver (See Below).
Check your phone (on Device Manager), it shows like "Qualcomm HS-USB QDloader 9***".
Open MotoFlasher, select your device and your last android version, detect and Flash...
You Will see the fastboot screen on your device (if everything works great).
Flash the Partition Table, and Full Bootloader Again (See Below).
How to: See if I can use MotoFlasher for repair my phone:
If your device don't turn on, follow this steps:
Plug in your device and check Device Manager:
If the driver isn't installed, the device show like "qusb_bulk" or any that start like "qusb_...."
If the driver is installed, the device show like "Qualcomm HS-USB QDloader 9***".
Install the Driver
Now from 1.7.1.1 the driver is installed automatically, and you can manage on "Driver Installer" app. You didn't need to override signing anymore
TroubleShooting:
a. It hangs on:
Code:
greeting device for command mode
or
Code:
opening device: \\.\COM**
Just mantain power button until the program start working...
b. Error:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
or:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
your MBM-CI dont match with your bootloader version, use another MBM-CI version.
c. Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
d. Fastboot Error:
Code:
preflash validation failed
Try your original (or last flashed) firmware

Reserved ??
Sent from my XT1053 using XDA Premium 4 mobile app

Boss442 said:
Reserved for FAQ and step by step guide
Click to expand...
Click to collapse
What is this tool for exactly??

Gundabolu SC said:
What is this tool for exactly??
Click to expand...
Click to collapse
If your phone Die and wont turn on again, you will need this tool.
This Reflash the whole bootloader

I hope I never need this tool. However, thank you very much for this! I am sure this tool will save some users if they get into big trouble.

This tool works even whit the mismatch partition error???

conquesoextra said:
This tool works even whit the mismatch partition error???
Click to expand...
Click to collapse
This tool won't work if the bootloader is working, you will need to flash something that break it (on moto g aboot or tz partitions)

I will be the first to ask what is probably an insanely stupid question... Would this work for flashing back to previous android versions on an updated phone?

Fadelight said:
I will be the first to ask what is probably an insanely stupid question... Would this work for flashing back to previous android versions on an updated phone?
Click to expand...
Click to collapse
No, only works if "emergency flashing" is running, and only run if the bootloader is broken

Even if the bootloader is broken intentionally, it is still not possible to downgrade from what I've read. 4.4.4 is locked tight, well done Google.
Sent from my iPad using Tapatalk

Johnny Wong said:
Even if the bootloader is broken intentionally, it is still not possible to downgrade from what I've read. 4.4.4 is locked tight, well done Google.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I think that is issue of motorola, google don't do the bootloaders and afaik, if you flash only system & boot, you can downgrade without downgrading the bootloader

Boss442 said:
I think that is issue of motorola, google don't do the bootloaders and afaik, if you flash only system & boot, you can downgrade without downgrading the bootloader
Click to expand...
Click to collapse
I meant Google locked down 4.4.4 so tight that nobody has been able to root it. If we could root 4.4.4, we would all have unlocked bootloaders thanks to Sunshine. I would expect a phone running 4.4.4 to bootloop in the best case scenario if you flash 4.4.2 system and boot files only, most likely soft brick. Which is why everyone is saying it is impossible to downgrade.

Johnny Wong said:
I meant Google locked down 4.4.4 so tight that nobody has been able to root it. If we could root 4.4.4, we would all have unlocked bootloaders thanks to Sunshine. I would expect a phone running 4.4.4 to bootloop in the best case scenario if you flash 4.4.2 system and boot files only, most likely soft brick. Which is why everyone is saying it is impossible to downgrade.
Click to expand...
Click to collapse
So, google is bad for repair an insecure issue? if you want to root, unlock the bootloader, if you can't unlock the bootloader, buy a phone capable of unlock the bootloader, or found a exploit.
Moto G with 4.4.4: Unlocked BL & Root.
PS: This tool is for people that had a bad downgrading, you can downgrade from 5.0 but only if you know how to downgrade

How did I imply that Google was bad for patching up security issues? "Well done" means good job. The only reason I posted is to save people the trouble of trying to downgrade in order to achieve root so they can unlock boot loader. Not going to happen. I'm typing this post on a Moto X Developer Edition so spare me the lecture about buying a phone that can unlock boot loader. Lol
P.s. what is the boot loader version on 5.0? Most custom Roms out now doesn't even touch the boot loader partition so not sure what you are talking about when you said you can downgrade from 5.0 back down to 4.4.4. Of course you can if you didn't flash motoboot and gpt. I used to run 4.4.4 on my Droid Maxx with 4.4 boot loader (30.B4 I think) and with that setup I could downgrade back down to 4.4. But if I flash the motoboot and gpt from 4.4.4 then I can only downgrade to 4.4.4. Make sense?
Boss442 said:
So, google is bad for repair an insecure issue? if you want to root, unlock the bootloader, if you can't unlock the bootloader, buy a phone capable of unlock the bootloader, or found a exploit.
Moto G with 4.4.4: Unlocked BL & Root.
PS: This tool is for people that had a bad downgrading, you can downgrade from 5.0 but only if you know how to downgrade
Click to expand...
Click to collapse

Johnny Wong said:
How did I imply that Google was bad for patching up security issues? "Well done" means good job. The only reason I posted is to save people the trouble of trying to downgrade in order to achieve root so they can unlock boot loader. Not going to happen. I'm typing this post on a Moto X Developer Edition so spare me the lecture about buying a phone that can unlock boot loader. Lol
P.s. what is the boot loader version on 5.0? Most custom Roms out now doesn't even touch the boot loader partition so not sure what you are talking about when you said you can downgrade from 5.0 back down to 4.4.4. Of course you can if you didn't flash motoboot and gpt. I used to run 4.4.4 on my Droid Maxx with 4.4 boot loader (30.B4 I think) and with that setup I could downgrade back down to 4.4. But if I flash the motoboot and gpt from 4.4.4 then I can only downgrade to 4.4.4. Make sense?
Click to expand...
Click to collapse
If you flash 4.4.4, you can downgrade to 4.4.3 or 4.4 flashing all exept the bootloader.
The thread isn't about downgrading, so, please, stop offtopic here
PS: the custom roms don't touch the bootloader, the only problem in 5.0 is when you flash the OTA, the zip updates the bootloader, and you can't go back the bootloader.

Boss442 said:
If you flash 4.4.4, you can downgrade to 4.4.3 or 4.4 flashing all exept the bootloader.
The thread isn't about downgrading, so, please, stop offtopic here
PS: the custom roms don't touch the bootloader, the only problem in 5.0 is when you flash the OTA, the zip updates the bootloader, and you can't go back the bootloader.
Click to expand...
Click to collapse
My original reply was to Fadelight when he asked if he could downgrade with this tool. The answer is still, NO!
I didn't realize that the lollipop OTA is out for the xt1060, oh wait, its not. So only custom Roms are available and relevant to the discussion. It would be a bad idea to take an ota without undoing all the modified stuff first. Using your example, if the boot loader is mismatched with the system, 4.4.4 boot loader and 4.4 system and you try to take an ota, it would end in failure. If you are lucky, the ota will not install, if you're not, it'll install and on reboot you have a nice brick.
The point is, most doesn't have this info and I'm trying to save them from having to do the research or the time they spend using this tool to undo their mess.
Your reply with the lecture summed it up best. Get a DE or Pure or Nexus if you want to have UBL & root. Or else, just wait till somebody comes out with an exploit. But as of now, don't waste your time. You'll know when an exploit is available long before it is released due to the amount of traffic it will receive. Sunshine for example.

Johnny Wong said:
My original reply was to Fadelight when he asked if he could downgrade with this tool. The answer is still, NO!
I didn't realize that the lollipop OTA is out for the xt1060, oh wait, its not. So only custom Roms are available and relevant to the discussion. It would be a bad idea to take an ota without undoing all the modified stuff first. Using your example, if the boot loader is mismatched with the system, 4.4.4 boot loader and 4.4 system and you try to take an ota, it would end in failure. If you are lucky, the ota will not install, if you're not, it'll install and on reboot you have a nice brick.
The point is, most doesn't have this info and I'm trying to save them from having to do the research or the time they spend using this tool to undo their mess.
Your reply with the lecture summed it up best. Get a DE or Pure or Nexus if you want to have UBL & root. Or else, just wait till somebody comes out with an exploit. But as of now, don't waste your time. You'll know when an exploit is available long before it is released due to the amount of traffic it will receive. Sunshine for example.
Click to expand...
Click to collapse
Yes, this tool don't work for downgrade, and tell him to the Moto G users, that flashed 5.0 OTA and he tried to go back bootloader to 4.4.4 and we brick their phones, only a few that only downgrade system get your phone working. The others will have to wait until a 5.0 release to add on my tool

Any idea what this error is?
OUTPUT*: C:\Python27\python.exe: can't open file 'C:\Program': [Errno 2] No such file or directory
OUTPUT*:
OUTPUT:

mjwill97 said:
Any idea what this error is?
OUTPUT*: C:\Python27\python.exe: can't open file 'C:\Program': [Errno 2] No such file or directory
OUTPUT*:
OUTPUT:
Click to expand...
Click to collapse
Install phyton, on the following route: C:\Python27\

Related

Stuck in fastboot, locked bootloader

In a stupid attempt to try to root my Moto G, I followed the instructions here up to step 6, rebooted, and was greeted in fastboot with a "failed to validate boot image" message. I have tried flashing a new boot image but I get a remote failure saying "Preflash validation failed", presumably because the phone's bootloader is locked.
The phone is from Cricket/AIO/ATT or whatever and does NOT qualify for bootloader unlocking.
Is there any way to fix this, or have I bricked my phone?

If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine: http://theroot.ninja/)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video: http://youtu.be/laU6NQ0LxR0
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.

skyguy126 said:
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
Click to expand...
Click to collapse
Thanks for the reply. Will definitely look into warranty if all else fails, I've only had the device for about a month.
The stock recovery factory reset doesn't fix the boot image. It successfully wipes everything but it still reboots right back to fastboot.
I cannot unlock the bootloader as it has been locked by the carrier and does not qualify for bootloader unlocking according to Motorola, and it looks like sunshine is a paid service, which even if I paid for I would have to be able to get into the phone to install the apk anyway.
It fails flashing any boot images or custom recoveries with a "(bootloader) Preflash validation failed" error.

To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.

skyguy126 said:
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
Click to expand...
Click to collapse
Yes, that's all fine and dandy, but like I said I'm stuck in fastboot so I wouldn't be able to use it anyway. At this point I don't even care about rooting, I'd just like to get my device working.

You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?

lost101 said:
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
Click to expand...
Click to collapse
It's an XT1032 and was running on 4.4.2. Maybe I tried with the wrong stock firmware, I used "AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml", which I found in this thread. The version matched the info I found using "getvar all" in fastboot so I figured it was the correct one. The http://sbf.droid-developers.org site seems to be down at the moment so I guess I can try a few more when it comes back up.

That would appear to be the correct firmware. However it would also appear your bootloader is preventing you from flashing it. As I said, the best solution would be to flash the 4.4.4 firmware image for your carrier, however there isn't one at this time.
You can always try flashing the XT1032 EU Retail 4.4.4 firmware image. It doesn't matter where you are in the world, it will should work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348

Is it bricked?

i have no idea about what happened to my MOTO G.
if it can be fixed tell me how. please guys
thanks
{
"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"
}

zakaria-b20 said:
i have no idea about what happened to my MOTO G.
if it can be fixed tell me how. please guys
thanks
Click to expand...
Click to collapse
If u can enter recovery u can save phone on this way...
First you have to know which version of moto g you have. Is it a xt 1032 or xt 1033. Are you unlocked your boot loader? Which version of android u have? 4.4 or 5.02
first hed in this post and download stock rom for your device. http://forum.xda-developers.com/showthread.php?t=2546251
then go to this tread http://forum.xda-developers.com/showthread.php?t=2542219
Follow those steps and it will be alive. But u will lost everything u have on your phone. If u are on 5.02 dont downgrade below 4.4
regards

bobrda said:
If u can enter recovery u can save phone on this way...
First you have to know which version of moto g you have. Is it a xt 1032 or xt 1033. Are you unlocked your boot loader? Which version of android u have? 4.4 or 5.02
first hed in this post and download stock rom for your device. http://forum.xda-developers.com/showthread.php?t=2546251
then go to this tread http://forum.xda-developers.com/showthread.php?t=2542219
Follow those steps and it will be alive. But u will lost everything u have on your phone. If u are on 5.02 dont downgrade below 4.4
regards
Click to expand...
Click to collapse
I think it was updated to lollipop. And its locked bootloader that's all what i know.
Thanks and sorry for my bad English

bobrda said:
If u can enter recovery u can save phone on this way...
First you have to know which version of moto g you have. Is it a xt 1032 or xt 1033. Are you unlocked your boot loader? Which version of android u have? 4.4 or 5.02
first hed in this post and download stock rom for your device. http://forum.xda-developers.com/showthread.php?t=2546251
then go to this tread http://forum.xda-developers.com/showthread.php?t=2542219
Follow those steps and it will be alive. But u will lost everything u have on your phone. If u are on 5.02 dont downgrade below 4.4
regards
Click to expand...
Click to collapse
I also probably "bricked" my device in some way.
However, I can access my custom recovery (TWRP). I can switch from TWRP to bootloader (and back), but I can't boot up to the system - because I accidentally deleted my /system partition. The only thing I need is to somehow get a zip file of a new ROM to my device. The problem is, that my PC (Windows 7) won't recognize a phone without an operating system.
I have XT1032 and I have of course unlocked bootloader. I had Android 5.0.1, but thanks to my stupidity, the Android OS is gone - the only OS left is a bootloader. I already have a stock ROM for my device downloaded, but I can't get it to the device. I don't care about files on my phone, I already backed them up. I have a backup of my ROM on my PC as well - but here's the problem again - I can't transfer files from PC to phone in any way. I tried Motorola Device Manager drivers, I tried adb drivers, but sadly nothing seems to work.
My phone doesn't have an SD card slot either.
If you can help me in any way, I'd appreciate it.
Thanks.

felmaster said:
I also probably "bricked" my device in some way.
However, I can access my custom recovery (TWRP). I can switch from TWRP to bootloader (and back), but I can't boot up to the system - because I accidentally deleted my /system partition. The only thing I need is to somehow get a zip file of a new ROM to my device. The problem is, that my PC (Windows 7) won't recognize a phone without an operating system.
I have XT1032 and I have of course unlocked bootloader. I had Android 5.0.1, but thanks to my stupidity, the Android OS is gone - the only OS left is a bootloader. I already have a stock ROM for my device downloaded, but I can't get it to the device. I don't care about files on my phone, I already backed them up. I have a backup of my ROM on my PC as well - but here's the problem again - I can't transfer files from PC to phone in any way. I tried Motorola Device Manager drivers, I tried adb drivers, but sadly nothing seems to work.
My phone doesn't have an SD card slot either.
If you can help me in any way, I'd appreciate it.
Thanks.
Click to expand...
Click to collapse
I wish i can help you, but i don't have had this kind of problem. maybe to tray download stock 5.02 brasil rom, for xt 1032 put the phone in recovery mode and with mfastboot recover phone/ i don't know will this work, didn't try it by my self. Some people have this problem on 4.4 and they successfully bring the phone to life, i cant find thread. But partition om Lollypop is different then KK you should search this forum. maybe ask member lost101
regards

bobrda said:
I wish i can help you, but i don't have had this kind of problem. maybe to tray download stock 5.02 brasil rom, for xt 1032 put the phone in recovery mode and with mfastboot recover phone/ i don't know will this work, didn't try it by my self. Some people have this problem on 4.4 and they successfully bring the phone to life, i cant find thread. But partition om Lollypop is different then KK you should search this forum. maybe ask member lost101
regards
Click to expand...
Click to collapse
Thank you very much. I actually fixed it before you replied to me, but I did exactly what you just told. I booted my phone to bootloader and used mfastboot commands to flash the 5.0.2 firmware. The thing I did wrong was, that I tried to recover the phone with adb commands from recovery, and that couldn't work for obvious reason. Mfastboot did the trick. Thanks for the reply though.

bobrda said:
If u can enter recovery u can save phone on this way...
First you have to know which version of moto g you have. Is it a xt 1032 or xt 1033. Are you unlocked your boot loader? Which version of android u have? 4.4 or 5.02
first hed in this post and download stock rom for your device. http://forum.xda-developers.com/showthread.php?t=2546251
then go to this tread http://forum.xda-developers.com/showthread.php?t=2542219
Follow those steps and it will be alive. But u will lost everything u have on your phone. If u are on 5.02 dont downgrade below 4.4
regards
Click to expand...
Click to collapse
This is my moto g..
Guys help me...

What model is your phone? Carrier? What bootloader version is on your phone? Any warranty left on your phone?

audit13 said:
What model is your phone? Carrier? What bootloader version is on your phone? Any warranty left on your phone?
Click to expand...
Click to collapse
No warranty. That's the only answer i have. I'm n00b

Since there is no warranty, the first thing I would do is unlock the bootloader. You can check by going here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Unlocking the bootloader makes it easier to flash a stock ROM.
I can't read everything on your screenshot. Could you take another picture or write out what it says in the first few lines?

[SOLVED] Any ROOTED XT1028 Users Still on Stock 4.4.4? Need Some Files Dumped...

**UPDATE May 31 2015**
I no longer need files dumped... although my original Moto G XT1028 is still busted... still working on that. If I figure out a way to fix the "downgraded boot" error on bootloader locked devices I'll update this post.
This is for the Verizon CDMA/3G variant. I'm sure chances are slim that someone has a rooted XT1028 still stock but might as well try...
Please PM or respond to this thread. Picked up this phone the other day and working on root/unlock. Managed to screw up some signatures somewhere and now I'm stuck in fastboot with: "version downgraded for boot" "failed to validate boot image"
I can still mess with a lot of the phone with fastboot so my quest shall continue regardless... but it'd be nice to possibly fix this...
but even more importantly than fixing my $20 phone... the dump's would help with the root/unlock process as there are some partitions and emmc areas I'm very interested in seeing but without a booting phone and root I cannot access.
If anyone knows someone with a rooted XT1028 please spread the word. Poking around here... it seems most people that have it rooted are flashed to 5.0 and changed all their stock files.

I just purchased a couple of these new. Will be reading up on rooting(and hopefully unlocking the bootloader if possible) it soon.
What is it that I need to capture that will help you?

autoprime said:
This is for the Verizon CDMA/3G variant. I'm sure chances are slim that someone has a rooted XT1028 still stock but might as well try...
Please PM or respond to this thread. Picked up this phone the other day and working on root/unlock. Managed to screw up some signatures somewhere and now I'm stuck in fastboot with: "version downgraded for boot" "failed to validate boot image"
I can still mess with a lot of the phone with fastboot so my quest shall continue regardless... but it'd be nice to possibly fix this...
but even more importantly than fixing my $20 phone... the dump's would help with the root/unlock process as there are some partitions and emmc areas I'm very interested in seeing but without a booting phone and root I cannot access.
If anyone knows someone with a rooted XT1028 please spread the word. Poking around here... it seems most people that have it rooted are flashed to 5.0 and changed all their stock files.
Click to expand...
Click to collapse
Follow this guide
http://forum.xda-developers.com/showthread.php?t=2542219
download this firmware
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
run in adb:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
This worked for me when I tired to update to a 5.1 GPE Moto G stock firmware, and had to restore back to stock verizon 4.4.4.
Hope this helps you.

groovadelickun said:
I just purchased a couple of these new. Will be reading up on rooting(and hopefully unlocking the bootloader if possible) it soon.
What is it that I need to capture that will help you?
Click to expand...
Click to collapse
there's currently no root/unlock for the device unless on 4.4.2 IIRC.. using either sunshine or chinese unlock code. all the models from bestbuy seem to be 4.4.4 and locked tight. there are a handful of users on here that managed to use sunshine within the timeframe but so far none of them are still on stock.
saw429 said:
Follow this guide
http://forum.xda-developers.com/showthread.php?t=2542219
download this firmware
http://www.filefactory.com/file/5cg..._4.4.4_KXB21.14-L1.41_42_release-keys.xml.zip
run in adb:
mfastboot flash partition gpt.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
This worked for me when I tired to update to a 5.1 GPE Moto G stock firmware, and had to restore back to stock verizon 4.4.4.
Hope this helps you.
Click to expand...
Click to collapse
thanks for the reply! :highfive:
unfortunately this is what I've been trying all along... my issue is fastboot will not allow me to write back gpt.img or boot.img.. mentioning failing pre-validation.
you were bootloader locked when you flashed 5.1 and had to go back to 4.4.4? or unlocked?
I feel like without being unlocked this isnt going to work.. for whatever reason.

autoprime said:
there's currently no root/unlock for the device unless on 4.4.2 IIRC.. using either sunshine or chinese unlock code. all the models from bestbuy seem to be 4.4.4 and locked tight. there are a handful of users on here that managed to use sunshine within the timeframe but so far none of them are still on stock.
Click to expand...
Click to collapse
Thanks. You pretty much just summed up what took me hours of reading and trying various methods without any success.
I also purchased from BestBuy and am on 4.4.4
It's too bad. I was excited to go on a ROM flashing rampage, :silly:
If the bootloader could be unlocked, these would be an insane bargain for $20 IMO!
I've set a couple up with IP Webcam. A low power, wireless webcam with 2 way audio for $20. Not bad... :good:

autoprime said:
there's currently no root/unlock for the device unless on 4.4.2 IIRC.. using either sunshine or chinese unlock code. all the models from bestbuy seem to be 4.4.4 and locked tight. there are a handful of users on here that managed to use sunshine within the timeframe but so far none of them are still on stock.
thanks for the reply! :highfive:
unfortunately this is what I've been trying all along... my issue is fastboot will not allow me to write back gpt.img or boot.img.. mentioning failing pre-validation.
you were bootloader locked when you flashed 5.1 and had to go back to 4.4.4? or unlocked?
I feel like without being unlocked this isnt going to work.. for whatever reason.
Click to expand...
Click to collapse
Bootloader locked Bestbuy $20 buy for the kids to play with. Originally on 4.4.4 bootloader 41.13 i beileve and now on 41.19 due to me trying to update to 5.1.

saw429 said:
Bootloader locked Bestbuy $20 buy for the kids to play with. Originally on 4.4.4 bootloader 41.13 i beileve and now on 41.19 due to me trying to update to 5.1.
Click to expand...
Click to collapse
hmm strange... let me make sure I'm not missing something here..
You updated to 5.1... and that "didnt work"... what error did it cause?. .. and which 5.1 images did you flash? I assume you flashed motoboot.img for 5.1 (since you now have an updated BL).. did you flash the 5.1 GPT? System?
Im just trying to figure out if you flashed something differently than I did. I flashed the Boost GPT, modem and motoboot imgs and after that I've been unable to flash any other GPT or boot img while in fastboot.
and then to restore your phone you just fastbooted all the images from the official 4.4 zip? I'm not missing some special step you did anywhere right? I've downloaded every single XT1028 and 1031 zip and tried all of those just to see what will flash thru fastboot.. and the ONLY GPT image I can flash successfully is the 4.4 boost.. all others give a prevalidation error. And at this point I cant flash ANY boot images as they all say prevalidation error.
It's got me scratching my head.

@autoprime
I have access to a boost Mobile that has been unlocked and should be running stock Motorola 4.4.4 and set up to work with Verizon on PagePlus
What would you need me to pull for you to try?
.

hhp_211 said:
@autoprime
I have access to a boost Mobile that has been unlocked and should be running stock Motorola 4.4.4 and set up to work with Verizon on PagePlus
What would you need me to pull for you to try?
.
Click to expand...
Click to collapse
howdy
appreciate the response! :highfive:
fortunately, I picked up another Moto G XT1028 (verizon) and managed to root it. so I'll be able to dump everything I needed. :good:
Now to work on fixing my original phone and working on a bootloader unlock :fingers-crossed:
{
"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"
}

autoprime said:
howdy
appreciate the response! :highfive:
fortunately, I picked up another Moto G XT1028 (verizon) and managed to root it. so I'll be able to dump everything I needed. :good:
Now to work on fixing my original phone and working on a bootloader unlock :fingers-crossed:
Click to expand...
Click to collapse
And how did you manage to do that? (root your xt1028) You must be a genius or something!
I was only able to root mine by paying a middleman for the bootloader unlock code last year. Is your root temp root or does it have ability to write to system as well? Anyway, good for you because the xt1028 is on serious lockdown so props for rooting it. :good:

autoprime said:
howdy
appreciate the response! :highfive:
fortunately, I picked up another Moto G XT1028 (verizon) and managed to root it. so I'll be able to dump everything I needed. :good:
Now to work on fixing my original phone and working on a bootloader unlock :fingers-crossed:
Click to expand...
Click to collapse
classic757 said:
And how did you manage to do that? (root your xt1028) You must be a genius or something!
I was only able to root mine by paying a middleman for the bootloader unlock code last year. Is your root temp root or does it have ability to write to system as well? Anyway, good for you because the xt1028 is on serious lockdown so props for rooting it. :good:
Click to expand...
Click to collapse
yeah, same here I would love to know if you rooted a 4.4.4 XT1028 too or maybe it was an earlier version? edit: sorry I can't read sometimes
I recently bought 2 new un's from best buy real cheap and all I really was planning to to is to debloat and give them to my kids.
If you have figured out a root method that would be a super bonus! please enlighten and share.
.

autoprime said:
Now to work on fixing my original phone and working on a bootloader unlock :fingers-crossed:
Click to expand...
Click to collapse
Please if you have made progress on getting root and/or unlocked bootloader to 4.4.2+ devices, can you share either publicly or privately with me/us please.
Thank you

hhp_211 said:
Please if you have made progress on getting root and/or unlocked bootloader to 4.4.2+ devices, can you share either publicly or privately with me/us please.
Thank you
Click to expand...
Click to collapse
I second this!!

Third! Well, I'm hoping whatever solution you've found also works on the Droid ultra. All Verizon phones are locked down very securely in likely the same way.
Sent from my XT1080 using Tapatalk

Me too. I have been waiting for a while!
I want to unlock the bootloader and root it! I don't want to pay for SunShine S-Off. And I found a temp. root with kingo root.

jakeh9777 said:
Me too. I have been waiting for a while!
I want to unlock the bootloader and root it! I don't want to pay for SunShine S-Off. And I found a temp. root with kingo root.
Click to expand...
Click to collapse
You temp-rooted the xt1028 moto g with kingo or king root? They are two separate root tools.

classic757 said:
You temp-rooted the xt1028 moto g with kingo or king root? They are two separate root tools.
Click to expand...
Click to collapse
Kingo not king. But sometimes kingo does not work every time... But most of the time.

Yeah, system write permission would be awesome
Sent from my XT1028 using Tapatalk Classic

autoprime said:
howdy
appreciate the response! :highfive:
fortunately, I picked up another Moto G XT1028 (verizon) and managed to root it. so I'll be able to dump everything I needed. :good:
Now to work on fixing my original phone and working on a bootloader unlock :fingers-crossed:
Click to expand...
Click to collapse
Flash the borked files using qdloader after soft bricking your device?
Then on to figuring out how to really root 4.4.4 given the annoying recovery restore issue...

@autoprime
How did you fully root Verizon Moto G (xt1028) on 4.4.4 and did it work... Did you get the bootloader unlocked without paying?

Update 6.0 mm full tmo & skinny debloated version

6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
New debloated version with insecure kernel and init.d support, rooted with Chainfire's Beta 2.71 SuperSU credit to SuperR for the help with the updater perms.
FIXED DOWNLOAD ALL APOLOGIES
Skinny Stylo Alpha version
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started

Saved

Requirements- Unlocked bootloader
Click to expand...
Click to collapse
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.

runningnak3d said:
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
Click to expand...
Click to collapse
@runningnak3d
I would prefer to be bootloader unlocked through fastboot oem unlock before doing any mods in 6.0. Every single time I did not I got secure boot error. If you make any system change on 6.0 with locked boot it will not boot.

Thank you for taking the time to do this.
:good::good:

So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.

Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
The main reason I made this was because I can never boot recovery or fastboot manually ( ex. w/hardware buttons) when you have the insecure kernel adb works when at the splash screen so it's easier to recover if you have any problems.
Sent from my LG-H631 using XDA-Developers mobile app

Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.

wrenchman76 said:
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
Click to expand...
Click to collapse
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.

runningnak3d said:
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
Click to expand...
Click to collapse
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?

wrenchman76 said:
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
Click to expand...
Click to collapse
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.

Waiting on the debloated version.
Sent from my LGMS631 using Tapatalk

runningnak3d said:
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Click to expand...
Click to collapse
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.

Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You didn't need to ship it back to LG. Firmware download mode is always available (hold vol up while plugging in USB cable -- just vol up, not vol up + power). Continue holding vol up until FW DL mode displays). Then just use the LG flash tool to flash a KDZ. It is a PITA when you have to go back that far, but you can't brick these phones, not with software at least -- they would need to be physically altered
-- Brian

Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You sent your device in for a soft brick? You should set up the flash tool for our phone with a 10j.kdz before doing anything. Hope you get it back soon.

Debloated version
Fixing some force close problems on a debloated version now, should be up later today or tonight.

@runningnak3d
Flashing the KDZ seems easy enough. But how could I fix it without unrestricted access to a computer? And my stock charger is broken without a USB cable. I had no choice but to send it in for repairs. Guess I'll be stuck on Lollipop for a while longer, at least.

Edubyah said:
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Click to expand...
Click to collapse
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)

JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
Can the bootloader be unlocked on the CDMA versions (ex. Boost, Sprint, Verizon)? If you can I will make a variant for it. But if you can't NO.
I just found out that the unlocked bootloader in 6.0 survives even the .kdz flashtool. So once you unlock your boot in 6.0 with fastboot oem unlock you never have to do it again even survived kdz downgrade to lollipop and update to 6.0 stayed unlocked.

JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
works great on metro ms631 just need wifi to stop turning its self off can you guys fix it! h631/ms631 mm kernel works find no errors help needed fixing wifi connection thanks

MT7-TL10 EMUI 3.0 B131 update to Lollipop or Marshmallow

Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced

M.Maany said:
Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
Click to expand...
Click to collapse
I just had this problem a month ago, same build number and barely any help. But, I was able to find helpful posts in the end. So I'm here to help... and yes. First Lollipop then Marshmallow update.
As you probably know, BACKUP what you need before proceeding.
Then you need to:
1- Unroot your phone if you have root.
2- Have EMUI's stock recovery. You can reinstall it in case you've installed a custom recovery on the phone.
3- Factory reset your device (HIGHLY ADVICE to do but not mandatory).
4- Download Lollipop update (to B326) from here: http://ministryofsolutions.com/2016/02/huawei-mate-7-lollipop-511-upgrade-for.html
5- After you finish the download, extract the "UPDATE.APP" file from it (no need to extract anything else from the archive), create a folder called "dload", and put "UPDATE.APP" in that folder.
6- Once you've done that, you should go to updater in your settings, select "local update". This time, the phone should detect the file "UPDATE.APP".
7- Next, attempt to update. The device should restart and attempt to install the update.
From my experience, the update took about 30 minutes to install, since I didn't factory reset before update. So, I don't know if it'll take less time with a clean device.
To update to marshmallow AFTER you've installed lollipop, simply find the OTA update online, download it, and repeat steps 5 to 7.
If anything of what I said was unclear, missing files to download, or you have any questions, feel free to post again here and I'll try to reply back.
Hopefully everything goes well with you, and have a good day.
Credit goes mostly to Mutahhar Bashir for posting the above site of the update.
EDIT:
P.S.: For bootloader re-lock, I personally don't think it's a must, since it worked updating ota with unlocked bootloader for me.

Highly appreciated my friend
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.

M.Maany said:
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
Click to expand...
Click to collapse
Found it on another site. This should be it: http://forum.android.com.pl/topic/2...recovery-sterowniki-mt7-l09-mt7-tl10/?page=27
Sorry I took long, had difficulty finding the file. Install the recovery version that you are CURRENTLY in. The file is called "Recovery mate7 mobopx v2.2". You'll find it on a specific reply on that page.
Keep me up-to-date with your progress for me to see if I can help.

Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant, u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?

M.Maany said:
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
Click to expand...
Click to collapse
Oh I was unclear. Sorry.
What I meant is, that the stock recovery you want to install should be the same as the android version of your phone currently. As in you are currently on Kitkat, then choose to install the kitkat stock recovery from the application.
I hope it's clear right now.

unable to install stock recovery
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
{
"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"
}
cscl.6te.net/Capture.JPG
any idea how to fix it?
by the way, i used kingroot to root my device, don't know if that's related.

Uhm... Just a few suggestions.
M.Maany said:
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
any idea how to fix it?
Click to expand...
Click to collapse
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.

iDoFatalities said:
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
Click to expand...
Click to collapse
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot

M.Maany said:
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
Click to expand...
Click to collapse
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.

ugggg
iDoFatalities said:
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
Click to expand...
Click to collapse
i uninstalled kingroot and this unrooted my device, installed adb drivers from clockworkmod site, installed hisuite from huawei site, already have usb debuggine enabled, but still getting same error
any alternative way to restore stock recovery?
can do the update.app manual update without restoring stock recovery?

uggggg
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?

M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
if I lock the bootloader then unlock it again, would that help? if yes, how do i re-lock it

M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
You MUST have stock recovery for OTA updates. Sorry.
You can try relock then unlock. But i specifically dont know how to. I think there is an app you can find on the tools/utilities tab of this device for utilities for the Mate7, which i think has a relock bootloader option, and many more utilities.
Other than that, I don't know yet how to help you man. For the meantime, surf the internet if you can find anything that can help.
I apologize.
EDIT: Doesn't your phone reboot into bootloader when trying to install? And have you made sure if the recovery has changed?

thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.

M.Maany said:
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
Click to expand...
Click to collapse
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.

YAYYYY !!!!
erayrafet said:
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
Click to expand...
Click to collapse
FINALLY !!!, tried unlocking bootloader again and it worked, although it took forever to get the unlock code.
anyway, now I have stock EMUI recovery, will remove root and do the OTA and let you know how it goes.

ON lollipop
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?

M.Maany said:
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
Click to expand...
Click to collapse
Yes.

AWESOME
Awesome !! now do you have a link for me to download the UPDATE.APP for Marshmallow?
or does it need to be updated in some other way?

Database Info

welcome