Ey guys! I really need you help, Im stucked with my Moto X.
I have a Moto X xt1053 with an unlockable bootloader, in the page of motorola says that my phone doesnt qualify to be unlocked.
So, the problem is that I was trying to upgrade to android kitkat 4.4 following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2545775
All was going good until when I try to flash boot.img, I cant load that file into my phone, So im stucked in the fastboot screen of my phone, because now I cant even get into the TWRP recovery option, just fastboot, I cant load any boot.img file into my phone.
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
So, what can I do?
Any help?????
THANKS A LOT!!!
What error do you get?
Ctrl-Freak said:
What error do you get?
Click to expand...
Click to collapse
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
daritoca said:
When Im trying to flash the boot.img file, the error that appears in my phone says:
Failed to hab check for boot: 0x56
preflash validation failed for boot
Click to expand...
Click to collapse
I'm guessing your T-mobile xt-1053 will not accept the boot.img from a AT&T xt-1058 while the bootloader is locked.
First of all, I don't think you are in danger of a 'brick.' You should still be able to flash back to stock 4.2.2, and there are a few tutorials on this subject within this forum.
I have no idea if it would work, but if you want to proceed with an AT&T version of 4.4, you could try flashing the boot.img from the T-mobile 4.4 build. Download "TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip" from http://sbf.droid-developers.org/ghost_rcica/list.php, extract boot.img to your fastboot directory, then proceed. If you 'go this route', you should also use the modem (NON-HLOS.bin) and fsg.mbn from T-mobile.
I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app
daritoca said:
I also do that, i downloaded the att 4.4 kitkat version and try to flash the boot.img but it doesnt work, no boot.img, no sistem.img
I've been trying with other versions and had same problem.
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear, did you download and try the T-mobile boot.img ?
Another random thought, are you using the correct motorola fastboot? (I used the "Motorola Fastboot Files" link from this post: http://forum.xda-developers.com/showthread.php?t=2406409, thanks mattlgroff)
No, i havent try the tmobile version.
Ill try in a few hours and tell you the result.
Thanks a lot!!
Sent from my XT890 using xda app-developers app
Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?
daritoca said:
Cant flash any *.img file because my bootloader is locked, I cant flash any file becuase of that. As long as I know, to flash an *.img file I need to have my bootloader unlocked, Am I right?
Click to expand...
Click to collapse
Not exactly. A locked bootloader keeps you from flashing images that are not properly signed. So if you have a T-mobile phone, the bootloader will allow official T-mobile *.img files. An exception to this is that if you upgrade your bootloader to a newer version (by taking an OTA for example), sometimes the newer bootloader will now allow older T-mobile *.img files. That exception should not apply here, as we are discussing kitkat - the latest version of android.
But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?
daritoca said:
But when I try to flash any boot.img I just cant flash it, I try with t-mobile and I couldnt, right now Im stucked, I dont know what else to do, my phone is dead and I just cant flash any image, right now Im working at night, so it takes me longer to answer and try to restore my phone.
What else I could do if I cant flash any image in my phone, and if in my phone I erased my boot.img file?
Click to expand...
Click to collapse
Flash the T-MOBILE SBF FILE COMPLETELY
Sent from my XT1058 using XDA Premium 4 mobile app
Ok, I'll do that this morning and tell you how it goes.
Thanks!
When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What else can I do?
daritoca said:
When Im flashing the T-mobile completely I have an error.
Failed to hab check for boot: 0x56
preflash validation failed for boot
Im doing with RSD Lite 6.1.5
It stops in step 5, cant flash boot.img
...
What else can I do?
Click to expand...
Click to collapse
I see you tried the T-mobile 4.4 SBF, and once again boot.img didn't work...
In your original post, you mention that you are on a xt-1053. Is that a US T-mobile and not a developer edition? I ask because the evidence suggests your phone is somehow different. If you are on a different version, you need to carefully pick the correct SBF from this list: http://sbf.droid-developers.org/ghost_rcica/list.php Then use RSD to flash it.
If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk
arcanexvi said:
If you've flashed the wrong bootloader/partition table, you'll need to manually flash your proper gpt and motoboot and reboot before running the sbf.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?
Ctrl-Freak said:
Good tip.
Question:
I noticed that boot.img was "step 5" within the OP's RSD lite process, and the previous steps include motoboot.img and gpt.bin (at least they do on my AT&T SBF). I didn't think the bootloader would allow itself to be overwritten with a "wrong" version. Am I mistaken? If so then what, if not the the code within motoboot.img and gpt, checks the signatures of images to be flashed?
Click to expand...
Click to collapse
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk
arcanexvi said:
It flashes them but doesn't reboot before trying to flash the rest usually. If the wrong info is currently loaded, it'll need a reboot first. This is really only an issue for unlocked devices as signature checks will stop you from borking yourself up this badly.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?
Ctrl-Freak said:
Gotcha.
The OP stated they had a locked bootloader. My question:
Is it possible, with a locked bootloader, to flash a "wrong signatured" motoboot and gpt? (I certainly have not tried it, and I assumed it was not possible.)
If the answer is no and the OP had the wrong SBF, then why did the OP's SBF attempt fail on step 5 instead of the earlier motoboot or gpt steps?
If the answer is no and the OP had the right SBF, then why did the SBF fail at all?
Click to expand...
Click to collapse
Some files aren't sig checked or share a sig with a different device. Others are. So it's possible to have a partial failure which leads to headaches.
Sent from my XT1060 using Tapatalk
Thanks a lot for your support, Im doing the flash with the original rom ( fastboot-ghost_amxmx-user-4.2.2-13.9.0Q2.X-116-LCX-26-29-release-keys-cid12-AmericaMovil-MX.tar.gz)
When Im trying to flash it, I got another error.
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
So, thats why I was no trying to flash the original rom, because in the first try to upgrade my phone, I try to upgrade to kit kat 4.4
Answering the question if my device is a developer edition, it isnt, thats one of the reasons I cant unlock my bootloader.
So, any other suggestion?
Hi
Is stock ROM for Moto G5s Plus available to download? I need to reflash my phone with stock ROM and unable to find it yet.
Thanks
Full firmware is available!
Here you go...
https://drive.google.com/uc?id=0B9VEaFoqTCkLX2JUd0lVdzZLUUk&export=download
Please tell me if it relocks your bootloader.
Thanks Raj.S. Just to confirm, this is for Indian variant of Moto G5s Plus, right?
Update: Tried to flash this using TWRP but got error: Invalid zip file format!
Tried fastboot update method and that also results into error: no android-info.txt file found.
Please help.
Ok, was able to install the ROM with fastboot. However, it doesn't relock bootloader.
There's a few additional steps required to relock the bootloader.
If you run "fastboot OEM lock" then it will tell you more.
Essentially you need to execute this command twice, then flash the OEM data (boot and system), and then execute the "fastboot OEM lock" command once more.
That should lock things back up again.
@Raminder_Singh
How did you overcome the no android-info.txt file found error?
I am unable to flash the ROM via fastboot.
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
xdafanboii said:
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
Click to expand...
Click to collapse
there is a firmware for the phone
unpack it
u will find there file Checksum.ini
and unlock‐secro.img(or diferent name point is unlock)
rename checksum.ini on checksum.oem
then turn off all checks in flashtool leave marked only SECRO line
u must choose unlock‐secrom.img for SECRO line
once u'll flash SECRO u will have to flash twrp, to do that u must turn off all checks except RECOVERY, for RECOVERY u must open recovery 1.72.img then flash it, after u can just flash supersu.zip via twrp
i've done it all on my 1.76 device it will also work on 1.79
twrp u can find here(u need to register on that forum)
https://4pda.ru/forum/index.php?showtopic=756527&view=findpost&p=53228248
Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
rmercer said:
Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
Click to expand...
Click to collapse
Looks like the E5 forum handles E5+ too (their TWRP says for E5+) and I see your post there. I'm not familiar with your phone but did you try a factory reset? Another option might be to fastboot flash the boot.img from your model's firmware on lolinet - see here - which should restore your stock kernel. Either option will delete your personal data though but sometimes no other choice. See what they say over there & maybe post in the TWRP thread where OP looks to know his stuff.
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
rmercer said:
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
Click to expand...
Click to collapse
Make sure it's the correct official firmware version for your software channel &/or vendor. You need to unzip the firmware into a temp directory on a computer, then you'll see boot.img among many files, copy it into your fastboot folder, connect the phone (do a 'fastboot devices' to make sure it's working), then type 'fastboot flash boot boot.img' and when it's done reboot. Also try a factory reset first if you can.