Related
Trying to do wireless tether, already rooted, just need correct kernel i believe.
There's a new *PROPER* CyanogenMod release out for the 1.2 that includes exactly what you're asking for. It's in this forum, and consistently in the top 20 most recently updated. All you need to do is click...
This one: http://forum.xda-developers.com/showthread.php?t=671122
But you can't just patch it onto any rom, you have to make sure you're using the official Cyanogenmod 4.2.15.1 ROM before you can flash that patch onto it. (see the second post of that thread above). But once you do that you'll have full hardware capabilities as well as the custom kernel features CM offers (Such as wifi and usb tethering, though I would use USB tethering as Wifi drains the battery even if you got it plugged in).
so which option would i select from here:
http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F
I just did "Upgrading from a CyanogenMod version less than 4.1.99 or other rooted ROMs", and now the phone is stuck at htc magic screen. any ideas?
Got it, just had to install the new ported cyanogen after installing the other 3 zips
Playa4Life352 said:
Got it, just had to install the new ported cyanogen after installing the other 3 zips
Click to expand...
Click to collapse
Ported (which one are you refering to, there's one that takes the official CM rom, then you flash a patch onto it, then there's one earlier thread with a 'ported' rom)?
just get barnacle tether and don't worry about the kernel.
it does perfect wifi tether
+1 that way you can keep your camcorder for now too
robkoehler said:
+1 that way you can keep your camcorder for now too
Click to expand...
Click to collapse
Camcorder works fine in the proper cm port
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Download: http://www.multiupload.com/7DH5QLGGGW
It work's great i pulled the stock browser from KG1 ROM & put it on this KG2 & it work's perfect .
sduvick said:
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Uploading now, and I will post the link when it gets uploaded.
Click to expand...
Click to collapse
Can this be flashed over a rooted KG1? I tried doing so and I softbricked. I'm in the process of ODINing to stock KG2.
Also, is it safe to restore the data from a KG1 nandroid?
This should work to flash from KG1, you may have softbricked because you didn't check your mounts before and after flashing? restoring data should be fine, make sure you wipe your dalvik-cache from the advanced menu in CWM after restoring your data so that it rebuilds.
Yea, I don't think I checked my mounts. I'm ODIN'ing to KG2, then I'll be rooting, CWM'ing, and then flashing this ROM. Thanks!
Let me know if you're still having problems, I'll do my best to help you out!
I got it to work. Thanks for giving me the heads up on the mounts. I'm sure that's what softbricked me. Thanks again!
Sent from my SGH-T839 using XDA App
So is this rom up to speed compared to Smooth Maximus GingerClone? I'm reading form T-Mobile support that it actually lags a lot more than stock rom. Can this be flashed from GingerClone? Or must I odin first?
This can be flashed from GingerClone, as it contains both the updated firmware and the updated kernel. This is not really intended to be a rom persay, but rather to be a base for other themers and devs to make roms with. There's no speed changes, other than the lagfix that comes from Bali.
I'm using it now. It is pretty good already with bali implemented. Other than Media Room becoming an active process periodically, the stock experience is going well. The disability of the track pad will be very helpful outdoors.
Also got a soft brick trying this. Goes to the boot screen, and the motor buzzes once, then twice in a row, pauses then does the buzzing again.
Double checked the mounts before doing it.
Can still get into recovery, but trying to reinstall packages gives an invalid signature error.
Ugh...
Then it didn't flash correctly. You would have red CWM if this flashed correctly. Odin back to stock and try again, as if you can't get into recovery correctly, you can't do anything from there. You may want to redownload to make sure that you get a good copy.
That's what I did. Odin to stoc kg2, rooted, added cwm recovery (orange) then used same copy i downloaded earlier to flash. Worked properly.
Might be worth a test, that this might not be cwm flashable over stock kd1. Thats 2 reports of it happening so far, and i am not a beginner in flashing or following directions. Just an annoyance really, odin was painless to use. (Now, having to reinstall windows on a old pc laptop, so much fun /sarcasm) ;P
I've done it before just fine, flashing on the SK4G is different from most phones, if you don't check your mounts before and after, then it will not work.
All ROMs here include a KD1 or KG2 specific kernel in addition to their specific systems, so as long as mounts are checked, everything is overwritten. /system is entirely wiped in the flashing process, and a new kernel is flashed. There is no possible way, given a correct flashing procedure and a ROM that includes a kernel (which as far as I know are all the ones here) that this would not work to flash KD1 over KG2 or vice versa.
So far, this is the fastest rom I've tried, thank you for creating it! Even if its stock.
This had serve me fantastically. Wish the same was available for kj2
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
sduvick said:
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
Click to expand...
Click to collapse
Sadly, it is Bali/Voodoo-less.
Download link for this doesn't work. States the file has been deleted.
Does anyone have this file still?
I have a D2G and I used to run Froyo-based CM7, but since the Gingerbread version is further along in development I went back to Gingerbread by SBFing. So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
PantherHeel93 said:
I have a D2G and I used to run Froyo-based CM7, but since the Gingerbread version is further along in development I went back to Gingerbread by SBFing. So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
Click to expand...
Click to collapse
In order for a Gingerbread ROM to boot it needs the Gingerbread Kernel. Are you booting with a white Motorola logo or a red one?
If it's still white and you're trying to boot Gingerbread CM7 it may be worth it to try to grab the .608 Gingerbread kernel from the TBH hack and flash that in. I've attached it to this post just in case.
PantherHeel93 said:
So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
Click to expand...
Click to collapse
7.1 Stable is probably the “official” CM7 build 7.1.0, from the cyanogenmod site.
That one is for Froyo (i.e. can only be installed over 2.4.x stock firmware).
As for RootzWiki builds… did you wipe data prior to or after installing the ROM via CWM?
projektorboy said:
In order for a Gingerbread ROM to boot it needs the Gingerbread Kernel. Are you booting with a white Motorola logo or a red one?
If it's still white and you're trying to boot Gingerbread CM7 it may be worth it to try to grab the .608 Gingerbread kernel from the TBH hack and flash that in. I've attached it to this post just in case.
Click to expand...
Click to collapse
Red. The SBF file put me in this situation:
System version: 4.5.608.A956.Verizon.en.US
Android version: 2.3.3
Kernel version: 2.6.32.9-gb092e69w360842ca25rhe92 #2
Build number: 4.5.1_57_D2G-38
Gasai Yuno said:
7.1 Stable is probably the “official” CM7 build 7.1.0, from the cyanogenmod site.
That one is for Froyo (i.e. can only be installed over 2.4.x stock firmware).
As for RootzWiki builds… did you wipe data prior to or after installing the ROM via CWM?
Click to expand...
Click to collapse
Yeah, the reason is didn't download the stable one first is because I thought as far as anyone had gotten was 7.0 nightlies. I'm just baffled right now as to why I can't get the Gingerbread CM7. I hate stock haha
Before I flash, I backup, reboot, factory reset, wipe data, cache, dalvik, and even battery stats. Then I install CM, then gapps package, then reboot.
Thanks for the help guys, I appreciate it!
Could you specify the file names for both CM7 and gapps you're using?
And you're wrong about RW builds being 7.0; they use the current CM7 source tree, and the “stable 7.1.0” is basically one of old Froyo builds by revnumbers.
Actually, I got everything from here: http://forum.xda-developers.com/archive/index.php/t-1297517.html
I used the latest version "update-cm-7.1.0-DROID2WE" and the "gapps-gb-20110828".
The second time I used the CM file from Rom Toolbox and the same Google Apps package. So if a bad gapps package can eff you over, that's probably it. I just don't want to waste my time and try again before I have some xda-genius opinions haha
This is the Froyo-only “official” build. It will never work with a Gingerbread kernel.
As for ROM Toolbox, I have no idea. The gapps package seems to be the right one, however.
Head to http://ez-netsolutions.com/synik4l/x13thangelx/D2G/cm/ for the latest build of CM7 for the D2G. x13thangelx is currently the lead developer working on this project.
Thanks a lot!!!!!! You're the best haha I'll let you know if it works.
Refer to this thread on RootzWiki for more information: http://rootzwiki.com/topic/3069-dev-threaddroid-2-global-cm7-with-gingerbread-leak-kernel/; note that the opening post hasn't been updated since forever, so you won't find the current build there.
And use this thread if you have any questions: http://rootzwiki.com/topic/4922-cm7-for-droid2-global-users-thread/
Not necessary haha, but I got it and it's working and beautiful and every setting has been adjusted and I'm super happy again!=D You're my hero.
i am able to get my gps to work on honeycomb roms but when i flash a ics rom i cannot get the gps to fix
i am also not able to recover an ics rom after i flash back to honeycomb to try to force the gps to work - my tf101 freezes at the bootscreen
also not able to get the faster fix and gps fix to work on the ics rom
any suggestions?
When you go back to HC via a nandroid restore, you have to also flash a HC kernel. CWM does not restore kernel for done reason.
That's why you're stuck at boot up screen.
+1 flash an HC kernel to fix on HC.
Try flashing Guevor's ICS kernel though, it's great stuff and fixes many ICS issues, may fix the GPS too.
Hello,
I searched for this issue but couldn't find the exact problem being experienced by others, so I'm asking about it now.
So I'm using the latest MultiROM and Lollipop firmware (the 02/09 one). I simply can't get any Lollipop ROM to stop bootlooping with a recent kernel. Boeffla, AK, Tyr, etc. all bootloop with every LP ROM I've tried, regardless if they're set as primary or secondary in recovery.
The only way I can get a ROM to boot is with a kernel meant for CM11/S, like AK r77 and Sensei r77, though I can't get the radios to work with these. But newer kernels simply won't work, period.
Am I missing something here? I thought the latest firmware and a recent kernel with kexec-hardboot was all I needed.
Edit: Also seems to happen with a fresh install of the latest CM nightly. Using the default kernel that comes with CM, too. There must be something that I am missing here...