yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] HANDSY:
Read thread see if any users from your region recommend a particular modem. Or just flash a selection and use a signal strength monitor app to find best for your area. Takes a while but well worth it
[Galaxy S II Q&A, Help & Troubleshooting] Phil3759:
First try wipe cache also, from stock recovery
[Galaxy S II Q&A, Help & Troubleshooting] theunderling:
Did you bother reading what I posted.I knew nothing about modems for that rom until I spoke to that chap I mentioned.He'll advise you the range of modems to install and the preferred method of flashing(ie pc rather than phone).
[Galaxy S II Q&A, Help & Troubleshooting] chiko2490:
THANKS for evry one first of all...

i have tried to flush a lot of modems used in my area and yet i see no change soo im

not sure that the modem is the problem... and im still having the same problem with the internet conection (3g)

also ive contected the that chap and im still wating for an ansawer from him ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diablo900t:
I'm still a noob when it comes to flashing kernels, and I tried flashing the Siyah kernel and my phone wouldn't boot. I flashed back to stock, and now whenever I try and enable wifi, nothing happens. Tapping the icon in notification causes it to "blink" but never turn on. Not sure what I'm missing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rybean:
Try this. this is from a AOKP ROM I used.

WARNING: This kernel has updated WIFI and Bluetooth drivers. If you are going back to stock, you need to get those drivers back or those 2 devices will not work. Simply flashing a kernel will not do it unless it also flashs back those drivers (they are in "/system/lib/modules" folder).

Or you can just flash this:

http://xdaforums.com/atta...8&d=1341720006
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evilmonkey1987:
Wait a second...what has updated bluetooth and wifi drivers? I'm having a terrible time with bluetooth, so if there is an updated driver somewhere out there, I want to know about it. Please link. Thank you!

EDIT: This is my thread. Please post the link there. Thank you.

EDIT: Found the updated kernel here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Yeah happens to me all the time.many roms don't have kernel with them even some stock so reflash either the seperate stock kernel file or another custom kernel right aftercu flash back to stock. Works for me every time!
[LG Optimus 3D] insestito:
Hi! This is the Acura Kernel for CyanogenMod or CyanogenMod Mod as Lewa Rom.

For me is the best kernel for Cyanogenmod, have a lot of features of the the great chef ACURA, from htcspain.

FEATURES:

- Updated all the kernel libraries.

- Oc to 1,300

- New frequencies added

- New Voltage

- Undervolt

- Minimum Frequency 100

- Frequency Series Max 1.3 GHz

- Ram at 450 MHz

- Bluetooth Settings

- Default Dealine

- Everything native EXT4

- Baseband Libraries Update

- Local Settings AND MORE ...

DOWNLOAD:

http://content.wuala.com/contents/infernum/Kernels/Kernel(AcuraTeam-LeWa).zip

HOW TO FLASH:

BEFORE FLASHING!: backing up of your applications and others with some program.

Log in recovery and make data / factory reset

wipe cache

Dalvik wipe

Now flash the kernel.

And does the super user

now restore applications and other

Original thread: http://www.htcspain.com/roms-lg-optimus-3d-384/acurateam-lewa-v1-espanol-53623/
[LG Optimus 3D] schubeir:
Does this have 3D / HDMI? ( I hope so, as CMs do not have the 3D / HDMI features)

schubeir

the answer is no!!!! just realised that from the original spanish post.
[LG Optimus 3D] Kaleptik:
Just so you know, kernels don't control 3D.

HDMI to an extent only.
[LG Optimus 3D] sketch2k278:
screenshots? and since this being a cyanogen type rom dare I ask about the wifi? is it stable?
[LG Optimus 3D] rezzsha:
sketch2k278, this is the kernel ONLY, so you cant really show screenshots, thats more for roms.
[LG Optimus 3D] roxito:
I have pandaballs CM 7.2+ U jelly v1.6 but when I put your kernel I lost root,and I cant install su again.

Sent from my LG-P920
[LG Optimus 3D] insestito:
:S

It's true...

I don't know why...
[LG Optimus 3D] pandaball:
I want to meet the person who packaged this kernel and slap him.

Try the package attached. Not sure if it will work, just quickly fixed the cwm zip to remove unnecessary flashing steps.

No idea how/why this breaks root. Nothing I saw can break root, unless it's kernel related (very unlikely).
[LG Optimus 3D] roxito:
No it doesnt work .no root.never mind i will stay as it is.

Sent from my LG-P920
[LG Optimus 3D] pandaball:
How does it break root? su missing? Busybox missing? Superuser.apk missing?
[LG Optimus 3D] roxito:
SU is missing.I open supersu and it says no su found.I unistall supersu and install it again but its the same.I made a folder with system/bin inside the zip with the kernel but nothing.
[LG Optimus 3D] ffteixeira:
Bluetooth problems. Not turn on bluetooth. Very fast and fluid. Great job.

Tested with cm-7-20120729-NIGHTLY-p920 and cm-7-stable.
[LG Optimus 3D] insestito:
I asked the creator, to see what he says ...
[LG Optimus 3D] pandaball:
Download the su flashable from here and flash it, see if it works: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
[LG Optimus 3D] infernum:
This is q beta kernel, is normal to fault...
[LG Optimus 3D] roxito:
No, I did that already it doesnt work.thanks anyway pandaball.I will wait for your next cm rom.

Sent from my LG-P920
[LG Optimus 3D] pandaball:
The su binary doesn't flash properly?

In any case, I would advise people to stay away from this kernel given that it doesn't like root a lot.
[LG Optimus 3D] roxito:
No it flashes ok but when I open superuser it says no su found.I go to system/ bin and its there.nevermind.hope for an update from your side for cm 7.2+ when you have time

Sent from my LG-P920
[LG Optimus 3D] insestito:
I know how you fix the problem of SU!

Look the first post
[LG Optimus 3D] speedyranger:
now work...i just install it. is the first time i install cm:p
[LG Optimus 3D] roxito:
how did you make it to work.I did everything as in the first post and nothing no superuser.
[LG Optimus 3D] insestito:
See all the instructions
[LG Optimus 3D] speedyranger:
nothing to special. i install normaly.

i have root and this work.

for permissions of /data and /data/app: must add to zip the root explorer, before install.

now with root explorer can change thats permissions and everything is right.
[LG Optimus 3D] roxito:
I tried EVERYTHING i cant get it to work no superuser.my nervessssssssssssss.
[LG Optimus 3D] bigfoot.kom:
Would be nice to use/try this kernel. Ok... it does work but without superuser permisions. They say follow the directions.

Step one, back up. Ok got it.

Step two, wipe cache. Good.

Step three, wipe dalvic. Got it.

Step four, factory reset. Easy.

Step five, flash kernel. Ok.

Now for...

Step six? "and does the superuser" what does this mean? could this step be the mistake?

Just wondering.
[LG Optimus 3D] insestito:
that means that you would have to run the superuser
[LG Optimus 3D] bigfoot.kom:
Thank you for the response. Did that, no luck.
[LG Optimus 3D] bigfoot.kom:
How does this kernel delete su binary so it is not found. I tried to install super su and it found no binary on a rooted cyanogenmod? Hmm?
[LG Optimus 3D] Pesach85:
I checked the last 14/10/2012 CM with this kernel! Really fast but no root permissions!

With quadrant i had a I/O score of 9200 points!

Anyway the CPU is not optimized as the promethius 1.5+ kernel does, could be useful to take some inspirations from it :)

-------

Edit: to make the root work just install manually with android commander or analog method, the su file in /system/bin :)

Ok all works fine great work!

-----

I don't know why but after the Fixed su my phone had 3866 total score with quadrant :) The CPU score was similar to the promethius kernel CPU score :)
[LG Optimus 3D] yourguitarist:
What do you install manually? The kernel or su?
[LG Optimus 3D] Pesach85:
The su
[LG Optimus 3D] yourguitarist:
Can you pm me a guide on how to do that?
[LG Optimus 3D] Pesach85:
Ok, have you ever used Android Commander?

http://xdaforums.com/showthread.php?t=597098

To work is needed sdk platform, so after you install android commander will be required to choose the adb folder into the sdk installation.

You need to find a su file, you could just copy the one you should already have in /system/xbin or download it form the official page taking it form the archive.

After you can start android commander: on the left you have a windows with your local files, on the right your android files, in both you can navigate into folders.

You need to copy from your /system/xbin folder the su file through the copy command located just up the right window and after in left window you choose a local folder where to put it.

In the right windows locate the /system/bin folder, then, up the left window you have the left copy command (which brings files into android): use it bringing the working su into the /system/bin folder.

Close android commander and now superuser should work.

WARNING: this method need to be done again after reboot, so i guess should be removed SOME STUFF which overwrite at every reboot the file.
[LG Optimus 3D] ima.monstaaa:
Using this kernel on CM7 10-14 and had no problems with superuser. I installed after wiping cache and dalvik and everything worked perfectly. Thanks for the work.
[HTC EVO 3D] rennard:
Hi,

I just would like a complete guide as to how to be able to install "root apps" to my gsm evo 3d, I'm not bothered about new roms or anything like that, I just would like to install something like setCpu etc. My hboot is 1.5. and I have no idea what I'm doing!

Thanks
[HTC EVO 3D] sitlet:
Well, root apps are installed like any other app. Download the app from the Market (play store), and install it, that simple.
[HTC EVO 3D] coal686:
Also, you have to be on a rooted ROM so that when you run the root app, you can give it Superuser permissions.

Save the Drama for your Mama with Tapatalk 2
[Xoom Q&A, Help & Troubleshooting] wesamothman:
Couldn't expect less from you. Super great guide...
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Post reserved for updates in case the initial post gets too large...
[Xoom Q&A, Help & Troubleshooting] Cubanluke88:
I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Thanks for your words...

In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).

"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".

Thanks.

--
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Updated with some pictures :)
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Updated with links to v141...
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
eos 6 recovery.img not available

the recovery image file is not available in the link..could you update the link. Thank You !

Great tutorial :)
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

According to this URL, EOS6 RECOVERY.IMG has been deprecated:

http://xdaforums.com/showthread.php?t=1604014

Now you can use Team Win Recovery Project 2.2, (TWRP):

http://xdaforums.com/showthread.php?t=1782235

Flashing is almost similar to EOS6 recovery method described above, just check the last link.
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
wow that was a quick reply.. THANKS (Y)
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).

I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
Same method for stock ics?

Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?

Thanks !
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
Help !!! In a lot of trouble

I flashed the twrp recovery and then it rebooted..everything was perfect till that point

then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.

I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.

Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)

please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?

HELP !!!!
[Xoom Q&A, Help & Troubleshooting] wesamothman:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.

May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?

because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
[Xoom Q&A, Help & Troubleshooting] wesamothman:
First time ROM flashing is longer than normal booting, like 5 min ,

If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Did you finally succeded "booting" EOS3?
[Xoom Q&A, Help & Troubleshooting] kakrikakri:
Yes it did and it works perfectly

Thank you NoP_Compiler and wesamothman
[Xoom Q&A, Help & Troubleshooting] dazbeach71:
Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup :)
[Xoom Q&A, Help & Troubleshooting] themonman:
dead android in step 2

Hi,

Thanks for the great tutorial.

I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"

In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.

Any idea about what I might be missing?

thanks!
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Sorry, it never happened to me.

If it's an specific TWRP problem, please, ask in the TWRP thread and let's see if their creators can help.

I flashed it without problems, starting with EOS6 RECOVERY and flashing it via CWM ZIP (not directly via adb).
[Xoom Q&A, Help & Troubleshooting] evioulsyr:
Thank you!!!Super great guide!!!
[Xoom Q&A, Help & Troubleshooting] rogerodd:
thank you for a REALLY GOOD NOOB GUIDE!!!
[Xoom Q&A, Help & Troubleshooting] furball2457:
thank you

thank you for a great guide ^_^

here is a link to new recovery.img i had to use because EOS-RECOVERY-V6 no longer exists:

http://xdaforums.com/showthread.php?t=1782235

It work like a charm using touch screen selection (no more vol up/vol down browsing)
[Xoom Q&A, Help & Troubleshooting] EliBsora:
another dead droid

the os works well but after flashing the recovery i get a dead droid, i think that i did something wrong with your tutorial because all the recoveries do the same thing,

i can go into some kind of limited menu that looks like the android default recovery but it doesnt even recognize my sd card.

i cant post a link yet, so look for "trying to activate my xoom recovery via cmd" on youtube,

thank you.
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

What nightly version did you flashed? Please note that this tutorial is for EOS3 (nightly <= 155) and not for EOS4 (nightly >= 156)...

At least ... did you managed to flash the recovery itself?

EOS4 needs a different recovery (TRWP) to flash the ROM image...

You can try asking here:

http://xdaforums.com/showthread.php?t=1764751&page=93
[Xoom Q&A, Help & Troubleshooting] EliBsora:
still cant flash recovery

that is the problem - i did not get to that part - i am still on part 1 of your tutorial, i cant install recovery. it flashes and doesnt load, i have tried 3 diffrent recoveries and they all crash.

thanx
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Maybe you've correctly flashed it but you're not doing the right key combinations to enter the installed recovery...

--
[Xoom Q&A, Help & Troubleshooting] wooly1:
Now that the warranty on my Xoom is close to expiry, I am getting excited about installing a new ROM and have been looking at various guides by way of doing my homework before I start.

In part 1 I note that after the fastboot flash recovery.img command is issued, the instruction seems to be to let the device completely reboot to the OS and then to enter recovery.

***********************

Code:

fastboot flash recovery eos-recovery-r6.img

You will see something like:

Code:

C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>

fastboot flash recovery eos-recovery-r6.img

sending 'recovery' (4114 KB)...

OKAY [ 0.499s]

writing 'recovery'...

OKAY [ 1.014s]

finished. total time: 1.529s

Check in the xoom's screen that the file was correctly written and execute:

Code:

fastboot reboot

You xoom will start again in Android OS mode. Execute:

Code:

adb reboot recovery

**********************

My impression was that allowing it to boot to the OS would overwrite the new recovery image with the old android one.

Other guides seem to suggest entering recovery by tapping the vol- button after rebooting.

Perhaps I lack some understanding of adb and fastboot commands, just trying to get this clear in my mind before I start.

I like this tutorial as it is very well detailed and seems easy to follow.

Thanks for any help in advance.
[Xoom Q&A, Help & Troubleshooting] EliBsora:
fixed it - dont let it reboot!

wooly1 is right, if the device reboots it overwrites the new recovery, i sort of figured it out and tried it and it worked, after the reboot command is given disconnect the cable connected to the pc and then enter recovery with the softkeys, after that everything worked like a charm!

thanks everyone! i have android 4.2 now on my xoom! this is amazing!
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Thanks all for pointing that, althought the initial procedure worked for me (!).

I've updated the tutorial with your comments (entering recovery mode directly after flashing) and with the v155 URL.

If anybody can explain here where to download TWRP (the exact required version for EOS4) and how it's flashed exactly, I can update the tutorial to cover both EOS3 and EOS4 or create a copy of this tutorial specific for EOS4.
[Xoom Q&A, Help & Troubleshooting] wooly1:
Thanks for your acceptance of my comments re your excellent tutorial.

No criticism intended, just trying to establish the facts.

Re using TWRP recovery the link you provided in post 9 is indeed the correct one and leads to v2.3.3.0 of the TWRP recovery which is the latest version and suitable for EOS 4.2 ans also EOS 3 variants.

If you look at post 406 in the link it is clearly stated that this TWRP version is now the one to use for all EOS nightlies.

http://xdaforums.com/showthread.php?t=1782235&page=9
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Don't worry, you don't have to "apologize", any help and correction is welcome! :good:

I'll save your message and when EOS4 becomes completely stable (I'll wait about 1-2 months from now) I'll update from v155 to EOS4 and I'll write a new post as a new tutorial, using TWRP and the link you provided.

Thanks! :)
[Xoom Q&A, Help & Troubleshooting] blocka:
Android Exclamation

Hi,

firstly this is a great guide, one of the best written I've seen!

I'm following your process to unlock, install recovery image etc etc.

I've done Part 1 successfully, well at least I think I have...but when it comes to part 2 and running Executing "adb reboot recovery" (I can't seem to do the manual method) I get a robot (a bit like bender from futurama) on his back with a red exclamation coming out of his chest. I can boot into the system but can't bring up the menu.

also can I install the clockwork recovery onto my device still?

Thanks!!!
[Xoom Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

Please, check the last update of the tutorial, as people pointed that you should not reboot the XOOM and make the "adb reboot recovery". You should reboot the xoom and enter recovery mode (first time) with the "hotkeys".
[Xoom Q&A, Help & Troubleshooting] blocka:
Thanks for your reply.

I've managed to get things happening via a mix of instructions. I couldn't get part 2 in your guide to stick and after reading some other posts I needed to ROOT first which sent me down another path see the links below....

1. Unlock boot loader using Part 1 from here http://xdaforums.com/show...php?p=29733454 (your guide)

2. ROOT using this guide http://xdaforums.com/show....php?t=1078019 (this is the stage where when I rebooted the device would only go as far as the Red M)

3. Install EOS Flash Part 3 from here http://xdaforums.com/show...php?p=29733454

I'm guessing now the stock ROM is now toast?

I'm not exactly sure just what happened and where it went pear shaped for me.

Cheers
[Xoom Q&A, Help & Troubleshooting] wooly1:
You do not need to root the device before using this guide because the TeamEOS ROMs are self rooting.

Not sure what went wrong for you, however, I would guess that your new recovery was overwritten by the old anroid one and you managed to get it to stick on the second go.

Yes, your stock ROM will be gone if you did not make a nandroid backup before installling the new ROM.

If you need stock again you will have to fastboot the stock images from Motorola.
[Xoom Q&A, Help & Troubleshooting] blocka:
Have another question, slightly off topic but still relevant.

I've been trying to backup my ROM now using ROM Manager but I'm getting an error from clockwork that it can't mount the sdcard..
[Xoom Q&A, Help & Troubleshooting] wooly1:
Can,t help too much with ROM Manager except to say that most queries I have read concerning it indicate that it is not compatible with most of the recoveries flashed to the Xoom.

Perhaps do a search for it on this site and also xoomforums.com
[Xoom Q&A, Help & Troubleshooting] blocka:
Wanted to confirm the DL site for the Stock Motorola Images with you I can't post the link yet 'cause I'm a new user but it's in the developer section, and secondly you mention EOS4 nightly >= v156 requires a slightly different procedure!!! You wouldn't have that handy?

Thanks again
[Xoom Q&A, Help & Troubleshooting] wooly1:
Motorola, for reasons best known to themselves, have removed the stock images from their website. There are, however, available to use elsewhere.

http://xdaforums.com/showthread.php?t=1049485

For installation instructions see post 3 of this link, I know it works as I have used myself

http://www.xoomforums.com/forum/mot...ooting-flashing-unrooting-under-one-roof.html

Not sure about iinstalling 156>

I think the only difference is the need to format/wipe the system partition when doing the wipes.
[Xoom Q&A, Help & Troubleshooting] blocka:
The first link you provided to the Motorola Images goes nowhere.... :eek: