THIS ISN'T A PUBLIC ROM RELEASE. THIS IS FOR DEVELOPMENT ONLY. THE ROM DOES NOT BOOT. FOR MORE INFO READ THE ENTIRE POST
I've been working on bringing our device onto par with a build of Android 4.3. I've set up a GitHub organization just for our device and it has everything we need to build for the device. Now I've been somewhat quiet with what I've been doing lately and I really don't have time to list everything I've done. @bradthomas127 and I have been communicating back and forth about building. I'd say he's done just about as much work as I've done trying to get 4.3 building. Well now, after some tips from him, I've got it building. It's using, in my opinion, the best up-to-date trees there are for our hardware. I am opening this project up to anyone that can help get it BOOTING. I don't need testers as right now I feel like I myself am the best tester for now because getting adb working on a device that sticks at a blank scree is a pain in the a**. So PLEASE I encourage anyone that knows how to maintain a GitHub and can compile and do a little coding to try to help us. The more people we can get, the faster and better we can get 4.3 actually running on our device.
Here is the GitHub:
https://github.com/Primo-Dev
If you feel you are capable of helping us dev this please PM me and I may add you to the GitHub so you can contribute.
Here is the latest build:
http://d-h.st/JSo
Logcat can be downloaded here:
http://d-h.st/SYz
Now, some basic rules for this forum:
1. DON'T ASK FOR ETA OR UPDATES - This kind of stuff is hard and takes time
2. Don't ask to test - I'll open this up for testing if we ever get it to boot
3. To all other people who aren't devs: Don't post here as this is for development only. I've made this thread in hopes of finding more devs to try to help with this, not open this up as a public ROM.
What needs attention:
I'll post bits and pieces of logcat here that shows things that need to be worked on
Code:
I/auditd ( 99): Starting up
E/auditd ( 99): Failed on audit_set_pid with error: Protocol not supported
I/auditd ( 99): Exiting
W/dalvikvm( 161): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument
I did not even notice this till you posted the logcat, libgenlock is not even building.
Code:
E/libEGL ( 1327): load_driver(/system/lib/egl/libEGL_adreno200.so): dlopen failed: could not load library "libgenlock.so" needed by "libEGL_adreno200.so"; caused by library "libgenlock.so" not found
Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.
robaho said:
Based on the logs, you'll need a kernel that has SELinux support. That is the major failure you are having. I am not sure if there will be a way to disable it.
Click to expand...
Click to collapse
That's what I've been thinking. All the devices that have been updated to cm10.2 have SELinux. Only problem is I'm not much of a kernel dev, but I can see what I can do. Also, if you take the main hardware libs from RhythmicRom and put them in cm10.2 you can get to the bootanimation.
Sent from my HTC One V using xda app-developers app
I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-
bradthomas127 said:
I just made a build with libgenlock.so in it, have not tried it yet.
I had to cherry pick this for SELinux support: GitHub That goes in primoc_defconfig and should take care of "audit_set_pid" & "PR_SET_NO_NEW_PRIVS" Errors.
To get libgenlock.so to build i had to bring in android_hardware_qcom_display-legacy because everything else is going ION now. display-legacy is "not" to replace qcom_display though we are already calling it in BoardConfigCommon.mk with this "TARGET_QCOM_DISPLAY_VARIANT := legacy", I used Icebox's but it is the same one we have in primo-dev <= lots of build errors though.
Edit: No boot, led blinks a couple times now. If anyone knows how to pull a logcat on 4.2+ on boot and would like to give it a try, it would be much appreciated.
cm-10.2-20130822-UNOFFICIAL-primoc.zip
-
Click to expand...
Click to collapse
I'll logcat. I'll also post instructions on how I logcat on 4.2+.
Sent from my HTC One V using xda app-developers app
Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app
reV17 said:
Hey @awidawad just an FYI the Incredible S has released CM10.2 and source is on Github. I figured it might help you guys somehow.
Sent from my LG Optimus F7 using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks I'll do some research on github later. It has almost the same specs so it will be useful.
BTW: To anyone waiting for logcat instructions I'm trying to find a simplest way to do it with the little time I have between work and football, and school coming up.
Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip
bradthomas127 said:
Alright guy's i finally got it past the black screen of death but i am stuck in a bootloop, if you know how to get a logcat from a non booting ROM on 4.2+ i really need to know how or get a logcat posted on this.
cm-10.2-20130924-UNOFFICIAL-primoc.zip
Click to expand...
Click to collapse
Hey man I'll post how to when I get home
Sent from my C525c using Tapatalk 4
You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Sent from my One V using xda app-developers app
Lucky CDMA people with half working 4.3 o-o
robaho said:
You need to enable adb and disable secure. If you use the eng (engineering) build. Otherwise you would need the GUI up so you can allow access from the computer due to the new security constraints.
Click to expand...
Click to collapse
I added ro.adb.secure=0 to the default.prop a couple days ago making the ramdisk/default.prop look like this now.
Code:
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
I've also tried moving adbkey.pub to data/misc/adb/pub_keys in TWRP but it gets erased as soon as i boot.
Is the USB driver working, that is, can you.see a USB device using your system devices view - varies by OS
Sent from my One V using xda app-developers app
This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.
awidawad said:
This is how I logcat on 4.3:
First off, you're going to need a WORKING android device running 4.2+
Now:
1. Plug the device into your PC
2. Go to Settings>Development and enable adb
3. When the dialogue comes up asking to trust the computer tap yes. If it doesn't appear run "adb devices" on your PC.
4. Get a root file explorer
5. In the explorer, go to \data\misc\adb and copy adb_keys to your PC. (Copy adb_keys to your Sdcard, mount phone storage, then copy to PC.)
6. Download THIS and extract all files on your PC
7. Open up the extracted directory.
8. Place adb_keys in \data\misc\adb and then run the "Run_to_build_zip.bat" file.
9. Download THIS and flash in recovery on the device you're going to logcat.
10. Copy the zip that was just created on your PC to your sdcard and flash in recovery. (Zip will be named "adb_hack_step2_**.**.**@**_**.zip" )
Reboot, adb should now be enabled and work on the PC you used.
Click to expand...
Click to collapse
Not working for me, messed with it a couple times.
bradthomas127 said:
Not working for me, messed with it a couple times.
Click to expand...
Click to collapse
Strange... I've used that method multiple times in ubuntu.
Sent from my C525c using Tapatalk 4
awidawad said:
Strange... I've used that method multiple times in ubuntu.
Click to expand...
Click to collapse
Getting boot now, just boot loops every min.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:highfive:
bradthomas127 said:
Getting boot now, just boot loops every min.
:highfive:
Click to expand...
Click to collapse
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app
robaho said:
You might need Simon's battery fix in the kernel???
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Do you mean this one? https://github.com/bradthomas127/an...mmit/9af6efa20ece323155a853ff508563a87670e2f0
Rukin added it 4 months ago.
You did just open my eyes though, i thought i commited the SELinux stuff but just noticed i didn't on this kernel, maybe why i am having reboots and SD card is not mounting (reason for no screen shot). Thanks :good:
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P930 and SU640 now officially supported by TWRP team. I will no longer be building recoveries for these devices. However I will keep this thread updated to the best of my ability.
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
If you want more information about twrp please go to this page.
Phone look:
CHANGE LOG: http://www.teamw.in/project/twrp2
DOWNLOAD:
P930: http://www.teamw.in/project/twrp2/162
SU640: http://teamw.in/project/twrp2/167
Installation Methods:
1 - GooManager (Android App)
Code:
Download the GooManager app from either location:
[URL="https://market.android.com/details?id=com.s0up.goomanager"]Market Link[/URL]
[URL="http://goo.im/devs/s0updev/gooinsideme"]Direct Download[/URL]
Install the app and open it.
Tap menu then hit Install OpenRecoveryScript.
Tap Yes.
Verify that the filename displays your device's code name and hit Yes.
The file will download and your device will reboot and install the recovery automatically.
2 - ADB
Code:
adb push openrecovery-twrp-*.img /sdcard/
adb shell
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
3 - Terminal Emulator
Copy openrecovery-twrp-*.img to root of SD card then in your terminal emulator type the following:
Code:
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
BUGS:
If you have found a bug, please consider posting it here,possibly with a recovery.log. It's very hard to keep up with multiple threads for multiple devices. Please search the issues list first. Your issue may have already been reported.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
DISCLAIMER:
I take no responsibility for bricked devices, nuclear wars or such things.
CREDITS:
TeamWin for making the recovery.
CyanogenMOD team for the device tree.
Goo.im for file hosting.
Thanks to Dees_Troy and TweakerL from twrp IRC for their help and guidance.
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
maybe. like p930's cwm recovery?
范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.
OK I WILL TEST FLASH IT TOMORROW IN MY SU640.....THX FOR UR WORK....HOPE MORE WORK FOR P930.....Sorry for my bad English....谢谢。
nexwave-mat said:
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.
Click to expand...
Click to collapse
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.
drumist said:
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.
Click to expand...
Click to collapse
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
Ok,i sent these in your mail:[email protected]!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...
范凯爱西西 said:
Ok,i sent these in your mail:........THX!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...
Click to expand...
Click to collapse
I never got the email. Can you please edit your post to remove my email address? I don't want to spam bots to find me! Thanks.
nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-su640.img
(It's listed under LG Optimus LTE on their site.)
Delete post
slg1119 said:
I think
TWRP for P93X have bug
it have...
Unmount/mount Bug!
Thx to your job~
Sent from my LG-SU640 using XDA
Click to expand...
Click to collapse
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.
nexwave-mat said:
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.
Click to expand...
Click to collapse
I don't think it is fixed.
I get a bunch of lines in the log saying:
E:Unable to mount /sdcard (Invalid argument)
Click to expand...
Click to collapse
I'm on Paranoid Android/CM10 Hybrid ROM
mattman86 said:
I don't think it is fixed.
I get a bunch of lines in the log saying:
I'm on Paranoid Android/CM10 Hybrid ROM
Click to expand...
Click to collapse
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first
nexwave-mat said:
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first
Click to expand...
Click to collapse
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.
mattman86 said:
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.
Click to expand...
Click to collapse
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,
nexwave-mat said:
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,
Click to expand...
Click to collapse
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
-- Could not mount: /sdcard.
-- Aborting.
Click to expand...
Click to collapse
mattman86 said:
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
Click to expand...
Click to collapse
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks
nexwave-mat said:
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
http://pastebin.com/LdGuWbUM
mattman86 said:
http://pastebin.com/LdGuWbUM
Click to expand...
Click to collapse
Very particular, could you please test with another sdcard or reformat the one you have on a PC and try again?
Thanks
Sent from my LG-P930 using xda app-developers app
Hey Fellow P930 owners,
Here are the files needed to get Ubuntu Touch to boot on our phones. The is a pre-alpha build and cannot be used for a daily ROM. I nor any of the involved sources take responsibility for problems, bricked devices or your cat's head exploding. If you do not know what to do with the following files do not go any further.
Phone look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
More detailed instruction will come when I have more time.
Here are the files:
Recovery: http://goo.im/devs/nexwave/p930/ubuntu-touch/cm-10.1-ubuntu-touch-20130225-UNOFFICIAL-p930.zip
CM part: http://goo.im/devs/nexwave/p930/ubuntu-touch/cwm-ubuntu-touch-20130225-UNOFFICIAL-p930.img
Ubuntu Touch part: http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip (Updated daily)
Install Instructions:
1. Have or get root on your phone.
2. Have or install a custom recovery. (TWRP, CWM and Ubuntu CWM all work)
3. Reboot to recovery.
4. Make a backup of your current ROM. (you will want to go back as not much works in the Ubuntu Touch preview at the moment)
5. Do all wipes. (cache, dalvik cache, data and system)
6. Flash CM part.
7. Flash Ubuntu Touch part.
8. Reboot and Enjoy! (It will take a minute or two before the ubuntu screen loads, be patient)
Working:
- WiFi
- Touch
- Display
- Power Button
Not working:
- Mobile Data
- Calling
- Bluetooth
- SDCard access
- Sound
- All hardware and capacitive buttons (except power button)
Project on Github:
https://github.com/nexwave-mat/android_device_lge_p930/branches/cm-10.1-ubuntu-touch
https://github.com/nexwave-mat/lge-kernel-iproj/tree/cm-10.1-ubuntu-touch
Later,
Thank you to:
goo.im - For file Hosting.
Ubuntu Touch - For the project.
The guys at work and Ubuntu Touch irc - For their helpful insight.
reserved
First off, great job man :good:
But i was wondering how did you get it to boot, in my case, i was able to compile the ROM without errors, but when flashing the .zip, i would get past the two LG Logos and it would just keep bootlooping afterwards. I see you posted 3 files in your initial post, is there a special way to flash it, i guess i ll wait for the future instructions ... ... but i would still like to know if i was even close of having a working compiled ROM, still new to this kind of stuff hehe
Thanks
Nice! Ya beat me to it. Good on ya!
Anyway, I read in the other thread that quite a few things don't really work right now. Things like calls. Do you have a list of anything not working?
I wondered the same initially then I realized the only thing you missed was flashing the zip image from (I purposely split the http so you could see what file you are fetching, there are a lot of builds there ) http://
cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
After flashing both zips it booted up for me... I wonder how well the rom would work with other kernel configurations.. You dont need the recovery.img
But for some reason my own build failed with the following in the logcat
Code:
E/linker ( 841): ics/linker.c:1072| ERROR: Library '/system/lib/libubuntu_application_api.so' not found
E/linker ( 878): ics/linker.c:1072| ERROR: Library '/system/lib/libubuntu_application_api.so' not found
E/linker ( 929): ics/linker.c:1072| ERROR: Library '/system/lib/libubuntu_application_api.so' not found
E/linker ( 937): ics/linker.c:1072| ERROR: Library '/system/lib/libubuntu_application_api.so' not found
E/linker ( 973): ics/linker.c:1072| ERROR: Library '/system/lib/libubuntu_application_api.so' not found
Nz
P.s.
After install there are a few features missing like
Unable to use the Phone,
browser,
texting..
In all it is pretty much just a small taste of what it could be - which does look to have potential - but in general a waste of time using it.
Nz
Re: [ROM][DEV]Ubuntu Touch Preview [LG-P930][2013-02-27]
I'll share my github forks as soon as they are ready. That way you guys can see changes and send commits to make things better. We can work on this together as it evolves.
Sent from my LG-P930 using xda app-developers app
Do Android apps work with this? Or do we have to get apps from Ubuntu?
Re: [ROM][DEV]Ubuntu Touch Preview [LG-P930][2013-02-27]
Scotsman828 said:
Do Android apps work with this? Or do we have to get apps from Ubuntu?
Click to expand...
Click to collapse
No, android apps do not work. You need to use Ubuntu apps.
Sent from my LG-P930 using xda app-developers app
Delete post
nexwave-mat said:
Hey Fellow P930 owners,
Here are the files needed to get Ubuntu Touch to boot on our phones. The is a pre-alpha build and cannot be used for a daily ROM. I nor any of the involved sources take responsibility for problems, bricked devices or your cat's head exploding. If you do not know what to do with the following files do not go any further.
More detailed instruction will come when I have more time.
Here are the files:
Recovery: http://goo.im/devs/nexwave/p930/ubuntu-touch/cm-10.1-ubuntu-touch-20130225-UNOFFICIAL-p930.zip
CM part: http://goo.im/devs/nexwave/p930/ubuntu-touch/cwm-ubuntu-touch-20130225-UNOFFICIAL-p930.img
Ubuntu Touch part: http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
Later,
Thank you to:
goo.im - For file Hosting.
Ubuntu Touch - For the project.
The guys at work and Ubuntu Touch irc - For their helpful insight.
Click to expand...
Click to collapse
Great job!!!
I have tested it ,It can work ,but no wifi ,phone,mms,music...and so on.
but ,your work should be thanked. Thanks a lot.
[/ATTACH][/ATTACH][/ATTACH]
I was building ubuntu touch on LG LTE ,but recently busying with Python.
p93x has little different with su640.
Could you build that at the same time.
Thanks for your work!!!
Looking forward to your good news!!!
So my second compiled build actually worked ! All i needed was the phablet .zip file ! damn it ! :silly::crying:
Anyways thanks for clearing that out for me :good:, im glad i got it to work, i ll be able to help you out on this build if needed
Alright for those wondering how to properly install this ROM (keep in mind this is a preview, nothing actually works, its only for show):
-Download those two files :
http://goo.im/devs/nexwave/p930/ubuntu-touch/cm-10.1-ubuntu-touch-20130225-UNOFFICIAL-p930.zip
http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
-Reboot in recovery
-Make a backup of your current ROM
-FULL WIPE: Factory reset(wipe data), wipe cache, wipe dalvik cache, wipe system
-Install cm-10.1-ubuntu-touch-20130225-UNOFFICIAL-p930.zip
-Install daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
-Reboot & enjoy the preview
I got mine to build last night and installed it.
Nothing happens... It boots up and says that there are "14 tweets received"... I even downloaded the links in the last post and installed them with the same result.
Is that all it does right now? If so, I'm kind of angry that I just wasted my time doing this.
mattman86 said:
I got mine to build last night and installed it.
Nothing happens... It boots up and says that there are "14 tweets received"... I even downloaded the links in the last post and installed them with the same result.
Is that all it does right now? If so, I'm kind of angry that I just wasted my time doing this.
Click to expand...
Click to collapse
Well you can do swipes to open menus and such. Also web browsing works on WiFi but ya... that's about it. Really not usable other than to dev on. Which is what it's intended for.
nexwave-mat said:
Well you can do swipes to open menus and such. Also web browsing works on WiFi but ya... that's about it. Really not usable other than to dev on. Which is what it's intended for.
Click to expand...
Click to collapse
I swiped the screen all over the place and nothing happened. except for the clock minutes changing.
Try drag from right edge out
Sent from my LG-P930 using XDA Premium HD app
Delete post
Wow this is awesome! I love the look and everything. Can't wait till it has full functionality.
Sent from my LG-P930 using xda app-developers app
I just wanted to thank you for this! Been itching to try ubuntu touch on my P930. Excellent work!
Cheers,
Hey Guys,
Just wanted to let you know that I'm going to be attending a port clinic with the ubuntu touch team tomorrow on IRC in order to learn how to port the new flipped image. I wouldn't want us to miss out on the awesomeness that is going to be Ubuntu Touch .
Feel free to join us/me, details quoted below.
We noticed that some of the port images linked from [3] haven't been
updated in a while. If you should need help to update to the newest
version of Ubuntu Touch, we are running a Ubuntu Touch Porting Clinic on
Thursday, 1st August in #ubuntu-touch on irc.freenode.net ([4] has a web
frontend, if you don't have an IRC client). Simply ask your question on
IRC and we'll have some folks around to help you out.
[3] https://wiki.ubuntu.com/Touch/Devices
[4] webchat.freenode.net/?channels=ubuntu-touch
Click to expand...
Click to collapse
nexwave-mat said:
Hey Guys,
Just wanted to let you know that I'm going to be attending a port clinic with the ubuntu touch team tomorrow on IRC in order to learn how to port the new flipped image. I wouldn't want us to miss out on the awesomeness that is going to be Ubuntu Touch .
Feel free to join us/me, details quoted below.
Click to expand...
Click to collapse
Awesome! Learn anything good?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For Latest Download Link Click Here
full SELinux support
Features:
Tested and Working
Backup / Restore
ROM Flashing (of course :good: )
Mounting partitions (and SD via USB to PC)
Screen Timeout - Lock / Unlock (double tap to wake or use power - change timeout in settings)
adb sideload
Clock
Battery
Log
File Manager
Advanced Reboot Options
when powered off and you plug in phone it auto boots to recovery, maybe nice for someone with a broken power button? (so not really a feature...)
Haven't Tested
Fix Permissions
[*]Terminal
[*]Themes
[*]Partition SD Card
let me know if you can confirm these working, my vision is out on loan to a friend an can not test - thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
*broken
SD-ext wipe/backup/restore - still working on this one, hopefully wont take too much longer to fix
anyone who wants to test will be rewarded with praise from me! should be safe, has been for me, but I guess I should say the whole I'm not responsible for xyz... but you're on xda, you know this
Just Some Random Screen Shots Of TWRP, Not From This Phone
*oh and I have some new clockwork recoveries if you all want these too, they appear fine with the minimal test I've done, if you all want I can upload these too - built from newest source something like 6.0.4.6? cant recall the versions and am lazy now, but built for kitkat roms
For sure gonna try this out if I have some free time tomorrow. It's getting late or else I would already be testing it out now
demkantor as you advised me first i just booted the recovery .. works well
flashed recovery works as expected
i dont have sdcard so you know the broken section is not for me
Working ADB sideload confirmed
Mind sharing how did you fix that?
My idea is that the problem is in fstab.recovery, but I'm not entirely sure on that. Could you please share "device-related" changes for TWRP?
Sure thing, I hope have some time in front of a PC this next week, I'll put up a new build with sd-ext fix and post a github link and clean up the op. Sorry just haven't had like ant quality PC time in the past few months
Sent from my Nexus 7 using XDA Premium 4 mobile app
Alright, finally got around to flashing this. All the basic functionality I used CWM for, works perfect in TWRP. Pretty awesome
Man, this is awesome! I was using some old TWRP 2.2.0 version i found on some weird chinese site after failing to build it myself. Thanks fr thins man! :laugh:
awesome job demkantor
and i can gladly take all the credits for this tool :d LoL
Why switch?
Hey @demkantor,
great work again, I guess, thanks. We vision users are lucky to have folks like you still working on our device.
One overarching question--why switch recoveries, and if I do, to this TWRP or your (or Nevergone's?) CWM? I have used 4EXT (I think at your suggestion, in fact) ever since I rooted my phone in August, 2012, and no problems. I have kept up with all the latest ROMs in the Flinny line (and a few others) including 11.0, though I have now stepped back to his last 10.1 build while KitKat needs fixing. My needs are pretty basic, I suppose...I just flash the occasional new ROM, make backups, occasionally restore them (like in going from 11.0 back to 10.1.) I rarely touch adb...it just hasn't been necessary. I am perfectly happy with my phone, and marvel at its longevity!
So, stick with the latest 4EXT, or jump to something newer?
Thanks,
p-d
ps still at the U? Go to Al's for me sometime, I miss breakfast there.
Thanks!
In truth I still prefer 4ext myself, its my favorite recovery but development on it has slowed over the past year. The only reason I bothered to make this was for @AYEHAN who has a broken SD tray and needed to be able to sideload a ROM, currently 4ext is lacking this feature. So if your current recovery is still working for you then I would suggest to stick with it, TWRP is nice and I use it on most my devices (as 4ext isn't available) but if it ain't broke don't fix it!
Yeah last few days of brake before the new semester begins, and for sure will go to Al's, best whole in the wall there is!
Sent from my Nexus 7 using XDA Premium 4 mobile app
One major bug I came across, is it will no longer flash roms. Like, regardless of what the rom is it just won't flash it, it spits out
assert failed: get prop("ro.product.device") == "
E:Error executing updater binary in zip '/sdcard ,
and I know these roms all work since it was flashing them beforehand. Just thought I'd let you know
*Edit*
So any rom other than G2Slim won't flash for me. CM10.1, Flinny's CM11, etc. It's so odd
*Edit 2*
I installed CWM v5 again just to make sure it wasn't a problem with the roms themselves or my sd card, and things install fine, so it must be a random bug with twrp, hopefully a very rare one at that
I just tried and found a similar result, without looking into it much I see there are a couple update-binaries used with various ROMs and this build works for one and not the other, at least that's what I see so far as I'm coaching my friend on how to do this as the phone is with him on the other side of town right now.
I'll look into a fix for this as it would be nice to be able to flash all Roms not just some, thanks for the bug report!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Fix permissions and terminal work fine, I'll try a theme if I can work out how to do it but I don't have a spare SD card I can test partitioning on. All in all great work
Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Thanks for running those tests, with school and not having my g2 in front of me I haven't had a chance to pick up this project, but I should have my phone back shortly. One of the things I was planning to do (after all functions are 100%) was make a few themes, which is quite easy if your interested
http://www.teamw.in/twrp2-theme-guide
It surprising how customizable and fun a recovery can be so if you get around to it I will for sure link any you make and hopefully will have a few of my on in due time
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just tried a theme, works fine. I would make some but I have no working PC right now. Might be able to unpack and edit an existing one on device though
Needed to get a recovery compatible with SELinux support in order to install latest CM11 Alpha 3 (Flinny's).
Works fine. None of the errors above when installing CM11 and gapps.
Great work!
tried this alot of times , plus flash the recovery 3 times but could not sideload an image :/
e:/ sdcard not found something error
sorry for that, I'm sure it's a stupid question, but just to be sure...
there is no different way except flashing this .img using a pc...right? I tried using TWRP app last night but it wants to know which device is and it's not listed
thank you a lot
Alex
If you want I'll make you a flashable.zip or you can use a terminal emulator on your phone, just download to SD card and name it recovery.img
Then open up emulator
su
flash_image recovery /sdcard/recovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
MODIFY A 4.4.x BASED ROM'S UPDATER-SCRIPT TO FLASH WITH TWRP 2.5.0.0!
WARNING
This is a disclaimer: While this has been tested I am not responsible for ANY damage done to your device. I take no responsibility for bootloops, soft bricks, hard bricks, living brick monsters, your phone proving an omnipotent being fallible(thus negating all existence), your great aunt smoking bath salts, flying monkeys, hot pockets, obamacare, dingleberries, carnivorous dingleberries or Sundays. Use at your own risk!!
Secondary disclaimer: If you have carnivorous dingleberries then you have bigger problems to worry about - but for any phone related questions feel free to message me on here either privately or in the thread.
In honor of my 300th post here on xda I thought I should do my first guide. I decided to make this guide because some people have had issues with TWRP 2.6.x which is the version you need to flash kit kat roms. However TWRP 2.5.0.0 has been beyond stable for me and everyone I know who has used it on our wonderful ls970. So how do you flash 4.4 based roms from TWRP 2.5.0.0?! Edit the updater-script, ofcourse!!!!
Now keep in mind, the screenshots I supply will be on Linux because it is what I use - the steps should be the same for Windows, however the programs used will probably be different(Archive Manager vs 7zip/WinRar for instance). If anyone wants to do this on Windows and take screenshots I will gladly post them or give OP privileges so that you can add them yourself.
Are there any downsides to installing roms this way?
Yes - it will essentially break OTA updates for the roms. 4.4 roms built from source will always have an updater-script meant for the newer recovery versions and will not flash in 2.5.0.0. So if you want to dirty flash an update to the rom you are using, you will have to modify that updater-script as well.
Well, let's get down to business!
Things you will need:
A flashable zip file for your rom of choice(I use Vanir for this guide)
An archive manager(7zip/Winrar for Windows)
A text editor(I use gedit but Windows users will want to use Notepad++)
A working brain
Step 1: Open the flashable zip file with an archive manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2: Navigate to the updater-script found in META-INF/com/google/android/
Step 3: Open the updater-script from within the archive manager. Keep the archive manager open during this process. I'm using Linux Mint 15 so it opens in gedit. Once open, scroll down until you see a bunch of lines that say 'set_metadata' and 'set_metadata_recursive'. These are the lines we need to edit.
Step 4: Now everywhere you see 'metadata' in these lines, you want to replace 'metadata' with 'perm' like in the images below.
Step 5: After replacing metadata with perm, we need to re-organize things a bit to look more like a 4.3 updater-script. After the parentheses you will see directories/files in quotation marks like in the picture below.
We need to move all of these to the end of the parentheses like so.
Step 6: The next thing we need to do is delete everything else in the parentheses EXCEPT the numbers. The numbers and quotations we just moved will be the only things left in parentheses when we are done. Also keep in mind that '0x0' will also be removed.
So - everything highlighted below, needs to go!
When you are done, it will look like this:
And when you are done with ALL of it, here is what it will look like!
Step 7: Remove asserts. This isn't always needed but it also won't hurt. The asserts placed in flashable zips are to protect you from installing a rom that isn't compatible with your device. The problem we lgog users frequently have is that our phone is called many things(ls970, geehrc4g, geespr, etc). If you've ever gotten a "Flash failed this isn't a geespr" error in TWRP, it's because that particular version of TWRP doesn't recognize your device as a geespr(even though it is). So as long as you know the rom was built for your device, it is safe to delete these lines. They are found at the very top of the updater-script like shown below.
Step 8: Save and update! Once you are done editing, simply hit save in the text editor and your archive manager should give you a warning similar to this one below.
Hit the update button and the updater-script will save inside the flashable zip!
And that's it! Your 4.4 based rom will now flash on TWRP 2.5.0.0!!
Just be careful that you edit it exactly, pay attention to the punctuation. This is not difficult but can be time consuming. Using your text editor's "Replace" function properly will help speed up the process!
So why go through all of this?
Certain users here on the lgog forums have experienced a problem with TWRP 2.6.x that essentially bricks the device. Randomly and mysteriously, the phone won't boot into the system. When trying to boot into TWRP, it will ask for a password - even though the user never supplied one in the first place. If you cancel the password, TWRP loses all functionality.
Users in other threads(specifically the nexus4 and nexus5 users) have experienced the same problem but not to the extent our lgog users have. In most cases it is because the data partition became corrupt/encrypted. The solution is to format your data partition(So best case scenario, you lose EVERYTHING). Nexus users seem to still be able to do this after cancelling the password - some lgog users haven't been as fortunate. When they cancel the password, nothing mounts, so nothing works. Even using LGNPST to revert back to stock gives an error so the phone is essentially a paperweight.
What is the cause of this?
It still isn't certain however it may be a bad emmc chip. Can't an emmc chip go bad using TWRP 2.5.0.0? Ofcourse, so this may all be superstition. It may just be a coincidence that a person's emmc chip fried while using the updated versions of TWRP. But until someone has this issue on TWRP 2.5.0.0(None have been reported as far as I know, if it happens to you, please prove me wrong), I'm going to err on the side of caution and stick with what I know works.
For most users it will just be easier to flash a different recovery like Clockworkmod but I personally wanted to stick with one recovery. Using this method, TWRP 2.5.0.0 can flash everything from stock to 4.4.x! You can look here in the lgog forums for working recoveries and their uses/limitations. But at the very least I hope this guide helped you to understand updater-scripts a bit better and the role they play in flashing roms.
QUESTIONS?
Feel free to ask me any questions you may have. If it doesn't flash, get a recovery log(from TWRP go to advanced->copy log to sd, then boot back into your system and it will be on your internal memory as recovery.log) and send it to me. Or open the recovery log yourself and look for E: (For error) around where the flash failed. Usually you will see a syntax error and it will tell you what line it was on - that means the edit wasn't done properly but you will atleast know where it went wrong.
Thanks
@xboxfanj - for showing me how to do this in the first place
@engine95 - for all of his guides here in the threads
For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man(out of daily thanks again) - I thought that's what Windows users should use but wasn't 100% sure.
Awesome work brother!
Sent from my Optimus G using xda app-developers app
PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ditto on that!
PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Code-Craft said:
Ditto on that!
Click to expand...
Click to collapse
Thanks guys! My laptop is so old I cant even attempt to build anything worthwhile(damn you 32 bit!) so I can only modify stuff but will pass on what I learn to you all. As soon as I get a new computer I will be learning how to build so stay tuned.
Good job man!! Hell yeah!
Sent from my LG-LS970 using XDA Premium 4 mobile app
SailfishOS for Galaxy Nexus (GSM)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a community port of Jolla's SailfishOS for the Galaxy Nexus.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different operating system.
It only uses parts of Android for hardware enablement (drivers).
Special Thanks to vakkov, sledges, mugna91, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Galaxy Nexus port is considered to be of alpha quality.
Though depending on your usage it might be stabile enough for daily use.
Bug reports:
Please issue bugreports at the Nemo Project Bugzilla.
Known issues:
Due to an issue with ofono, reading from SIM does not work. You'll need to remove your PIN lock before flashing.
Setting an ambiance (color theme & wallpaper) causes hangs. Either needs the battery to be pulled, or you can SSH into the device and run:
systemctl --user restart lipstick
The startup wizard is getting skipped for now, due to the issue above.
The Jolla Store currently does not work. As an alternative you can try Warehouse for OpenRepos.
The camera does not work.
Due to redistribution issues the codec for MP3 can't shipped. To enable the codec run the following command:
devel-su zypper in gst-av
Instructions & Download:
Make a backup
Factory Reset (Wipe /data & /cache)
Wipe /system
Install CyanogenMod 10.1.3
Install SailfishOS on top:
Mirrors:
beidl.eu
Reboot
Old versions:
Alpha1:
XDA
beidl.eu
XDA:DevDB Information
SailfishOS for Galaxy Nexus, ROM for the Samsung Galaxy Nexus
Contributors
beidl, vakkov, sledges
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-08-03
Last Updated 2014-08-24
Reserved
Changes:
August 24th, 2014:
Notification LED working
Bluetooth activation/deactivation fixed
Changes for Video playback (work in progress)
August 3rd, 2014:
Initial release
Nice & interesting..
Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).
Justice™ said:
Awesome! I'd love to check this out, as I've been following the progress in the other thread! (And because I'd actually like to check sailfish out, I never experienced Maemo and Meego so this will be an entirely new experience). However the XDA download link is unbelievably slow (Topping out at like 30 KB/s maximum on a decent internet connection). Does anyone have a download link from a service such as Google Drive/Mega/AFH? I'd be extremely thankful if someone did have a mirror, and would return the favour by uploading it. (If the OP allows for mirrors).
Click to expand...
Click to collapse
Mirror to my private server added.
Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.
freshgiammi said:
Ubuntu 14.04 recognizes the device as a ethernet cable connection..
I've played around the USB settings and all the others are charging-only.
Click to expand...
Click to collapse
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.
beidl said:
Alright, definitely something nobody has tested, for whatever reason. As you are using Ubuntu, a quick sshfs mount to [email protected] might do it for now.
Click to expand...
Click to collapse
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.
i couldnt select allow untrusted software to install warehouse. it does nothing when i select accept to allow it o settings.
freshgiammi said:
Also, powering down the device while connected via USB to the PC, reboots it instead of shutting it down.
Can't try sshfs since i've just restored my Android backup bc Gnex is my daily driver, I'm sorry.
Click to expand...
Click to collapse
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.
beidl said:
As mentioned, the "Alpha" tag is pretty much justified. Thank you for testing.
Also, the "untrusted software" switch is pretty useless and installing 3rd party applications
is supposed to be done through the command line for now.
Click to expand...
Click to collapse
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
edit:
ah yeah it does ext4..
z3n0x1 said:
so i have to install cm10.1.3 maguro and install the sailfish os alpha..?
cause it been 15minute it's stuck on google boot screen.
EDIT:
does it have to be EXT4..?
Click to expand...
Click to collapse
Yes, I would assume it needs to be EXT4
Justice™ said:
Yes, I would assume it needs to be EXT4
Click to expand...
Click to collapse
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..
z3n0x1 said:
yup correct just installed it now..
and now need to install the alternative jolla store.. the warehouse.. but i don't know how..
allow untrusted software are not working..
what i have to go.. even get the warehouse.rpm.. it still can't be installed..
Click to expand...
Click to collapse
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.
Justice™ said:
You need to install it through the terminal, I'm not sure what the command is to install rpms of the top of my head, so googling it would probably get you an answer.
Click to expand...
Click to collapse
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
EDIT:
open terminal
type cd ~/Downloads
type pkcon install-local ./downloaded-package.rpm
got "fatal error:nothing provides libsailfishapp.so.1 needed by harbour-warehouse-0.3-20.armv7h"
need the libsailfishapp.so.1.. lookfor it now..
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm
z3n0x1 said:
well i got this...
after download the warehouse.rpm
goto setting > develoment > set password > save
type into terminal: devel-su -c harbour-warehouse
and type the password.. but nothing comes up
do i have to restart after save password or maybe restart after type pass word?? :silly:
the alpha looks smooth untill now been few hours test.. message working.. wifi.. haven't check the rest..
im still curious about how to install .rpm
Click to expand...
Click to collapse
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
From terminal, root
Install a package
rpm –ivh packagename
upgrade a package
rpm –Uvh packagename
you can find out what the switches mean by doing a rpm --help from the command line.
Click to expand...
Click to collapse
I think -ivh would indicate installation and -uvh being the uninstall process
Justice™ said:
I assume you'd need to elevate to root using devel-su, and then use one of the commands I've quoted below to install the warehouse rpm.
I think -ivh would indicate installation and -uvh being the uninstall process
Click to expand...
Click to collapse
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
EDIT:
error: failed dependdencies:
libsailfishapp.so.1 is needed by harbour-warehouse-0.3-20.armv7h
so i perssume it the libsailfishapp.so.1 the problem..
http://forum.xda-developers.com/showpost.php?p=53171554&postcount=90
he's said that just copy it from /usr/lib/ . but how come even we don't have filemanager..
i'll try the pkcon install jolla-fileman (the native file manager from jolla) apprently the rpm are not there..
just maybe.. even we have the native file manager.. the missing libsailfishapp.so.1 still occur..
z3n0x1 said:
yes it's seems so..
i'll try you code now..
or maybe the -uvh are the upgrade..?? since it's upgrade on the code you are quote..
Click to expand...
Click to collapse
I must've misread it as uninstall then, yeah.
Justice™ said:
I must've misread it as uninstall then, yeah.
Click to expand...
Click to collapse
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?
z3n0x1 said:
oh my im deprresed Lol
oh my now what should i do..
is there anyway that we can reach the root via computer..?
Click to expand...
Click to collapse
You could try and SSH in and run the commands, which may be easier, I'm trying to get the warehouse installed now