Database Info

CWM Recovery

Hi I recently unlocked the bootloader and rooted (oneclick method) my HTC One X on rogers. I want to install CWM recovery, but I have heard it is unstable on the One X? If it's not, can I just download rom manager(premium) and flash the recovery through there? Or let me know a way I could install it. Thanks

jason.g said:
Hi I recently unlocked the bootloader and rooted (oneclick method) my HTC One X on rogers. I want to install CWM recovery, but I have heard it is unstable on the One X? If it's not, can I just download rom manager(premium) and flash the recovery through there? Or let me know a way I could install it. Thanks
Click to expand...
Click to collapse
I'd suggest using TWRP instead of CWM, CWM randomly wipes your SD from time to time.
To install TWRP, download the goo.im app from the play store and let it find a compatible recovery for your device. It will reboot and TWRP will be installed.

My advice would be to stick with the recovery installs methods that are in our specific forum. Just head to my index thread and look under "Recovery".
http://forum.xda-developers.com/showthread.php?t=1671237
CWM does not officially support our device, its just a port. Because of this, I don't even know if ROM Manager will let you install it.
More importantly, CWM is known to cause some serious issues for some people while flashing ROMs. Some (most?) of the devs don't advise using CWM. TWRP officially supports our device, and is the way to go.
---------- Post added at 03:04 PM ---------- Previous post was at 02:52 PM ----------
rohan32 said:
I'd suggest using TWRP instead of CWM, CWM randomly wipes your SD from time to time.
Click to expand...
Click to collapse
I've just had an instance of random files being erased or corrupted, this time it was on TWRP. I also had it happen on CWM a while back before I switched to TWRP, but neither recovery seems free of this bug (and may not be solely recovery's fault?). I've seen at least a few others have had SD contents corrupted by TWRP. Maybe its more common on CWM, but its probably hard to say.
I haven't had the instance of the entire SD card being wiped, so this may be a CWM exclusive thing, I can't say at all.
Moral of the story, before flashing anything, whether on CWM or TWRP, backup to your computer any contents of the SD that are not easily replaced. In particular, Titanium Backup folder, and any personal photos.
Also, aside from the SD wipe issue, CWM is known to cause some major problems when flashing some ROMs, so best to stay away from it.

rohan32 said:
I'd suggest using TWRP instead of CWM, CWM randomly wipes your SD from time to time.
To install TWRP, download the goo.im app from the play store and let it find a compatible recovery for your device. It will reboot and TWRP will be installed.
Click to expand...
Click to collapse
Does TWRP work the same as CWM. Also does it have all the same features as CWM? Thanks

I've been using clock work since its been available for the One X & personaly never had a single issue. You however can't flash CW through Rom manager.
Try this worked perfect for me.
http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att
Sent from my HTC One X using xda premium

[Q] Help with Rom Manager

Sorry for the noob questions but I can't seem to find a specific answer to my problem.
I am trying to create a backup of my stock Touchwiz ICS 4.0.4 using Rom manager premium v.5.0.2.1 so that I can flash CM10 to my Verizon S3. I have flashed the "ClockworkMod Recovery".
Current Recovery: ClockworkMod 6.0.1.2
Latest Recovery: ClockworkMod 6.0.1.2
Now when I try to "Backup Current ROM" my phone boots into a menu. I was under the impression that it should begin creating a Nandroid backup when I did this. It boots into Android system recovery <3e>
Word for word this is what I get
Volume up/down to move highlight:
Power button to select.
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition apply update from cache
_______________________________________________
# MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code : VZW
Succesfully applied multi-CSC
From there I didn't see an obvious Create backup type of option so I chose "Reboot system now" which then booted up normally. In Rom manger there is no file under Manage and Restore backups. Do I need to choose a different option in the boot menu. I could manually make a nandroid backup I think, but I'm not sure if it would work properly since I flashed the ClockworkMod Recovery.
Sorry, I am very new to this!

How did you flash your recovery? Was it through rom manager or through ez recovery?
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.

JBO1018 said:
Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.
Click to expand...
Click to collapse
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.

JBO1018 said:
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.
Click to expand...
Click to collapse
Good call!

I didn't see any mention of how he flashed his recovery, just assumed it was not through rom manager due to the issues he's having.
My experience with ez recovery made rom manager (an app I like alot) not work correctly. As soon as I re flashed through rom manager, all was well. Not knocking ez, just trying to get his rom manager app working for him.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

I am having the same problem. I flashed mine through Rom Manager also. It worked on the first reboot in recovery and has worked one other time in touch. Here's my thread. - http://forum.xda-developers.com/showthread.php?p=32795611#post32795611
Solutions?
If I install ez Recovery, how will that effect CWM?

I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

annoyingduck said:
I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
I got premium, I thought the same cause mine wont let me download roms either. It tells me to upgrade to the latest version.
Should we maybe uninstall and try a different install method, such as yours. Would there be any consequences?

I don't see any issues with that. To get touch through RM, there are 2 ways. One is in app purchase (don't do this, it's a one time, one use add on. Does not stay if you install a different recovery. Kind of a scam). The other is in RM you can link directly to cwm site and dl the apk for free. Just be sure you get the one for our phone, the site page is a little weird to navigate. Then you have it forever.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises

This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1

kintwofan said:
This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.

travis.bridges10 said:
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.
Click to expand...
Click to collapse
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1

kintwofan said:
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.

travis.bridges10 said:
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.
Click to expand...
Click to collapse
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1

kintwofan said:
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got three more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
3. If I was to keep the stock ROM what happens with VZW OTA updates. Doesnt it mess things up. This last update has messed everything up for GS3's and I bet the next will have even more "restrictions"
Thanks again

travis.bridges10 said:
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got two more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
Thanks again
Click to expand...
Click to collapse
1. I don't use RM so can't be much help there.
2. I personally use titanium backup to back up and restore user apps. I don't recommend restoring system settings.
Sent from my S3 running Eclipse 2.1
---------- Post added at 09:02 PM ---------- Previous post was at 08:52 PM ----------
One either thing make sure you backup your imie...there's a guide in the development section.
Sent from my S3 running Eclipse 2.1

I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app

travis.bridges10 said:
I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good. I don't remember seeing that option, but I've been rooted for a while.
Sent from my S3 running Eclipse 2.1

Why does Odin say passed, but CWM not there?

Ok, so i installed rom manager to install CWM, then i used odin to flash CWM touch, and it passed, rebooted phone fine, but when i enter recovery its the stock recovery, not CWM, any idea?

I cannot provide insight on why Odin did not successfully flash the CWM recovery as I have not flashed anything but official software with Odin but I highly reccommend using the app in the playstore called GS3 E Z Recovery to flash a custom recovery (after you have unlocked of course).
This is the cleanest way to do it IMHO.

thrgk said:
Ok, so i installed rom manager to install CWM, then i used odin to flash CWM touch, and it passed, rebooted phone fine, but when i enter recovery its the stock recovery, not CWM, any idea?
Click to expand...
Click to collapse
Because there are two scripts that need to be renamed. They replace the custom recovery with the stock recovery on every reboot. They are
System/recovery-from-boot.p
System/etc/install-recovery.sh
These need to be renamed with
.bak added to the end of them. Then u can flash CWM with odin and it will stick once u boot up.
You can also flash CWM and not let the phone boot up and then mount /system and use adb to rename the files. Whatever works best for you.
Sent from my SCH-I535 using xda premium

Why did you use Odin if you already used Rom Manager? Rom manager will completely take care of recovery for you. Like others, I've only used Odin to go completely back to stock.
Open Rom Manager, and click the top "flash cwm recovery" for the regular version, or even better click the flash cwm touch version (donate like 1.99 I think). Done
And FYI, there are lots of problems with ez-recovery versions....I'd stay away from it for now.....

TechSavvy2 said:
Why did you use Odin if you already used Rom Manager? Rom manager will completely take care of recovery for you. Like others, I've only used Odin to go completely back to stock.
Open Rom Manager, and click the top "flash cwm recovery" for the regular version, or even better click the flash cwm touch version (donate like 1.99 I think). Done
And FYI, there are lots of problems with ez-recovery versions....I'd stay away from it for now.....
Click to expand...
Click to collapse
There's no issues with EZ Recovery that I've run into. Its the EZ-Unlock that the newest versions don't work right, you have to use 1.2.
OP, here's the link to the latest CWM Touch that can be flashed with EZ Recovery(I just did it yesterday and it worked fine) https://www.dropbox.com/s/aqnnl5j8xc2u0ah/recovery-clockwork-touch-6.0.1.2-d2vzw.img

I agree with brian, use ez recovery to flash recovery of choice. Stay away from rom manager or any of those apps until you have a better idea of what your doing.

[Q] CWM Touch Issue

I first want to start off that I am brand new to all of this. I have been reading up about this for a while and finally decided to root my Galaxy S3 the other night. I followed the instructions by Phone Rebel in his Youtube video. I used these files: Download and Install Samsung Official USB Drivers - Link
Download and extract ODIN v3.07 - Link
Download the Zip Below
For Both Root and Unlocked Bootloader ***RECOMMENDED*** – Download SuperSU + Unlocked Bootloader to your SD Card - Link
Download the VRALEC Bootchain - Link
Download one of the below
For ClockworkMod Touch Recovery 6.0.1.2 (Download this to your computer) - Link
For TWRP Recovery 2.3.1.0 (Download this to your computer) - Link
Download the VRBLK3 Bootchain - Link
After completing the root, it automatically installed SuperSU. (not quite sure what it does, again, i'm very new to all of this) After reading up on what to do after you root, I read that it is a good idea to download ROM Manager as well as Mobile ODIN. I installed both, difference being I bought Mobile ODIN Pro.
Using ROM Manager, I tried flashing CWM Touch, I was successful in doing so. However, when I boot into recovery, I get a message stating that ROM will flash back to stock after boot. Do you want to fix? Yes= this can not be undone. No. Or Go Back. I was scared to press yes because I didn't know what it would do. I have not installed any custom ROM because I'm not 100% sure on how to do it so I am not going to take the plung until I know.
Any suggestions or answrs on how to fix this issue would be appreciated. I do want to flash a custom ROM like Cyanogenmod. I've just read that it's a really good custom ROM. Any ROM suggestions will be greatly appreciated as well.
Also, I've read that you have to back up IEML or IMEL? ( I probably butchered that all up, again i'm sorry) I have Titanium Backup, can i do it with that? And if you install a custom ROM do you have to do a wipe of your phone? If so, how do i do that? And if Verizon releases another OTA update, can I accept it or will it brick my device?
Thank you in advance for all your help.

It will ask disable stock recovery flash. You have to say yes else it will flash stock recovery and you will loose the cwm touch recovery which you flashed.
Thanks doesn't hurt....
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
As for the imei backup, you can not use Titanium Backup. There is a thread which talks about the imei backup and restore process. Try searching for it.
Thanks doesn't hurt....

[Q] Rom question regarding Lollipop.

Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin

IVS IVRIS said:
Hello guys,
I'm still relatively new to rooting stuff on the Nexus 5 (and 7). Running a rooted stock android 4.4.4. with Franco kernal, but with Lollipop now available.. Of course I want to upgrade. I am looking for a stock android 5 rom with prepoot. Is there a prerooted rom available? And do I have to flash stock kernal first before flashing the rom?
Thanks in advance!
Justin
Click to expand...
Click to collapse
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img

rootSU said:
Not exactly no. L root is different from KitKat. You have to flash a permissive boot.img (kernel) before flashing SuperSU in recovery.
There are flashable zips. There is one linked in the "guides and info" link in my signatrue (see section 6)... But you still need to flash the chainfire or @sykopompos Permissive boot.img
Click to expand...
Click to collapse
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?

IVS IVRIS said:
Thank you for the quick reply. The rom over here: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 may suit my needs indeed. Although he's saying "-Don't install SuperSU (won't work, must use CF-Auto-Root)"
So, in my situation.. what I should do would be:
Factory reset
Flash rom with TWRP (my recovery)
Flash radio
Use the latest CF-Auto Root (for Lollipop)
Do I keep my Franco kernal?
Click to expand...
Click to collapse
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then

rootSU said:
I wouldn't use CF autoroot myself. Its similar to a toolkit which we don't recommend.
All you do is flash ROM.zip
Flash Permissive boot.img (kernel)
Flash Elemental X kernal
Flash SuperSU (It will work in this case)
I'll see if I can find a link to @sykopompos boot image
No, I don't believe franco will work. I would recommend trying ElementalX though. You flash it after the permissive boot.img. You jeep the permnissive stuff as ElementalX doesn't replace RAMdisk (just modifies it) so you get best of both worlds.
Plus ElementalX is a great kernel. You'll also be running teh same setup as me then
Click to expand...
Click to collapse
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash Elemental X kernal
Flash SuperSU
Then reboot
Is that the correct way?

IVS IVRIS said:
Thanks allot for the explanation! Alright, to do:
Put rom on internal memory
Boot into TWRP recovery
Whipe everything, cache, system etc.
Flash the rom
Flash the radio
Flash permissive boot.img
Flash SuperSU
Then reboot
Is that the correct way?
Click to expand...
Click to collapse
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003

Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
UPDATE-SuperSU-v2.01 (SuperSU)
ElementalX-N5-2.03 (ElementalX)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?

rootSU said:
Yep, hold on on that, let me source the link.
---------- Post added at 04:33 PM ---------- Previous post was at 04:23 PM ----------
Search the OP of this thread for "modified kernel"
http://forum.xda-developers.com/google-nexus-5/general/rom-n5-l-developer-preview-t2796003
Click to expand...
Click to collapse
Sorry for bothering.. I think I've got everything setup up.
I've downloaded the files:
bigxie_hammerhead_LRX21O-signed.zip (rom)
LGD820_LRX21O_RADIO.zip (radio)
N5_+LPX13D_ModifiedKernel (modified kernal)
ElementalX-N5-2.03 (ElementalX)
UPDATE-SuperSU-v2.01 (SuperSU)
Is it correct to flash it in this order? Did I get all the steps? The files I have downloaded are partially for L developer (such as SuperSU) preview.. does that matter? I also see reports of sd card not showing up.. any problems ahead?

Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..

IVS IVRIS said:
Guys, I got myself in some real trouble I think.
First of all:
I came from 4.4.4. stock rooted with Franco kernal
I did make a backup in TWRP, files are on my pc.
Process:
First of all, I did a factory reset in TWRP
I flashed the rom, radio, kernal for root and supersu.
First boot went fine, although WiFi couldn't be found.
I decided to boot into recovery again to wipe my SD Card
Upon rebooting, phone is looking all black without a real 'launcher', sd card not found etc.
Than:
I managed to push rom, radio, kernal and supersu to /sdcard by adb in rocovery mode
I reflashed all of these, but the same problems occur
What should I do now? I'm ****ting my pants..
Click to expand...
Click to collapse
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.

Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.

jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
Sounds exactly like me indeed. Anyone knows the steps to help us?

galakanokis said:
Try updating TWRP to 2.8.1.0. Wipe system/data/cache/dalvik under advanced and then flash the ROM.
Sorry, only way I know how to flash a recovery is with fastboot, no zips...
Or fastboot flash the factory image but do each img separately as I hear there are still issues using the flash.all script when it comes to the system image.
Click to expand...
Click to collapse
Will this fix the sd card as well?

Are people having the same problem with clockworks recovery mod?

jeky82 said:
Exactly same problem here, using the same rom. I only flashed the rom. All was fine in the first boot. The problem appeared after I formatted the sd card recovery TWRP version 2.8.0.1.. I tried also to reflash the rom with a full wipe from recovery, but nothing .. black background, no navigation bar, no sdcard and no sim is found.
Click to expand...
Click to collapse
I fixed it! Please check this post: http://forum.xda-developers.com/showpost.php?p=56743199&postcount=10 and follow the instructions.. you may have to flash the seperate .img files though, like I had to.