[Q] Questions regarding un-rooting. - Moto X Q&A

Verizon Moto X (2013) 4.2.2 Build number: 13.11.1Q2.X-69-3
Hey guys, for the past week I have been trying to un-root my moto x and have been unable to with several different methods.
I first tried RSD Lite, but no matter what I try over and over RSD Lite is not detecting my phone and I havent come across a way to fix that
I then moved on and tried to un-root using Fastboot following this tutorial. For some reason when my when I try, gpt.bin fails.
I then moved on to the Moto X Toolkit. Since this is basically just an automated way of doing fastboot I wasnt to hopeful, and of course it too failed.
Here is what i get when the process fails
Code:
writing 'recovery' ...
Preflash validation failed
FAILED <remote failure>
writing 'system' ...
Preflash validation failed
FAILED <remote failure>
writing 'boot' ...
Preflash validation failed
FAILED <remote failure>
What can I do to fix this? Any help is greatly appreciated!!

paradoxfreq;56816079I then moved on and tried to un-root using Fastboot following [URL="https://www.youtube.com/watch?v=ZtRSrQrzIPI&list=UUVLBNAjddTt6AAPL5141Ybg" said:
this tutorial[/URL]. For some reason when my when I try, gpt.bin fails.
Click to expand...
Click to collapse
Start the phone in FastbootAP/Bootloader mode
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.

KidJoe said:
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.
Click to expand...
Click to collapse
System Version: 140.45.5.
In the command window.
Code:
C:\adb>fastboot devices
T062801FWT fastboot
C:\adb>fstboot flash partition gpt.bin
<bootloader> Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' <32 KB>...
OKAY [ 0.247s]
writing 'partition' ...
FAILED <remote failure>
finished. total time: 1.078s
On my phone.
Code:
getvar partition-type: partition
downloading 32768 bytes
done
[COLOR="Red"]downgraded security version
update gpt_main version failed
preflash validatoin failed for GPT[/COLOR]
Thank you for the Reply!

I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?

KidJoe said:
I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?
Click to expand...
Click to collapse
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)

paradoxfreq said:
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)
Click to expand...
Click to collapse
Ok, you have some conflicting info posted.
Post 1 you say you have 4.2.2 Build number: 13.11.1Q2.X-69-3. (I thought 13.11.1Q2.X-69-3 was 4.4)
But in Post 3 you say System Version: 140.45.5. (which is 4.4)
Now, the bootloader version being 30.b2 goes along with 4.4.
the GPT.BIN failing to flash usually indicates that you are trying to DOWNGRADE. There are warnings everywhere saying you shouldn't, The only time its safe to downgrade is if you have 4.4 on your phone and are following the SlapMyMoto process. But since you're trying to un-root, you shouldn't be following SlapMyMoto.
So what are you trying to flash exactly?
At this point, DO NOT ATTEMPT to flash anything but 4.4, 4.4.2 or 4.4.4 on your phone! You need to do a FULL flash, and I would suggest manually using mFastboot, with the extra commands (see option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html ). Because of the GPT.BIN downgrade failures at this point, I would suggest 4.4.2 or 4.4.4 and NEVER try to flash anything older.

Related

[Q] soft bricked verizon non-dev moto x

I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635366
slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
Are you still able to enter the Bootloader menu?
jpd_ said:
Are you still able to enter the Bootloader menu?
Click to expand...
Click to collapse
yes, I just cant boot into recovery or android.
slappydj1 said:
yes, I just cant boot into recovery or android.
Click to expand...
Click to collapse
Go ahead and flash the stock recovery img then follow the instructions from here:
http://forum.xda-developers.com/showthread.php?t=2639102
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Very helpful link here as well on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2603358
If you made a back up through TWRP, you can try restoring your phone from there too.
jpd_ said:
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Click to expand...
Click to collapse
The Verizon OTA is out. That is what got him in the situation he is in.
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
They generally seem to show up 1 week to 1 month from when the OTA is released.
slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Cozume said:
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Click to expand...
Click to collapse
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
slappydj1 said:
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Cozume said:
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Click to expand...
Click to collapse
I tried to boot into recovery using the fastboot menu on the phone.
slappydj1 said:
I tried to boot into recovery using the fastboot menu on the phone.
Click to expand...
Click to collapse
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Cozume said:
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Click to expand...
Click to collapse
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
slappydj1 said:
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
Click to expand...
Click to collapse
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Cozume said:
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Click to expand...
Click to collapse
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
slappydj1 said:
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Cozume said:
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Click to expand...
Click to collapse
So Ill have to wait until the factory image is released?
slappydj1 said:
So Ill have to wait until the factory image is released?
Click to expand...
Click to collapse
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Cozume said:
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Click to expand...
Click to collapse
I was going to do a factory reset using fastboot, and I flashed the gpt.bin. after that I could not flash anything. Later I learned that wasnt the factory image but the OTA update, so I realized I messed up then.

Trouble restoring PE to stock KitKat

Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
samabuelsamid said:
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s​
Click to expand...
Click to collapse
try:
Code:
mfastboot flash motoboot motoboot.img
holtenc said:
try:
Code:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Sorry, copy/paste error there.
I actually tried the motoboot motoboot.img too and get the same error.
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
holtenc said:
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks, those are precisely the instructions I used. I haven't done anything with the radios. I flashed the leaked lollipop rom and then used the official image files to try to go back. The bootloader was initially not unlocked, I unlocked it only in an attempt to get the motoboot file to flash. Now I can't relock it because this part of the image is missing.
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
Only thing I did with bootloader locked was the partition. As soon as I got to the motoboot and it failed, I figured I would need to unlock and did that. Since then, I've tried the whole process a couple of times with the same result. I will however, give it another shot.
You don't need motoboot to update. Go use the script and it will do everything for you.
tw1tch175 said:
You don't need motoboot to update. Go use the script and it will do everything for you.
Click to expand...
Click to collapse
Which script is that?
samabuelsamid said:
Which script is that?
Click to expand...
Click to collapse
My multitool in development section has stock restore included
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
Downloading V4.1 now, thanks
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
I flashed with the multitool and was able to get back where I started with the leaked PE lollipop version but something is still missing because I can't relock the bootloader.

[Q] Issues with Recovery

I have a motorola X 2014 Pure Edition that a while ago i side loaded the Lollipop Soak test image, however since it wasn't the final, it appears that I was instructed to downgrade back to 4.4.4 and then I would be able to upgrade to 5.0-11. I downloaded the Factory image from Motorola and re-flashed the images onto my phone. However when I attempted to refresh the motoboot.img it failed with the error below. However all the other parts flashed alright without issues. I then booted my phone and it booted into Kit Kat. I then attempted to do the OTA upgrade for Lollipop but it fails and puts the phone into a endless reboot phase. When I try to go into Recovery Mode it doesn't work, i get to the broken android screen however I cannot get to the Recovery Menu at all.
I reached out to Motorola support and they said: "We can not help you with this issue. I recommend you post this on forums dedicated to this (aka XDA), it should be fairly easy to find someone to help you there. here is not issue with the Moto X 444 BL. it seems to me it is related to the "stock Android 4.4.4" you flashed on your phone. It looks like you have a mismatch somewhere between TZ, GPT and the version of the BL on this device; it might have been cause by what you flashed on the device before having to return to stock.. .. "
I'm at a loss right now other than trying to send my phone back to Motorola to see if they can fix it. Hoping someone might have an idea of what i can do to fix my issue??
% ./fastboot flash motoboot motoboot.img
14-12-04 - 14:25:59
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.073s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.143s
Any help would be appreciated.
hey bro seems like the image might be corrupted. Try finding another motoboot.img. Or Lock and Unlock your bootloader again. And best of all try to get in fastboot and go back kitkat and keep it that way. Because i don't think you want to be in a brick again. Consult a person here on XDA that knows more about it. Thats my advice.
Sending it back won't work, your warranty is gone. Clearly stated in the page where you unlocked the bootloader. Sorry bro.
And btw next time please post this in the Moto X section.
Thank you! Greetz ErixGamer

Moto G XT1079 - Bootloader Update- HELP

I have a Moto G 2014 LTE XT1079 ASIAN Model (purchased in India)
Okay so i have no OS installed as of now as i unlocked the bootloader and somehow the OS got deleted.
I have TWRP recovery installed though. Whenever i try to install a custom rom like CM or Resurrection Remix, it shows be an error that this package i compatible for bootloader 0x4886 and 2 or 3 other bootloaders. it says that i have bootloader 0x4226. I want to change my bootloader so that i could install custom ROMS.
Does anyone have any idea about how i could do this.
PLEASE PLEASE PLEASE HELP.
Try flashing this Stock Firmware. Just follow the instructions given..
https://forum.xda-developers.com/moto-g-lte/general/update-stock-6-0-marshmallow-firmware-t3535380
Preflash Validation Error
ERROR : Pre flash validation failed. On the phone screen its showing 'version downgraded for primary_gpt'
i used it in mfastboot also. but same error.
Please, i could use help real bad.
C:\Users\Nikhil\Desktop\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.032s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.325s
RaviWL said:
Try flashing this Stock Firmware. Just follow the instructions given..
https://forum.xda-developers.com/moto-g-lte/general/update-stock-6-0-marshmallow-firmware-t3535380
Click to expand...
Click to collapse
Keep flashing the rest of the files..
System files : Preflash validation Error
Ravi bro, its giving the same error when i flash the system.img sparesechunk img...and on the fone it says that 'image is too large'
i think i have an old bootloader. thats why it wont let me flash CM through TWRP also. it says that CM firmware is for bootloader 4886 while mine is 4226
also i have seen people flash bootloader.img also...but there is no such file here.
I have only 2 options left-
1. Get rid of the preflash validation errors
2. Update my bootloader.
i would be lovely if you could provide me with an updated bootlader.img file.
Ravi bro i will be very grateful to you if you could help me through this problem
RaviWL said:
Keep flashing the rest of the files..
Click to expand...
Click to collapse
preflash validation errror
nklrwt said:
Ravi bro, its giving the same error when i flash the system.img sparesechunk img...and on the fone it says that 'image is too large'
i think i have an old bootloader. thats why it wont let me flash CM through TWRP also. it says that CM firmware is for bootloader 4886 while mine is 4226
also i have seen people flash bootloader.img also...but there is no such file here.
I have only 2 options left-
1. Get rid of the preflash validation errors
2. Update my bootloader.
i would be lovely if you could provide me with an updated bootlader.img file.
Ravi bro i will be very grateful to you if you could help me through this problem
Click to expand...
Click to collapse
same problem i am also having. tell mehow to fix it if possible
Try flashing a modern motoboot.img for thea (I have 0x4821) using:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
You can take one from an OTA package for your phone. It's strange. My XT1072 came with a recent bootloader preinstalled, but try.
Note, it must be for thea, not titan or you will cripple or hardbrick your device.

Pretty sure I just bricked my wife's G5S Plus

First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
HTML:
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?
natalic said:
First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
target max-sparse-size: 256MBsending 'partition' (45 KB)...OKAY [ 0.034s]writing 'partition'...(bootloader) Validating 'gpt.default.xml'(bootloader) Security version downgrade(bootloader) Image primary_gpt failed validation(bootloader) Preflash validation failed(bootloader) Cancelling 'gpt.default.xml'FAILED (remote failure)finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?
Click to expand...
Click to collapse
Flash newest software version
61-5
Adi5 said:
Flash newest software version
61-5
Click to expand...
Click to collapse
Got a link? I'm using:
NPSS26.116-45-5_cid50
I'm panicing here
https://androidfilehost.com/?fid=673956719939831738
Adi5 said:
https://androidfilehost.com/?fid=673956719939831738
Click to expand...
Click to collapse
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?
natalic said:
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?
Click to expand...
Click to collapse
Flash this one from afh should be flashed without error
Adi5 said:
Flash this one from afh should be flashed without error
Click to expand...
Click to collapse
I REALLY hope so
adi5 said:
flash this one from afh should be flashed without error
Click to expand...
Click to collapse
you saved me man...i am so thankful! It worked!!!
Hey, I have exactly the same problem but no luck with flashing 61-5. I can access fastboot from a PC but unfortunately nothing showing on the screen.

Categories

Resources