I've read hopsin's entire recovery thread. I just got my Mega a couple of days ago and rooted it today. I'm really excited about getting a custom recovery. I want to extend my support and say that I'm available to help test if you need anymore help. I have a Galaxy S5 as my "main" phone. I hope your back is healing up good. Good luck and thanks for all the work you've put into this project so far.
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
Its nice to know more people have the i527. As far as recovery goes im in the midst of tearing apart the boot structure of this bad boy could take a day or a week or a year but who knows. I do know this Hopsin fella wont be coming out with zilch, because doing this a lone is not realistic.
I been told him id test out whatever he has but as always, shady responses and dodgy behavior. Aside from that...
There simply is no way around this bootloader and for the 100th time its not knox. Tripping the knox counter will void your warranty? Yes but to trip knox you would have first break the security which voids your warranty!!!!!!!!!!!!
Dont take my word for it..
Ask Adam Outler or djrbliss or halekdev. Without a serious collaborative effort theres no recovery coming
I need someone thats hardware friendly, preferably knowlege of uart, and physical memory and proccessor knowledge.
I have the right people but they dont have the device, so even tho theyve worked on this board before, a lot of the exploitation is going to be device specific, which means that someone here needs to learn that a collective effort is the only thing thats going to win the race. This is for everyone!! Nobodys tryna steal nobodys credit, theres no bounty and even if there was I dont want anyones money lol if hopsin pm'd me right now and say we figured it out, he could have all the credit and donations because I dont have a donate badge in my profile, I do this for the sake of developing.
---------- Post added at 05:50 AM ---------- Previous post was at 05:19 AM ----------
Oh for the critics that say I have no screen shot either, even tho I didnt make a promise to have a working recovery by end of last month!!!!!
I've disassembled my aboot and found the check sigs and the boot_linux_from_mmc was not present or im just looking for it in the wrong place either way, I chatted with djrbliss (one of the best developers here!)( No longer here!!!!!!! )He recognized vulnerabilities in the galaxy s4 bootloader and various other comparable phones including lg so he wrote a little tool called loki_tool (im not writing a detailed report about it go to the loki tool page if youre curious) either way he was patient with me and walked me through the aboot but hes intensively busy! And once again he doesnt have the device but he was nice enough to run the tool against my original aboot but lo' and behold the boot_linux_from_mmc was either patched or is in a different place.
Aside from that I have access to an unsecure aboot but the partitions are not for out device, I swear we need someone who understands kexec, zrom, pbl, sbl1, sbl2, sbl3 because that would be the first steps to having a slightly unsecure or fully unsecure bootloader. If you dont understand anything just ask... ...not me, but a ARM reverse engineering book. Jk but seriously great people already did 70% of the work for us, so its gonna take real effort to close this gap.
