Related
I've been flashing kernels through Clockwork, but I decided to download Kernel Manager Lite and I'm considering trying it. Has anyone had any experiences with it, good or bad? I'd appreciate any feedback before giving it a go. Thanks
it's works flawless for me, i use the free one.
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
icesteve said:
The only problem I've run into was flashing a kernel while on BAMF 1.6, it worked but broke wifi. I flashed the same kernel using clockwork and wifi was back with no problem. I read someone else had the same problem.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I was using kernel manager pro when I attempted, not the one included in the rom. I figured it had to be kernel manager because CWM flashed it perfectly.
Sent from my ADR6400L using XDA Premium App
Thanks for the responses. I'll probably give it a try. I guess I can always reflash through Clockwork if anything goes wrong. Or worse case, I can flash a backup if anything gets seriously out of whack.
bunklung said:
That might have been me and more of a 1.6.1 ROM issue which has Kernel Manger Lite included. My story:
http://forum.xda-developers.com/showpost.php?p=13444295&postcount=351
Click to expand...
Click to collapse
I had the same problem .. I never considered that it may have been kernel manager .. thanks for that
Sent from my ADR6400L using XDA App
For me the issue is this ...
No backup made prior to flashing ... I'm sticking w/ RM for kernel flashing
Based on my experience with BAMF rom and leanKernel, it appears that any customization scripts and/or files that the kernel developer intended for you DO NOT get flashed with Kernel Manager (I have Pro version). The people with broken wifi using KM but working wifi with RM proves the point. My experience was that 4G hotspot didn't work when flashing leanKernel from KM, but works fine with an RM flash. This is actually a common problem across several devices I've used. Many kernel devs modify the wifi driver and/or other things in a manner that they end up only working with their specific ROM. The do this by including the modified files in their zip package along with a script telling the phone what to put where. The issue becomes if you switch to a kernel that's relying on a stock wifi driver, and doesn't put it back on its own, then you've got a busted wifi. The only way around that is to manually push/restore a copy of a wifi driver known to work with the kernel you're using. I kind of regret paying for the pro version after finding this out; hopefully the KM folks can figure it out. The kernel itself is just the boot.img file; the add-ons files that go into the /system partition or where-ever. If you're interested in knowing what a particular kernel is pushing on your phone, just open the zip file and drill down through the folders to find what files are in /system tree. This is also a way to find files you need to go back to stock drivers, just find a stock rom that's flashable in RM and drill down to the files in /system/lib and push them back to the phone via adb or root explorer.
i bought the pro version and i wish i hadn't. i downloaded/flash one of protekks kernels through there and it sent my phone into a bootloop and by the time i'd flashed a nandroid backup the 15 minutes had gone by -_______-
why?
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
turbosrrgood said:
I haven't actually tried this yet, I guess the question for me is why? Does it do something that CW cannot do? I don't know much about the product so I am just trying to understand the benefit of installing it.
Click to expand...
Click to collapse
It will notify you of kernel updates, and you can filter kernels based on what you want
Sent from my ADR6400L using XDA Premium App
I am running Eaglebloods 2.3.5 gingerbread ROM on my G2x and was just wondering if it is necessary to update my baseband through LG's updater tool. If yes, should it fix the issue I have with my data stop working sometimes, that I have to keep restarting my connection to get it to work again. What exactly is the Baseband and what does it do? Is it updated when you flash a ROM?
G2x
Eagleblood 2.3.5
Baseband takes care of all radio communications (calls, data...) and it cannot be flashed. The only way you can have it is to use the risky LG update tools, which has bricked many phones unfortunately. We all hope someone will soon put a flashable baseband.
Don't be too afraid of the LG tool, I used it and there were no problems whatsoever. Just remember to flash back to a nandroid of 2.2 stock before starting.
Sent from my Nexus 3 using XDA Ultimate App
thank you both very much for the advice. I will restore back to my first backup and try the updater tool.
have either of you noticed a difference after using the update tool?
Nope. And we have yet to receive a flashable baseband.
Sent from my LG G2X using XDA Premium for Android
The tool will put your recovery image back to stock so you will need to re-flash.
The best method is:
Make a backup of your current setup
Restore a stock backup
Reboot
Run lg tool
Flash CWM with nvflash
Restore your backup
I have noticed a HUGE difference, mostly in gps. It used to take upwards of 8 minutes to get a lock, now it takes 1.
Sent from my Nexus 3 using XDA Ultimate App
Also, the new Baseband doesn't fix the Data issues present in CM7 and Eagle'sBlood..
UPDATE 6-15-2012: i just wanted to update the beginning of this post to make it a little clearer, the original text is below
to get the v21y base band on your phone over the air, you have to go back to stock
to do this you need a stock rom, either your own backup or the one from this thread
http://forum.xda-developers.com/showthread.php?t=1248644 (the first and second link is a stock 2.3.3 nandroid which is a zip you extract on your pc and run flash.bat from inside that folder)
if you need the drivers, download the third link.
follow the steps in that thread, it works
if you have your own stock nandroid, just boot into ClockworkMod Recovery and restore it (after you backup whats on your phone now)
then reboot your phone
after restoring either your stock nandroid or the one from the post above, shut your phone off and remove the battery and use NVFlash to restore the stock recovery
http://forum.xda-developers.com/showthread.php?t=1056847
reboot your phone
now that you have your phone like it was from the beginning you can go to System Settings/About Phone and click on Software Update. this should pull down the updated Gingerbread version 2.3.4 and the new baseband v21y. IT WILL OVERWRITE YOUR PHONE AND WILL BE PLAIN STOCK
it takes a few minutes so be patient
once it is done and it rebooted your phone you will have to put ClockworkMod Recovery back on it using NVFlash. then you can flash other roms to your phone
please keep in mind that there is a bluetooth issue with both GB and ICS roms on this baseband and that only a few roms actually support v21y. Owain has written an update file that you flash to get support on any rom with v21y, supposedly it does work on any rom (GB or ICS) but i have not tested it, so read up and test if you want.
as of CM7 RC3 all CM7 builds support v21y
please thank the owners of the threads linked above, their methods worked flawlessly for me and i hope they work for you as well. this was a very easy way for me to get the new baseband. good luck!
original post------------------------------------------------------------------------
i was having a heck of a time trying to get the new baseband installed on my phone. i had all the stuff downloaded and all the instructions ready, had the KDZ file, the LG tool, everything...but i could not get anything to work
so what did work?
well using CWM Recovery i restored my stock backup i had made when i first got the phone (best to save this off the phone as well in a safe place) and then using NVFlash i put the stock recovery back on it
once that was done and i was booted back into stock you can go into the About Phone and choose Software Update (or whatever its called) and check for an update. it found one and proceeded to download a 30meg file. asked if i wanted to apply the update, installed it, and rebooted into a nice shiny new 2.3.4 GB setup with v21y and the new baseband installed!
the CM7 nightly build (June 3) is working great. getting ready to try a couple of others (Buru, EB, Genesis (although i was having a problem there, see that thread))
so its only been one day on it but so far calls are good, gps lock is fast, overall loving my phone even more than before!!
Great that the OTA worked for you, I left my phone stock the whole week it was mentioned about sending it and I checked the software update and it always told me the software update check failed/timed out lol
Sent from my LG-P999
I am extremely pleased with the update.
I had been running a rooted stock ROM + CWM Recovery. I had been dismissing the update notice for weeks now. Finally, earlier this week I flashed back the stock recovery and let the OTA proceed.
Current uptime: 67:59:06
I haven't gone a full day without either a random reboot or a sleep of death in a LONG time.
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
which cm7 are you using? i had the last nightly june 3 and could not get mass storage to work
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
edekalil said:
Did mine the other way not over the air. Then did the sound update. Also running CM7 and all has been fine.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
lamdaman said:
I just did this method too and its a lot easier
---------- Post added at 08:56 AM ---------- Previous post was at 08:51 AM ----------
What is the sound update? I thought it was included in the new baseband and is it in the ota update? Thanks
Click to expand...
Click to collapse
there were a few people that got a bad motorbooting sound when making calls and lg released an update to the new bb but it was only for people who had the sound issue
its was hard
i swear it was hard trying get it to work but once i found me a stock rom i was all good from there
Can you test if the 6.3.12 nightly has working in call bluetooth?
Joe333x said:
Can you test if the 6.3.12 nightly has working in call bluetooth?
Click to expand...
Click to collapse
i dont believe it was, i just had that installed on my phone and coming to work today i tried to connect it to my car bluetooth and it would not connect. i have an ICS rom on my phone now, hope it works with that...i know it did on EB ICS
updated the first post
Reverted back to stock this morning and installed the OTA update...now i'm back on cm7 with no issues. Great suggestion on an easy way to get the March baseband.
Thanks!
Sent from my LG-P999 using Tapatalk 2
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
Use the LG update tool
Sent from my LG-P999 using XDA
adame09 said:
im trying to do this but when i check for updates it says connection failed ive been trying for 30 mins on and off wifi
Click to expand...
Click to collapse
you are on stock rom AND stock recovery? data connections good otherwise?
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
partylikeaninjastar said:
A little clarification, if I may...
Could I just flash the stock 2.3.3 nandroid from this thread: http://forum.xda-developers.com/showthread.php?t=1048274 to bring myself back to "stock" then, using NVFlash that's already on my computer from when I first rooted my phone, flash it back to stock recovery? After that, try the OTA to get myself to 2.3.4 or, if that doesn't work, use the LG Updater tool? Then just root my phone again and go back to enjoying custom ROMs?
Seems like it would be easier and one step less if I get the nandroid from that thread rather than following the link in the OP and having to extract something on my computer.
Click to expand...
Click to collapse
yes that will work as well and whether you get a stock rom from the link i posted or the one you posted makes no difference this was just how i did it
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
partylikeaninjastar said:
Hey, thanks! I've been wanting to update my BB ever since it became compatible with the new ROMs, just haven't been able to set aside the time to be able to do that. Just wanted to make sure I had it right before I attempted.
Your steps sounded easy and straight forward; it just never hurts makes sure!
Thanks again, bro.
Click to expand...
Click to collapse
you're welcome
there is a bluetooth issue with all roms and the new BB so if you use BT you might want to stick with the stock 2.3.4 that you will get with the upgrade. lots of devs are working on that issue so hopefully it wont be long
suggestions?
I followed the instructions in the first post, and now am back on the stock rom (21e, july 15 2011). However, when I go to try the software update, I get the following message: "current version is the latest version." Is there another way to get the new 21y baseband?
Ive looked just like the rules stated. Yet i can not find out a reason to my problem. Im no noob whenit comes to flashing kernels and roms. with that being said here goes. I have jst aquired a Nexus S. I traded it for my old iphone 4 felt good to be back to android. anyways I have Kangy-U loaded up and ready to go just flashed it yesterday. today I figured after some resarch I would flash Air kernel. after I flashed it through recovery (CM) it goes through the proces and says it s flashed. I boot back into kangy and look under settings and find Its still stock. I tried again, same problem. by this point I figured bad download redownloded same problem. so I then figured ok they are just not playing nice together. I trie a different one. this time cyans stock universal still same problem.
Is there a step Im missing?
Have you posted over in the thread for the ROM? Never heard of a kernel not flashing like that with the recovery saying the flash was successful.
Sent by pocket technology
Try reflash the rom, just a guess.
Sent from a sandwich using my Nexus S
ya i reflashed everything wiped data system cache boot. then it worked. I do know CM can be weird sometimes. all is figured out. thanks guys.
It kood just be the kernel
Sent from my Nexus S 4G using xda premium
I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!