Database Info

problem flashing roms on moto g xt1032

Hi, I'm new to flashing roms and after installing CWM 6.0.4.7 on my xt1032 and rooting whenever i try to flash a rom it gets stuck in the boot animation. I have tried CM 11 Carbon rom and paranoid android. I don't know if I'm using the wrong GAPPS or what. Please help.

Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app

skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
Ok thanks, I will try that when i have some free time. And how do you revert back to 4.3
never mind i found a post on how to testing now

Brick?
skorpionvenom said:
Gapps are not the problem:the same thing was happening to me. The real problem is the bootloader: if you are on kitkat, you have to revert to stock jelly bean (4.3), install custom recovery (for JB), root and flash the custom rom you desire. That's the only way that worked for me.
Sent from my falcon using xda app-developers app
Click to expand...
Click to collapse
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help

Go back to Stock and start from Scratch.
As long as you can enter fastboot you should be fine.

I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.

Worked
quizmaniac said:
Try this,when you get to the broken android follow the instructions in the link below for "external reset" this will reset your phone.
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth
if that fails just flash a stock 4.4 image with fastboot using one of the guides.
Click to expand...
Click to collapse
Yes thank you so much I'm back on 4.4.2 You guys are great

hello everyone
I have a question about PaulOBrien superboot root method (look in modaco forum the moto g root method 1).
I have a 16GB Moto G and updated to Kitkat via OTA.
yesterday I used the method 1 (superboot) on windows 7, to root my phone, and run it for the first time and ended on a black screen with green bars (supposedly normal). I power off the phone and turned on and load kitkat normally and noted that the phone was not rooted.
y tried the method for a second time and have the same results (ended on a black screen with green bars), but when kirkat launched, on the initial screen i saw a message "System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and the system didn't respond.
I performed a factory reset via stock recobey and kitkat showed the same message but let me in the "i´m feeling lucky button" worked this time. there I noticed that my device was now rooted but non app was able to access the internal memory due to some r/w permissions as I think, because when I try to copy files to the phone via USB cable, I get have the same denial, even whit ADB push i get the same message of permissions denial.
I need a way to solve this because in this actual stage the phone works but the apps have like no access to the memory making them unusable,
for example i cannot take a picture, or download a file, for some reason all google apps not work or force close every time.
I need a way to upload a .img file to the phone in order to perform a recobery or to make a fresh install via fastboot, donn't know how to make the phone let me wrhite files on it. :crying:
(note: sorry for my bad English)

A Wild Willis said:
I tried o revert to 4.3 but when flashing boot.img it said hab check failed for boot and now when i try to boot up it goes to the unlock booloader warning turns off and repeats. I can get back to fastboot but when i try to enter recovery it shows a broken android lying sideways. I think i bricked my phone. I really need help
Click to expand...
Click to collapse
As long as you can enter the bootloader you haven't bricked anything!!! so don't you worry!
I have two questions: when did you download the stock rom, did you check the MD5 ??? Are you sure that it wasn't a bad download ?
Additionally: are you sure that you have downloaded the appropriate ROM? Did you try to flash any other ROM?

will8578 said:
I too have suffered with this problem, today i have done as above said, reflashed 4,3 but when i onstalled the cwm 4.3 version i still suffered the same problem, so i tried the cwm4.4 and hey presto, i now have cm11 on my phone, yee haaa
Click to expand...
Click to collapse
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032

dreezz said:
i'm having troubles too...
tried to install custom roms (c-rom and liquid rom), coming from 4.4 (unlocked and rooted) stock but it stays at the bootanimation.
flashed a stock 4.3, rooted installed, tried 2 recoveries (cwm and twrp), tried c-rom once more...
same problem :crying:
i've run out of options, so have to flash a stock 4.4 again, unless someone gives me thé idea what i can do to make it work.
xt1032
Click to expand...
Click to collapse
I am having the same issue. I got this xt1032 after it was OTA upgraded to Lollipop 5.0.2 and I downgraded it to KitKat 4.4.4 Stock. Now I'm also getting stuck on the boot animations on every Custom ROM I try to flash on it.
Does anyone know if having the bootloader upgraded due to the Lollipop update has anything to do with this? mine is at Ver. 41.18.
EDIT: I was finally able to flash after Formatting Data from Recovery. Keep in mind this will basically delete everything from the internal storage and you need to put everything back there manually. Always make sure you backup your info/apps/music/fotos before Formatting Data.

[Q] Flash to stock 4.4.2 issues

I am currently trying to flash into stock rom 4.4.2. Everything is set up and i run flash-all.bat everything is fine until it finishes flashing the radio. After that it hangs when flashing image-hammerhead-m7864a-etc. for a while. I restart and trying doing it manually with each .img. I succesfully flash recover and boot and userdata.img, but system and cache seem to hang also. The cmd window never reaches the second ok and just sits there. Am i not waiting long enough or is there something wrong. The phone is responsive in the bootloader during the waiting, and there is no downloading, writing, or erasing message at the bottom.

How much time are you giving it? Some of then take a couple of minutes
Sent from my Nexus 5

jd1639 said:
How much time are you giving it? Some of then take a couple of minutes
Sent from my Nexus 5
Click to expand...
Click to collapse
I have waited up to half an hour, with no success.
I tried flashing the 4.4 image instead as my nexus5 is rev 11, supposedly before 4.4.2, but still the same problem. At one point it said out of memory error, so i flashboot formated the userdata and cache, but still hangsafter flashing radio. Some parts of the image-hammerhead zip are getting flashed, as a second cmd window pops up and runs, but as soon as that finishes and closes, the flash-all.bat is still stuck.
Edit: After getting stuck at this point, is it possible to flash an image correctly through stock recovery?
Edit2: fastboot -w update image-hammerhead-krt16m.zip seems to close when trying to flash system.img before it finishes, sometimes leaving the bootloader stuck in downloading.

apocalypserisin said:
I have waited up to half an hour, with no success.
I tried flashing the 4.4 image instead as my nexus5 is rev 11, supposedly before 4.4.2, but still the same problem. At one point it said out of memory error, so i flashboot formated the userdata and cache, but still hangsafter flashing radio. Some parts of the image-hammerhead zip are getting flashed, as a second cmd window pops up and runs, but as soon as that finishes and closes, the flash-all.bat is still stuck.
Edit: After getting stuck at this point, is it possible to flash an image correctly through stock recovery?
Click to expand...
Click to collapse
Yes with unlocked bootloader.
What problems did you have before wanting to flash stock images?

GUGUITOMTG4 said:
Yes with unlocked bootloader.
What problems did you have before wanting to flash stock images?
Click to expand...
Click to collapse
Is there an image of stock 4.4 or 4.4.2 someone could post here, i can only fined .tgzs.
I wanted to reflash to stock because my gps was unable to lock on any satellites, even after trying topntp along with gps status. I read in PA forums that some were having issues with that rom and gps, and that stock worked fine. I pretty much flashed to pa right after i got the phone last week, and never really tried gps under stock. I wanted to reflash to stock to check gps if it works, other wise I was going to RMA and hope for a newer batch (mine is from November, supposedly 312k batch works perfect gps wise).
Edit: found a stock zip: http://forum.xda-developers.com/showthread.php?t=2676691
Downloading and will flash when its ready
Edit: zip did not work (incorrect header/footer?) going to try flashing cwm recovery to see if that works.

apocalypserisin said:
Is there an image of stock 4.4 or 4.4.2 someone could post here, i can only fined .tgzs.
I wanted to reflash to stock because my gps was unable to lock on any satellites, even after trying topntp along with gps status. I read in PA forums that some were having issues with that rom and gps, and that stock worked fine. I pretty much flashed to pa right after i got the phone last week, and never really tried gps under stock. I wanted to reflash to stock to check gps if it works, other wise I was going to RMA and hope for a newer batch (mine is from November, supposedly 312k batch works perfect gps wise).
Edit: found a stock zip: http://forum.xda-developers.com/showthread.php?t=2676691
Downloading and will flash when its ready
Edit: zip did not work (incorrect header/footer?) going to try flashing cwm recovery to see if that works.
Click to expand...
Click to collapse
my previous answer was meant for using flash-all method.
you can't flash anything withing the stock recovery.

GUGUITOMTG4 said:
my previous answer was meant for using flash-all method.
you can't flash anything withing the stock recovery.
Click to expand...
Click to collapse
Yeah, ending up flashing cwm and the above image and it worked.
Gotta say as a relative noob to all this waiting for your device to boot after messing with adb/fastboot is kinda heartpounding.

[Q&A] OTA Collection

Q&A for OTA Collection
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for OTA Collection. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Problem with falshed x920e
hello all,
for a long time now i have some troubles using my htc butterfly x920e.
when i bought it, back in 2013 there was no 4.3 OTA available. so i dicided to root the phone and flash a custom rom.
the first issues came along because of the confusing different model numbers out there (dlxu, dlxub1, x920e, x920d) but finally flashed hboot 1.54, rooted it and the most importend, installed sense 6 + 4.4 KitKat in InsertCoin 2.4.0 Kernel. Erverything seems to run just fine that days after flashing my device.
nower days
there are many little things that comes along with the not perfect ported kernel,
but one thing drive me crazy!
the battery wont hold for more than 10h, maybe 12h if i just turn off everything + less than 10% brightniss (i even cant remember when i last used more than 40%) + just use the phone as clock! , running every day 2-3x to my power adapter.
it seems there be huge problems with the kernel and my device. just flash a new version of insert coin isnt that easy.
so i want to go back to ANY stock ROM that will improve the battery. i installed twrp 2.8.0.0 and downloaded the recovery out of this thread (4.3 for twrp) unzipped the .rar and copy it to the backup folder from trwp.
the device detect the recovery file, start to do his job. it runs through, finish and when it restart nothing happen! the HTC logo on white ground will show, after that it just get black an turns off.
so i get back to insert coin, just to have a working phone again.
is there a huge mistake when i think, that i can just restore with a recovery and stock ROM which i get here?
is there another step i have to think about when my devive is root and falshed with another kernel + ROM than the stock one, to get back to stock?

harriepotre said:
hello all,
for a long time now i have some troubles using my htc butterfly x920e.
when i bought it, back in 2013 there was no 4.3 OTA available. so i dicided to root the phone and flash a custom rom.
the first issues came along because of the confusing different model numbers out there (dlxu, dlxub1, x920e, x920d) but finally flashed hboot 1.54, rooted it and the most importend, installed sense 6 + 4.4 KitKat in InsertCoin 2.4.0 Kernel. Erverything seems to run just fine that days after flashing my device.
nower days
there are many little things that comes along with the not perfect ported kernel,
but one thing drive me crazy!
the battery wont hold for more than 10h, maybe 12h if i just turn off everything + less than 10% brightniss (i even cant remember when i last used more than 40%) + just use the phone as clock! , running every day 2-3x to my power adapter.
it seems there be huge problems with the kernel and my device. just flash a new version of insert coin isnt that easy.
so i want to go back to ANY stock ROM that will improve the battery. i installed twrp 2.8.0.0 and downloaded the recovery out of this thread (4.3 for twrp) unzipped the .rar and copy it to the backup folder from trwp.
the device detect the recovery file, start to do his job. it runs through, finish and when it restart nothing happen! the HTC logo on white ground will show, after that it just get black an turns off.
so i get back to insert coin, just to have a working phone again.
is there a huge mistake when i think, that i can just restore with a recovery and stock ROM which i get here?
is there another step i have to think about when my devive is root and falshed with another kernel + ROM than the stock one, to get back to stock?
Click to expand...
Click to collapse
Have a look on here somewhere. There is a stock TWRP backup. Give that a try. Or you can find a Boa rom and flash that.
Let me know how you go.

I just tried to install the stock 4.3 twrp backup, a user posted in the OTA x920e thread. It runs complet through but after reboot, the HTC Banner just disappear, followed by black screen / device off. Maybe because of the trwp Version? I installed 2.8.0.0 , for dlxub1 .
What means "boa update" , sry about the bad knowlegde.

harriepotre said:
I just tried to install the stock 4.3 twrp backup, a user posted in the OTA x920e thread. It runs complet through but after reboot, the HTC Banner just disappear, followed by black screen / device off. Maybe because of the trwp Version? I installed 2.8.0.0 , for dlxub1 .
Click to expand...
Click to collapse
It's not because of twrp. You have incompatible firmware with stock 4.3.
Do you know how to post info from fastboot?
Just go into fastboot and use command "fastboot getvar all" and post that info here, so I can figure out what you have to do.

bokithq said:
It's not because of twrp. You have incompatible firmware with stock 4.3.
Do you know how to post info from fastboot?
Just go into fastboot and use command "fastboot getvar all" and post that info here, so I can figure out what you have to do.
Click to expand...
Click to collapse
Finaly i got a stable internet connection at home.
i captured a screenshot with all the data from comman getvar-all :

harriepotre said:
Finaly i got a stable internet connection at home.
i captured a screenshot with all the data from comman getvar-all :
Click to expand...
Click to collapse
Because you are S-ON, You have to flash boot.img from backup manually from fastboot.
Or you can S-OFF your phone and just restore backup from twrp.
Procedure for flashing boot.mg S-ON users:
1. Go into recovery and do a backup
2. Download this stock x920e 4.3 boot image and rename it to boot.img
2. Follow this guide on flashing boot.img :LINK or this video guide :Video LINK
3. After that go into recovery, restore 4.3 backup from there, reboot and wait for ROM to boot.

I did it just the way you told.
the boot.img flash was successful.
after that i tried to restore with twrp and the 4.3 backup.
now i stuck right at the green logo on whte ground. nothing else happen..
what did i wrong?
bokithq said:
Because you are S-ON, You have to flash boot.img from backup manually from fastboot.
Or you can S-OFF your phone and just restore backup from twrp.
Procedure for flashing boot.mg S-ON users:
1. Go into recovery and do a backup
2. Download this stock x920e 4.3 boot image and rename it to boot.img
2. Follow this guide on flashing boot.img :LINK or this video guide :Video LINK
3. After that go into recovery, restore 4.3 backup from there, reboot and wait for ROM to boot.
Click to expand...
Click to collapse

harriepotre said:
I did it just the way you told.
the boot.img flash was successful.
after that i tried to restore with twrp and the 4.3 backup.
now i stuck right at the green logo on whte ground. nothing else happen..
what did i wrong?
Click to expand...
Click to collapse
You did nothing wrong.
Maybe firmware is not compatible with this stock rom backup. Radio is same as mine (updated on stock 4.3) so I thought it should work.
Also try 4.2.2 twrp backup. I think that one is the same as your original one before you started messing with roms. flash 4.2.2 stock boot.img same way.

bokithq said:
You did nothing wrong.
Maybe firmware is not compatible with this stock rom backup. Radio is same as mine (updated on stock 4.3) so I thought it should work.
Also try 4.2.2 twrp backup. I think that one is the same as your original one before you started messing with roms. flash 4.2.2 stock boot.img same way.
Click to expand...
Click to collapse
YES!
the 4.2.2 backup + boot.img worked!
thank u very much, this is everything i wanted

harriepotre said:
YES!
the 4.2.2 backup + boot.img worked!
thank u very much, this is everything i wanted
Click to expand...
Click to collapse
You're welcome, glad to help

No operating system left after GPE flash fail - plz help!

After literally two weeks of reading thread after thread attempting to understand this , I tried to go from a sense ROM to a GPE ROM and I tried to flash the GPE firmware following Digital high's instructions here..
Things did not work out as instructed I'm afraid and that is probably due to my not understanding enough....nevertheless following DH instructions left me with repeated flash failures. Finally the following flashes got me from firmware 5.0.1- the firmware I was already on- to this:
fastboot flash zip VZWm8LfirmwareTWRP.zip - success; followed by the same ' flush" flash - again, success:
then:
fastboot flash zip 5.1_6_firmware+hboot.zip - and again another "flush" flash with success
From the way I read it we are then to reboot to bootloader and proceed further with recovery flashing the rom, blah, blah.... , however, my little android guy is overlaid with a black screen (instead of white) and he is dead. I rebooted to recovery to see if I could flash the sinless GPE ROM which is my goal in the first place (yes I realize it is a 4.4.4 but NOTHING flashes in recovery now) but now I m out of ideas. I have no workable phone and I have to get my ass to a new job in the afternoon. Can anyone help with either finishing my goal to install the sinless ROM or restore back to the adrenaline ROM I was running? I don't want to restore as I am afraid I may have altered the firmware and thus brick if I do restore...PLEASE HELP!!!! PLEASE!
right now my phone is sitting on the charger on the dead android screen. i don' dare touch it. What should i do?
Update: I am flashing digital highs GPE_5.1-multi_dh_051215.zip and I am getting a bootloader remote 24 "parsing android info fail". Does anyone know what that means or how to fix?
Update again: Figured out this needs to be flashed in recovery and not fastboot. Now I have been booting for about five minutes now. Hope I'm not bootlooped. ....

Figured it out
Got it figured out.
Mods, could you please close the thread. thanks!

kerryh said:
Got it figured out.
Mods, could you please close the thread. thanks!
Click to expand...
Click to collapse
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.

cntryby429 said:
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
Click to expand...
Click to collapse
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?

kerryh said:
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
Click to expand...
Click to collapse
When compared to the steps I took to flash the 6/15 build as cleanly as I could manage, here's what jumps out to me as strange or unnecessary:
-I don't know what the '5.0.1 firmware' is but I suspect it's the same as the 'VZWm8Lfirmware.zip' you flashed next. I chose to run the 5.0.1 RUU and considered that as complete of verizon 5.0.1 firmware as there is.
-I don't think that superCID has been necessary for DHs GPE for some time. I don't know that it would necessarily cause a problem but I've never gone to superCID and have had no problems
-flashing DH's carrier-agnostic 5.1 firmware is stated as optional in his OP and I think DH himself admitted a little while back that it may actually be the cause of some folks' wi-fi issues
Regarding restoring old nandroids to a system with updated firmware, I can say that each time a new official software has been released, I've flashed tigerstown's firmware-only zips alongside whatever custom rom I was running at the time with no issues. This points to a trend of successfully running roms on top of newer firmwares without issues. I know of many 5.x roms saying that you must update firmware but I've never read about a 4.x rom having issues with 5.x firmware. I don't think there's much risk of flashing a custom rom (or restoring a nandroid) from recovery that doesn't match the firmware beyond a possible bootloop.

Problems with Nandroid backup

Hello!
I recently had my OnePlus One on RMA because of a OTA-update brick.
Now when I got it back from OnePlus, my device was now suddenly running OxygenOS based on Android 5.0. This is not what I want! Fortunately, I have done Nandroid backups in the past of the Cyanogen Android 4.4.4 which I wish and need to run. So I went ahead and unlocked the bootloader of my phone, rooted it and installed TWRP, which is the same as I used to take said backups. Then I took a backup of OxygenOS 5.0 just to be safe.
Now, the issue is as soon as I restore any of my old backups (I tested that these are working in the past.), the phone goes into a bootloop and refuses to start until I flash back the OxygenOS backup.
What in the world is going on here?

After reading around some, I am wondering if this is because the "modem" or "firmware" is different now from what it was before when the backups were working?
See Step 9 here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Is this my problem? Could I try it out safely by first restoring my backup and then applying one of those (Which? I am confused why there are two downloads for the same task.)?
Please, I need a little help here as I do not want to hard brick my phone.

NodCom said:
After reading around some, I am wondering if this is because the "modem" or "firmware" is different now from what it was before when the backups were working?
See Step 9 here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Is this my problem? Could I try it out safely by first restoring my backup and then applying one of those (Which? I am confused why there are two downloads for the same task.)?
Please, I need a little help here as I do not want to hard brick my phone.
Click to expand...
Click to collapse
Yes it's because the firmware is incompatible. You can search for the right one based on which version of CM11 you had before in your backup. Oxygen modem is compatible with 5.1.1 CM ROMs in case you want to upgrade later
http://boeffla.df-kunde.de/bacon/modems/
Sent from my A0001 using Tapatalk

Renosh said:
Yes it's because the firmware is incompatible. You can search for the right one based on which version of CM11 you had before in your backup. Oxygen modem is compatible with 5.1.1 CM ROMs in case you want to upgrade later
http://boeffla.df-kunde.de/bacon/modems/
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply!
How can I tell more precisely what version I had before? All I really know is that it was CM11 and Android 4.4.4. Do I need to be more specific in my knowledge than that?
Sorry, but what do you mean by that last part? If I flash the CM11 modem, would not that remove the Oxygen modem?

Hello again,
After doing some research I decided on the XNPH44S-modem as it seems to be the newest modem for CM11.
This did however not help, the phone still bootloops after flashing the modem. Is the modem separate from the firmware? Do I need to find a firmware as well?
Help is highly appreciated.
Edit! I solved it! With a combination of http://forum.xda-developers.com/oneplus-one/general/cm11-cm12-firmware-repository-t3019881/page2 and http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 as guidelines I made the phone boot successfully! The snag is that "fastboot flash LOGO logo.bin" failed because it "remote: partition table doesn't exist", so "half" the boot animation seems to be missing. Any fix?
I am a little confused though, after booting up I had the OTA updated suggest update XNP44HS, which is the exact same name as the modem flash I did. What gives? Is it safe to download this update?
OTAs have me slightly worried. Last time I went through all the CM11 updates and then jumped into CM12, found it not to my liking and tried to go back, which I managed to, after which I tried to update to the latest CM11 using OTA; and the first security update here gave me a hardbricked phone that time. Any suggestions or insight into this from someone with good knowledge?

NodCom said:
Hello again,
After doing some research I decided on the XNPH44S-modem as it seems to be the newest modem for CM11.
This did however not help, the phone still bootloops after flashing the modem. Is the modem separate from the firmware? Do I need to find a firmware as well?
Help is highly appreciated.
Click to expand...
Click to collapse
You'll have to test out the older modems till you find out which is the right one. Last I checked 05Q was the latest CM11. Try that one, otherwise download and test 33R, 30O etc till you find one that works. It would have been really easy if you could remember what version your backup was and make sure you're using TWRP 2.8.6.0. Download Oxygen OS modem too if you want to go back to it or use newer ROMs
Sent from my A0001 using Tapatalk

Renosh said:
You'll have to test out the older modems till you find out which is the right one. Last I checked 05Q was the latest CM11. Try that one, otherwise download and test 33R, 30O etc till you find one that works. It would have been really easy if you could remember what version your backup was and make sure you're using TWRP 2.8.6.0. Download Oxygen OS modem too if you want to go back to it or use newer ROMs
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I updated my message within a minute of you posting yours, so you might have missed the edit.
SIM and calling works with the XNP44HS modem which I flashed. Still, the OTA updater claims to have it as an awaiting update, but I am not sure if I dare downloading it or not? Also, why is that specific version of TWRP important? I can see that my current version is 2.8.5.1.