Develop Bugs

[Guide] Re-lock and Un-root WI-FI Xoom Build HWI69

This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com

first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse

HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally

I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while

I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?

Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work

I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update

what format are these imgs in?
I am trying to unyaffs them but it is not the right format

Your trying to what?

The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk

I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.

Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?

worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..

yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...

Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.

Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt

Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s

need help flash stock image

I am new to android and this is my new first android.
I saw postings yesterday says OTA 4.0.2 rolled out, and people got it already and there are manual way to get it, so I decided try to work on it. I followed the guide how to unlock bootloader and how to root, the first steps went through, but I can get through the last steps because it isays 'waiting for device', i tried everything. somehow I see the bootloader is unlocked.
I installed the stripped 4.0.2 update from here . I used odin mode. now my battery is dropping 1% every few minutes.
I want to flash restore stock image see if I can fix the problem. I trie flash it with odin, but oding crashed.
can anybody help?

Are you running Linux??
Edit:
From Windows or Linux (only tested by myself of Debian Linux) with fastboot in your PATH:
Reboot into bootloader (adb reboot bootloader)
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip

windows.
USB driver is installed when phone is normal mode. but in orin the usb driver does not show.

Moved. Please don't post in the wrong forums.

this is GSM version.
where do you get the image files? also why I can't do in orin?
is there a simple way to flash the factory image directory or any gui tool to do it?

Files are here: http://code.google.com/android/nexus/images.html
Make sure to pick the right one: yakju is GSM and mysid is CDMA
Download the tgz file and extract it (might need winrar on windows IDK)
All the Radio,Bootloader,Recovery and system files are included. The only way I know how to flash these files is fastboot, which imo is a safer way than odin - though I have not really used odin before.

can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.

citrix80 said:
can you explain how to use fastboot. I tried vol-up+down+power, it boot into fastboot, I supose it is, on bottom, it says 'unlocked'. what should I do next?
I am really new to this. I don't want to mess with me device like putting custom rom or stuff. I just want keep it original, it looks better that way. I do not want to add any fancy stuff to it unless they are really good. I used to do tweaks with windows mobile, they had better gui tools to work around make things easier.
Click to expand...
Click to collapse
You need the android sdk installed on your computer. Read this guide:
http://www.xda-developers.com/android/adb-easy-tutorial/
There are also a handful of threads in this very forum answering your same question. A few of which I have given step by step guides myself. Do a quick search.

I downloaded file from
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
and used fastboot, all steps worked out.
here is the log
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-primekj1
0.img
error: cannot load 'bootloader-toro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
j10.img
error: cannot load 'bootloader-maguro-primekj10.img'
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primek
k15.img
sending 'bootloader' (2308 KB)... OKAY [ 0.296s]
writing 'bootloader'... OKAY [ 0.604s]
finished. total time: 0.900s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools>fastboot flash radio radio-maguro-i9250xxkk6.img
sending 'radio' (12288 KB)... OKAY [ 1.545s]
writing 'radio'... OKAY [ 2.375s]
finished. total time: 3.920s
C:\android-sdk\platform-tools> fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
C:\android-sdk\platform-tools> fastboot update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0146882D0601C00A
--------------------------------------------
checking product... OKAY [ 0.007s]
checking version-bootloader... OKAY [ 0.007s]
checking version-baseband... OKAY [ 0.008s]
sending 'boot' (4074 KB)... OKAY [ 0.517s]
writing 'boot'... OKAY [ 0.492s]
sending 'recovery' (4406 KB)... OKAY [ 0.562s]
writing 'recovery'... OKAY [ 0.789s]
sending 'system' (317594 KB)... OKAY [ 39.809s]
writing 'system'... OKAY [ 36.250s]
rebooting...
finished. total time: 78.476s
C:\android-sdk\platform-tools>
the phone reboot automatically after the last step.
the battery is still dropping.
is there a way to reset to 4.0.1? I am not sure what is causing the problem.

I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE

You dont put the files on your phone. They go in the same folder on your computer as fastboot.exe

trilogee said:
I really need someone to help me...Please...im on the verge of suicide here
i unlocked and rooted, dl'd cwm.
i dl'd the SDK package (i dont have platform-tools, i have tools)
i put the cwm image, and the tgz files on the root directory (there no /sdcard)
i turn on usb debugging
i load bootloader
i launch cwm recovery
i navigate to the sdk folder (cd c:/ > cd sdk > cd tools) then type fastboot -w update image-yakju-itl41f.zip and get an invalid command error ..that didnt work so i copied the tgz and cwm file to the folder which contains the adb stuff and try again..same result
PLEASE HELP...i know im an annoying **** n00b thats wasting youre time but ive been at this since 9am PLEASE
Click to expand...
Click to collapse
put files in ur tools folder inside sdk and you fastboot -w update image-yakju-itl41f.zip and get an invalid command error ,,,should of been ,,, fastboot flash -w

oh god didnt realize i got any replies.
so ive gotten past that part now i have a more frustrating problem...installed platforms-tools from the sdk manager, that enable me to get this:
c:\sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >
but when i open the image zip the boot recover and system are there.
the waiting for devices deal, in device manager Android Phone is listed with sub Android ADB interface...driver is installed and device is recognized...why does it still say waiting for device...thank you guys so much.
If I get this working today I promise I will make a small donation to both xda and those that help me.

you need open the zip then extra the tar inside it with 7 zip, then copy all 4 extracted file into sdk folder, or same folder with fastboot. then run fastboot. you can use my output in page 1. type exact same thing.

trilogee
How sure are you that the phone is in bootloader mode at the time of flashing? Try executing fastboot devices first to confirm that fastboot can see the phone...Then what the OP has suggested above or do what you were doing.

Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)

trilogee said:
Hey I think I explained this in another post, not sure where, but fastboot devices initiates a blank command line. Doesn't show anything...which is odd though because I downloaded the right drivers from Samsung, it's recognized on my computer and it worked with ODIN (although updating through odin actually bricked me and forced me to restore)
Click to expand...
Click to collapse
If fastboot is showing a blank command line, then it means that it can't see your phone. Anything done after that is not going to work. It could then be one of two things, i.e. either your setup is not correct or your phone is not in bootloader mode. Can adb see the phone normally from your PC, i.e. can it see it when you call 'adb devices' or can you see the logcat output?
With the former, I can suggest that you check if the installation is correctly done? As with the latter, I tend to get adb to reboot the phone in bootloader by issuing a 'adb reboot bootloader' and is far quicker than the button-press option.

did you install sdk and driver? when your phone in normal mode, plug in usb to pc, in device manager, you see android driver?

I tried again. whe I get here
C:\android-sdk\platform-tools>fastboot -w update image-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but the files are actually in the zip file.
the process still finished.
did it skip those files?

I think that has something to do with the .sig verification settings
..same thing happened to me but image flashed fine and everything seems to be running smoothly. Crazy how I struggled with this so much at first its actually an extremely simple process.
Sent from my Galaxy Nexus using XDA App

Samsung Galaxy Nexus SCH-I515 Will not go past google start screen

The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.

joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
the lock symbol means your phones bootloader has been unlocked allowing for custom development. i assume you have bought the device second hand as you obviously didnt unlock it yourself.
to make your phone boot i suggest cleaning your devices cache.
-power off device
-hold power up+down while pressing power button
-use the volume buttons to scroll down to recovery and press power to select
-after google logo disappears a little android with a blue thingy will come up, at this point hold the power button then press volume up and another selection screen will come up.
-select clean cache and then press power to select. when this is done reboot your device.
im not 100% sure this is your problem but its worth a try.

I was stuck at the same screen this morning. I tried booting into CWM Recovery from Jelly Bean and my phone wasn't having any part of it. I kept waiting and eventually pulled the battery. Luckily, I was able to boot into the ROM on my second battery pull. I doubt this helps though, just my two cents.

joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
me too same problem.how to solve?
can you tell me about this?or Anybody have..?

Boot into boot loader. Flash stock. Flash clockwork. Flash a rom that works

Yes had the same issue. I had to walk away and give it time and I came up.
How long have u let it go?
Sent from my Galaxy Nexus using xda app-developers app

animal24 said:
Boot into boot loader. Flash stock. Flash clockwork. Flash a rom that works
Click to expand...
Click to collapse
Thanks to reply
but i don't understand about flash. i can do fastboot mode only then...............what do? which software help me to flash?
i download [mysid-icl53f-factory-65895fa8.zip] file from goo.im but this is zip file.no software.
so please help me out.

sattar_00977 said:
Thanks to reply
but i don't understand about flash. i can do fastboot mode only then...............what do? which software help me to flash?
i download [mysid-icl53f-factory-65895fa8.zip] file from goo.im but this is zip file.no software.
so please help me out.
Click to expand...
Click to collapse
the newest released stock images are here https://developers.google.com/android/nexus/images
down towards the bottom should be imm76k for the mysid
its a zip, but inside, there is a bootloader, 2 radios, and a system image, maybe some other tidbits
so just unzip it to the same directory as your fastboot.exe
assuming you're unlocked.
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
after that i always boot into recovery and do another factory reset, but thats me.
enjoy!

animal24 said:
the newest released stock images are here https://developers.google.com/android/nexus/images
down towards the bottom should be imm76k for the mysid
its a zip, but inside, there is a bootloader, 2 radios, and a system image, maybe some other tidbits
so just unzip it to the same directory as your fastboot.exe
assuming you're unlocked.
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
after that i always boot into recovery and do another factory reset, but thats me.
enjoy!
Click to expand...
Click to collapse
on fastboot mode show follow status on screen
Code:
FASTBOOT MODE
PRODUCT NAME-tuna
VARRIANT -toro
HW VERSION-9
BOOTLODER VERSION-PRIMKK15
BASEBAND VERSION-I515.EK02 CDMA-I515.EK05
CARRIER INFO-NONE
SERIAL NUMBER-0146970F11019005
SIGNING-production
LOCK STATE-UNLOCKED
so i download [mysid-icl53f-factory-65895fa8]
but while flashing stop on
sending 'boot' (4074 KB)...
OKAY [ 0.420s]
writing 'boot'...
full log is
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\sattar>cd C:\Users\sattar\Desktop\mysid-icl53f
C:\Users\sattar\Desktop\mysid-icl53f>fastboot-windows
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
< waiting for device >
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.830s]
finished. total time: 21.074s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.069s]
writing 'radio'...
FAILED (remote: Unknown Partition)
finished. total time: 1.082s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.061s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 42.821s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot -w update image-mysid-icl53f
error: failed to load 'image-mysid-icl53f'
C:\Users\sattar\Desktop\mysid-icl53f>fastboot -w update image-mysid-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I515.EK02
Serial Number........: 0146970F11019005
--------------------------------------------
checking product...
OKAY [ 0.008s]
checking version-bootloader...
OKAY [ 0.009s]
checking version-baseband...
OKAY [ 0.009s]
checking version-cdma...
OKAY [ 0.009s]
sending 'boot' (4074 KB)...
OKAY [ 0.420s]
writing 'boot'...
what happean this?

You skipped the part where it was suggested to go download the IMM76K image. I'd start there. You're trying to flash an older build.

Cilraaz said:
You skipped the part where it was suggested to go download the IMM76K image. I'd start there. You're trying to flash an older build.
Click to expand...
Click to collapse
still no luck. try all image but not sucess. what i do?

sattar_00977 said:
still no luck. try all image but not sucess. what i do?
Click to expand...
Click to collapse
Try flashing the images one by one, instead of using "fastboot update". See here.

efrant said:
Try flashing the images one by one, instead of using "fastboot update". See here.
Click to expand...
Click to collapse
really i am a fool. i can't understand even many people teach me.
i extract all file like this on desktop.
Uploaded with ImageShack.us
it,s right?
Then first i write bootloader
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.832s]
finished. total time: 21.075s
Click to expand...
Click to collapse
it's done
then try radio it take upto 1 hour but not sucess
this time show fastboot status --flash radio on buttom of screen
i wait upto 1 hour but sucess then i remove
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\sattar>cd C:\Users\sattar\Desktop\mysid-icl53f
C:\Users\sattar\Desktop\mysid-icl53f>fastboot-windows
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\sattar\Desktop\mysid-icl53f>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.009s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot reboot bootloder
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\sattar\Desktop\mysid-icl53f>fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash bootloader bootloader-toro-p
rimekk15.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.241s]
writing 'bootloader'...
OKAY [ 20.832s]
finished. total time: 21.075s
C:\Users\sattar\Desktop\mysid-icl53f>fastboot flash radio radio-toro-i515.ek02.i
mg
sending 'radio' (10496 KB)...
OKAY [ 1.067s]
writing 'radio'...
Click to expand...
Click to collapse

sattar_00977 said:
really i am a fool. i can't understand even many people teach me.
i extract all file like this on desktop.
it,s right?
Then first i write bootloader
it's done
then try radio it take upto 1 hour but not sucess
this time show fastboot status --flash radio on buttom of screen
i wait upto 1 hour but sucess then i remove
Click to expand...
Click to collapse
I can't view your screen shot. It's too small.
Your reboot command didn't work because you are missing the dash. It is "fastboot reboot-bootloader" not "fastboot reboot bootloader".
Not sure why the radio is not flashing for you. Try skipping it and move to the next image.
Sent from my Galaxy Nexus using Tapatalk 2

I have this same but problem but I tried what Efrant suggested doing from the bootloader and it appeared to work, my phone booted up and was back to stock. I continued to test restating it and it would go through the google splash screen only about 5-10 times to boot, so i thought that it was fine and continued to use my phone throuhgout the day.
Well I restarted it again later and it went right back into the bootloop. I flashed to stock again following Efrants directions and it worked for a little but soon went back into the bootloop.
What else can I do? I dont want to have to get a new one through Asurion because you never know what kind of ****furb you'll get and its 50$..
Don't mean to hijack but I can't find answers anywhere else!

jigawut said:
I have this same but problem but I tried what Efrant suggested doing from the bootloader and it appeared to work, my phone booted up and was back to stock. I continued to test restating it and it would go through the google splash screen only about 5-10 times to boot, so i thought that it was fine and continued to use my phone throuhgout the day.
Well I restarted it again later and it went right back into the bootloop. I flashed to stock again following Efrants directions and it worked for a little but soon went back into the bootloop.
What else can I do? I dont want to have to get a new one through Asurion because you never know what kind of ****furb you'll get and its 50$..
Don't mean to hijack but I can't find answers anywhere else!
Click to expand...
Click to collapse
That is very strange. If you successfully flashed ALL the stock images as per that guide, and the device boots properly, but you are still getting bootloops, it is either an app that you have installed that is causing it, or a hardware issue.

finitestruggle said:
the lock symbol means your phones bootloader has been unlocked allowing for custom development. i assume you have bought the device second hand as you obviously didnt unlock it yourself.
to make your phone boot i suggest cleaning your devices cache.
-power off device
-hold power up+down while pressing power button
-use the volume buttons to scroll down to recovery and press power to select
-after google logo disappears a little android with a blue thingy will come up, at this point hold the power button then press volume up and another selection screen will come up.
-select clean cache and then press power to select. when this is done reboot your device.
im not 100% sure this is your problem but its worth a try.
Click to expand...
Click to collapse
Doesn't this mean he is locked, not unlocked.the lock symbol has to be one of an open lock.this could be why flashing falls.
joester818 said:
The phone will power on with a google logo and on the bottom of the screen a lock symbol. Anyone ever deal with something like and maybe have a solution.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk 2

koftheworld said:
Doesn't this mean he is locked, not unlocked.the lock symbol has to be one of an open lock.this could be why flashing falls.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If it was locked there would be no symbol

efrant said:
That is very strange. If you successfully flashed ALL the stock images as per that guide, and the device boots properly, but you are still getting bootloops, it is either an app that you have installed that is causing it, or a hardware issue.
Click to expand...
Click to collapse
Yes I'm pretty sure all the images flashed succesfully but when i did the last one it said something about something not being available, not home right now or else I'd check. I really hope this isnt a hardware problem but I don't see how it could be. When it started doing this I was downloading a bunch of files on my phone at work and it randomlly restarted and went into the bootloop. Is there anything I could try before getting a replacement?

how many time take for flashing?
i need tested working fastboot.exe for window.

Steps to flash Android 4.3 factory image without losing data

NOTE: Bootloader should be unlocked for this method to work. Root not required.
1) Download the factory image relevant to your Galaxy Nexus from the below page.
https://developers.google.com/android/nexus/images#takju
2) Unzip the .tgz file and keep it under, say C:/
3) Edit the "flash-all.bat" and remove the "-w" parameter from "fastboot -w update image-takju-jwr66v.zip"
4) Delete "userdata.img" from "image-takju-jwr66v.zip".
5) Copy fastboot.exe file into the “takju-jwr66v” directory.
6) Reboot and keep the phone in fastboot mode. [ a) Turn on USB Debugging b) Turn off your Phone c) Hold down Volume UP + Volume Down + Power buttons ]
7) Issue the command "flash-all.bat".
8) Wait for the process to finish, and then the Galaxy Nexus will reboot upgraded with stock Android 4.3
9) Cheers and enjoy !!!
Logs below for even better understanding
=========================================
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>dir
Volume in drive C is OSDisk
Volume Serial Number is C49E-94F0
Directory of C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v
07/24/2013 11:25 PM <DIR> .
07/24/2013 11:25 PM <DIR> ..
05/07/2010 11:48 AM 578,611 adb.exe
05/07/2010 11:48 AM 96,256 AdbWinApi.dll
05/07/2010 11:48 AM 60,928 AdbWinUsbApi.dll
07/12/2013 03:56 AM 2,363,392 bootloader-maguro-primemd04.img
05/07/2010 11:48 AM 336,613 fastboot.exe
07/24/2013 11:08 PM 953 flash-all.bat
07/12/2013 03:56 AM 956 flash-all.bat.bak
07/12/2013 03:56 AM 827 flash-all.sh
07/12/2013 03:56 AM 785 flash-base.sh
07/24/2013 11:09 PM 295,614,131 image-takju-jwr66v.zip
07/12/2013 03:56 AM 12,583,168 radio-maguro-i9250xxlj1.img
11 File(s) 311,636,620 bytes
2 Dir(s) 7,925,932,032 bytes free
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>
C:\gn4life\takju-jwr66v-factory-c2ef855e\takju-jwr66v>flash-all.bat
sending 'bootloader' (2308 KB)... OKAY [ 0.314s]
writing 'bootloader'... OKAY [ 1.478s]
finished. total time: 1.793s
rebooting into bootloader... OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.675s]
writing 'radio'... OKAY [ 1.856s]
finished. total time: 3.532s
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BDCB0D012016
--------------------------------------------
checking product... OKAY [ 0.006s]
checking version-bootloader... OKAY [ 0.008s]
checking version-baseband... OKAY [ 0.007s]
sending 'boot' (4376 KB)... OKAY [ 0.709s]
writing 'boot'... OKAY [ 0.506s]
sending 'recovery' (4924 KB)... OKAY [ 0.662s]
writing 'recovery'... OKAY [ 0.689s]
sending 'system' (479244 KB)... OKAY [ 65.013s]
writing 'system'... OKAY [ 48.280s]
rebooting...
finished. total time: 115.913s
Press any key to exit...

So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

beekay201 said:
So it's not just my bootloader that got slower. Yours also made you <waiting for device> each time the process rebooted the bootloader. It never happened before.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
yessssssssssss worked for me

Caused a bootloop for me and when I tried to reboot in recovery I got red triangle and Android. Didn't give any error messages.
Am just going to do full wipe now and retry.

Worked like a charm
Did what the post said and got 4.3 without losing any data.
Thanks!

Color me suspicious, but I bet there's a good reason that the -w is there...

flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?

I did get a bootloop by this method until I flashed by loosing data

omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop

banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
I have updated my original post with this info. Thanks...

theillustratedlife said:
Color me suspicious, but I bet there's a good reason that the -w is there...
Click to expand...
Click to collapse
Got bootloop so I did full wipe and lost all data but all works fine.
omegagt said:
I did get a bootloop by this method until I flashed by loosing data
Click to expand...
Click to collapse
Same.
banditnich said:
your gnex must be unlock to do this flashing process, maybe that's why you get the bootloop
Click to expand...
Click to collapse
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

sui785 said:
Got bootloop so I did full wipe and lost all data but all works fine.
Same.
My GNex hasn't even been carrier locked(they don't do that in Belgium) and my bootloader has been unlocked since I got this phone.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Unlock refers to the bootloader not to carrier locking.

banditnich said:
flash successful without losing data.. but camera lag still exist on my gnex, and vitamio got multiple crash after rebooting. Anybody got the same experience?
Click to expand...
Click to collapse
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.

I updated my UNLOCKED takju like this, and it seems to work ok:
- Download and unpack takju-jwr66v-factory-c2ef855e.tgz to some folder (gives you a subfolder called takju-jwr66v)
- Unpack file image-takju-jwr66v.zip (found in folder above, gives you files boot.img, recovery.img, system.img ..)
- Connect phone, make sure to activate debugging first
- Check with command adb devices , this should show you an id for your phone
Something like this:
List of devices attached
0149C25E0A011009 device
Go to folder takju-jwr66v and issue commands below
- fastboot flash bootloader bootloader-maguro-primemd04.img
- fastboot reboot-bootloader
- fastboot flash radio radio-maguro-i9250xxlj1.img
- fastboot reboot-bootloader
Go to folder image-takju-jwr66v
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash system system.img
- fastboot reboot
DO NOT flash userdata.img !!

Gryph Lionheart said:
Mine is still lagging when screen rotates, but if you deactivate screen rotation it works just fine.
Click to expand...
Click to collapse
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.

banditnich said:
So I'm not the only one with the lagging camera bug, well camera work fine too with screen rotation disabled on 4.2.2.
Camera bug supposed to be fix in 4.3... maybe must do clean flash will do the trick...
But I'm too lazy to do backup and restore all apps and data on my phone right now, and already used to using another camera apps lately so the bug doesn't bother me that much to do clean flash all over again.
Click to expand...
Click to collapse
Everything is working fine for me. No bugs.

This isn't working for me.
I typed in adb reboot bootloader to get into fast boot.
Then I ran the flash-all.bat file and it said "AdbWinApi.dll" not found. After adding this .dll to the folder a command shell opens with "waiting for device". Already turned on USB debugging and connected it to PC.
One issue though is that even though USB debugging is on, I can still connect to the phone as a media device and see all my files. I think you're not supposed to be able to access the phone's file while USB debugging is on.
So basically all the bat file does is has it stuck on "waiting for device." Although in fastboot if I type in "fastboot devices" it shows something like "X57U31581759 fastboot".
------------- Update ------------
So after watching a few youtube videos I found the problem: bad original instructions.
First the phone is to be on ANDROID, connected to the computer with USB debugging on. You can check to see if the device is connected using: adb devices
Then click the .bat file and it'll say "waiting for devices". Then I use another command shell and typed in : adb reboot bootloader to get into fastboot. This makes the .bat file work successfully.
If you start the procedure already rebooted into fastboot like steps 6 & 7 suggests, you'll be stuck on "waiting for devices" all day. Basically step 7 should be done before step 6.

Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.

beekay201 said:
Something wrong then, because I use flash-all.sh directly from fastboot, never had such an issue.
Click to expand...
Click to collapse
Mine too, never had such issue. The flash all bat file executed from fastboot and its working flawlessly.
Sent from my Galaxy Nexus using Tapatalk 4

Didn't work for me either... Got bootloop... I had to wipe everything.

[DEV][N][DP2][CRACKLING]Android N Developer Preview

Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?

No root and OTA.
Before flashing via fastboot wipe data through twrp.

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot

http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions

Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing

Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?

I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.

cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected

Can I use this TWRP? I did not found Wileyfox Swift among supported devices.

cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.

Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?

Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.

I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?

yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)

yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.

mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get