Related
Got Rom Premium, CWM, and AmonRa on N1.
Playing and trying to learn about the manual (green) recovery screens.
Q1: What is the Apply Update:Update.Zip for?
Q2: When in those screens, no buttons I try can take me back to previous screen, like vol- does in AmonRa.
Thanks for any help and I read dozens of search results without really understanding Apply Update and no luck on going back on screens.
I am not expert yet, so please keep replies at a for dummy level.
Ken
If your using Clockword Recovery then Ill help ya out.
1: Thats used if you have the rom or update on the root of your sd card and have it named update.zip. This is how we used to flash roms on the old recovery menus on the G1, they just left it in. Now you can just search your sd card for the rom you want.
2: The power buttom will go back, and if your on the main screen the power button will turn off the display to save power.
What do you mean when you say manual recovery screen? Do you mean the stock recovery or are you talking about a custom? With the stock recovery it will only install files named update.zip signed with google keys. If you are talking about a custom recovery that means that it will search for a file named update.zip and flash that.
Thanks a lot,
1. I thought the zip wasn't needed anymore based on my research.
2. Got it, I swore I tried that.
When on main screen how do you exit it?
Ken
rugmankc said:
Thanks a lot,
1. I thought the zip wasn't needed anymore based on my research.
2. Got it, I swore I tried that.
When on main screen how do you exit it?
Ken
Click to expand...
Click to collapse
1: It isn't, they kind of just left it in as a fast way of flashing without having to look for it.
2: Just hit the reboot option at the top.
One more question, at least for now.
Is going back and forth between recoveries, as easy as just "flashing alternate recovery" from that selection. I.E. CWM to AmonRa and vice versa?
Your help is greatly appreciated
rugmankc said:
One more question, at least for now.
Is going back and forth between recoveries, as easy as just "flashing alternate recovery" from that selection. I.E. CWM to AmonRa and vice versa?
Your help is greatly appreciated
Click to expand...
Click to collapse
Yup. Tho id recommend Clockwork, since im a little bias.
And no prob, I was an android noob at one time.
Ninja Edit:
A warning tho, if you use nandroid, the 2 recoveries don't play nice with each others nandroids.
Thanks McFroger3,
I like what CWM offers just heard some problems with it and AmonRa is rock solid, but more manual and doesn't allow for quick flashes of the CM6 nightlies I am on.
Ken
evilkorn said:
What do you mean when you say manual recovery screen? Do you mean the stock recovery or are you talking about a custom? With the stock recovery it will only install files named update.zip signed with google keys. If you are talking about a custom recovery that means that it will search for a file named update.zip and flash that.
Click to expand...
Click to collapse
I am just talking about the green screens where you do your backup/restores, flash roms etc. Bad semantics on my part. It's where you go when you select Reboot into Recovery on the CWM main screen.
I think I am good to go,
Thanks,
Ken
Ninja Edit:
A warning tho, if you use nandroid, the 2 recoveries don't play nice with each others nandroids.
Right, I am assuming you are talking about Backup with CWM, restore with CWM and same for AmonRa.
Ken
rugmankc said:
Ninja Edit:
A warning tho, if you use nandroid, the 2 recoveries don't play nice with each others nandroids.
Right, I am assuming you are talking about Backup with CWM, restore with CWM and same for AmonRa.
Ken
Click to expand...
Click to collapse
Yea, if you back up with CWM, and try to restore with Amon, you will run into issues lol.
Thanks Again for the heads up,
I read that during my research to solve these issues which you quickly helped me with. I won't mix the two. If CWM works well for me, I will use it most if not all of the time. I got into this helping new rooters on the Nexus One forum when most used 1 click to root and started using Rom Mangager and CWM.
Got to call it a day!
Thanks,
Ken
OK,
I want CWM Recovery to work for me. I flashed the latest nightly from the list in ROM Manager. Followed all prompts and allowed the Google Addons to be downloaded also. OK'd backup. The backup and nightly went fined. But, the gapps hung on installing. Had to pull battery, reboot, and restore to previous backup. All Ok now, but it bothers me and not sure if I want to try again. Have been flashing roms, gapps etc with AmomRa for awhile.
Did I miss something? CWM did all the choosing of what to dl and flash. Something different on gapps? It was hdpi-frf91-2-signed.zip. I know that is not the latest. Latest is frf91-UP. Don't know if that matters.
If I have to copy that to sd and flash, what is the procedure? If I select the latest nightly, I have to tell CWM I don't want the gapps, then does it give me that opportunity to grab the gapps zip from sd card before it flashes the nightly. If not, I have no market on phone to dl anything like Titanium to get phone running.
What am I mising?
I copied latest gapps zip to sd card, did not rename. It has .zip on end. Playing around I selected Install Rom from SD Card and found the zip. Clicked on it. Options under Install Queue screen: Ok or Add Zip. Do I zip since it has one. And this allowing me to queue it and go back and add another rom. Didn't see those choices when I did the procedure from the Download Rom choice on Rom manager main screen.
Easier question may be:
If I want to flash latest nightly and a gapps zip I copied to sd card, the latest. What is the procedure?
It seems CWM won't let me install latest nightly without installing gapps, not the latest. Don't know if that is my problem.
Seems I would need to flash latest nightly again and if ok, just flash latest gapps, no wipe, over the just installed nightly.
And if gapps don't install, I can go back and flash my latest gapps from the sd card.
Any thoughts.
Had to flash my latest .zip fromsd card after the gapps attached to lastest nightly failed to install again.
Resolved
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
So, finally I roted my N4. Cause I was an appleboy, didn't have a clue how to do that. But downloaded N4 toolkit and did it in Sec...
After I downloaded Parandroid 3+, and is awesome ROM.
But, there is an app called goomanager now on phone, and keeps telling me that my rom have an update, but when I press that notification nothing happens, at all... What to do.
I have CWM 6 recovery (i have no idea what that means, but I have that too...)
I just how that I will be good with this roting thing cause it's just great.
Thanks...
May the force be with you...
I believe goo.im (goomanager) have connection problems atm.
If that happens goomanager can go a little crazy with the updates.
Sent from my Galaxy Nexus using Tapatalk 2
Nuuq said:
So, finally I roted my N4. Cause I was an appleboy, didn't have a clue how to do that. But downloaded N4 toolkit and did it in Sec...
After I downloaded Parandroid 3+, and is awesome ROM.
But, there is an app called goomanager now on phone, and keeps telling me that my rom have an update, but when I press that notification nothing happens, at all... What to do.
I have CWM 6 recovery (i have no idea what that means, but I have that too...)
I just how that I will be good with this roting thing cause it's just great.
Thanks...
May the force be with you...
Click to expand...
Click to collapse
Yeah, goomanager is telling there's a new version of the ROM your running, you can download the new version (look for it in the forum) and then install it (flash it) via recovery, or keep your old one. I personally like stock, don't like custom ROMs on nexus devices.
zcucurullo said:
Yeah, goomanager is telling there's a new version of the ROM your running, you can download the new version (look for it in the forum) and then install it (flash it) via recovery, or keep your old one. I personally like stock, don't like custom ROMs on nexus devices.
Click to expand...
Click to collapse
So Parandroid is ROM, and CWM is recovery??? And when i download new version of rom, to flash it is to update/install it?
May the force be with you...
Nuuq said:
So Parandroid is ROM, and CWM is recovery??? And when i download new version of rom, to flash it is to update/install it?
May the force be with you...
Click to expand...
Click to collapse
Yep: Paranoid android = ROM and CWM/clockwordmod = recovery
And yes, you download and flash roms to install new ones.
chromium96 said:
Yep: Paranoid android = ROM and CWM/clockwordmod = recovery
And yes, you download and flash roms to install new ones.
Click to expand...
Click to collapse
If I download update and want to flash it via goomanager, do I need to wipe device???
Sent from my Nexus 4 using Tapatalk 2
Nope. Reboot into recovery, install .zip from SD card, find the downloaded ROM zip you want to flash, wipe cache/dalvik cache and reboot. None of your data should be lost
Nigeldg said:
Nope. Reboot into recovery, install .zip from SD card, find the downloaded ROM zip you want to flash, wipe cache/dalvik cache and reboot. None of your data should be lost
Click to expand...
Click to collapse
Don't forget yo flash the gapps after the ROM to
Sent from my Nexus 4
spaceman860 said:
Don't forget yo flash the gapps after the ROM to
Sent from my Nexus 4
Click to expand...
Click to collapse
That too. I forgot about it because I downloaded the gapps that I wanted individually from the play store so I don't have to reflash gapps every time, but yeah OP flash gapps.
Nigeldg said:
That too. I forgot about it because I downloaded the gapps that I wanted individually from the play store so I don't have to reflash gapps every time, but yeah OP flash gapps.
Click to expand...
Click to collapse
But play store, google backup transport and other google apps are to be flashed saperately in order for play store to work. And the contacts sync and other stuff can only be got by flashing gaps.
---------- Post added at 12:41 AM ---------- Previous post was at 12:36 AM ----------
Nuuq said:
So, finally I roted my N4. Cause I was an appleboy, didn't have a clue how to do that. But downloaded N4 toolkit and did it in Sec...
After I downloaded Parandroid 3+, and is awesome ROM.
But, there is an app called goomanager now on phone, and keeps telling me that my rom have an update, but when I press that notification nothing happens, at all... What to do.
I have CWM 6 recovery (i have no idea what that means, but I have that too...)
I just how that I will be good with this roting thing cause it's just great.
Thanks...
May the force be with you...
Click to expand...
Click to collapse
Goo.im manager is the software that can be used by developers to provide ota updates to users of their custom roms. It sometimes goes mad and asks to update rom. It could be some data problem. Just erase the app data and restart app. This works most of times.
Nuuq said:
So, finally I roted my N4. Cause I was an appleboy, didn't have a clue how to do that. But downloaded N4 toolkit and did it in Sec...
After I downloaded Parandroid 3+, and is awesome ROM.
But, there is an app called goomanager now on phone, and keeps telling me that my rom have an update, but when I press that notification nothing happens, at all... What to do.
I have CWM 6 recovery (i have no idea what that means, but I have that too...)
I just how that I will be good with this roting thing cause it's just great.
Thanks...
May the force be with you...
Click to expand...
Click to collapse
WELCOME to android!
just remember this.
flashing for update:: clear cache/dalvik cache, flash update, flash Gapps,
flashing new rom, factory reset, flash rom, flash Gapps, clear cache/dalvik. reboot, restore apps using Titanium Backup
I've been running the 10-20130303-Nightly-encore for a while now with no problems. Yesterday I decided to try to use the CyanogenMod update to upgrade to 10.1.2. Did both Ti and CWM backups, then went ahead with the 10.1.2 update. This mostly worked, but several things broke right off the bat.
First, some of my apps either got erased or uninstalled. The icons were there, but tapping on them would bring up a message saying the app was not installed.
Second, as my Nook booted up, it reported several apps have stopped. (Such as gmail, Trillian, etc.) Worse yet, some of my apps wouldn't even run. (RomManager for one!) I attempted to restore some of those apps via Ti. Some of them restored but still didn't run. On a few of them, Ti just got stuck on the "Restoring..." popup.
Third, although my WiFi was connected and apparently working for some apps, other apps reported no network connection. (Namely the Play store!) I did notice that the WiFi icon at the top was always gray, not the normal blue.
After fiddling with it for several hours, I managed to get RomManager back up and reverted back to my previous backup.
So my questions are:
1. What is the correct way to update/upgrade using CyanogenMod's updater?
2. Should I have updated to 10.1.0 first, then 10.1.1, then 10.1.2?
Thanks!
You need to factory reset/clear data (probably need to wipe/format system as well) and install the correct gapps for 10.1 (20130301)
So, are you saying that I should go to the "CyanogenMod updates" settings, select the cm-10.1.2, download it (by taping the button to download), then not install it using the button to install it, but instead download (manually) the correct gapps, move both files to the sdcard root, reboot into recovery, totally wipe/reset the whole tablet, then install cm-10.1.2 and the gapps, and then begin to re-install all of my apps and data?
If so, then I think I fail to see the purpose of the "CyanogenMod updates" settings page.
software_samurai said:
So, are you saying that I should go to the "CyanogenMod updates" settings, select the cm-10.1.2, download it (by taping the button to download), then not install it using the button to install it, but instead download (manually) the correct gapps, move both files to the sdcard root, reboot into recovery, totally wipe/reset the whole tablet, then install cm-10.1.2 and the gapps, and then begin to re-install all of my apps and data?
If so, then I think I fail to see the purpose of the "CyanogenMod updates" settings page.
Click to expand...
Click to collapse
If you have a "CWM based recovery" on internal memory, you should be able to download and install the CWM 10.1.2 using cmupdater. But you may have to manually install the right version of gapps the first time. After that just use the updater. No need to wipe anything if just updating CM10.1 to another CM10.1.
Obviously something when wrong last time and that is why dizzy recommended wiping. Usually that is not necessary.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
If you have a "CWM based recovery" on internal memory, you should be able to download and install the CWM 10.1.2 using cmupdater. But you may have to manually install the right version of gapps the first time. After that just use the updater. No need to wipe anything if just updating CM10.1 to another CM10.1.
Click to expand...
Click to collapse
Personally I have found the TWRP recovery to work more reliably than CWM. At some point I was having similar issues with the first updates after fresh-flashing my first CM10 nightly, and after switching to TWRP there has been no problems so far. As a bonus, ROMs which use GooManager for updates would also be able to install updates from GooManager automatically. If you only plan to use CM, what leapinlear says should work, too.
Thread targets me exactly, so thank you, thank you all.
Requesting further clarification ; I wish to use cmupdate to latest stable version for my Nook. Regardless of which flavor recovery I use, should I, first flash the appropriate gapps, then run the updater?
This seems to be the logical order if there is a chance that the recovery might get hosed during the update process. But will it work?
If I'm off track here please set me straight!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Chipsy Chopsy said:
Requesting further clarification ; I wish to use cmupdate to latest stable version for my Nook. Regardless of which flavor recovery I use, should I, first flash the appropriate gapps, then run the updater?
This seems to be the logical order if there is a chance that the recovery might get hosed during the update process. But will it work?
Click to expand...
Click to collapse
The CM Updater should work regardless whether gapps are installed or not — the updater does not need gapps to work.
The first time you install CM, the usual thing is to flash both CM and gapps (some people may decide to not use the Google stuff, so they choose to not flash gapps, but in general almost everybody would/should flash them). If gapps are installed, the CM updater will then preserve the gapps when doing an update, so it is not needed to flash gapps with each update.
I hope the explanation makes things a bit clearer for you
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