Related
i unlocked my bootloader just to be able to flash the carbon rom on my xt925.
i downloaded the rom from various site(including goo.im)
but when i flash it i cant get it to work.
when i flash it and boot into carbon rom i just get a black screen.
i wipe the cache of the partition i am flashing the rom.
i am flashing via twrp by the way.
anybody got any idea of what i could do?
hugodefcon said:
i unlocked my bootloader just to be able to flash the carbon rom on my xt925.
i downloaded the rom from various site(including goo.im)
but when i flash it i cant get it to work.
when i flash it and boot into carbon rom i just get a black screen.
i wipe the cache of the partition i am flashing the rom.
i am flashing via twrp by the way.
anybody got any idea of what i could do?
Click to expand...
Click to collapse
Have you try Format system?
Factory reset, wipe cache/dalvic, format system, flash rom, flash gapps, then reboot... let it sit for a good few minutes just in case it's tkaing a long time to get through first boot.
I'm about to try carbon myself so curious to see how it goes for you... currently using PAC but it's incorrectly reporting my RAM as 675mb.
tzlot said:
Have you try Format system?
Factory reset, wipe cache/dalvic, format system, flash rom, flash gapps, then reboot... let it sit for a good few minutes just in case it's tkaing a long time to get through first boot.
Click to expand...
Click to collapse
This process should work for you and this is the ROM you should probably use. Official support w/ nightlies (Also it runs like a dream.)
Definitely just backup what you want to keep and factory reset, wipe all that stuff, and you should be fine
I was running LiquidSmooth 2.9. Decided to try the latest KK nightly. Downloaded everything, made a backup, etc. Went to flash and it said (status 7) error. Tried again, same thing. Decided to update to the latest TWRP and try again. Same error. Tried one more time and it worked. After the rom was loaded I immediately noticed that the rom was not stable enough for a daily driver.
Booted into recovery and tried to restore to my previous backup. For whatever ready TWRP could not locate the backup. I tried to move the back up for a while but it wouldn't move to the correct folder. I said screw it I will just download the Liquid Smooth 2.37 which was the latest official release and just reflash. Downloaded everything, then flashed it. Everything set successful, gaps and rom, but now it wont get past the splash screen. I have reflashed like 5 times now all without issue but stuck at splash screen. I can get into recovery fine.
What is my next step to revert back to my previous backup or reflash to a working rom? Any help would be greatly appreciated.
Odin my friend
Sent from my SCH-I535 using Tapatalk
I had the same problem on kk i had to do a factory reset wipe catche dalvik then flash liquid smooth kk pa gapps im working fine. Honestly my own opinion i prefer liquid 2.37 over kk. I read couple post ppl had to get the latest cwm recovery to flash KK roms
Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.
1967ls2 said:
Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.
Click to expand...
Click to collapse
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37
twistedillutions said:
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37
Click to expand...
Click to collapse
what recovery are you using? TWRP or CWM?
I'm getting no where.
1967ls2 said:
what recovery are you using? TWRP or CWM?
I'm getting no where.
Click to expand...
Click to collapse
Twrp
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!
SI have revert from the CM13 to Resurrection Remix (which is also a CM) however Im wanting to change to a predated ROM or even a different ROM and it isnt allowing me. In both CWM and TWRP it says the it installed just fine but when I boot up its still Resurrection and yes I have done all the wipes that should be done and still same thing happens.
How can I fix this?
OK
johneflik said:
Jut use advanced wipe in TWRP then wipe everything except the external SD. I guarantee no thing will boot again unless you flash it.
Click to expand...
Click to collapse
That did the trick, was able to flash again and put back on the ROM before it got stuck on RR. Idk what went wrong in that ROM change, had to edit Updater-Script and got CM13 going again
Just figured I'd give the heads up if you factory reset with a patched boot, for root or otherwise, it bootloops the phone twice and then goes to recovery. Flashing back stock boot img fixes it.
So don't be stupid like me and reset settings while rooted lol.
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Bradl79 said:
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Click to expand...
Click to collapse
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Chris123NT said:
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Click to expand...
Click to collapse
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
Yeah, I did, so I dunno what happened, but when I booted into the OS after all the steps WiFi was boned.
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
virtyx said:
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
Click to expand...
Click to collapse
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Bradl79 said:
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Click to expand...
Click to collapse
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
virtyx said:
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
Click to expand...
Click to collapse
I could be wrong but I believe the OP might be talking about the root files and not twrp. Prior to twrp release, factory reset was the only option. As it happen to me also, after rooting device.
Plus Oneplus did not include a rom install zip in the stock recovery.
Damn, this AB partition setup really makes things a hassle
Bumping because other people are getting tripped up by this. Something in the factory reset process is not compatible with any sort of mods.
This happened to me as well. Not sure how I recovered, as I flashed via fast boot a bunch of image files. Is the boot image in the image files the latest stock boot image for 5.1.5?
For those of us rooted and no TWRP can someone link the stock boot.img?
Nevermind I found them on the ota page by titokhan
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
That could be what's causing it, I did wonder about that.
Chris123NT said:
That could be what's causing it, I did wonder about that.
Click to expand...
Click to collapse
try it and let us know
So before factory reset we need to make sure to reflash stock boot.img that will unroot the phone and only then do a factory reset..
So factory reset with twrp is working or not?
Anyone know where I might be able to get the stock boot.img? My phone is now toast and the referred thread should carry a health warning
Sorry for the noob question but does factory reset delete the media partition too?
itsadme said:
Sorry for the noob question but does factory reset delete the media partition too?
Click to expand...
Click to collapse
No, it does not.
this happened to me too. I was thinking of flashing the latest OxygenOS 5.1.11 with a clean install and I am rooted with TWRP. So what I did was reboot to recovery, wiped data, flashed OOS, then TWRP, reboot recovery and then flashed magisk. Then it got stuck in a TWRP bootloop.
Good thing I had a nandroid so i restored it and tried again.
This time I did the above steps but didn't wipe data. I booted successfully to 5.1.11 and i tried Factory Reset inside OxygenOS. Phone rebooted to TWRP and no data wipe was done. I did the Wipe Data within TWRP, same thing happened... bootloop to TWRP.
Nandroid restored again.
3rd attempt to dirty flash 5.1.11 but this time i didn't flash TWRP nor magisk and just rebooted system. I was back to stock. Then I tried factory reset again within OOS, it was successful so i had to do the whole TWRP and Magisk install again, and restored my apps via Titanium.
Moral of the story is (at least for me), Factory Reset within OOS or Wipe Data in TWRP both doesn't work. If i need to do a clean install, flash OOS then factory reset after rebooting to system, and then go through the whole TWRP and Magisk install process from scratch. Pain in arse really...:crying: