Related
Old Thread:
Hi guys,
With this new kernel and a lot of new ideas, isnt better if we try a new port of cyanogen with no motoblur?? Particulary, i prefer that ROM...
I didnt know how to do, but i can test...
There are so many roms for droid 2, like fission, that i want to use in my milestone 2, but see that mike and others try to port but doesnt work. But now, we have new roms and new oportunites...
=)
Is that port possible now (with leaked CHINA rom)?
Click to expand...
Click to collapse
Rom UPDATED!! (02/09): Check on DEV Section using the link below
New Rom Release (28/08):
Hi Guys,
A new CM7 Rom was just released in DEV forum by Endless7 (thanks!)... If anyone (like me!) dont be able to post in DEV forums and need suport for this ROM... PLZ!! USE THIS TREAD....
I´m working now, but I will try this ROM at Night, finger crossed! THIS IS THE WAY
Bye..
jorgebaruchi said:
Hi guys,
With this new kernel and a lot of new ideas, isnt better if we try a new port of cyanogen with no motoblur?? Particulary, i prefer that ROM...
I didnt know how to do, but i can test...
There are so many roms for droid 2, like fission, that i want to use in my milestone 2, but see that mike and others try to port but doesnt work. But now, we have new roms and new oportunites...
=)
Is that port possible now (with leaked CHINA rom)?
Click to expand...
Click to collapse
Well, I'm still learning the basics of android building. As soon as I get my custom hijack for 2nd init working I will try to port CM to the Milestone2. Note that I'm not promising any dates. My free time is very short and I'll do my best, but I don't want to get under pressure because of this
I think a leaked unlocked bootloader would do the trick
Just jocking. As I see it, nothing has changed regarding custom roms, as the bootloaded stays the same.
But I am quite confident, that r2beta0 will have progress on 2nd-init soon.
cypressious said:
I think a leaked unlocked bootloader would do the trick
Just jocking. As I see it, nothing has changed regarding custom roms, as the bootloaded stays the same.
But I am quite confident, that r2beta0 will have progress on 2nd-init soon.
Click to expand...
Click to collapse
filgers crossed!! but i remender that there are some blocks on system booting with froyo rom... then, i thinked that new rom could change this issue... =/
well, thks everybody!
r2beta0 said:
Well, I'm still learning the basics of android building. As soon as I get my custom hijack for 2nd init working I will try to port CM to the Milestone2. Note that I'm not promising any dates. My free time is very short and I'll do my best, but I don't want to get under pressure because of this
Click to expand...
Click to collapse
I think we don't need the 2nd-init built specially for GB rom, since Defy's CM7 (and Droid 2/X's) still have the base SBF on froyo. Maybe if we exchange the boot.img and devtree.img from GB leak to the ones inside Defy's CM7 update.zip (don't forget to delete /system/etc/motorola/bp_nvm_default/pds_init too, or you'll get all that GSM problems again)?
Edit: Won't Apex 2.0 RC2 work on GB Mile2?
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
I think we don't need the 2nd-init built specially for GB rom, since Defy's CM7 (and Droid 2/X's) still have the base SBF on froyo. Maybe if we exchange the boot.img and devtree.img from GB leak to the ones inside Defy's CM7 update.zip (don't forget to delete /system/etc/motorola/bp_nvm_default/pds_init too, or you'll get all that GSM problems again)?
Edit: Won't Apex 2.0 RC2 work on GB Mile2?
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
We need 2nd-init in order to change the boot sequence required by CM7. DroidX already have a customized 2nd-init for CM7, but I don't want to use it yet as it uses bootscripts inside a /system/etc/shadow-boot.zip. I prefer to have my files ready to edit and not inside a zip file. Also, trying to make my own hijack is giving me knowledge I will need when trying to port CM to M2.
r2beta0 said:
We need 2nd-init in order to change the boot sequence required by CM7. DroidX already have a customized 2nd-init for CM7, but I don't want to use it yet as it uses bootscripts inside a /system/etc/shadow-boot.zip. I prefer to have my files ready to edit and not inside a zip file. Also, trying to make my own hijack is giving me knowledge I will need when trying to port CM to M2.
Click to expand...
Click to collapse
Hm... Okay, nice! So we have a better coded 2nd-init.
PS: If you need to unpack a boot.img to get the scripts/zImage, I got it with dsixda's Kitchen
@Milestone 2 (Finnaly on Gingerbread!)
dangpzanco said:
Hm... Okay, nice! So we have a better coded 2nd-init.
PS: If you need to unpack a boot.img to get the scripts/zImage, I got it with dsixda's Kitchen
@Milestone 2 (Finnaly on Gingerbread!)
Click to expand...
Click to collapse
Yeps, I'm using that one too.
Hi guys,
Searching the web, i found a oficial port of MIUI for droid 2, than i think: "Can we port this version with the ch kernel and change the baseband?"
If its possible, i think that this way is more simple, however port a defy rom and fix the incompatible bugs...
=)
jorgebaruchi said:
Hi guys,
Searching the web, i found a oficial port of MIUI for droid 2, than i think: "Can we port this version with the ch kernel and change the baseband?"
If its possible, i think that this way is more simple, however port a defy rom and fix the incompatible bugs...
=)
Click to expand...
Click to collapse
We should check first if this ROM is compatible with the kernels we have available. If so, we can try to port from that. Some ppl into Development forum are already trying to do that.
r2beta0 said:
We should check first if this ROM is compatible with the kernels we have available. If so, we can try to port from that. Some ppl into Development forum are already trying to do that.
Click to expand...
Click to collapse
It is more difficult to port from a CDMA device. If you achieve Apex Rom to work with GSM network, then you can think about porting it.
@Milestone 2 (Finnaly on Gingerbread!)
Hey guys, a new ROM has just released on Dev Forum, click here and see by your self!!!!
One maybe stupid question:
Can I install this rom on froyo or should I first upgrade my MM2 to GB?
There´s what u have to do (didn´t test yeat, I will try at night. But u can always downgrade with a stock SBF):
** Make u sure of your phone is rooted before everything !! **
1. Download all-in-one.zip and put into /sdcard/
2. Download and Install Droid2bootstrapper (old CWM) from the internet/market
3. Update to Ported Defy CWM (there´s a thread in general forum explain how to install that)
4. Boot into CWM and apply the all-in-one.zip and after (without reboot) make a full-wipe (make u sure that u have maked a backup of everything before)
5. At this moment, reboot your phone and use the keys combination for enter in bootloader mode
6. Download the fixed_sbf from the original thread in DEV forum and apply with RSD lite.
7. Your phone will reboot and after some minutes, U Can Enjoy the new ROM!!!
I think I made a big mistake!
I touch everything and I'm going to Defy baseband! I change the parameter.
Since the network can not be found.
Any idea?
i will take a look at this
ping0o said:
I think I made a big mistake!
I touch everything and I'm going to Defy baseband! I change the parameter.
Since the network can not be found.
Any idea?
i will take a look at this
Click to expand...
Click to collapse
Strange..
Try that tread and if dont work, reapply the rom...
Good mod!
But does anybody know how can I get back low battery beep and camera sounds? I find them rather useful.
I got struck in "google" logo and the phone dont boot
how can i do factory reset in bootmenu from the CM7 ? i dont find this option there...
or even re-install all the stuff...
EDIT: i can't open CWM 4.0 from the BootMenu 1.0.2 , i try latest recovery or stable recovery but it says "error in /system/bootmenu/script/recovery.sh (result: no such file or directory)
Please help ! T__T
I can't post in thread on development's subforum, so I ask my question here:
where can I find a tool and howto to make my own custom *.zip file to use with CWM? I have found a tool called Android Kitchen, but readme inside archive says, that it is mainly created for HTC devices. Am I following a correct path , or I should search some other tools?
update:
I have successfully flashed my custom *.zip file based on information taken from www[dot]londatiga[dot]net/it/how-to-create-android-update-zip-package/
coming from miui, how should i update?
Listen, I can read fine and understand instruction.
the phone is rooted but each time I try to install a ROM it gives me a new error, the last one was library cannot found.
I tried about 10 different roms from here, each failed. Either its stuck on boot screen or doesnt let me pass boot menu no matter what.
I guess I got the devils phone.
Any suggestions?
I don't know why your phone is crazy, but maybe flashing the SBF again will help?
auctsbe x651
sack148 said:
I don't know why your phone is crazy, but maybe flashing the SBF again will help?
Click to expand...
Click to collapse
Which SBF? the rom's? I tried, same BS everytime.
I just use this ****ty looking 2.3.6 I just want the phone to look nicer cuz I hate that too-androidish look.
And a nice smooth scrolling in the menu will be nice aswell.
i'm really sorry to ask and i dont mean to offend you but we need a starting point:
- did you try to install zip via stock recovery perhaps
- did you install 2ndinit?
- defy or defy+?
- did you wipe/factory reset before flashong the zip?
- do you maybe have bl7 kernel?
actually, sounds really bad but hopefully there is a way for you!
Please list the exact steps you followed to root and get a recovery and also mention what you did in recovery.. don't worry, we will help you as much as we can
And also list some of the roms you tried flashing..
Sent from my calculator using xda premium
measel said:
i'm really sorry to ask and i dont mean to offend you but we need a starting point:
- did you try to install zip via stock recovery perhaps
- did you install 2ndinit?
- defy or defy+?
- did you wipe/factory reset before flashong the zip?
- do you maybe have bl7 kernel?
actually, sounds really bad but hopefully there is a way for you!
Click to expand...
Click to collapse
Yes
Yes
Defy+
Yes
I have 2.3.6 I'm not sure what BL7 is
I'm not a pro. But first I'd like you to
- install 2ndinit again
- reboot and press Vol-Down when the blue light appears
- use custom recovery do install your preferred custom ROM. (only use the ones for defy+)
you can NOT install custom roms from stock recovery!
measel said:
I'm not a pro. But first I'd like you to
- install 2ndinit again
- reboot and press Vol-Down when the blue light appears
- use custom recovery do install your preferred custom ROM. (only use the ones for defy+)
you can NOT install custom roms from stock recovery!
Click to expand...
Click to collapse
Should I install a specific version of 2ndinit Defy? Can you give me the program, I'm confused what to download.
What do you mean stock recovery?
And another Q: If I was to successfully flash a rom, should I use GB or flash to JB?
stock recovery = shut down > power + vol-down
custom recovery = reboot > vol-down when blue light
no specific 2ndinit. just use the one that is mentioned in FAQ or howto install...
or here: http://forum.xda-developers.com/showthread.php?t=1032212
If you don't know the difference between stock and custom recovery you might want to start reading here: http://forum.xda-developers.com/showthread.php?t=1216982
...and might want to rethink your first sentence:
Hesanka said:
Listen, I can read fine and understand instruction.
Click to expand...
Click to collapse
measel said:
stock recovery = shut down > power + vol-down
custom recovery = reboot > vol-down when blue light
no specific 2ndinit. just use the one that is mentioned in FAQ or howto install...
or here: http://forum.xda-developers.com/showthread.php?t=1032212
Click to expand...
Click to collapse
I have a few more Q:
Do I need to upgrade my phone to 4.1.2 before flashing a ROM that is 4.1.2 or will that be the upgrade?
Which ROM do you suggest for me use because I am not very decisive about it.
What do I need to do for this ROM to work for me? http://forum.xda-developers.com/showthread.php?t=1033654
I have GB 3.2.6 rooted with DFP 231
1. no. there is no official 4.1.2 for defy.
2. i would recommend cm7.
use a version that is for the defyplus and you dont have anything to prepare more than you will find in the howto's.
check this thread for cm7 builds: http://forum.xda-developers.com/showthread.php?t=1458729
CM7 nightlys | info collection [update: 12-12-07 Maniac] + PDroid
and please give some feedback what helped and what was the problem.
measel said:
1. no. there is no official 4.1.2 for defy.
2. i would recommend cm7.
use a version that is for the defyplus and you dont have anything to prepare more than you will find in the howto's.
check this thread for cm7 builds: http://forum.xda-developers.com/showthread.php?t=1458729
CM7 nightlys | info collection [update: 12-12-07 Maniac] + PDroid
and please give some feedback what helped and what was the problem.
Click to expand...
Click to collapse
Ok, tried to do this guide http://forum.xda-developers.com/showthread.php?t=1054447
with CM7 nightlys and my phone is stuck after rebooting on the stupid motorola boot sign
I'm gonna have to flash with RSD again. why does motorola has to make stupid devices EACH YEAR?!
You need to get some things STRAIGHT.
Hesanka said:
Ok, tried to do this guide http://forum.xda-developers.com/showthread.php?t=1054447
with CM7 nightlys and my phone is stuck after rebooting on the stupid motorola boot sign
I'm gonna have to flash with RSD again. why does motorola has to make stupid devices EACH YEAR?!
Click to expand...
Click to collapse
Listen to this. It is not Motorola's fault that you have soft bricked your device. It is entirely your fault. Hundreds of other guys have successfully flashed their device with the ROM of their choice and are having no problems. Maybe you should read threads before trying to flash ROMs. If you do not know the basics of rooting and modding android, you should not attempt to do it. And if you have flashed your device without doing the neccessary homework, please do not expect help from the community. Please educate yourself to the required level before attempting to do such things. There are several well written and comprehensive guides and tutorials on the cyanogen wiki as well as here on xda which can answer all your questions for sure. For your own sake, please read them. Your posts in this thread highlight your severe lack of rudimentary knowledge about android. I'm not saying that's a bad thing, because everyone was like that at some point. BUT, we read and we read and if we didn't understand, we read some more!
Please understand that this is a community where we cannot help you if you do not help yourself. I'm sorry to to tell you this, but you are being a jerk by criticising Moto and whining that things aren't working when it is you who has done things in the incorrect manner. So stop being a n00b, stop whining, go read some threads ( ALL THE STICKY ONES, MINIMUM ! AS WELL AS THE ONES ON THE CYANOGENMOD WIKI ! ) and educate yourself. Just because your friend has modded his device does not mean that you can too.It requires a certain level of expertise which can be easily gained, provided that you are ready to be an eager learner. Remember this, TO GET GOOD REPLIES, YOU HAVE TO ASK GOOD QUESTIONS.
Get rid of the attitude, --- learn the basics --- and then come back. If you are still having a genuine problem, then we will help you.
PS: You mentioned that you are going to flash using RSD lite. PLEASE flash the appropriate SBF file. If you flash the wrong SBF, it can lead to some serious problems. Choose wisely. And if you make ****s in that too, please do not start a new thread, refer to the pre-existing help threads. Good luck.
And please do not ask for the links to the above mentioned threads, use the search function and your common sense.
viki1296 said:
Listen to this. It is not Motorola's fault that you have soft bricked your device. It is entirely your fault. Hundreds of other guys have successfully flashed their device with the ROM of their choice and are having no problems. Maybe you should read threads before trying to flash ROMs. If you do not know the basics of rooting and modding android, you should not attempt to do it. And if you have flashed your device without doing the neccessary homework, please do not expect help from the community. Please educate yourself to the required level before attempting to do such things. There are several well written and comprehensive guides and tutorials on the cyanogen wiki as well as here on xda which can answer all your questions for sure. For your own sake, please read them. Your posts in this thread highlight your severe lack of rudimentary knowledge about android. I'm not saying that's a bad thing, because everyone was like that at some point. BUT, we read and we read and if we didn't understand, we read some more!
Please understand that this is a community where we cannot help you if you do not help yourself. I'm sorry to to tell you this, but you are being a jerk by criticising Moto and whining that things aren't working when it is you who has done things in the incorrect manner. So stop being a n00b, stop whining, go read some threads ( ALL THE STICKY ONES, MINIMUM ! AS WELL AS THE ONES ON THE CYANOGENMOD WIKI ! ) and educate yourself. Just because your friend has modded his device does not mean that you can too.It requires a certain level of expertise which can be easily gained, provided that you are ready to be an eager learner. Remember this, TO GET GOOD REPLIES, YOU HAVE TO ASK GOOD QUESTIONS.
Get rid of the attitude, --- learn the basics --- and then come back. If you are still having a genuine problem, then we will help you.
PS: You mentioned that you are going to flash using RSD lite. PLEASE flash the appropriate SBF file. If you flash the wrong SBF, it can lead to some serious problems. Choose wisely. And if you make ****s in that too, please do not start a new thread, refer to the pre-existing help threads. Good luck.
And please do not ask for the links to the above mentioned threads, use the search function and your common sense.
Click to expand...
Click to collapse
I've read well over 30 topics here ENTIRELY and none helped, I've done everything according to the guides, simply when I start to boot my device after a ROM flashing it has a new problem, I just gave up on motorola, tomorrow I'm going to return this piece of rubbish and get myself a SGS2 Because I've had enough of Motorola.
Thanks and no thanks to all, I've had enough of this rubbish.
good luck with your new device.
Well then..
Hesanka said:
I've read well over 30 topics here ENTIRELY and none helped, I've done everything according to the guides, simply when I start to boot my device after a ROM flashing it has a new problem, I just gave up on motorola, tomorrow I'm going to return this piece of rubbish and get myself a SGS2 Because I've had enough of Motorola.
Thanks and no thanks to all, I've had enough of this rubbish.
Click to expand...
Click to collapse
Okay, wish you better luck with your SGS2, try harder with it.. And please don't call the Defy a piece of rubbish because it is a lovely phone, infact I don't know any other device which can boot custom kernels on a locked bootloader :laugh:
And if you manage to brick the SGS2 also, perhaps it's best that you get an iPhone next time.
Hi! Im trying to install the new CM11 dev builds for the Galaxy Y and I keep getting:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-11-2014-05-28-EXPERIMENTAL-totoro.zip
(Status 7)
Installation aborted.
Any ideas. I'm installing it upon the CM9 build re recently got and upon that kernel.
its recovery issue.
How can I fix it then? I guess that much. :L
sorry but i have no permission to share something.
So, can I or cant I fix it...
Boncey said:
So, can I or cant I fix it...
Click to expand...
Click to collapse
you need to use the correct cwm recovery v6.x
for that you need the new kernel
But I dont know why you want to - its for devs only - its experimental - has a high risk of bricking your phone - and nothing on cm11 works yet other than it boots
If you are a dev and want to develop all the details are on the cm11 thread in the dev section but I repeat - unless you are a dev please dont not post there or flash anything on your device
marcussmith2626 said:
you need to use the correct cwm recovery v6.x
for that you need the new kernel
But I dont know why you want to - its for devs only - its experimental - has a high risk of bricking your phone - and nothing on cm11 works yet other than it boots
If you are a dev and want to develop all the details are on the cm11 thread in the dev section but I repeat - unless you are a dev please dont not post there or flash anything on your device
Click to expand...
Click to collapse
Thanks and yes I know. I like to try out the newest things, I'm not in any major need of my phone for a while so I can do whateva.
Could you link me to the new CWM Recov. and the Kernel?
Unfortunately the devs are not in favour of releasing these things as yet. -CALIBAN666- and marcussmith2626 had put up links and attachments for the files but have since taken them down at bieltv.3's request.
Try and understand, they as devs do not want to hard brick your phone with their work.
Until we get a beta, don't even try.
Boncey said:
Thanks and yes I know. I like to try out the newest things, I'm not in any major need of my phone for a while so I can do whateva.
Could you link me to the new CWM Recov. and the Kernel?
Click to expand...
Click to collapse
their website is
http://androidarmv6.github.io/
Its a public website that is freely available via a google search so there is no permission required to post a link to it
Since it contains no advertising or is used for commercial profit to make money from xda users me posting it here does not violate xda rules
Where you go from there is entirely your choice
I can give ABSOLUTLEY no gurantee!! All you do with your phone will be on your own. I'm not responsible if your phone will brick or whatever...
Attation! This kernel is for the I8200 variant ONLY... the I8190 is absolutley not compatible !!!
Kernel should be work also for I8200/I8200Q/I8200L-Variants, but can not be gurateed as the basis was I8200! If it works then a notice will be fine!
If you are not sure about the process, the data are important on your phone or you need it as a daily phone, then LET IT BEE, and wait for the messages that it is safe to use. Its important at the beginning that users with knowledge tried it at first !
Changelog:
12.02.2016: Long time ago, but now after a lot of investigating some new things comes up. Check what was done
05.01.2014: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was. not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more main.tained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possibility to include also selinux what is needed for a kitkat-rom. Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to get a contact...
Baroni-V0.1 contains:
Basis of opensource from Samsung with some bugfixing
fixed recovery-boot-loop with a config-setting which must be used special in the Recovery zImage
Loglevel pushed down to minimum
Uber-Toolchain 4.9
set onDemand-Governor to standart. just to check how that works
start implementing SmartAssV2-Gonernor, but leave it inactive, due to some compile-errors.
bringing SELinux to work for future kernel releases if needed for > 4.4
Planned:
new govenors at the moment not established (will come later)
more other stuff (depending on learning-curve
Installation:
Install a recovery for safetyreasons (I prefer TWRP https://www.dropbox.com/s/d3rnfp3vabz9ee8/twrp_i8200_corrected.7z?dl=0
Read carefully the hints of the usage in the following firts post: http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565 (There also the needed Odin (3.09) can be get)
Make backups of the complete phone, and be sure that you know what you do!
Download the right Firmware for your phone from http://www.sammobile.com/firmwares/ (just to have a other safety fallback in your hand!)
Download the file, start odin as usual (all kies-tasks closed!)
extract the file, and put it to AP
put the phone in Downloadmode (Vol-down,Home-key and powerbutton), and connect the phone with PC
flash the kernel, and let the phone reboot
pray
If things go wrong, please give everytime the following information's:
what you did before
what exactly happened (its not easy to help if you say: it did not work )
which rom in which version, which recovery and which version of my Kernel you use
try to get a /proc/last_kmsg (if a unknowen reboot appears) and/or Logcat, Build prop, CPU info, Sysctl, Kmsg, Dmesg and send it to me (or as a attachment to the post) for further analyse (you can use that tool for it: https://play.google.com/store/apps/details?id=com.bassel.andylog )
Attention: First checks seem to be that I8200 (without N or L or Q) did not work atm.
Download:
kernel_i8200n-Baroni:
https://www.androidfilehost.com/?w=files&flid=47763
kernel_i8200n-Stock.7z (to getting back to stock kernel via Odin):
https://www.dropbox.com/s/xfhufcpxl5kxmue/kernel_i8200n-Stock.7z?dl=0
Recoverys (with fixed recovery boot loop):
https://www.androidfilehost.com/?w=files&flid=49834
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
One question.
SolarPlexus said:
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
Click to expand...
Click to collapse
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Danh23 said:
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Click to expand...
Click to collapse
Attention with TWRP-Recovery. Data-Partition restore seems to be not right. At the moment please did not use it, because it can delete your data-partition. We have to investigate it further! Other partitions seems to be ok, but its a good Idea if you copy your important data also manually to a other storage (like PC) while you trying things of this thread.
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
KwstPap said:
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
Click to expand...
Click to collapse
Did you made a backup with twrp (as described)? If yes, then make a restore only with boot marked in the list.
Otherwise, which version did you have? Plain n/l/q? Than I can make a package for Odin...
send with my Oneplus One (bacon) SlimKat Tapatalk
About the data recovery, use aroma FM to restore. Out worked for me
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
KwstPap said:
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
Click to expand...
Click to collapse
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
hahahahaha always forget to take a backup .but i am very stypid .i had a backup on my pc.hahah in one weak i have reflashing the stock formware 5 times and the root recovery and other staff again hahaha
thanks for the stok kernel
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
¿which brings benefits to install this kernel?
RodsonBorja said:
¿which brings benefits to install this kernel?
Click to expand...
Click to collapse
Atm nothing... Its alpha and not working. Unfortunately I'm a little bit blocked by illness and x-mas and was not able to work on it... Maybe next week...
send with my Oneplus One (bacon) SlimKat Tapatalk
Hi to all followers of this thread.
Just to give an update: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more maintained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possebility to include also selinux what is needed for a kitkat-rom...
Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to invite him/her. To ask in forums (also in xda) is something what I do, but unfortunately the responding are not every time safe...
So I wish you all a happy new year, and lets work together to bring our device a little bit forward
SolarPlexus
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
VallNAr said:
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
Click to expand...
Click to collapse
Ask MARDON he made the kernel for Galaxy Ace - maybe he support Your work.
Any progress on the kernel? Is it on github?
Why does this not suport usb flash drives or can the function be ported
Gershy353
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
SolarPlexus said:
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
Click to expand...
Click to collapse
How is this done i have the sandisk dual flash drive but its useless on my device
Gershy353
Ah, you mean otg support, not sdcard seen as USB instead of mtp?
send with my Oneplus One (bacon) SlimKat Tapatalk
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
What have you done? Device tree something else?
Nope. Just changing libs here and there, according to this guide. I'm still noob in porting roms so I can't do much.
amirarsyad97 said:
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
Click to expand...
Click to collapse
Did you edit the updater script?
Gibz97 said:
Did you edit the updater script?
Click to expand...
Click to collapse
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
If you have an idea for kernel, I'll help you
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
Let's wait for the response then
Would be graet to see CM to release this device's potential. Especially since HTC is taking it's sweet time with 6.0 update and 5.1 was officially skipped.
Anyway if you would need some testers I would gladly help.
Good news! The permission has been granted. I will try my best to port this rom.
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
We don't have 64-bit kernel sources for 820n MSM chipset
Hi @amirarsyad97, so did you manage to extract system files?
Gibz97 said:
Hi @amirarsyad97, so did you manage to extract system files?
Click to expand...
Click to collapse
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
amirarsyad97 said:
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
Click to expand...
Click to collapse
I will try porting the kernel using the kitkat kernel as base when I find time
Unfortunately, I did not succeed, I could not even get into the bootanimation. Hope someone can help us.
I am now trying to squeeze the Lollipop system partition so that we can liberate some more free space for the internal storage, hope it works
That would be the coolest thing???
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Gibz97 said:
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Click to expand...
Click to collapse
I was wondering how you can make the kernel work. Anyway good work!
amirarsyad97 said:
I was wondering how you can make the kernel work. Anyway good work!
Click to expand...
Click to collapse
Use this kernel and build.prop and use the original system (don't replace with stock files) https://mega.nz/#!c4USzSTL!rXmsjMYaxR9ECwNeiMjissLPuFRLBWBUSLIuwiBFwQk
Almost everything works right now except Bluetooth, camera and Sim
Great work keep it up
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app