[Q] error excecuting updater binary in zip with twrp - Galaxy S 4 Q&A, Help & Troubleshooting

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english

Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.

Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?

I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?

2.8.5.0

Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.

AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.

GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?

Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it

eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.

I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.

thank you guys I upgraded the recovery and now it works fine thank you very much

Related

[RECOVERY][KANG] TWRP 3.0.2 recovery for u8800pro/u8860

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!
Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.
Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.
Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.
Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?

[MOD] MultiROM

this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/9t2yfkIPc7yPj - this is modded recovery. flash via odin (updated 19/10. Thanks to @arcadia2uk for fix flashing bug)
2. https://yadi.sk/d/TtXcwe6Hc54cR - patched stock kernel
https://yadi.sk/d/r2lnH3N3c54eF - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/r9ZLm0vCc68um - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Click to expand...
Click to collapse
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
PS the link to the MultiROM decription does not work, here is the correct one http://forum.xda-developers.com/showthread.php?t=2011403
arcadia2uk said:
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
Click to expand...
Click to collapse
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
bonuzzz said:
this is beta release. for t900 only.
Installation:
1. https://yadi.sk/d/Sm4V4SMDc54ay - this is modded recovery. flash via odin
uninstallation:
https://yadi.sk/d/Sm4V4SMDc54ay - flash this uninstaller through recovery, then flash original twrp
Click to expand...
Click to collapse
It doesn't seem correct that the modded recovery and the installer has the same d/l link?
---------- Post added at 11:35 PM ---------- Previous post was at 10:52 PM ----------
bonuzzz said:
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
Click to expand...
Click to collapse
When trying to flash the recovery with Odin there's an error message saying that the MD5 Hash value is invalid, recovery_mr_t900.tar.md5 is invalid.
I recompiled recovery and refreshed links. try again to flash.
bonuzzz said:
I recompiled recovery and refreshed links. try again to flash.
Click to expand...
Click to collapse
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
arcadia2uk said:
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
Click to expand...
Click to collapse
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
I renamed the tar file by taking away the .md5, that worked.
The boot with the stock ROM went fine. However, I tried install my cm11 by restoring a backup and got stuck, or so I thought it actually came to life after having looked a SOD for 5 min. so I guess it went well. Next problem is that when I'm on the MultiROM boot menu it doesn't give me the option to select the alternative ROM, but makes the countdown and then boots internal. There is no possibility for me to select my alternative ROM as the blue strip does not react to touch. Well, I hope you understand what I mean...
---------- Post added at 09:59 AM ---------- Previous post was at 09:29 AM ----------
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
It might also be linked to the fact that the recovery is trying to validate the ROM as a v2awifi, while it should be v2wifixx on the T-900.
I assume the recovery.img need to be modified?
---------- Post added at 10:19 AM ---------- Previous post was at 09:59 AM ----------
It's actually as simple as touch mode that is disabled in the bootmenu, and you have to use up/down keys to select and power key to confirm your ROM choice (I bet it says this in the OP already...)
Now when that is cleared out it seem to be running great, but as I need to test drive another T-900 Rom I have to uninstall it as I need original TWRP to flash that ROM, due to the naming convention.
After all this gave me the opportunity to test the uninstaller that also worked well
.
So the only issue is the Recovery naming convention the T-900 should be v2wifixx.
This is how I came to have the v2wifixx:
TWRP 2.8.0.0 downloaded from http://www.techerrata.com/browse/twrp2/v2wifixx where I selected openrecovery-twrp-2.8.0.0-v2wifixx.img.tar and flashed it with Odin 3.07. This is the most common version for T-900 owners, as they followed the posted instructions HERE. It's also the version for which Valeria ported the cm-11.
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
bonuzzz said:
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
Click to expand...
Click to collapse
v2wifixx is the one. (no a after the 2)
But as I mentioned, apart from the small glitches you mention in the OP everything runs smoothly, and what a relief it is to quickly transfer between different ROMs. Great work, I just wished we had a decent touchwiz ROM for the T-900... Thank you, Great work (but I'm getting used to it ) With this, the only thing I had wished for is a 64G internal SD, rather than the 32G I have, unfortunately you can't perform miracles Bonuzzz.
I've been looking into MultiROM before, bet never saw the need for it, but after this experience I have also installed it on my HTC One (m8) which allows me to test ROMs quickly and smoothly, what a difference it makes.
Updated 10/18/2014 08:40am EST
Temporary work around:
1. backup you TouchWiz ROM* (TW),
2. install cm11(s) prior to MultiROM and make a backup,
3. recover your TW, and
4. proceed with MultiROM install after Bonuzzz's instructions in post 1
Once a fixed recovery is available, simply flash this new recovery image and you're good to go. As of that point you can update cm11 nightly's on the go.
HOW to Updating/changing ROMs
Primary ROM (Internal)
- Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs) (note: don't forget fixed kernel)
- Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
- If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
- Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
- Select "Flash ZIP" and flash ROM's ZIP file.
* I installed Bonuzz's Custom ROM 1.0.1 (for the P-900) and flashed his MultiROM kernel (see post 1) on top of it. And with no other modifications it seems to work perfectly well. I have only encountered a single minor issue, auto screen-rotation didn't work, but mine is always locked in landscape anyway. I froze the TouchWiz launcher and using Google Now Launcher instead, it couldn't be done w/o freeze, and also fixed an issue with incorrect cropping of my wallpaper. After all everything is good, and as always a great performance by Bonuzzz. Thank you/arc
reuploaded recovery. try again.
bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
This package is for device: v2wifixx; this device is v2awifi.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
Click to expand...
Click to collapse
arcadia2uk said:
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
Click to expand...
Click to collapse
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
bonuzzz said:
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
Click to expand...
Click to collapse
I sent you an e-mail about the problem a few minutes ago
Am I correct to assume that the only way to install cm-11 with gapps is by flashing a backup under MultiROM?
Or, at least until you can get the Advanced/MultiROM/List ROMs option corrected, since that seems to be to only place where you can flash a .zip on top of an existing ROM, and this install option only allow you to make a simple flash, or have I missed something?
bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
Do I feel that you're abandoning this project, when you're this close....

Cm12.1 optimized

Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!
PePeMoke said:
Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!
Click to expand...
Click to collapse
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.
GDReaper said:
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.
Click to expand...
Click to collapse
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?
PePeMoke said:
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?
Click to expand...
Click to collapse
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..
GDReaper said:
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..
Click to expand...
Click to collapse
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.
PePeMoke said:
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.
Click to expand...
Click to collapse
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified
GDReaper said:
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified
Click to expand...
Click to collapse
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
I know he's right.
I was just trying to figure out if he really wants to convert or not.
To me it seemed as if he thought F2FS is obligatory in order to run your rom. So I made sure he gets the point that it isn't
AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?
Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!
PePeMoke said:
Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!
Click to expand...
Click to collapse
The rom is already rooted. But you have to enable root first. The rom developer (AntaresOne in this case) posted instructions in the rom thread on how to do that.
But installing SuperSU from the market or via a flashable zip is also good. I've had problems with the CM Superuser app.
PePeMoke said:
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?
Click to expand...
Click to collapse
CF auto-root is only for stock rom. It's NOT for CM 12.1. I would reflash CM 12.1 without wiping just to make sure CF auto-root is gone.
Every CM rom contains root. You just have to enable it like GDReaper told you.
Thanks guys!
Runs smooth and I have root access via cm.

[NANDROID] Motorola Marshmallow Soak test v5 - Dec 13 - makes other phones jelleh!!

This is considered a beta rom. Things may break, things may change, and your phone may brick or turn into a portable toaster. I'm not responsible.
You are flashing this at your own risk!!!
This is a nandroid backed up from a US 2gb/16gb xt1540. It may or may not work on all models...that is to be determined.
Confirmed compatible variants:
XT1540 (US 1/8GB and 2/16GB) (Canada)
XT1541 (UK) (France)
(if your variant is not here it only means it's either not tested or not reported working. please test and report back!)
If you are unable to boot or obtain any signals after flashing this, it is highly recommended you flash a full factory image intended for your specific model and wait for another solution.
This is only meant to be a temporary fix while we wait for the big guys to build us a standard rom.
PLEASE READ THE GUIDE BELOW!!! Some things have changed with v3
How to install:
Extract the .tar.gz archive like any zip
copy the folder to the directory where your other TWRP nandroids are on your internal storage or sd card (TWRP/BACKUPS/ZZY222____/) in here you will see folders with dates, times, rom names and info, etc in the folder names...copy the folder you extracted to this directory.
boot to TWRP
restore this backup
if coming from anything but a previous soak test, wipe userdata
wipe cache and dalvik cache
flash systemless root zip SuperSU v2.61 (optional) DO NOT flash any lower SuperSU version!!
reboot (Please be patient...it's a VERY long wait. If you pass 10 minutes waiting and it hasn't booted, force a reboot by holding the power button)
profit!
***It is HIGHLY recommended US xt1540 users update their radio. It is not required to run this soak test, though. THIS IS ONLY FOR US USERS!!!!! DO NOT FLASH THIS IF YOU ARE NOT IN THE UNITED STATES!!!!***
See this post for the updated soak test modem.img files (just flash to the modem partition with fastboot and reboot the device)
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
For anyone who is not in the contiguous USA (48 states) but still has xt1540 and would like to test the modem above, you can use the app linked below to back up your modem partition directly from your device before you try the new modem. This way you don't have to download a factory rom to get the right modem.img if you don't already have one backed up on your computer. You have to be rooted to use it.
Wanam Backup & Restore app (free)
How to root:
Please see this thread for the download:
http://www.xda-developers.com/update-to-snapprefs-xposed-module-includes-17-instagram-like-filters
The newest root method provided by chainfire does not touch the system partition. To the end-user, the only change is that when you flash a new kernel you must re-flash superSU....not your rom!!! What this means to us in this case is we can use the stock kernel provided with the soak test, flash the superSU zip, and have root, just like a Nexus device without having to wait for a permissive kernel!
*****After flashing the new systemless root zip you will be prompted to install superSU before the device reboots. DO NOT ALLOW IT TO INSTALL!!!!!! If you allow it to install with this option you will get a bootloop*****
**To view your device storage from your computer, open your notification shade, click the "USB for _____" notification, and select "transfer files (MTP)". It won't stick through a reboot, so you'll have to do this each time you boot.....the same thing goes if you unplug the cable.
Download:
https://drive.google.com/file/d/0ByE999IDa0JnaEpnX0FCRjNxX28
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
feligoni said:
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
Click to expand...
Click to collapse
TWRP wipes for you automatically in the restore process. You don't have to wipe system manually. Just restore wipe userdata and reboot!
hp420 said:
TWRP wipes for you automatically in the restore process. You don't have to wipe manually. Just restore and reboot!
Click to expand...
Click to collapse
Awsome. Im downloading the file right now, gonna report back when i try it
feligoni said:
Awsome. Im downloading the file right now, gonna report back when i try it
Click to expand...
Click to collapse
I'm reuploading a new nandroid...please wait to install the new version
hp420 said:
I'm reuploading a new nandroid...please wait to install the new version
Click to expand...
Click to collapse
Haha, ok. I was about to restore te backup, but i'll wait.
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
hp420 said:
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
Click to expand...
Click to collapse
Dont worry, i've got pretty good download speed at work hehe
All done! new link in the OP guys...go nuts
610mb??
Sarath280 said:
610mb??
Click to expand...
Click to collapse
it's system and boot only, and compressed.
it's all there, trust me
hp420 said:
All done! new link in the OP guys...go nuts
Click to expand...
Click to collapse
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
feligoni said:
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
Click to expand...
Click to collapse
We will only get an update if our friend who is an official tester shares it with us.
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
feligoni said:
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
Click to expand...
Click to collapse
Glad it worked!! Thanks for reporting back
it booted on xt1550 ril not working
Sarath280 said:
it booted on xt1550 ril not working
Click to expand...
Click to collapse
have you tried manually entering your carrier's APN information?
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
l3ones said:
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
Click to expand...
Click to collapse
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
hp420 said:
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
Click to expand...
Click to collapse
Apparently it was just an issue with 7-zip, WinRAR handled it perfectly.
This is my first time making a flashable ROM but it should be up later today.

[GUIDE][6045]How to Restore Android MM TWRP BACKUP

Hello Everyone
This is A Guide how to restore the TWRP BACKUP OF ANDROID 6.0 Marshallow for Idol 3 5.5
They are TWO Backups of MM 6045i update
1.Here's Marionette Backup (System Img,Boot img,Data)
2.Here's Masterdex Backup(System Img,Boot img)
1. First of all you must install TWRP on your Idol 3 5.5", Link for TWRP
2.Download and unpack archive in a separate folder
3.Boot in TWRP and make backup of your current firmware
4.. Make Wipe through TWRP menu
5.After you make your backup on external microSD or USB-OTG
TWRP -> Backups -> xxxxyyyy,
(xxxxyyyy is a "number", It's unique for each device.)
6.Copy this folder 2016-06-17--13-51-57_MMB29M_release-keys from archive to xxxxyyyy folder on microSD or USB-OTG and choose Restore in TWRP.
After finished Restoring you need new partitions to work System (if you don't flash the system will not boot )..so they are two zips flash it !
Here's ZIP by me
It takes 15-20 minutes to Boot
Thats all,Enjoy
Credits:
Thanks to @Famewolf @The Marionette and @masterdex for TWRP BACKUP​
Thanks Alex, now we have fully functional android 6.0.1 on our devices.
WIFI and BT works, android 6.0.1 is very fast, almost no lag os.
Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that
frankee207 said:
Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that
Click to expand...
Click to collapse
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...
Alek Dev said:
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...
Click to expand...
Click to collapse
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...
frankee207 said:
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...
Click to expand...
Click to collapse
Twrp works so if you have Twrp backup you can restore or Mobile upgrade q or Panasonic Firmware Tool can restore you back....if you restore Twrp backup .of 5.0.2 the system will work good with newer partitions... So you will can't have any problems ??
Will this work on the 60450 Cricket phones.
Jimhackthorn said:
Will this work on the 60450 Cricket phones.
Click to expand...
Click to collapse
Yes works with every model
Root?
MoRRLiNsS said:
Root?
Click to expand...
Click to collapse
https://download.chainfire.eu/751/SuperSU/
Just flash it with Twrp !
Dosent work anyway dude gonna wait for a real dev to release MM
MoRRLiNsS said:
Dosent work anyway dude gonna wait for a real dev to release MM
Click to expand...
Click to collapse
You must do something wrong ..even Masterdex solved the problem with MM...
Alek Dev said:
You must do something wrong ..even Masterdex solved the problem with MM...
Click to expand...
Click to collapse
I think its because it cant mount system for some reason it mounts it when it wants
MoRRLiNsS said:
I think its because it cant mount system for some reason it mounts it when it wants
Click to expand...
Click to collapse
Go to twrp go to WIpe then Advanced Wipe then select system and then Repair or change system and then Repair file system
and then read again the thread and try again!
WIFI Not Working
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.
Jimhackthorn said:
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.
Click to expand...
Click to collapse
I had the same issues with wifi but try again with this thread ..for me helped and i'm having WIFI AND BT ON MY IDOL 3 with MM
Here's instructions
1.,WIPE EVERYTHING
2.Download and Flash this
3.Restore one of the Backups
4.And Reboot
wifi and BT still not working
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​
Jimhackthorn said:
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​
Click to expand...
Click to collapse
Send me PM i will try to help you
wifi and BT still not working
Here is the picture of it failing to mount.
Jimhackthorn said:
Here is the picture of it failing to mount.
Click to expand...
Click to collapse
Before installing unmount system and try again?

Categories

Resources