[Tool/Converter]ROM 2 GPe [Testers needed] - Sony Xperia Z Ultra

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.

Related

[ROM][ATT][4.4]Kitkat 140.44.3.ghost_att + root for locked bootloader [UPDATED]

Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away

[Q] Flashing CM11/10.2 Problem.

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.

[4.4.4] [Rom] [Safestrap] Optimum Polarity BETA v1

Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
If I took the 4.4.4 OTA update, is there any way for me to get root at the current time?
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
CurbThePain said:
Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
Click to expand...
Click to collapse
Jaocagomez said:
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
Click to expand...
Click to collapse
If someone could test that and see if it actually works on this rom that would be amazing and I will post pictures asap.
Blade765 said:
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
Click to expand...
Click to collapse
Please do not quote the the op. But yes. You can also always go back to the old 19.5.3 4.4 rom. But dont forget to flash the boot.img provided in the op post. Lastly you will still have wp off. But for some od reason there are a lot of google play issues with this rom. Ive redone all of my work 2 times and it still ends up with the same issues.
If you want to stay rooted with wp off stay on 4.4 but you can still flash this. So basically no you cant get root on 4.4.4 ota to my knowledge. Yet.
Works on the MINI
Just wanted to say THANK YOU!
This worked on my DROID MINI (was on 4.4 Rooted WP Off/ SafeStrapped)

[GUIDE] [C6802] Stock To Custom ROM [Without Losing/Recover Lost IMEI & BASEBAND]

Thanks to blueether for His very useful thread
! ATTENTION !
There is a SIMPLE SOLUTION HERE
The C6833 modem works for my C6802 [TESTED]
Thanks to Triflot​
Requirements:
*. DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANYTHING THIS WILL DO TO YOUR PHONE
1. Xperia Z Ultra (Absolutely! ) [Tested on XZU with Unlocked Bootloader]
2. FlashTool, Download link & tutorial here
3. Required FTF (NUT's *.532 & *.136)
4. Custom ROM
5. PC running Windows OS
How to get into Flash Mode:
1. Power Off your Z Ultra
2. Press & hold Vol-
3. Plug your phone to your PC (USB driver > read for intallation step here)
How to get into FastBoot Mode:
1. Power Off your Z Ultra
2. Press & hold Vol+
3. Plug your phone to your PC (USB driver > read for intallation step here)
[TRICK] Get Into FastBoot Mode/Flash Mode​
If you're having trouble getting into FastBoot Mode/Flash Mode, you can try this trick
1. You have to be on Windows
2. Make sure you opened FlashTool & installed driver for Z Ultra
3. Open Device Manager
4. Show hidden device [Not really necessary, I did this to make sure my Z Ultra driver is installed]
5. Plug your phone while holding Vol+ (FastBoot) OR Vol- (Flash)
6. If it doesn't recognized by Windows, then Scan for hardware changes (this simulate USB Unplug & Replug for me), do this while holding the Volume Rocker
7. Repeat number 6 until you got it connected
For Windows 8/8.1 Only:
When you connected Z Ultra using Flash Mode to your PC, it'll disconnect after a while, to solve this problem, try to prepare your files you want to flash first, then when FlashTool asked to connect your phone, do step 1 to 7, your phone won't disconnect at the time it being flashed
Fresh Install [RECOMMENDED]​
Steps:
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool [Default Settings, Flash Everything]
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available
Thanks to x1123 for his post here
Update Custom ROM [EXPERIMENTAL]​*Please Correct Me If I Wrong
Steps:
*. This Will Not Keep Your Google Account, So, Contacts, Mails, Hangouts Messages, etc. That Related To Google Account Will Disappear
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery [GAPPS Must Be Installed, Otherwise Google Framework Will Crash]
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available [Some Google Apps Will Disappear, You'll Need To Re-Install It]
Tested ROMs: copied from here
Carbon - Build 8: Working
SlimKat: Not tested yet
LiquidSmooth: Not tested yet
FXF CM11: Not tested yet
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe ROM: Not tested yet
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
blueether said:
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
I lost my imei yesterday so i have to go through this process. And since i'm already in a custom rom, so i don't need to flash boot.img via fastboot right? Just flash everything via recovery?
And if i do lost imei again, i just need to restore the backup of my previos rom?
Coming from a nexus, this quite confusing :/
Azra4 said:
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
Click to expand...
Click to collapse
You flash it via Flashtool. The link for the thread is in the op.
satriamau said:
You flash it via Flashtool. The link for the thread is in the op.
Click to expand...
Click to collapse
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Azra4 said:
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Click to expand...
Click to collapse
I don't think you should flash ftf to a gpe z ultra. I've read somewhere it'll brick your device.
Dang! OK, so how do I get my IMEI back then?
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
you flashed the normal togari CM11 not the togari_gpe version? is so just flash the _gpe version over top
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Riza said:
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Click to expand...
Click to collapse
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
So Carbon worked fine with no IMEI issues?
blueether said:
So Carbon worked fine with no IMEI issues?
Click to expand...
Click to collapse
No since i follow these steps while flashing carbon. I flash cm without these steps. Wanted to try cm since carbon giving me random reboots sometime. I love the features btw.
Oot : is there anyway i can turn heads up off on carbon?
Thanks.
juggz143 said:
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Click to expand...
Click to collapse
i tried this AFTER i unlocked my bootloader, so idk about XZU with locked bootloader, but i think it's safer to unlock your bootloader first, it's to avoid soft brick of the device, many thread says u must unlock your bootloader before you install any custom ROM
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
i'm afraid idk the other way, if you want to change your rom, then you must follow the fresh install guide, but if ure upgrading [from CM 11 to later CM 11] then follow upgrade guide
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Flash the attached c6833-modem.zip file for a workaround.
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
That makes perfect scene, good on you mate
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Riza said:
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Click to expand...
Click to collapse
Thanks, that's great!
Did you try the c6x02 file, too? And it didn't work? I wonder why it's included, then - I guess we should ask CM on their issue tracker. In the meantime, you can just delete the c6x02.sh file from the root of any ROM zip you want to install, and it should use functional modem files. (Or use the above zip, but it may become obsolete in the future.)
Still, this doesn't tell the full story if for example Carbon users have had the IMEI problem, since it doesn't have the script. Have you had reports of that, @blueether? Maybe they were caused by not flashing on top of a compatible stock ROM?
There was one I think. I'm not sure what the cause was though

Can´t get TWRP to work

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?

Categories

Resources