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]
Related
*RESOLVED*
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
wipe data then reflash your rom
benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Follow this guide to re-root and install CWM.
simms22 said:
wipe data then reflash your rom
Click to expand...
Click to collapse
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.
rhoadster91 said:
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Click to expand...
Click to collapse
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?
benblb said:
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.
Click to expand...
Click to collapse
yes, in cwm. wipe data then flash the rom. you can try just reflashing your rom first, without wiping data. if it still bootloops, then wipe data and reflash. flashing the system img via fastboit will wipe everything.
benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.
a wipe data/factory reset in Recovery Mode can solve this bootloop, especially after you have just flashed a ROM.
benblb said:
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?
Click to expand...
Click to collapse
Flashing from fastboot will automatically clear all data. There should be a system.img file. Flash it using
Code:
fastboot flash system system.img
But to make a clean install, I would recommend you flash all the factory images. Refer this for more detail.
JaiaV said:
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.
Click to expand...
Click to collapse
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.
benblb said:
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.
Click to expand...
Click to collapse
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).
simms22 said:
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).
Click to expand...
Click to collapse
I'm on stock. What file do I flash? Thanks for all your help.
benblb said:
I'm on stock. What file do I flash? Thanks for all your help.
Click to expand...
Click to collapse
look in the development section, there are a few rooted stock roms available.
simms22 said:
look in the development section, there are a few rooted stock roms available.
Click to expand...
Click to collapse
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
Flashing the factory images will have restored the stock kernel.
If you are going to flash a factory image or anything like that, watch this: http://forum.xda-developers.com/showthread.php?t=2039162
after you flash that ROM, if your phone stucks in a bootloop, then go to Recovery, wipe cache and reset factory will solve the problem.
benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
na, the kernel is always included in the rom. you flash a kernel if you want to use a different kernel(trinity is great with stock).
Hi everyone,
Thanks for your help. I have flashed stock 4.2.2 to my phone and have finished setting everything up. I really appreciate the quick responses and dedication to my issue. It means a lot to me that you guys helped me in my time of need. Thanks again.
Cheers,
Ben
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Zouk18 said:
Hi,
It seems that I have CWM and recovery installed on my Nexus 4. I was on TWRP previously and switched to CWM, now it seems that it is stucked.
I erased recovery in command prompt and flash it with CWM after installing stock ROM but ROM Manager still detected TWRP. How do I get rid of TWRP?
Click to expand...
Click to collapse
try flashing stock recovery via adb
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
ijustzeke said:
try flashing stock recovery via adb
Click to expand...
Click to collapse
So you are suggesting that I erase and flash to stock recovery via adb and then flash custom recovery again?
EddyOS said:
If you reboot into recovery does CWM come up or TWRP? If it's CWM then ignore ROM Manager and continue as normal
Click to expand...
Click to collapse
CWM comes up as the recovery because it's the latest one I flash. I know it might now matter but this really bugs me.
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Mine was gone when i unrooting the device
Sent from my Nexus 4
EddyOS said:
Dunno why you're using ROM Manager anyway, pointless piece of software IMO. Just flash everything manually
Click to expand...
Click to collapse
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
curtzxion said:
Mine was gone when i unrooting the device
Sent from my Nexus 4
Click to expand...
Click to collapse
Is there a way just to unroot but keep my ROM, kernel and data intact?
Zouk18 said:
I was just checking out the app, don't really use it. That was when I saw two recoveries. I erased and flashed everything via adb previously. Just really wanna know the cause and how to get rid of it.
Is there a way just to unroot but keep my ROM, kernel and data intact?
Click to expand...
Click to collapse
My rom, kernel, and data doesn't change, when i was unrooting the device(as i remember)
Sent from my Nexus 4
That's normal. I have it too. Just choose cwm on recovery already installed and leave it like that.
Sent from my Nexus 4 using xda premium
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)
Hello all, I accidentally used ROM Manager to try to install CWM, but when I booted into recovery, it gave me that Android with the red triangle icon. How should I go about removing any remnants and installing TWRP? Thanks for your help!
Sounds like you probably just booted into stock recovery (meaning, CWM didn't install). Try booting into the phone's OS again, then try a different recovery flashing method like loki_flash.
antinorm said:
Sounds like you probably just booted into stock recovery (meaning, CWM didn't install). Try booting into the phone's OS again, then try a different recovery flashing method like loki_flash.
Click to expand...
Click to collapse
Ok, so I booted into the Stock ROM, do I need to do anything other than follow the instructions for Loki_Flash? It's safe even though I already tried installing CWM?
charlesz54 said:
Ok, so I booted into the Stock ROM, do I need to do anything other than follow the instructions for Loki_Flash? It's safe even though I already tried installing CWM?
Click to expand...
Click to collapse
loki_flash performs validation checks that many other methods don't, so it's safer than they are. Just make sure you run it as root, and you have the correct image for your device.
Hi all
Got an I9505 on O2 and since lollipop update it restarted a few times by itself. Now it keeps going into a loop where it will restart and the home screen loads, you can use it for about 20-30 seconds and it will reboot again!
Initially when I researched I though it was an app problem but couldn't find the culprit. Then I took it into the Samsung repair centre and they said it needed a clean flash by them. This didn't work and they fitted a new mother board and this still hasn't worked.
I can say that it has twice happened when the Wifi hasn't been working properly so I have turned it off but other than that I have no idea!
Also I have tried rebooting into safe mode but it still does it, aaarrrggghhhh!!!
Any ideas where I can go from here please?
P
Return to kitkat if you can. Otherwise use a custom rom. These would be my suggestions. Since Samsung's repair couldn't fix it, warranty should not be a problem anymore.
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
PJBXDA said:
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
Click to expand...
Click to collapse
It's fairly easy. Depending on what S4 model you have. Some models have a locked bootloader and that makes the whole thing trickier.
This is what I did:
1) Root with CF-Auto-Root. Thread here.
2) Backup all my apps.
3) Install a custom recovery (TWRP). Download and instructions here.
4) Flash custom rom. Most roms have their own instructions.
You can skip 1 and 2 if you don't want to backup.
Installing a custom recovery can be done using Odin. I recommend TWRP since it's the only one I've used.
Lollipop GPE rom. I've used this rom and didn't have any issues. CM12 seems a bit faster, but the GPE was more stable and bug-free.
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
PJBXDA said:
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
Click to expand...
Click to collapse
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
PJBXDA said:
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
On the CF-Root page it says to open Odin and click on the PDA button but I cannot find a PDA button!
Edit: It is the AP button on the newer version!
Click to expand...
Click to collapse
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
Click to expand...
Click to collapse
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
PJBXDA said:
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
Click to expand...
Click to collapse
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
GDReaper said:
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
Click to expand...
Click to collapse
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
PJBXDA said:
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
Click to expand...
Click to collapse
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
GDReaper said:
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
Click to expand...
Click to collapse
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
PJBXDA said:
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
Click to expand...
Click to collapse
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
GDReaper said:
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
Click to expand...
Click to collapse
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
PJBXDA said:
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
Click to expand...
Click to collapse
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
GDReaper said:
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
Click to expand...
Click to collapse
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
PJBXDA said:
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
Click to expand...
Click to collapse
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
GDReaper said:
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
Click to expand...
Click to collapse
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
PJBXDA said:
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
Click to expand...
Click to collapse
SaberMod is a rom. SaberMod CM12.1.
They are very similar. The difference is how they tackle optimizations.
Yes, you will have to flash it. But you can also stick with normal CM12 if you don't have any issues.
The google search box from the home screen or the recents?
You can change the launcher to get rid of it from the home screen.
To remove it from the recents there is an option somewhere in the settings.