Hey all,
Just nuked my phone set up so I could install the latest doomkernel (first time wanted to try it out) on my GSM play running latest SE software, but it refuses to flash the boot.img file to the device.
I unlocked (after a re-lock a while ago) the boot loader and can access fastboot (blue LED on phone, "fastboot.exe -i 0x0fce getvar version" brings a version 0.3)
fastboot.exe flash boot boot.img ---> stuck on "< waiting for device >" message
I tried with the latest flashtool and I got this from the log:
Code:
05/046/2012 00:46:31 - INFO - Device connected in fastboot mode
05/046/2012 00:46:42 - INFO - Selected kernel (boot.img or kernel.sin): C:\boot.img
05/046/2012 00:46:42 - INFO - Flashing selected kernel
05/046/2012 00:46:43 - INFO - FASTBOOT Output:
sending 'boot' (7330 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
I then rooted the phone using zergrush and it's rooted properly, but I can't for the life of me figure out why I can't push the kernel, since I know the fastboot process is working because I used it to unlock the boot loader
Code:
C:\Users\Access\Downloads>fastboot.exe -i 0x0fce oem unlock 0x
< waiting for device >
... INFOUnlock phone requested
INFOErasing block 0x00000d00
INFOErasing block 0x00000e00
INFOErasing block 0x00000f00
Is there something I'm missing or will I never be able to have a custom kernel?
Any ideas and suggestions appreciated thanks
I have the exact same problem with my Arc S, can`t figure out why is getting stuck on "< waiting for device >"
Try fastboot -i 0x0fce flash boot boot.img
Michealtbh said:
Try fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
Thx alot man, it worked like a charm !
Code:
C:\Android>fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (7922 KB)... INFOUSB download speed was 9187kB/s
OKAY [ 0.892s]
writing 'boot'... INFODownload buffer format: boot IMG
INFOFlash of partition 'boot' requested
INFOS1 partID 0x00000003, block 0x00000280-0x000002e3
INFOErase operation complete, 0 bad blocks encountered
INFOFlashing...
INFOFlash operation complete
OKAY [ 1.532s]
finished. total time: 2.424s
Related
Hi there!
I am completely new to Android. I don't use Windooze (and won't do ), so i am not able to upgrade the arc's Firmware with "Flashtool".
Sadly i have not found a lot information about ".ftf-Files" and the way Flashtool works.
Code:
[email protected] ~/X/LT15i_4.0.1.A.0.283_Generic Global>
file LT15i_4.0.1.A.0.283_Generic\ Global.ftf
LT15i_4.0.1.A.0.283_Generic Global.ftf: Zip archive data, at least v2.0 to extract
extracted, i found a kernel.sin and a system.sin.
I succesfully flashed them with
Code:
fastboot -i 0x0fce flash boot kernel.sin
fastboot -i 0x0fce flash system system.sin
But What about the other files inside of this firmware-archive?
Code:
[email protected] ~/X/LT15i_4.0.1.A.0.283_Generic Global> ls inhalt/
adsp.sin fota0.sin LT15i_4.0.1.A.0.283_Generic Global userdata.sin
amss_fs.sin fota1.sin META-INF/
amss.sin kernel.sin simlock.ta
cache.sin loader.sin system.sin
Is there an image to upgrade that "baseband/radio" thing?
I guess "cache.sin" is the android cache partition and "userdata.sin" is the user partition...
is loader.sin a new Bootloader i should flash?
Greeting
matto
Wine?
Sent from my MT15i using Tapatalk
taaviu said:
Wine?
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Thanks for your quick replay. I think i have read in the "[TOOL] [UPDATE 14/08/2011] Flashtool version 0.3.0.0" - thread,
http://forum.xda-developers.com/showthread.php?t=920746
that flashtool will launch, but flashing is not working.
I am really not sure if i should give it a new try, wine is known to crash a lot. crashing while flashing a new bootloader might brick the phone...
isnt there anywhere some documentation about those ".ftf firmware containers" and its content?
after some internet research i would guess amss.sin/amss_fs.sin could be the fm-radio rom
http://en.wikipedia.org/wiki/Amplitude_modulation_signalling_system
....
flash amss.sin
Has anyone ever tried
Code:
fastboot -i 0x0fce flash amss amss.sin
or
Code:
fastboot -i 0x0fce flash radio amss.sin
?
I will try this, if someone tells me he could unbrick my phone or tell me how to unbrick it when the arc bricks
muell_matto said:
I am really not sure if i should give it a new try, wine is known to crash a lot. crashing while flashing a new bootloader might brick the phone...
Click to expand...
Click to collapse
I'm also using Linux and I tried running flashtool in Wine. I wasn't able to get it to recognise the phone when I plugged it in so I finally gave up and used my Windows 7 computer at work to flash....
I think that's the safest choice, as I don't think ftf files were meant to be flashed with fastboot. You can, however, use img files with fastboot (unlocked bootloader). Like the 2.3.4 one in this thread, for instance:
http://forum.xda-developers.com/showthread.php?t=1269937
Or you can use vmware to install win 7 within linux...!!! That is the way I flash my phone...!!!
Sent from my LT15i using XDA Premium App
so ... sadly i need to get myself windows ... only to flash my phone. (Dammit )
thanks anyway
ps: I will tell you if i decide to do a risky fastboot baseband update, at last, that is the only missing part of the update.
for other readers who foud this thread using the search function:
Don't get it wrong, you can flash a new firmware with fastboot (linux, mac, whatever-platform the official sdk/platform-tools will be ported to), but without the baseband, which works great for me. how? see the first post.
tried this way and didnt work for me.
first, i lost my baseband.
second, when i tried to flash userdata.sin to userdata, got my phone bricked. any suggest?
blackbiron said:
tried this way and didnt work for me.
first, i lost my baseband.
second, when i tried to flash userdata.sin to userdata, got my phone bricked. any suggest?
Click to expand...
Click to collapse
Hi!
What exactly did you do?
(Do you remember the outout or ... maybe saved it?)
regarding "userdata.sin"-brick , have you tried
Code:
fastboot -i 0x0fce erase userdata
and
Code:
fastboot -i 0x0fce erase cache
?
greetings
risky fastboot baseband update
muell_matto said:
ps: I will tell you if i decide to do a risky fastboot baseband update, at last, that is the only missing part of the update.
Click to expand...
Click to collapse
If someone is interested:
I tried to apply the remaining part of the update with fastboot...
It seems like
[a] It is not possible
or
SE chooses weird, hard to guess partition-names
Code:
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss amss.sin
sending 'amss' (17612 KB)... INFOUSB download speed was 2003916kB/s
OKAY
writing 'amss'... INFOFlash of partition 'amss' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss_fs amss_fs.sin
sending 'amss_fs' (62 KB)... INFOUSB download speed was 9166kB/s
OKAY
writing 'amss_fs'... INFOFlash of partition 'amss_fs' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash adsp adsp.sin
sending 'adsp' (5287 KB)... INFOUSB download speed was 9334kB/s
OKAY
writing 'adsp'... INFOFlash of partition 'adsp' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota0 fota0.sin
sending 'fota0' (1470 KB)... INFOUSB download speed was 9353kB/s
OKAY
writing 'fota0'... INFOFlash of partition 'fota0' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota1 fota1.sin
sending 'fota1' (1470 KB)... INFOUSB download speed was 125493kB/s
OKAY
writing 'fota1'... INFOFlash of partition 'fota1' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash loader loader.sin
sending 'loader' (98 KB)... INFOUSB download speed was 8382kB/s
OKAY
writing 'loader'... INFOFlash of partition 'loader' requested
FAILED (remote: Partition not found)
Not sure if you tried this or not but what about looking in the META-INF directory? It could help...
adiktz said:
Or you can use vmware to install win 7 within linux...!!! That is the way I flash my phone...!!!
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
I have win7 on my vmware, and flashtools is reading the device but I got abort msg and wont flash any thing, can you help me how to configure it ?
(( xperia x8 )
sultan-mrm said:
I have win7 on my vmware, and flashtools is reading the device but I got abort msg and wont flash any thing, can you help me how to configure it ?
(( xperia x8 )
Click to expand...
Click to collapse
Use the latest flashtool or place Lt15 loader in the loader folder of the flashtools...!!!
Download nd extract the attachment...!!!
Post a screen shot please...!!! That would make helping you easy...!!!
adiktz said:
Use the latest flashtool or place Lt15 loader in the loader folder of the flashtools...!!!
Download nd extract the attachment...!!!
Post a screen shot please...!!! That would make helping you easy...!!!
Click to expand...
Click to collapse
I will try once get back my Laptop
Thanks man
@adiktz
it's not work
see attached screen shot.
muell_matto said:
If someone is interested:
I tried to apply the remaining part of the update with fastboot...
It seems like
[a] It is not possible
or
SE chooses weird, hard to guess partition-names
Code:
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss amss.sin
sending 'amss' (17612 KB)... INFOUSB download speed was 2003916kB/s
OKAY
writing 'amss'... INFOFlash of partition 'amss' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash amss_fs amss_fs.sin
sending 'amss_fs' (62 KB)... INFOUSB download speed was 9166kB/s
OKAY
writing 'amss_fs'... INFOFlash of partition 'amss_fs' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash adsp adsp.sin
sending 'adsp' (5287 KB)... INFOUSB download speed was 9334kB/s
OKAY
writing 'adsp'... INFOFlash of partition 'adsp' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota0 fota0.sin
sending 'fota0' (1470 KB)... INFOUSB download speed was 9353kB/s
OKAY
writing 'fota0'... INFOFlash of partition 'fota0' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash fota1 fota1.sin
sending 'fota1' (1470 KB)... INFOUSB download speed was 125493kB/s
OKAY
writing 'fota1'... INFOFlash of partition 'fota1' requested
FAILED (remote: Partition not found)
[[email protected] inhalt]$ fastboot -i 0x0fce flash loader loader.sin
sending 'loader' (98 KB)... INFOUSB download speed was 8382kB/s
OKAY
writing 'loader'... INFOFlash of partition 'loader' requested
FAILED (remote: Partition not found)
Click to expand...
Click to collapse
thanks for this courageous test!:good:, I was wondering about this...
I still have another idea...
in my xperia neo v it seems that some so called "partitions" are not really partitions but areas maped in the hardware (Nand)ROM memory.
For example it is true for the "/boot" and kernel image that can't be found anywhere (at lest in my stock installation), but when you use "fastboot flash boot kernel.sin" it is able to find in the correct place to put the kernel image on the correct internal block of rom address.
So for the baseband, I was just wondering that maybe the solution would be concatenating the 03 sin files using something like the linux dd comand (no idea about the order of the sin files) into a unique image file, lets say "bb.img", and then flashing it using fastboot with a special name of baseband partition (something like radio, modem, baseband, who knows what this name could be?...:crying and then use a commmand like:
fastboot flash part_name bb.img
Sorry for not having an answer,
I'm just sharing my wondering because I saw that you are so curious about this stuff like me!!
Hi All,
Trying to install the ICS beta on my Arc S using fastboot and the three .img.
I have to use these commands:
fastboot.exe -i 0x0fce flash system system.img - works fine,
fastboot.exe -i 0x0fce flash bot boot.img - works fine
fastboot.exe -i 0x0fce flash userdata userdata.img - returns:
"C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash
userdata XICS\userdata.img
sending 'userdata' (198 KB)...
(bootloader) USB download speed was 101376kB/s
OKAY [ 0.038s]
writing 'userdata'...
(bootloader) Flash of partition 'userdata' requested
FAILED (remote: Partition not found)
finished. total time: 0.073s".
http://developer.sonymobile.com/wp/...e-for-unlocked-2011-xperia-smartphone-models/
http://forum.xda-developers.com/showthread.php?t=1513172&highlight=userdata+img&page=9
I feel I'm this close to saving my bricked phone, can someone help me out here I'm clueless.. wheres the partition gone? Do I need to wipe it with CWM or something?
Much pre-emptive gratitude!
Fixed! Ignore noobish error..
Sent from my LT18i using XDA
mynameisnafe said:
Hi All,
Trying to install the ICS beta on my Arc S using fastboot and the three .img.
I have to use these commands:
fastboot.exe -i 0x0fce flash system system.img - works fine,
fastboot.exe -i 0x0fce flash bot boot.img - works fine
fastboot.exe -i 0x0fce flash userdata userdata.img - returns:
"C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash
userdata XICS\userdata.img
sending 'userdata' (198 KB)...
(bootloader) USB download speed was 101376kB/s
OKAY [ 0.038s]
writing 'userdata'...
(bootloader) Flash of partition 'userdata' requested
FAILED (remote: Partition not found)
finished. total time: 0.073s".
http://developer.sonymobile.com/wp/...e-for-unlocked-2011-xperia-smartphone-models/
http://forum.xda-developers.com/showthread.php?t=1513172&highlight=userdata+img&page=9
I feel I'm this close to saving my bricked phone, can someone help me out here I'm clueless.. wheres the partition gone? Do I need to wipe it with CWM or something?
Much pre-emptive gratitude!
Click to expand...
Click to collapse
Hi there, I am having the same issue and can't fix it. userdata partition not found. I cant receive texts because there is no place to save them or install apps. Im desparate. Do you know how to fix this issue. Create a new userdata partition?
Can you email me at [email protected] as I am new here and dont know if I will find this thread again.
Flash the stock Rom, THEN flash over the ice beta.. Except use flash tool to flash the official ICS.. Do a forum search and you'll find it.
Sent from my LT18i using XDA
Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!
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
Hi guys, I have just flashed a new TWRP from the command line and wanted to boot to it with fastboot using "fastboot boot recovery.img". Unfortunately I did not pay enough attention when recalled the original command from the CLI and issued "fastboot flash boot recovery.img" instead of the correct "fastboot boot recovery.img" command. The device is still in fastboot mode - how can I restore boot? This was the output of the command:
c:\Program Files (x86)\totalcmd\plugins\wfx\ADB\bin>fastboot flash boot e:\Letöltések\twrp_v3111_hydrogen-helium_nijel8-MOD_A7.1.2.img
target reported max download size of 536870912 bytes
sending 'boot' (16176 KB)...
OKAY [ 0.569s]
writing 'boot'...
OKAY [ 0.230s]
finished. total time: 0.803s
Any help is appreciated - I am scared ****less.
Edit: extracted boot.img from the flashable .zip of the ROM I originally wanted to flash and flashed it with fastboot, hope it works