Database Users

E:Can't chown/mod/mod /system/

wasn't sure where to post this since i wasn't getting any responses in the Q&A section but i keep getting this error
E:Can't chown/mod/mod /system/
(No such file or directory)
E:Failure at line 343:
set_perm_recursive 0 0 0755 0644 SYSTEM:
Installation aborted.
is my system memory full? Is this fixable? I'm unable to flash almost any rom with the exception of cyanogen nightlies and Leofroyo Beta3. Is this because these betas and nightlies write files that aren't written by finished roms? Thanks.

Did you wipe first?

evilkorn said:
Did you wipe first?
Click to expand...
Click to collapse
Yes i did.

What recovery are you using? If you aren't using Amon_ra's try that.

I'm on Ra's. I found these threads if it helps
http://forum.xda-developers.com/showthread.php?t=530900
http://forum.xda-developers.com/showthread.php?t=527598

Anybody? Seems like maybe i partially lost root access? Would a re-root help?

Same probem here
Same problem here I have a Droid X2 with 2.3.4 and am able to root use OTA ES File and can write to /system from ES File Explorer. But when I go to upload ROM o it I get the same error. I already tried 3 different ROMs all with same perms error. What's Up?
---------- Post added at 12:34 AM ---------- Previous post was at 12:08 AM ----------
I found out my issue was that I had a backup of su using the OTA Rootkeeper. I deleted the su backup and then the ROM install worked perfect.

Accidentally Odin with I9000 Pit

I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.

kenpachi069 said:
I do the flash without further study, and I accidentally flash my samsung fascinate with I9000 Pit 512, and now I can't get back to stock verizon. Can anyone please help me?
thanks.
Click to expand...
Click to collapse
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
http://forum.xda-developers.com/showpost.php?p=8195563&postcount=43

thank you
Thank you for a quick reply. I will try and let you know..

namebrandon said:
I did something similar.. don't worry too much.. yet..
Let me find my post on this.. basically, I had to flash the US cellular kernel, then it would allow the stock fascinate kernel to take.
So flash US cellular..
then flash stock Fascinate
Here
Click to expand...
Click to collapse
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.

kenpachi069 said:
I tried, and it still doesn't work. I think the problem is not the kernel. The problem is the PIT file that I also flashed. I need to map to the right place, I can't find i500 PIT file anywhere. I hope someone can direct me. thanks.
Click to expand...
Click to collapse
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.

namebrandon said:
I've got it at home, but not here. I got it from angel (fallingup) originally. PM him.
Click to expand...
Click to collapse
If you get home can you upload it for me, please?
Thanks.

Gotta love dropbox. extract from zip.

namebrandon said:
Gotta love dropbox. extract from zip.
Click to expand...
Click to collapse
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.

kenpachi069 said:
Nice, thank you so much. Now i just have to find the right file to flash it back. Where do i get the file for pda, phone, and csc?
Sorry, I am really noob to android. Once again, thank you for all the help.
Click to expand...
Click to collapse
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
http://forum.xda-developers.com/showthread.php?t=782204

namebrandon said:
You only use PDA.. And rarely would you ever use the PIT file.
You can find the stock odin files here, in the first post.
Click to expand...
Click to collapse
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?

kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
What does..? I don't know what "it" is man.. Is that during recovery?
Regardless, if you're getting that output from the phone, we're heading in the right direction.

Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.

kenpachi069 said:
Well after I do the system restore, it just reboot and that's what it say.
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
It won't start up.
Click to expand...
Click to collapse
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.

namebrandon said:
Ok.. You need to start over.. using the files from the post I linked to..
Start Odin, and flash the /system file. You use the PDA box. You do not put anything in PIT.
Then do the same thing, but use the stock kernel file.
Then do the same thing, and use the stock recovery file.
Click to expand...
Click to collapse
There is a PIT file in that thread now. Use it if you flashed another phone's pit file.

did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please

kenpachi069 said:
Thanks,
Now it say: E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
??? any idea?
Click to expand...
Click to collapse
This means ur phones file systems those 2: stl11 is your /system/ and mmcblk0p1 is your /data/ and if it cant read it then that means you must have had voodoo 5 enabled and it converted all of ur file system to ext4
Sent from my SCH-I500 using XDA App

atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
I am stuck at this after doing one click restore odin3 for captivate on galaxy s i500.
i can get to download mode, using homemade jig.
please someone help me when i flash my phone to atleast normal mode. please
Click to expand...
Click to collapse
I have several questions...
1) Why does getting into download mode require a homemade jig?
2) What were you running before you tried to restore back to stock?
....oh what was that third one....OH YEA
3) Why on gods green earth would you use the one click restore for the captivate on the fascinate!? If you got it from here...you'll notice that in all caps in the title it says "CAPTIVATE ONLY". le sigh.
This is the thread with the files you need: http://forum.xda-developers.com/showthread.php?t=782204
I'm not sure if the one click restore also writes over your modem...but if it did you need to go into irc (irc.freenode.net #samsung-facinate) and ask someone for it.
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.

If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App

times_infinity said:
If you flashed another galaxy S's ANYTHING, you now have a brick.
Now go ahead and pat yourself on the back. You've earned it.
Also, this thread is totally in the wrong section. Just sayin'.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
False..
It's a stupid move, but far from a brick.

atinder said:
did you managed to fix that
E: can't mount /dev/block/stl11
(Invalid argument)
E: can't mount /dev/block/mmcblk0p1
(Invalid argument)
Click to expand...
Click to collapse
You need to follow this http://forum.xda-developers.com/showthread.php?t=804784
Redwing said:
I have several questions...
In addition, if you were running voodoo before doing this you'll need someone more acquainted with these sort of facepalm dilemmas. These people can also be found in irc.
Advice: Read Read Read....and don't think about or mention taking your phone in to verizon. The irc gods will smite you.
Click to expand...
Click to collapse
Completely agree.

Cache partition size

Hello to all in comunity.
Galaxy s has only 30MB of cache size. And this is bad because some apps on the market can't be installed, since market uses this cache partition for the downloads. Is there a way to increase this size or to symlink it on some bigger partition like /data or somewhere else?
Sent from my GT-I9000 using XDA App

Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.

Do you have ext4 lagfix enabled?
Sent from my GT-I9000 using XDA App

No. Do i need to enable it?
Sent from my GT-I9000 using XDA App

Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App

avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Click to expand...
Click to collapse
And what version of speedmod are you using? I'm on K12-T 500Hz....if i enable ext4 lagfix on cache, will i get the 100MB too?
And also, were you using CM7 already?
Thanks!!

I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.

avary said:
Using speedmod kernel with lagfix enabled on cache (ext4) gave me 100 MB.
Sent from my Galaxy S/CM7 using XDA App
Click to expand...
Click to collapse
I call bull****.

So there isn't a way to do it right now? I guess we need supercurio's or hardcore's help. Please people, help to contact them. Thx!!
Sent from my GT-I9000 using XDA App

I agree
snapper.fishes said:
I call bull****.
Click to expand...
Click to collapse
So do I. I tried using the latest speedmod, and no change. Think the only solution would be to have the cache size changed in the internals. Definitely out of my league; I don't want to try changing a setting and lose the use of my phone. Hopefully someone gets a fix in; battle bears is calling...

Definitely we need to move this thread to android development and see if someone there with enough skills can help us. I think it's an urgent problem. What about battle bears? And what if gameloft start to sell their games on android market now?
Sent from my GT-I9000 using XDA App

Thanks!!!!

gangpe said:
I tried to symlink the cache to a folder i created ala hardcore's suggestion (Thanks again hardcore!), but unfortunately I got the same sized partition as the original cache folder, which kinda makes sense. Hopefully Samsung or one of the guys on XDA (yeah, they'll probably get a fix out before Sammy does) will have a solution.
Click to expand...
Click to collapse
lucbl1 said:
Anybody? I heard that's a way to symlink cache anywhere else, but i can't do it, everytime i try a message saying "resource busy" or something like this appears on Terminal Emulator. I'm trying to symlink cache to /data.
Click to expand...
Click to collapse
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache

shantzu said:
How do you guys exactly try to symlink it? I guess more people could help out if they knew exactly what you are doing and what the error messages exactly say.
I'm not really interested in getting a bigger cache partition since I don't use really big apps, but this would probably be thay way I'd do it:
(you could type these command either through adb shell or directly on the device using a terminal emulator -- WARNING: these commands are not tested and may horribly break something)
Code:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
Click to expand...
Click to collapse
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!

I mentioned this issue to supercurio who is looking into it.
Sent from my GT-I9000 using XDA App

lucbl1 said:
I was just using the same code you posted. But i think that for symlinking, /system and /data must be in Ext2/3 or 4 format, am i right? I'll be testing it in the weekend!
Click to expand...
Click to collapse
well, tbqh I didn't work much with RFS, so I am not sure if it supports symlinks, I guess it can't hurt to try though...
If it doesn't work on RFS you'd have to try some ext FS (ext2, ext4, whatever you prefer).

rlorange said:
I mentioned this issue to supercurio who is looking into it.
Click to expand...
Click to collapse
So maybe supercurio can fix it. Let's hope! Any news please report here.
Sent from my GT-I9000 using XDA App

Problem fixed on last speedmod kernel!
Sent from my GT-I9000 using XDA App

can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!

romdroid. said:
can someone plz help me? i got the problem and its rly annoying..i have 2.3.3 xxjvo with cf_root how do i fix this ****?!
Click to expand...
Click to collapse
If rou are rooted just folow this commands in terminal...
su
mkdir /sdcard/tempcache
mount -o bind /sdcard/tempcache /cache
This is temporary, after reboot cache will return normal and you can delete tempcache in sdcard...
Cheers

[q] status 7 : Rom won't flash

I'm trying to port a 4.3 rom from Galaxy S3 to Nexus 4, but when I finally try to flash the rom I'm given the error Status 7 (symlink):
symlink: some symlinks failed
E:Error in /data/media/0/port.zip
(Status 7)
Instalation aborted.
I took the error log from CWM and here is what is said:
minzip: Process function elected to fail (in inflate)
minzip: Error extracting "/system/lib/libSpenSkia.so"
failed to mkdir /system/etc/firmware/wcd9310: No space left on device
symlink: failed to symlink /system/etc/firmware/wcd9310 to /data/misc/audio/mbhc.bin : making parents failed
symlink: failed to symlink /system/etc/firmware/wcd9310 to /data/misc/audio/mbhc.bin : No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
E:Error in data/media/0/port.zip (that's my rom's name)
(Status 7)
Instalation aborted
I:using /data/media for /sdcard/0/clockworkmod/ .recovery_version
What should I do?

Are you using the latest CWM? You could also try TWRP to flash the rom.

I've heard twrp doesnt work with custom roms
Sent from my Nexus 4 using XDA Premium 4 mobile app

Xintorrim said:
I've heard twrp doesnt work with custom roms
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All I have used on my N4 is TWRP and I've had no problems so far. I have tried Slim, Experience, Asylum, etc.

I've tried twrp but still no success. It must be a problem inside the rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

As a test, try TWRP with another 4.4 custom rom.

My custom ROM won't flash with CWM nor with TWRP. Tried to flash it using another custom ROM and it didn't work too. I really believe there's something wrong with my custom ROM or with the device itself. In another thread a user told me that "Like the error said. NO SPACE LEFT. So, increase the system Partition or delete some APK in the rom". I guess I can't delete any apk's and I don't know how to increase system Partition. Moreover, I don't know if that would even work. I'd like someone to help me with a solution based on the error log I posted before.

Flash first CyanogenMOD, then flash any other ROM and use TWRP for it!

Would it really make any difference?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Xintorrim said:
I'm trying to port a 4.3 rom from Galaxy S3 to Nexus 4, but when I finally try to flash the rom I'm given the error Status 7 (symlink):
symlink: some symlinks failed
E:Error in /data/media/0/port.zip
(Status 7)
Instalation aborted.
I took the error log from CWM and here is what is said:
minzip: Process function elected to fail (in inflate)
minzip: Error extracting "/system/lib/libSpenSkia.so"
failed to mkdir /system/etc/firmware/wcd9310: No space left on device
symlink: failed to symlink /system/etc/firmware/wcd9310 to /data/misc/audio/mbhc.bin : making parents failed
symlink: failed to symlink /system/etc/firmware/wcd9310 to /data/misc/audio/mbhc.bin : No such file or directory
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
E:Error in data/media/0/port.zip (that's my rom's name)
(Status 7)
Instalation aborted
I:using /data/media for /sdcard/0/clockworkmod/ .recovery_version
What should I do?
Click to expand...
Click to collapse
Had this problem with my old xperia mini and this was the solution : (not sure it'll work, but give it a shot if you want to take the risk)
Download notepad ++
Open up the updater script and delete the first two lines I think.
I'm not a 100% sure this was all so best,
SEARCH FOR STATUS 7 ERROR IN THE XPERIA MINI FORUMS. YOU'LL GET YOUR ANSWER THERE.
Sent from my Nexus 4

Tried to do what you guys said but still no results. Here are logcat and the recovery.log
http://d-h.st/o7w recovery
http://d-h.st/AgE logcat
Sent from my Nexus 4 using XDA Premium 4 mobile app

updater-script mounting issue

Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated

XxZombiePikachu said:
Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated
Click to expand...
Click to collapse
I'v got the same problem i tried to copy other roms updater scrips put it does not work too

XxZombiePikachu said:
Okay so I am working on a custom rom and my first few attempts didn't copy anything into the /system so I decided to add the mount system into my updater-script-
I added the mount to system:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
but after flashing and grabbing a copy of the recovery.log I get the following error:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
so I am wondering if something is wrong with the mount command or if something else could be wrong?
Any assistance will be appreciated
Click to expand...
Click to collapse
These commands are correct actually... But are you following them with:
delete_recursive("/system");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
If you use the updater-script from my stock ATT rom as an example it should boot for you...
Also you need to make sure you have Loki in the script and rom itself...

VECTUS said:
These commands are correct actually... But are you following them with:
delete_recursive("/system");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
If you use the updater-script from my stock ATT rom as an example it should boot for you...
Also you need to make sure you have Loki in the script and rom itself...
Click to expand...
Click to collapse
I definitely have the delete recursive system followed by the extract system/data but I don't have the loki folder/commands for updater-script mainly because I don't know where to get them from/what is the command to run, when I get home I'll take a look at your updater-script and do what needs to be done(I don't want to be using other peoples scripts or files because I know some can get rather overprotective, so far I've been getting help from xdabbeb/bigfau but I don't want to have to ask for every little detail) thanks for the tip I'll update if anything good or bad happens
Sent from my potato d800

XxZombiePikachu said:
I definitely have the delete recursive system followed by the extract system/data but I don't have the loki folder/commands for updater-script mainly because I don't know where to get them from/what is the command to run, when I get home I'll take a look at your updater-script and do what needs to be done(I don't want to be using other peoples scripts or files because I know some can get rather overprotective, so far I've been getting help from xdabbeb/bigfau but I don't want to have to ask for every little detail) thanks for the tip I'll update if anything good or bad happens
Sent from my potato d800
Click to expand...
Click to collapse
Anything you want to use in that stock ROM is free to use. That's why I made it. The ROM includes loki with correct file structure. Loki install commands are at the end of the udater script in the ROM...
Edit. Lol I just remembered I threw in the data folder in the stock ROM as a place holder for apps etc. If you use the data command I'm your updater script you will need a data folder in the ROM but the data folder is not a must have for your ROM because it will be created anyway... The data folder is an old trick to load updated apks or system app Apks can be moved there to create more space for system/apps...

VECTUS said:
Anything you want to use in that stock ROM is free to use. That's why I made it. The ROM includes loki with correct file structure. Loki install commands are at the end of the udater script in the ROM...
Edit. Lol I just remembered I threw in the data folder in the stock ROM as a place holder for apps etc. If you use the data command I'm your updater script you will need a data folder in the ROM but the data folder is not a must have for your ROM because it will be created anyway... The data folder is an old trick to load updated apks or system app Apks can be moved there to create more space for system/apps...
Click to expand...
Click to collapse
The boot.img in your Rom is the 10d boot?
Yea I know about the data folder and I have it in to include some apps/others stuff and remove some of the system apps and use them as normal apps for greenify
Sent from my potato d800

hey @VECTUS after getting loki working(tested with some test splitwindow stuff I'm working on and in case you are wondering one of them force closes and renders the phone unusable while the other works but no apps show up so work in progress), I rebuilt my custom rom with new stuff(loki/kernel) and still get the mount failed in recovery, everything after the mount fails does it stuff extracting data/system, symlink and loki/boot flash(I don't see the recursive system delete in recovery.log), if you would like to take a look at the script/log let me know and i'll share a link for now I am taking a break because everything else I have made works(custom bootanimation/mods/etc) but the rom is a no go, in the last 2 days I've flashed like 15 different test and nothing if you have any insight please let me know
p.s. in your updater script you use the set_metadata/set_metadata_recursive, when I tried it I got a syntax error and changing it to set_perm/set_perm_recursive eliminates the error but then I get the /system is not a valid uid bla, bla, bla any thoughts on this?

XxZombiePikachu said:
hey @VECTUS after getting loki working(tested with some test splitwindow stuff I'm working on and in case you are wondering one of them force closes and renders the phone unusable while the other works but no apps show up so work in progress), I rebuilt my custom rom with new stuff(loki/kernel) and still get the mount failed in recovery, everything after the mount fails does it stuff extracting data/system, symlink and loki/boot flash(I don't see the recursive system delete in recovery.log), if you would like to take a look at the script/log let me know and i'll share a link for now I am taking a break because everything else I have made works(custom bootanimation/mods/etc) but the rom is a no go, in the last 2 days I've flashed like 15 different test and nothing if you have any insight please let me know
p.s. in your updater script you use the set_metadata/set_metadata_recursive, when I tried it I got a syntax error and changing it to set_perm/set_perm_recursive eliminates the error but then I get the /system is not a valid uid bla, bla, bla any thoughts on this?
Click to expand...
Click to collapse
Hey can you send me a link to your ROM? I have tomorrow to look at it... Just pm me...

I'm getting this exact same error with my SafeStrapped, GPE re-ROM'ed AT&T S4 (the one that Asurion had the nerve to replace a shattered first-gen Moto X of mine with) when attempting to take the Lollipop OTA from Joe-Tech's ROM... but then again, that's what you'd expect from a bootloader/recovery-locked device. Even so, it actually passes the verification stage... which is remarkable.