Related
After a long wait... It's time! 6.0 love for your US Cellular Samsung Galaxy S3! Get ready!
This variant is backed and based on the CyanogenMod13 (d2vzw) found here. Thanks to them!
Some things to remember BEFORE installing
This is in TESTING Stage. Expect lots of bugs!
I would not put this on a daily driver. Persue as you please.
I am in NO way responsible for you bricking your phone.
I have not tried cellular service on this variant. (Verizon is CDMA and so is US Cellular. I haven't heard any bugs regarding cell service from the forum below, so assuming it works.)
This should only be downloaded by developers, and those who have this as a second phone.
Installing
factory reset
wipe devlik/cache
install ROM
install GAPPS
*If you have issues with GAPPS on first boot, reboot. If it continues, repeat the steps above.
I recommend OpenGapps for this ROM, which can be downloaded below.
DOWNLOADS:
GAPPS: OpenGapps
ROM: CyanogenMod13
md5: eaec4bf8eebfb6fd10c0d747801cb365
XDA:DevDB Information
[ROM] [d2usc] UNOFFICIAL CyaongenMod13, ROM for the Verizon Samsung Galaxy S III
Contributors
samsung_d2usc, Master Cylinder, Stealth111, and any additional contributors that developed the d2vzw variant.
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-15
Last Updated 2015-12-15
Got a status 6 error trying to flash on D2usc. Toggled signature verification off and still got status 6 error.
Sent from my SCH-R530U using Tapatalk
I also got a zip signature verification error.
Fix for status 6 error
First of all, thanks for samsung_d2usc.
About the "status 6 error", it is normally something relating to syntax error of the updater script.
Fix:
Locate the "updater-script" and delete all the comments lines (that starts with semicolon ';' ).
Or you can use the attached one.
Just re-zip or updated the zip content (for example: Winrar allow that).
"updater-script" location:
Code:
cm-13.0-20151210-UNOFFICIAL-d2usc.zip\META-INF\com\google\android\updater-script
Nevertheless, there is no radio, neither sound!.
Good luck...
Any way to fix the sound yet?
Odd problem I have a play store I built that I "need" installed at /system as well as two other modded system apps. But when I go install my play store it will get to about a quarter of the install and then tells me no more system space that's a little odd to me as I just came from cm13 all system installs are fine and have 850mb + leftover what can I do to salve this I'm not seeing anything in logs to indicate that its a bug. As well as titanium backup is saying the space is there......
I cannot install this on the USC GS3. It keeps giving me an error when attempting to install. I have TWRP installed. Also, I have tried replacing the updater-script with the one posted above, but it did not work. Hopefully an updated version of the ROM will be available soon!
Any updates on CM13 for the d2usc??
does this actually work or no
I've been wondering if I'd be able to use D2VZW, D2SPR and D2USC roms on my D2CRI --- They were once unified so I'm guessing the formats of the roms didn't change..(?)
I know how to edit updater-scripts so that's not a problem.. I just don't want to risk a brick because 1 or 2 things may have changed down the line after they became "un-unified"
The phone is out of service so any proprietary APN's on the roms or anything really don't matter to me. I just use it as a wifi phone.
Been using this as a daily driver and no real issues. I'm having GPS lock issues, but I think it might be more hardware related since I haven't been able to get a single GPS satellite lock in the past 4 months on my previous ROM. I've had it crash randomly 3 times so far, but as far as a daily driver, totally dealable.
One big issue for me coming from LiquidSmooth(4.4.2) is the extSdCard permission stuff. Android really got annoying with that. There's an exposed module which allows the sdcard access from previous android versions which is nice
Also, anyone know where I can find a modem to flash with this? My baseband is still VRALF2.....
Problema de sonido y me salen una actualización pero a la hora de instalar me dise error 7 que puedo hacer
Yes it works but a pain to get it to
CurbThePain said:
does this actually work or no
Click to expand...
Click to collapse
I just wanted to post my success story with steps...
Download from post 1
Download 7zip command line
Extract files with: 7za x cm-13.0-20151210-UNOFFICIAL-d2usc.zip
Remove all semicolons from the updater-script file found in the directory: META-INF\com\google\android\
I opened it using Notepad++
I added a a directory called h2f and copied all the files I extracted to there
I entered that directory and then compressed the files with 7zip: 7za a h2f.zip
You can call the .zip whatever i.e. cm13-repack-UNOFFICIAL-d2usc.zip
Downloaded Open Gapps
Copied h2f.zip and gapps.zip to external sd card
Booted into Recovery mode (TWRP)
Wiped my device (factory settings)
Installed h2f.zip (it worked!!!)
Wiped Dalvik Cache
Installed gapps.zip
Installed SuperUserv2.78.zip (not required but an old habit)
Opted to install the TWRP app and as a system app
Rebooted
Took almost 8 minutes to "turn on"
Set up phone
Success!!!
Hope this helps any other d2usc users that have *lost* all hope... Together, we can keep this device alive!
~h2f
h2f said:
I just wanted to post my success story with steps...
Download from post 1
Download 7zip command line
Extract files with: 7za x cm-13.0-20151210-UNOFFICIAL-d2usc.zip
Remove all semicolons from the updater-script file found in the directory: META-INF\com\google\android\
I opened it using Notepad++
I added a a directory called h2f and copied all the files I extracted to there
I entered that directory and then compressed the files with 7zip: 7za a h2f.zip
You can call the .zip whatever i.e. cm13-repack-UNOFFICIAL-d2usc.zip
Downloaded Open Gapps
Copied h2f.zip and gapps.zip to external sd card
Booted into Recovery mode (TWRP)
Wiped my device (factory settings)
Installed h2f.zip (it worked!!!)
Wiped Dalvik Cache
Installed gapps.zip
Installed SuperUserv2.78.zip (not required but an old habit)
Opted to install the TWRP app and as a system app
Rebooted
Took almost 8 minutes to "turn on"
Set up phone
Success!!!
Hope this helps any other d2usc users that have *lost* all hope... Together, we can keep this device alive!
~h2f
Click to expand...
Click to collapse
So does this fix sound?
I was able to watch a YouTube video and it had sound. However, I have since changed ROMs to LineageOS 14.1 for my d2usc. Having really bad network drops with it though.
h2f said:
I was able to watch a YouTube video and it had sound. However, I have since changed ROMs to LineageOS 14.1 for my d2usc. Having really bad network drops with it though.
Click to expand...
Click to collapse
Nice, I'll try out the LineageOS 14.1 port you made. I tried changing the updater script of LineageOS 14.1 for d2vzw to flash on a d2usc once, everything worked except sound, data etc.
V0idst4r said:
Nice, I'll try out the LineageOS 14.1 port you made. I tried changing the updater script of LineageOS 14.1 for d2vzw to flash on a d2usc once, everything worked except sound, data etc. Care to elaborate on how you ported it with a working baseband?
Click to expand...
Click to collapse
can you please provide me with the link to lineageos14.1 d2usc ?
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
You need the recovery from here to flash sagaopt roms IIRC.
jc1993 said:
You need the recovery from here to flash sagaopt roms IIRC.
Click to expand...
Click to collapse
Yes, that is the instructions I have been using and experiencing trouble with. I'll try it again.
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
tag68 said:
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
Click to expand...
Click to collapse
Well I tried it again with no success.
Can someone confirm for me that the ONLY difference between Saga and Sagaopt ROMs is the prerequisite partitioning and filesystem types required? ie, convert filesystems and SDcard filesystem to EXT4.
Trying to install CM13 Sagaopt complains something like "unable to execute the binary updater in the zip file". Trying to install CM12.1 Sagaopt gives exactly the same error so I guess the prerequisites are not right.
My phones are standard HTC Desire S and I assume that's okay?
I downloaded the ROMs from the Open Desire site after selecting device Desire S.
So still scratching my head on this one.
here my desire s runs now cm12.1
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
the sagaopt rom uses the complete internal memory for the system (for a stable rom use latest CM12.1 nightly CM13 has ram and bluetooth issues)
Preparing and updating
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1679338 for new S-OFF HBOOT
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1858508 for new RADIO and Firmware (only B the rest is for a better stock 4.0.4 android)
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
@Layer_DE...........thank you for that. Certainly upgrading to TWRP v2.8.7.1 is key.
I flashed recovery file "TWRP-recovery-sagaopt-2.8.7.1.img" and the "error executing binary updater in zip" is gone.
Yes, I'm having some issues with CM13 so will try your suggestion of CM12.1
Many thanks. I'll post back with any further issues.
@Layer_DE.......I've flashed CM12.1 and it boots. Can you tell me which gapps file you flashed please? I'm finding that whatever gapps file I flash I seem to lose the virtual keyboard function. Using just CM12.1 the virtual keyboard works fine. I'd like to get the Play Store functioning correctly and its icon on my home screen. Thanks.
opengapps.org
ARM 5.1 pico
it works fine BUT for the first app you download you need more than a hour and every appinstallation takes very long
I'll give that a go. Thanks.
sent from my HTC smartphone
Hi All,
Just thought I'd give an update on this one........
I flashed TWRP 2.8.7.1 recovery and used it to set all filesystems to type ext4.
Then installed CM12.1 no problem.
Then installed opengapps 5.1 pico as suggested. No problem.
All working fine with that. In fact extremely good. No problem installing/uninstalling apps at all.
Still can't get CM13 (Marshmallow) to work. It will install but on reboot doesn't behave.
- You had me at 'Hello'...
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Nunya-Biz said:
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Click to expand...
Click to collapse
the CM12.1 is very stable and only has typical android bugs (found no device specific things) and the official cm people hasn't used the kernel 3.0 source of the desire from android 4.0
for istallation:
1. download adb from http://forum.xda-developers.com/showthread.php?t=2317790
1.1 download and install adb driver
1.2 if you use windows 8 or higher use the fastbootfix form https://opendesireproject.org
2.install adb to "C:\Windows" (pro: no path needed)
3.check android version in system settings if it is lower or lower2.3.X (if its not it could be ****ty) than check bootloader version
3.1 turn off fastboot in battery settings
3.2 power don phone
3.3 boot phone with vol down clicked and if its -REVOLUTIONARY- or if its 0.98.x s-off or 2.0X s-off go to 6
if its 0.98 s-on you go to 5
if its 2.02 ask anyone else on my desires with 2.02 s-off newer worked for me but you can try it (go to 4) or only unlock it
http://www.htcdev.com/bootloader select HTC Desire HD and dont upgrade anything (start at step 1 skip preparation) after that go to 8
4.download the oldest rom with you branding from http://androidruu.com/?developer=Saga
4.1 http://forum.xda-developers.com/showpost.php?p=18746686 downlad misc_version
4.2 http://forum.xda-developers.com/showthread.php?t=1312859 download DooMLoRD_v4_ROOT-zergRush-busybox-su.zip and extract zergRush
4.3 go to folder with misc_version and zergRush and open cmd there and type
adb push misc_version /data/local/tmp/
adb push zergRush /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 777 zergRush
chmod 777 misc_version
./zergRush
./misc_version -s 1.27.405.6
exit
exit
exit
4.4 execute the firmware form step 4
5 download and follow http://rev.alpharev.nl
6 follow http://forum.xda-developers.com/showthread.php?t=1679338 (optional)
7 follow B in http://forum.xda-developers.com/showthread.php?t=1858508 (optional)
8 follow my first tuturial (if you need help post it to the tread)
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
ElFidel said:
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
Click to expand...
Click to collapse
Try CM11 it runns very smooth and is fine (older than 4.4 isnt 100% supported by app developers)
I installed CM13 as well on my Desire S - at first it was really slow. Until I bought a faster SD card as I saw that the internal memory was emulated on the SD card. Therefore I tried it with a U3 speed SD card - now it is workable - I am happy to have cm13 installed
@schneert
What's the size of your SD Card? What do you mean by 'workable'?
@zurpher: I bought a 32Gb SD Card., therefore I have 32GB stated as internal memory. It is workable in that sense that it is fast enough to use it without very much slow issues. It is still not fast but I guess that is because of the RAM of the device.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:
Lenovo Vibe X2 Custom roms
Finally released my first rom, for a uncommon device - Lenovo VIbe X2.
Very thanks to bug reporters. Should you have any bugs found on my ROM, please reply in this forum. :highfive:
Notes
Code:
To support all versions, you must install a modem. (the default modem is for EU, pre-installed for first boot.
Please go to [URL="https://forum.xda-developers.com/android/software-hacking/lenovo-vibe-x2-modems-t3564185"]this link[/URL]
Since I haven't found the method of building custom rom for dual-sim devices,
this rom currently 0support one sim only.
Need to install open gapps after first setup.
CM 13 Versions(development temporarily stopped)
Code:
20170203 - Installer error ( not able to install at all )
20170628 - AROMA error ( not able to install at all )
20170629 - AROMA installer removed
- Tester needed! ( My vibe x2 is broken )
RR-N Versions
Code:
20180118-24 - Boiling in the terminal [COLOR="Red"]error:[/COLOR] Unknown type name ' MTKLegacyGnssSvStatus '
How to installNote: You're going to lose all your installed apps, app data, system, etc.
1. Upgrade your system to android 5.0+ if available or flash the os here BACKUP ALL YOUR DATA INCLUDING INTERNAL STORAGE AS YOU'LL LOST THEM!!!
2. Right after flashing whole system flash the TWRP recovery here Thanks for BOPOH' Ok
3. Download the latest version of the rom, which should be here within one week
Links
AFH:
CM 13
RR-N
Hi NamelessXXV thank yuo very much for your work. When I try to install your rom I gen an error.
I'm using TWRP recovery and I'm on a x2-CU
Thank you.
Paolo
Lenovo vibe X2-AP
NamelessXXV said:
Cyanogenmod for Lenovo Vibe x2 all version
Finally released my first Cyanogenmod.
Very thanks to bug reporters. Should you have any bugs found on my ROM, please reply in this forum.
Code:
To support all versions, you must install a modem. Please go to [URL="https://forum.xda-developers.com/android/software-hacking/lenovo-vibe-x2-modems-t3564185"]this link[/URL]
Need to install open gapps after first setup.
I'm not able to install modem on my lenovo vibe X2-AP. Please help:angel:
Click to expand...
Click to collapse
Attention please
Links are updated in the main post!
/* Just as an announcement for people who subscribed */
moamahi said:
Hi NamelessXXV thank yuo very much for your work. When I try to install your rom I gen an error.
I'm using TWRP recovery and I'm on a x2-CU
Thank you.
Paolo
Click to expand...
Click to collapse
Thanks for your reply! See above:fingers-crossed:
NamelessXXV said:
Thanks for your reply! See above:fingers-crossed:
Click to expand...
Click to collapse
Thank you for answering
I've tried new version (20170628) and I get: SYNTAX ERROR!!! aroma -config on line 181 col 23.
In another life I've been a developer so I checked and I found some blank spaces unneeded:
"ini_get("rom_name") + " by " + ini_get("rom_author") +
"\n\n"+
"ini_get("rom_name")+" by "+ini_get("rom_author")+"\n\n"+
But now I get again Error 1 and update fail.
Thank you again
moamahi
I have a vibe X2 AP device.. I was searching for this for a long time. Im really happy to see this.I tried installing the rom. it worked fine after pushing the modem file to required location. But I'm not able to use my second sim, It's not shown.. I tried my best to get it work,but it didn't ..
I tried editing build.prop and change single sim mode 'ss' to 'dsda'..
I tried replacing '/system/etc/firmware' and '/system/etc/mddb' folders with that of the AP folder, still no luck!!..
I want some help to get it Working...
This rom work on china version?
pzy64 said:
I have a vibe X2 AP device.. I was searching for this for a long time. Im really happy to see this.I tried installing the rom. it worked fine after pushing the modem file to required location. But I'm not able to use my second sim, It's not shown.. I tried my best to get it work,but it didn't ..
I tried editing build.prop and change single sim mode 'ss' to 'dsda' and sim number to 2 ..
I tried replacing '/system/etc/firmware' and '/system/etc/mddb' folders , still no luck!!..
I want some help to get it Working...
Click to expand...
Click to collapse
Which version worked for you..
Crazy hacker2499 said:
Which version worked for you..
Click to expand...
Click to collapse
His latest Build. But I didn't copy the modem provided by him..I took it from my own stock rom. Then it started showing my Primary sim, Secondary sim was not shown and gave an out-of-coverage-area while calling to it..
Can not install this rom in my phone X2 CU
I try to install the twrp in my device, but i cant, I was reading a lot of forums but I can not find a version for my Lenovo Vibe X2 CU, Can you help me, sorry for my english.
when the rr-n realese
i"m waiting for it my plasure because of my bad english
I am not a professional
As you had seen in the change log I faced a problem that I don't know how to solve it, any professionals can help out here?
Code:
device/lenovo/x2eu/mtk/gps/hal/gps_mtk_aosp.c:1454:5: error: unknown type name 'MTKLegacyGnssSvStatus' MTKLegacyGnssSvStatus sv_status_gnss; ^
ı do some researchs abot this rom unfortunatelly ı couldnt fount anthing abot it.
can you share rom with problelms
for two sims?
i dont can get rr
New member, had to post it in this section.
This is a test version of MultiROM.
WARNING
It is DANGEROUS to flash MultiROM to your device. It can cause data loss. If you have important files on your phone, NEVER try to do that.
Introduction
MultiROM is a boot manager that allows you to flash multiple roms into the device.
This port for Polaris is based on Tasssadar's work and Vasishath's modification. It seems to work fine now.
You can refer to Vasishath's original post for installation guide.
Reference Links:
[XDA Thread] https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
[Github][MultiROM] https://github.com/ARTI5T/multirom
[Github][Modified-TWRP] https://github.com/ARTI5T/android_bootable_recovery
Download link is below.
Notes:
* You can use MultiROM only with decrypted devices.
* Flash a patch to disable force encryption after flash a ROM with force encryption.
* Don't manually encrypt your data in any ROMs.
* If you want to flash treble GSI, choose A-only images.
** Flashing A/B GSI is theoretically possible if you flash it to a secondary ROM which supports system-as-root. (NOT TESTED)
* Unfortunately, until now, we cannot update a secondary ROM with treble GSI. Now you can update a secondary ROM with system.img.
* Always backup your file before flashing. Especially boot.img or boot partition.
* Be careful with your lockscreen password. You can only set password in either primary ROM or secondary ROMs. Refer to vasishath's thread for more details.
* Not all ROMs are compatible with MultiROM.
* Android 10 can be flashed as a primary ROM. If you have an android 10 ROM as primary, you need an android 9 boot.img and vendor.img in case you have GSIs based on android 9.
Known issue:
* Sometimes touch in TWRP or MultiROM boot screen doesn't work. If you are in TWRP, just reboot. If you are in boot screen, you can also reboot or use volumn +/- instead.
* If you want to uninstall MultiROM, you may need to flash the stock boot.img (In case it can't boot). So please backup your boot.img before flashing.
* Still some bugs with system/vendor compatibility verification. If you meet such errors, please flash a "base firmware" (e.g., MIUI) first, and then flash your zip in "List ROMs".
* In some rare cases, flashing a zip in secondary ROMs may cause primary ROM damage.
This port is only for DECRYPTED device. Don't flash if your device is encrypted.
Please BACKUP before you flash MultiROM.
We're not responsible for any loss caused by this modification.
Download link:
[Google Drive] https://drive.google.com/drive/folders/1C2d3GQT5WVsw83XU6J5qA_oJOYMxyXNX?usp=sharing
Update Log:
28-01-20: Support Android 10 as secondary ROMs. Fix bugs which in some cases cause error 7 when flashing.
17-08-19: Add "Install system.img/vendor.img" in "List ROMs".
16-08-19: Add "skip compatibility verify". Fix some small bugs.
15-08-19: Merge omnirom 3.3.1 source code.
14-08-19: Initial release
Tested on:MIUI11(Android10);ArrowOS(Android 10);LOS17;Flyme8(Android9)
Fantastic. Will try it tomorrow morning and report. Looking forward to it!
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
edit:
Started completely over from scratch. Completely wiped data, installed latest vendor/firmware/ etc...
Still have the same issue, but different flashing error:
With pixel3rom
"string resource 'zip_compatible_err' not found.
Using default value.
ZIP Treble compatibility error!
invalid zip file format.
And then it just aborts.
With arrow OS:
Zip treble compatibility error
invalid zip file format
And then it just aborts.
Firipu said:
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
Click to expand...
Click to collapse
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
__ART1st__ said:
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
Click to expand...
Click to collapse
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Okay. I'll try to update my code. Perhaps a looooooong time
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Now you can try the new recovery.img with version 3.3.1 and let me know the result. It may fix that issue (haven't tested yet myself)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Just remove the asserts lines in updater scripts. That would do it.
Sent from my Pixel 3 using Tapatalk
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
It always happened to me with multirom and dualbootpatcher. You have to delete locksettings files in data/system directory...
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Lucas_Maximiliano said:
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Click to expand...
Click to collapse
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Click to expand...
Click to collapse
If you have the password problem, go to vasishath's thread and download a patch to clear password.
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Install fw+vendor 9.7.25.eu,for me resolve the problem
Sent from my [device_name] using XDA-Developers Legacy app
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Are you sure your are using MIX2S Polaris? Not Mi8 or Poco F1 or MIX3?
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Writesin said:
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Click to expand...
Click to collapse
Did you boot any version of MIUI successfully? Could you try another version to see if it can boot? It can sometimes be the ROM's problem. If it still fails to boot, please tell me the version that can boot and the version which can't boot. But I am a student so maybe not too much time on debugging.