Hi to all!
I've created this topic that we can discuss about the CM7 and CM9 ROMs that are in development, and not flood the development topic with Q&As. Feel free to post!
How to avoid bricking the SGS+
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!
You can get the most important partitions from the wiki: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/GT-I9001#Partitions
I once dumped all partitions and can verify that the most important stuff is below the kernel partition, so don't mess with them. mmcblk0p14 is a parameter partition (thx skywalker01) for the bootloader, that is what causes some devices (including mine) not to work 100% correct with CWM. You can only get out of recovery boot loop by dd'ing zeros to that partition.
despotovski01 said:
I've heard that this phone is somewhat easy to brick. This made me think twice before doing some 'serious stuff' with the phone, like trying to make a CM7 or ICS ROM. Can somebody tell me how to avoid bricking this phone? And is it risky to flash source-built ROMs? It would be good if someone tell me the partitions of the phone (in which is stored what: e.g. in which partition is the kernel, the bootloader, etc.).
Thanks in advance!
Click to expand...
Click to collapse
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .
rayiskon said:
looking back at this post u gave very high expectations . Anyways, building a rom from source isn't hard at all, the tough part is to make the hardware work, so most probably u'll end up with a non working touchscreen for a start, not to mention u need a kernel that'll make it boot at all. As for the partitions, skywalker is the man to ask, i can tell u though that the kernel (boot.img) is in /dev/block/mmcblk0p8 .
Click to expand...
Click to collapse
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.
Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.
despotovski01 said:
Thanks. I was looking for the bootloader partition, because if you mess it up, your phone wouldn't boot at all. If you mess up the kernel partition, your phone won't be able to boot into the OS, but it will be able to boot in CWM and Download mode. I'm asking this here because I heard that this phone has weird partitions, so I want to be sure I'm not going to brick my phone doing these stuff.
Click to expand...
Click to collapse
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker
rayiskon said:
as wintel already said and as it's mentioned in the wiki (WARNING: Partitions below 8 contain absolutely vital stuff like the primary boot loader responsible for low-level hardware initialization. Messing with them is what leads to fully bricked phones because you will not be able to get into download mode anymore! ) . but for any detailed info, contact skywalker
Click to expand...
Click to collapse
Thanks, I've sent him a PM.
GIBbeerSKY said:
Hello all
Today i've made small performance comparation of CM7 KANG and Teamhacksung's ICS b14.
Please note that this KANG is used by me for everyday use with over 60 apps installed, without any scripts etc. (only Chainfire 3D @ nVidia) and ICS is freshly installed. All tests made on airplane mode.
Standard 1000MHz, ondemand, no UV/OV.
I plan to made comparation with latest Samsung ROM.
Click to expand...
Click to collapse
Are you talking about SGS i9000 or SGS+ i9001?
I'm sorry, I've missed the "1" at end of model.
well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??
YMYA said:
well is there any hopes that the CM7 or CM9 will be issued soon for the i9001?
one more thing, should I buy the i9001 or the i9000 is better??
Click to expand...
Click to collapse
i think u already made ur choice. here and here
rayiskon said:
i think u already made ur choice. here and here
Click to expand...
Click to collapse
tht wasn't mine..
so what do you suggest?
YMYA said:
tht wasn't mine..
so what do you suggest?
Click to expand...
Click to collapse
neither. S2 or galaxy nexus
rayiskon said:
neither. S2 or galaxy nexus
Click to expand...
Click to collapse
what if i have to choose one of them..which one is better?
YMYA said:
what if i have to choose one of them..which one is better?
Click to expand...
Click to collapse
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.
rayiskon said:
http://www.gsmarena.com/compare.php3?idPhone1=3115&idPhone2=3908
S+ has a stronger CPU , GPU comes about the same when u update gpu drives,other stuff are more or less similar. so S+ is a lil stronger, but if u care for community support (ICS etc..) u will go for I9000.
Click to expand...
Click to collapse
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?
YMYA said:
I am aware about all of this..i mean whats ur personal opinion..if u have to buy one of them which one will YOU get?
Click to expand...
Click to collapse
although the lack of community support is a very big minus, but i'd still get the S+ , coz it's better. the only thing i miss is to try an ICS build, but i'm sure it will be here sooner or later.
DroidXDA
SGS+ News :: We almost to booting stage with now fixing the kernel (we hope it will work out) :: do support us by clicking our advert at our blog thanks Have A nice Days
Click to expand...
Click to collapse
Just to let you know...So hopefully they will get it working
What Build is current cm9 ?
One Question, What is the Build Number of our cm9 ? because i want to patch LunarUi Theme ,but it has many zips for many builds of cm9 , thanks
Related
Hey ,,
can someone root Cyanogenmod 7 or Cyanogenmod 6 android roms to A101??
Is it possible??
For the thousandth time:
No, there is no Cyanogen Mod on Gen8
We have only one Rom: Urukdroid, but this one is goood Try it.
Why you want exactly Cyanogen?
Why you want exactly Cyanogen?
Because It supports Arabic and other languages
but Uruku not support them
Aahh, thats the problem
ask sauron whether he can add this feature
Otherwise you have to live with english
until we get a custom recovery
hmmm
Ok then we must wait for that
If Cotulla is here he can do it easily
@saprano614:
Why do people thing that CM7 needs a recovery?
THERE IS NO NEED FOR A RECOVERY ON GEN8.
If you get someone to compile the CM7 with all the specifics for the gen8 ( f.ex. display via usb ) and some other things it is easily done, as $auron has allready proven with UrukDroid.
So please all stop wining about a recovery.
Moved to proper forum.
fzelle said:
@saprano614:
Why do people thing that CM7 needs a recovery?
THERE IS NO NEED FOR A RECOVERY ON GEN8.
If you get someone to compile the CM7 with all the specifics for the gen8 ( f.ex. display via usb ) and some other things it is easily done, as $auron has allready proven with UrukDroid.
So please all stop wining about a recovery.
Click to expand...
Click to collapse
Thanks for enlighting us/me
I want to learn about android developement (at the moment i test solune's Urukconfig),
could you tell me: what is an recovery? (I dont think its a recovery what recovery you data/apps/media like on a pc.)
"The Recovery" is kind of an extended bootmenu for the devices where you can flash new ROMs or make a backup so that you can get back to where you are.
Normally it also comes with alot of custom scripts for root, displaydensity,cleaning caches, memhacks etc.
This is needed on other devices because they don't habe a SDE.
fzelle said:
"The Recovery" is kind of an extended bootmenu for the devices where you can flash new ROMs or make a backup so that you can get back to where you are.
Normally it also comes with alot of custom scripts for root, displaydensity,cleaning caches, memhacks etc.
Click to expand...
Click to collapse
Oh thank you i didnt know that
fzelle said:
This is needed on other devices because they don't habe a SDE.
Click to expand...
Click to collapse
Okey, but if thats true i've another question:
Why nobody test some Roms from other Tablets/Phones on our Gen8?
It's true we have SDE that let us use UrukuDroid !!
That mean we can have other versions of roms like Cyanogenmod 7 or 6
Why nobody test some Roms from other Tablets/Phones on our Gen8?
this is good question ,,
why we don't try other roms like HTC HD2 !! It uses many many roms !!
impossible to install cm7 with the SDE
cajl said:
impossible to install cm7 with the SDE
Click to expand...
Click to collapse
Impossible is not French
@cajl:
That's not true.
CM7 is just one of many kernels done on the google basiscode.
If you could get the display to work and get the drivers of the other stuff in there it is just the work to get the initramfs to do the wireing of the partitions.
So if some of the cracks from the cm team would start with a "port" they would probably be ready before the end of the week.
I know, why don't one of you send the Cyanogenmod guys your Archos so they can get it done? lol
willowave said:
I know, why don't one of you send the Cyanogenmod guys your Archos so they can get it done? lol
Click to expand...
Click to collapse
Thats a good idea
I emailed them, when them response me, i report it here
Lennb said:
Thats a good idea
I emailed them, when them response me, i report it here
Click to expand...
Click to collapse
I think this is the best thing you have done in your life >> joking
Thanks bro and we'll wait for your feedback,,
fzelle said:
@cajl:
That's not true.
CM7 is just one of many kernels done on the google basiscode.
If you could get the display to work and get the drivers of the other stuff in there it is just the work to get the initramfs to do the wireing of the partitions.
So if some of the cracks from the cm team would start with a "port" they would probably be ready before the end of the week.
Click to expand...
Click to collapse
cm7 is not ''just'' a kernel and we have no indication how long it will take the cm7 for sgs is in the making for month and they have some great devs
it could be easy but to be honest i would bet money that we will never have a stable cm release
Sent from my GT-I9000 using Tapatalk
You are partially right, but the kernel part is the harder one to port, if that is done ....
But you are right with timing.
Even on my milestone it took them so long and roms like froyomod are alot more stable.
Hey everyone,
I'm an X G2x user, and over there in "G2x" land I rooted my phone first.
Then I flashed Clockwork recovery on it
THEN I had a smorgishboard selection of "Roms" to put on my phone.
Here's where i'm confused with the Galaxy S 2, and Terminology really..
What "do we have" here with the SGS2 so far?
Just rooting it? I see over on the dev section people talking about all these kernels... what is that? are they like Roms? Has anyone mad a rom? can we flash it like clockwork mod recovery?
Just a little confused with the differences in terminology and procedures over here on the samsung side.. thanks
No custom roms yet, no CWM either. Just kernels and root....the kernel is a bridge between applications and hardware basically. Terminology shouldn't be that much different really.
computermilk said:
Hey everyone,
Then I flashed Clockwork recovery on it
No clockwork for SGS 2
THEN I had a smorgishboard selection of "Roms" to put on my phone.
No roms for SGS2
Just rooting it? I see over on the dev section people talking about all these kernels... what is that? are they like Roms?
Kernels are the base interface between OS and hardware and part of a rom
Has anyone mad a rom? no can we flash it like clockwork mod recovery? no
Far to early for all that SGS2 been out a week + devs in many cases do not yet have SGS2 ( donate one to them ) .
Devs are not getting paid for all this work so as and when they find time and the money to buy SGS2 .
SGS2 is being worked on and no doubt more in the future .
jje
Click to expand...
Click to collapse
Bear in mind things don't always get posted as soon as they're done. I don't like releasing things that I can't test, so I've got some stuff for as soon as mine actually turns up...
The stock issues have slowed things down a LOT.
pulser_g2 said:
Bear in mind things don't always get posted as soon as they're done. I don't like releasing things that I can't test, so I've got some stuff for as soon as mine actually turns up...
The stock issues have slowed things down a LOT.
Click to expand...
Click to collapse
When did you order yours? It seems like you've been waiting forever...
Thanks for the answers guys it was confusing me.
I'll wait for a CWM flash
computermilk said:
Thanks for the answers guys it was confusing me.
I'll wait for a CWM flash
Click to expand...
Click to collapse
You can use Odin to flash newer ROMs and to root the device...it's pretty easy.
bigmo7 said:
You can use Odin to flash newer ROMs and to root the device...it's pretty easy.
Click to expand...
Click to collapse
Oh yeah?
Is Odin better then Clockwork mod recovery? i'll go take a look over in the dev forums for the thread on it. thanks
computermilk said:
Oh yeah?
Is Odin better then Clockwork mod recovery? i'll go take a look over in the dev forums for the thread on it. thanks
Click to expand...
Click to collapse
They're just different, CWM just doesn't need a PC to flash the FW...that's all.
pulser_g2 said:
Bear in mind things don't always get posted as soon as they're done. I don't like releasing things that I can't test, so I've got some stuff for as soon as mine actually turns up...
The stock issues have slowed things down a LOT.
Click to expand...
Click to collapse
when is urs coming buddy ? i feel like posting it to you once i get my hands on this coming tuesday... because i have seen so many posts where you are quoting that you have been waiting for your device & its still not delivered because of delay..
is it true that you r waiting for the device with NFC or its just a delivery delay ?
Team Nyx
-- DemonWav -- Nushor -- Onecosmic -- PaulForde -- RaymondDull -- Trae32566 --
This ROM is based directly on the source code straight from Google themselves, the way Android is meant to be. This ROM is produced by a collaboration of many different people, with the main development being done by Onecosmic himself. We strive to bring releases as often as possible and provide a stable AOSP ROM.
We are in the midst of many changes and will try to have our source code back up as soon as possible.
We do not support anything that is not produced by us!
Team ICSSGS is now Team Nyx!
We have made lots of changes, and part of that includes moving our base from XDA to our own website. All information, as well as downloads will be on our website, but please continue your discussions and we will continue our support here on the forums. Please check out our site at http://team-nyx.com/
loleverything works pretty much not a huge need for this here
The other thread needed replacing.
not that im complaining, but why did it need replacing? (in your eyes)
TRusselo said:
not that im complaining, but why did it need replacing? (in your eyes)
Click to expand...
Click to collapse
Lack of willingness from the OP to cooperate and to keep the thread updated.
TRusselo said:
not that im complaining, but why did it need replacing? (in your eyes)
Click to expand...
Click to collapse
b-eock wasn't involved with the project, we wanted a bit more control over how the OP was updated, and we didn't want someone not even contributing to make the real people behind this (mostly Onecosmic) look bad.
ytt3r said:
b-eock wasn't involved with the project, we wanted a bit more control over how the OP was updated, and we didn't want someone not even contributing to make the real people behind this (mostly Onecosmic) look bad.
Click to expand...
Click to collapse
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..
goob1284 said:
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..
Click to expand...
Click to collapse
The kernel wasn't changed, actually. And there is a chance, but we're focusing on the big issues now, we'll put more features in later.
is this build going to be pure ASOP first? the other thread was talking of changing the "crappy" battery icon and other stuff.
ASOP fist. right?
goob1284 said:
So.... since your in charge of the kernels... any chance of a 1600Mhz over clock? Just wishful thinking..
Click to expand...
Click to collapse
I just hope it doesn't end up like Talonmtd lol.
Herp derp Captivate XDA Premium.
TRusselo said:
is this build going to be pure ASOP first? the other thread was talking of changing the "crappy" battery icon and other stuff.
ASOP fist. right?
Click to expand...
Click to collapse
That's another thing, that other thread was complete bullcrap. We are focusing 100% on AOSP at the moment. I'm working on side flashes to try to improve the rom, but they are not a part of the rom or have anything to do with Onecosmic.
I don't know why you said it won't boot. I'm on a7 with captivate kernel you posted in google code. Can't get 3g working yet but it boots just fine
If I want to flash from apex 11 w/ dark kernel, what's the process I should go through?
jmbradd said:
I don't know why you said it won't boot. I'm on a7 with captivate kernel you posted in google code. Can't get 3g working yet but it boots just fine
Click to expand...
Click to collapse
I did the same, except none of my buttons are working? i might reflash and see what happens. Also it seems to lag more the A6. Im gonna try a reflash and see if everything gets straightend out
autocorrelation said:
If I want to flash from apex 11, what's the process I should go through?
Click to expand...
Click to collapse
Download the required files (ROM, Kernel, and SU fix), and make sure you have a GB Bootloader.
1. Backup your files, and do a Nandroid
2. Reboot to Recovery
3. Wipe Data, Cache, and Dalvik. No need to wipe system because it's done already on the updater script.
4. Install .zip from SD card. First of all flash the ROM, then go for the Kernel.
5. Reboot, the first boot takes longer.
6. Setup your account.
7. Boot to recovery, and install the SU.zip to grant you with Root access.
8. Reboot, and enjoy.
Notice I do not ask you to wipe and flash several times, it honestly works at the first attempt.
Good Luck.
dumb question is this still a port for the captivate ? and will flashing this mean you need specific boot loaders to start I run i9000 boot loaders and sorry for posting question here but never got an answer in the q&a will ICS support HSDPA like JVT did?
Just wanted to thanks guys. This is awesome.
@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
white00gt said:
dumb question is this still a port for the captivate ? or is phone listed in title different and will flashing this mean you need specific boot loaders to start I run i9000 boot loaders and sorry for posting question here but never got an answer in the q&a will ICS support HSDPA like JVT did?
Click to expand...
Click to collapse
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
everest.deth said:
@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
Click to expand...
Click to collapse
It is the same, I am just packaging it up to simplify it for the noobs. I just uploaded a .zip, then I realized that I had screwed up with it, so I'm re-uploading now.
EDIT: As for it being slower, Alpha 7 has some wicked partitioning changes that should speed it up. Of course we are always trying to make it better, but HW Accel. is built into Alpha 7.
everest.deth said:
@OP
Is it the same thing to go to: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list, download the A7 ROM "ICS_4.0.1_r1-alpha7.zip", and flash the Captivate Kernel? Or are you uploading a different version, with more changes?
I am asking because I honestly feel like this A7 update is a tad slower than the A6 i downloaded previously. (The A6 zip i was linked to already merged both the Kernel, and the ROM into one same updater script.)
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
Yes, It is working for the Captivate. So far, all you have to do is download the I900 ROM, and then flash the Captivate kernel.
Links: http://code.google.com/p/ice-cream-sandwich-sgs/downloads/list
Click to expand...
Click to collapse
thanks might wait a little while before flashing but it is very tempting
Ok so i have attempted a port of the galaxy note 10.1 jellybean rom, using CM10 as a base i have run into a bootloop you can download this link and try it out also will be my logcat
also if you can tell me how to fix this i would be happy to do it too
Drop Box Port: Galaxy Note 10.1 Port
Logcat:LOGCAT
i believe the error is with my kernal
jnktechstuff said:
Ok so i have attempted a port of the galaxy note 10.1 jellybean rom, using CM10 as a base i have run into a bootloop you can download this link and try it out also will be my logcat
also if you can tell me how to fix this i would be happy to do it too
Drop Box Port: Galaxy Note 10.1 Port
Logcat:LOGCAT
i believe the error is with my kernal
Click to expand...
Click to collapse
Have you tried other kernel, like eztery or godmachine's kernel?
Sent from my GT-S5570 using Tapatalk 2
10507 said:
Have you tried other kernel, like eztery or godmachine's kernel?
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
no if you have it can you please try, I don't feel like installing another kernel, but will work on it
Wow this would be a miracle if this ROM works
yes sir indeed i got my fingers crossed hoping this ROM happens
Did you split your boot.img and change the ramdisk image and such? While retaining the 500 kernel?
If you are going to port something, this is one of the basics.
Just changing a few hardware files, won't work.
MD
Moscow Desire said:
Did you split your boot.img and change the ramdisk image and such? While retaining the 500 kernel?
If you are going to port something, this is one of the basics.
Just changing a few hardware files, won't work.
MD
Click to expand...
Click to collapse
No i knew i forgot something, did you read the logcat, i dont read logcat but i think it said that it had a memory error
jnktechstuff said:
No i knew i forgot something, did you read the logcat, i dont read logcat but i think it said that it had a memory error
Click to expand...
Click to collapse
Well, you said it all, probably there is no memory in the the place the kernel is trying to setup its stack, is your kernel an A500 one or is it from another machine with a different memory layout? because it smells like the latter.
Cheers
you've also got the think about the ramdisk too . . .
Hey guys i will be on vacation for the next week so i will not be able to work on it, if you want the download link is right up there^^^^
If you get it booting, you will get credit and half of donations:angel:
i am resigning from this project, working on my own custom rom, the stuff is here do it if you want
What happens
jnktechstuff said:
i am resigning from this project, working on my own custom rom, the stuff is here do it if you want
Click to expand...
Click to collapse
Sorry to say this but you are a very unstable person, you already made another thread some time ago regarding MIUI in the iconia A500 but you did not finish anything and you quit and now the same thing happens again. You only make people get insterested in something and then you abandon the arena. This is very disgusting and rude for people who try to believe in the developers' work . But Moscow Desire gave you another chance but you did not take advantage of this oportunity-.
Godwarrior1 said:
Sorry to say this but you are a very unstable person, you already made another thread some time ago regarding MIUI in the iconia A500 but you did not finish anything and you quit and now the same thing happens again. You only make people get insterested in something and then you abandon the arena. This is very disgusting and rude for people who try to believe in the developers' work . But Moscow Desire gave you another chance but you did not take advantage of this oportunity-.
Click to expand...
Click to collapse
Agree!
Thread Closed
And as such, this thread is closed for eternity. Link will remain for anybody who wants to download it.
MD
Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
@VictoriousShooter
@rr46000
@S0bes
@yajnab
I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)
@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.
for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?
For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.
Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time