Related
Anyone who has or know if tun.ko has been ported to work on the LG 2x yet?. Its because I need the tun.ko drivers to activate a VPN connection and the 4 standards provided off the shelf is not supported .
The only way I can connect is via an app from market, but said app requires the presence of tunn.ko to work.
MoDaCo has a kernel with tun included.
I would prefer it not being a custom kernel etc . Im not really that much into flashing new roms and such until at least I have seen Gingerbread on the 2x.
So at present I am hoping for a solutuon that only requires me to push it to the phone and not flash a new rom.
MeX_DK said:
I would prefer it not being a custom kernel etc . Im not really that much into flashing new roms and such until at least I have seen Gingerbread on the 2x.
So at present I am hoping for a solutuon that only requires me to push it to the phone and not flash a new rom.
Click to expand...
Click to collapse
Then either get it from the kernel image or ask Paul nicely to help you out.
Does this paul have name on this board.
You must be new here.
It's paulobrien. His 2X forum is at http://2x.modaco.com.
I just joined a few months ago, so no im not venerable yet . But does this paulk frequent these boards as well?.
The reason I ask is that I find it a bit excessive to register at yet another board for the mere reason of needing to contact him and enquire about that tun.ko file
Alright, let me put it this way; You wouldn't regret taking a minute to sign up for modaco.com, because his custom ROM's and kitchens tend to be for members there only. The MCR (MoDaCo Custom ROM) kitchens are famous for their easy way of choosing what you want to include and not in the ROM.
He's frequently here and on Twitter as paulobrien.
Yea I sent him a PM already on here . But for all the goodness of custom roms I have never really ventured into that realm and tried one. I meant to do it when I had my Desire and started to realise I might get Gingerbread for it. But then HTC says they would give it gingerbread so I stalled even more
And now I have the LG as well, and for what it is worth I am generally content in a a large extend with having a stock rom, albeit with some of the provided apps removed and a few tweeks and addons here and there, without going all the way.
But time will tell with the LG
It's definitely a good phone, and hopefully it will get even better. Let's cross our fingers for Android 2.3 or 2.4(?) soon.
In the meantime I can tell you that flashing custom ROM's is very easy. It's close to impossible to screw up the O2X because we have nvflash working and can overwrite all partitions easily. Nvflash is Nvidia's own tool for writing to the ROM. Paul has a guide for how to flash the latest stock ROM in the dev section here. Just beware that using nvflash will in most cases format (delete) everything including your external sdcard, but you can of course remove it first.
Better yet is to install the custom (ClockWorkMod) recovery, backup and flash a ROM from there, because then you don't have to reinstall apps+data. All data+sdcards will be intact, but system settings and any manually added apps in /system/app will be lost though.
If you decide to give it a go we are all friendly and helpful people, just do a little bit of homework yourself.
I had rooted and security offed my Desire which I have have now passed on .
My LG 2x is also equally rooted, I got CWM on it and flashed radio drivers . So I have already did some manner of mocking about with it . But is NVflash a "required" item on our phones. Because I considered installing it, but didn't thnk I really had a need for it at first.
But sadly rooting and doing such to your phone also means OTA software downloads are not possible as the phone is not detected as being the original phone anymore :/
MeX_DK said:
But is NVflash a "required" item on our phones. Because I considered installing it, but didn't thnk I really had a need for it at first.
Click to expand...
Click to collapse
NVFlash poses as a "last resort" if you brick your phone beyond the ability to make an adb connection. As far as I understand it, it hooks in far earlier and thus enables you to flash system partitions.
If you don't brick your phone, you probably won't need nvflash, but its a safety net to revert the phone to a stock ROM if you screw up.
Still no dice, I sent Paul a PM some days ago and not a word back :/
So is there anyone else that might be able to help, since I will assume I can't just "reuse" the version I got for my Desire
I was wondering if anyone would be able to code a bootloader like piece of software
in theory if we could make something that can start at the same level as revoery then we could have that select wich rom to start. I think then we could have mutiple roms on one device.
i was thinking it could be very good right now as devs and testers are using GB roms. THey could have a nice stable themed rom and then a dev rom and be able to switch between the to.
Is this possible or a pipedream(and why wont it work)
kedster said:
Is this possible or a pipedream(and why wont it work)
Click to expand...
Click to collapse
Bootloaders are closed source, and no one wants to re-write them right now.
Also, Q/A.
actually there was a script to dual boot the nexus S rom on our captivate a while back but it required data as system..
I can't seem to find the answer - I've purchased the VZW Tab Bootstrapper, which at this point only seems to brick my tab - after Heimdalling, I installed Oldmacnut's Rooted Gingerbread Rom - ROM Manager says that CWR 3.0 is installed - if I push flash new recovery, the only devices i can select from are Galaxy i900 - assuming that the rom was built from this device - so, what do i need to do to get clockwork properly installed? If i volume up/power up, I get stock recovery - if I use ROM Manager, it gives me the triangle with a progress bar for a second or two, then reboots - don't want to reboot with the bootstrapper program again, as i don't want to re-brick my tab - unless I'm crazy, there doesn't seem to be an easy solution - am I crazy and/or blind? There seems to be a possible kernal solution, but I have to flash it, and I can't flash it if i can't get clockwork recovery going - i think. help....
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Is there a way to stay on rfs with your cwm kernal you posted?
oldmacnut said:
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Click to expand...
Click to collapse
Thanks - at least I know I'm not nuts - I honestly don't know that it's necessary to mess with the kernal that's in the GB rom you compiled - it works great as is - I'm just so used to flashing stuff through Clockwork from all the android phones I've had - new to the samsung/tab world, trying to get myself up to speed -
Thanks again for getting back to me, and please, PLEASE take care of yourself and family - this android world is supposed to be fun, not just for us that take advantage of the work that devs like yourself put in, but fun for the devs too - now put your feet up, pour yourself something cold, and watch some football.
Just make sure to have all the ROM's you started finished by morning...
My name is Jack, and I'm a romaholic.
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
TheATHEiST said:
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
Click to expand...
Click to collapse
Oops - copy that - thanks for the heads up.
Thread moved to Galaxy Tab Q&A.
Oldmacmnut,
I can't seem to get Heimdall working (or USB at all, for that matter) on my Tab. I have root, and I can reboot into recovery, although it isn't CWM recovery. I tend to believe that the problem is in a corrupt ROM install of some sort, and would like to either flash a stock ROM to get back to square 1 or a rooted ROM. Problem is, I think I need to figure out a way to do that through recovery as USB doesn't seem to work at all on any computer that I have tried. If you have a CWM Recovery that works, is it flashable in the stock recovery?
Thanks,
Seth
Hello, people of xdadevelopers! I'm new here and keen to learn up on custom Android roms. Sorry if i sound really noob or am doing things wrong in this forum, but... everybody has their own starting phases right?? ^^ Please guide me where I'm going wrong...
Anyway, I'm from Singapore and i own a SAMSUNG GALAXY BEAM GT-I8520 (rare and unheard of phone released only in Singapore x.x). I won't elaborate much, but basically I'm kind of still a student (therefore no money to buy other phones) and my mobile plan is left with about 11 months to go before i can renew my plan and select another phone for a cheaper price... I don't really like my phone because the moment Samsung released it, they decided to stop updates because there is not enough users of this phone so I'm stuck with 2.1 eclair. It also has a slow 500/700mhz processor and lags like he**. By the way, it was released around July 2010 at the same time with the Galaxy S, and they have really similar specs, that's why i posted in this area of the forums.
So, i was thinking of switching over to the MIUI rom which i desperately want... and i decided to follow the Galaxy S I9000 (because they are sister phones!) tutorials to flash over to MIUI in hope it would revitalise my phone, stop the laggyness and crashes, give it a new look, allow me to use features that i miss out in froyo or gingerbread!!
I can understand most terms and softwares about flashing... been researching for a few days... and i found this guide
http://forum.xda-developers.com/showthread.php?t=1101601
which tells me to replace my bootloader with a gingerbread bootloader through ezodin, then boot into recovery mode which is the custom cwm recovery, and from there straight up install my rom that was placed in the sd card, and walla i get my MIUI. I assume that the bootloader will give me CWM recovery because the guide doesnt tell me to get it through rom manager. I currently have the base google stock recovery, so question <1> do i have to install cwm recovery through rom manager first or will the gb bootloader give it to me once flashed? and question <2> i've tried to install it through rom manager but it didnt work the first try (i chose my phone model as the S) and even erased all my apps and data :S Is there a way to go around installing clorkworkmod? I understand my phone isn't EXACTLY Galaxy S, but they're similar...
Also, another problem i face is that i DON'T have the 3 button shortcut to recovery mode or download mode. I'm following this tutorial to try repair it, since I've heard a batch of Samsung galaxy s have flawed recover and download modes that can't be accessed by the 3 buttons. since the two phones were released around the same time, it could be that the galaxy beam was affected also. Everything is fine going through this tutorial (even getting to download mode trough ADB is fine), problem is i get stuck every single time in ODIN at SetupConnection. Question <3> any freaking idea how to solve this? I've gone through google and searched through this forum... Now i don't know what to do and don't dare try anything else or other flashing unless i fix this 3 button shortcut because i know i can only access recovery or download through ADB REBOOT RECOVERY / DOWNLOAD and the phone has to be plugged in, turned on, booted into android, and in usb debug mode. the ADB command won't work if the phone is off and i'm worried the GB bootloader will stop eclair from loading.
This leads to the question <4> if i decide not to follow this repairing tutorial and just flash the gingerbread bootloader up front, will it give me the 3 button shortcut boot? because if i am not able to load the eclair rom with gingerbread bootloader, and have no 3 button shortcut, i will not be able to boot into recovery to install rom and wipe data and cache etc. Also, if i flash the gingerbread bootloader, can i still load into my stock eclair rom? If i can load into the stock eclair rom, then i don't need the 3 button shortcut, i can go straight to doing usb debug and the ADB command again after flashing bootloader and rebooting to go straight into recovery and installing MIUI.
Question <5> What about gingerbread bootloaders that can backtrack and load froyo roms and eclair roms? Do these exist? Where to download? If so, i can load into my eclair rom and use ADB for recovery mode, eliminating the step: repairing the 3 buttons.
Question <6> Also, i noticed the guide didn't speak anything about kernels etc. From what I understand about kernels, it is the architecture or system between the hardware and the software. People can tweak kernels (leading to custom kernels) for different and maybe even better sound and video etc right? But the guide doesn't say anything about installing a custom kernel, so am i supposed to keep my current Zues kernel from Samsung, or is a custom kernel recommended by MIUI ALREADY provided in the zip folder i downloaded from here? (the I9000 one) When i flash this zip through CWM recovery, is the kernel changed together? Does this apply for the bootloader also? Is the bootloader supplied in the zip and flashed together at the same time? if everything, (rom kernel bootloader) is flashed together at the same time then i can eliminate many steps and just work on installing CWM recovery through rom manager. then use adb to boot into recovery and flash that one simple MIUI zip. no need for 3 button boot...
Question <7> Is there another way to get MIUI to install on my device without so much hassle? haha..
Thanks for the trouble, I know it's a lot of questions... Please answer whatever you can
umm, almost a 100 views... but no replies? :'(
I'd never heard of it until this post, I looked at some specs and they're quite significantly different to the SGS's ones, smaller screen and completely different processor(which is most important(TI OMAP 3440 720MHz in the Beam and Hummingbird S5PC110 in the SGS)). It's a completely different phone, don't even try to install MIUI for the I9000 on it unless you don't mind your phone being in a bricked state. I may not be right but it's my strong opinion. Here is the Xda wiki for it: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Beam Which shows how to root and then OC it which may increase performance. And if you like the Miui look there is a look a like launcher floating round if you search. Good luck
true, they aren't exactly the same. the processor is definitely different, but i think MIUI was made for performance, which fits well with this lousy processor haha. screen shouldn't be a problem, most softwares fit to screens automatically. I've already Rooted and OC'ed it but its still slow.
Is there any way to flash everything at once, e.g. kernel rom everything flash together at the same time using ODIN, then maybe i will reboot and see if the MIUI works... The problematic part is the 3 buttons download mode. I'm willing to flash everything at once then see if i'm lucky and MIUI will work for me. I'm not willing to flash just kernel or etc, then can't get in to download mode already because phone cant be booted, thus cannot install ROM...
Does anybody know exactly what when flashed into the phone gives me the 3 button recovery and download...?
I also realised something in the wiki link u gave me...
Power+Menu+Volume Down -> Soft Reset
Power+menu+Volume Up -> Ready for Flash Screen
Could this be my recovery and download...? I'll try later.
I'll try and give you an example, the Galaxy SL or the I9003 came out the start of this year as a replacement for the original with the only difference being the chipset and display type. Quite a few people have got this phone and have being trying to get Miui to work on it hasn't happened. The I9000 kernel for Miui is made for the I9000, it only works with the Hummingbird chipset, end of story. I'm not stopping you from trying but expect the most likely consequence to be the phone dead, not running Miui.
Wow, if the I9003 which was even closer (spec-wise) to the I9000 can't flash I9000 MIUI, then my I8520 won't make it... :'( I understand what you mean, any kernel made for I9000 phones, even custom user-made ones, only work with specific hardware, like that chipset, unless that kernel some how is clever enough to work with my hardware, or probably just lucky enough to be compatible with my chipset.
I didn't know the software had to confirm so tightly to the hardware... I'd always thought software would automatically work with basic hardware, albeit there would be some issues and glitches, but at least it would still work. I thought maybe it would be possible to keep my Zues kernel, and just flash the rom, and let the rom use my kernel.. It wouldn't be very optimised because they weren't made for each other, but at least with a few bugs, still usable... But now I know my Zues kernel works with my hardware but probably wont work with I900 MIUI unless it was coded for my phone... Though, if my phone does have the same chipset and gpu, maybe it will work?
Seems like I'll have to continue to use this lousy unsupported phone :S
Thanks for your help
I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys