Related
[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.
*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this
*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.
Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847
Thanks for the guide
Appreciate the work. What gapps are you using.
Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)
Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app
can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx
I Have opened this thread for test purposes only
THIS is a thread of Ressurection Remix 5.2.5 android 5.0.2
LINK to rom here
LINK TO gapps Here
Link to raw kernel here
FIRST YOU NEED the compaitble recovery and kernel ,the same one that cm12 uses
Refer THIS Thread
installing:
copy Rom+Google Apps to sdcard
boot into recovery
(factory reset) (if you get fc's or bootloops after updating from an older rom)
flash the rom and gapps zip file
reboot
now remember always take a nadroid backup of previous rom
some users report this error
Code:
error status 7
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
somebody knows how to fix this error please feel free to share here and test the ROM
status 7 error as I have always seen is related to incompatible recovery.
People got it while trying to flash kk ROMs coming from JB using a non SE Linux recovery.
Maybe try raw kernel?
remember not to boot system after flashing that kernel but reboot to recovery.
REVENGE SOLVES EVERYTHING
Help needed
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
varund7726 said:
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
Click to expand...
Click to collapse
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
tysonraylee said:
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
unfortunately I can't this the only phone I had, my S plus are not with me currently,
anyway, I'm not sure any of this issue causing the error are appear to be mine only, but I'm sure it is
status 7 error failed to write..bla..bla "/tmp/boot.img.."
I already forgot how's the error,
I'll try again in some time, currently at work and kinda busy, :crying:
so sorry guys,
hopefully others help too, :highfive:
please :good:
varund7726 said:
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
Click to expand...
Click to collapse
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
tysonraylee said:
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
goodluck buddy! :highfive: :victory: :highfive:
I heard 4.2.2 is going to landed on our device by old sammy, seems nice for forest kernel development! :victory:
kazuna69 said:
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
TouchLeclouds said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
Click to expand...
Click to collapse
Status 7 here is due to se linux recovery
varund7726 said:
Status 7 here is due to se linux recovery
Click to expand...
Click to collapse
I had the same issue before, my problem was solved by changing the update script
TouchLeclouds said:
I had the same issue before, my problem was solved by changing the update script
Click to expand...
Click to collapse
So can we change bauner update script and check the possibility
mjrifath said:
So can we change bauner update script and check the possibility
Click to expand...
Click to collapse
you can try that, but also keep in mind that this issue could be caused anything else. i just gave the solution that worked for me
Ok i got it to boot.thanks for the help guys.ill open a thread in the dev section and close this one
Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Edit: Looks like jeryll already said it.
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9
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.
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Got now rr as primary rom and will try later on to flash some roms on the second space... Let you know if that works out.
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
superior8888 said:
Tried to dual RR and liquid rom ..No luck. Just reboots to twrp..
Skickat från min ONEPLUS A5010 via Tapatalk
Click to expand...
Click to collapse
I have also rr as primary but second rom install ended in error 1 in twrp. Maybe you can try to reset data of second rom with the dualboot patcher zip.
It might be helpful to read the Dual Boot Patcher thread for the OP5, as there may be some important info there that is relevant for getting it to work on the 5T.
I tried rr as primary, no problem. Tried adding 2nd rom as secondary, as data slot 1, and no dice. Even tried removing assert lines in the updater script as suggested in op5 with rr as 2nd rom but that didn't work either; either booted back to twrp or booted to a black screen. If anyone makes it work please document and share your work. I'm encrypted by the way, even though you're "supposed" to be decrypted I was able to switch between primary and the non-booting rom just fine.
Anyone having any luck with this?
matteosaeed said:
Anyone having any luck with this?
Click to expand...
Click to collapse
Nope primary install goes good with a oos rom not stock. But when you try to install a second rom it gives error 1 in twrp and rom don't boot up.
That's great! Old MultiROM user here!
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
superior888 said:
I created this thread in order to get some discussion going with the possibility to use DualBootPatcher for our Device. The device is supported and so far i got roms to patch but no luck to get it booting.
I hope we can share some information here to get us some dual booting.
Device must be rooted and decrypted for starters.
Click to expand...
Click to collapse
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN ?
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
cubandanger05 said:
Ok, so I was able to successfully patch and boot into LOS and RR. LOS as primary and as slot 1 ROM, and RR as slot 2 ROM while encrypted. This wouldn't allow me to access any files in the phone via file managers for either slot ROMs, only in primary, so you must be decrypted if you're wanting to use/see the data in your internal memory on secondary ROMs. By the way I was only able to boot Nougat ROMs, dualpatcher doesn't work for Oreo ROMs yet. I'll do a small write up tomorrow, it's 1 am here ?
Click to expand...
Click to collapse
Thanks for updating us, I'm an old multirom user as well and I'm going to keep my eye on this.
cubandanger05 said:
Here is what I did:
IF YOU DON'T KNOW HOW TO DECRYPT, BACK UP YOUR STUFF, FLASH, ROOT, ETC, STOP READING NOW, THIS IS SOME HEAVY STUFF GETTING READY TO HAPPEN
If you want functional internal storage and have access to it on all secondary ROMs you must be decrypted. This guide assumes you have all required files on phone and/or computer
1. Flash bluspark recovery (wouldn't work on codeworkx for me)
2. Back up all your data, including internal storage somewhere safe
3. Wipe system, cache, and data (not internal)
4. Coming from Phoenix, so I flashed the Nougat firmware and then LOS 14.1 and booted it
5. Flash magisk 14.0, then install dualbootpatcher app
6. After granting root permission to dualbootpatcher go ahead and go to ROMs and set kernel now
7. Now you must patch another Nougat ROM as data-slot, ID 1 or 2 or 3, whatever you want. You can use the same LOS 14.1 as a test, or the RR Nougat version
8. Transfer the patched ROM to your PC or laptop and without unzipping/extracting the zip go to META-INF/com/google/android and open updater-script with notepad++. Delete the first two lines that's start with the word "assert" and save
9. It should now ask you if you want to update the zip, hit yes. Then transfer the updated patched ROM back to your phone
(you can do this from your phone too using winrar and your favorite file manager; it s a tad easier on your computer as you don't have to extract anything)
10. Now reboot into recovery and flash the patched ROM (do not flash from within the app)
11. Now flash the dualboot utilities in recovery and it should take you to an Aroma menu where you can see both primary and and data slot ROM. Tap the data slot ROM and choose "switch to". If you did everything right it should say "succeeded" and now you can reboot your phone and should boot into the secondary ROM.
12. To root data slot ROMs you must patch the magisk zip for that data slot ROM and then flash it in recovery, the same goes for gapps. Make sure whatever you patch does not have the "assert" lines in the updater script after patching it, else you must delete these lines.
Try it and report back. I can hardly debug my own device so I can't provide much support for you. The above is what I did while encrypted, so again, if you want functional internal storage for the additional ROMs must be decrypted before you try this.
Click to expand...
Click to collapse
Thanks! I'll try this next days.
Thanks. Nothing works with Oreo as of yet i suppose :/
superior888 said:
Thanks. Nothing works with Oreo as of yet i suppose :/
Click to expand...
Click to collapse
It may be possible to have oreo as primary and flash Nougat as data slot roms. I tried with Phoenix as primary and I could boot into rr Nougat in data slot but Phoenix wouldnt boot. If someone can try rr oreo as primary and report back. I'm tempted to try with otg and see if I can install secondary roms using extsd option
*Quick update*
I was able to keep latest Phoenix oreo ROM as primary and install and boot Nougat RR as data-slot and as secondary using the latest dualbootpatcher app which may have fixed the "failed to update mbtool" error I was getting on Phoenix ROM. Also I used Magisk 14.0 for root as the latest version 16.0 kept booting back to recovery on non primary ROMs.
I'm still unable to flash Oreo ROMs as data-slot or secondary. At least we're able to keep Oreo as primary and test Nougat ROMs until dualbootpatcher app is compatible with Oreo or until some other fix is released.
Internal storage/data is still encrypted and unreadable on all non-primary ROMs; you must be decrypted prior to installing additional ROMs to have access to it, which I haven't tested yet.
See screenshots
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
es0tericcha0s said:
Thanks for keeping up with this. I'm really interested but traveling without my PC so don't want to get stuck without a backup plan. Hopefully it's sorted by the time I get back home or I'll help test some more too.
Click to expand...
Click to collapse
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Edit: Now that it's working almost as intended we should make an official "how to" thread
cubandanger05 said:
It's been relatively "safe" all the testing that I've done, not many scares, but you can never be too careful.
Click to expand...
Click to collapse
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
es0tericcha0s said:
If I wasn't out of the country, it'd probably be different. I've customized 100s of phones, 1000s of times but sometimes it's better safe than sorry. I'm great at fixing stuff because I've broken about everything I can (sometimes on purpose, sometimes not lol) but I need navigation and translation more than another custom rom I suppose.
Click to expand...
Click to collapse
? understandable