Flashed the latest RUU from HERE, and it boots into the OS perfectly.
Then, flashed Stock GPE from HERE and also tried LolliGPE from HERE. Both will not get past the boot screen, after waiting over 30min's.
In attempts to fix, the latest full firmware, TWRP, full wipe/dirty wipe, and DH's 5.1 firmware have been flashed, then the custom ROM's flashed again followed. Same issue is persists. Each time, trying to flash the RUU back, boots without issue.
Prior to flashing the latest RUU (hboot method, 0P6BIMG.zip), I have ran all the ROM's mentioned and others without issue.
I'm at a loss of what to try next, or why it's hanging. Right now, i'm leaving it for hours at the boot screen, but I doubt this is going to cure anything and only provide a hot phone during the whole time.
The phone is unlocked, S-OFF, and SuperCID.
Any suggestions i'm willing to try.
Update:
Woke up 6+ hours later, and it was still stuck on the boot screen.
Flashed the latest Fluent ROM found HERE, and it boots fine. Then did a full wipe (Cache, Dalvik Cache, Data, System), then the standalone data wipe, and factory reset. Installed GPE from HERE, and it stuck on the boot screen again after waiting 20min's...
Next step i'm going to try is 4.4.4 RUU, then full latest OEM firmware. If GPE doesn't boot still, i'll try DH's 5.1 firmware.
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
kcasner said:
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
Click to expand...
Click to collapse
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
santod040 said:
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That was exactly it, what a relief. Thank you!
kcasner said:
That was exactly it, what a relief. Thank you!
Click to expand...
Click to collapse
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
kcasner said:
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
Click to expand...
Click to collapse
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
dottat said:
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Honestly can't recall. I follow; we're on the same page, different lingo.
kcasner said:
Honestly can't recall. I follow; we're on the same page, different lingo.
Click to expand...
Click to collapse
kcasner, I had exactly same issue as you. Could you explain a bit detail on how you get it fixed?
I want to flash DH5.1. Are these correct steps I should following:
1) open DH5.1 zip file, find the boot.img (I found there're two boot.img, stock/boot.img and elite/boot.img, I guess I should use later one)
2) fastboot flash the boot.img
3) boot into recovery to flash DH5.1
4) reboot
Thanks for help!
Related
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
viprk24 said:
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
Click to expand...
Click to collapse
why don't you start by reading this http://forum.xda-developers.com/showthread.php?t=1957193
If you have ruu'ed you have to root again and unlock your bootloader again.
What recovery did you install ?
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
Crappyvate said:
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Click to expand...
Click to collapse
apparently he did and some did not read the information
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
CheesyNutz said:
apparently he did and some did not read the information
Click to expand...
Click to collapse
surprise...that would be a first
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
subarudroid said:
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
Click to expand...
Click to collapse
don't think so since apparently he still gets the htc splash screen but need more info.
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
what exactly is it doing im not understanding is it freezing ? just not installing what error code is it giving
Are you flashing the boot image for your ROM in adb?
Sent from my One X using xda premium
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Crappyvate said:
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Click to expand...
Click to collapse
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
CheesyNutz said:
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
Click to expand...
Click to collapse
not sure the boot.img was flashed the right way...or in the right place
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
Its not a good idea to ask for help and then flame. Honestly what was hard about posting this the first time? I thought maybe English wasn't your language or something. How could you flash a recovery before unlocking???
If you wiped everything, you should reflash bootimage in adb. Then flash your ROM. Please be nice.
Sent from my One X using xda premium
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
CheesyNutz said:
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
Click to expand...
Click to collapse
likewise. Over and out.
Hello my friends!!
I really need you help, I have some kind of soft brick. After I try to update my new htc one xl (asia version), now I'm stuck in a boot loop. Here's my info:
my CID=11111111.
I can get to bootloader & fastboot. My phone is stuck on the htc logo "htc quietly brillant". I think tha I screw up the OS.
Any ideas??
Best regards,
Happened to me, too. What worked for me was getting into fastboot and doing:
Code:
fastboot erase cache
in the windows command prompt. After that get the ROM you most recently installed and extract the "boot.img" and put it in the same directory as fastboot.exe and then flash that boot image with:
Code:
fastboot flash boot boot.img
Once that is done, do this again:
Code:
fastboot erase cache
and it should boot normally.
Let us know if that is not the case.
You should only need to use fastboot erase cache once. Doing it a second time is pointless. Also, your problem is extremely well documented on this site by the hundreds before you who have posted this exact same issue.
Not to mention, if you can't figure this out, you never should have rooted in the first place. This is why I ignored this post.
Search and read and you'll easily fix your phone.
Egoista's solution assumes you have a 1.14 hboot and hadn't flashed the boot.img
Sent from my One X using xda app-developers app
Thanks a lot for both replies!!
Finally I use RUU tool and everything was great. Now I have my phone updated to Jelly Bean
Regards!
exad said:
You should only need to use fastboot erase cache once. Doing it a second time is pointless. Also, your problem is extremely well documented on this site by the hundreds before you who have posted this exact same issue.
Not to mention, if you can't figure this out, you never should have rooted in the first place. This is why I ignored this post.
Search and read and you'll easily fix your phone.
Egoista's solution assumes you have a 1.14 hboot and hadn't flashed the boot.img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Tatirulo said:
I really need you help, I have some kind of soft brick. After I try to update my new htc one xl (asia version), now I'm stuck in a boot loop.
Click to expand...
Click to collapse
The reason for this is quite simple, and should have been obvious. OTA needs stock recovery in order to install. When it can't find stock recovery, the install gets stuck.
RUU worked because RUU also overwrites recovery with the stock one.
In any case, you should never ever install an OTA on a rooted device without first researching what will happen, at a minimum. It usually won't work, and will often bootloop the device.
redpoint73 said:
The reason for this is quite simple, and should have been obvious. OTA needs stock recovery in order to install. When it can't find stock recovery, the install gets stuck.
RUU worked because RUU also overwrites recovery with the stock one.
In any case, you should never ever install an OTA on a rooted device without first researching what will happen, at a minimum. It usually won't work, and will often bootloop the device.
Click to expand...
Click to collapse
I suggest not updating at all without reading. Even custom ROMs.
Sent from my Carbon-ize Evita using xda-developers app
So here's the story. I installed a new screen on my Nexus. After putting the phone back together, it got stuck on the boot logo.
Tried restoring a backup and flashing a different rom, but both things gave me a /data error in recovery. I used adb to flash a 4.4.2 factory image but that was stuck on bootscreen too.
I flashed a 4.2.2 factory image and that works absolutely fine. But when I try to update it to 4.3, or flash a custom 4.4.2 rom, it gets stuck on the boot logo.
Everytime I flash I am fully wiping my phone.
How can I fix this and update my phone?
Before all of this happened I was running a cyanogenmod build absolutely fine without any problems.
Thanks!
harro3 said:
So here's the story. I installed a new screen on my Nexus. After putting the phone back together, it got stuck on the boot logo.
Tried restoring a backup and flashing a different rom, but both things gave me a /data error in recovery. I used adb to flash a 4.4.2 factory image but that was stuck on bootscreen too.
I flashed a 4.2.2 factory image and that works absolutely fine. But when I try to update it to 4.3, or flash a custom 4.4.2 rom, it gets stuck on the boot logo.
Everytime I flash I am fully wiping my phone.
How can I fix this and update my phone?
Thanks!
Click to expand...
Click to collapse
You will need to flash a full firmware. Files and instructions are found here --> LINK
LS.xD said:
You will need to flash a full firmware. Files and instructions are found here --> LINK
Click to expand...
Click to collapse
Hi there.
I have already tried this. I tried to flash the 4.4.2 factory image, but the phone is still stuck on the boot logo.
Is your bootloader unlocked?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Is your bootloader unlocked?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes, bootloader is unlocked. I have tried locking and unlocking it but this doesn't work.
harro3 said:
Yes, bootloader is unlocked. I have tried locking and unlocking it but this doesn't work.
Click to expand...
Click to collapse
You performed as followed? :
"You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system"
LS.xD said:
You performed as followed? :
"You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system"
Click to expand...
Click to collapse
Yes, I did exactly the same for the 4.4.2 image that I did for 4.2.2.
For some reason the 4.2.2 works fine but the 4.4.2 doesn't.
Then I must be sorry for having really no clue how to solve your issue
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Then I must be sorry for having really no clue how to solve your issue
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Thank you for your help though!
I hope I can fix it
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?
kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
So while sideloading it should I unroot as well?
jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app
pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app
No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...
If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.
I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.
jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?
I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me
pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?
I'm not sure what exactly caused it but about a week ago I lost cell service on my xt1032. When I dial *#*#4636#*#* it says the radio is off and the turn radio on button doesn't do anything. Wifi and GPS are working fine. Around that time I had updated the bootloader to 41.18 so that I could flash cm12.1 nightlies, erased modemst1 and modemst2 in fastboot, and flashed cm12.1. I had com.android.phone crashes like a few others did which they resolved by flashing backups.
I have tried to fix it by clean flashing cm12.1, flashing the latest XT1032_GPE_3112.97.00R radio, and clean flashing an old cm12 nightly but the radio remains off.
Any ideas?
I'm having the same issue. Dit you find a solution?
Have either of you tried flashing stock firmware?
Sent from my XT1031
ATTACK said:
Have either of you tried flashing stock firmware?
Sent from my XT1031
Click to expand...
Click to collapse
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
BiggyB99 said:
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
Click to expand...
Click to collapse
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
ATTACK said:
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
Click to expand...
Click to collapse
Thank you for your reply's. I'm now flashing stock rom from here (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510). Let you know in a sec
edit: still nothing Flashed the stock rom, wiped dalvik cache after. Rebooted a couple of times, but nothing seems to work.
Any other ideas?
edit2: Tried the optimized 'stock' rom, no success either. Also, I ruled out a SIM failure before, just did it agian because this is making me crazy!
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
ATTACK said:
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
Click to expand...
Click to collapse
Searching for the smiley that hits a hammer into his head. Sorry for my noobness! Flashing the firmware now.
edit: hanging on (bootloader) Preflash validation failed . Search xda learns me that that means the bootloader is locked, but the message says it is unlocked. I'll just go ahead and search some more
edit2: trying the bootloader unlocking procedure learns me that the bootloader is already unlocked: (bootloader) Device already unlocked!
What can I do next. (btw, the error comes on step 2 of the guide, where I put in: mfastboot flash motoboot motoboot.img. Everything else comes woth an OKAY. (http://forum.xda-developers.com/showthread.php?t=2542219)
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
ATTACK said:
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
Click to expand...
Click to collapse
I do not have a flash-all.bat (or something in that way) in my folder. Downloaded the firmware from the site you gave, the mfastboot from the Guide (http://forum.xda-developers.com/showthread.php?t=2542219) and I runned the commando's named there (for a xml.zip file).
edit: could it be that my bootloader is newer than the stock firmware is expecting? Running 41.18 now...
edit2: WORKED! I just kept trying to flash the stock firmware, error kept the same. Tried another recovery, did the flashing again but skipped the recovery step (error with bootloader still came up). After that I booted, and it worked! Sticking with stock 4.4.4 for now
Thanks for the help!
edit3: Working on 5.0.1 (stock) Did the OTA, failed because of my custom recovery. Flashed stock recovery, did OTA again --> works like a charm
Awesome!
Sent from my XT1031