Related
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]
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
drguild said:
I have CWM as my recovery and PA on the device.
I got a message today saying a new PA is out and grabbed the zip from goo manager.
Now I understand with goo manager you need a openscript recovery to use that to update though it appears CWM recovery doesn't use that but TWP does.
In CM10 you go to the settings and update from the OTA section in the about tab.
PA doesn't use those OTA updates it seems when CM does.
I would still be using CM but was getting a lot of crashes on M3 so I decided to try a few roms and currently running PA.
So what's the best way to update can I just flash the rom over the top of the current system without formatting first?
Thanks
Click to expand...
Click to collapse
Move the zip containing the update to /sdcard (your root documents directory, where all your files are stored- ANdroid, Data, DCIM, Downloads, etc), reboot to CWM, flash zip, select zip and go. That should be all you have to do. :good:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
purmou said:
It worked fine for me using CWM and the usual method to update (recovery->install zip->select from SD). The only problem I'm having is a DPI issue in the launcher. Make sure to install the newest gapps as well and clear the cache.
Sent from my Nexus 10
Click to expand...
Click to collapse
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
drguild said:
Cheers guys I read you can just flash over the top in CWM but just wanted to confirm it.
Click to expand...
Click to collapse
Correct.
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)
So i finally rooted and went into twrp. This is the first rom im installing. Ive done this whole root thing for a little over 4 years now.
I went to do a wipe, system, cache, dav....and its been stuck on "factory reset" for 10 mins now what do i do. did i do something wrong?
formatting cache using make_ext4s function" is what its saying
the phone shut of and i thought it was done for. It did reboot but nothing was wiped. am i doing something wrong here?
normally you just go into the twrp, slide to wipe everything, install rom, gapps, wipe cache and dav and reboot.
xzero425x said:
So i finally rooted and went into twrp. This is the first rom im installing. Ive done this whole root thing for a little over 4 years now.
I went to do a wipe, system, cache, dav....and its been stuck on "factory reset" for 10 mins now what do i do. did i do something wrong?
formatting cache using make_ext4s function" is what its saying
the phone shut of and i thought it was done for. It did reboot but nothing was wiped. am i doing something wrong here?
normally you just go into the twrp, slide to wipe everything, install rom, gapps, wipe cache and dav and reboot.
Click to expand...
Click to collapse
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
RubbleTea said:
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
Click to expand...
Click to collapse
thats the one im using!! is there a newer one around? ill give it another shot.
EDIT: I did them separate, and tried installing a 4.4.2 rom and it keeps failing, hmm
xzero425x said:
thats the one im using!! is there a newer one around? ill give it another shot.
Click to expand...
Click to collapse
Which build do you have? I'll post the link if you want?
RubbleTea said:
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
Click to expand...
Click to collapse
RubbleTea said:
Which build do you have? I'll post the link if you want?
Click to expand...
Click to collapse
tmobile, now i tried to reboot and it just keeps taking me right back to twrp
http://www.teamw.in/project/twrp2/197
Here's the link just click on which build....if you have tmobile ...there's a unofficial 2.6.3.3 I think and 2.6.3.4 or try philz cwm recovery here;
http://forum.xda-developers.com/showthread.php?t=2554053
RubbleTea said:
http://www.teamw.in/project/twrp2/197
Here's the link just click on which build....if you have tmobile ...there's a unofficial 2.6.3.3 I think and 2.6.3.4 or try philz cwm recovery here;
http://forum.xda-developers.com/showthread.php?t=2554053
Click to expand...
Click to collapse
My computer for some reason isnt recognizing the phone, so i cant put any files on it. when i hit reboot, it just goes back to twrp....
should i do a recovery of my backup?
xzero425x said:
My computer for some reason isnt recognizing the phone, so i cant put any files on it. when i hit reboot, it just goes back to twrp....
should i do a recovery of my backup?
Click to expand...
Click to collapse
Did you flash a ROM? After wiping....you could use koush universal drivers and sideload a ROM if your stuck in recovery.....sounds like you Dont have a rom
RubbleTea said:
Did you flash a ROM? After wiping....you could use koush universal drivers and sideload a ROM if your stuck in recovery.....sounds like you Dont have a rom
Click to expand...
Click to collapse
i tried flashing gummy 4.4.2 and it keeps failing, no idea why. maybe the older twrp.
xzero425x said:
i tried flashing gummy 4.4.2 and it keeps failing, no idea why. maybe the older twrp.
Click to expand...
Click to collapse
OK do you have signature check off? Do you have gapps too?
RubbleTea said:
OK do you have signature check off? Do you have gapps too?
Click to expand...
Click to collapse
yes and yes
the error it gets is - error executing updater binary in zip (where my file is)
:good:
xzero425x said:
yes and yes
Click to expand...
Click to collapse
Ah....2.6.3.2 doesn't support 4.4 Roms man try philz recovery
RubbleTea said:
:good:
Ah....2.6.3.2 doesn't support 4.4 Roms man try philz recovery
Click to expand...
Click to collapse
Derp. Alright well. whats my best bet from here? My computer isnt seeing the device atm and i dont have a rom?
Recover my old image and see if that works or something else?
xzero425x said:
Derp. Alright well. whats my best bet from here? My computer isnt seeing the device atm and i dont have a rom?
Recover my old image and see if that works or something else?
Click to expand...
Click to collapse
Crap guessing you don't have a backup......try using koush universal drivers to get your phone recognized...and use adb to sideload a ROM or use adb to push the philz cwm recovery zip to your recovery
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
If you want to sideload a ROM its easy and I'll guide you through or you can push a zip with adb to your recovery
RubbleTea said:
Crap guessing you don't have a backup......try using koush universal drivers to get your phone recognized...and use adb to sideload a ROM or use adb to push the philz cwm recovery zip to your recovery
Click to expand...
Click to collapse
no no! i do have a backup! Thats what i meant from restoring my old image. Ill recover my back up now, then hopefully put the newer twrp on it, then flash the 4.4 rom. hopefully
xzero425x said:
no no! i do have a backup! Thats what i meant from restoring my old image. Ill recover my back up now, then hopefully put the newer twrp on it, then flash the 4.4 rom. hopefully
Click to expand...
Click to collapse
Yah try the backup...the newer twrps for tmo aren't official either so you'll have to find
RubbleTea said:
Yah try the backup...the newer twrps for tmo aren't official either so you'll have to find
Click to expand...
Click to collapse
the backup is restoring now, taking a bit
xzero425x said:
the backup is restoring now, and i cant even find the new twrp in that list, sadly bc i cant figure out the name for the tmobile lgg2. like my old nexus was "toro" but im not sure what this is "called"
Click to expand...
Click to collapse
If you want to flash 4.4. Try the philz cwm recovery link...its a zip so just flash and reboot recovery....there's a unofficial 2.6.3.4 in android development section but no longer supported......I would choose philz over 2.6.3.4 IMO only....and thanks for all the thanks!!!! Just saw them
RubbleTea said:
If you want to flash 4.4. Try the philz cwm recovery link...its a zip so just flash and reboot recovery....there's a unofficial 2.6.3.4 in android development section but no longer supported......I would choose philz over 2.6.3.4 IMO only....and thanks for all the thanks!!!! Just saw them
Click to expand...
Click to collapse
haha thank you! Alright, my phone is alive, im downloaded the philz recovery. going to flash it and try the 4.4..again, haha here we go
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
MGREX said:
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
Click to expand...
Click to collapse
Just reflash the rom.
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
or pull the boot.img out of the rom zip and use the flashify app to flash it. the boot.img is the kernel. but honestly, it sounds like you have absolutely no idea what you are doing. if you have any questions, please ask, im willing to help. can you explain what happened?
Yeah I screwed up, didn't notice it wasn't CAF
22sl22 said:
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
Click to expand...
Click to collapse
It's 11.0-InstallerXNPQ08Q
Thanks!
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
MGREX said:
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
Click to expand...
Click to collapse
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
simms22 said:
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
Click to expand...
Click to collapse
I'm able to force-access recovery and CWM but that's it, once it boots it gets stuck on the splash screen, and thanks to the lack of a SD port I'm unable to easily load a kernel or ROM, and despite having the android SDK I'm unable to sideload the file through adb on Windows.
Any ideas? besides trying the adb through Linux (I'm doing that now)
Here's the flashable kernel zip taken from Snapshot M7 build :good:
Okay now it gets stuck in the cyanogenmod boot animation
Any ideas? that don't involve wiping everything I mean
simms22 said:
or pull the boot.img out of the rom zip and use the flashify app to flash it
Click to expand...
Click to collapse
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
MGREX said:
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
Click to expand...
Click to collapse
What about TWRP?
Sent from my Nexus 4 using Tapatalk
22sl22 said:
What about TWRP?
Click to expand...
Click to collapse
You mean installing TWRP?
BTW that problem is with the kernel I assembled using a CM11 ROM, your zip actually does boot into cyanogenmod but it gets stuck in the CM boot animation
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
MGREX said:
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
Click to expand...
Click to collapse
No problem
Do a titanium backup that backs up all your apps with data. Always have a backup so if things do go wrong you can just wipe and restore apps afterwards :good:
Sent from my Nexus 4 using Tapatalk