I was running CM 14.0 with TWRP. I did a OTA download through CM Updater to 14.1 nightly. The phone rebooted to recovery and nothing happened. I manually found the OTA under sdcard/cmupdater and flashed the file. Now, whenever i try to boot the phone, it keeps going into recovery. I tried restoring nandroid backup, wiping everything and installing the older cm14.0 zip and nothing worked, phone keeps going into recovery, what can I do, please help!!
I think there are few users reported same issue before.
Try to check the ROM thread. If Im not mistaken, the solution has been posted there.
Hope this help. Good luck
Sent from my Nexus 4
Sorry, I panicked and didnt look through the forums thoroughly before posting. I managed to boot my phone up by flashing factory images and going back to stock. Afterwards, I tried to install the CM 14.0 again (StephanMC's build) which was working fine before I tried the update process. TWRP throws error 7 when I try to flash it. I looked around and found that the problem can be fixed by editing the Meta-INF, but I did not have this problem before, did I mess something up in the factory image flash process?
Would it be wise to go ahead and force install the ROM by editing the zip?
Related
yeah, im a dummy. i know. so when i told the phone to update it rebooted to the twrp recovery and stopped because twrp is a straaaaaaaaaanger. first it must have wiped or something though, because reboot brought twrp back up. wipe, restore, reboot, twrp. ok, wiped, flashed different rom and gapps, reboot, twrp. apparently twrp is the only thing on the phone? ive never pulled such a boner so im stuck as to what to do. every thread about restoring stock is full of links to 404s and other files that are no longer there. anyone have any ideas?
Just looked it up everything is there to use the lg flashtool and all files to return to zva stock.
i used the dev/zero fota/misc fix. after starting this thread i found a thread making this one redundant but OPs cant delete the P i guess. if a mod wants to delete this thread, i wouldnt be mad at them haha.
Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
oneunder311 said:
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
Click to expand...
Click to collapse
Which guide did you follow? What steps did you exactly take and which version nougat rom you have and which oreo build(stable/beta) do you want to install?
There are plenty of instructions, like this one here: https://forum.xda-developers.com/showpost.php?p=75155514&postcount=8618