Related
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
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]
Apologies, I am sure this has been asked before but I am in such a pickle as I have read all the threads I can find and that's why I am in this state.
I have root access via ODIN So that's a good start.
Tried to install Pacman no joy, tried then with Goo and their custom roms, no joy, installed CWM no joy so I think all the threads have confused me even more.
I cant see the "install from SD card option" when I boot to recoevery.
I have tried the one click rom update but that fails due to failed to verify whole-file signature
So I currently have a working phone with standard rom and SU and Root access but I cant install any ROMs
I am sure I have missed a stage so I wanted to write a new thread to see if we can go back to basics.
Hope you can help
uktotty said:
Apologies, I am sure this has been asked before but I am in such a pickle as I have read all the threads I can find and that's why I am in this state.
I have root access via ODIN So that's a good start.
Tried to install Pacman no joy, tried then with Goo and their custom roms, no joy, installed CWM no joy so I think all the threads have confused me even more.
I cant see the "install from SD card option" when I boot to recoevery.
I have tried the one click rom update but that fails due to failed to verify whole-file signature
So I currently have a working phone with standard rom and SU and Root access but I cant install any ROMs
I am sure I have missed a stage so I wanted to write a new thread to see if we can go back to basics.
Hope you can help
Click to expand...
Click to collapse
Let's see if i follow you here: You have rooted your device and then installed a custom recovery, or is it that the recovery won't install that's the problem? If you have a custom recovery maybe the fault lies with the recovery ittself?
If that is the problem I had that as well, What i did before flashing a new recovery with ODIN was to unable automatic reboot. Then, when the flash was done I took out the battery and made sure the phone was off. After this I booted into recovery and it worked like a charm... My firts tries with TWRP couldn't flash custom roms though, so I had to flash CWM recovery instead, and that worked as a charm.
Soliquidity said:
Let's see if i follow you here: You have rooted your device and then installed a custom recovery, or is it that the recovery won't install that's the problem? If you have a custom recovery maybe the fault lies with the recovery ittself?
If that is the problem I had that as well, What i did before flashing a new recovery with ODIN was to unable automatic reboot. Then, when the flash was done I took out the battery and made sure the phone was off. After this I booted into recovery and it worked like a charm... My firts tries with TWRP couldn't flash custom roms though, so I had to flash CWM recovery instead, and that worked as a charm.
Click to expand...
Click to collapse
Hiya
Ok so not sure about the Custom recovery bit,
I have now done the PhilzTouch thing and installed that via odin also.
What should II be looking for as far as the custom recovery goes?
Hold on a minute!
Looks like PacMan is now loading up, will update in a bit
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)
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.