Related
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
I'm looking for a brave soul or two that has a GPe and would like to do some testing to see if we can have a tool that will convert any togari ROM into one that will boot and have working radio on a togari_gpe. PM me if you want to be a tester.
A huge thank you to @flipperg and @adfurgerson for testing this and helping to improve this tool and the instructions below.
Warning:
If this does't work it may leave your GPe in a non booting state, only test if you are comfortable re-flashing boot.img and ROMs again
ROM 2 GPe:
A tool for converting a ROM into GPe ROM
This tool will take an installed ROM and GPeize it so that it will boot with a working radio etc
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
Getting a working kernel & recovery: <=== Read This Section Carefully
If you are running DooMKernel or if you get "This device is a honami" and you are flashing a custom ROM do this:
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
Download:
Version 1 [10/05/2014]
Working conversions:
Working on CM11 and Carbon with some bugs
Should work with all AOSP/CM11 ROMs
Might even work with Stock based ROMs (read monx and partial* FTF flashes)
Now that I have thought about it I can't see this working on Stock based ROMs, and now we have DooMLoRD's Sony port there is little point in trying to get it to work on Sony firmware.
* Warning:
Never flash the whole FTF or you will hard BRICK your GPu Ultra, only ever flash the kernel and system and never use Sony OTA/PCC updates
Again:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
XDA:DevDB Information
ROM 2 GPe, Tool/Utility for the Sony Xperia Z Ultra
Contributors
blueether, flipperg, adfurgerson for testing and prbassplayer for the idea in the first place
Version Information
Status: Testing
Created 2014-05-10
Last Updated 2014-05-25
Reserved
Any one testing? We cant have development if no one tries I dont have my phone yet or I would man
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gtshiftin6 said:
Any one testing? We cant have development if no one tries I dont have my phone yet or I would man
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
30 hours and no takers? I'll just upload the zip and someone can test at their leisure...
blueether said:
30 hours and no takers? I'll just upload the zip and someone can test at their leisure...
Click to expand...
Click to collapse
Firsrt let me say thank you for your work. I have had my GPE for less than a week and am still getting a grasp on what is needed for unlocking,root, and recovery. I am also waiting for parts to arrive for my old LG Optimistic G, if I can get it working as a backup phone I will be willing to test. Hopefully you won't lose interest before then.
Edit...parts came for what I hoped would be my backup phone, but it didn't fix it.
Edit...tried to flash Carbon with TWRP from DooMLoRD's kernel and it failed with message "This package is for C6802 C6806....E:Error executing updater binary in zip"
@blueether if you can upload a zip later I will try, or I could try to remove that line if it was explained to me.
I'd prefer to not be the first... Has anyone attempted?
CCJ22 said:
I'd prefer to not be the first... Has anyone attempted?
Click to expand...
Click to collapse
See my second edit in above post. Updater script wouldn't let me flash ROM.
Thanks for the willingness to test.
The error will go away if you open the zip and edit the updater script and remove the check... or I could upload another version...
EDIT
bugger, the error is on the Carbon_togari zip isn't it, this is because DooMKernel is ported from the Z1, if you are coming from CM11 or Carbon for the GPe etc then the extra step shouldn't be needed.
um So new instructions:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel, do this:
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that will work
Alright, I'll bite.
I'm backing up now, but just to make sure I understand:
I will:
1) Wipe/Format
2) Install [ROM][LB&UB] C68XX ★ monxDIFIED ★ ZUltra™ (442.757) BEST AROMA [v06-02][24/04] from the Android Dev Thread
3) Install rom2togari_gpe from your thread
4) Reboot
Right?
FAILURE
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
flipperg said:
I'm backing up now, but just to make sure I understand:
I will:
1) Wipe/Format
2) Install [ROM][LB&UB] C68XX ★ monxDIFIED ★ ZUltra™ (442.757) BEST AROMA [v06-02][24/04] from the Android Dev Thread
3) Install rom2togari_gpe from your thread
4) Reboot
Right?
Click to expand...
Click to collapse
---------- Post added at 09:57 PM ---------- Previous post was at 08:59 PM ----------
So I figure the Honami - Togari issue is because I'm using ZU_GPe-AdvStkKernel-KOT49H.S2.2052-v01 to do the flashing... for some reason it has a boot.img signature for the Honami - go figure. But I'm not sure how to get around this.
If I flash the boot.img from any other ROM (I tried CM11), then how do I flash the Custom Rom and Tool without a Custom Recovery? Do I do all this via adb/fastboot from my Mac?
Just trying, thanks for all the help.
Flipper
flipperg said:
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
Click to expand...
Click to collapse
flipperg said:
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
---------- Post added at 09:57 PM ---------- Previous post was at 08:59 PM ----------
So I figure the Honami - Togari issue is because I'm using ZU_GPe-AdvStkKernel-KOT49H.S2.2052-v01 to do the flashing... for some reason it has a boot.img signature for the Honami - go figure. But I'm not sure how to get around this.
If I flash the boot.img from any other ROM (I tried CM11), then how do I flash the Custom Rom and Tool without a Custom Recovery? Do I do all this via adb/fastboot from my Mac?
Just trying, thanks for all the help.
Flipper
Click to expand...
Click to collapse
Thanks for testing, I cant up load a version with out the check as my dev machine is down, but it will be back up over the weekend.
I think an easy fix for you would be the instructions just above (not the ones in OP) or to reboot back into recovery after flashing monx. All the kernels / boot.img should have recovery so you can flash the boot.img from the ROM zip... so:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel or if you get "This device is a honami" do this: <=== Read This Line
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that this works and we get a GPe running a modified Sony ROM. if it does work it will work on a pure Sony firmware
Again I have to say:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
Thanks for the quick response
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
blueether said:
Thanks for testing, I cant up load a version with out the check as my dev machine is down, but it will be back up over the weekend.
I think an easy fix for you would be the instructions just above (not the ones in OP) or to reboot back into recovery after flashing monx. All the kernels / boot.img should have recovery so you can flash the boot.img from the ROM zip... so:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel or if you get "This device is a honami" do this: <=== Read This Line
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that this works and we get a GPe running a modified Sony ROM. if it does work it will work on a pure Sony firmware
Again I have to say:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
Click to expand...
Click to collapse
flipperg said:
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
Click to expand...
Click to collapse
I would try rebooting system after flashing img. when the Google splash screen shows and led lights up press volume up or down to get into recovery.
flipperg said:
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
Click to expand...
Click to collapse
OK, it sort of makes sense that monxROM doesn't include the kernel. You could use jackie099's kernel or the port of DooMKernel for the togari. Both of these kernels have recovery built in (as should all custom ROMs). A CM11 kernel or one from/for a custom ROM will not boot Stock Sony or monx's ROM, nor the other way around so we have to get the correct kernel for the type of ROM you are flashing.
Once you have a custom kernel installed you can boot into recovery by pressing the vol up or down key when the LED lights during boot (could be pink, purple some other colour depending on the kernel)
Changed the install instructions in the OP again, I hope that it is clearer
@blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it gain.
---------- Post added at 05:04 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it again.
edit...camera crash has small toast message saying "Insert anSD card before using the camera" and tried downloading a new Play Store from web and get toast saying "No D card'.
Report
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
blueether said:
OK, it sort of makes sense that monxROM doesn't include the kernel. You could use jackie099's kernel or the port of DooMKernel for the togari. Both of these kernels have recovery built in (as should all custom ROMs). A CM11 kernel or one from/for a custom ROM will not boot Stock Sony or monx's ROM, nor the other way around so we have to get the correct kernel for the type of ROM you are flashing.
Once you have a custom kernel installed you can boot into recovery by pressing the vol up or down key when the LED lights during boot (could be pink, purple some other colour depending on the kernel)
Changed the install instructions in the OP again, I hope that it is clearer
Click to expand...
Click to collapse
flipperg said:
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
Click to expand...
Click to collapse
FTF=flashtool file which are stock firmwares.
flipperg said:
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
Click to expand...
Click to collapse
Getting there :victory: did cell, wifi and data work in togari cm11?
The status 7 error is my script not the kernel, so it looks like monx will be harder to crack than custom then, I'll have to create a separate version for stock based ROMs I think.
We need the kernel that will boot the system/ROM that we are installing, not a GPe when you flash monx's ROM ie jackie's one or the ported DooMKernel one (not the GPe version of DooMKernel). But with the status 7 error this may not work.
If you still have monx on the GPe you could just flash jackie's or the DooMKernel http://forum.xda-developers.com/showthread.php?t=2705130 and then see if it boots, the simlink errors might not be too important.
adfurgerson said:
@blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it gain.
---------- Post added at 05:04 PM ---------- Previous post was at 04:54 PM ----------
edit...camera crash has small toast message saying "Insert anSD card before using the camera" and tried downloading a new Play Store from web and get toast saying "No D card'.
Click to expand...
Click to collapse
Getting there, did cell, wifi and data work?
blueether said:
Getting there, did cell, wifi and data work?
Click to expand...
Click to collapse
Cell, WiFi, Bluetooth worked didn't think to try regular data. Made a backup of Carbon then restored stock GPe ROM just fine. Can restore Carbon and test or should be able to restore and flash anything else you need tested.
edit.....cell data works but it seems auto rotate doesn't, tried toggling it off then on and looking for more than one place to set it but didn't find any others.
Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
If any questions or need some open discussion regarding the rom feel free to ask.
Q: Is this ROM really S-OFF only? No option for S-On phones?
Click to expand...
Click to collapse
If flashing the aroma build, say no to reboot in aroma. If using twrp and reboot to bootloader manually. The installer forces s on ph98img creation.
You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Is this ROM really S-OFF only? No option for S-On phones?
If not I guess I'll go learn how to S-OFF my phone.
Also TWRP is not a supported recovery? The only recovery that works is Philz?
Most recoveries should work fine. S-on flashing process is to extract the boot.IMG from the ROM.zip, flash the ROM.zip, reboot to fastboot, plug into computer, then "fastboot flash boot.img"
signupstuffid said:
Is this ROM really S-OFF only? No option for S-On phones?
If not I guess I'll go learn how to S-OFF my phone.
Also TWRP is not a supported recovery? The only recovery that works is Philz?
Click to expand...
Click to collapse
If using twrp, say no to reboot in aroma and reboot to bootloader. The installer forces s on ph98img creation.
And no, I've done quite a bit of updates and this works with all the custom recoveries available. You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Snuzzo said:
If using twrp, say no to reboot in aroma and reboot to bootloader. The installer forces s on ph98img creation.
And no, I've done quite a bit of updates and this works with all the custom recoveries available. You also have the option of using flashify to flash the boot.IMG prior and then reboot to recovery to finish flash. The installer will detect you as s off.
Click to expand...
Click to collapse
Cool, Thanks for the tips.
Flashify is usually what I use, unless I forget then I just fastboot flash the boot.img.
One last question, does this ROM have the camcorder bug where you can only take about 3 videos before it requires a reboot to take more?
signupstuffid said:
Cool, Thanks for the tips.
Flashify is usually what I use, unless I forget then I just fastboot flash the boot.img.
One last question, does this ROM have the camcorder bug where you can only take about 3 videos before it requires a reboot to take more?
Click to expand...
Click to collapse
Yes. Its a device wide bug. It either records 3, 6, or none at all. Please if none, let me know, I only test for boot since this is no longer my daily device.
Yw on the few tips.
i made a mistake ....help
i think that i made a mistake. i installed from recovery => install from sc card a zip, directly. for the first zip: Plain-Andy-4.4.4-20141001-vigor-EXPERIMENTAL ...... after gapps-ds-ERE36B-signed
result; no gsm service (no signal)
second zip: Release-v14.2-vigor ................ the phone dont start to android systeme after booting => many msg of errors
if someone can save me from this probleme.....please
thankkkks
I'll have to get you some good gapps for 14.2
CamCorder and Camera no works
Hi ,
I have installed yesterday Plain-Andy, that's it's great job, so smooth and so fast
I like it.
The only problem is camera and camcorder doesn't work
how can I fix this
Thanks for answer
NilkNarf80 said:
Hi ,
I have installed yesterday Plain-Andy, that's it's great job, so smooth and so fast
I like it.
The only problem is camera and camcorder doesn't work
how can I fix this
Thanks for answer
Click to expand...
Click to collapse
The ROM will need rebuilt but unfortunately I no longer have the ROM source available locally.
Device information:
Xperia Z Ultra
Cyanogenmod 11 M12 (togari from offical cm side)
Smartphone is encrypted
Bootloader unlocked
Nothing else changed (kernel etc.)
Hi,
since a few hours i try to get TWRP 2.8.5.0 to work.
After installing it according the offical description and rebooting into the recovery, my z ultra only shows the Sony logo and doesn´t do anything (it took me some time to figure out how to turn it off... Power + vol up).
To get the cm cwm back, i´ve used fastboot to flash boot.img.
The integrated cwm can´t mount the encrypted data partition and is useless for me. To avoid problems on my heavily used z ultra, i tried TWRP first on my old (encrypted) Nexus 7 (2012) tablet, works like a charm and most important, it doesn´t have any problems with encrypted devices.
The installation on the Nexus 7 was not really mentionable, fastboot flash recovery file.img, that´s it.
The Z Ultra is different, the teamwin page says :
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It won´t work, the above mentioned problem is the result.
Maybe i need a custom kernel, any suggestions?
Thanks for your help.
CM kernel probably doesnt allow to flash other kernel than it has (cwm). Flash great devs kernel and than twrp. I have it (at least multi rom 2.8.4 one) and it works.
However after screen off it reboots and i dont know what cause it
Thanks for your answear, i try it next weekend.
Code:
Rom: Resurrection Remix® Lollipop v5.3.6 - Togari
Kernel: from rom
Recovery: Dunno where it came from? Perhaps when flashing Candy5 Beta.
Im kind off in the same position, recovery says
Code:
E: Cannot load volume /misc
Finding update package...
Opening update package...
Installing update package...
Package is for device: ...[B][I]bla bla bla you get the thing[/I][/B]
E: failed to install /sideload/package.zip
E: Please take note of ..[B][I]bla bla bla[/I][/B]
Installation aborted.
E: Cannot load volume /misc!
When trying to flash any zip file. When the flash starts I see something like "verification failed" flashing by really quick .....I guess the verify is active which is causing this issue?
BUT this damn recovery has no damn setting to change that! Probably possible to modify some config.txt manually.
Is it possible to change recovery somehow from CM recovery?
I tried by flashing great devs with fastboot. Then it says finished but the same recovery is still present...
Sorry for ranting a bit ..I'm in the middle of some other projects going on with BSD but this one is driving me nuts :silly: I just want to flash TWRP on my device It should not be this difficult
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
ch3mn3y said:
My advice for you is to flash boot.img from resurrection remix - its great devs kernel v2 with twrp - or zombie kernel for 5.0 which has built in twrp.
Both can be flashed using fastboot, so u dont need working recovery for it and they both should work with all 5.0 roms except gpe one.
Im not sure what versions of recovery they have built in, but after that u can flash multirom zip, which has 2.8.4.x one (with mutirom support ofc,but its just addition for "stock" functions it has). I dont think u can use official twrp 2.8.5.0 with nonstock kernel as i tried to flash it to recovery partition and fotakernel and always it doesnt boot (recovery, rom and kernel worked fine, just after pressing vol+, vol- or power when purple light comes up, it changes to yellow and stay like this till i forced reboot).
I tried it with Great Devs KK (v1 + AICP 7.0l) and LP (v2 + RR or AICP 8.0 unofficial build), built in kernel in AICP 8.0 unofficial and Validus.
MultiROM twrp works fine with GD v1 and v2
Click to expand...
Click to collapse
....well im stuck. I have tried everything. Even hotbooting. That damn CM recovery is there no matter what!
I'm gonna give it a try tomorrow and start on zero. Either flash a stock rom with flashtool or scrubber port which is not based on cm.
I'll report later with some results
Mybe try to:
- dl your rom and zombie or gd
- open ur roms zip with ie 7zip
- delete boot.img
- unpack kernels zip and move boot.img to roms zip
- copy new zip to device
- flash stock
- flash kernel (zombie or gd)
- using built in recovery (should be twrp( flash roms zip
As there will be built in kernel with twrp it should stay after reboot.
If not do it again but before reboot in the and flash multirom zip
Sent using C6833 - AICP/GreatDevs
Solved the issue.
First I Downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "SRF FR".
GoogleDrive: Download FTF
Thanks to @dandyqb
Click to expand...
Click to collapse
And Flashtool 9.18.5
But I got stuck with Flashtool prompting me to move content from C:\flashtool\firmwares C:\users\admin\.flashtool/firmwares (??)
Abandoned flashtool and downloaded Flashtool 9.16.1 instead. But this time I hit another issue.
Code:
Flashing system bla bla bla.
Abort..
Error..
Device connected in Flashmode.
Grrrrr..!!
Abandoned the FTF file and downloaded
STOCK ROM] [FTF] Xperia Z Ultra 6833 14.4.A.0.118 "VodaFone UK".
mediafire: Download FTF
Thanks to @Feodorus 4PDA
Click to expand...
Click to collapse
This time it worked out. Flashtool read the FTF and pushed it to the device as it should.
Booted device and transfered files to my device
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
I did the rest manually. Downloaded and opened [email protected]_LRX21P.S3.4201_by_Scrubber.
Took out the file "For_ALL_ZU_5.0_Scrubb_GPE_kernel_initD.img"
Renamed file and flashed it with
Code:
Fastboot flash boot boot.img
Booted into recovery and flashed
Code:
cm-Resurrection_Remix_LP_v5.3.6-20150221-togari.zip
gapps-lp-20141109-signed.zip
MultiROM-v30x-180115-UNOFFICIAL-togari.zip
Turned off device. Booted into Fastboot mode
Renamed "TWRP_multirom-togari_20150201-00.img" to "recovery"
Flashed file with
Code:
Fastboot flash recovery recovery.img
Fastboot reboot
Wooh.. And I reached a very unfamiliar place named Multirom upon boot saying Auto-boot! :good::laugh:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
Glad u made it. It strange that u need steps with gpe port, but maybe some devices are different
Multirom lets u boot more than one rom. Its like grub on pc, so its good thing, but take 5-6 secs of additional booting time
And flash older version of flashtool (eg. 0.9.18.2), if u want to keepfirmwares in flashtool/firmwares folder. Devs change somethin and people like me with small system partition or ssd drive, which has limited space will have problems if it keeps that way (or well need to stay with older verions)
Sent using C6833 - AICP/GreatDevs
Click to expand...
Click to collapse
I didn't really need scrubbers kernel. I just used it to flash a recovery on to my device as I came from stock rom after flashing the FTF.
Just kind of a "safety first" step instead of jumping right onto flashing the multirom .img file and not knowing if its gonna boot or not. :silly:
Scrubbers gpe port was just the first rom that popped up in my head so its why I used it.
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
What kernel are u using? Im on GreatDevs and after flashing 2.8.5.0 it doesnt boot. I mean its flashed, but after reboot when i press vol+/- like i do with twrp 2.8.4 (multirom one)or before did with cwm it freezes on kernel logo (led color changes from purple to yellow)
Sent using C6833 - AICP/GreatDevs
ch3mn3y said:
What kernel are u using?
Click to expand...
Click to collapse
If this question is for me, I use official CM12.
Its in my forum and tapatalk signatures - Great Devs, KK one.
So maybe its it and cm11 kernel (or only GD) doesnt support 2.8.5+ ??
I can live with 2.8.4 for now (till I move to LP)
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
I have tried this app. And other similar apps I could find on play store. They did not work.
The output in this app showed that it successfully replaced recovery but on reboot CM recovery was still present.
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
the app doesn't work for me either (i'm running slimkat build 9 stock)
i can't get 2.8.5.0 working permanently (at least not after a power down)... it'll work right after a fastboot flash
lame Sony putting kernel and recovery together.... wth... my Note 2 was so much simpler to work with...
anyone got a TWRP theme which is suitable with xperia ultra z?