Database Users

[Q] defy 2nd init

Can anyone outline a step by step instruction for using defy 2nd init and subsequently installing rdannar's latest MIUI rom?
I'm having trouble using it, and the defy forums weren't really helping..

syllogyking said:
Can anyone outline a step by step instruction for using defy 2nd init and subsequently installing rdannar's latest MIUI rom?
I'm having trouble using it, and the defy forums weren't really helping..
Click to expand...
Click to collapse
What rom are you using now?
Its very easy to use it.

Just download from market and install
Search in market for defy init
josuearisty said:
What rom are you using now?
Its very easy to use it.
Click to expand...
Click to collapse
Sent from my MB520 using XDA App

josuearisty said:
What rom are you using now?
Its very easy to use it.
Click to expand...
Click to collapse
Not gonna lie, this is my first rom install lol. I have v1.9 installed and have used titanium for my backup. I follow the instructions it says on the app and install the stable bootmenu. So, then I disabled USB debugging and rebooted (once blue LED came on) into the bootmenu. However, I'm stuck after that. Any help would be much appreciated.
rdannar's instructions below:
"1. DO NOT LEAVE RECOVERY MENU UNTIL YOU ARE COMPLETELY DONE WITH INSTALL (how do I know when I am completely done?)
2. download and place on sdcard (downloaded MUTT_rdannarV1, but when do I place on sdcard? unzipped/zipped?)
3. reboot into recovery menu
4. format data in recovery (what does this mean?)
5. wipe Dalvik in advanced menu of recovery
6. wipe Cache in recovery
7. choose install zip and click to install ROM
8. reboot and give it some time for first boot
9. IF ANY PROBLEMS with getting bootloader error then use the SBF called rdannarFIX in downloads and install like regular SBF"
Thank you
EDIT: Never mind, I figured it out. Experimentation is sometimes all you need hah. Thanks rdannar and all others for continued work and support.

[Q] Defy Plus 2.3.6 BL7 -WIUI install guide discrepancy(?)

Hello
I tried to install the WIUI rom - Stable GB+version - for Defy Plus ( my device is BL7 Android 2.3.6) today and encountered a discrepancy in the install guide pasted below.
1. Download 2ndinit 1.4.2-----> DONE
2. install 2ndinit (Important!:following the instructions)--->DONE
3. Boot into bootmenu by pressing volume down when device flashes a blue led at bootup. Set default boot mode to 2nd init.-----> DONE
4. (a) Select Recovery/Stable Recovery. ---->There is no such option available. The available options are :
1. Custom Recovery, &
2. Stock Recovery
------> So which option do we choose?
Did not proceed to the following stages
(b) Choose "Wipe Data/Cache" option. Let finish--->
5. Choose Install zip from SD Card, select WajkIUI_multilang .zip and let it finish.
6. select "Wipe Cache" then go to Advanced and select "Wipe Dalvik Cache". Reboot Now!
(If you are stuck on boot (Motorola logo), do 4th and 6th point again.)
7. After boot, set your prefered language in Settings menu
8. Done! Recommend: use Battery Calibration for maximum battery.
Anyone having installed WIUI on a device similar to mine and having faced the same confusion as me, willing to help ?
aCs
ps: I have encountered only one thread where such a problem is described and that person went the CM way rather than continue with WIUI. So if I have missed any thread detailing this problem and the solution please point me to it. Thanks

aCs_ND said:
Hello
I tried to install the WIUI rom - Stable GB+version - for Defy Plus ( my device is BL7 Android 2.3.6) today and encountered a discrepancy in the install guide pasted below.
1. Download 2ndinit 1.4.2-----> DONE
2. install 2ndinit (Important!:following the instructions)--->DONE
3. Boot into bootmenu by pressing volume down when device flashes a blue led at bootup. Set default boot mode to 2nd init.-----> DONE
4. (a) Select Recovery/Stable Recovery. ---->There is no such option available. The available options are :
1. Custom Recovery, &
2. Stock Recovery
------> So which option do we choose?
Did not proceed to the following stages
(b) Choose "Wipe Data/Cache" option. Let finish--->
5. Choose Install zip from SD Card, select WajkIUI_multilang .zip and let it finish.
6. select "Wipe Cache" then go to Advanced and select "Wipe Dalvik Cache". Reboot Now!
(If you are stuck on boot (Motorola logo), do 4th and 6th point again.)
7. After boot, set your prefered language in Settings menu
8. Done! Recommend: use Battery Calibration for maximum battery.
Anyone having installed WIUI on a device similar to mine and having faced the same confusion as me, willing to help ?
aCs
ps: I have encountered only one thread where such a problem is described and that person went the CM way rather than continue with WIUI. So if I have missed any thread detailing this problem and the solution please point me to it. Thanks
Click to expand...
Click to collapse
chose custom recovery and follow next steps.

Unsuccessful attempt
Method Followed: As indicated in WIUI Rom thread.
First discrepancy:
Select Recovery/Stable Recovery. ---->There is no such option available. The available options are :
1. Custom Recovery, &
2. Stock Recovery
So I chose Custom Recovery
Then again instructions followed per the thread:
Wipe Data stage
Message from install utility:
*Data wipe complete
*E: can't open /tmp/recovery.log
Wipe Cache Stage
Message from install utility:
*Cache Wipe complete
*E: can't open /tmp/recovery.log
Install Zip from SD Card
Selected Wajkui_Multilang*.*
Message from install utility:
*Finding Update Package
*Opening Update Package
*Installing Update Package
*E: Can't make /tmp/update.binary
*Installation aborted
Now the question needs to be answered is:
Was there a problem in the way I followed the instructions , if so what?
If the answer to the above is No based upon the record of the install/flash process listed above:
Why did the install abort?
Is the install procedure method listed on the ROM thread NOT suitable for Defy Plus BL7 Android version 2.3.6 devices which have been rooted using the procedure listed over here------>http://forum.xda-developers.com/showthread.php?t=1542956

I too have a MB526 with BL7 and rooted the same way. I am running WajkIUI 2.5.27 successfully. All the steps are mentioned correct. Choose Custom Recovery and you'll have the option of Stable Recovery within that.
Just re-download the ROM file. IT might be that your ZIP is corrupt.

nishantgandhi said:
I too have a MB526 with BL7 and rooted the same way. I am running WajkIUI 2.5.27 successfully. All the steps are mentioned correct. Choose Custom Recovery and you'll have the option of Stable Recovery within that.
Just re-download the ROM file. IT might be that your ZIP is corrupt.
Click to expand...
Click to collapse
Thank you for your response.
I tried to see if there is a sub-option titled Stable Recovery within Custom REcovery. No such option. Please confirm you are using 2ndinit 1.4.2.
I checked the zip file using Winzip. It is not corrupt.

No brother! You are to use ver 2.3.
My file name reads as 'SndInitDefy_2.3'. Attached is the APK for you!
Sent from my MB526 using xda app-developers app

nishantgandhi said:
No brother! You are to use ver 2.3.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
how to remove/uninstall recovery,i have installed v2.3
Sent from my MB526 using xda app-developers app

nishantgandhi said:
No brother! You are to use ver 2.3.
My file name reads as 'SndInitDefy_2.3'. Attached is the APK for you!
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Thanks once again for your help. I too had downloaded ver 2.3 to start with but after going through the install guide went for the lower version. Will test it out and see if I succeed.
Just saw your initial thread when you ventured out to root your phone and flash it. You mention you installed CM10 and liked it. So did you switch to WIUI and if so why? Which in your opinion is a better build in terms of stability?
jackajay said:
how to remove/uninstall recovery,i have installed v2.3
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
You must use the "manage app" options to uninstall any app including 2ndinit.

Yes I did install CM10 to begin with. Heck, I had bought Defy+ only with the intent of flashing a good JB ROM on it.
However, there was quite a bit of lag (especially when the call comes in, or when you launch the dialer, or while playing games like Temple Run etc). The battery life was pathetic and it didnt suit as a daily build.
I stumbled upon WajkIUI and thought of giving it a try. Boy, what a fabulous ROM it is. You don't even feel the need for JB. This ROM is super smooth, fast, stable and what have you. No FC or restart at all. I simply loved it from the first day.

nishantgandhi said:
Yes I did install CM10 to begin with. Heck, I had bought Defy+ only with the intent of flashing a good JB ROM on it.
However, there was quite a bit of lag (especially when the call comes in, or when you launch the dialer, or while playing games like Temple Run etc). The battery life was pathetic and it didnt suit as a daily build.
I stumbled upon WajkIUI and thought of giving it a try. Boy, what a fabulous ROM it is. You don't even feel the need for JB. This ROM is super smooth, fast, stable and what have you. No FC or restart at all. I simply loved it from the first day.
Click to expand...
Click to collapse
Hello
It worked. All thanks to you, as I had given up.Also initial impressions confirm your view of the WIUI Rom. However there is no Stable Recovery
option in Recovery during the install process. A couple of small niggles but more or less everything is functional as it should be .
If you think it proper, you could compile a comprehensive guide and post it. It will be a boon for all Defy Plus users whose devices are similar to your and mine and intend to ROOT &/or flash WIUI. I was fortunate that you chanced upon my thread and therefore I could solve the problem, but a guide would ensure your knowledge will be available to any one who is searching to go down this route.
Regards
aCs

I found the same error while installing the PVL Stock Rom for defy plus. After rebooting, i was back on my stock rooted rom, with all the apps missing including sndinitdefy. But the clockworkmod is still accessible. So if i install the new version of sndinitdefy, will it automatically replace the clockwordmod associated with it? Thanks for your reply!

Liquidsmooth (can't turn on now)

I was use a nexus4tookit v1.3.0 to root my nexus 4 , however I was download a Liquidsmooth and install from sdcard , but now the mobile cannot open , just load in liquid-smooth logo screen, what can I do now? My nexus 4 is JOP40D , Thanks a lot.

You may have a bad download. Check the md5 sum or re download it and try flashing it again.
Sent from my Nexus 4 using Tapatalk 2

Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.

First off. You shouldn't be using a toolkit, they get you from Point A to Point B. But now you are trying to backtrack because your phone won't boot. This is why people shouldn't use toolkits, you are getting to Point B without knowing what you're doing.
Is it stuck at the bootanimation screen? Did you wipe factory settings when flashing the ROM?

estallings15 said:
Restore the backup you should have made in recovery before you flashed anything.
Hold down power for ten seconds to reboot, then hold volume down to enter boot loader. You can get to recovery from there.
Click to expand...
Click to collapse
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:

cf017 said:
I already unlock the bootloader ， but I can't enter to boot loader now , just can enter to recovery mode or restart boot loader ,power off or start.:crying:
Click to expand...
Click to collapse
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.

estallings15 said:
If you can get into recovery, you're fine. Is this your first Android phone? Your first step after rooting is always to make a backup.
Anyway, flash Franco's kernel. It plays well with liquid smooth. That should fix you up. You will figure out how if you STOP PANICKING and try.
Click to expand...
Click to collapse
and not use toolkits! take the 15-25 minutes to read whats going on and not click one button to do it all for you
that's why OP is panicing because he didnt manually do it, a toolkit did it for him.

Post sent in error apologies

bash156 said:
Hi I hope you don't mind me messaging you I just noticed your last post that we should use toolkits for our phone can you please tell me what is the best way to do it I apologise for asking this is my first android phone and I'm realising that battery life is crap and I've been reading about people making changes to make their battery life live longer
Regards
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
We should use toolkits? I never said a thing about using them. The best way is to NOT use them. If this is your first android phone, it is IMPERATIVE to know simple ADB and Fastboot methods so you won't fall into the common errors when people use toolkits getting them into things they don't understand.
http://forum.xda-developers.com/showthread.php?t=1972508 is a guide to get started after you boot up, you can then proceed to go into the Original and Android dev forums to select your ROM / Kernel that you desire. I'd recommend CM10.1 (jellybro) + Franco Kernel R20. --- so after unlocking bootloader. Put the ROM, Gapps, Kernel on your phone storage using USB cable.
Use computer --- ADB... "adb reboot bootloader"
fastboot flash recovery <nameofrecovery>.img (download TWRP or CWR and put it in same folder as fastboot /platform-tools/ most likely)
boot into recovery (use volume up/down to navigate then power to enter)
wipe factory settings,dalvik,cache
flash rom then gapps then kernel (gapps and kernel can be reversed up to you)
then reboot.
done.

Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app

bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
He answered your question with great detail. Hit the thanks button.

bash156 said:
Apologies I meant that we should not be using tool kits my bad
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem. Just read what I said above, if u have any questions, feel free to ask. It's a very straight forward guide on how to unlock your bootloader. The stuff thats not included in there would be:
- Download ROM, Gapps (optional depending what rom you use. the rom says whether its included or not, if it doesnt say assume its in there), kernel (optional but recommended u switch --- upon flashing a new version u will need to reflash the kernel)
- Flashing Custom Recovery while in Bootloader Mode (which I said in my post on how to do.. basically download TWRP or CWR [you choose, i recommend twrp] and put the .img folder in the same folder as fastboot.exe)
- Use vol up / down to go to recovery in bootloader mode (it says the text on the phone)
- Wipe factory
- Flash ROM, Gapps, Kernel (gapps and kernel order doesnt matter. ROM goes first)
- Reboot to system
..... done.
edit: yeah what estallings said thanks given.

Thank you very much for your help I'm going to try and unlock the bootloader now I'll let you know how I get on to back everything that's on my phone already can I just sync to my Google account
Sent from my Nexus 4 using xda app-developers app

sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them

bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
Original development.

bash156 said:
sorry to bother you again thanks to you I have now unlocked bootloader but im finding it confusing on what to do next I havent managed to find the cm 10.1 and franco kernal you talked about is there a link somewhere for them
Click to expand...
Click to collapse
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.

zephiK said:
CM10.1 Jellybro: http://forum.xda-developers.com/showthread.php?goto=newpost&t=2015081
Franco Kernel: http://forum.xda-developers.com/showthread.php?t=2002782
Download CM10.1 Jellybro + Gapps + Kernel R20.
Click to expand...
Click to collapse
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up

bash156 said:
Hi I did everything you said I flashed the cm10 gapps and kernel now its stuck on the cynogenmod logo I went back to recovery wiped everything and tried to flash cm10 and the rest again and still stuck on the cynogen mod logo have I done something wrong because I dont have anything backed up
Click to expand...
Click to collapse
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.

zephiK said:
When you mean wipe everything... just factory settings, dalvik, cache right?
- Wipe Factory, Dalvik, Cache
- Flash CM10
- Flash Gapps
- Flash Kernel
- Reboot.
Click to expand...
Click to collapse
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.

estallings15 said:
I always wipe system as well. I used to not do that, but I found less phantom issues appeared if I wiped system.
Click to expand...
Click to collapse
Interesting. First time I've heard this, I will have to try that sometime although for the last year I've been pretty content with CM + Franco set up. Maybe when a new version of Android comes out, I swap over to that AOSP ROM for a little while but once CM is set, im moving.

[Q] Nexus 4 problems.

I'm having a big problem with my Nexus 4 here lately. I tried to root it about 2 days ago, and it did not work. So i downloaded TWRP and my computer read it the same as the Nexus 4 root toolkit by WugFresh. I opened TWRP and it asked me to flash or boot (it was on flash), and i think i clicked "Recovery" and it made my Nexus not boot up, it was just at the logo screen. Then i tried to flash TWRP to the bootloader and System and it flashed TWRP, now it won't go into android. It just takes me into the TWRP interface. In the TRWP interface there are 8 options( Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot). I pressed "Reboot" and i when press System, Recovery, or Bootloader it tells me that the is no OS installed, I've looked up how to install OS back via WugFresh's toolkit, but it's still not working (maybe because I'm on a old computer). So I'm kinda panicking, is there anyone i can call,or take my phone to, or can you guys help PLEASE!?!

1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.

Okay, i'll try that right now..

chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??

Yiddish said:
I'm having a problem with the ADB setup, i followed all the directions carfully, and that last step were i had to type in "adb devices" in did not work... is there anyway i can open adb??
Click to expand...
Click to collapse
Try install these drivers: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi

chromium96 said:
Try install these drivers
Click to expand...
Click to collapse
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?

Yiddish said:
Nice, that worked. Okay i'm back on track. Also, does it matter what ROM i download?? I don't have to be rooted to push them huh?
Click to expand...
Click to collapse
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app

chromium96 said:
Nope. Just make sure u put the phone in recovery mode (twrp) before you use the push command.
Sent using xda-developers app
Click to expand...
Click to collapse
Recovery mode is when the Android is on it's back with a red exclamation over it right??

Yiddish said:
Recovery mode is when the Android is on it's back with a red exclamation over it right??
Click to expand...
Click to collapse
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.

chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
Oh, i see. Okay here i go

chromium96 said:
1. Calm down, dont panic. Its an easy fix. You need to push a rom onto your phone using adb, then flash it using twrp.
2. Setup adb.
3. Download ROM: here or here.
4. Use this command to copy the rom to the phone:
Code:
adb push nameofROM.zip /sdcard
5. In TWRP go to Install, look for the rom you pushed, select it, and finally swipe to flash it.
Click to expand...
Click to collapse
Okay, it got past the Google screen, now it's been on the multicolored X for about 10 minutes+ not doing anything

chromium96 said:
Thats the stock recovery, but since you have TWRP installed that is your current recovery. So go into TWRP and use the command from there.
Click to expand...
Click to collapse
How long will i be on the X loading screen??

Yiddish said:
How long will i be on the X loading screen??
Click to expand...
Click to collapse
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.

BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Thanks! I think it was just the ROM i chose. I just downloaded Slim Bean, this seems to be working( the startup screen looks cool ) I'm on the "Android is upgrading..." screen and it says "Starting apps." at the moment.

Okay, SlimBean took more than 10 minutes, so i factory reset and tried again, and it's still not booting up. ):

BobWalker said:
On the first boot after flashing a new ROM the Nexus should start up within 5 to 10 minutes. If the phone is still displaying the boot animation, reboot into the phone into TWRP recovery, select Wipe, select Factory Reset, wipe Cache and Dalvik cache, and reboot the phone.
Click to expand...
Click to collapse
Any ideas why it's still not working??

Yiddish said:
Any ideas why it's still not working??
Click to expand...
Click to collapse
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.

BobWalker said:
I have not used Slim Bean. It sounds as though you got past the boot animation screen to Slim Bean updating apps (Android upgrading). Normally ROMs that update apps on startup display a count as they update. Does Slim Bean display such an update counter? Does the count progress or does it hang at some point? Note that the system update on startup will take additional time depending on the quality of your phone's network connection. If you are still experiencing issues with Slim Bean, I recommend that you post on the developers forum where you downloaded the ROM.
Click to expand...
Click to collapse
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??

Yiddish said:
I got passed the boot animation, and it was taking too long to update my apps so i turned my phone off, and back on, after that my phone would not go past the boot animation. Are you guys sure that all i need to do is pus a ROM file?? Because it doesn't seem like it's working. Also, does it matter were i flash TWRP too??
Click to expand...
Click to collapse
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.

BobWalker said:
It is certainly more convenient to replace the stock recovery with TWRP permanently since this gives you more freedom when installing ROMs and performing nandroid backups.
I would try booting into TWRP again, install the Slim Bean ROM one more time, install Gapps, wipe Cache and Dalvik cache, and reboot your phone. If the Nexus gets past the boot animation to "Android upgrading" allow the upgrade to complete. If you are still having problems with Slim Bean, I suggest posting your question in the Slim Bean thread in the developers forum.
Click to expand...
Click to collapse
Where do i get Gapps??

[Q] Defect CM10.1, Teamwin Recovery defect, fix & install KitKat

Hello,
I currently have installed CM 10.1-20130709-NIGHTLY-mb526 (Android 4.2.2, 2.6.32.9-AeroKernel), but I had a problem yesterday (phone would not boot).
So I did a Cache/Dalvik wipe, and after reboot it optimized all the apps but looped at "opening apps".
So today I decided to reinstall the above mentioned rom. But after installation it turned out to be defect somehow (e.g. the unlock screen will never appear, altough it is activated; in the swipe down menu the right-above button won't appear/won't work; browser won't turn on; home button does not work etc.).
So I decided to give KitKat a try. I visited this page by Quarx and I would begin with the Recovery Update. I put the update recovery zip on the sd card and install it via TeamWinRecovery.
After reboot, the TeamWinRecovery won't turn on and it simpy reboots. So now I am stuck. How do I install/recover TeamWinRecovery (or any necessary Recovery to install KitKat?).
After the installation I can simply install the latest KitKat rom, right? Or is there anything else necessary (kernel update etc.?). If I don't like KitKat, can I simply flash the latest CM10.2 rom?
Thank you very much!
Edit: The first rom i woul like to try is cm-11-20140117-NIGTHLY-mb526 (this is the KitKat, right?) and if this is not stable enough for me I would install cm-10.2-20131020-NIGHTLY-mb526 (Jelly Bean, right?). The reason I want to change is that I do not think the CM10.1 I have installed is neither stable nor perfomant.
Edit2: I tried the GooManager but it did not work! After reboot into Recovery screen stays black and reboots again.

mrkernelpanic said:
Hello,
I currently have installed CM 10.1-20130709-NIGHTLY-mb526 (Android 4.2.2, 2.6.32.9-AeroKernel), but I had a problem yesterday (phone would not boot).
So I did a Cache/Dalvik wipe, and after reboot it optimized all the apps but looped at "opening apps".
So today I decided to reinstall the above mentioned rom. But after installation it turned out to be defect somehow (e.g. the unlock screen will never appear, altough it is activated; in the swipe down menu the right-above button won't appear/won't work; browser won't turn on; home button does not work etc.).
So I decided to give KitKat a try. I visited this page by Quarx and I would begin with the Recovery Update. I put the update recovery zip on the sd card and install it via TeamWinRecovery.
After reboot, the TeamWinRecovery won't turn on and it simpy reboots. So now I am stuck. How do I install/recover TeamWinRecovery (or any necessary Recovery to install KitKat?).
After the installation I can simply install the latest KitKat rom, right? Or is there anything else necessary (kernel update etc.?). If I don't like KitKat, can I simply flash the latest CM10.2 rom?
Thank you very much!
Edit: The first rom i woul like to try is cm-11-20140117-NIGTHLY-mb526 (this is the KitKat, right?) and if this is not stable enough for me I would install cm-10.2-20131020-NIGHTLY-mb526 (Jelly Bean, right?). The reason I want to change is that I do not think the CM10.1 I have installed is neither stable nor perfomant.
Edit2: I tried the GooManager but it did not work! After reboot into Recovery screen stays black and reboots again.
Click to expand...
Click to collapse
Hello, i had a similar problem and i finally flashed a new sbf then CM10.1 and after that CM10.2 and it worked. As for recovery the only way that worked for me is with cwm through 2init.apk. CM11 seems unstable atm...

PerryTrademark said:
Hello, i had a similar problem and i finally flashed a new sbf then CM10.1 and after that CM10.2 and it worked. As for recovery the only way that worked for me is with cwm through 2init.apk. CM11 seems unstable atm...
Click to expand...
Click to collapse
sbf is not a option for me!

mrkernelpanic said:
sbf is not a option for me!
Click to expand...
Click to collapse
SBF is the only option. The reason why CM10.1 didn't work as intended is that you must have used full gapps.
Sent from my Nexus 7 using Tapatalk

Hi,
I think I used the minimal Gapps linked in the thread! And no, sbf is not an option right now as I do not have acces to a Windows based PC where I have rights to install software!
Any other solution how I can restore/install TeamWinRecovery? Should I try 2ndinit?
Thanks anyway and regards kernel

There is a method through ADB explained by @YetAnotherForumUser in CM11 thread by Quarx. This if you can enter in boot menu.
Sent from my MB526 using Tapatalk

adb is neiher an opion, I currently have no acces to a computer with root-acces!
I read somewhere that 2ndinit won't work wih a custom rom installed, ist this correct?
Regards kernel

Yes is correct. You must start from sbf when you have access to a computer.
Sent from my MB526 using Tapatalk

mrkernelpanic said:
adb is neiher an opion, I currently have no acces to a computer with root-acces!
I read somewhere that 2ndinit won't work wih a custom rom installed, ist this correct?
Regards kernel
Click to expand...
Click to collapse
What about a linux live session?
Sent from my MB526 using xda app-developers app