Related
Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Another note... If I boot into Recovery and adb push a file to the /sdcard, the transfer looks like it completes, but when I go to flash zip in recovery it gives me an E: Can't mount /sdcard/. Same thing if I go to the mounts and storage option and try to mount /sdcard.
Any ideas guys? Never seen this before.
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Mr. Monkey said:
Update... Just rebooted into bootloader and tried:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-jro03d-factory-e102ba72\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 3.34
Baseband Version.....: N/A
Serial Number........: 015d256898080e19
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4890 KB)...
OKAY [ 0.608s]
writing 'boot'...
OKAY [ 0.390s]
sending 'recovery' (5234 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.343s]
sending 'system' (438656 KB)...
FAILED (unknown status code)
finished. total time: 3.292s
That's the most progress I can get. System seems to fail though. Tried multiple times.
Click to expand...
Click to collapse
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
comminus said:
The "archive does not contain *.sig" messages are normal. The FAILED messages on sending the system image is disconcerting. Use the platform tools from Google which includes fastboot. http://dl-ssl.google.com/android/repository/platform-tools_r16-windows.zip
There is a .bat file in the factory image archive that you can run to return to stock. If you don't want to run that, at least open it up and manually run the commands in sequence.
Click to expand...
Click to collapse
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Mr. Monkey said:
I think that's the same thing I've been trying. I did download Google's platform-tools and try with that and still got the same error. Seems like I can't write to /system. Can't even erase it:
c:\android\platform-tools>fastboot.exe flash system C:\android\nakasi-jro03d\ima
ge-nakasi-jro03d\system.img
sending 'system' (438656 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.094s
c:\android\platform-tools>fastboot.exe erase system
erasing 'system'...
FAILED (command write failed (Unknown error))
finished. total time: 0.733s
c:\android\platform-tools>fastboot.exe format system
formatting 'system' partition...
FAILED (command write failed (Unknown error))
FAILED (command write failed (Unknown error))
finished. total time: 0.889s
What are my options? Flash stock recovery, re-lock bootloader and send it in for an RMA? Anyone else know what to try?
Click to expand...
Click to collapse
Two more thoughts - 1. try updating drivers. 2. verify the sha1 hash of the factory image
Did you try switching to a different usb port? Just a thought is all.
Wow. Can't thank you guys enough. Thought this was toast. I ended up trying all of the above, haha. Even though I had done it several times. I tried multiple computers, multiple factory images, multiple programs, multiple USB ports. But somehow, maybe your encouragement, something helped. I'll watch it and make sure nothing seems fishy, because I don't know how in the world that worked.... but it did. Thank you very much.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Hi there
I was having the same problem but when I try to flash the system.img (or the 'image-nasaki-jop40d.zip file too for that matter) I get the following error:
"error: cannot load 'system.img': Not enough space
I have done ALL the steps found in this guide without any issues until I get to that part
Help please my wife just gave me this N7 for christmas and I can't believe I may have just bricked it!!
My solution
I understand this is an old thread but I came across it when I was having the same issues earlier today.
Oddly, using the USB cable that came with the N7 seemed to fix the multiple "FAILED" I was getting.
Using my Samsung USB cable seemed to cause the issues.
Hope this can be a solution to others that may come by this thread by googling the issue.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
This one helped me!:good::good::good:
Thanks a lot.
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Works, thanks. :good:
Unlock bootloader
Mr. Monkey said:
Hey guys. My brother got himself a Nexus 7 which is his first Android, and he was playing with some tweaks or mods or something and tried flashing via recovery and has messed something up. I have tried using the Toolkits as well as doing it manually with fastboot. I am able to flash a recovery and use that, but lose it after boot (the permanent option doesn't seem to stick). But, when I try to do a factory restore with the google image, it doesnt matter if i'm doig it manual or with the toolkit, the all respond with a "archive does not contain... " boot.sig, recovery.sig, or system.sig. Here is my output:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe -w update "C:\Users\monkey\nakasi-
jro03d\image-nakasi-jro03d.zip"
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.836s
Even if I do them manually, one at a time:
C:\Google Nexus 7 ToolKit>fastboot-toolkit.exe flash boot nakasi-jro03d\image-na
kasi-jro03d\boot.img
sending 'boot' (4890 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.858s
I have also tried pushing a stock rom .zip to the /sdcard and it doesnt seem to make it either.
Feels like internal memory is corrupt. Any thoughts or ideas I can try? Also... should any custom recovery allow adb access? TWRP or CWM Touch don't seem to work.
Click to expand...
Click to collapse
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
nexus 7 (mobile)
shap4th said:
You need the bootloader to be unlock. First run the command " fastboot oem unlock " . It works flawlessly after that! Awesome!
Click to expand...
Click to collapse
Hi!
I bought a second hand nexus 7 rooted. I had a problem with updating os via wifi because it doesn't update. some kind a problem. I tried to do a hard reset hoping I could just restore the device manually but I messed up so I am now stuck with just a google logo and can only access bootloader with start, bootloader, restore and power off option. I don't know what to do. please help me. I am not a tech person but if you can give me a specific instructions, I know i can manage. i saw a lot off post here that they were able to restore their device so I have faith in this site and the members are highly recommended.
thank you in advance
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks man! This works for me..
manasgirdhar said:
Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc.
Click to expand...
Click to collapse
Thanks. This one works for my friend.
Same case, solved on spanish forum.
/showthread.php?t=748207 on htcmania(dot)com
*Note: damn spam filter
Try this website. If you have any question ask me.
You will need to install files one by one.
SImply open flash bat file see what they are doing. and do same but one by one.
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
Similar issue, please help
I'm using ubuntu 14.10 LTS. I had the same issue arise so i listened reextracted (even though boot.img, system.img & recovery.img were within .zip but im still getting "critical error: extent_create_backing: calloc: Cannot allocate memory
Mmap:invalid argument
Cannot generate image
FAILED()"
Anyone has a suggestion?
---------- Post added at 11:49 PM ---------- Previous post was at 11:18 PM ----------
So as my previous and maybe above msg said i was just about to attempt adb sideload to manually update to lollipop... From the bootloader i entered recovery... My nexus 4 shut down & got stuck @ wild new boot animation for lollipop. I waited 5 minutes while the fantastic yellow, red, blue & green orbs whizzed around, shut my 4 down & now "Android is upgrading... Optimizing app x of 68." How wild is this... But i still have to lock bootloader. Hopefully it doesnt screw anything up... I'll report back asap
---------- Post added 24th November 2014 at 12:19 AM ---------- Previous post was 23rd November 2014 at 11:49 PM ----------
So I relocked bootloader... Sent several test sms & so far so good. Wifi of course works, haven't tested bluetooth but ill report back. Boy I got lucky. No more linux for me... Jk
Everything You may need to install android 5.0.1
I'm writing this so that you all will not have to go through what I just experienced when trying to flash the android 5.0.1 OTA manual update. Here are some of the errors I've gotten out of and I will give you some tips to get fix these. I always seem to encounter issues that no one else has when flashing, so here we go.
Tip 1
1.)If you are trying to flash 5.0.1 (tip applies to any version) from the google website here: https://developers.google.com/android/nexus/images ....Make sure your computer can handle ".tgz" files. This took me a day and a half to figure out. If you try to download one of the files off this website without the proper software to do so you will simply get a ".tgz" file that you cannot extract the necessary files from.
*The solution is to download winrar from http://www.win-rar.com/predownload.html?&L=0 this website. Once you do and run it the ".tgz" file will become a folder (icon should look like stacked books) and you can proceed to actually follow the instructions on the page where you downloaded the file from. I learned this the hard way.
Tip 2
If you dont really understand how to us the "ADB" tools or "SDK" and everything related sounds like a foreign language to you then watch this video: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/. It will explain how to copy files to your device while in bootloop. Pay special attention to the part about making sure your drivers are set up correctly. Drivers always get me when I installs. This knowledge will transfer over to downloading any rom or factory image in the future.
Links for Moving files to your device while in recovery:
Here are the appropriate drivers for copying files while in recovery to the nexus 5:
http://downloadandroidrom.com/file/drivers/Android/usb_driver.zip
Here is the fastboot link: http://downloadandroidrom.com/file/tools/fastboot.zip
Tip 3
The way I installed android 5.0.1 was:
1.)I downloaded the file from the google developer website that i pasted at the top
2.)I moved that file to a folder named "root" that i created on my desktop
*In this folder i have chainfire auto root http://autoroot.chainfire.eu/ in case i need to re-root my phone, I have the adb and fastboot.zip folders in my root folder as well.
3.)I moved the folder inside the FASTBOOT folder and extracted the file that i got from the developer website here. Once this is down there is another
3.)I extract the files here. After you extract there should be another folder called "image-hammerhead-lrx22c.zip." I copied those files to the fastboot folder as well so that they are outside of the zip file. I did not remove the zip file once I copied the insides to the outside. Right or wrong this is what I did.
4.)I used the Command prompt to navigate to this directory. Watch the how to copy files video to see how to navigate using the "cd" command
*basically i typed "cd desktop" which means change directory to the desktop. Then i did "cd root"....then "cd fastboot" ...YOUR PATH MAY BE DIFFERENT.
5.)Once i was here i could follow more of the instructions on the developer website. I could run that "flash-all.bat" command to begin flashing the 5.0.1. In order to run this command you literally type "flash-all.bat."
6.)After it finished it said,
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
helpful links: http://forum.xda-developers.com/showthread.php?t=1992063
This was okay, what you dont want is falures. While 5.0.1 is being installed, if you notice it say failure in the place where everything else is saying "OKAY" you have a problem. One guy on that xda link said:
"Extract the zip.You will get another file..extract that...keep extracting all the files till you get system.img, recovery.img, boot.img, etc ..then boot into bootloader and Manually flash all the img files
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img"
You can type this into cmd and do each one by one and it may work.
7.)YOU MUST MAKE SURE TO EXTRACT THAT SECOND FOLDER inside the developer file! If you don't you will get failures because the program is looking for them. That's why manually installing them may work as well.
8.)IF YOU SEE THE ANDROID WITH NO LOADING BAR UNDERNEATH this does not mean that you are bricked. I thought it did and kept flashing 5.0.1 over and over and over again. Then i just waited a bit and my phone rebooted and i say the glorious dots rotating on my screen. I lived happily ever after.
9.)Once you are finished installing 5.0.1 you will loose root. Run that chainfire auto root program.You have to boot in to the bootloader screen...NOT RECOVERY...just the screen where you see the android and you can select "start" "recovery" etc. and open up that chainfire program and hit a key to start it. There are instructions on the actual program if you need help. If you are on the bootloader screen that i am talking about and you start the program it will "auto root" that is, automatically root your phone and thats that.
10.)Download root checker off the play store to see if you are actually rooted and have a blessed day. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Let me know if you need further explanation. I'm no pro but I've failed in soooo many ways i probably could help ya out! Jesus loves you all!
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
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!
Hello,
I have a Mi A1 since one week and I have already a large problem.
The problem began with a basic crash on an app (Facebook). The phone didn't respond and I turned off the phone.
When I turned on, the phone was stuck on the boot image (White screen with Mi Logo and Google colors). I tried to turn off and on several times but it didn't work.
I opened the phone and disconnected the battery but always the same problem.
Then, I booted the phone in fastboot and unlocked it via the command fastboot oem unlock. Then I tried to flash the stock ROM via fastboot. I choosed this version : Android 7.1.2 Nougat (N2G47H.7.12.7) because I had the last update (from : https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/).
Immediately i have this error :
Code:
fastboot flash modem_a C:\Users\Lau\Desktop\tissot_images_7.12.7_7.1\images\modem.img ||
target reported max download size of 536870912 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 2.466s]
writing 'modem_a'...
FAILED (remote: flash write failure)
finished. total time: 2.499s
"Flash modem_a error"
I tried to flash with Miflash tool 2017.7.20 but I have the same message, Flash modem_a error.
I also tried to boot the phone in EDL Mode with fastboot_edl, the phone reboot, I have a message your device software cannot be checked for corruption and then the boot screen (with the messsage "Unlocked") and after 30 seconds, I have the black screen with the droid and "No command" (https://scache.vzw.com/kb/images/google/pixel/android_system_recovery_no_command.jpg )
Someone should have an idea to restore the phone ?!
Thanks a lot !
That screen with "No command" is usually related to the recovery. If I remember well, once in that screen, you have to press and hold power button for few seconds then press and release volume up button to enter in recovery. By reading your post I can see you didn't even try the most easy thing: A factory Reset! Try to wipe data from recovery if you can enter in it.
The modem error could be related at the fact that you're flashing a firmware that is not global or for your country. Try to change firmware version and make sure it is the right firmware region.
Inviato dal mio G8141 utilizzando Tapatalk
Thank for the quick answer.
I thinked to the recovery but I didn't know how to acces. With your help, I found and I made a wipe data. It made 5 minutes I have the message Formatting /data.... It seems too long... :/
EDIT : I stopped the wiping, it's seems it was block.
When you spoke of an other firmware, do have you a link ? Here is the information of my phone
Code:
xiaomi/tissot/tissot_sprout
71.2/N2G47H/7.12.19
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
lolo1410 said:
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
You must flash to system_a or system_b, "system" partition really doesn't exist.
Indeed, it's work now, it's flashing !
I noticed that for TWRP, there is also a "slot A" and "slot B". Is it new in Android ? Is there 2 kind of system ?
EDIT :
Unfortunately, it didn't work...
I had this message :
C:\adb_new>fastboot flash system_a system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (522959 KB)...
OKAY [ 15.867s]
writing 'system_a' 1/6...
FAILED (remote: flash write failure)
finished. total time: 15.898s
And here is the log for Miflash :
Code:
[16:52:10 28ba25530704]:MiFlash 2017.7.20.0
[16:52:10 28ba25530704]:image path:C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1
[16:52:10 28ba25530704]:env android path:"C:\Users\Lau\Desktop\miflash\Source\ThirdParty\Google\Android"
[16:52:10 28ba25530704]:script :C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\flash_all_except_storage.bat
[16:52:10 28ba25530704]:Physical Memory Usage:1355776 Byte
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
[16:52:10 28ba25530704]:product: tissot
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 oem unlock ||
[16:52:11 28ba25530704]:...
[16:52:11 28ba25530704]:$fastboot -s 28ba25530704 flash modem_a C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\images\modem.img ||
[16:52:11 28ba25530704]:(bootloader) Device already : unlocked!
[16:52:11 28ba25530704]:eek:KAY [ 0.030s]
[16:52:11 28ba25530704]:finished. total time: 0.030s
[16:52:13 28ba25530704]:target reported max download size of 536870912 bytes
[16:52:13 28ba25530704]:sending 'modem_a' (86016 KB)...
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:"Flash modem_a error"
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:process exit.
[16:52:13 28ba25530704]:flashSuccess False
[16:52:13 28ba25530704]:isFactory False CheckCPUID False
[16:52:13 28ba25530704]:before:flashSuccess is False set IsUpdate:True set IsDone True
[16:52:13 28ba25530704]:after:flashSuccess is False set IsUpdate:false set IsDone true
Can you boot into TWRP (use version 3.1.1-0 or 3.1.1-1 "fastboot boot twrp.img")? Do you see /data partition?
Yes I can boot into but I can't install it. Before I tried to flash manually, I was able to unlock the data partition but not anymore (Error : E: Decrypt took too long, killing process - Failed to decrypt data)
I have an access with adb shell.
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
_mysiak_ said:
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Click to expand...
Click to collapse
I flashed "persist.img" succesfully but always the same problem, stucked on Boot...
zeyaan said:
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
Click to expand...
Click to collapse
I already tried several times but I have always errors (See log of previously post). With Miflash, I succeeded to flash the 2 boot et 2 system but phone is always blocked.
I tried to wipe via TWRP but it blocks on "Formatting Data using make_ext4fs...".
I think I'm good to send it at a service center...
There's a TWRP backup of first beta build oreo.Try restoring it.
Same Problem.
inally he managed to flash the ROM action, thank you very much to everyone for your patience and help, especially PALMATRON and fosco_
He used the tutorial of this link: https://xiaomifirmware.com/roms/down...-xiaomi-mi-a1/
1. Tools Download r26 for Windows.
2. Unzipped the instruments on disk C of my computer.
3. Unzipped the files of the last ROM available for the Xiaomi Mi A1 in the folder C: \ Tools so that the Images folder and the flashing scripts that come with the ROM are included in it.
4. Then double click on flash_all.bat to delete everything and just leave the boot loader open.
5. Automatically start flashing and take about 10-15 minutes and voila!
https://uploads.tapatalk-cdn.com/20171123/37d3867bf5d0fb7967a03a05869914ae.jpg
Try do with clean and lock or just clean i was have the same problem and i fix this only with miflash and after when my mi a1 restarts on boot i copy with terminal persist.img
thanks a lot
Saved my life, thanks. The rom on this link works PERFECTLY - my Mi A1 was stuck on botlooping after a fail tentative to root it.
XDVRMX said:
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Click to expand...
Click to collapse