So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
bogomil4e said:
So I did everythign I normally do with a new device!
1)I unlocked it through Fastboot
2) I downloaded the latest TWRP recovery image for that device and flashed it with Fastboot
3) I rebooted the device into recovery to check if everything is ok.
4) Proceeded to download Cyanogenmod for Nexus 6p (Angler) and OpenGapps ARM64 for 6.0 stock package and put them on the phone
5) Opened the Zips from the phone to check that none are corrupted
6) Wiped Everything on the phone via Advanced Wipe incl System, Data, Cache etc,
7) Flashed Cyanogenmod Zip first after that the Gapps package
8) Rebooted to System and waited for the phone to finish its first boot
This is where my problems begin. No matter what I do and how much I toubleshoot the first boot never seems to finish. I have played with devices long before I got the 6p and know that the first boot taked a long time but not this long!
I checked if it was the recovery, or the CM zip or Gapps but no matter how many scenarios I try and rule out Im stuck at the CM boot logo (Which seems pretty laggy). I even tried without gapps.
I searched online and cant find ppl with a similar problem. There are people who cant get past the Google logo but I get past that with no problem. Its just that I cant boot the OS.
I even checked a few guides to see if I missed a step when I was doing it on my own but no! I have done everything absolutely correctly and cant seem to find an issue this time (usually finding issues with Android and repairing them is my specialty ).
I can not think of ANYTHING that ive missed here. I just cant seem to find the problem. The hardware boots Stock/Factory imaged perfectly so its working fine. Where am doing wrong?
Click to expand...
Click to collapse
I'm not sure but on an old HTC phone I had the same issue which was caused by a mismatch between the rom version and phones firmware. I'm not sure how it works on the nexus hope someone here can help
Try different GAPPS ?
Sent from my Nexus 6P using Tapatalk
Have you tried flashing a vendor zip yet? Sounds like not booting cause missing binaries.
https://www.androidfilehost.com/?w=files&flid=43551
If you're able to get to twrp, wipe everything, flash cyanogen reboot, and then flash a different gappd
Sent from my Nexus 6P using Tapatalk
You must format data in TWRP or it won't boot.
Related
I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!
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 really want to run PA on my nexus 6p.
Everytime i install i get 2 corrupt system warnings one in yellow one in red.
Phone doesnt work correctly other members are running this rom just fine
flashed super su,updated vendor image,tried new download what in the world could be the problem.
Freezes reboots,phone apk wont work etc.
A. The "error" message you see is normal when you unlock and ROM your phone. It started with the Nexus 6p and 5x.
B. In recovery, wipe data, system, then install ROM, GAPPs. Boot and verify it works. Then reboot to recovery and flash the latest SuperSU.
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
Basically, I went completely from stock (already unlocked the BL):
1. Installed TWRP 3.3.1-0
2. Rebooted to TWRP and did a factory reset (because it said so on the install guide: https://docs.omnirom.org/Installing_Omni_on_your_device)
3. Flashed OmniROM 9.0 Weekly from the SD card
4. Unsuccesfully installed Open GApps because error 64 (apparently was supposed to use the ARM64 version, even though CPU-Z stated I was on ARM)
5. Installed Magisk 19.3
6. Wiped Dalvik/ART cache and Cache partitions
7. Installed TWRP app to /system and rebooted
Now it gets stuck on the Sony logo every time I power it on.
I tried leaving it for about 15 minutes to see if it was taking so long because of a fresh install, but previously I tried installing Paranoid Android and the boot up took only a few seconds, so obviously that wasn't going to work.
I tried rebooting multiple times, wiping the cache partitions again, uninstalled the TWRP app, did another factory reset, tried fixing contexts, and it still gets stuck on the Sony logo.
At this point I'm not sure if I should just give up, because none of the ROMs I tried flashing actually worked, which includes Resurrection Remix, Paranoid Android and LineageOS, and now OmniROM as well. So far, I haven't found anyone with the same problem as me, except https://www.reddit.com/r/SonyXperia/comments/acot9y/trying_to_install_omnirom_on_my_x_compact_stuck, but that's not quite the same.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
z0mg.jer1Cho said:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
Looks like u skipped Step #3
Click to expand...
Click to collapse
Right, I'm an idiot. I'll try again and see if that works.
ŽeljkoLončar said:
So I decided to finally flash OmniROM 9.0 on my XC, and started having some problems.
EDIT: After flashing the ODM image, the phone booted up, but it's asking me for a password. I tried typing "password", and it said the password was correct, but my data was corrupt. It offered me a factory reset, but it made no difference. This is nothing new to me, the same thing happened when I tried flashing Paranoid Android. Should I do a clean install, like, wipe Internal storage and System?
Click to expand...
Click to collapse
Did u boot the Phone after u've installed the default firmware?
z0mg.jer1Cho said:
Did u boot the Phone after u've installed the default firmware?
Click to expand...
Click to collapse
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
ŽeljkoLončar said:
Yes, I did. Went through the setup and everything. Ttied it multiple times, didn't make a difference.
Click to expand...
Click to collapse
Dont boot the Phone after installing the Factory Firmware. After u've installed it, just go on with the flashing procedure as told you in OPs thread
Same issue
I have exactly the same issue. Recovery successfully flashed, did a factory reset, successfully installed Omnirom, and then I reboot into a permanent white screen with the Sony logo in the center...
After several tries I gave up and installed the stock firmware again using Sony's flash tool Emma.