OK so here's what's going on.
I have a nexus 6p OTA 7.0 build rooted. I downloaded cm 14.1 and the correct Gapps which is Android 7.1 arm64 I used full version.
Booted to custom recovery and wiped all but internal storage. Then went to flash as usual flashed cm14.1 first. Yes downloaded from the CyanogenMod site official release. Then flashed the Gapps mentioned. And wiped cache after each installion.
Rebooted system and it loads the cm loading screen as should be. But the issue lies within this....it's takes 10-15 minutes to boot and goes straight to "Android system, there's an internal problem with your device. Contact your manufacturer for details" message. Hit OK and phone runs...set up completely goes through and everything. Once set up is done the message "cm bug report has stopped working" shows up.
I did use wugfresh toolkit to do all of this at newest version with all current updates.
What can I do to fix this error? Is it in the 14.1 ROM? Is it the Gapps? Or what's going on if someone can explain or help that'd be great. Again phone is working and fully functional but that internal error message is really concerning to me.
jessyjoseph2044 said:
OK so here's what's going on.
I have a nexus 6p OTA 7.0 build rooted. I downloaded cm 14.1 and the correct Gapps which is Android 7.1 arm64 I used full version.
Booted to custom recovery and wiped all but internal storage. Then went to flash as usual flashed cm14.1 first. Yes downloaded from the CyanogenMod site official release. Then flashed the Gapps mentioned. And wiped cache after each installion.
Rebooted system and it loads the cm loading screen as should be. But the issue lies within this....it's takes 10-15 minutes to boot and goes straight to "Android system, there's an internal problem with your device. Contact your manufacturer for details" message. Hit OK and phone runs...set up completely goes through and everything. Once set up is done the message "cm bug report has stopped working" shows up.
I did use wugfresh toolkit to do all of this at newest version with all current updates.
What can I do to fix this error? Is it in the 14.1 ROM? Is it the Gapps? Or what's going on if someone can explain or help that'd be great. Again phone is working and fully functional but that internal error message is really concerning to me.
Click to expand...
Click to collapse
Flash the vendor.img that is linked in the CM 14.1 OP. This will resolve the "internal problem" error:
http://forum.xda-developers.com/showthread.php?t=3498453
Sent from my Nexus 5X using Tapatalk
Do I just enter recovery and flash it there? Do I need to reset the phone and do a clean flash as well? Or can I just download the vendor.img and boot to recovery and flash it. Thanks for the info
SlimSnoopOS said:
Flash the vendor.img that is linked in the CM 14.1 OP. This will resolve the "internal problem" error:
http://forum.xda-developers.com/showthread.php?t=3498453
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Do I just enter recovery and flash it there? Do I need to reset the phone and do a clean flash as well? Or can I just download the vendor.img and boot to recovery and flash it. Thanks for the info
Flash it within twrp, as written in CM14.1 OP
Related
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Same problem
cyborgmanu said:
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Click to expand...
Click to collapse
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
I also posted this is the Nexus 4 Community on Google Plus. I am going to try out what they said.
Here is the link:
https://plus.google.com/117172821556811787798/posts/dzVorg3JSUw
SOLVED!
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
Hey I fixed it! It finally booted up.
You need to use the first Factory Image, that is, the Android 4.2.2 Jelly Bean Factory Image.
Once you have flashed the image, the phone will boot up quickly - Mine booted in around 5 minutes I guess.
Here is the link - https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hey guys! So I just flashed cm13 on my zen5. And I'm having a problem with gapps. I have downloaded the x86, 6.0 pico version of it. The rom flashed fine i suppose. The issue is with gapps. As soon as I started to flash gapps, 3 lines of error came and went immediately. After that once again I tried and it showed it was done. I booted the rom after clearing dalvik and cache.(I'm dumb and I forgot to clear system data and all). So now, as soon as the OS boots, it gives me force close. For every single app. What to do? Please help.
UPDATE: UPDATE: The error was with TWRP it seems. None of the files are flashing through TWRP. Can you give me the latest/stable TWRP link for it? For the time being, I have no google play services whatsoever in my device. The rom is from dgadelha I think. CM13.1 20161205
TWRP 3.0 links
https://www.androidfilehost.com/?w=files&flid=52033
TWRP 2.8.x links
https://drive.google.com/file/d/0BzMGgN-tWY2zQnVucDdIUFlQdHM/view
https://drive.google.com/uc?export=download&id=0B05UM2q8MdJFb0VrV2oxTG5rTzQ
While I was on XOSP I faced the same problem so I had to go to 2.8.x version.
Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
I installed LineageOS with and without Gapps and it still crashes my Shield. Should I try a different build from Lineage's page? I was running 12/15/21 with Gapps 12/17/21. Is it common for LineageOS to crash, freeze and reboot by itself?
I installed the build from 12/15/2021 and have not experienced a crash, freeze or reboot yet. I have never tried to install gapps. So if you followed the installation instructions in the LineageOS wiki, it should work.
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
jenneh said:
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
Click to expand...
Click to collapse
I wiped the partitions in TWRP using your guide. I have not tried wiping those partitions manually in fastboot. That could explain the issue I was having. Thank you
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Kladderadatsch said:
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Click to expand...
Click to collapse
Thank you for sharing, this will Surely help someone else in the same shoes. Glad you got it working!~!
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Skel40 said:
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Click to expand...
Click to collapse
I'm sorry to hear that! But thank you for being honest and letting us know you are still having problems! I think you are correct that waiting for a more stable build is a good step.
I have only gotten my feet wet in kernel editing and manipulation, so It's A lot Lineage does for us, its just a matter of them getting the Science down to a good, clean, consise, logic
I have now replaced the lineage recovery with TWRP and the memory is now recognized.
I must say everything runs stable, without crashes or so.
Also wiping the partitions messes up with fastboot booting TWRP. I only was able to have Lineage recovery flashed and booted up using boot recovery kernel found in bootloader mode. I don't know what I'm doing wrong here but another issue is the recovery itself directly from Lineage. I tried to factory reset as it told me to after wiping the partitions and it failed. Emmc is not supported, factory reset failed.
What wouldn't make sense is it's not the Shield's power supply issue or any of the components failing after booting into LineageOS. Nvidia's OS works perfectly without constant freezing and reboots. Hopefully this issue can be resolved at some point. It's a bummer I've tried everything to get this far.
I the same problem and i noticed an error in the fastboot flash of mdarcy.dtb
I checked the batch file that you tasked it to and found
Fastboot flash mdarcy.dtb mdarcy.dtb.img
I changed it to fastboot dtb mdarcy.dtb.img
And it corrected the partition