i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed @Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. @Heisenberg @Vivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
vicelord97 said:
i need help this problem has been there with me since i bought my opo 2 months back. i received it with cm11s build which was not official. so i had to manually upgrade my opo to cm12s after that i have flashed many lp roms even cm12.1s but never a kk rom. then i felt like going back to kk i flashed Bobbi lim cm11s mod rom 3.5 and i got no service tried many things still no service i then flashed cm11s 44s factory image but still got no service. then i gave up and continued to stay on lp roms. then till recently i found that it was not the roms but the modem if i flashed lp modem on kk roms i got service but with black screen bug but when i flashed back kk modem again no service.
please help me is there something wrong with my opo hardware. HeisenbergVivek_Neel and anyone else who has solution to this problem.
sorry for making it so long.
Click to expand...
Click to collapse
Did you flash *fastboot images* of CM11S?
If yes and still if you are facing radio problems, please refer http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 and try out KK modems
Otherwise please flash OxygenOS and give it a try.
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
vicelord97 said:
@Mr hOaX i have flashed fastboot images of cm11s with toolkit and manually too still no service and as i have said i get service on all lp roms including oxygen os. I have tried flashing modems using twrp 2.8.6.0 still got no service whatsoever with kk modems but with lp modems i get service even on lp roms if i flash kk modem i instantly get no service after booting back up.
Click to expand...
Click to collapse
Firstly, make sure your TWRP is 2.8.6.0
Secondly, flash KitKat firmware before flashing any kitkat ROM.
Thirdly, don't use toolkits.
To your problem, here's my suggestion. Do a full wipe in TWRP. Flash KitKat firmware A FEW TIMES - PREFERABLY 5 TIMES. Each time with a cache and dalvik cache in between. After that do a full wipe again and flash the KitKat rom. Not sure if its placebo but that's what I did to get KitKat working after I switch back from 5.x to 4.4 and have the same problem as you.
If it doesn't work, do a full wipe in TWRP. After that flash factory images except recovery and userdata. You should be good to go to flash my ROM.
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Didn't help still got no service tried flashing fast boot image too manually still no service.
vicelord97 said:
By full wipe u mean clean flash or including internal storage?
And thanks will try and report back
Click to expand...
Click to collapse
vicelord97 said:
Didn't help still got no service tried flashing fast boot image too manually still no service.
Click to expand...
Click to collapse
Are you flashing fastboot images correctly? Full wipe = wiping system, cache, dalvik cache and data in TWRP
Related
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
kevinga said:
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
Click to expand...
Click to collapse
So just to make sure I understand this correctly you just want to know why you cant dirty flash CM11s rom over itself. First off you can dirty flash all you want but the issues you may or may not get are on you. Now may I suggest your wipe system when dirty flashing with TWRP. I check off dalvilk, cache and system whenever I upgrade or dirty flash.
Also this is still android and most if not all of the flashing rules still apply
The problem I have is with wifi. This developed a couple of days ago where I have to toggle airplane mode on/off before wifi will reconnect. I actually did a factory reset last night and it did not fix it. I am now thinking that I will need to do more. I suppose the wifi is monitored by the kernel? baseband? I am not sure that a factory reset would reset those things. I could be wrong.
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Hello xda community. I have a problem. I've been using Nexus experience rom(MM) and i've decided to go back to LP. I tried so many LP roms and after a short use(1 hour to 1 day, depends on rom) it gives me a bootloop. I tried 4-5 roms. One of them was my daily driver one month ago. Now I am using stock 5.1 with root and no problem at all. But why a custom rom gives me bootloop All answers appreciated.
Edit: Now i got bootloop on stock 5.1 too!! Please help!
Have you installed xposed framework?
No. The problem encountered after CM. I formatted system, data (not internal storage) but i got bootloops since then.
Have you tried flashing stock vía fastboot?
Nope, but is there any difference between flashing via fastboot or recovery?
well if you flash stock via fastboot, it will also reset some partitions and system files like radio/modem or gps
flashing via recovery just changes the OS and kernel
Than you. And is this procedure needs full wipe?
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
You said you did the wipes when you flashed, did you mean that you did factory reset, wipe cache and wipe dalvik cache? Or did you mean that you did the advanced wipe options to wipe system partition and data partition before flashing?
If you didn't do the advanced wipe before flashing then it might help if you did them before flashing. Wipe system and wipe data then factory reset then flash ROM then wipe cache and dalvik after flashing then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I flash stock roms through Odin with the .tar.md5 file.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I have tried all the factory reset/wipe cache suggested on other threads and websites i have found regarding bootloops.
When going back to CM13 after trying methods to get stock back i flash TWRP again as flashing stock through Odin replaces TWRP with stock recovery again and then do a restore of CM13 through TWRP with all my necessary apps on, much easier than installing everything again after each try (a fresh install of CM13 also works fine with no problems). I also tried various versions of Odin just in case it was a problem with the version i used but every time i get the same same results.
I am flashing full pure stock from sammobile.