Related
I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.
I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.
Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.
I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.
I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2
Hi, I Need Somebody Who Can Fix The Failed From TWRP.
I'm Using cm-11-20140914-NIGHTLY-bacon.zip
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E : Error executing updater binary in zip '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
E : Error installing zip file '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
Basically i've done an advanced wipe removing EVERYTHING from the phone then installed
cm-11-20140912-NIGHTLY-bacon.zip
then tried to update to Using cm-11-20140914-NIGHTLY-bacon.zip but same error happen so factory reset
and now this error happen again!
Pissed off of doing factory reset everytime.
So i need somebody who can find a way to remove the incompatible data without doing a factory reset.
WoohWooh said:
Hi, I Need Somebody Who Can Fix The Failed From TWRP.
I'm Using cm-11-20140914-NIGHTLY-bacon.zip
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E : Error executing updater binary in zip '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
E : Error installing zip file '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
Basically i've done an advanced wipe removing EVERYTHING from the phone then installed
cm-11-20140912-NIGHTLY-bacon.zip
then tried to update to Using cm-11-20140914-NIGHTLY-bacon.zip but same error happen so factory reset
and now this error happen again!
Pissed off of doing factory reset everytime.
So i need somebody who can find a way to remove the incompatible data without doing a factory reset.
Click to expand...
Click to collapse
Try re-downloading the update and try to install that. If that doesn't work, just wait till tonight when another update is released.
I am using PhilZ Touch to install Nightlies without issues.
If you installed TWRP 2.8.0.0 there is a bug that prevents you from flashing. Update to 2.8.0.1:
http://techerrata.com/browse/twrp2/bacon
f231f said:
If you installed TWRP 2.8.0.0 there is a bug that prevents you from flashing. Update to 2.8.0.1:
http://techerrata.com/browse/twrp2/bacon
Click to expand...
Click to collapse
Thank You Man
Fixed :good:
OK, I seem to be having the same issue as above. I've tried TWRP 2.8.0.1 and the latest Philz Recovery but neither can flash the latest Nightly (24th September). MD5s match and I get the status 7 error so not sure what else to do. I'm sure it's something in the script but thought I'd see if others are having issues
EDIT: Not to worry! Turns out you can't dirty flash CM11 over CM11S so I made a backup and flashed it new
I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it
sebreens said:
I had this problem, that I couldn't turn on WIFI. I didn't want to use the internet so flashed lollipop 5.0.1(from 4.4.4). When flashed to 5.0.1 it was rebooting every time the screen locked, so decided to go back to 4.4.4. At first everything was ok, but then the mobile network just stopped to work. I was ok to cope with the disabled wifi, but i really need the phone internet. What should I do? Already tried flashing stock and factory wiping a couple of times, didn't help
The 'tower' of signal strength looks orange, but there's an H on it
Click to expand...
Click to collapse
Using the right gapps version?
beekay201 said:
Using the right gapps version?
Click to expand...
Click to collapse
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?
sebreens said:
I'm sorry, but where can i check that?
if i download the zip from teamandroid.com, how can i install them?
Click to expand...
Click to collapse
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
beekay201 said:
make sure you're getting the correct gapps version: L and KK need different gapps.
KK: http://forum.xda-developers.com/showthread.php?t=2397942
L: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Click to expand...
Click to collapse
When i first tried to install it showed
* Incompatible GApss Currently Installed *
PA GApps can ONLY be installed on top of an existing installation of PA GApps. You must wipe (format) your system partition BEFORE installing any PA GApps package.
**** GApps Installation failed ***********
when i look lower i see
E: Error in ... (the specified image address)
(status 1)
Installation aborted.
when i try to install gapps the second time it shows
E: Can't make /tmp/update_binary
Installation aborted
what should i do?
(I didn't have CWM Recovery before, now I have it installed and rooted the phone)
OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.
beekay201 said:
OFC, you already flashed gapps.
Wipe /system, reflash ROM, flash correct gapps.
Click to expand...
Click to collapse
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
Well first of all. Flash TWRP. Trust me. Then solving your problems will be much easier than in CWM
sebreens said:
I don't get it. I've done it several times already, every time it showed that there is an incompatible version already. maybe the google stock image already contains some gapps?
the only time the install went through was when i just wiped /system and without reflashing rom tried to install the zip
maybe you can do a thorough step by step guide what i have to do? i thought that maybe i had to have root access, but after rooting nothing changed.
Oh, and i can't mount usb through CWM. if i proceed to startup, the device itself installs all the apps
Click to expand...
Click to collapse
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.
beekay201 said:
NOTE: Ofc, the factory image has gapps included. Google owns gapps, in case you don't know.
Due to lack of info, I was mislead to think that you was running custom roms, and not a factory image.
The orange colored network indicators simply mean that you're not connected to Google Play services. This would NOT prevent you from accessing the internet on a browser for example - doesn't matter if on wifi or on mobile data - visiting www.google.com.
If you want to get a clean/fresh start, flash a factory image. I assume you know how to, so if you don't go read the guides on General. It's very simple.
That said, after flashing a factory image, and booting it, EVERYTHING should just work: adding your google account, connection to google play services, everything.
If you want to run custom roms, then you'll need a custom recovery (as suggested, TWRP), a custom rom, and an appropriate gapps version. Simple.
Click to expand...
Click to collapse
Ok, so I should just contact warranty if I got this after flashing stock? I cannot turn on wifi (the problem persisted before flashing) and now I have no internet connection. (I checked all the providers, and I have the right ones set there)
What should I do before I bring it to the warranty service?
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
What Official Lolipop ROM ? Maybe ask in the appropriate ROM thread ?
Cholerabob said:
What Official Lolipop ROM ? Maybe ask in the appropriate ROM thread ?
Click to expand...
Click to collapse
The one OP posted on their site:
https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
To the OP, reflash TWRP and then flash the GApps again
Are you able to access the phone through ADB or FASTBOOT?
nboorla said:
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
Click to expand...
Click to collapse
You'll have to install TWRP again using fastboot.
I did the same as you. I used one of the toolkits it can be done quite easily just take your time. You can actually Google Play store apk in the browser and install it.
I'd just open developer options enable debugging and plug the phone in your PC and allow drivers to install.
Then download one of the toolkits and install TWRP your bootloader should still be unlocked.
Once I found the toolkit the other night and installed it I was up and running in minutes.
Solved
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
nboorla said:
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
Click to expand...
Click to collapse
The same tool can be found on XDA:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
nboorla said:
Thank you all for the swift replies. I tried flashing TWRP multiple times but couldn't get it done. Then I chanced upon this link in another thread.
account[.]onepluscontent[.]com/downloads/tools/oneplus-one-reflash[.]zip
It's a zip file from OnePlus which when extracted will give you drivers (I didn't need them) and a ReadMe file that explains how to get the OPO back to just the way it was when you unboxed it. It's incredibly simple and hardly takes any time. After that I was able to easily flash TWRP and root the phone.
Click to expand...
Click to collapse
Well done.
I know you will note the ROM you flashed is an Alpha ROM. So though 'official', is still very new, as the OP advised.
Fresh ROMs can be a lot of fun to bug hunt, and a lot of time to work through, until the components are ripe, when they have heightened depth, balance, finesse, intensity and end, where the ROM has become pure, vibrant, opulent and mature; a ROM that is seamless.
The dream.
nboorla said:
Hi,
I rooted my OPO a few days ago and installed the unofficial CM12 Lollipop based build using TWRP and everything worked just fine.
Now a few hours ago I downloaded OnePlus' official Lollipop ROM and flashed the recovery after wiping data, cache and dalvik cache. Having done so and booted the phone I went back to recovery to flash Gapps only to realize TWRP wasn't available anymore. The screen showed android's recovery interface with touch disabled. I attempted to install Gapps after copying that to the phone's memory but failed to do so.
When I scroll down using the volume rocker and attempt to "apply update from sdcard" I get an error message saying:
"E:error opening /data/media/0: Permission denied
-- No package file selected. "
Now without Gapps I do not have access to Google Play Services, sync, backup of contacts or even the Play Store.
I tried rooting the phone again, flashing TWRP etc. But no matter how many times I try the phone just won't show TWRP in recovery
So now I'm stuck with a phone without any Gapps and no Play Store from which to download even the most basic apps. APKs can't be installed either because there's no app to open them.
Can anyone help me please?
Click to expand...
Click to collapse
Did you unmount system before installing?
Save time and flash to stock CM11S
For anybody that is stuck in this situation as I was too. Just load the stock CM11S and perform this through fastboot.
Example >fastboot update cm-11.0-XNPH44S-bacon-signed-fastboot.zip
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!