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!!
Related
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
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
Alright, so I've rooted my Sony Xperia Arc S (Lt8i) and installed the latest JJHybrid 3.1 ROM. I wanna install the Trinity ICS kernel.
So from what I know I need to have an unlocked bootloader. I unlocked my bootloader the first time using the fastboot cmd method. It showed that it worked. However, trying a few times to flash the new kernel, I keep getting the error that my phone is not rooted when it is! So I thought the bootloader was not locked and tried to unlock it again... This was what I got.
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot> fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot.exe -i 0x0fce oem unlock 0x!36D
24885F3ADF806
...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.002s
Click to expand...
Click to collapse
Using Flashtools to install the kernel fails too... I get the following
01/016/2012 03:16:14 - INFO - <- This level is successfully initialized
01/016/2012 03:16:15 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
01/016/2012 03:16:15 - INFO - You can drag and drop ftf files here to start flashing them
01/016/2012 03:16:16 - INFO - Device connected in fastboot mode
01/016/2012 03:16:21 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/016/2012 03:16:21 - INFO - Device Status: FASTBOOT mode
01/016/2012 03:16:56 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernelboot.img
01/016/2012 03:16:56 - INFO - Flashing selected kernel
01/016/2012 03:16:56 - INFO - sending 'boot' (8366 KB)...
01/016/2012 03:16:56 - INFO - FAILED (remote: The Device must be rooted first)
01/016/2012 03:16:56 - INFO - finished. total time: 0.001s
01/016/2012 03:16:56 - INFO - FASTBOOT Output:
sending 'boot' (8366 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
01/016/2012 03:16:56 - INFO - Please check the log before rebooting into system
01/017/2012 03:17:03 - INFO - Finished Fastboot Toolbox
Click to expand...
Click to collapse
I'- very sure that I have root access... I have CWM installed.
I tried using the fastboot cmd dialouge to install the kernel but I get this message
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot flash boot kernelboot.img
sending 'boot' (8366 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>
Click to expand...
Click to collapse
Can someone tell me what is going on? What should I do? %r9:
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot> fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot.e xe -i 0x0fce oem unlock 0x!36D
24885F3ADF806
...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.002s
Click to expand...
Click to collapse
on your 1st Quote it clearly states that the (bootloader) Unlock phone requested
FAILED....your bootloader still may b locked...
Yeah your bootloader is locked go unlock it, mate.
Sent from my LT18i using xda app-developers app
Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again
OrionyX said:
Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again
Click to expand...
Click to collapse
There's the problem
You only need to unlock it once...
BL unlocking is very much easy.
Follow the instructions again carefully mate
.
Sent from my LT15i using Tapatalk 2
OrionyX said:
Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again
Click to expand...
Click to collapse
BL only need to be unlocked once.
Sent from my LT18i using xda app-developers app
Hi everyone,
i rooted my z1c, backuped TA, unlocked bootloader and recovered TA. The firmware is .157 since it arrived me.
But everytime i try to flash a kernel or recovery in fastboot i gives mit this error message.
(flashing kernel for example)
Code:
./fastboot flash boot ../../LS-KK-MileStone-3.2-amami/boot.img
sending 'boot' (11352 KB)...
OKAY [ 0.358s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.361s
I am on archlinux with newest android sdk.
Is there something wrong with recoverying the TA partion after unlock? Or needs fastboot more parameters?
I banged my head for this since hours... Got someone a idea.
You've probably relocked whist restoring the TA.
XperienceD said:
You've probably relocked whist restoring the TA.
Click to expand...
Click to collapse
That explaaaaaaaaaains everything. Thanks ^^. Now verything is working.
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
adryyandc said:
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
Click to expand...
Click to collapse
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
clsA said:
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
Click to expand...
Click to collapse
Ok, Thank you! Don't really need RUU then.
I will read boot image from device with:
Code:
dd if=/dev/block/mmcblk0p63 of=/sdcard/boot.img
beacause boot is linked with /dev/block/mmcblk0p63
and then replace zImage with my kernel zImage with abootimg.
but remeber you need to be S-Off.
LLegion said:
but remeber you need to be S-Off.
Click to expand...
Click to collapse
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
adryyandc said:
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
Click to expand...
Click to collapse
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
clsA said:
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
Click to expand...
Click to collapse
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#xxxxxx
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
adryyandc said:
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#493992
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
Click to expand...
Click to collapse
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
clsA said:
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How can i put the device in S-OFF mode if the device does not boot?
As i could flash a bad kernel in first step it means i had S-OFF previously?
I was able to upload my stock boot.img (the one backed-up) even i had S-ON with:
Code:
fastboot oem rebootRUU
fastboot flash boot boot.img
fastboot reboot
Don't know why in download mode i was not able to do this.
I have build number 1.32.617.6 CL493992 release-keys
Do i really need to be S-OFF to upload only my custom kernels? According to HTC i don't need to because bootloader is unlocked and:
"What is meant by unlocking the bootloader is that certain partitions are unlocked to provide write access. Specifically: boot, system and recovery. "
http://www.htcdev.com/bootloader/about_unlock_process
Answer: Yes, i need too!
Thanks!
I was able to S-OFF the device. Now the problem is that my compiled unmodified kernels from HTC site won't boot. Any ideea why?
Would i be able to convert this device to Developer Edition using AT&T RUU?
Fixed my problem by using right tool to unpack and repack boot image.
I used this one:
https://github.com/xiaolu/mkbootimg_tools
Help
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
elmasry82 said:
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
Click to expand...
Click to collapse
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
adryyandc said:
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
Click to expand...
Click to collapse
I tried many stock flashes but doesn't work. I don't know the stock flash of my phone. I couldn't reach fastboot. SD card is my only way