Database Info

[ROM] TF101 Rooted Stock 9.2.1.17 + bootloader + modded recovery US and WW

This is a full rom for stock(ish) 9.2.1.17 and includes the following:
9.2.1.17 US bootloader and kernel/boot.img
modded recovery based on Roach's 3.2.0.1
Superuser
su binary
busybox
adb enabled, ro.secure=0 (if you previously disabled adb, it will remain disabled, unless you wipe data)
The updater script will also clear cache and dalvik cache.
Plus, if you flash now, it will also fix the cwm recovery bootloops by writing zeros to the first 80 bytes of /misc (/dev/block/mmcblk0p3)
I was lazy and the progress bar in recovery does not udpate- it is a full rom so it does take a while to flash.
This is pretty close to a rooted stock experience. It isn't for everyone, but I think some will find it useful. I thought this would help out people who get in in a pickle by flashing various roms and ending up with unbootable systems, or people who tried a few other roms and want to return to a more stock experience. I think a custom recovery is safer with a rooted rom so that flashing via recovery is still available. This should still receive OTA updates, but they will probably fail to flash because the build.prop file is different (ro.secure=0 and adb). This rom will flash in situations where doaist's CWM friendly updates will not. As a matter of fact, this rom will probably flash on any version of cwm/custom recovery that can read it.
The recovery is modded- it is based on Roach's 3.2.0.1 and only sees the external sd card. I used Roach's ramdisk, but used the the inits, fstab, and ueventd files from the stock recovery. This recovery will seem identical, but you can look at the default.prop to see the difference. In future versions, I might change the version number in case there is any confusion.
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
Flash at your own risk. I am not responsible for any damages or consequences.
ALL WARRANTIES REGARDING MERCHANTABILITY OR FITNESS OF PURPOSE, EXPRESSED OR IMPLIED, ARE DISCLAIMED.
Please thank Kuromera for hosting the files on a speedy server and check out the other files hosted there. See his thread here - http://forum.xda-developers.com/showthread.php?t=1549055
Download from here!
US version
ics_92117_stock_EBT_SOS.zip
MD5(ics_92117_stock_EBT_SOS.zip)= 201eae30cbeb00687d5cc69c14469027
WW version
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36
http://www.xdafileserver.nl/index.p...+(TF101)/ROMS/Stock+Roms+by+gee+one/With+Root

Alright, gonna try flash this from Revolution 3.0.1, gotta get back to .17, .11 is so unstable for me, random reboots and shutdowns, and I woke up this morning to a flat battery - from 100% before I went to bed...
Will report back inna bit!
+++
All good, thanks (and thanked)!

Flashed over Revolver 3.11, it automatically optimized the apps on first boot, so far so good.
The weather widget won't update my location, but I've had trouble with that on a lot of the stock firmwares. Could also be from the flash over revolver.
Anyways, thanks for the good work.

I'm very interested in a WW version of your update!!
Anything Ican do to help, just tell me, and I will try. But i might need a little guidingalong the way
Sent from my Transformer TF101 using xda premium

edit: OK, WW version should work now
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36

Having difficulties downloading.
I keep getting "download unsuccessful" If I download straight to the tab.
If I download on my PC the MD5 changes every time. File is listed as 300MB but shows up as 193MB???
Can anyone post a mediafire link?? Or anything.

Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055

If anyone is having problems downloading, I uploaded to Box:
I've shared a folder with you through Box.
To access this folder, visit the following link: https://www.box.com/shared/a479f50d578d27a355f9
Due to my account limitations, I had to upload it as a multi-part zip (6 50mb sections, and a tiny trailing 7th section)
Hope that helps!
Sent from my Transformer TF101 using xda premium

OK, WW version is uploaded. Sorry for the confusion.

Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?

gVibeR said:
Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?
Click to expand...
Click to collapse
This flashes through clockworkmod or any other custom recovery. I think there is a recovery installer.apk in the dev section, or there are nvflash versions of some of the custom recoveries.

gee one said:
Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055
Click to expand...
Click to collapse
Happens with both the US & WW versions. I watched the download stop at approx 190MB. Don't know what's causing it. I guess I'm the only one.

I';ll check the server hold on
Mmm cant see anything strange, the ww file and us file have both be downloaded succesfully allready but i'll keep watch. The server should support download managers btw.

gee one said:
This is a full rom for stock(ish) 9.2.1.17 and includes the following:
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
=====================
The WW version make the same, overwrite the bootloader and recovery?
Thanks
Click to expand...
Click to collapse

Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.

Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk

So far all fine.
Sound finally on the normal volume.
Reboots not seen yet. (too early to tell)
Only problem i had was busy box and super user but fixed it in the end.
WW version.
Cheers!

gee one said:
Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.
Click to expand...
Click to collapse
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado

No one can please post an NVFlashable rom of the WW version??
I only need the system and the boot part, as using a dual boot system i can only update via nvflash
PLEASEEEEE!!

AllanJacques said:
Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
ValenteL said:
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado
Click to expand...
Click to collapse
The bootloader gets updated with the OTA so I left it in to stay with the rooted stock experience. The bootloader I included is the one asus includes with their update. I'm not sure if other roms will be expecting older bootloaders. I think most nvflash versions use the oldest bootloader still, and I don't know if this will cause any issues. I don't foresee issues with other roms and kernels, although I did notice I had to wipe data completely to get some of the aosp roms to boot.
As I said, this is directed to someone who wants root and a more stock rom. You can edit system to debloat (and reinstall if you take too much out )
sent from my cyanogen(mod) vision

[Q] What exactly does ROM Manager's fake flash do?

Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.

yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
The problem with ROM Manager is that it messes up the files when flashing a ROM or any file. It is more advised to use CMW Recovery.

yuma80 said:
Simple question that I can't find an answer to...
What exactly does ROM Manager's flash option do? If it's a fake flash where does it write the recovery program to and how does it get the phone to boot it? I don't see any kind of update zip on either the internal or external SD so it must have written it to one of the partitions on the block device, but which one and what did it replace?
The phone is a Wind Mobile G2X not a T-Mobile and stock recovery is nothing more than factory reset + reboot. As far as I can tell it's still there and I can still get into it with power+volume-down at boot, so that's not what ROM Manager replaced I guess.
Click to expand...
Click to collapse
Rom Manager should not be used on the G2x. If you flash a rom and something goes wrong and you can not boot you are dead in the water. Use Nvidia CWM instead.
http://forum.xda-developers.com/showthread.php?t=1056847

Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...

yuma80 said:
Yes thanks. I understand that I shouldn't use ROM Manager, but I want to know what it does and why it doesn't work. For starters anybody know where it writes CWM to?
Worse comes to worse I'm just going to dump /dev/block/mmc* and look for strings or disassemble the apk or something...
Click to expand...
Click to collapse
I've always been curious about the details of a 'fake flash' too.. please let us know if you figure out any details.

Rom manager has been around since the original Droid from Verizon. The fake flash you refer to isn't actually a fake flash. It actually flashes CWM recovery. It just doesn't work on this particular phone. I may be wrong on the exact details but the G2x partitions and drivers require the use of NVflAsh to install the CWM. However, there are many phones that once they have been rooted, the user can install Rom Manager and use the Flash Recovery option to install their CWM recovery. There are also times when a particular recovery version (ie.. 5.0.5. Or 4.6.3) works better than another on one particular phone. Rom manager allows users an easy way of flashing between those CWM versions by simply pushing the flash button.
So in summary of a long response... it is only called a fake flash because it looks like it worked on our phone , but in fact it does not. We have to use NVflash to flash our recovery.
If it looks like I'm remotely right ( which I think I am..) hit that thanks button. (Shameless request, I know)

From my understanding, the "fake flash" that ROM Manager does is that it doesn't actually flash CWM like NVFlash does (on the recovery partition) but still puts the CWM files on your SD card saying that you do have it installed (sdcard/clockworkmod) so when you try to flash/install a ROM, it can't put it anywhere. I don't think it will flash anything, but people mess up their devices by wiping data/system and such...
OR...
Maybe it does flash CWM to your device but it has the partition tables all messed up?
One or the other lol, it's just a guess for both options but I believe the first one is right.

I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this

DorisTheHeavy said:
I've wondered for a while why rom manager is included in roms for the g2x when it's not advised to use it
Sent from this
Click to expand...
Click to collapse
To rename your nandroid backups .

buru898 said:
To rename your nandroid backups .
Click to expand...
Click to collapse
I never thought about that. I was always unsure what flashing CWM with ROM Manager would do when it's already on my phone using NVFlash.

Since our phones have a dual partition in it. I think it flashes to the internal 1 gig memory so then loading another rom writes over it.
Sent from my LG-P999 using xda premium

OK, I finally had some time to do some poking around. Some of this is guess-work since I was too lazy to verify 100% exactly what it does when you specify that you're running a G2X.
Anyway, in it's settings DB it says this phone's recovery partition is read-only, and there's no flash command set, so I guess it doesn't try to flash it directly. It looks like it's relying on the Google stock recovery image to do the flashing instead, so it downloads a recovery-update.zip to the SD card and writes a script to /cache/recovery and reboots the phone into recovery mode. Google stock recovery would execute the script in /cache/recovery, which says to apply recovery-update.zip, but the actual stock recovery on the phone is either not Google stock, or has been modified; it doesn't bother to execute scripts, it just does a factory-reset (clear /cache, /data, etc) so that's why it doesn't work.
Meanwhile, ROM Manager writes to it's DB that it just flashed CWM version X.Y.Z and happily displays that every time it runs, even though that's not true.
I used NVFlash and moved on with my life.

[Q] Summary / Overview - Upgrade to JB

Hi all,
I am farily new to Android and by reading the forum have been able to root and am using ClockWorkMod o my Galaxy Note 10.1 8013. I am pretty happy with all that
So now that JB is out, I went to settings on the Device and did the sofware updated. It download a ~500MB files, then rebooted into CWM which attempted to load the firmware. It then gave me a text error that looked like some code evaluation that was failing (sorry, I did not write it down)
I made backups of my device using CWM, both to the internal card and to the extsdcard. However the external backup failed becuase it could not access /data. I also created an update.zip on the intneral card.
I've read that I *might* be able to upgrade to JB via Kies, but I see a lot of problem posts with this.
So my questions are:
- What is the right/best way to upgrade to JB?
- Do I need to revert to stock firmware first?
- If the Kies process works, will that wipe my data?
- What is the best way to wipe my data and then restore it?
- If I create a full backup using CWM and restore it, does that backup include ICS (hence overwriting JB if I successfully upgrade)?
- I see the term ROM, firmware, OS tossed around alot; I know what these terms mean, but is there any difference, for instance I would think that both CWM and JB are firmware and ROMS and JB is the OS. So when people speak of ROM and firmware what are they really referring to?
- Will I lose all my data and apps and if so what is the best way to back them up and restore them? (I have both the CMW Backup and Titanium backups)
- Is there a cannonical reference for steps like this? It seems like there are alot of questions and suggestions but I cannot find a complete reference.
Thanks in advance. I apologize if this info is readily available in one spot. I've not found it yet.

Jon.Willard said:
Hi all,
So now that JB is out, I went to settings on the Device and did the sofware updated. It download a ~500MB files, then rebooted into CWM which attempted to load the firmware. It then gave me a text error that looked like some code evaluation that was failing (sorry, I did not write it down)
Root phones may fail OTA update .
So my questions are:
- What is the right/best way to upgrade to JB?
Samsung use Kies or OTA
- Do I need to revert to stock firmware first?
No if using Kies .
- If the Kies process works, will that wipe my data?
No
- What is the best way to wipe my data and then restore it?
CWM Recovery format data sd card .
- If I create a full backup using CWM and restore it, does that backup include ICS (hence overwriting JB if I successfully upgrade)?
Backup is whatever you backed up .
- I see the term ROM, firmware, OS tossed around alot; I know what these terms mean, but is there any difference, for instance I would think that both CWM and JB are firmware and ROMS and JB is the OS. So when people speak of ROM and firmware what are they really referring to?
CWM is advanced recovery not firmware .
OS is Android system .
Rom is a firmware of any type .
-
- Is there a cannonical reference for steps like this? It seems like there are alot of questions and suggestions but I cannot find a complete reference.
There are reference posts covering flashing and rooting .
http://forum.xda-developers.com/showthread.php?t=2080366
But as to a full guide no and as 99% refuse to read the basics faqs and guides i would not compile one .
jje
Click to expand...
Click to collapse

Well what you can do is download the JB stock firmware and then install it using Odin.
I would advice against installing OTA using CWM it is not a safe method.
Both the download link and tutorial can be found on the links in my signature

Thanks guys, this helped a lot
I used Kies to get JB installed, that wiped CWM and Root, so I just redid that process (a lot easier this time). So it seems like the 'Recovery mode' is a special boot firmware that can be used to load other firmware. So what I did was, downloaded and installed the new JB OS firmware which put the stock Recovery firmware back in place, upgrade the OS and left all my apps and data alone. Then I used ODIN to load the CWM firmware and then I applied the root software from the zip file. Sound like an accurate summary?
How does the root software actually work? I am familiar with froot on Unix but this seems different.

[Q] What's the best upgrade method?

I have my tablet still on ICS, locked, all stock ROM, except I used a root exploit for ICS to have root.
What I would like to know; what is the best method for me to be able to happily try out different ROM's without fluffing up and bricking my tablet?
I know I need to unlock, install customer recovery. Is NVFlash backup necessary?
I've also got a HTC Desire HD which I've flashed with many ROM's without ever running into issues.
The Asus TF300 seems different and I've seen too many posts where people have bricked their devices.

Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?

psjw12 said:
Is it true that flashing a ROM designed for one version of the bootloader, on a device with a different version will brick your device?
Also it is true that certain wipes from recovery brick your device?
Click to expand...
Click to collapse
Yes flashing a rom on a 4.2 bootloader that was made to work on a 4.1 bootloader will most likley cause a bootloop or a softbrick but should be able to be recovered in most cases.
The main cause of bricked devices atm is flashing the incorrect recovery for your bootloader version. This is flashing a non-4.2 recovery on a 4.2 bootloader, causes a fastboot flash brick - more info on this in my how-to in sig below.
I'm not sure about bricking your devices using wipes in recovery but the wipe data option in the bootloader menu will in most cases brick the device.
Not sure what the best method is but I pefer using the fastboot method over the twrp method but it's up to you, however the fastboot method does seem to work even with a locked device (but try at own risk).
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.

pjc21 said:
It's up to if you want to do the NVFlash backup, it is suposed to be a fail safe in case of brick, although this does seem to depend on how the device was bricked. ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
How is a fastboot flash brick caused?
pjc21 said:
If you need more info or would like a step-by-step on how to unlock and upgrade for your situation just let me know.
Click to expand...
Click to collapse
Thank you. I understand what to do but I don't feel confident. I've been happy flashing my HTC Desire HD for a long time and never had issues but I've seen so many bad stories on these forums it's really making me uncomfortable. I really want to go ahead and flash my device as it's slow and keeps crashing, and I want to be able to flash different ROM's without breaking a sweat. But I'd rather have a slow crashing device than a bricked one.

pjc21 said:
ie does not seem to work with the fastboot flash brick.
Click to expand...
Click to collapse
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.

EndlessDissent said:
Sources? I've never seen anyone with NVFlash even say they experienced any bricks. I don't see why it wouldn't be recoverable. As far as I've seen, everyone who succumbed to the "4.1 recovery on 4.2 bootloader" brick had no NVFlash backups. Unless you're talking about a different brick, in which case you lost me. NVFlash should work just fine with any brick. Unless you brick it while restoring your NVFlash backups, in which case, you're boned.
Click to expand...
Click to collapse
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
I agree with you that as long as you can boot to apx and have nvflash backup and don't brick during nvflash restore then you should be able to unbrick from any brick.
Sorry for any confusion here.

pjc21 said:
No sources, I was just going off a few comments in this thread but they don't state weather they did actually have nvflash backup or not, just that there was no fixing with nvflash.
Click to expand...
Click to collapse
Where? I went through the thread backwards from the last page back to page 7 or 8. Only one person even mentioned NVFlash, and he was asking if he could use NVFlash backups from a different tablet because he didn't have any of his own (that's not possible because of the way the bootloaders are signed). I also didn't see anyone actually tell him it wasn't possible. He was the third to last post in the thread.
So nobody in that thread (after page 7, anyway) said anything about NVFlash let alone that it doesn't work. NVFlash should work just fine to fix the fastboot bricks, just like any other brick.
Edit: So one other guy in a random post just kind of said NVFlash wouldn't work, nothing else - no details at all. A couple people asked him for details and proof, but he never replied. I have a feeling he meant NVFlash couldn't help because he didn't have any backups. If you have the NVFlash backups, you can recover from pretty much any brick.

Thank you guys for your help.
So does the following plan sound safe to you?
1. Backup my device (apps, data and sdcard)
2. Unlock with Asus unlock tool (v7 right?)
3. Do NVFlash Backup
4. Do official ASUS upgrade to JB 4.1 (I would do this by extracting the download from their site onto my SD card right? Because once unlocked I won't get offered any updates)
5. Once on JB, flash the correct 4.1 TWRP onto my recovery via Fastboot
6. Get Flash happy with my 4.1 compatible ROM's, do a few data wipes in between.

Sounds good to me. As long as you check version numbers and filenames carefully, there shouldn't be a problem.

What about on an Unlocked device
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?

teedoe said:
Back in March when Jelly Bean 4.2 came out I went from a rooted and unlocked machine to the newest stock os (10.6.1.8) I am looking to upgrade to the official 10.6.1.15.3 that is available on the ASUS site. Is it as simple as downloading the ASUS updateLauncher and putting it on my sd card and running it from the tablet? Or am I at risk being on an unlocked device, do I need to add any other steps?
Click to expand...
Click to collapse
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.

psjw12 said:
From what I know you should be able to upgrade from stock version to a newer stock version without any issues. The only thing I'm not sure about is if that method will wipe all your data. I'd advise a backup first.
Click to expand...
Click to collapse
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,

teedoe said:
Well now I am stuck, here is what I tried without success.
Backed up my data
Downloaded the newest file from ASUS - 10.6.1.15
Placed file on my internal SD
Renamed it to US_epad-user-10.6.1.15.3.zip
System Update is detected so I tried to run it from the OS - but it fails, gives me a Unknown Error (2) and restores itself to previous. I tried it twice with no luck.
Any idea how I can get this file to update.
Thanks,
Click to expand...
Click to collapse
Did you remove any apps or system files? If your ROM isn't 100% exactly stock before the update, the update will fail.

It was a simple mistake, I just needed to extract the zip file I downloaded from ASUS one time and then transfer it to my SD card. Worked perfectly after that and I did not lose any data or apps.
Thanks to all on the forums for your advice and help!

[Q] stuck in bootloop while installing elementalx.help!!!

i was installing elementalx on my nexus 5 via cwm. after going through the installer it asked if i wanted to fix root as i would lose it otherwise. i clicked yes. after that it started rebooting but got stuck on google. then went black. then again it showed google and is still looping. please help!!!

Try clearing cache by going to recovery.... Else my man you might need to flash stock again .....
To shutdown the phone press volume down and power till the time you get 3 vibrations

Dirty flash the ROM your on. What ROM did you flash EX on top of?

1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).

BirchBarlow said:
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
It was the other way round for me.... Twrp gave me issues .... I always use cwm touch .... Works good for me

i was on stock
BirchBarlow said:
1) Download and flash the latest TWRP recovery.
2) Reflash your ROM. (Wipe cache and Dalvik)
3) Reflash ElementalX.
4) Never use CWM again. (It's completely outdated and is problematic with Lollipop).
Click to expand...
Click to collapse
i am on stock so will i have to install the 5.0.1 factory image. also once in a while green screen comes asking whether to reboot or go into dload mode. also do i flash twrp before the factory image. can you tell me how this is done via pc as i was using flashify.

thanks guys
thanks guys it worked. i flashed stock and its working perfectly. thanks.

theesotericone said:
You know, it' funny. I keep hearing people say that but it still works fine for me. Maybe I'm just lucky. I've had way fewer issues with CWM than I've had with TWRP. There both good recoveries and TWRP is more current but to say CWM doesn't work is false.
Click to expand...
Click to collapse
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.

1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)

BirchBarlow said:
I didn't say it doesn't work, I said it's problematic. I believe CWM is built on JB, so incompatibilities exist with KK and LP. For example, when you exit CWM whether you are rooted or not, it will tell you that you have a problem with root and offer to fix it. This is because CWM can't detect the SuperSU binary, it doesn't search the right place. Therefore novice users will say select okay causing CWM to install an outdated version of the SuperSU binary into the wrong location causing all sorts of problems with KK or LP. This is just one example of why it's better to just avoid CWM. TWRP is current and backward compatible. CWM is practically ancient.
Click to expand...
Click to collapse
Lethargy said:
1. CWM lacks functionality
2. CWM uses outdated legacy location of /data/media rather than /data/media/0 as sdcard/internal storage
3. CWM's option to "fix root" actually breaks root (and possibly other things)
Click to expand...
Click to collapse
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.

theesotericone said:
I never really thought about it from a noob stand point so there is that. With me it works but I will stop publicly saying so after this post. You guys do bring up valid points and I'm just used to using it. TWRP back when had loads of issues so I steered very clear of it for a long time. Now it seems the tables are turned. I know eventually I'll have to make the switch but for now I'm still happy with playfulgods swipeable build of CWM. You both have my respect for trying to steer users down a more user friendly option.
Click to expand...
Click to collapse
Hey, what works for you, works (until it breaks, of course).
But for newer users, TWRP is now recommended as it's more friendly, as well as being up-to-date. CWM has had it's time.