Related
Hello!
This is a thread where potential developers can get kernel and platform source code for Samsung Galaxy S I9070 Advance, and other info. I will try to update this until we will have first custom rom ready. I encourage everybody with some experience with android development, to share their knowledge with other users here. Please if any of you will make any progress in rooting, making recovery or developing custom rom, to write here in this thread or even start a new one if some major break trough will be made.
Ok so here are the links to sources (I don't know the diference between those to, but I guess it is region related):
GTI9070_GB_OpenSoruce
GTI9070_LA_GB_OpenSoruce
All sources, can be found HERE.
In the attachment you can also find some other info I've pulled from my phone, which used to be rooted, cause I had some test version. I hope all this stuff will help us get root access, custom recovery and last but not least a whole bunch of custom roms.
NOW LETS HACKING AND DEVELOPING BEGIN!!!
One more thing, PLEASE take a minute to VOTE for this phone to get its own forum section here on XDA. Just make a post in THIS THREAD. The device is not in the poll yet, so you must write a post in thread. THANK YOU!
We've made a step into a right direction with a lot of help from forum I've made a working root method!
I've hard bricked my phone, so I am off the developemnt from this phone, only if by some chance I get a replacement. Sorry guys, in spirit of developing I've killed my phone .
I wish I was better at kernel development... I would love some development for this phone!
Sent from my GT-I9070 via Tapatalk 2
I've somehow managed to configure linux and pulled andorid sources from the repo, now I have to figured out how to compile a kernel. I have much to learn but if nobody else will give it a try, maybe I will succeed.
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
kilsmap said:
yeah...we as new wannabe devs are learning back the basics...i'm still trying to figure out what to do about the kernel source...afraid of bricking my phone in the process... hehe.. but all the kernel sources for all regions has been released...
Click to expand...
Click to collapse
Dear friend. I come from China, now I already have a good i9070, I can help you with your test, you can send to my mailbox [email protected]
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
kilsmap said:
hmmm...qzem, im getting stuck at initramfs...how do we get these for our phones? because the kernel can only be flashed safely when it is compiled with initramfs files from our phone... and for the phone to get custom recovery, i think they will also need initramfs files...
Click to expand...
Click to collapse
Same thing here. I have no idea how to get those, been asking around the forum an searching, but for now all the directions indicates that you need to have root access to get iniramfs. That really sucks...
hahaha...from this point of view, all Samsung phones after Galaxy S Advance will be quite hard to root... I'm waiting for the Galaxy SIII to launch, and for someone to root it... Maybe then we will be able to use the same way to root our phone... If only we can see what's inside our kernel.bin.md5... I'm sure the files we needed are in there...
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
an0nym0us_ said:
the initrams? u mean ramdisk?
grab stock boot.img and extract from it.
the stock boot.img can be grabbed from odin flashable stock rom.
Click to expand...
Click to collapse
Yeah.. We have the stock rom, but can't figure out which one should we extract the boot.img from.. There was system.img.md5, cache.img.md5, hidden.img.md5, modem.bin.md5, and kernel.bin.md5... So which one? My suspicion lies to the kernel.bin, but I have no idea how to extract it..
Sent from my GT-I9070 using XDA
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Good luck!
Hope you get to a solution soon
I can't work on it as I currently don't have a phone to test on, sent it in for repairs.
qzem said:
I have compiled a stock kernel from source code, so I got zImage file, now I have to find out how to build boot.img from this. I will contiue tommorow I hope I am close to the solution! Mabe few days to crack this baby .
Click to expand...
Click to collapse
Have u tried flashing it directly to the phone? You don't have to make it into a boot.img to flash it.. Because I'm afraid that the zImage will be useless if not paired with working initramfs.. Compiling the kernel is quite straightforward, the thing is to get the initramfs to turn the kernel insecure.. There are also scripts to extract initramfs from zImage, but I haven't had time to test it..
Sent from my GT-I9070 using XDA
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
qzem said:
Ok what exactly is in initramfs, that is what I am trying to figured out? I've recompiled some other samsung boot.img with dsixda kitchen, and I got zImage and a folder caled boot.img-ramdisk, which included different files like init, init.goldfish.rc init.rc, default.prop, etc. In a file default prop is the setting ro.secure=0, and this is the settign I belive, that makes kernel insecure. I've also tried to unpack the zImage that I got from thsi boot.img, with the kitchen to see if includes those so called initramfs, but it doesn't. So I think that if I figured out which files should be in ramdisk, and if those files can be pulled of the phone, that than maybe I can repack a working boot.img. What do you think?
Click to expand...
Click to collapse
Yep, you got everything right there, I think.. Initramfs, ramdisk are the same thing.. They should include the cpio.gz, init.rc, default.prop etc... Have you extracted these files from the source kernel? Cos I don't think we can copy directly from phone, cos we need to preserve the permissions set on the files... Can you do that with kitchen?
Sent from my GT-I9070 using XDA
I am following the topic and hoping it works out the development of kernels and roms to the device.
Come on it has to be a way to compile an insecure kernel without having the access to rooted phone. Cause all the options I found till now, required some files, that can only bee pull from rooted phone. But the whole point of an insecure kernel is the possibility to root the phone. Anybody can help us? Maybe I should start another thread, damn it!
Haha... Yeah, somehow I feel that Samsung is screwing with us, what with the new firmware format (never had kernel.bin before) and secured kernel, this is becoming impossible.. If we just have some devs good-hearted enough to port CWM recovery for us.. But without initramfs, I don't know if it's possible..
Sent from my GT-I9070 using XDA
The initramfs is inside kernel.bin.md5 (as for the Galaxy S firmware).
kernel.bin.md5 is a normal zImage Linux kernel (+md5).
the initramfs is included in the kernel image (see http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage)
the initramfs is in our case a uncompressed cpio archive, therefore the script in the wiki does not work, but https://github.com/mistadman/Extract-Kernel-Initramfs/blob/master/unpack-initramfs can extract it without problem.
So, there should be no difficulty to root the i9070...
The easiest way would be to change the initramfs and repack everything.
Hi all.
I open this thread about how i theme my OMEGA V20 LSD ROM only for people who are using an LSD ROM (works with LSJ,LS8 or >) in 2nd ROM.
Before continuing reading my speech, You have to follow this uniq thread
http://forum.xda-developers.com/showthread.php?t=2120514
to understang what i'm talking about.
If you have understand the thread, you can adjust and use my ZIPs as you want.
(I use the thread mentioned with OMEGA V20 LSD which i REPACK for good use in 2ND ROM.)
I Assume that my ZIPs THEMER are working only in this configuration.
What about this special configuration with a little explaination :
due to the volume of LSJ,LS8,LSD rom,your system have to be organize like that :
\system\app\*.apk
\data\app\app\*.apk (which contain apks system which normally are in \system\app\ but in our case, they are
symlinked in \system\app\*.ln so we have gain place in partition \system\ , also *.apks and *.ln are
put with the good rights.
So if you have this configuration you can use my ZIP and in case modified them before flash if your APKs system are put in <> forders from mine.
I have to modify installtheme.sh and updater-script too.
You can see some example here too :https://www.youtube.com/watch?v=cCpwfLOP4As
some other interesting screenshot on pages http://paymadman.blogspot.fr/2013/03/theme-pour-omega-v20-lsd.html
and http://paymadman.blogspot.fr/2013/02/omega-v20-lsd-orange-ou-vert.html
If i make a mistake in creating thread here, inform me to help me too.
Thank's for reading until here and hope you have also understand my poor school english we learn in France and excuse it
All my ZIP here or here always updating
Be careful
Sometimes flashing my ZIP take very very long time but dont be affraid, it's not freeze like windows XP before blue screen , you have to be patient during flash, that's all
If someone make Omega(or any other stock rom) looks like a CM10.1 that would be an achievement for sure.
Nice info man.
AW: THEMES for LSxxxx 4.1.2 only in 2nd ROM
Well done Mate
Sent from my GT-I9100 using xda app-developers app
some other repack theme
ohwarumbloss said:
Well done Mate
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
All thank's to you Man, for your thread too
After http://forum.xda-developers.com/showthread.php?t=2172236 Liverpool Theme I repack for Omega v20 2nd Rom,
I test this from
http://foro.elrincondelmovil.com/ro...oid_4-1-2_xxms1-adesirello-y-sherpa47-243053/
New repacked MODS from ApriliaM3 and Spannaa
Regarding these 2 links
http://d-h.st/users/ApriliaM3/?fld_id=13203#files
and
http://goo.im/devs/Spannaa/SGSII_VRThemes/JellyBean_VRThemes/
I think some NeatRom users and others LSN JB 4.1.2 users that manage a 2nd ROM should have a look here , i share some repack i just finish now.
Thanks to waste time to test them
And Thanks ApriliaM3 and Spannaa for their great great works .
Hi all,
This is probably my first post so before I go ahead I'd like to thank all developers on this site. It's got a wealth of information that helped me a lot.
Unfortunatey I haven't found a way to do this yet, so I'm posting and asking for help with this issue I'm having...
I used to run CM10.1 on my Nexus 4, I always patched that rom with autopatcher to apply openpdroid so I could set privacy stuff using the Pdroid Manager app.
I decided to go back to the stock rom due to issues I was having (my phone actually got bricked and I managed to fix it following excellent instructions that I found here).
Now I can't apply the openpdroid patch to the stock ROM because autopatcher only accepts zip files and I'm sure that it needs the structure of the ROM.zip to work. The Google factory image is a ROM.tgz file and upon extracting a zip and the factory image, I noticed that the structure is completely different. I have no idea how to create a zip file out of the stock rom.
I'm wondering if anybody could do this? I'm not sure if autopatcher requires deodexing... All I need is a stock 4.3 mako image in the form of a zip file that works like the CM roms, so I can patch it with openpdroid via autopatcher.
Is this possible? Could someone here do it, please?
I'll be keeping an eye on this thread.
Thanks all for reading!
Welcome to the great xda-developers forums
Well you should search the Forum with the forum search for a tutorial to zipalign your stock rom, there are many out there i think.
I think i even saw a rom kitchen for that.
That thread belongs to Q&A by the way
(Just a tip on the side)
272 2589539
Thank you, as you can see I'm new here I tried to search for something but I'm not sure if I was using the right terms, so I decided to ask. I didn't even know about this zipalign or rom kitchen stuff, but now that you mentioned it I will research. Thanks!
Kartoffelrudi said:
Welcome to the great xda-developers forums
Well you should search the Forum with the forum search for a tutorial to zipalign your stock rom, there are many out there i think.
I think i even saw a rom kitchen for that.
That thread belongs to Q&A by the way
(Just a tip on the side)
Click to expand...
Click to collapse
hithereperson said:
Thank you, as you can see I'm new here I tried to search for something but I'm not sure if I was using the right terms, so I decided to ask. I didn't even know about this zipalign or rom kitchen stuff, but now that you mentioned it I will research. Thanks!
Click to expand...
Click to collapse
Just my opinion but I think it would be better to find a stock, 4.3 deodex ROM in a flashable zip. I'm dead sure there's a few floating around in android or original android development. That would make it easier to patch
Edit: this should do, stock 4.3 zip:
http://forum.xda-developers.com/showthread.php?t=2010887
Enjoy :thumbup:
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hello everyone, I'm a newbie here so please do correct me if I'm posting in the wrong section or the wrong format, etc. I want to play by your rules!
Every time I boot my phone it takes very long - usually about 53 seconds. I know I have way too many apps (178 user ones last time I checked) but I still think that's too slow. I read about a build.prop tweak that enables the "quickpoweron" setting, like some Samsung devices have built in. I would try it out, but I've already bootlooped my phone once after I made some other changes to build.prop, so I'm reluctant to bootloop it again and go through the pain of restoring a backup. Does anyone have any experience of mixing a CM11 M9 Nexus 4 and "ro.config.hw_quickpoweron=true"? If anyone has, I'd like to know:
Does it work - will it bootloop the phone?
Is it worth it? What (if any) is the speed improvement - before/after?
Is there anything else I ought to know before doing it - any negatives?
Many thanks in advance to anyone who can help me out here with any experience! I appreciate it greatly!
--
XDA Newbie
Rooted Nexus 4 (Mako) 16GB
CM11 M9
CWM 6.0.5.0
pmedwards25 said:
Hello everyone, I'm a newbie here so please do correct me if I'm posting in the wrong section or the wrong format, etc. I want to play by your rules!
Every time I boot my phone it takes very long - usually about 53 seconds. I know I have way too many apps (178 user ones last time I checked) but I still think that's too slow. I read about a build.prop tweak that enables the "quickpoweron" setting, like some Samsung devices have built in. I would try it out, but I've already bootlooped my phone once after I made some other changes to build.prop, so I'm reluctant to bootloop it again and go through the pain of restoring a backup. Does anyone have any experience of mixing a CM11 M9 Nexus 4 and "ro.config.hw_quickpoweron=true"? If anyone has, I'd like to know:
Does it work - will it bootloop the phone?
Is it worth it? What (if any) is the speed improvement - before/after?
Is there anything else I ought to know before doing it - any negatives?
Many thanks in advance to anyone who can help me out here with any experience! I appreciate it greatly!
--
XDA Newbie
Rooted Nexus 4 (Mako) 16GB
CM11 M9
CWM 6.0.5.0
Click to expand...
Click to collapse
No harm done, no bootloop. Phone starts just fine running android L preview. If you don't mind anecdotal evidence, my phone did seem to boot slightly quicker. I'm not willing to spend the time to clock how fast it boots with/without the build.prop edited, though...too much hassle for how far I'm willing to go for this, since it's probably only 10 seconds, at best.
Thanks
Thanks for the advice, on the first boot I got a bootloop. On the second boot (out of recovery) I didn't time it but it was quite quick. On the third boot (normally) it was 1:03. Odd.
Probably just a placebo effect, unfortunately. I would just let the device do its thing on boot up
Sent from my Nexus 4 using XDA Free mobile app
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
CrashDSB said:
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
Click to expand...
Click to collapse
Is it the global version of MIUI 8? Must be based on cm13. Right? I will be glad to be a tester.
Me...
Would be great to have a Miui8 for N4! I will be glad to be a tester.
im so interested
Miui 8? of course
Somebody tell me the procedure... I can port it...
I was reading the porting guide myself the other day... but it seems to be quite a bit of work!
Count me in. Currently running the last version.
Bleh........
Sent from my Nexus 4 using Tapatalk
CrashDSB said:
I've been learning and figuring out how to port MIUI, and I have a general understanding of it, would anyone be interested in a port for Nexus 4? I do not have a Nexus 4 on the ready though, so it'd have to have others testing it.
Click to expand...
Click to collapse
What's the status?
I'm interested
Past monday I've made one version based on AOSP 6.0.1 from xda
I can't test it yet, because I've only one nexus 4 and it's used on my work.
I've tried to flash but, I can't, get stuck on the begining of updater script. I think it was because I'm on TWRP and I need to change to Clock Work Recovery.
I have no time to flash it beacuse I need to travel out from home this week. All rejects should be repaired.
If some want to test, i'll put a link to my drive. It's a heavy zip about 650 Mb, I think some apk's should be removed like FM that will not work on our nexus 4 but I can't do it today..
magnus48 said:
Past monday I've made one version based on AOSP 6.0.1 from xda
I can't test it yet, because I've only one nexus 4 and it's used on my work.
I've tried to flash but, I can't, get stuck on the begining of updater script. I think it was because I'm on TWRP and I need to change to Clock Work Recovery.
I have no time to flash it beacuse I need to travel out from home this week. All rejects should be repaired.
If some want to test, i'll put a link to my drive. It's a heavy zip about 650 Mb, I think some apk's should be removed like FM that will not work on our nexus 4 but I can't do it today..
Click to expand...
Click to collapse
It's not a problem with TWRP, it's a rom size problem. Fullota.zip is too big and compatible with TWRP 3.0.2.
I'm reducing his size deleting sounds, apk's inside the zip.
I've made a first version that can be flashed (takes really long long time it's about 550Mb).
Unfortunatelly, boot begins, miui animation is charged, but get stuck with this message in logcat
11-09 07:24:07.017 186 186 E kickstart-qcks: File '/firmware/image/efs1.mbn'
was not found
E kickstart-qcks: Prepend failed.
Seems a problem with boot.img but don't know yet how to resolv this...:crying:
whats the latest news
I love you miui
Efs partition relates to the modem and radio I'm pretty sure are you sure its not that
Sent from my Nexus 4 using Tapatalk
It's a boot.img problem. I Need to study it, but i have no time...
I just bought a Redmi note 3 pro. So my, now, i have a spare nexus 4 just for test, so feel free to send me roms and i'll give you the logcat.
Hope i can help!
---------- Post added at 02:30 AM ---------- Previous post was at 02:30 AM ----------
I just bought a Redmi note 3 pro. So my, now, i have a spare nexus 4 just for test, so feel free to send me roms and i'll give you the logcat.
Hope i can help!
miuı 7 problems rom