[Q] Stock ringtones replaced despite deleting contents of OEM partition topic

Hi,

So I recently got my AT&T Nexus 6 and was eager to rid it of its molestations. I followed the guide on this thread:

http://forum.xda-developers.com/nexu...hread-t2947581

I got to the portion where you delete or rename the OEM partition and use the terminal command to just wipe the whole partition. That's when I got this error:

Code:

---

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase oem
erasing 'oem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.004s

---

Luckily, another user here had the same problem, and a user named Bodosom had a solution:

Quote:

Originally Posted by bodosom (Post 57556270) Start a shell in the root directory. The two commands below won't quite look as shown because the TWRP terminal emulator is idiosyncratic. Naturally you don't type the / # . / # mkdir oem / # mount /dev/block/mmcblk0p39 oem exit the shell and /oem will be visible in the file browser or just make the changes in the terminal. Renaming media is sufficient. You can ls /oem after the mount to verify you got the right partition. These two commands undo the above. They may not be needed. / # umount /oem / # rmdir /oem Reboot.

I followed this method to delete the contents of the partition. I didn't bother unmounting the partition. I restarted my device and it worked! The AT&T splash screen was gone and I was happy. That is, until I went to change my ringtones.

I discovered that the alarm and ringtone folder both contained the correct file names for the files, i.e. Titania, etc., but when you played any of the files you got AT&T tones instead. I compared these with my Nexus 5 to make sure I wasn't just crazy. I checked the OEM partition again and it was definitely empty. Somehow, the AT&T files had replaced the AOSP files except for in name. I re-flashed stock android 5.0.1 and the problem persists. To make matters worse, when I try to select a custom ringtone, the filetype is not supported (both .wav and .mp3).

Any idea what's happening here? Is it something with the SIM card? Are AT&T's machinations more cunning than they were at first? Help would be appreciated.

Very Frustrated(not getting past bootanimation despite every try topic

I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation

rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files