I bought the Xperia Mini Pro as second-hand device just days ago (almost new for just ~$40 ) and this small guy really impresses me with its MSM8255 CPU and the ability to run CM10.1 as smoothly as my other devices
However, as I checked in ROM threads, before I flash any ROM, I have to flash the boot.img included MANUALLY VIA FASTBOOT, which renders on-the-go ROM switching impossible (i.e. I'll have to reach for my laptop whenever I'm itching to flash ).
One extra thing I tried is that, for my other devices, this command:
Code:
flash_image boot boot.img
...flashes a boot.img kernel via Terminal Emulator on the phone, enabling me to switch kernel really fast. Plus, these devices can also flash zip packaged kernels via CWM.
But when I executed the same command on XMP, an error pops up that goes, "can't find boot partition, failed with error: -1"...
So here's my question: how to flash kernels (boot.img) on the phone itself? Both command line method and CWM flashing method are welcome.
Thanks for reading this far and thanks in advance for any assistance!
Sent from HTC Incredible S @ PACman v21
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Koloses said:
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Click to expand...
Click to collapse
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package.
Click to expand...
Click to collapse
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
XperienceD said:
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
Click to expand...
Click to collapse
mihahn said:
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Oh well... I must have forgotten about that Arc S, yeah I remembered I used fastboot to flash a FXP128 kernel to it back in the days... Thanks for helping guys! Too sad that I don't have easy access to my PC though...
Sent from HTC Incredible S @ PACman v21
mihahn said:
One reason should be that kernel+recovery are on one partition.
Click to expand...
Click to collapse
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Well then, thx
Sent from HTC Incredible S @ PACman v21
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
an0nym0us_ said:
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
Click to expand...
Click to collapse
But here I'm talking about boot, not recovery, and not having a dedicated recovery is no prob for me. (Sorry if this sounds rude)
Recovery is fused into kernel, then is there a dedicated BOOT/KERNEL partition?
Sent from HTC Incredible S @ PACman v21
Of course there is. Every phone got boot partition. If it doesnt have one then where would the kernel be stored.
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
I recently purchased a Xperia S LT26i. It does not have a recovery partition and cwm is embedded in the kernel ramdisk. Still, it is possible to flash kernels from recovery. I have no idea how does it work but we can definitely flash kernels via CWM. Secondly, flashing kernels means flashing a new recovery but on XS we have a Fota partition which is being used for storing the recovery(even without using this partition kernels can be flashed via CWM)
So maybe something can be done for our phones too.
Sent from my LT26i using xda app-developers app
mnishamk said:
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
Click to expand...
Click to collapse
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
AndyYan said:
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Even I think that Cwm is loaded into the ram when it starts. Here is the proof - when I had cwm installed on /system partition, I formatted /system in cwm but cwm still functioned properly until I rebooted. This proves that Cwm is loaded into Ram memory which is volatile.
Sent from my LT26i using xda app-developers app
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
RavinduSha said:
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
Click to expand...
Click to collapse
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
AndyYan said:
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
RavinduSha said:
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
Click to expand...
Click to collapse
Thanks, will try tonight!
(However, having to flash kernel in this way really suppresses my enthusiasm of flashing ROMs on XMP... )
Sent from HTC Incredible S @ PACman v21
Related
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
I can't cange my Xperia U kernel from Windows 8.1 via fastboot.
Is there a way to do that without fastboot? If so, how?
2Radon said:
I can't cange my Xperia U kernel from Windows 8.1 via fastboot.
Is there a way to do that without fastboot? If so, how?
Click to expand...
Click to collapse
If you ave adb access you can root and install CWM and flash with it.
I have currently CWM on my phone as the recovery. What should I do?
Copy the boot.img to SD card, go CWM Advanced -> Img tools and use it?
Oh and if I flash kernel from CWM, will my CWM disappear or get changed? Or can I recover through it any time?
Those functions are not implemented in my CWM yet... So how?
If I just flash CM10 ROM over some sort of Sony kernel will it brick?
2Radon said:
I have currently CWM on my phone as the recovery. What should I do?
Copy the boot.img to SD card, go CWM Advanced -> Img tools and use it?
Click to expand...
Click to collapse
You need to have a flashable zip file, or get one from another kernel and replace the .img file.
2Radon said:
Oh and if I flash kernel from CWM, will my CWM disappear or get changed? Or can I recover through it any time?
Click to expand...
Click to collapse
If the CWM was with the kernel you lose it, it you installed CWM for locked bootloader than not.
2Radon said:
Those functions are not implemented in my CWM yet... So how?
If I just flash CM10 ROM over some sort of Sony kernel will it brick?
Click to expand...
Click to collapse
Do you have locked or unlocked bootloader?
Read the instruction for rom installation or you will likely be back for help to unbrick your phone.
I think I have unlocked bootloader, unless that changed when I reset the phone and re-rooted it from CM to some Sony kernel... (But if I have it rooted then I must have unlocked?) How do I check that?
And how do I check if my CWM came with the kernel? I don't clearly remember whether I specifically installed CWM myself or it was with the kernel/ROM.
Flashable zip? You mean the CM10 ROM zip? It's on SD card at the moment, along with Gapps and boot.img out of CM10 zip.
2Radon said:
I think I have unlocked bootloader, unless that changed when I reset the phone and re-rooted it from CM to some Sony kernel... (But if I have it rooted then I must have unlocked?) How do I check that?
And how do I check if my CWM came with the kernel? I don't clearly remember whether I specifically installed CWM myself or it was with the kernel/ROM.
Flashable zip? You mean the CM10 ROM zip? It's on SD card at the moment, along with Gapps and boot.img out of CM10 zip.
Click to expand...
Click to collapse
If you have unlocked BL it remains unlocked unless you relock it, flashing kernels or roms does not relock it.
It's hard to tell where you're CM comes from, if you on CM rom it probably is in the kernel, most if not all custom kernels come with CWM.
Which kernel exactly do you want to flash (link to thread). Many custom kernel have a flashable zip, you just need to replace the kernel file (and possibly rename it).
ChikeD said:
If you have unlocked BL it remains unlocked unless you relock it, flashing kernels or roms does not relock it.
It's hard to tell where you're CM comes from, if you on CM rom it probably is in the kernel, most if not all custom kernels come with CWM.
Which kernel exactly do you want to flash (link to thread). Many custom kernel have a flashable zip, you just need to replace the kernel file (and possibly rename it).
Click to expand...
Click to collapse
I use this ROM at the moment: http://forum.xda-developers.com/showthread.php?t=2289674
I had to flash a kernel for it, I came from CM when I did that. Now I want to go back to CM.
I want to flash Cyanogen Mod 10 or 9: http://freexperiaproject.com/
Can't fastboot as Windows 8.1 will at this point never recognize it, and I couldn't connect my phone using Oracle VM with virtual Windows 7. Last resort is the phone itself, which I came to me last.
2Radon said:
I use this ROM at the moment: http://forum.xda-developers.com/showthread.php?t=2289674
I had to flash a kernel for it, I came from CM when I did that. Now I want to go back to CM.
I want to flash Cyanogen Mod 10 or 9: http://freexperiaproject.com/
Can't fastboot as Windows 8.1 will at this point never recognize it, and I couldn't connect my phone using Oracle VM with virtual Windows 7. Last resort is the phone itself, which I came to me last.
Click to expand...
Click to collapse
My advise to you is, if you can't flash with flash mode or fastboot don't flash anything because you won't be able to recover in case of need which is most likely to happen.
2Radon said:
Can't fastboot as Windows 8.1 will at this point never recognize it, and I couldn't connect my phone using Oracle VM with virtual Windows 7. Last resort is the phone itself, which I came to me last.
Click to expand...
Click to collapse
Windows 8.1, huh?
Two simple solutions...
Try to install drivers and flash from flashtool or try to flash the kernel with adb, there are two different ways that I know.
By the way, did you tried to flash from a Linux based OS like Ubuntu? It may work on that.
manudo said:
Windows 8.1, huh?
Two simple solutions...
Try to install drivers and flash from flashtool or try to flash the kernel with adb, there are two different ways that I know.
By the way, did you tried to flash from a Linux based OS like Ubuntu? It may work on that.
Click to expand...
Click to collapse
I haven't tried doing it with Ubuntu, but can I connect my device to an Oracle VM virtual Ubuntu? I couldn't to a Windows 7, but I'm not sure it's the virtual OS's fault.
2Radon said:
I haven't tried doing it with Ubuntu, but can I connect my device to an Oracle VM virtual Ubuntu? I couldn't to a Windows 7, but I'm not sure it's the virtual OS's fault.
Click to expand...
Click to collapse
If Ubuntu can recognize it then good, try to flash from Ubuntu's terminal, I didn't tried in a guest virtual OS but if any problem happen post here.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Sony Xperia Z Ultra (togari)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Note: based on cm-11.0 kernel
Meant for advanced users / dev to be eventually repacked and provided for all ROMs
Feel free to repack and open your thread
Just post a link to your topi here
Sweet!
Yay! About time you got round to this device, great work man
Oh yeah! I gotta say, things are moving fast for the Ultra these days!
What's the best way to flash this IMG file ?
Sent from my C6806_GPe using XDA Premium HD app
golfinggino said:
What's the best way to flash this IMG file ?
Sent from my C6806_GPe using XDA Premium HD app
Click to expand...
Click to collapse
I just 'noobly' fastboot flash boot the image over GPe rom and the phone won't boot, just blank after the power pushed.
I had to fastboot flash boot this GPe kernel with recovery to get the phone booting normaly.. : )
OK I am currently running the gpe ROM what exactly do I need to do to replace my current cwm recovery ?
Sent from my C6806_GPe using XDA Premium HD app
Kernel won't boot. Looks like "dt.img" is missing from the kernel.
I tried "fastboot boot philz_touch_6.10.0-togari" and command prompt says "Failed: dtb not found".
Then I tried "fastboot flash boot philz_touch_6.10.0-togari" and the phone won't boot. The led blinks orange for a while and the phone turns off.
EDIT: Woops, my bad. OP says this is meant for devs to repack into their kernels and not for direct usage.
EDIT 2: I repacked GPE ROM kernel with Philz Touch from this thread and TWRP from [NUT]'s XZDualRecovery. Download it here: http://forum.xda-developers.com/showpost.php?p=49565501&postcount=337
In recovery, Philz Touch says version 6.0.4.6. Don't know if it's normal 'cause the download says 6.10.
ChillyChan said:
Kernel won't boot. Looks like "dt.img" is missing from the kernel.
I tried "fastboot boot philz_touch_6.10.0-togari" and command prompt says "Failed: dtb not found".
Then I tried "fastboot flash boot philz_touch_6.10.0-togari" and the phone won't boot. The led blinks orange for a while and the phone turns off.
EDIT: Woops, my bad. OP says this is meant for devs to repack into their kernels and not for direct usage.
EDIT 2: GPE ROM kernel with Philz Touch from this thread and TWRP from [NUT]'s XZDualRecovery: http://forum.xda-developers.com/showpost.php?p=49565501&postcount=337
In recovery, Philz Touch says version 6.0.4.6. Don't know if it's normal 'cause the download says 6.10.
Click to expand...
Click to collapse
It should have a dt.img. But like most sony devices, seems useless when rom doesn't match kernel
So, like i said, it is meant for a dev owning the device to repack it
Guys is this recovery gonna change my .139 kernel for a old one ?
So I thought of installing a new ROM to my XZU today. First I rooted my device using the following guide : https://www.youtube.com/watch?v=BkQT3nX5yWM. (As I had updated my device to Android 4.4.4 and had .108 FW). I successfully rooted the phone and took a TA Backup. Afterwards, I went on to unlock the bootloader and unlocked it successfully as well. As I wanted to install the ParanoidAndroid 4+ ROM, I downloaded it and got the boot.img from the ZIP file, and flashed it using the Flashtool. However, afterwards, when I tried to go the recovery mode, it is stuck on the Sony Logo, and doesn't blink the notification LED in order to do so.
Did I do anything wrong? I am quite a noob when it comes to XZU related stuff..so I would really appreciate if someone can help me out..
Thanks in advance!
EDIT: (Thought of editing this thread rather than deleting it so that it could be an help for someone who faces a similar problem) I was able to make my device up and running again by flashing the FTF found in this thread: http://forum.xda-developers.com/showthread.php?t=2798690.
Now, I have again come to the status where I have installed a recovery successfully and unlocked my bootloader, and I want to install PA 4+ to my device. Would really appreciate if anyone can guide me on how to do this
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
blueether said:
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
Click to expand...
Click to collapse
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
I downloaded "pa_togari-4.5-BETA1-20140805.zip" available in this link: http://aospal.hostingsharedbox.com/aospal/roms/togari/ . Should I try the last stable release rather than the beta one?
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else? I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Thank you again
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Prabash said:
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Click to expand...
Click to collapse
Good to hear you got it sorted, but I'll run through what you did wrong...
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
Click to expand...
Click to collapse
So you now know it wasn't the boot.img :laugh:
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
Click to expand...
Click to collapse
Normally the way to recover would be to flash a boot.img that works and then enter recovery rand restore, easy when you flash the boot.img correctly
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else?
Click to expand...
Click to collapse
The boot image is the kernel and recovery backed into one (it's a Sony thing ) and it belongs on the /boot partition
I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Click to expand...
Click to collapse
I think you have figured that one out now :cyclops:. So what you did was write the kernel and recovery to the /system partition, not to where it belongs ie /boot
You can also use the "select kernel to boot (hotboot)" (or what ever words it uses) to boot a kernel/recovery and not change the one on the /boot partition - can be handy at times
I hope that helps you understand some bits about your new Sony ZU
Yep! thanks a lot for your help! Really appreciate it! :victory:
Simply put, this is (as of now) the latest TWRP (with F2FS, without multirom - sorry).
https://www.mediafire.com/?mj5885q1x5lamzv
Either install it normally or by using fastboot:
Code:
fastboot flash recovery fota.img
If you head over to AndroPlus' thread and download his latest kernel (as of writing, that is Z3_AndroPlusKernel_F2FS_v26a.zip) you could format /system and /cache as F2FS and it will boot and run fine, /data will however, sadly, not format or work as F2FS. But so far, /system and /cache does.
* Goal: get /data to work with F2FS as well
Thanks for contributing ! Will Multirom ever get integrated by any chance ?
Sent from my Xperia Z3 using XDA Free mobile app
I didn't think anybody was interested.
But sure, I'll see what I can do!
You do need to wait a few days though.
Sure I think there would be a good amount of interest considering it would mean that no matter what happened to the Kernel/recovery we would still be able to fall back on Fota for Multirom.
Sure take your time, would be great if possible.
Sent from my Xperia Z3 using XDA Free mobile app
I don't suppose we are any closer to having MultiRom integrated into this ?
Thanks bud
Sent from my Xperia Z3 using XDA Free mobile app
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
so you mean i can just flash this into fota and boot into it? Thanks.
kjames2001 said:
so you mean i can just flash this into fota and boot into it? Thanks.
Click to expand...
Click to collapse
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
panzerscope said:
Correct !
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
kjames2001 said:
I flashed it via fastboot, but i couldnt enter any recovery. no led indication or vibration. pressed vol up and down and not working. runing lollipop tho, maybe that's the problem?
Click to expand...
Click to collapse
Lol, just Remembered, you need Cm to use it.
来自我的 D6603 上的 Tapatalk
kjames2001 said:
Sorry if i should know this, but do we need a supported kernel or something to boot into FOTA recoveries?
Click to expand...
Click to collapse
You need something that, in the init, at boot, waits to check and see if you hit a set key.
"If set key is pushed - load "kernel" (or really ramdisk) from FOTA-partition"
Or more correctly, as @AndroPlus has coded it:
Code:
if [ -n "$POWRKEYCHECK" ]
then
#load FOTA ramdisk
busybox mknod -m 600 ${BOOTREC_FOTA_NODE}
busybox mount -o remount,rw /
busybox ln -sf /sbin/busybox /sbin/sh
extract_elf_ramdisk -i ${BOOTREC_FOTA} -o /sbin/ramdisk-recovery-fota.cpio -t / -c
busybox rm /sbin/sh
load_image=/sbin/ramdisk-recovery-fota.cpio
busybox echo 'Selected FOTA recovery' >>boot.txt
fi
If you want to do that yourself I can attach the original Sony LP kernel, dt.img and ramdisk for you.
Stock ROM
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
da900 said:
Hi. Just flashed your TWRP on my Z3, but I can't boot into it. What could be a problem? I am using latest CM12. Everytime I press vol + button during boot and lila light I get into CM recovery.
Click to expand...
Click to collapse
Well, to put it easy:
On boot the phone has a script that tells it to look for certain keys to be pushed.
1. If volume up is pushed then go to CM Recovery
2. If volume down is pushed then go to TWRP Recovery
3. If camera button is pushed then go to...
And so on. If there is no script telling the phone to do so (original Sony kernel/ramdisk) then the phone will just simply boot in to android. Nothing tells it to do otherwise.
If there is a script that only tells the phone to boot in to CM recovery or what ever, then that's the only options the phone has.
The kernel (or rather, the ramdisk with the kernel) you use has to have support for booting from the FOTAKernel-partition. If there is no support for it in the kernel then the installed FOTAKernel will just exist there. Not hurting anything, but not doing any good either.
TL;DR - ask the creator/developer of your kernel to add booting from the FOTAKernel as a feature.
Is there any automated or hassle-free way of replacing the nightly CM12 installer script with the script required for this recovery? Or do I have to download the zip manually, unzip, replace the sript manually, rezip, transfer the zip to my Z3, and then flash - every day?
panzerscope said:
No, Fota Recovery is independent from the Kernel
Sent from my Xperia Z3 using XDA Free mobile app
Click to expand...
Click to collapse
Wrong. On Sony devices, once the bootloader is locked, the device will NOT boot the contents of the FOTAKernel partition.
This is similar to older Samsung devices.
The problem with this, of course, is that you normally can't change recovery without changing the kernel.
The workaround developed (IIRC by Dees_Troy of TWRP) was to have the boot kernel extract its recovery ramdisk from the FOTAKernel partition if present, allowing a person to switch recoveries without switching kernels - but they still need a kernel that will read the ramdisk. Also, the recovery ramdisk present needs to "play nice" with the kernel itself, which can lead to problems when Qualcomm or Sony do things that break display compatibility. For example, I'm fairly certain most current Z3 FOTAKernel builds use RGBX_8888, which Qualcomm dropped support for in vanilla framebuffers (like what recovery uses) in newer kernels. So any FOTAKernel ramdisk that tries to use RGBX_8888 will fail, for example, with Sony AOSP (due to it using a newer 3.10 kernel)