Database Info

[solved] OTA update (176.44.1) fails w/ CWM or ends in bootloop w/ stock recovery

Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2

Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6

I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed

CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2

I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2

Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install

total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir

Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!

So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?

Thanks!

Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day

Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse

Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app

I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation

Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing

Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...

i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)

[Q] I can't install custom recovery. It just reboots.

Hi guys! I am stuck with a dilemma if I should format my phone. I am quite aware of the dev tools as an IT student but this is the first time I've experienced this problem:
First I stupidly installed Nexus 5's Ambient Display mod without making a backup of the apk's affected resulting for I guess maybe a coincidence but I cannot install the 5.01 OTA as when I went back to the original recovery, I get the green Android logo and "Error" under.
So I flashed via the flash-all.bat the 5.01 stock firmware from Google but removed the userdata.img as I don't want to lose any of my files. It worked seamlessly. No lags, no crashes, bootloops, nothing.
Now, my problem is I want to get the Ambient Display 5.01 to run again, but this time when I tried installing CWM/TWRP via fastboot, it says okay then when I select recovery, it goes back to the Google logo then it boots normally.
What do you guys think is the problem? Should I re-flash the whole firmware? BTW I was able to root my phone the other day. So I don't know what's up. Any suggestions would be great. Thanks!

Remove the scripts in the ROM that flash stock recovery on boot. Then, fastboot flash the recovery of your choice.
http://forum.xda-developers.com/google-nexus-5/help/flash-recovery-stuck-dead-android-t2978052

[Q] New type of Boot logo hang issue

I am getting a hang on the bootlogo
This happened after installing the OTA for 44S. if I boot reboot the phone 20 or 30 times I can get past it.
TWRP works fine. if you pay close attention when booting into recovery you see the 1+ logo, and just before TWRP loads the screen goes slightly brighter.
When booting into system, you usually see the 1+ logo, and then the screen goes slightly dimmer. Just after this the logo should change into the rotating animation.. This is where my phone hangs. Just after it goes dimmer but before the logo starts to animate.
Now here is the weird part. I've done all the tricks, returning to stock 44s deleting all the partitions and re creating them, deleting cache, dalvik, flashing a persist.img or manually creating that partition, etc etc. after many days of crying and swearing I flashed stock 38R. it boots 100% of the time. I flashed Calkulins 44S rom, back to hanging on boot. I then restored ONLY the boot partition from 38R, and my phone boots 100%
I can't stay on 38R boot/kernel as I have the jumpy touch screen and a few other bugs which 44S fixes.
Does anyone have any ideas?
In a nutshell, 44S boot hangs 95% of the time.
38R boot image works all the time for booting (but I need the bug fixes from 44S)
(working kernel: 3.4.0-cyanogenmod-g33fa374 [email protected] #1 mon Oct 6 11:03:38 PDT 2014)

Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon

timmaaa said:
Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?

artymarty said:
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?
Click to expand...
Click to collapse
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon

timmaaa said:
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon
Click to expand...
Click to collapse
Oh I wiped and formatted it so well Timmaaaa, the paint started coming off!
I'm not the only one with the problem, I found a thread in the oneplus website forum that a staff member had posted with that 38R recovery zip that basically said they had so many support claims about boot logo hangs they were going to ignore them all and to just run that recovery procedure as it fixes them all. There are a lot of posts saying "hooray! It fixed it!" followed by "the phone said there was an OTA update to 44S which I installed and now it's not working again"
Such a great phone apart from stupid bugs like this and God awful support. Apparently if you run colour OS it doesn't hang, but who wants to run that?

OnePlus Bootlop, can't enter recovery, when I do bootloop persists

I should note that I've had serious issues with this phone for the last two months. Touch, reboots, everyhting, boot loops, everything. Only flashed CM because Oxygen stopped working. CM was running sort of ok after the touch boot.img fix but worked something like 10 hours only with no changes to phone at all.
Running CM12.1 yesterday phone crashed, completey wiped, restored. Still issues. Ran the persist partition fix "make_ext4fs /dev/block/mmcblk0p15" (using latest twrp) and it worked.
Today crashed again, started into CM a few times, crashed a home screen or lock screen, then refused to boot, crashing at the OnePlus logo, sometimes turning off. It now crashes from recovery too, sometimes not even being able to enter recovery.
I've made a paypal dispute now, this is insane, no phone has ever caused me this much trouble, even after soft bricks they've been easily fixable. I'm out of patience now. I hope to find some sort of answer or explanation for this.
(sideload doesn't work)

Managed to get it into recovery, adb push worked after some issues, installing CM 12.1 latest nightly now. Will report back.
Edit: Phone returns to bootloop while installing. Will flash new TWRP from Fastboot.
Edit 2: Phone is now seemingly booting into CM.
Edit 3: Phone crashes at "enter wifi password"...

Flash the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon

Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you, pushing ooold recovery now and will test, will do yours if that fails. Which it probably will....

Followed your steps : Booted, crashes when signing in to google... FFS now when starting. AAAAAAAAAAAAAAAAAAAAAAAAARGH

Kind of bricked my OPO in a weird way after 3 years.

I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage

naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Change the battery. U are not only one... There are lots of people had this issue after 2.5+ year including me. I changed battery two days ago (not original) now its work normal.
https://forum.xda-developers.com/showthread.php?t=3565871
https://forum.xda-developers.com/showthread.php?t=3610933
Sent from my A0001 using Tapatalk

naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Did you tried flashing stock Cos13.1.x through fastboot?

Mr.Ak said:
Did you tried flashing stock Cos13.1.x through fastboot?
Click to expand...
Click to collapse
Yup I've tried that

naeem76 said:
Yup I've tried that
Click to expand...
Click to collapse
So,what happens after that? Does it boots?

Mr.Ak said:
So,what happens after that? Does it boots?
Click to expand...
Click to collapse
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
Here this one, it was weird, it never booted afterwards

Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted

naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
Device works fine when it is in TWRP? Like,no reboots or power off(s) whatsoever? Battery works fine in TWRP? Like,charging and stuff? If it does,then this is unlikely a battery issue,however,I would suggest you to remove battery(go through tutorials on youtube) and attach it again.
This has happened to me before,like if I'm not able to flash anything from TWRP then I just change/update recovery to unofficial/newer versions of it(did you tried this?) or,I just flash Cos13 through fastboot then it boots up fine and I flash TWRP again and boom,everything is back to normal.In cases where I'm even fail to flash Cos13(shows system error/system partition corrupt) or I'm not even able to boot to fastboot i.e.,hardbrick,I just use Cm11S restore tool(modified version of color os toolkit,you can find on general thread) and it flashes perfectly fine and boom,device is back!
I hope it helps!
Ps- This is the tool I'm talking about,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I always use this because after flashing from color os tool,I used to get bootloop,though fastboot mode was accessible then so I could just flash Cos13 through fastboot and I no longer get any system errors and it boots up fine.

naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.

It happened to me once. I had to erase every partition via fastboot, not only system data and cache, but also modem, efs, recovery ecc. Then I flashed stock COS13.1 partitions images and it worked. Just remember: do NOT turn off or reboot your phone between the erase and the flash, it could hard brick the device!
edit: You should also backup your existing efs partition via recovery.

Fixed my device. For future reference, it was a battery issue, Just couldn't retain enough charge, enough to boot into recovery but not enough to boot any ROM, Changed battery and everything is back to normal

Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now

naeem76 said:
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
Click to expand...
Click to collapse
@psxda97

Mr.Ak said:
@psxda97
Click to expand...
Click to collapse

psxda97 said:
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
Click to expand...
Click to collapse
psxda97 said:
Click to expand...
Click to collapse
My trust on you

naeem76 said:
My trust on you
Click to expand...
Click to collapse
LOL!
I'm glad it worked