Related
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
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.
This ROM has been tested and retested... IF you cannot follow instructions provided DO NOT FLASH,IF your wanting tweaks etc DO NOT FLASH OR ASK FOR THEM THERE ARE OTHER ROMS WITH YOUR WANTS AND DESIRES,IF you are uneasy about flashing firmware DO NOT FLASH THIS ROM,DO NOT USE ANY PART OF THIS ROM WITHOUT PERMISSION, IF your wanting to use another kernel (99% stock is included) etc,DONT ASK HERE IF ISSUES ARISE (ASK THE KERNEL DEV) Folks who use this want a clean stable ROM..IF you are a flashaholic,id suggest copying pics,music etc to computer format your data partition then flashing.
Whats included:
Extra Themes
Eye Experience
Extra Camera Modes
Xposed ONLY included in 4.4.4 and below for now
Integrated VVM (Dialer and Messages)
Isis (Working with Xposed Modules) ONLY WORKING 4.4.4 and below for now
Speed Tweaks
Battery Tweaks
SD Card Tweaks
Screen Touch Tweaks(more sensative)
Dalvik Tweaks
Hardware Tweaks (Qualcomm)
Network Tweaks (Qualcomm)
Stock recovery
Twrp recovery
Weather images updated Thanks Basil3 Not included in latest 5.0.2
Read write module Thanks Flar ONLY WORKING on 4.4.4 and below for now
Rooted
Stock file manager
Quick office Removed in 5.0.1
Extreme Power Saving
S-OFF IS MANDITORY!!!!
BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
***Current 5.0.1 Lollipop Flashing Instructions***
If you have not flashed the 5.0.1 firmware it is included:
CID's that will flash correctly
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
****S-OFF is necessary to proceed with flashing firmware package****
Extract firmware.zip from zip, copy to adb/fastboot location,reboot phone into bootloader connecting it via fastboot option,run commands listed below
Also included in this firmware package is the modified hboot with red text removed
IF you do flash this firmware package the commands to do so are as such:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip firmware.zip(if needed re-run this command)
* 3.fastboot reboot-bootloader
After flashing this firmware package stock recovery will be installed,extract twrp_2_8_3_0_m8.img from zip, copy to adb/fastboot location reflash twrp recovery that is included by running command:
fastboot flash recovery twrp_2_8_3_0_m8.img or latest twrp image
Now after flashing twrp reboot device into recovery,do these steps as it is important!!
factory wipe device,click advanced wipe and select data,system,cache and dalvik wipe these partitions.(TWRP will reload,do not flash until after rebooting recovery) Once this is finished reboot recovery and proceed to flash this ROM.
ATT_4_28_502_1_M8_Lollipop_No_CIQ_Firmware and ROM(is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
https://goo.gl/0gGHLr(current)
ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r(depreciated)
ATT_ISIS_3_42_502_1_M8 ***Use Instructions below for 4.4.4*** (Firmware not included)
http://goo.gl/YM12mn (depreciated)
3_42_502_1 Firmware Bundle (is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
http://goo.gl/U7gocS (depreciated)
DEPRECIATED
Updating Firmware:
1. Copy ROM to storage
2. Copy Firmwarezip to adb/fastboot location
3. Drag twrp openrecovery-twrp-2.7.1.0-m8.img to adb/fastboot location
4. Reboot phone to bootloader/fastbootusb(adb reboot bootloader)
5. Once connected via fastbootusb
6. Open command prompt,
7. Run these commands:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
* 3 repeat #2 command to finish firmware flashing.
Already modified to work on cid's,so no need to change cid
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
* 4.fastboot reboot-bootloader
8. Once rebooted, run these commands:
* 1.fastboot flash recovery openrecovery-twrp-2.7.1.0-m8.img or whatever latest twrp image is
* 2.fastboot reboot-bootloader
* 3.Boot into recovery,factory reset,flash rom (IF ROM has been wiped off data partition,copy rom zip to fastboot/adb location and run adb sideload from recovery..Or adb push nameofrom.zip /sdcard/. Then flash
Modified hboot is already included to remove developer text
After installing ROM:
REMINDER *You MUST flash the latest 2.22.1540.3/.4 or whatever the latest builds firmware zip is called firmware(Included)* ,Once booted DO THESE NEXT STEPS FIRST BEFORE ANYTHING ELSE!!!!,ROM is rooted,has read/write protection disabled,has at&t apn's ...Set Superuser permissions to grant always(no prompts)...Update Xposed Framework and installer...Reboot when prompted....Download Rootcloaker Module, install and activate it....reboot run isis....THEN finish setting up ROM...I dont have a secure sim,butit asks for it,so that means its a go...this also has visual voicemail integrated into system(dialer/messaging app)...I suggest disabling animations in developer options to get the full effect of rom speed...
Enjoy
Download:
M8 - 2.23.502.3(depreciated)
http://goo.gl/3DiIQz FULL WIPE REQUIRED
Mirror: http://goo.gl/9wNs1J (Thanks krazyace35)
ATT 1.16 Radio fix (Thanks runsoverfrogs)
** S-OFF IS MANDATORY **
Radio Download: ONLY For 2.23.502.3
http://goo.gl/vB9dA7(depreciated)
Copy radio-1.16.zip to adb/fastboot loacation
Open cmd
Run commands as shown below
fastboot oem rebootRUU
fastboot flash zip radio-1.16.zip
fastboot reboot-bootloader
Make sure radio has flashed correctly reboot...
Modded Hboot(Thanks santod040):
M8 - 2.23.502.3
No Red Text: http://goo.gl/ins3or(depreciated)
Download:
M8 - 2.22.1540.3
http://goo.gl/uoRz8X(depreciated)
Download:
M8 - 2.22.1540.4
http://goo.gl/yE6s5V (depreciated)
Download:
M8 - 3.28.1540.5 (Read flashing instructions included in download)11-11-2014 Update :good:
http://goo.gl/S5hpMC(depreciated)
Blinkfeed update 11-11-2014
http://goo.gl/iYYAEp(depreciated)
Blinkfeed update 12-10-2014
http://goo.gl/FHpxlV(depreciated)
For those who want to update to newest versions for developer build,you must have stock operating system and recovery and soff to run any of these files
Download:
2.22.1540.4 ota
http://goo.gl/7mec4o (Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 ota
http://goo.gl/MHF4ie(Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 Firmware only unmodified (Latest 4.4.4 Update,S-OFF REQUIRED)
http://goo.gl/tyhRRZ(depreciated)
Download:
2.22.1540.4 firmware only unmodified(Latest 4.4.3Update,S-OFF REQUIRED)
http://goo.gl/FJ7Hhv(depreciated)
Mirrors for ROM's(Thanks tarund)
http://goo.gl/7AuuJf
Changelog:
08-09-2014: App updates....Speed increase,some other minor fixes
08-13-2014 App updates...Minor tweakage
08-27-2014 New base 2.22.1540.4
08-29-2014 New base AT&T Official 2.23.502.3 Debloated and carrieriq removed
09-08-2014 Fixed double/not sending txt issue (I think),Kernel enhancement
9-10-2014 Reverted back to TWRP 2.6.3.3 as used recovery,Reverted Some edits back to stock.
10-19-2014 New Base 4.4.4 3.28.1540.5
11-06-2014 Updated HTC apps, 3rd party apps & some other stuff I dont recall off top of my head.
11-10-2014 Updated LTE configs,Some Camera Enhancements
1-20-2015 Developer Lollipop Release
5-19-2015 Official AT&T Lollipop Release
Thanks for this possible fix as well if the dble txt is still happening
runsoverfrogs said:
I fixed my hanging double text by rolling my radio back from 1.19 to 1.14 Edit WNC 1.16 works as well) baseband
Click to expand...
Click to collapse
Donations:
Thank you...
bruce7373
swapgut
orvon.freeman
co.ag.2005
vegasdiceshooter
cortez.i
ozziedog
effezie
fuzz_33594
Alpione
mimart7
aka120
Vegasdiceshooter
Isis111
Thanks to
ccb101
californiarailroader
orvon freeman for getting me the files
HolyAngel for helping with update script
homeslice for helping with carrieriq
Big thanks to my testers
manup456
mobb315
zero209
pumpiron579
ccb101
tarund
Judge Joseph Dredd
redpoint
swapgut
Already have the firmware installed can i just flash rom
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
vegasdiceshooter said:
Already have the firmware installed can i just flash rom
Click to expand...
Click to collapse
Enjoy....
Pumpiron579 said:
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Click to expand...
Click to collapse
This Rom is kick ass! Way better than any Euro Rom imo.
Glad my boy is back in the building great work bro.
Sent from my HTC One_M8 using Tapatalk
Flashed and its a great ROM much better for AT&T than European ROMs
Glad your enjoying it...
vegasdiceshooter said:
Flashed and its a great ROM much better for AT&T than European ROMs
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
Click to expand...
Click to collapse
So is the z-data file that wipes the phones removed from the firmware?
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
GermanGuy said:
So is the z-data file that wipes the phones removed from the firmware?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
Click to expand...
Click to collapse
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
No its not, and will not be removed from download,this ensures no bugs from things left on storage...and also ensure the storage doesnt encrypt because of stuff left over from other roms...So if you want to remove it thats on you,not resposible for anything that goes wrong.
GermanGuy said:
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
Click to expand...
Click to collapse
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Yes developer edition is same device only difference is ones locked and ones not.The base for the rom is developer edition correct...
Johnny424 said:
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for the 2.22.1540 firmware, and great instructions. While I've flashed firmware before and familiar with the process, its nice to not have the proper command syntax right here.
Also great forethought to have it packaged with the ROM, and a good explanation of the process.
Anyone having issues with keeping wifi on? Mine keeps turning off...
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
diehardbattery said:
Anyone having issues with keeping wifi on? Mine keeps turning off...
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
Click to expand...
Click to collapse
Installed Sense Toolbox, changed the theme of the statusbar icons. At first I thought maybe it was the theme and the icon just wasn't showing, but when I went to wifi settings, it wasn't connected to anything. Made some other tweaks in there, mostly visual.
Installed Battery Stats Permission, SD Full access, and Xposed Call blocker. That's it.
And I did follow the directions to the letter.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
ROM devs...Get ready to start building some beautiful AOSP ROMs for the pixel and pixel xl!!!! It's time!!!!
OK, these are the mini dynamic Gapps built by the pure nexus team. I edited all the scripts within the package to flash properly to our pixel devices. I have tested them myself with a custom ROM and they work perfectly! The instruction are really ridiculous but please trust that at this point, it's the only way to get them working and bypass dm-verity!
Without further stall I give you the package that will allow us pixel user to have custom roms!!!
Moderator EDIT: link removed
Now for the hard part...You must follow these I structions down to the letter or it won't work...If you don't do this exactly, don't cry to me or anyone!
First flash the custom ROM of your choosing and let it boot all the way into the OS, please follow the ROM developers instruction for this.
Next, after the ROM boots, reboot into the bootloader.
Once in the bootloader, fastboot boot twrp.img to get into twrp.
Once in twrp, flash the twrp.zip and flash SuperSU.
After flashing those, go to the home screen of twrp and then to mount and mount the system, after mounting the system, flash the Gapps package.
Then wipe data and reboot your device.
Wait forever.......profit!
There you have it folks...The most convoluted way to flash Gapps ever made...But for the moment, it's the only way I have found!
Credit for to beanstown for making the Gapps package
All I did was edit the way and places that it flashes to better accommodate the pixels partition system.
Please everyone enjoy!
I will be getting these uploaded elsewhere in the near future but for now, drive should work just fine.
Big thanks to the pure nexus guys for the Gapps package!!!
Installation process doesn't seem too involved, for a Pixel.
Great job on everyone who got this working This could be a milestone for this phone!
Wow what a set of instructions tho lol, fingers crossed it will get simplified at some point! For now tho Awesome!
Well the package was built by beanstown, I just toyed with the scripts inside to get the apps and stuff to go to the proper place...I know the dm-verity is what makes it so hard to flash....If you flash root right after a ROM without booting it will result in a bootloop
Moderator Information,
Thread has been closed, as a new thread will be created soon.