[General Topics] BfunnY6t9:
Hello I'm sending this post now because I'm going to need somebody's assistance. A quick story I have been doing this for about 3 months as far as my first root to a flashaholic. I have successfully got around my bootloader. The problem is I'm not 100% sure how. I have a good idea of what I did but I don't know exactly as I am NOT a dev and I am new to this. I catch on rather quickly though and have found a passion for modifying my android and this site has been my number one contributor. My goal is to give back and help others out as well. I started off by editing permissions in my system file along with floating feature, csc, features and the customer XML. It was somewhere right in one of those files that I did this.. I simply changed the permission or function and immediately when I did I was prompted by super user to let boot animations by JRummy apps creator of the toolbox to allow permission which I did. The problem is as I didn't realize what I did at the time until I reset it as I changed about 10 different things. About a week prior I tried installing the boot animation into different file folders which was the two options that they suggest. Nothing happened of course my bootloader is locked and i wasn't surprised. Well I changed the permissions that shouldn't have in the calling feature section and I got stuck with force close force close so I hard reset into the factory recovery and trief to clear the cache partition which was unsuccessful. I then decided to install philz custom recovery so I could do a good clean out because obviously the factory recovery is garbage but every time I tried to change it it would stick me in a boot loop after being successfully flashed and in use for at least 24 hours. After I wiped the dalvik cache and the cache partition with Phils I then decided to try one last flash with a custom ROM and everything flashed fine. But once it rebooted I noticed a completely different boot animation and to my amazement it ended up booting and upgrading all my apps it started up normal. The rom I installed was real rwilco's mostly stock version 1.2 G900PVPU3BOG1. After that I decided I was going to take another chance and flash a few modification files. Once again succesfull. This morning I decided I was going to try to do a backup and restore. I backed it up with Phil's recovery and then I restored it. Restoring gave me a bit of a problem as I had to delete the cache and the dalvik cache. I then restarted the system the first time it didn't work or I didn't wait long enough I'm not sure. The second time I hard reset it introduced a normal boot and it started back up and was upgrading all 590 something after they have. Before I did any of this I was working away at a stock rom that I managed to modify a file in. This would be the aboot.mdn i believe. I was able to open it up into a notepad and replace it with the older version in the text part only so the file name itself stayed the same. I don't know if that played a major part to it or not. But I have sense flash recovery and files without getting stuck into a bootloop and with this new firmware almost every time I turned it off and on it would put me in a boot loop just because I was rooted. I attempted to simply change a new battery that I ordered powered off replace battery powered back on and was stuck in a boot loop. I have been making it my goal to somehow crack this thing. This is where I need help because I am still a noob I always just happened to poke in the right places I could care less about reaching 10 posts so I can post links if you like after I upload my information you can go ahead and reset that. I am here because I can seriously help and this website has been a major contributor to me becoming a flashaholic. I am at work right now and have already attempted but I'll go down to a 3G signal if that. I have absolutely no reliable internet here but within 5 hours I will be home uploading to my Google Drive a copy of my manifest and CSC, permissions, and features files. I have also created a clockwork recovery which I am going to upload as well I need somebody to help me go through these and pinpoint exactly what I did so we can get a legit thread with the fix. I somehow basically flashed a new boot animation which i think is blocking my other boot. I have confirm this working I have 2 screenshots I'm going to upload. Anybody with real experience and actually knows what they're doing I would appreciate your help in this matter.. And actually knows what they're doing I would appreciate your help in this matter. I just need to get home to my laptop to upload. Thanks xda you guys are awesome and I hope this is finally my opportunity to contribute and give back.

i ran out of time and couldnt proofread. sorry about that lol'

in my drive account i have a 1) factory rom that i modded aboot.mbn. 2) The backup "philz" cwm recovery. its my full backup apps and all down to the boot image that replaced the sprint yellow screen and the samgsung boot logo. 3) The system files that i have modified.. csc, features, floating feature, customer xml... 3) screenshots of rom info and adding others of some of the mods as we speak. still need 15 mins to finish uploading the sys files

if someone can figure out exactly what i did we have a fix. i have since flashed 30+ mods with no bootloop. email is bfunny6t9@gmail.com just incase for contact purposes

h t t p s: // drive. google. com / drive / folders / 0B5AfudcH1XDQMVFZdFhVTFdYQ0U---has many spaces only way to fit link

the system files have been diificult to et into my drive. most did not want to copy and the size themself. the full custom restore is in my drive already along with some screens. i have also set my boot animations to random and have about 20 or so cycling. also after restore make sure to wipe dalvick cache and cache. also some of the apps might fc i didnt have them fully restored when i created backup. i added a backup file in drive that has full copy.