Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Good to see you here!
I am not sure if memory is locked to bootloader
I dont think so because ics changed the system partition size
We cant edit the .sin files in a .ftf
Sony included a file which contains a long key (like a long md5) which is unique
We cant fastboot boot. ..:... It is not included in the bootloader
If you need any info pm me
Sent from my LT22i using xda app-developers app
Hey Nicholtus!
Thanks for the reply!
So ICS upgrade changed partition layout ? On which model ? And upgrade preserved data or is it a global format ?
You're sure about fastboot boot ? Because it's doing something on Xperia S. Kernel doesn't boot, but something starts as device get stuck, so I was thinking that maybe I was not doing it the right way.
And system ext4, any idea ?
Regarding sin, I know about signature and that we have no way to bypass it.
Hi,
Layout is changed on the xperia s
I thought it was the system partition
If we find a way to bypass the sin header we can re partition the phone
I heard from DooMLoRD that the fastboot boot option is not included
Sent from my LT22i using xda app-developers app
letama said:
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Click to expand...
Click to collapse
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
munjeni said:
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
Click to expand...
Click to collapse
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
I should ask that someday on sony forum I guess.
Regarding the extract of ics, I solved the issue since then, the issue was an incomplete understanding of sin format. Since that time, I wrote a tool that can directly extract sin properly and Androxyde introduced similar changes in recent releases of FlashTool, so now it can be all done on PC without having to flash and dump.
I saw also your investigation regarding boot partitions, isn't the second one the one used for fotakernel ?
Just in case you want to look into this, don't bother if your bootloader is similar to Xperia S . I wanted to use it to have a second kernel for recovery, but after looking at bootloader, booting from this partition is blocked by bootloader as soon as you unlock your bootloader.
This is why I came to this, three different kernels boot with one dedicated to recovery .
letama said:
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
Click to expand...
Click to collapse
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
munjeni said:
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
Click to expand...
Click to collapse
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
Click to expand...
Click to collapse
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
munjeni said:
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
Click to expand...
Click to collapse
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
letama said:
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
Click to expand...
Click to collapse
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
K900 said:
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Click to expand...
Click to collapse
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
munjeni said:
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
Click to expand...
Click to collapse
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
letama said:
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
Click to expand...
Click to collapse
Fastboot is actually open source in AOSP.
K900 said:
Fastboot is actually open source in AOSP.
Click to expand...
Click to collapse
Yes, but I was looking for hidden/unknown oem commands, found known
Is bootloader partition locked? We can write to him by dd?
munjeni said:
Is bootloader partition locked? We can write to him by dd?
Click to expand...
Click to collapse
The bootloader is not stored on the eMMC.
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Wow. We've got an expert here.
K900 said:
The bootloader is not stored on the eMMC.
Click to expand...
Click to collapse
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
---------- Post added at 06:26 PM ---------- Previous post was at 06:26 PM ----------
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
munjeni said:
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
Click to expand...
Click to collapse
The lowest level thing is not there, and I'm pretty sure that's what blocks fotakernel.
munjeni said:
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
Click to expand...
Click to collapse
It should work now with a recent flashtool. Androxyde implemented my sin extraction method that properly extract ext4.
Sent from my LT26i using xda app-developers app
Today I rooted my device,my next step is installing recovery, which is the simpliest,fastest method for installing!?with easy steps or tutorial? on x10 flashing,rooting etc. was much simplier than on S, and on x1 was easy too...I am planning to install CM 10 ...
4.0.4 .45
piponxs said:
Today I rooted my device,my next step is installing recovery, which is the simpliest,fastest method for installing!?with easy steps or tutorial? on x10 flashing,rooting etc. was much simplier than on S, and on x1 was easy too...I am planning to install CM 10 ...
4.0.4 .45
Click to expand...
Click to collapse
Go to dev section and in the search write cwm and you will find a .bat file for cwm... Install it... Super easy
Sent from my LT26i using xda premium
Installing any custom kernel you will have CWM automatically
Thanks guys it works!!!... my last question is how will I install .img or any other rom (.img) file, now when I have recovery , Do I have to put .img on my phone or .zip or I installit through cmd? and what with kernel? Tried theese steps but it wont work http://forum.xda-developers.com/showthread.php?t=1780338
piponxs said:
Thanks guys it works!!!... my last question is how will I install .img or any other rom (.img) file, now when I have recovery , Do I have to put .img on my phone or .zip or I installit through cmd? and what with kernel? Tried theese steps but it wont work http://forum.xda-developers.com/showthread.php?t=1780338
Click to expand...
Click to collapse
Nope, flash through fastboot mode. Copy .img file to fastboot folder and open cmd there, then type : fastboot flash boot boot.img ( boot.img is the name of .img file )
Kernel on the latest CM rom (137) is provided in .zip file. Remember that this kernel (boot.img) is flashed last, after wiping & installing Rom successfully
Sent from my LT26i using Tapatalk 2
lilude56214 said:
Nope, flash through fastboot mode. Copy .img file to fastboot folder and open cmd there, then type : fastboot flash boot boot.img ( boot.img is the name of .img file )
Kernel on the latest CM rom (137) is provided in .zip file. Remember that this kernel (boot.img) is flashed last, after wiping & installing Rom successfully
I cant enter fastboot mode..after blue led comes up,phone turnes on
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
piponxs said:
Click to expand...
Click to collapse
Did you install fastboot driver ? Or could flash .img file through Quick Img tool
Sent from my LT26i using Tapatalk 2
title says it all. I'm not sure where to find the latest boot img
help? links would be best.
The boot.img from the latest stock rom? Can't you unzip the rom and get it or use flash gui?
can't use flash gui, phone is stuck at boot.
I'll try unzipping, thanks!
I'm not too familiar with ADB stuff but you might need to use that. There's guides for that in the dev section.
Extract the kernel from the Rom you flashed. Once you have the boot image, place it in you adb tools folder or SDK and connect to pc. Open the terminal and navigate to the folder and type fastboot flash boot boot.img
Well there ya go!
werd. Ok, I'm working on it. Thank you.
You misspelled word.
You misspelled "I'm a grammar nazi.".
I couldn't resist...
Well then, shouldn't the "g" and "n" be capitalized? - "Grammar Nazi":silly:
I am a grammar Nazi, and proud of it!
I have a program called boot.IMG flasher in Original Dev that has the latest boot.IMG, modules, and will even flash it for you if stuck in bootloop or in bootloader.
Sent from my EVO using Tapatalk 2
-viperboy- said:
I have a program called boot.IMG flasher in Original Dev that has the latest boot.IMG, modules, and will even flash it for you if stuck in bootloop or in bootloader.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1917106 ^^^^^ he said
What is the image for or what does it do?
Thanks
Sent from my EVO using xda premium
It's the kernel and all related files packed into a file called an image file
Hi,
I wanna change the splash screen (boot logo) of my sony ericsson xperia active (st17i) , with FXP 152 CM 10 on it, I can't find the original logo.rle, I found the bootanimation but not the boot logo, can someone help me please? Thanks
Sent from my Xperia Active using xda app-developers app
u cant change kernel boot logo with just a simple copy pasting. its in ramdisk.
one has to unpack ramdisk from kernel, change the boot.rle in ramdisk and repack back ramdisk with kernel.
http://forum.xda-developers.com/showthread.php?t=2066539
First, start off by installing any linux distro (preferrably Ubuntu) and download android kernel kitchen - http://forum.xda-developers.com/showthread.php?t=1659584
In the kitchen, you have to first unpack the boot.img. Then you have an option to convert your (the one you want to put) png file to a rle file and replace the stock logo.rle file and then repack the ramdisk and create the boot.img. Flash it to your phone using fastboot and the following command - fastboot -i 0x0fce flash boot boot.img
Press thanks if I helped and good luck
Hello! I just rooted my xperia u today and now I'm trying to flash a custom ROM. The problem
is that I keep getting error/status 7 in cwm when trying to do this. I have searched around,
but can't find a solution. Any help appreciated!
Info:
Xperia U ST25i
Stock kernel
Stock ICS 4.0.4
CWM 5
Fixed it by following this:
1) Extract the contents you will get 3 things in it .... boot.img (file) , system(folder) , meta-inf (folder)
2) Leaving the boot.img out repack the other two folders (system,meta-inf)
3) fastboot the boot.img file via fastboot by this command "fast boot flash boot boot.img" without quotes
4) then place the new packed zip file
The one without the boot image
5) try flashing it
6) factory reset and wipe delvik cache and reboot
step 2?
blackjacknapper said:
Fixed it by following this:
1) Extract the contents you will get 3 things in it .... boot.img (file) , system(folder) , meta-inf (folder)
2) Leaving the boot.img out repack the other two folders (system,meta-inf)
3) fastboot the boot.img file via fastboot by this command "fast boot flash boot boot.img" without quotes
4) then place the new packed zip file
The one without the boot image
5) try flashing it
6) factory reset and wipe delvik cache and reboot
Click to expand...
Click to collapse
Hi, i'm what you call a noob and I could really use your help.
Could you explain to me what you mean by step 2 'repacking the other two folders (system,meta-inf)'? And do I put all the files in the fastboot folder?
Thanks a lot!!
blackjacknapper said:
Fixed it by fooowing this:
1) Extract the contents you will get 3 things in it .... boot.img (file) , system(folder) , meta-inf (folder)
2) Leaving the boot.img out repack the other two folders (system,meta-inf)
3) fastboot the boot.img file via fastboot by this command "fast boot flash boot boot.img" without quotes
4) then place the new packed zip file
The one without the boot image
5) try flashing it
6) factory reset and wipe delvik cache and reboot
Click to expand...
Click to collapse
Yeah, u should flash the kernel first
I have..
MT27i said:
Yeah, u should flash the kernel first
Click to expand...
Click to collapse
I flashed the kernel via the cmd promt fastboot flash boot boot.img. The device is rooted and bootloader is unlocked.
But when i reboot the phone into recovery mode it doesn't get the FXP screen it just gets the sony logo.
Then when i try to instal from zip I get status 7. I placed the gapps and cm zip files on the sd card.
What am i doing wrong?
I really appreciate the help:good:
blackjacknapper said:
Hello! I just rooted my xperia u today and now I'm trying to flash a custom ROM. The problem
is that I keep getting error/status 7 in cwm when trying to do this. I have searched around,
but can't find a solution. Any help appreciated!
Info:
Xperia U ST25i
Stock kernel
Stock ICS 4.0.4
CWM 5
Click to expand...
Click to collapse
Watch this video (start watching at 8:05).
youtube.com/watch?v=O52IeX93Jek
In this video, he is showing how to flash cm9, but you can also use other custom roms.
What software are you trying to flash?
@Buddha's belly
Have you flashed the kernel that's in the ROM zip?
And you can look at the log to see what exactly fails.
ChikeD said:
@Buddha's belly
Have you flashed the kernel that's in the ROM zip?
And you can look at the log to see what exactly fails.
Click to expand...
Click to collapse
@ChikeD is rights.
try to flash the kernel from rom zip.