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?
Related
I would be grateful of some help. I have successfully unlocked the Bootloader, flashed a custom kernel and rooted my Xperia Z Ultra on 4.4.2.
The problem I have is when trying to flash CM11 nightly using TWRP and CWM Recovery. I carry out the wipes in TWRP, then proceed to select the CM11 latest nightly to flash. On swiping the bar to begin the flash, the process fails and the following message displays:
"E: Unknown File System: 'datamedia'
Updating partition details...
Running book script...
Finished running boot script.
Installing '/external_sd/Xperia Root/CM11/cm-11
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This package is for "C6802, C6806, C6833, C6843 to
E: Error executing updater binary in zip '/exter
Error flashing zip /external_sd/Xperia Root/CM
Updating partition details...
FAILED
(I think some of the text to the right of the window has been cut off)
When I Power Off my device in TWRP a message displays saying I don't have root, do I wish to install supersu. I went with this message and assume supersu installed when I powered off. However, on powering back on and re-entering TWRP and trying again, I am still unable to flash my CM11 zip.
I have also re-downloaded the CM11 zip, all to no avail.
To confirm, I can access TWRP and CWM, but can't install my CM11 nightly zip. I have tried installing from the internal SD to no avail.
pretty pixel said:
I would be grateful of some help. ...
Click to expand...
Click to collapse
Flash the boot.img from the ROM zip using flashtool and put the phone into fastboot mode. Hold the vol up key when connecting the ZU to the PC (phone powered off of cause) and select fastboot mode in flashtool flashing dialog. you will have to change to .img from .sin in the file open box
Thank you so much for the reply and support. I'm new to the ZU coming from a Samsung Galaxy Note 2, so please forgive my inexperience.
When you say "Flash the boot.img from the ROM zip", do you mean the CM11 nightly ROM? I only have the ZIP file downloaded from CM website.
Could you please explain the process in simpler terms please?
Thank you again
pretty pixel said:
Thank you so much for the reply and support. I'm new to the ZU coming from a Samsung Galaxy Note 2, so please forgive my inexperience.
When you say "Flash the boot.img from the ROM zip", do you mean the CM11 nightly ROM? I only have the ZIP file downloaded from CM website.
Could you please explain the process in simpler terms please?
Thank you again
Click to expand...
Click to collapse
Quick explanation of what the issue is:
Some kernels/recoveries are ported from the Z1 so tell the ROM installer script that it is running on the wrong type of phone. As you have a ZU (I hope) we can get around this by flashing a new kernel and recovery to the phone, this is the boot.img that you can extract from the ROM zip that you are trying to flash.
This assumes that the phone has an unlocked bootloader, if not you cant run a custom ROM
Save the ROM to the internal storage of the phone (I always use /sdcard/0/Downloads)
Open the CM ROM zip in 7zip/winzip/etc and just extract the boot.img to somewhere (desktop will do)
Open flashtool (https://unrestrict.li/flashtool)
Select the thunder bolt
Select fastboot mode
Select 'Select kernel to flash'
Open the folder where you saved the boot.img file, and change the file type at the bottom from *.sin to *.img and open boot.img
With the phone powered off connect to the PC while holding the vol up key
Wait for about 1-2 seconds (you will see OK in the main flashtool window)
Reboot into the new recovery and flash the ROM like normal
Thank you so much for your support. I will follow your instructions this afternoon, when I have some free time and report back
I've just followed your instructions and they worked perfectly! Thank you so much
After, I flashed the boot.img with Flashtool I was able to install the CM11 rom without issue And I now have a new recovery - CWM which is fine.
Am I correct in thinking that future CM11 zips should now install OK, without having to flash the boot.img each time?
Many thanks again.
pretty pixel said:
I've just followed your instructions and they worked perfectly! Thank you so much
After, I flashed the boot.img with Flashtool I was able to install the CM11 rom without issue And I now have a new recovery - CWM which is fine.
Am I correct in thinking that future CM11 zips should now install OK, without having to flash the boot.img each time?
Many thanks again.
Click to expand...
Click to collapse
Yep that is correct, and any other ROM should install just fine as well.
That's great, Thank you again
Through rooting and flashing CM11 on the Z Ultra, it's made it so much nicer to use and taught me lots too.
Install CM11 Z ULTRA
Ola amigo, se possivel faça um tutorial ensinando a flashear a cm 11 no Z ultra brasileiro.
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.
hi
im flash cynagen mod 12 by twrp recovery but when the phone up recovery is changed to cyanogen and dont work very good for ex dont work for install any things... i flash zombie kernel by flash tool but dont change my recovery !.... what to do change my custom recovery to philiz or twrp or.... ?
If youre trying toflash another rom or restore a backup You can hotboot doom kernel by placing the boot img in your adb area open command prompt and place phone in fastbootmode (hold vol up and connect usb to pc) type fastboot devices then enter in command prompt then type fastboot boot boot.img...as the phone boots remember to hold vol down when you see purple led otherwise you might have to repeat the process!!!
....
zubeedubs said:
If youre trying toflash another rom or restore a backup You can hotboot doom kernel by placing the boot img in your adb area open command prompt and place phone in fastbootmode (hold vol up and connect usb to pc) type fastboot devices then enter in command prompt then type fastboot boot boot.img...as the phone boots remember to hold vol down when you see purple led otherwise you might have to repeat the process!!!
Click to expand...
Click to collapse
i have win8 and dont work fastboot
Try number 4 on this list and place the shortcut and boot img in your adb folder...
http://www.7tutorials.com/7-ways-launch-command-prompt-windows-7-windows-8
After hotbooting doom kernael ,how to get TWRP recovery in 5.0 ROMs
recovery Problem
I have the same Problem( but my phone is xperia z) but it only appears automaticly in lollipop . and i can't change in lollipo ,on KitKat Roms it works fine. I really don't get it how this works .i flashed to stock then i flashed a aosbam Rom (KitKat) ,after that I flashed the lightning kernel. On kit kat i habe twrp but as soon flash a lollipop Rom it becomes a useless
Cyanogen recovery.All this started after I installed a APP in lollipop to getrecovery because it disapeared in validus rom ( lollipop).
Sorry that i ask for help in this thread but it's the only one i could find which is active.
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
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 a recent CM12 nightly installed on my Z Ultra and would like to get rid of the built in CM Recovery and flash TWRP. Will the app Rashr flash the TWRP img successfully, without any further modifications - change of kernel etc?
Thank you.
pretty pixel said:
I have a recent CM12 nightly installed on my Z Ultra and would like to get rid of the built in CM Recovery and flash TWRP. Will the app Rashr flash the TWRP img successfully, without any further modifications - change of kernel etc?
Thank you.
Click to expand...
Click to collapse
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
B.Maximenko said:
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
Click to expand...
Click to collapse
That's great. Thank you. I don't mind if I need to re-flash TWRP after each CM update
---------- Post added at 11:51 PM ---------- Previous post was at 10:53 PM ----------
B.Maximenko said:
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
Click to expand...
Click to collapse
Thank you. On boot, how do you enter TWRP? Volume up, or volume down?
pretty pixel said:
That's great. Thank you. I don't mind if I need to re-flash TWRP after each CM update
---------- Post added at 11:51 PM ---------- Previous post was at 10:53 PM ----------
Thank you. On boot, how do you enter TWRP? Volume up, or volume down?
Click to expand...
Click to collapse
During boot, wait until device vibrates and hold vol down until you see TWRP logo.
B.Maximenko said:
During boot, wait until device vibrates and hold vol down until you see TWRP logo.
Click to expand...
Click to collapse
I can confirm this worked for me. Thank you again..
TWRP 3.0.2-0 for Xperia Z Ultra
Alternative: MusterMaxMueller's build with MultiROM support (requires a kexec hardboot patched kernel):
http://forum.xda-developers.com/showpost.php?p=67108468&postcount=89
Up-to-date TWRP with new looks and functional display/brightness settings.
Download:
http://forum.xda-developers.com/devdb/project/?id=13710#downloads
Built in an OmniROM tree, with TWRP commits currently up to and including this one.
To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once.
Then, erase the recovery partition and flash TWRP using fastboot.
Code:
fastboot erase recovery
fastboot flash recovery twrp-3.0.2-0-togari.img
To enter recovery:
Switch off the phone
Hold Vol-Down & Power button simultaneously until the phone vibrates
Release the power button and keep holding Vol-Down until the Sony logo appears
Device sources:
https://github.com/olefb/device-sony-togari/commits/android-6.0
https://github.com/olefb/android_device_sony_rhine-common/tree/android-6.0-twrp
https://github.com/olefb/android_device_sony_common/tree/android-6.0-twrp
https://github.com/olefb/android_kernel_sony_msm/tree/android-6.0-f2fs (thanks, @MusterMaxMueller)
Thanks to all contributors to the Sony AOSP program, the FreeXperia team, and to OmniROM/TWRP
XDA:DevDB Information
TWRP Recovery for Xperia Z Ultra (togari), Tool/Utility for the Sony Xperia Z Ultra
Contributors
Triflot
Version Information
Status: Snapshot
Current Stable Version: 3.0.2-0
Created 2016-02-03
Last Updated 2016-05-31
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Obi-Wan said:
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Click to expand...
Click to collapse
You need to put the Customization.ini file in Emma's folder prior to running, as per the instructions. Then it won't need a login.
A full guide by alia5 here.
Obi-Wan said:
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Click to expand...
Click to collapse
You should already have the new recovery, it will have been installed/ partitioned when you first installed Stock 5.1.1. (The method described in the link above or even using Emma does not work on C6806 by the way.)
It does require an unlocked bootloader for it to be active though.
-------------------------------------------------------------
Doesn't work on my C6806, device just continues to boot the OS.
I have the recovery partition as I can access championswimmer's build of CWM or Saatvik Shukla's build of TWRP 2.8.5.0 if flashed into recovery. (and a build of TWRP-2.8.7.0 that I forgot that I had downloaded from somewhere in December)
Hi. Are you going to make a TWRP 3.0 build_?
fnldstntn said:
Hi. Are you going to make a TWRP 3.0 build_?
Click to expand...
Click to collapse
Thread updated with TWRP 3.0.0-0.
Enjoy.
Triflot said:
Thread updated with TWRP 3.0.0-0.
Enjoy.
Click to expand...
Click to collapse
Not working on C6806, keeps rebooting, your build of 2.8.7.0 didn't work either, that went straight to booting the OS.
C6866. Works good with sony new bootloader.
pTeronaut said:
Not working on C6806, keeps rebooting, your build of 2.8.7.0 didn't work either, that went straight to booting the OS.
Click to expand...
Click to collapse
If you have the new bootloader, you go into recovery differently.
Instructions are provided by sone here: http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
alia5 said:
If you have the new bootloader, you go into recovery differently.
Instructions are provided by sone here: http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
Click to expand...
Click to collapse
I know, I can flash into the recovery partition (and access) three different recoveries, See my previous post.
@pTeronaut sorry didn't read that
----
There is an "issue" with the fstab and recovery.init.rc script with this recovery.
I just built crDroid-mm, and the mountpoints of the "new" install scripts don't work with this build of twrp, since there is a missing symlink (github commit)
If any1s interested, i've gone ahead and also built twrp 3.0.0 for our togari
How can I check if I have new partition for recovery? I flashed with flashtool .216 firmware a month ago. Now I have gpe port with recovery in kernel. Is possible to have recovery in kernel (old recovery) and in the same time new recovery?
If You flashed/updated to newest fw at least once You have new bootloader with /recovery.
Sent using XT1562 - Resurrection Remix/Ultra Kernel
Uploaded a new version with the fixed symlink, as pointed out by @alia5.
Still no idea about the C6806, sorry.
Triflot said:
Uploaded a new version with the fixed symlink, as pointed out by @alia5.
Still no idea about the C6806, sorry.
Click to expand...
Click to collapse
Now we should have 2 identical twrp-3.0 versions here, oh well...
We figured it out... his (the(?))C6806 doesn't have the seperate recovery partition....
Shouldn't Fastboot flash recovery [image] result in an error if the partition isn't there?
pTeronaut said:
Shouldn't Fastboot flash recovery [image] result in an error if the partition isn't there?
Click to expand...
Click to collapse
In my experience, it flashes it to FOTAKernel, or just doesn't do anything without throwing any errors (rather stating it has flashed it succesfully)
alia5 said:
In my experience, it flashes it to FOTAKernel, or just doesn't do anything without throwing any errors (rather stating it has flashed it succesfully)
Click to expand...
Click to collapse
You can also use the Emma Bootloader and flash it into recovery via:
Code:
fastboot flash recovery FILENAME OF YOUR RECOVERY
fastboot reboot
But this way needs UB
PDesire said:
You can also use the Emma Bootloader and flash it into recovery via:
Code:
fastboot flash recovery FILENAME OF YOUR RECOVERY
fastboot reboot
But this way needs UB
Click to expand...
Click to collapse
Only on C6833 & C6802
Emma doesn't find any 'services' for C6806 (NA LTE ) & C6843 (Brazil with OTA TV) variants.
An update on my attempt to get TWRP 3.0.0.0 installed and working on my C6806.
My previous attempt was coming from flashing stock roms from 5.0 onwards using Flashtool or PC companion.
This time, I relocked the bootloader & flashed the FTF of 14.3.A.0.681 (4.4.2) and let my phone update itself all the way to 14.6.A.1.236, re-unlocked the bootloader, and tried to flash TWRP again.
This time I was successful, either Flashtool and/or PC companion cannot handle the repartitioning, or they mispartitioned my phone the last time around.