Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod 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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Viewsonic G Tablet, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0.1-smb_a1002
Download: link
Mirror: link
MD5sum: 6a47f51bac0ee3657749873eeac721be
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Thank you!!
Thank you. I just installed cm7.1 and it is excellent!
Can I flash this with the 1.2 bootloader?
Edit: nope, just tested it out, you need to be on 1.1 bootloader to flash this rom as is.
The first thing I noticed is the status bar keeps force closing. Could just be me. I did wipe everything, installed the update, gapps, and google talk. Maybe I'm supposed to install only 1 version of gapps. BTW I am running boot loader 1.1 for those who might ask about it. After installing a few things, I notice my status bar just isn't there at all. I think I'll try installing only 1 version of the gapps and see if that helps.
Another edit. The google talk gapps file only has Talk.apk in it. The regular gapps has the regular google apk files. I tried wiping and installing the cm71 update + gapps and my status bar still force closes. So which file should I be installing?
Does this rom have hw acceleration and camera working?
Thanks
Enviado desde mi GT-I9000 usando Tapatalk
Aside from froyo rom, none of hardware acceleration in any GB/HC rom works.
as for camera, see the front post
From the first post in this thread, the first download link for cm71 shows 404 file not found. The second link to goo-inside.me shows "This page has been removed or never existed!"
From the official post, the first download link using download.cyanogenmod.com says 404 file not found.
From the official post, the second link works. I checked the md5sum and it matches so this is a good link.
http://goo-inside.me/cm/smb_a1002/stable/update-cm-7.1.0.1-smb_a1002-signed.zip
MD5sum: 6a47f51bac0ee3657749873eeac721be
Now going to http://download.cyanogenmod.com/?device=smb_a1002 the
MD5sum: 3e8bd3af4dc310210c78f1965eb8c342
(Don't use this one. This file is the one I used but the status bar gets force close issues)
fury7 said:
Aside from froyo rom, none of hardware acceleration in any GB/HC rom works.
as for camera, see the front post
Click to expand...
Click to collapse
thanks for the info. I think this info should be stated on the OP of every GB/HC rom. that way we would avoid that kind of questions of early adopter of the gtablet (like I just did)
after flash touch not work? WHY??? I try to reflash stock rom, full wipe and repartion SD but problem remains!
Having a few problems here....just noticed in the post above it only works on 1.1 boot.....can we confirm this? Because this might be my problem. I'm coming from Flashback and I'll have to NVflash back to 1.1 if so.
dobah said:
The first thing I noticed is the status bar keeps force closing. Could just be me. I did wipe everything, installed the update, gapps, and google talk. Maybe I'm supposed to install only 1 version of gapps. BTW I am running boot loader 1.1 for those who might ask about it. After installing a few things, I notice my status bar just isn't there at all. I think I'll try installing only 1 version of the gapps and see if that helps.
Another edit. The google talk gapps file only has Talk.apk in it. The regular gapps has the regular google apk files. I tried wiping and installing the cm71 update + gapps and my status bar still force closes. So which file should I be installing?
Click to expand...
Click to collapse
Both Stable 7.1.0 and Nightly 61 are having this status bar FC problem.
Nightly 62 and stable 7.1.0.1 are both ok.
What boot loader does this rom support?
What boot loader does this rom support?
bootloader 1.1
for bl1.2, you have to edit updater-script to check for upc300.
unzip the cm7 zip file, edit /META-INF/com/google/android/updater-script, replace in the first line, harmony to upc300
rezip the files back to a cm7-fixed-bl12.zip
also I find flashing one of the kernel zip (eg pershoot's gingerbread 1.2 kernel http://droidbasement.com/gtab/kerne...2632.46_gb_newbl-oc-uv-xtra-vfp_fp-083111.zip ) after flashing cm7 helps with first boot stuck at 3 birds problem.
google market (gapps) can be download from http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps get the one for Cyanogenmod 7
or you can merge the kernel zip + gapps zip (110828) into cm7 rom zip.
Sent from my HTC Glacier using XDA App
Happy to report back after a week of solid daily use that this is an amazing ROM for the Viewsonic G-Tab. As soon as it was confirmed that this was a 1.1 Bootloader ROM I just did the simplest thing and just NVflashed back to 1.1 with Clockwork built in (always use the one from "Viewsonic G Tablet for Dummies" website). It really is the easiest way because it takes less then 2minutes to have a bone stock 1.1 G-Tab.
Flashed CyanogenMod 7 V7.1.0.1 and it went on smoothly the first time with no troubles at all. Flashed the google apps as well and have had no major problems at all. Yeah there's the occasional small problem ( I think the Facebook App gives me problems time to time) but overall its great. The speed is superior and the customizing options from widget size to lockscreen are just nice.
I'm still playing with it and welcome anyone who's found anything great that this ROM does over others to please share. I know problems I've had in the past with other ROMs have been accessing both the internal harddrive as well as the SD card seperately. Just remembered I have to try that for this one.
Anyway, great work and happy to report back my positive remarks regarding this ROM. Its always good to have a new ROM I can rely on for a daily driver...!!!
Problems with stable 7.1.0.1 and Nightly 67:
Youtube not able to view HQ video, audio only
Facebook only works when first install, then force-close every time subsequently
XDA force-close upon exit, not saving userid/password
Map force-close overnight
Same problems whether installed on BL1.1 or BL1.2
I have discovered a problem I'm hoping someone might know how to fix on this Rom. When using Pandora, every other song plays in super slow mode. You have to skip to the next song to fix it. Extremely annoying. Anyone have a fix?
Sent from my PC36100 using xda premium
Hi all
Im trying to compile OmniRom for Galaxy Note 2 N7100.
Did everything as instructed.
When running "brunch n7100" I have an error:
=============================================
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
WARNING: Trying to fetch a device that's already there
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/n7100/omni_n7100.mk]]: "vendor/samsung/smdk4412-common/common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'omni_n7100'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
=============================================
What should I do to fix it?
Thanks
EDIT: OK, "The Muppets", of cause. Not it builds...
sms2000 said:
EDIT: OK, "The Muppets", of cause. Not it builds...
Click to expand...
Click to collapse
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
PonsAsinorem said:
First off, I'd use DonkeyCoyote instead of TheMuppets. Entropy said TheMuppets wouldn't work, but he might have been speaking about only one device. Still I'd use DonkeyCoyote instead.
Still not building?
Click to expand...
Click to collapse
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
sms2000 said:
I'm using VM on Win7 8Gb machine so it's slow. Last time it stopped on Email right after successfully building boot.img.
Attempting to rebuild.
I'll try my next with DonkeyCoyote.
Click to expand...
Click to collapse
It didn't not stop...
Actually it is compiling libchromodium.so (forget how it spell), which is 1.2GB in size.
Just let it run for few hours, it will completed eventually.
PS: I'm using VM on Win8.1 4GB, no complain here.
Sent from Windows 98
Yep, it fails again and again on 'libwebviewchromium.so'. The well known 'Error 1' aka not enough RAM.
I recently built a dedicated computer (8Gb + Haswell 3220) just for ROM compiler but have no time to install it properly. Dealing with VMs is not good.
My VM has 4Gb RAM of total 8Gb installed. I know I need 8+ but have to wait till new RAM received.
For now the thread is on hold.
Thanks for all your help.
EDIT: Just for the small experiment I added a 8Gb 'swap' partition to VM and the following build succeeded using no more than 450Mb of it.
I think we need 6 to 8Gb of RAM for good.
Now the question is would it boot and run for good? But we will see...
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
dynomist said:
Ya I did set the swap partition to 8gb... And it will boot nicely.
If it didn't boot, jus replace/delete the media_profiles.xml
Another note, my Bluetooth and hardware decoding /encoding fail... Pls test it on ur system too.
Sent from Windows 98
Click to expand...
Click to collapse
I indeed failed to boot. Just the black screen with nothing. I think it was a very bad idea to use TheMuppets with "jallybean".
And what is "media_profiles.xml" for? And where?
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
dynomist said:
U r using jb blob?
i think OmniRom hv all the stuff u need
http://docs.omnirom.org/Samsung_Galaxy_Note_II
___
Btw did ur screen show omnirom animation?
If yes u r lucky, u need to enabled the ro.adb.secure=0 in ur build.prop, then only you can use adb without authorization to troubleshoot.
Type# adb logcat > logcat.txt
___
Google media profile...
Sent from Windows 98
Click to expand...
Click to collapse
Yes, if you can download the closed source parts from the phone itself. I cannot. Something wrong with switching 'adbd' to 'root'. It switches sort of but locks at the downloading (never finishes).
Currently I'm recompiling with 'DonkeyCoyote'.
'Nightly' build fails to pass boot animation
I downloaded and installed OmniRom Nightly. Not good.
It cannot pass the boot animation. The OMNI BA just loops across different colors for 15 minutes already.
As I remember the same problem I have with any AOSP or CM ROM. I suspect the problem is the boot loader related.
When I installed my first 4.3 ROM it required the latest BL and I flashed it. Should I downgrade now? Which version of BL works for sure and where can I find it?
Thanks.
EDIT: I verified. My Bootloader - MJ5. Is it OK?
EDIT 2: Downgraded to DMF2 and succeeded installing OmniRom Nightly. Testing...
glad that you able to solve the booting prob...
pls update the roms status after u done with your testing
Hi all, here I wish to continue porting OmniROM from the P4/P4wifi over to our device the P5/P5wifi.
*Please note that this is simply a port of an already built rom. It was not built from source therefore anything that you may find to be broken will more than likely remain broken until it is fixed in the parent ROM.
-Many thanks to the builder of this rom @AAccount. His hard work made this ROM possible. :good:
-Thanks to @jolinnard whose kernel is being used in these ROMs. :good:
*On first boot the keyboard will not be showing. The fix is simple. Go to settings>Language & Input. Tap on Current Keyboard and flip the toggle next to Hardware. The keyboard should now be fine.
Working:
Everything works on the P5 AFAIK
Not working:
SELinux---------Need a recovery that supports it.
To those looking forward to a P5 3G rom then please note that there will not be one any time soon. AAccount has stopped building for the p4 3g so that means we don't have a 3g rom to port anymore. So unless AAccount starts porting for the p4 again there won't be a P5 rom.
Flash Instructions
Wipe data, system, cache, dalvik if coming from another ROM. If ugrading to a newer build then a simple Dalvik and cache wipe will do
Flash the ROM zip
Flash GAPPs (Thanks to @jolinnard)
Flash SuperSU
Reboot and enjoy
Original ROM thread
Credits
@AAccount - for the ROM
@jolinnard - For the kernel
@decatf - for his work on the p4 kernel which is used here that delivers great performance
If you helped out and I missed you in the credits then send me a PM and you will be credited
This port has been discontinued!!
"See why
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
@L3Ron ,i will give it a try.
@jolinnard
If you want to port or start with omni source? Nice to See your work for our Tab 8.9.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
Awesome!! Erased my internal sdcard by accident last week. Luckily I have the same files on my Nexus 9 so I was saved. This port works great for me. Should I even port for the P5? AAccount stopped building for the p4 as of May 23. Reason being that 3G doesn't work but oddly enough it does work on the P5 using our modified KK kernel and your data_on script.
bierma32 said:
@L3R0N ,i will give it a try.
Click to expand...
Click to collapse
Great. Tell me how it works for you.
L3R0N said:
Great. Tell me how it works for you.
Click to expand...
Click to collapse
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
bierma32 said:
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
Click to expand...
Click to collapse
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
julen163 said:
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
Click to expand...
Click to collapse
I tried different setting at the advanced configuration of WLAN settings with out success.
bierma32 said:
I tried different setting at the advanced configuration of WLAN settings with out success.
Click to expand...
Click to collapse
I have no such problems. My WiFi connects just fine. Try turning airplane mode on for a moment then turn it back off and try connecting again. Could it be the kernel? I'll p.m you a kernel to try and see if it fixes anything later on. Any logs?
OP has been updated with links to the new build released by AAccount today. According to him there were no major changes, just the usual Omni sync.
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Edit: used the sideload option with ADB and used the omni-5.1.1-20150706-p5wifi-HOMEMADE ROM
Got also problems with the WiFi connection. My network uses 192.168.2.xx range
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
No you are not the only one. This was reported to me earlier today by another user. I'm in the process of uploading a new zip to androidfilehost and another to mega. They will be up soon.
Nonomen said:
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Click to expand...
Click to collapse
I'm sorry to hear that. You can use adb to push a zip file to your sdcard for installation.
Use this command
Code:
adb push romname.zip sdcard
Or you could use sideload to install one as well. in twrp go to advanced then select adb sideload and connect your tab to your pc. Open up windows command prompt and type
Code:
adb sideload romname.zip
This should get a rom installed to your tab.
File has been re-uploaded. It opens fine now and should work fine.
L3R0N said:
File has been re-uploaded. It opens fine now and should work fine.
Click to expand...
Click to collapse
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Nonomen said:
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Click to expand...
Click to collapse
I have absolutely no problems with the ROM. No force closes or anything. Can you try a clean install of the 0716 build and see if it fixes anything?
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Nonomen said:
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Click to expand...
Click to collapse
There aren't any huge differences but here are a few notable changes
1) Ability to change battery icon
2) Battery color changes based on charge level
3) Pre rooted
4) Performance settings app included
5) Omniswitch recent
And a few others nothing big. IMO I prefer the browser in the omnirom over the aosp browser and the omni keyboard over the Google keyboard in the aosp ROM. But that's personal preference. Try both and pick a side *twix ad*
how i can use this rom for the p5 ?
thanks
4rch0 said:
how i can use this rom for the p5 ?
thanks
Click to expand...
Click to collapse
Edit the updater script and at the top where you see p5wifi simply delete the "WiFi" part so only p5 remains. Save the file put it back into the ROM zip and flash. Or you could simply flash the p5wifi recovery and you'll no longer have to worry about editing the script.
For future ROMs I think I'll remove the assert lines in the updater script so nobody else will have to worry about them.
I'm NOT the developer/creator of this app/method. Chenxiaolong is. Here's the link to the official thread: http://forum.xda-developers.com/showthread.php?t=2447534
Credits: @chenxiaolong - This guy is just great. Our device required many additional hacks and changes to work because of its crappy closed-source update-binary and closed-source Mediatek sources. This awesome dev had to work a lot to get this work fully on our device. Yes, he did. Debug builds, logs, debugging, reworking and all, and he never stopped. That's just amazing. So, I want to thank him wherever you see his post and if you can PLEASE donate as your token of appreciation. :good::fingers-crossed:
@911-Future_Maker Some help and tips in the initial stages.
@FeyoMx Initial helps since my phone wasn't rooted then.
Me. No I'm not exaggerating. I did my fair share of work in testing debug builds and providing logs and testing again. So, press thanks if this worked for you :victory:
Disclaimer:
Neither I nor the dev is responsible for any damage this app does to your device.
You MUST have a nandroid backup in case something bad happens.
Only do something after the whole thread a few times.
Yes, this is true multibooting. Install as many ROMs as our internal storage allows. I can't install more than 3 ROMs (on extsd-slot) as I have a lot of apps.
Here's the procedure:
1- Download the latest version of the app from https://snapshots.noobdev.io and the DualBootUtilities.zip (https://snapshots.noobdev.io/DualBootUtilities-8.0.0.r2162.gc717564.zip)
Note: Only version 8.0.0.r2157.g7d47ab8 and newer completely supports our device.
2- Select ROMs from the navigation drawer of the app on the left
3- Grant supersuser/root rights when it asks
4- Click "Set kernel" if it is asked.
5- Click the three-dot menu on the first ROM, which will be your current ROM.
6- Scroll down and click update ramdisk
7- Reboot
8- Select "Patch Zip file" from the navigation drawer
9- Press the + button and select the zip of the ROM you want to install.
10- Select the slot to which you want to install the ROM.
Take either a data-slot or an extsd-slot.
I recommend using an extsd-slot because the internal memory gets full very fast. Even if you install to extsd-slot, only /system/ is stored on the SD card because having data and cache as image files on the SD card shortens its lifespan by almost a week.
11- Patch the GApps, Xposed or any other zip you want to install to this ROM the same way giving the extsd-slot number you gave for the ROM.
12- Install the patched zip. There are two ways:
I) in recovery (highly recommended)
II) through the built-in zip flasher. Click on the circle in the ROMs page. Add the zips with the plus button. Click the tick.
13- Reboot. It'll automatically reboot the new ROM if it was installed successfully.
14- Voila!! You are now multibooting!
To switch between ROMs, you need the Dual Boot Patcher app on that ROM. Navigate to ROMs, and click you ROM you want to switch. A tick will appear.
Reboot.
EDIT: Forgot about app sharing. Here it is
App Sharing:
Yes, this feature allows you to share the data of your apps across the ROMs. That means you'll have your Chrome tabs open as you left it in the other ROM. Cool !
Instructions:
1- Navigate to App Sharing settings in the navigation drawer.
2- Select "Share individual apps" and reboot.
3- Select the apps you want to share in "Manage shared apps" and select "Use shared data".
4- Reboot to the same ROM. This is very important. If you switch ROMs, you'll lose your data and you will have uncheck "Use shared data" to get it back.
5- Reboot to the ROM with which you want to share data.
6- Install the app if it isn't installed.
7- Do the same as steps 2, 3 and 4 in that ROM. Yes, rebooting to another ROM there can also result in data loss.
8- You will now have the same data across all those ROMs :victory:
I've tried sharing WhatsApp, Google Chrome, a game and Tapatalk and all these work perfectly fine.
Bugs:
I haven't seen any (of the app, do NOT report ROM bugs here)
If you find any, provide logs. If it was while installing provide the recovery.log from TWRP>Settings>Copy logs to SD
If ROM not booting, flash GetLogs.zip from the website (link: https://snapshots.noobdev.io/misc/getlogs/GetLogs-20160120.zip)
If a ROM is not booting, don't worry, reboot to recovery, and flash the DualBootUtilities.zip and switch to primary ROM.
N.B.: The touch screen doesn't work in AROMA on our device. So, navigate using volume buttons. It's a bit weird, but you'll get you used to it.
Yes, it's risky. That's why you should have a nandroid backup.
I'll try to help you as much as I can, but I'm not a dev. So, if you provide logs, I'll see and if it is something new, I'll tell the dev. He is usually busy.
N.B.: This whole post was written on my phone, so it's bad, I know. I'll edit it when I get time.
Please press thanks if I have helped you.
Good guide but if the roms support sdcard as default storage then its worth dual booting
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits.
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
sandeep.sethi said:
Good guide but if the roms support sdcard as default storage then its worth dual booting
Click to expand...
Click to collapse
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed. Btw @sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. :laugh: 5 fast vibrations and back to recovery.
911-Future_Maker said:
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits.
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed.
Click to expand...
Click to collapse
4 roms ? are they all vibeui based ??
whats ur internal memory space left
---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------
911-Future_Maker said:
@sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. :laugh: 5 fast vibrations and back to recovery.
Click to expand...
Click to collapse
i dont know bro maybe space is interferring it
sandeep.sethi said:
4 roms ? are they all vibeui based ??
whats ur internal memory space left
Click to expand...
Click to collapse
Of course, screenshot attached. Unfortunately only around 500MB free internal storage.
911-Future_Maker said:
Of course, screenshot attached. Unfortunately only around 500MB free internal storage.
Click to expand...
Click to collapse
its the problem
internal space will be less available
sandeep.sethi said:
its the problem
internal space will be less available
Click to expand...
Click to collapse
Wait! That was an old shot my bad. The one attached below is representing my current usage. I'm using BlissPop, it's a monster.
Interestingly enough I'm same person with the guy who's using the niklabs username @needrom. lol Nice to meet you mate.:highfive:
To be honest 4 roms are overkill, 3 roms can serve me just fine.
sandeep.sethi said:
Good guide but if the roms support sdcard as default storage then its worth dual booting
Click to expand...
Click to collapse
Thanks.
911-Future_Maker said:
Congrats for this great tutorial my friend! I'm sure it will help many peeps having questions around. Also thanks for mentioning me in the credits. [emoji14]
---------- Post added at 18:34 ---------- Previous post was at 18:30 ----------
Why? You can dualboot no matter what's your default write disk. You must just have enough free space. Using 4 roms currently, my default disk is internal storage and my primary rom has a tons of apps installed. Btw @sandeep.sethi I'm having problems trying to dualboot your latest AICP rom. [emoji23] 5 fast vibrations and back to recovery.
Click to expand...
Click to collapse
Thanks. You are welcome [emoji6]
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
911-Future_Maker said:
Wait! That was an old shot my bad. The one attached below is representing my current usage. I'm using BlissPop, it's a monster.
Interestingly enough I'm same person with the guy who's using the niklabs username @needrom. lol Nice to meet you mate.:highfive:
To be honest 4 roms are overkill, 3 roms can serve me just fine.
Click to expand...
Click to collapse
nice to meet you too
failed to flash zip
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Pradeepnegi said:
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Click to expand...
Click to collapse
Which is your ROM??
It's because of the ro.build.product of your build.prop
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Pradeepnegi said:
Sir I'm not able to flash zip. I'm getting error. Image is attached below. Please help
Click to expand...
Click to collapse
This is easy. I'll guess you're installing MIUI or CM right? Because these roms usually contains this limitation about "hermes" only devices. Just open the updater-script which can be found in META-INF/com/google/android path, open it as text via some root file manager and edit it removing the following lines:
Code:
getprop("ro.product.device") == "hermes" || abort("This package is for \"hermes\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Success.
Hey @Salman A. bro I have a little update on your question about that can we install a VibeUI on extsd-slot or in any other slot different than primary. Good news - it works like a charm, screen attached from last night when I was again playing with flashing roms on my phone lol.
Installed VibeUI_1604_ST on extsd-slot all working, I just edited the updater-script to prevent boring errors like that one above removing these line:
Code:
getprop("ro.product.model") == "Lenovo K50-t5" || abort("This package is for \"Lenovo K50-t5\" devices; this is a \"" + getprop("ro.product.model") + "\".");
So now running VibeUI from my extsd card lol, I flashed it just to confirm it's possible, but I think I'll wipe it and flash it again as primary because I mostly play games on VibeUI and I don't want to run a heavy game from my extsd while the entire phone system is also running from the card. It will slow down the things.
Meanwhile I still can't make the AICP rom by sandeep a multiboot ready. Sometimes it hangs at the logo, sometimes vibrates 5 times and reboots back to recovery. I posted at the dualboot thread and really hope that Chen will help me.
911-Future_Maker said:
Hey @Salman A. bro I have a little update on your question about that can we install a VibeUI on extsd-slot or in any other slot different than primary. Good news - it works like a charm, screen attached from last night when I was again playing with flashing roms on my phone lol.
Installed VibeUI_1604_ST on extsd-slot all working, I just edited the updater-script to prevent boring errors like that one above removing these line:
Code:
getprop("ro.product.model") == "Lenovo K50-t5" || abort("This package is for \"Lenovo K50-t5\" devices; this is a \"" + getprop("ro.product.model") + "\".");
So now running VibeUI from my extsd card lol, I flashed it just to confirm it's possible, but I think I'll wipe it and flash it again as primary because I mostly play games on VibeUI and I don't want to run a heavy game from my extsd while the entire phone system is also running from the card. It will slow down the things.
Meanwhile I still can't make the AICP rom by sandeep a multiboot ready. Sometimes it hangs at the logo, sometimes and vibrates 5 times and reboot back to recovery. I posted at the dualboot thread and really hope that Chen will help me.
Click to expand...
Click to collapse
That's great! I'll try out the MM ROM then.
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Salman A. said:
That's great! I'll try out the MM ROM then.
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Click to expand...
Click to collapse
Wait! I forgot to mention that I also tried VibeUI_1606 from needrom and it while it had instaled fine it doesn't boot! Got stucked at the logo... I don't know for the other MM roms, you may want to try 1605 as I already tried 1606 and as you can see without success. So may be no multiboot for MM for now...if you have enouh space on internal you may try and report. So the bottom line:
VIBEUI_1604_ST Android 5.1 is working
VIBEUI_1606_DEV Android 6.0 won't boot.
Phone: Lenovo K3 Note
ROM: 04_K3_NOTE_5.1_1604_STABLE_ROW_004_CUOCO92
Kenrnel fix successful but in primary ROM While updating ram disk it gave error
log file attached
Please help
Using the latest Dualboot 2162 build with the VibeUI_3.1_1606 - can't update the ramdisk and also not indicating that the primary rom is the currently running.
I still can switch to other rom via the utilities zip so for now it's a compromise that I chose to make.
Salman A. said:
Which is your ROM??
It's because of the ro.build.product of your build.prop
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Click to expand...
Click to collapse
Now I have installed k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 as the primary ROM.
And again same error I m having. But now it is saying this device is aio otfp m. Please help. Even I m not able to update ramdisk.
911-Future_Maker said:
This is easy. I'll guess you're installing MIUI or CM right? Because these roms usually contains this limitation about "hermes" only devices. Just open the updater-script which can be found in META-INF/com/google/android path, open it as text via some root file manager and edit it removing the following lines:
Code:
getprop("ro.product.device") == "hermes" || abort("This package is for \"hermes\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Success.
Click to expand...
Click to collapse
Sir where to find this folder meta inf
Pradeepnegi said:
Sir where to find this folder meta inf
Click to expand...
Click to collapse
In the ROM zip.
Pradeepnegi said:
Now I have installed k3 note mm 6.0 ui 3.5 dev 1605 row cuoco92 as the primary ROM.
And again same error I m having. But now it is saying this device is aio otfp m. Please help. Even I m not able to update ramdisk.
Click to expand...
Click to collapse
You have to change ro.build.product to aio_otfp without _m in your build.prop. If you are still trying that zip, you will still have to edit the updater-script. My advice, don't use it. That's very old. Try the new CM 12.1 Beta 3
Sent from my Lenovo K3 Note (K50-T5) using Tapatalk
Hi there,
I flashed my nexus 10 with Lineage 16 ROM. When I try to install GApps Pico - even with everythng removed in gapps-config - I get the well know Error 70.
When I try to resize with TWRP I see Size 787MB Used: 755MB and its not getting bigger.
Can I somehow resize the system disc or is there any way to get Lineage together with GApps running on my Nexus 10 without repartioning it?
Is there a smaller lineage?
ROM: lineage-16.0-20201215-UNOFFICIAL-manta.zip
GApps: open_gapps-arm-9.0-pico-20190209.zip
Thanks for the help!
To anwser my question. Yes, if you have a Nexus 10 your /system directory is too small! You need to resize it. I used this very good guide here: https://forum.xda-developers.com/t/...s-4s-system-partition-for-more-space.3800264/
I ve stolen 250MB from /cache and then I could easily install gapps on top.