Hello Everyone,
I recently bought this device G7 play with on-going offer with MetroPCS. Since last one week, I've been getting my hands dirty on successfully building and booting the kernel from the source code provided by moto here https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPYS29.105-134-7
I would like to share with you all my progress currently.
Working:
Boots
Touch works
Not Working:
Camera
Baseband (radio)
A lot more
Screenshot :
{
"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"
}
I will update my progress here and release it once I manage get around few major issues and also I'm working on building TWRP for our device from source.
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Hello, is this 32bit or 64bit?
brickhayabusa said:
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Click to expand...
Click to collapse
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
Electimon said:
Hello, is this 32bit or 64bit?
Click to expand...
Click to collapse
It is a 64 bit build
kD said:
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
It is a 64 bit build
Click to expand...
Click to collapse
Do you have telegram?
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Spaceminer said:
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Click to expand...
Click to collapse
Sent a PM to you.
Thanks for your work!!!
A custom kernel for this device will be amazing! Go on!!
Using this kernel im going to build halium-boot eta s0n
This is amazing!! Please continue, you are a hope for us and share your progress with us
nothing new?
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Spaceminer said:
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Click to expand...
Click to collapse
Seems like great news! When we can get a 64 bit OS running ill make a zip to convert from this 64 bit rom to 64 bit halium 9!
Hey man! Good work! Any news in your 64bit kernel?
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", @ARGV) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Spaceminer said:
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Click to expand...
Click to collapse
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
ErikAlvarez00 said:
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
Click to expand...
Click to collapse
That explains the problem. I removed one of those, because it caused an error, but it really needed to be moved to the end... Thank you so much!
What's wrong with this command?
I need help with the syntax on this. There's an error somewhere and I can't find it, so I can't finish building a 64bit kernel. I've tried moving the ' symbol to a few places and nothing works. I'm very lost on this part.
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\"' kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > $kernel_out_dir/mapphone_defconfig || ( rm -f $kernel_out_dir/mapphone_defconfig && false )
Edit: I think that I found the solution. It should actually be this according to build instructions for other Motorola devices.
/bin/bash -c "( perl -le 'print "# This file was automatically generated from:\n#\t" . join("\n#\t", @argv) . "\n"'
Related
I was able to partialy boot Linux kernel on Samsung i780. It wouldn't be possible without help from tmzt. You can find him, and other helpful people on #htc-linux IRC channel on freenode network.
Here are files (kernel, kernel config, default.txt) http://netbsd.pl/~lama/i780/
{
"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"
}
How have i to use these files (.config,linux+default ecc)?
And what means "partially boot"?The i780 doesn t start?
Partially boot means the video is corrupt and the kernel panics because it can't find the root filesystem, the sd card is not implemented yet and ll4m4 did not use an initramfs.
This kernel is not specific to i780, it's just the first step in linux/android on i780.
Nice!
Now that's cool!! I'll be watching...
isn't the i780 hardware similar to the omnia?
It s a start point, but now we only know the i780 can run haret, we don t have a specific zImage or a specific default.txt...
I think we can modify the "omnia's linux" to get it working on i780.I tried to run those files without any modification but the phone vibrates a lot during boot and there is also a screen issue.
ilMessia said:
I think we can modify the "omnia's linux" to get it working on i780.I tried to run those files without any modification but the phone vibrates a lot during boot and there is also a screen issue.
Click to expand...
Click to collapse
Looking forward to test this !!!
Keep the good work
I've manage to make some "progress"...
rev 1
Build kernel based on linux-2.6.29-rc4 sources with arm-2008q3 cross-compiler (config attached )
+fixed res problems, keys reacting (not mapped right), kernel is chill-out
-no connection with device
Cross-compiled busybox-1.13.2 and made initfs (I'm not sure is it working)
It's not big step but step at all
UPDATE 14.02
rev 2
+fixed key mapping, most letters are correct
+kernel is more stable, compressed and it don't spill errors,
+you can actually do something besides writing, there is busybox but don't have all symlinks. all commands are available by "busybox command" // usage example "busybox touch new_file"
- initrd still sucks a lot, it was created in 5min for sake of kernel. but this is just first day of develop...
Besides this I'm planning to move news and files to MelPlace2 website...
UPDATE 24.02
rev 3
+further key fixes
Vol up/down = up/down arrows
Green/red keys = page up/down (usefull to scroll console SHIFT+PGUP)
Rest of keys = explore
+framebuffer corrected - no cut letters near margins
+initrd with little kick, it show that working on this device can be enjoyable
+many devices appear in dmesg...
but
-initrd is still not enough - working on MMC and Ethernet
-randomly kernel boots with white area on right part of screen - reset your device as fast as possible or it will leave strange mark on screen for few minutes, even in WM (!!)
Please test latest revision and send some constructive feedback
I've created kernel git repository on GitHub HERE.
So if you want to help check it out (do not trash this thread with messages about git- it's separately thing).
I've just started (1 patch) so everybody should know what is going on.
Updated download link: i780Linux.zip (2,4 MB)
melgurth said:
I've manage to make some "progress"...
Build kernel based on linux-2.6.29-rc4 sources with arm-2008q3 cross-compiler (config attached )
+fixed res problems, keys reacting (not mapped right), kernel is chill-out
-no connection with device
Cross-compiled busybox-1.13.2 and made initfs (I'm not sure is it working)
It's not big step but step at all
Download link: i780Linux.zip (2,3 MB)
Click to expand...
Click to collapse
Great work man!!!
I just baught my i780 couple of weeks ago. My original plan was, to buy an Android phone. But there was just the HTC Dream available and its price was doubled - compared to the i780.
Now I am glad to hear, that you are working on getting Linux running. I am a Linuxer since 1997. I will try the kernel.
If I can help somehow, let me know.
Cheers
Holger
linuxholgi said:
....
If I can help somehow, let me know.
Cheers
Holger
Click to expand...
Click to collapse
...help is always needed.
Right now I'm in need of good initrd. If You willing to help You can try to make something.
I'll brake work on this weekend due to my birthday (social life) but I'm gonna resume kernel dev in monday. Could be useful to have good initrd with busybox and rootfs.
Ok, is there a ready-to-use toolchain I can use?
Holger
linuxholgi said:
Ok, is there a ready-to-use toolchain I can use?
Holger
Click to expand...
Click to collapse
yes it is. it's magical and working like charm
http://www.codesourcery.com/sgpp/lite/arm/portal/release644
Advanced Packages:
IA32 GNU/Linux TAR
unpack to (location) and make changes in makefile of compiling source
Code:
ARCH ?= arm
CROSS_COMPILE ?= /(location)/arm-2008q3/bin/arm-none-linux-gnueabi-
OK I am prepared now, but take some time to get a good working initr.d. Quite busy these days but do my best!
Holger
Anyone has anynews?
check out this link guys:
http://forum.xda-developers.com/showthread.php?t=484228
which links to video on http://exabyte.es/omnia/2009/02/video-con-linux-corriendo-en-omnia/
which contains video of the omnia AND the i780! (starting from around 2min30s)
They even seem to have enabled all of the functions like camera as well, so why not try contacting those people instead of reinventing the wheel?
Greetz
bazzix said:
check out this link guys:
http://forum.xda-developers.com/showthread.php?t=484228
which links to video on http://exabyte.es/omnia/2009/02/video-con-linux-corriendo-en-omnia/
which contains video of the omnia AND the i780! (starting from around 2min30s)
They even seem to have enabled all of the functions like camera as well, so why not try contacting those people instead of reinventing the wheel?
Greetz
Click to expand...
Click to collapse
It would be great, but i don't think samsung will tell you how to run LiMo
Awesome work!
Is there some news?
anyway, keep it on!!! *Thumps Up*
Linux seems to be running fine on the phone. Anyone trying android?
SD card isn't working is the only blocker for me.
I have got CM7 to boot on my Galaxy S using some of the same methods used to boot the stock Gingerbread ROM.
I take credit for nothing... All I did was switched around a couple files to boot CM7 instead of GB.
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be absolutely 100% sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
This is the gingerbread Folder to push in /data/: h**p://dl.dropbox.com/u/17890197/gingerbread.tar
Steps:
1: Download CM7 dump to SDCARD:
h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar
2: Run the following via ADB
adb shell
su
busybox mount -o remount,rw /data
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/CM7.tar
busybox cp -a /efs efs
sync
reboot recovery
3: Flash "nsonsgs-unsigned-cwm-update.zip" via CWM Recovery
Watch CyanogenMod 7 boot on your phone!
How do I get back?
This is a dual-boot setup... Everything is still intact that you were running before this.
All you have to do is download and flash your previous kernel via ODIN. Once you do this, the phone will reboot into Froyo. Simply reinstall the nsonsgs-unsigned-cwm-update.zip and your back on CM7 again, just like you left it. MAGIC!
What's about this port:
- It uses the Nexus S kernel compiled from sources by supercurio
- It runs the exact /system image release, that I pulled from a CM7 alpha .zip file posted in the NS forums.
Which filesystem?
This is simply a mod of supercurio's early gingerbread preview, so it runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
No; will update as I discover more of what does and doesn't work.
Camera is not working.
Wifi is not working.
This can fry the front camera.
Phone could not work . ( sometimes it works )
KEEP IN MIND
CyanogenMod ROMs do not come with any Gapps and using this method, you will not be able to access CWMrecovery to flash the Gapps files floating around. I hope to have an answer to getting Gapps installed with ease by late tonight.
Thanks for all the devs who did this hard work in such a short period of time... please donate to them.
DOWNLOADS:
Kernel : h**p://dl.project-voodoo.org/nexus-s-kernel-on-galaxy-s/nsonsgs-unsigned-cwm-update.zip
CM7 : h**p://dl.dropbox.com/u/17890197/CyanogenMod/CM7.tar
Gingerbread Folder: h**p://dl.dropbox.com/u/17890197/gingerbread.tar
Alberto96 said:
Kernel : http://dl.project-voodoo.org/nexus-s-kernel-on-galaxy-s/nsonsgs-unsigned-cwm-update.zip
CM7 : http://db.tt/TrRnYdm
Click to expand...
Click to collapse
Does this kernel fry front-facing camera?
Just a heads up.
Camera app is not working.
where did this CM7 come from?
from nexus s alpha build . http://forum.xda-developers.com/showthread.php?t=886903
sounds nice, thanks for sharing!
do phone/sms/data/wifi work?
jodue said:
sounds nice, thanks for sharing!
do phone/sms/data/wifi work?
Click to expand...
Click to collapse
Based on my experience from when running the GRH78 build, data etc will work (polling problems persist) Wifi will not work.
Just a heads up for people codeworkx and coolya said not to use this kernel as the voltages are wrong and can cause for you to fry your front facing camera.
They are working on a proper port. Be patient.
Plus its not really alpha because you are not really working in it so how can there be a beta?
This shouldn't really be in the development section.
Sent from my GT-I9000 using XDA App
I was thinking of doing this, never mind
Sent from my GT-I9000 using XDA App
@Alberto96, your CM7.tar.gz file is corrupted !
I've just tried your tutorial in the first post all went well until I typed the line "busybox tar zxvf /sdcard/CM7.tar.gz" then it gived an error :
tar: invalid tar magic
# tar: write: Broken pipe
Click to expand...
Click to collapse
I've tried re-downloading it three times, wipe dalvik cache, update busybox, activate USB debugging but it always gived me this error
tried with supercurios dump and all went well so it can only come from your dump
help will be much apreciated
i will upload a new CM7.tar soon . now i can't because is too late . tomorrow you will have the working one . However, it worked on my Galaxy. Maybe the upload is unsuccessful.
Edit : I did a test and found intact , not corrupted.
7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: C:\Users\Utente\Downloads\.ptmp573137\system.tar
Testing system
Testing system\app
Testing ..............
Testing system\xbin\vim
Everything is Ok
Folders: 63
Files: 1267
Size: 114894721
Compressed: 115906048
Will check that another time then...
Maybe that's because I tried to download it within the phone, I'm downloading now from my PC but... it is now a CM7.tar.tar file ??
will report back after few minutes...
still the same problem here
I've made a screenshot if it can help...
When you said u tested it what are you meanig ? did you try to flash or do you just clicked on the properties thing on the file ?
@Rawat, you are really boring if you don't want to test it on your GS just go get a life and leave this thread alone ! you are ridiculous...
{
"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"
}
Just bumping this.
This Rom/Port whatever will most likely fry your front camera
skyworxx said:
Just bumping this.
This Rom/Port whatever will most likely fry your front camera
Click to expand...
Click to collapse
Not correct if you don't use it at all
thanks for soft.
but loop boot, not work
device nexus, device android ... device nexus, device android ....
Everyone, we (the mods) have gone over this thread and the ROM posted here, and while it certainly will have a limited appeal and use, it is still within the guidelines for what is allowed...the proper credits, etc are included, and it doesn't violate GPL or any other regulations. Therefore the thread will remain, and I will ask everyone here to keep the discussions related to troubleshooting of the ROM itself.
I firmly believe that we should wait until an official alpha is posted by the CMSGS team.
After hearing of the front camera overvoltage, who knows what else could happen? The devs do, and they are working hard to bring us a great experience.
Excitement is great, but so is patience I'm sure it will be available very soon, so just hold on.
If you have a boot loop you must convert your data in EXT4 . I'm uploading the new file . And you must have mounted has R/W the data folder
i uploaded the new CM7.tar . Please test it on your phones .
I created this thread to avoid chatting into other threads keeping them clean..
Please if you have questions about anything post them here, and keep an order.
Use quoting of maximum 3-4 lines, use
or use @ to mention someone without quoting.
Thanks! :good: :highfive:
hi @corsicanu
i have samsung i9070 s advance
cwm and root install method: flash directly through stock recovery
and it does not increase binary counter
and you know that to flash something through stock recovery,
package must be signed with original signature
now, why not it be for fame and for other packages like roms or themes
do you have any idea about signing with an original signature
regards
Naney said:
hi @corsicanu
i have samsung i9070 s advance
cwm and root install method: flash directly through stock recovery
and it does not increase binary counter
and you know that to flash something through stock recovery,
package must be signed with original signature
now, why not it be for fame and for other packages like roms or themes
do you have any idea about signing with an original signature
regards
Click to expand...
Click to collapse
i have no idea how to sign them but i think i have a solution to flash cwm without increasing custom bin.. from what i`ve seen vroot works good for Galaxy Fame without increasing the counter.. And if you succed rooting you can use Flashify to flash img of cwm directly from phone, getting rid of odin.. I didn`t tested this but i assume it works.. will search to see if it`s any chance to sign zip`s with original and also i`ll try the above method to root and install cwm without increasing counter..
Hi @corsicanu
I think, like you, the better idea for optimize our FAME is a new Kernel... I don´t know how to make a new one, but if you can recommend me some literature about it, maybe I can help you in any task.
Thanks for your work.
corsicanu said:
i have no idea how to sign them but i think i have a solution to flash cwm without increasing custom bin.. from what i`ve seen vroot works good for Galaxy Fame without increasing the counter.. And if you succed rooting you can use Flashify to flash img of cwm directly from phone, getting rid of odin.. I didn`t tested this but i assume it works.. will search to see if it`s any chance to sign zip`s with original and also i`ll try the above method to root and install cwm without increasing counter..
Click to expand...
Click to collapse
hey this method is fully working 101% working........as i flash recovery every time with this method on my S6812 !!!!!
it does not effect phone working, binary counter, and it is 100% safe !!!!!!!
cheers !!!!!!!!!!
Vkas Raj said:
hey this method is fully working.. as i flash recovery every time with this method on my S6812 !
it does not effect phone working, binary counter, and it is 100% safe !
Click to expand...
Click to collapse
Not so sure about it.. I need to test it on a fresh device because i have a feeling that the counter will get to 1 automatically when it will detect custom binary flashed.
Hakets said:
I think, like you, the better idea for optimize our FAME is a new Kernel... I don´t know how to make a new one, but if you can recommend me some literature about it, maybe I can help you in any task.
Click to expand...
Click to collapse
First of all you will need a linux distro installed and configured. I followed this tutorial to make it happend. The only toolchain working for our kernel will be 4.6 as the source code needs an update for compiling with newer toolchains without errors. The source code for our devices is here. Download the proper pack for your device/region and unzip it. Inside will be 'how to' file. Looks like this:
Code:
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.6
- edit Makefile
edit target architecture.
- ARCH ?= arm
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.6/bin/arm-eabi- // check the location of toolchain
$ make bcm21654_rhea_ss_nevisp_rev00_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
################################################################################
Long story short:
Code:
mkdir ~/Desktop/kernel
cd ~/Desktop/kernel
mkdir nevis
mkdir toolchains
#Unzip source code for kernel into 'nevis' folder
#and toolchains into their folder.
cd ~/Desktop/kernel
export ARCH=arm
export CROSS_COMPILE=~/Desktop/kernel/toolchains/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-
make bcm21654_rhea_ss_nevisp_rev00_defconfig
make -j16
The outputed file after succesfully compiling will be zImage. Using boot image tools, pack your new kernel with the new zImage and ramdisk.gz from old kernel. Congrats! Now you have a new kernel..
For changing govs, schedulers, freq`s and others see this and make changes in the source. After changing the source use 'make clean' before starting a new build of kernel. Hope i covered all.. Cheers!
Wow, nice answer, thanks so much.
Enviado desde mi GT-S6810 mediante Tapatalk
@corsicanu
buddy
i have problem with apktool
it does not work
i decompile package and even with no changes i can not recompile it
different faults each time
do you know anything about it
i have been using it for months, but i did not faced such a thing before
i updated sdk but no solution
very funny!
i searched xda but found nothing
i used it with no problem yesterday
and suddenly it created problems today
did not understand anything?
{
"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"
}
install framework.apk and tw-framework.apk and set api level to 16 for 4.1.x roms.. and after that it should work.. i'm not at home and i can't give more instructions..
corsicanu said:
install framework.apk and tw-framework.apk and set api level to 16 for 4.1.x roms.. and after that it should work.. i'm not at home and i can't give more instructions..
Click to expand...
Click to collapse
buddy
i told, i have been using it for months
i already installed frameworks and worked on lots of apps
i know how to use it
but interesting, it suddenly gives errors!
regards
Naney said:
buddy
i told, i have been using it for months
i already installed frameworks and worked on lots of apps
i know how to use it
but interesting, it suddenly gives errors!
regards
Click to expand...
Click to collapse
sorry my bad.. i've read in rush.. try with a new working folder and re-setup apk tool.. i had those errors from second print when was a wrong api.. are you using the latest apktool? or try with other apk.. maybe its SecSettings guilty.. cheers!
corsicanu said:
sorry my bad.. i've read in rush.. try with a new working folder and re-setup apk tool.. i had those errors from second print when was a wrong api.. are you using the latest apktool? or try with other apk.. maybe its SecSettings guilty.. cheers!
Click to expand...
Click to collapse
it is not from tool version or working folder or apk.
i deleted apktool folder in personal folder and now it is ok again.
it contains 1 framework file at the moment.
what do you think, why is it?
Naney said:
it is not from tool version or working folder or apk.
i deleted apktool folder in personal folder and now it is ok again.
it contains 1 framework file at the moment.
what do you think, why is it?
Click to expand...
Click to collapse
dont know what to say.. when i decompiled i installed first framework-res and second was tw-framework.. and in personal were two zips.. 1.apk and 2.apk.. and from what i read in cmd from apktool output 1 was for framework and 2 was for tw-framework.. this method of setting up apktool i found it here on xda and was working for me.. but who knows.. if it's working i don't see any problem with that single zip.. btw test the outputted apk because it may compile without errors and could not work if there is anything wrong..
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
Hello,
A few days ago I wrote a new implementation inspired by the work of CyboLabs and Codefire that in harmony contributed for the creation of Open_Bump. Basically I rewrote Open_Bump using POSIX C to run directly on LG G2 or any compatible device with Open_Bump. So now you can bump any kernel or recovery using the target device, validate images to know if they have been bumped and other things.
The source code and binaries for Linux and Android found at: https://github.com/ferreirawax/cbump
FAQ
What is POSIX?
POSIX is an API for Unix-like systems (Linux, Android, etc).
But what are the benefits of this?
Considering the benefits already mentioned above. Other example, if you are a developer, you will probably will get rid of Python or even get rid of everything and create a script to bump the Kernel/Recovery on the flash time.
And why the original developers did not do it?
I do not know.
I do not know how to use it.
See the readme in the link above.
Click to expand...
Click to collapse
Cheers!
It will be useful for developers, thanks for the effort
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
wulsic said:
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
Click to expand...
Click to collapse
Hello,
I know that Python works well, but Cbump was thought to be portable. I did not even know about MultiROM, I checked now and discover that he used the unrepresentative signature in many standard unicodes which is not an elegant method. About -f, yes. I had not thought about Loki up because I have no reason to use Loki instead of Bump (Without disregarding the Dan's splendid work), Maybe I can add support for Loki verification later. About streams take look here, I'll add more information/instructions in thread soon.
Thanks.
@ferreirawax
Very cool work. Can't wait to expand on this and find more use cases!
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Sj12345 said:
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Click to expand...
Click to collapse
{
"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"
}
You're in the WROOOOOONG thread, buddy...
jeebspawnshop said:
You're in the WROOOOOONG thread, buddy...
Click to expand...
Click to collapse
haha,no I dont buddy, LG exploits can be used for all LG devices (we have root on g2,g3,g4,gflex,gflex2 with the SAME EXPLOIT) He understands how the exploit "bump" works... so I need help from HIM to try this in my devices
....... thanks
From Readme.txt
"The flash function uses MSM identifier to detect partition block, Tested only on LG G2, Probably works too with LG G3 and others LG devices powered by Qualcomm."
Sorry its me again
I have a lot of question???? can you help me? @ferreirawax
I have two partitions on my phone (aboot and boot), which should be used???
I will dump the correct partition with
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/boot.img
then use your tool like
Code:
cbump /data/media/0/boot.img /data/media/0/cboot.img
flash partition with
Code:
dd if=/data/media/0/cboot.img of=/dev/block/bootdevice/by-name/boot
and try to booting up....so if this boot up means it works?
and my next step will be make a TWRP recovery???? I will be carefull cause My phone doesnt have kdz or tot for go back to stock... I only have my own backup from dd
@Sj12345 this is a rewritten version of open_bump so if bump didnt worked on your device this won't work either. Lollipop isn't working with bump only jellybean and kitkat as far as I know. Also I suggest before doing these things to learn what the partitions etc are before you will hardbrick yourself. Aboot is the bootloader. Boot is the boot.img so that's the kernel.
It probably will result into an security error.
Sent from my LG-D802 using Tapatalk
One word: COOL
This is awesome, thank you so much. Now we can use .zip to bump and flash, just like loki method. Will make testing things SO much easier. Won't have to re-bump the image every time
You the man!
Now if u can get one for the G4 n get the $10,000 bounty!
Sent from my LG-H811 using Tapatalk
5 Star For You [Excellent]
Testing Cbump to our devices
Awesome Tools! :good:
It should help multirom?
Inviato dal mio LG-D802 utilizzando Tapatalk
Edited
Sorry for the bump (ehehe), but does anyone have a mirror of this? Nvm, solved!
https://github.com/dorimanx/cbump