I am looking for someone who owns the korean version of the LTE 8.9. My internet searches havent found anything, but I believe the device has been upgraded to ICS. If we can find someone with the device and who has updated, then we can build a working US version from it. If anyone can find the firmware online that also works.
Info: http://www.samsung.com/sec/consumer/mobile-phone/mobile-phone/skt/SHV-E140SZW3SC-support
Source: http://www.samsung.com/sec/ics/06_shv-e140s_ics_kies.html
I've been looking for that very thing since I posted in the official ics thread earlier. No luck so far...
orlandoxpolice said:
I am looking for someone who owns the korean version of the LTE 8.9. My internet searches havent found anything, but I believe the device has been upgraded to ICS. If we can find someone with the device and who has updated, then we can build a working US version from it. If anyone can find the firmware online that also works.
Info: http://www.samsung.com/sec/consumer/mobile-phone/mobile-phone/skt/SHV-E140SZW3SC-support
Source: http://www.samsung.com/sec/ics/06_shv-e140s_ics_kies.html
Click to expand...
Click to collapse
i looked everywhere .. chinese site even korean site ... cant find the rom
or maybe we should get someone who read korean to check out the korean site and see when is the update actually out.....
i believe it says ics is coming ... but when
It appears the source for the SHV-E140S is now posted on opensource.samsung.com.
This is new in the last few days, I checked earlier in the week and it wasn't there... Yay!
there are 3 seperate versions... I'm downloading all of them ATM and see what is in there...
link: just scroll down until u see the device name. : http://opensource.samsung.com/reception/receptionSub.do?method=list&menu_item=mobile&classification1=mobile_phone
also there are 4 different files but only one is ICS update
I opened the ICS update and there are a few interesting things... but I don't know if the internals are identical to 8.9 so we could just copy the drivers over...
nvm, saw OP's signature. This one is based on Qualcomm, different from P7300/P7310.
The platform stuff from the opensource site is probably mostly useless, as it's going to be an asian version of android that likely doesn't have english support. Correct me if I'm wrong.. It's probably best to use the kernel to bring up CM9 on this device.
The kernel does have config selections for the I957, and it successfully builds with this option, unlike the I717 and I727 releases -- They both had the 957 option in the kernel config, but didn't include most the actual code bits to allow it to build for that device, and the bits it did include didn't compile, all sorts of compile errors as if it hadn't been QA'ed at all...
Also.. I found the binary package, for the SHV-E140S, hosted on xbigfile.naver.com at some torrent page: w3ww.matpclub.com/b/torrent/119077
http://xbigfile.naver.com/bigfileup...jK6MrFoCop6kvaxb9MxbZaxkoFqM9axi4Mo+4F6EwK6E=
Let me know if you need me to mirror this...
The SHV-140 and SGH-I957 are very similar.. If you look at the ifdefs in the kernel source code (CONFIG_KOR_MODEL_SHV_E140S vs CONFIG_USA_MODEL_SGH_I957) the only difference I could find is in the DSP module -- Includes wrapped in ifdef tags select arch/arm/mach-msm/qdsp6v2/timpani_profile_p5lte_att.h vs arch/arm/mach-msm/qdsp6v2/timpani_profile_p5lte_skt.h. These are the DSP codecs. These files contain several hundred KB of what appears to be binary code in hex for the DSP engine, and are extensively different. From what's there, it looks like most of it relates to handling audio streams at various bitrates, including mic, line in, headphone sources. It appears the DSP engines in these devices are pretty different?
So, the binary kernel for the SHV-140 isn't going to work well with the I957, even if only because of the DSP changes. This isn't too surprising.
I think the next step is to investigate getting the kernel into the CM9 build tree. Anyone a ninja with that sort of thing?
nrvate said:
The platform stuff from the opensource site is probably mostly useless...
The SHV-140 and SGH-I957 are very similar.. If you look at the ifdefs in the kernel source code ...
So, the binary kernel for the SHV-140 isn't going to work well with the I957, even if only because of the DSP changes. This isn't too surprising.
I think the next step is to investigate getting the kernel into the CM9 build tree. Anyone a ninja with that sort of thing?
Click to expand...
Click to collapse
Funny enough... I ran the above through Google Translate and it came out just the same! :silly:
Whatever you and/or the other brilliant devs can come up with as a path forward will I'm sure be farther along than it is now. Just let us tinkerers know what we can do to help. :highfive:
https://github.com/CyanogenMod/android_device_samsung_p5att
Looks like someone is starting a device tree for the P5 ATT version!
Jellybean branch too, looks like CM10. That'd sure be pretty awesome.
Already posted. Nevermind.
http://story537.tistory.com/category/갤럭시 시리즈 펌웨어/갤럭시탭 8.9 LTE
check out this site
i am not sure this is what we all are looking for
maybe it is ... maybe not ... cuz its in korean... and i dont understand it
madsatan said:
http://story537.tistory.com/category/갤럭시 시리즈 펌웨어/갤럭시탭 8.9 LTE
check out this site
i am not sure this is what we all are looking for
maybe it is ... maybe not ... cuz its in korean... and i dont understand it
Click to expand...
Click to collapse
It's the ICS firmware for the SHV-E140S (SKT).
Someone flashed it and cant get past the samsung logo.
Hopefully, the Dev. will look at it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lookin for ICS firmware
I cant update via Kies also FOTA,when it enter download mode,the tab is disconnect with PC!
Shv e140s JB download links in regular dev section. Need to grab links before mod edit/ closes.
Edit: ics not jb. Got excited for sec
see a ICS rom for E140S at : http://forum.xda-developers.com/showthread.php?t=1943435
e140K
Yes I own a e140 but it's e140k. Still looking for the Stock ROM for ICS.
Got it
I have the stock firmware for SHV-E140K when it upgraded the firmware. It is HOME_SHV-E140K.UK22.1901_CL1174059_REV01_user_low_ship.tar.md5.
Can anyone do something with it? I will upload it to any site people prefer.
Hello, I'm a student from China, Tablet PC Samsung SHV-E140L Brush failed, and now can not boot, I need SHV-E140L BOOT.BIN file.This used to JTAG repair.Pro help me.Please send to 635854900 @ qq com. Thank you
Related
Roms based on froyo or gingerbread?
The discussion in the thread "30/Jun r1 (JFB) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen" is a bit confusing so I thought it best to make it a new topic to get it straight.
Will it be possible to make roms based on froyo, gingerbread or any other coming android version, before Samsung makes an update? As I understand psychoace it will be ”near impossible to get roms from other sources like Sense roms or Froyo”. Others are not so sure.
This is important as Samsung is known for its lack of interest in OS updates. Who knows if they will take gingerbread to GS? If they won't can it be done by the really smart guys?
I don't think even HTC will update there top line to V3 (ginger bread). Froyo is coming any way to GS in near future. Now ginger bread should be possible too as GS is power full enough to run. When? we should wait and see. Nexus just got updated to 2.2.
Will see how things go in future.
Samsung has released there kernel sources and there software sources. I haven't had a chance to look in to it deeply but if it has the code of the drivers etc.. it should be possible to merge (with some work obviously) sources and to compile froyo.
kimatrix said:
Samsung has released there kernel sources and there software sources. I haven't had a chance to look in to it deeply but if it has the code of the drivers etc.. it should be possible to merge (with some work obviously) sources and to compile froyo.
Click to expand...
Click to collapse
But don't those drivers only work with 2.1 and just simply won't with any version higher unless samsung releases new source and drivers for 2.2 and then 3.0. So if say samsung never releases anything any source/drivers that work with 3.0 then you would be out of luck to actually get everything to work.
MrDSL said:
But don't those drivers only work with 2.1 and just simply won't with any version higher unless samsung releases new source and drivers for 2.2 and then 3.0. So if say samsung never releases anything any source/drivers that work with 3.0 then you would be out of luck to actually get everything to work.
Click to expand...
Click to collapse
That is true but if you have the full sources you are able to look what the differences are and maybe patch those by your self. Assume a wlan driver is using an function that has changed or is gone in 2.2, then you can try to patch that by finding the new one for it to work with. If you don't have the sources it's much harder to do those kind of things.
As I sad you have the sources so you can play by your self even if samsung does not do anything. It does not mean it's easy and it does not mean it can be done fast. But it does mean it could be done.
kimatrix said:
That is true but if you have the full sources you are able to look what the differences are and maybe patch those by your self. Assume a wlan driver is using an function that has changed or is gone in 2.2, then you can try to patch that by finding the new one for it to work with. If you don't have the sources it's much harder to do those kind of things.
As I sad you have the sources so you can play by your self even if samsung does not do anything. It does not mean it's easy and it does not mean it can be done fast. But it does mean it could be done.
Click to expand...
Click to collapse
But the video drivers are already compiled. Can they be easily decompiled? It's not a source file if it's already compiled.
psychoace said:
But the video drivers are already compiled. Can they be easily decompiled? It's not a source file if it's already compiled.
Click to expand...
Click to collapse
Can they be decompiled and made to work? Of course!
Will someone be motivated to do all this work? Unknown.
Besides drivers arent the only issue to getting a new version of Android on a phone. If you dont have source for any proprietary userland daemons/apps (like radio?) that communicate with the hardware you will be SOL on that as well.
MMMMMMMMM if we can do it for the G1 we can do it SGS...the question is when and how much work. The Galaxy S will be Samsung's flagship device for A YEAR so I'd hope to get Gingerbread...unless Samsung are really stupid. Especially with a lot of US launches, they'll be able to relaunch with Gingerbread as it comes is my hope.
psychoace said:
But the video drivers are already compiled. Can they be easily decompiled? It's not a source file if it's already compiled.
Click to expand...
Click to collapse
Who told you that??? The source code of the GPU as well as every other coprocessor is there.
The two .o file that started this all fiasco are ok and you as long as the make file include them in the build they would work perfectly.
All they have inside is a simple elf code to tell the s3c*** to do whatever it needs to do. A source code wouldn't have been beneficial as it would have to be compiled differently for a different ARM instruction set .
kitsune223 said:
Who told you that??? The source code of the GPU as well as every other coprocessor is there.
The two .o file that started this all fiasco are ok and you as long as the make file include them in the build they would work perfectly.
All they have inside is a simple elf code to tell the s3c*** to do whatever it needs to do. A source code wouldn't have been beneficial as it would have to be compiled differently for a different ARM instruction set .
Click to expand...
Click to collapse
But when you need drivers for 2.2 the source code would be optimal because these drivers are not going to work without some hacking.
They are going to work as they are non kernel bound ELF files.
Guys this isn't a driver ,if it was a kernel module ( or "driver" s you call it) it would have been a .ko file and had a slightly different structure ( use readelf on a kernel module and then on this to see the difference). So no matter what it is when can use the compiled version as it not kernel bound
From quick inspection it seems like the injection code for the s3c*** . so basically its there so the kernel could reference to it when the code tells it to do so . So Basicly all we have to do is put it in the proper place when building the kerne.
So please DON'T PANIC
well the TP2 just got 2.2 FroYo (2.1 has more working drivers ATM).. but if we have it, how would it be different for the SGS to get FroYo?
You need to remember that while other companies can update kernel quite easily ( all the work is done for them by the chip manufacturer and some member of the community ) this isn't possible here as this is a chip only used in one android/other linux platform device and the company making the device also make the chip.
So give them a few weeks to work on it
J-Hop2o6 said:
well the TP2 just got 2.2 FroYo (2.1 has more working drivers ATM).. but if we have it, how would it be different for the SGS to get FroYo?
Click to expand...
Click to collapse
let's just say it will be the first time a non Samsung Rom has worked on a Samsung Android phone.
psychoace said:
let's just say it will be the first time a non Samsung Rom has worked on a Samsung Android phone.
Click to expand...
Click to collapse
Not true.
Look here: http://forum.samdroid.net/f28/lkmod-v-2-5-1-based-jce-en-upd-03-30-a-336/
I see a custom ROM made for the i5700
Everything is possible.
clubtech said:
Not true.
Look here: http://forum.samdroid.net/f28/lkmod-v-2-5-1-based-jce-en-upd-03-30-a-336/
I see a custom ROM made for the i5700
Everything is possible.
Click to expand...
Click to collapse
Did I say custom rom? No i said specifically non samsung based roms on a samsung device. That custom rom is based off of a Samsung rom.
This is the closest we have got to a Hero rom on a Samsung device.
http://androidforums.com/all-things-root-behold-2/60408-port-htc-hero-behold-2-wip.html
He couldn't get Rosie to boot so who knows what other problems he would of had after that (from the picture you can see he never got any network connection)
So there don't say I didn't give you any hope.
Froyo is offical. That's good, but we need to be looking past it to Gingerbread.
Froyo is announcedm confirmed, and now dated for the end of September, and that's great. But to me, that's not the question we need to be asking Samsung anymore, we need to be thinking past that.
The question people need to be asking Samsung, so we can get them on the record committed to it now, is will you release a Gingerbread update for the phone as long as the hardware is capable of supporting it. The OS is only 2-3 months from being unveiled if Google sticks to their time table, and if the rumors are true it'll be a much bigger overhaul than 2.1-2.2 is.
So unless we want our phones to be outdated before the end of the year, we need to start making a push as a community to get a commitment from Samsung to support not just the OS that was released 4 months ago, but also the much bigger one that's right around the corner.
2.2 is good.. proves everyone wrong who said "ooh its Samsung, of course they won't release Froyo."
but somehow, I doubt that samsung will somehow not upgrade SGS to 3.0. If they do, it might be a few months (at least) after everyone else gets it. The reason is, they could have new flagship devices out that they wanna push to the mass-markets, so putting gingerbread on that will boost the sales.
However, considering that they marketed the SGS so well, and have it well on its way, they might just put gingerbread on it
seriously, i see ads for SGS EVERYWHERE online.
mjgunn said:
[....]
So unless we want our phones to be outdated before the end of the year
[....]
Click to expand...
Click to collapse
I totally expect that my phone will be outdated by then. That's a consequence of the world we live in But then again, i'm a nihilist
As I make progress towards making us an overclocked kernel I will keep m380w users informed in this thread. Wish me luck!
June 16, 2012 Had to post an updated torrent file.
May 01, 2012 New Firmware Released (NOT ICS)
Attached is a torrent file for FD19
Dec. 08, 2011 Development Halted
Here's the latest. The source code that Samsung makes available seems to have issues. I have tried and tried again to reproduce a stock kernel that will boot with the initramfs. However, the defconfig provided does not match the .config extracted from config.gz. There are some big differences between the two. The defconfig supplied with the source code defines the board as p4 yet the .config from the kernel defines it as p4wifi. So naturally I have tried both and I have tried many, many other things. All for not.
I contacted FOSS and the response was to the tune of, "We sent your message to the dev. team. If they respond, we'll respond. Until then, just wait."
With that said, I see no reason to muck about with trying to make an overclocked kernel, when there is no indication that I have valid source code.
Nov. 24, 2011
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
SHW-M380W.EK10.7z
Rooting directions and files I have tested and do work with this release can be found here on XDA
Nov. 26, 2011
I made some progress and have extracted the initramfs from the EK10 kernel using koush's AnyKernel. See attachments. One step closer to an overclocked kernel.
Pershoot has graciously offered his time and resources and built a recovery cwm_5.0.2.7_kor for the m380w. Which now displays correctly on this device.
He included the following notes:
UMS is not implemented (so the option will not work).
no radio/extra partitions will be available.
Click to expand...
Click to collapse
koe1974 said:
As there are only a few of us in here and nobody in Korea seems to be developing this model, I took it upon myself to retain this ROM from my most recent bout with Kies.
Here is a stock ROM of EK10, released 11/23/2011 for those who need or want it.
HOME_SHW-M380W.EK10.1207_CL583812_REV00_user_ship.tar.md5
Rooting directions and files I have tested and do work with this release can be found here on XDA
I hope to offer an overclocked kernel in the near future but we'll have to see.
Click to expand...
Click to collapse
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
BeeGee_Tokyo said:
Can you give a few more details?
Is it HoneyComb 3.2?
Is it for WiFi or 3G tablets?
Click to expand...
Click to collapse
It is Honeycomb 3.2. The shw-m380w is a wifi model.
Sent from my SHW-M380W using xda premium
One of the most noticeable difference is the integrated digital dmb tv and radio receiver and antenna. With no change in the look and dimensions. It comes wifi with or without 3g.
koe1974 said:
Nov. 26, 2011
Pershoot has graciously offered his time and resources and built recovery-cwm_5.0.2.7-sam-tab-10.1_kor_odin.tar.zip
He included the following notes:
Click to expand...
Click to collapse
refreshed:
http://droidbasement.com/db-blog/?p=2439
pershoot said:
refreshed:
http://droidbasement.com/db-blog/?p=2439
Click to expand...
Click to collapse
Excellent! Just completed a backup and all worked as expected.
Thanks
Sent from my SHW-M380W using xda premium
Thank you so much pershoot and Koe1974. Now, CWM can operate normally with my device. Actually, my device model is shw-m380s with 3g and I would like to ask you is it able to upgrade by CWM with the custom roms of P7500 (as overcome rom) and the overclock kernel?
Hi pershoot. I've just made a backup for my kor tab (model shw-m380s). Please help me to check the boot.img attached and let me know my device is able to apply your kernel or not. Thank you in advance.
Your device is not compatible with my kernel.
pershoot said:
Your device is not compatible with my kernel.
Click to expand...
Click to collapse
Thank for your reply Pershoot. Yesterday, I tried to patch your kernel and my tab couldn't boot, so I had to back to its stock kernel. I also upgraded my tab to Overcome Rom with stock kernel and it works fine exclude one issue is the brightness level couldn't adjust anymore. Because I am not good at hex and linux coding, so I appreciate if you or other developers could help me (and people own this device) to fix my stock kernel to make it is suitable with CWM roms and able to be overclocked. Thanks alot in advance.
Just to share some of my experience, I have an M380W model, I installed pershoot's CWM-based recovery, backed up everything, and installed Galaxy Task 6.2 ROM for a try (and 6.3 update). The screen keeps scrolling, but this is solved by restoring boot.img within the recovery.
I then have the same symptom as phuonglev, the screen brightness level can't be adjusted (set to medium and looks so), and I sometimes have orientation problems.
Could all this be resolved with your specific kernel koe1974 ?
I don't imagine it will. All I am planning at this point is to enable overclocking. It will essentially be a stock kernel. It sounds as if it is something in the rom causing the problem. As much as we would like to think the korean models are the same, from past experience with a galaxy s 'shw-m110s vs gt-i9000', the roms are just not interchangable. It always seems that there is 'something' that does not work as it should.
Sent from my SHW-M380W using xda premium
How is your progress Koe? I'm waiting for the good new from you.
Awesome, can't wait to see some progress.
I thought I was the only one with problems trying to use tasks rom.
Just FYI for any other M380W owners out there, you can supercharge your tab. Made a big difference for me.
*Edit
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
aigoya said:
Btw Koe,
There is a small update for the M380W 10mb file from software update. After it downloads and reboots it's telling me that it failed to install. Any advice on how to get past this? (I'm rooted and supercharged).
Click to expand...
Click to collapse
If you are on EK10 then it is probably the update for Polaris Office. However, if you are not running the stock rom, your device may be reporting that is an p7500 or p7510 which I think comes with QuickOffice. So it might be confused.
Sent from my SHW-M380W using xda premium
could you upload the rom to other source please?
samoelito said:
could you upload the rom to other source please?
Click to expand...
Click to collapse
This is the best I can do ( http://www.wupload.com/file/2662167342/SHW-M380W.EK10.7z ). If you prefer bit torrent, let me know.
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
[email protected] said:
So, just to confirm.
If I want to root my device (I just picked it up yesterday) I need to download the
Samsung_Galaxy_Tab_10.1_root.zip file, then follow the instructions for apply the zip through recovery mode.
So what is the ek10.7z do? I understand it is a stock ROM....is it just for back up or why would it be needed? I guess I am just asking what is special about it
Then, who do you flash a ROM with this one?
I am familiar with the Korean ROMs and kernels. I have the m110s and have received so much help from Koe before Thanks for that.
I have taken over the old thread and have been trying to fill your shoes! hahhaa
Click to expand...
Click to collapse
To root just follow the instructions and you will be fine.
ek10.7z is just the stock rom for if you choose to revert from back. currently, there doesn't seem to be much development going on for the m380w so I uploaded it for those brave enought to try roms built for other 10.1 models. I always delete tons of stock apps so it's helpful to have a stock rom to get back it i need to.
is flashing ROMS still the same?
Just using Odin and put the file into the PDA slot?
Hi !
I'm really curious about why I can't use ROM for the 10.1 version on 8.9 version of Galaxy Tab.
Except the panel size (10.1 vs 8.9) and battery capacity, there are other hardware differences ?
Any ideas ?
Thanks.
You /can/ use 10.1 ROMs. The 8.9 and 10.1 are virtually identical.
You just need to swap out boot.img and recovery.img AFAIK. And edit build.prop.
Hurrian said:
You /can/ use 10.1 ROMs. The 8.9 and 10.1 are virtually identical.
You just need to swap out boot.img and recovery.img AFAIK. And edit build.prop.
Click to expand...
Click to collapse
can you point me to the right track
what i need to edit the build.prop?
Here, courtesy of alterbridge86.
BTW, Overcome 2.0.0 is a P75xx ROM ported to P73xx, if you'd want to start on that.
http://forum.xda-developers.com/showpost.php?p=18872241&postcount=48
Thinking about the same thing.There is much less rom on the 73xx section, . Is anyone here would like to give more detail on these?
Hurrian said:
Here, courtesy of alterbridge86.
BTW, Overcome 2.0.0 is a P75xx ROM ported to P73xx, if you'd want to start on that.
http://forum.xda-developers.com/showpost.php?p=18872241&postcount=48
Click to expand...
Click to collapse
thanks, will start to learn on this
I hope good theme'rs get the 8.9 soon. I wish i had the talent to do it
Actually, I don't think it's as simple as that post from alterbridge - that was quite early on in his experimentations with Overcome on the 8.9. I recall from the subsequent release of Overcome that he said that there were other considerations, which is why the camera was flipped in the earlier versions based on 10.1 ROMs. He switched back to 8.9 bases for the 1.2 version for this reason.
Clearly, these issues were resolved as the latest Overcome is now based on a 10.1 base again. However, I think there are a couple of other things needed that aren't articulated in the thread where he was replying to me on the subject. Anyone know for sure what else needs fixing?
i think - the most intresting problem with ROM - support language
How can add/delete longuga in ROM
Loccy said:
Actually, I don't think it's as simple as that post from alterbridge - that was quite early on in his experimentations with Overcome on the 8.9. I recall from the subsequent release of Overcome that he said that there were other considerations, which is why the camera was flipped in the earlier versions based on 10.1 ROMs. He switched back to 8.9 bases for the 1.2 version for this reason.
Clearly, these issues were resolved as the latest Overcome is now based on a 10.1 base again. However, I think there are a couple of other things needed that aren't articulated in the thread where he was replying to me on the subject. Anyone know for sure what else needs fixing?
Click to expand...
Click to collapse
You are right. Is much complicate than what they said. I just did an experiment. I replaced the boot.img in one 7510 custom rom with 7310Overcome 2.0's own boot.img, and changed some word in the build.prop. Put it on my 7310. Luckily ,it boot alright, but when the android welcome page(select your langurge ) show up, the screen did't respond my touch correctly, I need to touch somewhere under the target what I want to touch to make it work.
Looks like there is lots of thing I need to know.
I wonder when the CM ICS rom hits the 10.1 will alterbridge86 be able to work his magic ?
Fingers crossed !!
The true is,it is simple as what they said. My experiment work finally. I replace the boot.img in one custom 7510rom by the one in 7310Overcome2.0.
The tweak of the build.prop is very simple. Just replace all "P7510" by "P7310". Add "ro.sf.hwrotation=90" in the last. And All is done. The little mod Rom work perfectly on my 7310.
But I think the success belong to alterbridge86's boot.img and his work,without that, the rom just showed the Logo, nothing else.
By the way,I am going to investigate what magic alterbridge86 do in the file boot.img. The file size is much small than the stock one(half),and what's the impact. I have lots thing to learn
Might give this a try tomorrow. Would love to try a Vanilla rom on the 8.9.
any luck with the vanilla rom?
I wanted to play around with my captivate armani version, and since I like features of custom roms and dont like camera driver phone , audience etc... and i don't like that my froyo is rly slow rly for some reason idk why, i did restore to stock fresh install with wipe everytihng still slow since android market went google play froyo laging as hell.
So as I'm enthusiast I wanna try to copile my own froyo from soruce ( http://opensource.samsung.com/ and i typed i search i9010) I got soruce, atm i don't even learn how to compile from source installing ubuntu on other machine atm, but I take a look insade files and It's look like this is just AOSP soruce code not samsung soruce code for i9010... sound rly strange to me.
So my questing basically is this samsung soruce for i9010 or aosp from google?
File is only 170mb so if some of dev have a time to download it and take a look i will be really grateful...
If' it's not samsung source i don't have with what to start
Pls any advice will be helpful...
bg.stefan90 said:
I wanted to play around with my captivate armani version, and since I like features of custom roms and dont like camera driver phone , audience etc... and i don't like that my froyo is rly slow rly for some reason idk why, i did restore to stock fresh install with wipe everytihng still slow since android market went google play froyo laging as hell.
So as I'm enthusiast I wanna try to copile my own froyo from soruce ( http://opensource.samsung.com/ and i typed i search i9010) I got soruce, atm i don't even learn how to compile from source installing ubuntu on other machine atm, but I take a look insade files and It's look like this is just AOSP soruce code not samsung soruce code for i9010... sound rly strange to me.
So my questing basically is this samsung soruce for i9010 or aosp from google?
File is only 170mb so if some of dev have a time to download it and take a look i will be really grateful...
If' it's not samsung source i don't have with what to start
Pls any advice will be helpful...
Click to expand...
Click to collapse
I can't check the file right now but you're in the wrong section. This is for the I897 and I896.
BWolf56 said:
I can't check the file right now but you're in the wrong section. This is for the I897 and I896.
Click to expand...
Click to collapse
There is no section for his device, and I believe it is identical hardware.
Sent from my SGH-I777 using xda premium
korockinout13 said:
There is no section for his device, and I believe it is identical hardware.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Wow didn't pay enough attention, my bad. Seems like you're right, most of it is the same.
I did find this though which might help you on your quest: http://forum.xda-developers.com/showthread.php?t=876094
Yep i9010 is i897 for eu with armani sign and better plastic, and as far as i found only different is that armani have "better gps module" idk if it true but they are 99% same.
But if anyone have idea about this source i will be really happy to start working
Basiclly is this source useful and complete, i mean if i compile this i will get samsung touchwiz froyo or aosp foryo?
I will go trougth guides I already studied and i think i will be able to compile but only question is this samsung source.
Sent from my GT-I9010 using xda app-developers app
bg.stefan90 said:
Yep i9010 is i897 for eu with armani sign and better plastic, and as far as i found only different is that armani have "better gps module" idk if it true but they are 99% same.
But if anyone have idea about this source i will be really happy to start working
Basiclly is this source useful and complete, i mean if i compile this i will get samsung touchwiz froyo or aosp foryo?
I will go trougth guides I already studied and i think i will be able to compile but only question is this samsung source.
Sent from my GT-I9010 using xda app-developers app
Click to expand...
Click to collapse
My guess, Samsung. best way to know is to look for TW in it, it's the launcher after all
Yep that`s what was strange to me i think that source not comleate at all. Maybe im wrong but i downloaded i897 and few more source from samsung base and all are same they dont have any launcher in or im looking wrong. Only in anounsment file on site there is list of copyrights licence and i found on list launcher2.apk but it just in txt file list. As i know tw is seclauncer or tw03launcher something like that.
Sent from my GT-I9010 using xda app-developers app
bg.stefan90 said:
Yep that`s what was strange to me i think that source not comleate at all. Maybe im wrong but i downloaded i897 and few more source from samsung base and all are same they dont have any launcher in or im looking wrong. Only in anounsment file on site there is list of copyrights licence and i found on list launcher2.apk but it just in txt file list. As i know tw is seclauncer or tw03launcher something like that.
Sent from my GT-I9010 using xda app-developers app
Click to expand...
Click to collapse
I do think it's great you're trying to compile your on ROM but if you don't mind me asking, why Froyo? We're up to JB 4.2.1 now :silly:
Last stock for i9010 is froyo, and im begginer,
So i wanted to do next:
1st compile Froyo for i9010 to test if it work ( it would be as same as stock) to see if i can and have knowledge to do it and if its usable. Its easiest to test since its orginal one so without modding it should boot and work.
2nd compile GB for i897 with small modification to work on i9010 if any is even required ( to use component from i9010 code if needed)
3d step is to try port from some similar hardware device witch have stock JB to I9010.
I like stock look even stock froyo vs custom jb. I know there is TW custom rom but only think is ported laucher quality of calls and camera are bad, i know there was some guys that ported from samsung source GB i897 with some mods and custom kernel but system was full stock unforcunalty links are death so i didn't test it.
and as i read somewhere there is not all opensource i will prolly need to get drivers TW and some other things. idk why but i read that they are closedcode in most case.
I really like and support your idea to start developing for i9010. I have an i9010 and I must say before you start, I have successfully flashed and used various custom ROMs for captivate (i897/i896), mostly ICS and JB ROMs. The first time I was sweating bullets, but it works and in my experience have never had issues using captivate ROM's on the Galaxy Armani.
danigrad said:
I really like and support your idea to start developing for i9010. I have an i9010 and I must say before you start, I have successfully flashed and used various custom ROMs for captivate (i897/i896), mostly ICS and JB ROMs. The first time I was sweating bullets, but it works and in my experience have never had issues using captivate ROM's on the Galaxy Armani.
Click to expand...
Click to collapse
I know i tried almost all custom roms. But i don.t like look of dialer phone. Qualty of camera and voice. So i would like to have something like samsung jb or ics on captivate/armani. I was think about 2 option port s2 rom or compile something from source but i didnt have time to check anything cuz of duties on university. So as soon as i get time i will study source.
Sent from my GT-I9010 using xda app-developers app
Hello can you please help me to get on a stock ROM for Giorgio Armani?
I flashed I897 GB 2.3.5 but my phone doesnt't work.
While discussing this custom rom in other roms' threads, I came across one for the MB886 with CN localization.
I was able to download it and flashed. But before doing so, looked at the archive and noticed it had a /data directory with suspicious apps in it. So I wouldn't really recommend anyone actually flashing it for use until someone with knowledge took a look at it.
Interestingly enough, it does flash and seems to be working, I cleared data/wiped before booting it.. Take note that it's is not officially supported by slimkat nor is it available on their site.
EDIT: We have a working rom now thanks to Technofreak, check it out here http://forum.xda-developers.com/showthread.php?p=49622265
I finished compiling it to see how it goes. Will post ROM if is good.
TecknoFreak said:
I finished compiling it to see how it goes. Will post ROM if is good.
Click to expand...
Click to collapse
share
Sent from my MB886 using Tapatalk
WAREZ/malware linked, DELETED.
Mobile Data is not even working for me. Yes it does have trojans and I woudnt download this rom. Did Data worked for you when you installed this crap? Ok I went Further guys this is actually a build for xt907 devices and NOT mb886.
Please delete the Links to this Chinese Rom from this forum and from the Cyan thread. THis Rom Contains Applications that require payments from the Google Play and its Developers. It contains apps like
Android Tweaker PRO
Root Explorer
NexMusic +/Plus
and others
Ok to my Fellow forum friend @clockcycle and others wanting this ROM I have made an Modified version out of this Chinese Rom which works 100% without any lag and is working great. I will make a thread for this one and there is also and right now is the one I use as it looks lots as Validus without much Clowns as @skeevydude like it. lol
Seen very solid to me and is my and will be my daily drive (For now) lol
Also there is one I compile together but since time limits I havent been able to test it. This one should have more options and few then other fixes to options that came after my Modified version
Will explain more at the Developers thread
TecknoFreak said:
Ok to my Fellow forum friend @clockcycle and others wanting this ROM I have made an Modified version out of this Chinese Rom which works 100% without any lag and is working great. I will make a thread for this one and there is also and right now is the one I use as it looks lots as Validus without much Clowns as @skeevydude like it. lol
Seen very solid to me and is my and will be my daily drive (For now) lol
Also there is one I compile together but since time limits I havent been able to test it. This one should have more options and few then other fixes to options that came after my Modified version
Will explain more at the Developers thread
Click to expand...
Click to collapse
Yea I was really surprised to how lite "SLIM" the CN version of the rom was. But didn't trust to install gapps, login or install any apps. I also wiped /data after first flash before the boot. Downloading your version right now.