I decided to return my Sprint variant. So i needed to s-on and lock the bootloader. Problem is, now I have a 1 sec bootloop. Here's what I did. No idea how to fix the problem now.
Here's what I did in order to get the phone back to 100% stock to return it.
Changed the CID (incorrectly) to spsc_001 instead of spcs_001 but iddn't notice that.
Managed to get s-on but couldn’t get bootloader locked again.
reinstalled twrp and SU
booted up
installed sunshine and successfully s-off'd & locked
rebooted to download mode
Did a s-on using fastboot oem writesecureflag 3
rebooted and got a 1 sec bootloop
booted back into download mode and tried to factory reset via fastboot but can’t write the partition
tried to flash twrp, but got a security warning BL-unlocked
Now I'm stuck in a super short .5 second bootloop and can’t access stock recovery.
I try to install the ruu.exe and I get a Customer ID error. I try to install RUU.zip and I get a load_file: could not allocate -2146013644 bytes (which I assume means the partition is full but I can't even erase the userdata.) I also get a Security checking failed GT_CONNECT_FAIL on the download mode screen. I'm totally clueless as to how to get out of this situation. Anyone been here before or knows how to deal with this?
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
honestly, I think you're screwed...I don't know how you'll be able to fix this w/o being able to boot up, can't unlock bootloader, can't use fastboot to flash anything, can't flash RUU...somehow u need to get your CID back to SPCS_001...u may just have to return it in that condition & act ignorant.
any ideas @dottat @Captain_Throwback
vijn said:
Now, my vars are:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT64xxxxx6
(bootloader) current-slot:
(bootloader) imei: 99xxxxx1
(bootloader) version-main: 2.42.651.63
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: spsc_001
all:
finished. total time: 0.009s
Click to expand...
Click to collapse
OMJ said:
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
Click to expand...
Click to collapse
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
vijn said:
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
Click to expand...
Click to collapse
Well did you attempt to see if HTC dev would give you an unlock token at least?
Sent from my SM-G955U using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
You might be able manually flash the ruu partitions one by one as well. Have you tried that?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-G955U using Tapatalk
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
Click to expand...
Click to collapse
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
dottat said:
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
vijn said:
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Click to expand...
Click to collapse
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
OMJ said:
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
Ok well, I tried these.
The sd card method failed due to the CID mismatch.
The stock boot.img from the firmware zip method gave the following:
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
The Firmware flash via fastboot, no ext sd card needed gave this:
sending 'zip' (66180 KB)...
OKAY [ 3.269s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 6.456s
I'm screwed aren't I?
dottat said:
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
vijn said:
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
Click to expand...
Click to collapse
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
dottat said:
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
Click to expand...
Click to collapse
Ok, will try that. You wouldn't happen to know where I can find the zip would you? I always used the exe cause that's what was on the htc site. Not sure where the actul RUU.zip file can be found. I assume I can use the one found here: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
And dottat, OMJ, thanks a lot for your help. It's people like you who make this community what it is.
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
vijn said:
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
Click to expand...
Click to collapse
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
OMJ said:
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
Click to expand...
Click to collapse
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
vijn said:
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
Click to expand...
Click to collapse
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
OMJ said:
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
Click to expand...
Click to collapse
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
vijn said:
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120734364
Saw your post while looking for an sim unlock for my Japanese HTC 10.
Couldn't resist reading more about your problem tho.
First idea but quite dangerous if done incorrectly..
Try and see if you can change the cid in the ruu.exe with a HEX editor?
If that doesn't work, next try and change the cid of the ruu. zip.
Might be a long shot, but if the files cid's aren't encrypted it might work!
Related
Hi everyone,
I have an HTC Magic 32B (SFR/Vodafone FR).
I updated hboot from 1.33.0013 to 1.33.0014G (*1) to be able to unlock the bootloader with htcdev unlock.
I unlocked it successfully using HTC official instructions.
Now I want to boot or install a custom recovery (recovery-RA-sapphire-v1.7.0G.img) and it doesn't work.
My hboot boot says :
Code:
*** UNLOCKED ***
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0014G (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Jan 31 2012,14:43:52
HBOOT
<BACK> FastBoot Mode
From fastboot (when I hit Return) I have the "FASTBOOT USB" string, from fastboot if I try :
1)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.712s]
booting...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.733s
2)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.712s]
writing 'recovery'...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.738s
After reading htc instructions to flash img, I also tried from RUU mode using "fastboot oem rebootRUU", that gives me RUU USB on the phone and on the computer :
Code:
C:\android\downloads>fastboot oem rebootRUU
...
OKAY [ 0.012s]
finished. total time: 0.016s
Then I try :
1)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.718s]
writing 'recovery'...
[B]FAILED (remote: image type not support)[/B]
finished. total time: 1.749s
2)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.714s]
[B]booting...[/B]
Here it hangs, I must enter a fastboot reboot to regain the control on the device.
I don't know what's wrong here. Either from fastboot (usb) or ruu (usb) it don't work even if the bootloader is unlocked.
amonra recovery should install and work on this phone right ?
Currently I don't want to root or S-OFF the phone because I like to apply not too much modification on it.
Can you help me ?
Thanks for the attention, and even more if you can help
(*1) 1.33.0013 cannot be htcdev unlocked because it don't accept "fastboot oem get_identifier_token", that's why I updated to 1.33.0014G.
The update was given by htcdev.com through an RUU that didn't work because I started it from adp (phone started normally with usb debugging on) and for an unkown reason adp reboot bootloader didn't work, I made it work be starting RUU exe from fastboot directly.
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
superbob56 said:
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
Click to expand...
Click to collapse
hi, i have same problem on my HTC Magic, from hboot 1.33.0014 i can`t do enything (flash new recovery or new rom or make RUU)
did u resolved that problem?
I must admit I've given up.
I recently bought myself a fresh Nexus 5...
Gold luck to you if you try to go on with the HTC Magic !
Dear All,
A few days ago SPRINT moto X 1056 gets Firmware Update of about 5.4 MB.. After that update alot of people which have moto x 1056 and they are not using Sprint network get them sim locked.. Sim was not recognized and default network was selected "sprint" on the mobile and also the nv-items files were changed to Read Only Mode. Also after the update.. People keep getting UPDATE PRL on every restart.
Click to expand...
Click to collapse
I have also got in trouble after this update and researched about 3 days to get my problem solved.
The things u need to do is to
Install Motorola Drivers.
Backup Your Personal Data.
Install adb + fastboot (I recommend to use mfastboot).
Unlock Your Boot Loader.
Flash TWRP Recover throug fastboot.
Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
(OPTIONAL: If your phone have "SPC code" . Then you need to Flash "161.44.32.ghost_sprint.Sprint.en.US[1].zip" through TWRP. and get your SPC code then unlock the sim) In my Case i dont have SPC code set in my phone and i was able to unlock sim without giving SPC code on firmware 4.4.4 pre 5.4 mb update.
Click to expand...
Click to collapse
Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Unlock Sim
Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US" (To Remove Update PRL messages/things)
Remove Bootloader Warning Message (Flash [GHOST] Moto-WinterBoot-20150419-STABLE)
Note: This GUIDE is for MOTO X SPRINT [XT1056]
Now Lets Get Starting with Steps.
1. Install Motorola Drivers.
Downlod the drivers from the following link and install it.
"https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481"
Or
"http://motofirmware.center/files/file/41-motorola_end_user_driver_installation_640_32bitzip/"
Click to expand...
Click to collapse
2. Backup Your Personal Data.
Connect your device to your PC. Check Usb Options selected to "MTP" on your device.
Backup your personal data on phone.
Click to expand...
Click to collapse
3. Install adb + fastboot (I recommend to use mfastboot).
You can install adb + fastboot by installing Android-SDK. To Install Android SDK. Download the Standalone Android-SDK from following Link.
"http://developer.android.com/sdk/index.html#Other"
and now watch the following Guide to install and set parameters of Android-SDK.
"https://www.youtube.com/watch?v=oaNM-lt_aHw"
OR as i said i Recommend to use "mfastboot"
You can download mfastboot from following link
"http://www.mediafire.com/download/6b3aw3dq8omefyw/mfastboot-v2.zip"
Just download and unzip it to use
Click to expand...
Click to collapse
4. Unlock BootLoader:
You can easily unlock bootloader of your device by clicking
"https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b"
OR watch this video for 100% Success.
https://www.youtube.com/watch?v=3sxgz7jxRMw
Click to expand...
Click to collapse
5. Flash TWRP Recover throug fastboot.
Download latest TWRP recovery from link
"http://techerrata.com/browse/twrp2/ghost"
Now, Install TWRP using this site method.
"https://twrp.me/devices/motorolamotox2013.html"
Click to expand...
Click to collapse
6. Wipe Everything " System, Cache, Dalvik Cache, Internal Storage, Data" (After this u will have no OS in your mobile)
After installing recovery . Go to recovery by following method.
Hold and press VOL DOWN + POWER button for 5 secs and release.
Now u r in bootloader. Go to recovery by VOL DOWN button and select by VOL UP button.
Now go to WIPE > Advanced > and then wipe All folders. except USB OTG.
Now you have NO OS installled on ur Moto X.
Reboot to Recovery to bootloader again.
Click to expand...
Click to collapse
7. Flash Firmware "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml"
Now its time to flash the pre 5.4 mb update firmware to your moto x xt1056.
Download the firmware from here
"http://www.filefactory.com/file/6tiwapkl82jl/"
And flash through fastboot. just extract the zip file and copy all files and folders in "Mfastboot folder" 0r "android-sdk folder"
Now open Mfastboot folder and press "Shift key + Right Click" now click "Open Command Prompt here"
Perform the following steps as i have performed .
Click to expand...
Click to collapse
C:\mfastboot-v2>mfastboot devices
T063204CVP fastboot
C:\mfastboot-v2>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.275s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.468s]
finished. total time: 0.743s
C:\mfastboot-v2>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 5.049s]
finished. total time: 5.419s
C:\mfastboot-v2>mfastboot flash logo logo.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'logo' (628 KB)...
OKAY [ 0.343s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.224s
C:\mfastboot-v2>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.920s]
writing 'boot'...
OKAY [ 1.358s]
finished. total time: 2.280s
C:\mfastboot-v2>mfastboot flash recovery recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (10240 KB)...
OKAY [ 0.928s]
writing 'recovery'...
OKAY [ 0.968s]
finished. total time: 1.898s
C:\mfastboot-v2>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [ 16.692s]
writing 'system'...
OKAY [ 10.502s]
sending 'system' (262144 KB)...
OKAY [ 16.684s]
writing 'system'...
OKAY [ 9.854s]
sending 'system' (262144 KB)...
OKAY [ 16.683s]
writing 'system'...
OKAY [ 8.245s]
sending 'system' (114215 KB)...
OKAY [ 7.443s]
writing 'system'...
OKAY [ 3.613s]
finished. total time: 89.725s
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
C:\mfastboot-v2>mfastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'fsg' (1223 KB)...
OKAY [ 0.386s]
writing 'fsg'...
OKAY [ 0.828s]
finished. total time: 1.216s
C:\mfastboot-v2>mfastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.164s]
finished. total time: 0.165s
C:\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.001s
C:\mfastboot-v2>
C:\mfastboot-v2>
Click to expand...
Click to collapse
Now please Proceed to Next POST.
2nd Post
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
To unlock your sim follow the following guide here on XDA.
"http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2"
Note: In my case i have checked and there is no SPC code needed to sim unlock. No need to check spc code checkbox in NV-ITEMS-READER-WRITER software.
So the you just connect your phone to nv items reader writer software and flash only
nv-unlock.txt
nv-unlock2,txt
unlock-domestic.txt
nv-ruim files need SPC code to write . If u dont have SPC code set in your phone for enable / disable DIAG PORT then you dont need to write nv-ruim files.
Click to expand...
Click to collapse
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Download LolliPop Retail 5.1 from following link.
"https://drive.google.com/file/d/0BzTDEHw-bGypMGhfdEFVczd1dHM/view"
This is XT1053 untouched Retail ROM
Open TWRP recovery. and Flash the ROM by clicking Install . Select the location where you copy the zip rom in internal memory.
After installing the ROM , Reboot to TWRP Recovery again and WIPE CACHE and DALVIK CACHE.
Then reboot to system. Now it should start the OS 5.1 and there should not PRL updation on start and restart.
Click to expand...
Click to collapse
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Download your favorite Boot Animation Image from the link
"https://drive.google.com/folderview?id=0Bx0JlaDkWMGAfkpQcGl2M3NCWi11SmZ5N3hiV05EdFFERzRrNUhBcjNjb0JXRU5fQ2lDZjg&usp=drive_web "
Copy it in mobile memory. and Then install through TWRP. Again now wipe Dalvik Cache and Cache. Restart to System.
Click to expand...
Click to collapse
For StageFright Update:
Make your nandroid backup first.
Now Download this System image from "https://mega.nz/#!LwEXWRLB!NAQBXMwI6aoNNw7VXB_u3m3XjEOSiZ_bUGcbBL1ykTk"
Now flash this system.img through TWRP.
Clear your Cache and Dalvik Cache.
Download the Stagefright System 222.27.5 TWRP backup from the above link
Unzip the Stagefright System 222.27.5 folder to your computer
Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
Reboot your phone into recovery (TWRP)
Click Restore and select the Stagefright System 222.27.5 folder
Verify that the System partition is selected and then Swipe to Restore
Clear your cache
Click to expand...
Click to collapse
Now this update should flash and phone should work fine,
Credits Goes to mastarifla
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.
Credits
All Credits Goes to
XDA-Developers
Ghost_Developer for
http://forum.xda-developers.com/moto-x/themes-apps/ghost-original-bootanimations-unlocked-t3087294
Perseus for
http://forum.xda-developers.com/moto-x/general/index-welcome-to-motorola-moto-x-t2558785
d_shadow for
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
VitaTaf for
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
samwathegreat for
http://forum.xda-developers.com/showpost.php?p=54338871&postcount=2
My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?
Files for getting SPC
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
this in regards to me?
emerica243 said:
this in regards to me?
Click to expand...
Click to collapse
To all of us, happened to me also
fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes
you have to use mfastboot flash system system.img
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2
yar_nl said:
you have to use mfastboot flash system system.img
Click to expand...
Click to collapse
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk
Superpopsss said:
If you're using mfastboot, then yes that's the command.
I'm using android-sdk. For android sdk comand is :
fastboot flash system system.img
Managed to make it work with RSD lite.
Sent from my iPhone 6s Plus using Tapatalk
Click to expand...
Click to collapse
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959
yar_nl said:
See this thread of why use mfastboot for details http://mark.cdmaforums.com/MotoX-mFastboot.htm
---------- Post added at 04:01 PM ---------- Previous post was at 03:53 PM ----------
For those who know their MSL/SPC code see --> http://forum.xda-developers.com/showpost.php?p=63585276&postcount=959
Click to expand...
Click to collapse
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
Superpopsss said:
Good to know, but it's easier to use rds lite then manually flashing all the files needed :
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
Click to expand...
Click to collapse
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/
yar_nl said:
http://www.droidviews.com/restore-moto-x-to-stock-firmware-using-rsd-lite/
Click to expand...
Click to collapse
Exactly, takes 1 min compared to the potential errors you could encounter by flashing manually.
Superpopsss said:
fastboot.exe has stopped working when flashing system.img.
Any one had this problem ?
C:\android-sdk\platform-tools>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Thats all it gives me then crashes
Click to expand...
Click to collapse
Please use mfastboot
emerica243 said:
My Sprint 2013 Moto X just got an update last night and now this is happening to the phone. It has no calling capabilities now but has data. This is also not a developer edition phone so I don't see how iwould be able to do all of this like unlocking the bootloader and all this flashing. It seems like put simply, sprint pushed out an update and bricked my phone in terms of making and receiving calls. Is there no other solution to this? What would they do if I take it to the store?
Click to expand...
Click to collapse
Take it to sprint store is the best solution.
Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
ameraze said:
hi there can u please tell me how to get spc on 4.4.4 motox sprint i would really appreciate ur help
EDIT: got my spc by downgrading to 4.4.2
Click to expand...
Click to collapse
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
flopadmi said:
After flashing the 4.4.4 firmware. Now the device should boot and start the Android. But notice after starting and every restart It automatically checks the Profile and PRL activations. Now time to unlock your Sim.
8. Unlock Sim.
Congrats. U have Sim-Unlocked Moto X Sprint .
9. Flash LolliPop 5.1 "Version: 222.21.15.ghost_row.Retail.en.US"
Now you have unlocked your sim and have Lolipop 5.1 with Stock System Version 222.21.15
10. Remove Boot-loader Warning .
Now You have Sim Unlocked Lolipop 5.1 with Removed Bootloader Warning Message.
Click to expand...
Click to collapse
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
m0ndul said:
For those who needs the SPC, here are the links for the needed files:
4.4.2 TWRP Flashable ROM (thanks to Aaron Nickolopoulos for uploading and sharing the link)
4.4.2 Modem (can be flashed thru RSD Lite or fastboot) (uploaded by me )
Advice for the future: Use EFS Professional to change SPC to 000000
Click to expand...
Click to collapse
hmajid_039 said:
Hi, can you please let me know how did you install 4.4.2 thought TWRP. I downloaded 4.4.2 from the link provided here.
Thanks
MAJID
---------- Post added at 09:38 AM ---------- Previous post was at 09:35 AM ----------
Hello, I followed till step 8, but my phone is still giving sim card error, any other suggestion?
---------- Post added at 09:59 AM ---------- Previous post was at 09:38 AM ----------
Hi,
if i install only 4.4.2 modem file, shall it be helpful to run SPC utility?
and if yes....then do i have to execute all below commands or just the first one?
C:\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'modem' (53804 KB)...
OKAY [ 3.664s]
writing 'modem'...
OKAY [ 2.468s]
finished. total time: 6.134s
C:\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.437s]
finished. total time: 0.439s
C:\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.445s]
finished. total time: 0.445s
Click to expand...
Click to collapse
If u have downloaded 4.4.2 rom then open twrp recovery and click on install.. Then select zip file....
If u have downloaded 4.4.2 firmware then u need to flash through mfastboot or rsd lite...
Yes if u need only to flash modem then please execute the all three commands representing modem...
For unlock sim. Please tell me rather u can enable / disable ur DIAG port with spc code or without soc code ?
Hi, I have 4.4.2 rom with zim file. I did the same through twrp. But after that my phone goes black after showing statrup moto logo/animation..
Currently again i am back on 4.4.4 with sim card error.
And I am also unable to enable DIAG port.
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
Hello, i have a serious problem with my U Ultra.... Last night I unlocked the bootloader, I installed TWRP(lastest version from official site), before all this I made backup (with TWRP) of every partition and then I make back-up of system, data, boot I think, I have everything on my laptop.
But I wanted to back on stock (Don't ask me why...) and i restored a back-up, a full back-up of every partitions. Everything great, but google play didn't had Device Certification: Uncertified like in this pic and I tried to do this method and it didn't worked and I don't know why I thought that if I will relock the bootloader, everything will be okay :| and now I don't have TWRP anymore and of course neither stock recovery, but the stock rom boots but the password I have made it, is not working.
Tried to unlock bootloader but this error shows up
Code:
diesel-X550CL Downloads # fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Now how can I solve this problem?
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
QDT said:
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
Click to expand...
Click to collapse
Through fastboot with this command:
Code:
fastboot oem lock
I don't need it for a special purpose but some apps don't work and I saw that was the solution, anyways I don't need that no more, I just want the phone to work....
Just go to fastboot mode perform oem unlock and reinstall the twrp
QDT said:
Just go to fastboot mode perform oem unlock and reinstall the twrp
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I can't because oem unlock is not turned off
kempactick said:
I can't because oem unlock is not turned off
Click to expand...
Click to collapse
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
QDT said:
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
Click to expand...
Click to collapse
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
kempactick said:
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
Click to expand...
Click to collapse
In what mode are you?
QDT said:
In what mode are you?
Click to expand...
Click to collapse
I'm on download mode, bootloader mod ain't for flashing
kempactick said:
I'm on download mode, bootloader mod ain't for flashing
Click to expand...
Click to collapse
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
QDT said:
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
Click to expand...
Click to collapse
Tried to flash RUU but is not working too, i'm trying with htc sync right now
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
iAlcatrazZ said:
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
Click to expand...
Click to collapse
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
kempactick said:
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
Click to expand...
Click to collapse
I managed to restore my phone :v, I could partially remember how I did it, I'm still gathering resources so that I can write a complete guide for everyone