Possible bootloader unlock method!
- Thread starter Dankchild
- Start date
- Status
*facepalm* ........
Sent from my SM-N900A using XDA Premium 4 mobile app
Sent from my SM-N900A using XDA Premium 4 mobile app
I'm so ready for some custom Kernels and some ASOP goodies (Mostly PAC)
I just want custom kernels for speed and battery. I prefer TW on the Note 3.
Sent from my SM-N900A using XDA Premium 4 mobile app
Sent from my SM-N900A using XDA Premium 4 mobile app
An actual recovery like twrp would be nice too! But a custom kernel that can match the battery life of the t mobile variant would just be awesome
Sent from my SM-N900A using XDA Premium 4 mobile app
That is what we would need to flash custom kernels.
Sent from my SM-N900A using XDA Premium 4 mobile app
I'm not greedy. Plain old root would be nice
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I know. Just stating that having an actual recovery and not ss would be the biggest thing for me
Sent from my SM-N900A using XDA Premium 4 mobile app
If we potentially are able to unlock the bootloader, would it be possible to go back to stock after doing so? Would it just be as simple as flashing back the stock bootloader? Sorry, just don't really know much about it.
You can flash kernel without twrp. Simply need unlocked bl. But yeah recovery would be nice. Personally I'm looking forward to Temasek's N3 kernel. Battery life on that one is just ridiculous.
Either way... This is a huge step for all locked bootloader Qualcomm Samsung phones.
Sent from my SM-N900A using XDA Premium 4 mobile app
Sent from my SM-N900A using XDA Premium 4 mobile app
Wonder how long till any things known...
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I want full recovery kernels and aosp/cm11 so tired of touch wiz!!
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Sent from my SAMSUNG-SM-N900A using xda app-developers app
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8
Yeah, that was his response when I asked about the keys. They've got it. Don't believe the nay-sayers just yet. :good::fingers-crossed:7I saw this and nearly jumped out of my seat! Not sure if its legit or if/how it works. Does this look good for us?
http://xdaforums.com/showthread.php?p=51983540
EDIT:
ALL HANDS ON DECK! Skilled developers please look at these files/this utility! It seems to have been deemed worthy of a twiceover by designgears!
*Mirror removed due to copyright claims*44
Whoa, I never lied to anyone regarding the source. In fact only 1 person asked about the source (not including the nice dmca notice), and I told them.
The info posted publicly was a legit qualcomm tool, it is used across vendors.
I'm very sorry to get hopes up, but calling me a liar is unnecessary. I've helped countless people with my restore method and defaming me isn't appreciated and only scares futures users into using unproven, possibly more dangerous, methods.
Moving forward, I'll refrain from hysteria releases. I won't ask for help from developers, I'll just work on my own when I have time like I've done in the past. It may not be "as juicy" as your preferred security bulletin leaks, but my contribution will help someone. Hell, it may even contribute to some of your future efforts, and that was the whole point.
Edit-
To the whole stepping over the line on sharing this info - the information contained in the qpsa tool isn't new information. We all know how to sign images. Releasing that info would not affect QCom's bottom line. It does not make them money, therefore I felt okay with posting it. The real issue was the certificates posted. I understand QCom's issue with those being shared (they'll just update remotely to recover from the loss). It just gave us a bit of a head start.
Note - Trade secrets are only trade secrets if a reasonable attempt at security is performed. I found all the files through a friggin Google search.
If anything I feel that the ethical issues surrounding this conversation is the real concern. I'm the one who that will ultimately have to deal with it though. I promise you'll sleep soundly after all is said and done. I promise that I'll continue to use the limited resources I have to force my equipment do the things I want it to. If I have to use proprietary code to get it to that state I'll still do it - my device is mine, doesn't that make it an IP?
Tell me you wouldn't unlock your Note 3 even if you understood that the method utilized close sourced code.
