Database Info

[Q] Asus Slider Stock Kernel

Hi,
im wondering if someone can help me out.
I made a nandroid and installed a custom rom with custom kernel (Krakd) all worked great and am still toying around with it and want to go back to stock kernel. I put back the nandroid but am still on the roach kernel i found out that the CWM still doesnt backup the boot but will in a future version which i found out too late. Is there anyone who can get me a zip for CWM so i can put back the stock kernel for 8.6.5.18 ? Its the WW SL101 i have.
Thanks in advance.

HellsAngel_NL said:
Hi,
im wondering if someone can help me out.
I made a nandroid and installed a custom rom with custom kernel (Krakd) all worked great and am still toying around with it and want to go back to stock kernel. I put back the nandroid but am still on the roach kernel i found out that the CWM still doesnt backup the boot but will in a future version which i found out too late. Is there anyone who can get me a zip for CWM so i can put back the stock kernel for 8.6.5.18 ? Its the WW SL101 i have.
Thanks in advance.
Click to expand...
Click to collapse
did you get the stock kernel? I need the stock kernel too...
Or known some custom rom version that have no problems with the slider.
I tried the Revolver 3.9.5 but It can boot on my slider...
Thank you!!!

Does anybody have the stock kernel for the ASUS Slider ICS?
I tried flashing a Transformer Cyangoenmod and then flashing the Slider Comparability ZIP on top of that but there are too many problems. So, I reinstalled the backup I made before this started, but my tablet still says it is on the Cyanogenmod kernel.
Does anybody have the stock kernel for the ASUS Slider for ICS, know where I can download it, or would be willing to compile it for me from the ASUS website?
Thank you!
Chris Williams

I'm going to bump my thread with a little updated info.
I tried to flash the latest Stock ROM from the ASUS website by installing it on the MicroSD card. It installed just fine but it did NOT overwrite/update the Kernel so it's still trying to use the Kernel written by cyanogenMOD for the Asus Transformer.
The source code for the ASUS Slider Kernel is available on the ASUS website. I don't have enough posts to directly link to it yet unfortunately.
I do not have the expertise to take the stock source code for the kernel and compile it into something I can flash onto my tablet through ClockworkMOD. Can I please beg/donate to somebody to compile this for me? It's been asked for a few times throughout different forums so I'm sure it would benefit more than just myself.
Thank you,
Chris Williams

If I have time today I'll dl and compile it, I'm sure its in a thread somewhere though.
Otherwise you can flash Guevor's kernel which works great with stock

Thanks Thing-O-Doom. I'll be happy to be back on the stock kernel since the stock ROM is pretty darn close to vanilla Android and by rooting I've got the few functions I do use that are "advanced."
Do you know if Guevor's kernel works with the ASUS Slider also or is it just for the Transformer?
Thanks,
Chris

Bumping my thread with updated info.
I was experiencing a booting problem where the tablet was booting into ClockworkMOD by default but I didn't think the problems were related... they were. Because upon reboot it was going directly into ClockworkMOD it was not allowing ANY new install process to work. I discovered this when I tried to flash Guevor's latest kernel and it STILL said CyanogenMOD. Imagine my surprise.
So, I got the booting problem corrected and sure enough the new kernel installed just fine and appears to be okay for the moment so I'm back to having a functioning tablet. Yay!
If somebody would still be willing to compile the stock ASUS Slider Kernel for me and post it I will gladly donate to them. While Guevor's kernel does work I would prefer to be back on the Stock Kernel designed specifically for the tablet.
Thank you,
Chris

Voodoo Lagfix and others after GB Update?

Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?

You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.

shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.

now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?

By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.

trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.

hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?

Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium

Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?

Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip

Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again

I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.

KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.

Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.

It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!

I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app

KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?

iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.

trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium

Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.

[Q] nvflash, blob, and getting back to tf101

Ok after trying the 3g disabler and the market fix, and flashing 3 different roms i was never able to get my transformer back to tf101 instead of tf101g. i was told i could use nvflash to do so but so far ive only ever used nvflash to unbrick. if i download the nvflashable version of prime will this be all that is needed to restore me back to tf101 or do i need to edit something before flashing?

you can use nvflash stock as it wipes everything and you dont have to use the version of prime the unbricking thread references you can use any nvflashable rom

understood
ok. i understand that part. i can flash the rom but what must be done to get back to tf101? i flashed prime using nvflash and still my tf is showing tf101g in about tablet. this is wrong and im looking for a fix.

build.prop
I have revolver 3.9.5 too, and giving a look to the build.prop file I see some rows that can be interesting:
"ro.pad.features.modem=true" (my last line of the file)
"3g.picasso=true" (a bit above)
I haven't tried to set those to "false" because I don't need that, but maybe it can somehow help.

also i just flashed earlier versions on prime but still no change... could really use some help with this.

if i install the stock rom from the asus website will would this restore my model number back to tf101 or would this cause problems coming from a rooted custom rom?

You could try the repacked stock ROM
http://forum.xda-developers.com/showthread.php?t=1154947
Same here but repacked without the SU apk
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/

ok i flashed the repacked stock rom and that took me back to tf101. so i flashed back to prime and back to tf101g. what is it about prime that changes the model number and why would it be setup that way. i want to use prime but i dont want to change wha ever maakes my tf101 show as a tf101g. can someone elaborate on what causes this and how to fix it.

Freemantig said:
ok i flashed the repacked stock rom and that took me back to tf101. so i flashed back to prime and back to tf101g. what is it about prime that changes the model number and why would it be setup that way. i want to use prime but i dont want to change wha ever maakes my tf101 show as a tf101g. can someone elaborate on what causes this and how to fix it.
Click to expand...
Click to collapse
That's really weird, I've been on Prime since 1.4 or so and never got that.

Yeah I know. It just started the other day when I flashed from are to prime.
Sent from my Liberty using Tapatalk

[Q] Rom Flash - Gummy or CM9

Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Some notes:
I was the the newest CWM Recovery Version
I checked all the MD5 and they all aligned perfectly
Thanks for any help I receive, if you want to know something else about my phone data during this procedure, just let me know.

so you flashed back to.33 or .608 before you flash cm9?
Sent from my DROID2 GLOBAL using xda premium

odnanreh12 said:
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Click to expand...
Click to collapse
Hexen was made for 2.4.x stock firmware (Android 2.2 and the corresponding Motorola kernel).
All newer ROMs (CM7, CM9, Gummy, Apex, etc.) are based on 4.5.x. Update to 4.5.608 (preferably via SBF; do NOT accept any OTA updates once you're on 4.5.608) and proceed from there.

Ah thanks so much, I forgot that Android Firmware numbers had to match up, I will try again later tonight

forgot that Android Firmware numbers had to match up,
Click to expand...
Click to collapse
just fyi, not android firmware, moto's system version/firmware

Firmware must be watched
Sent from my GT-I9001 using xda premium

[Q] Would Samsung fix my bricked phone?

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!