yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Jaocagomez:
My heart says yes

my head says no

just post the code, someone clever enough will figure it out what to do with it, OR DONT RELEASE IT AND MOTOROLA WOULDNT KNOW HOW TO FIX IT AND IT WILL STILL BE POSSIBLE TO ROOT ANDROID 5.1 WITH THE SAME METHOD

your call
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] dmbtech:
Too late, I believe motorola is all ready aware of this exploit and how it works, and will have it fixed by next software update.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
[MENTION=2376614]jcase[/MENTION] already stated they know about it. Release the exploit and start a dev thread about it.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Diego1751:
Motorola already knows about it
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
nothing to release, authors notified qualcomm/motorola, the details are in the commit history in CAF. Its not secret, no point exists to overly vague forum posts about it.

SaschaElble is mistaken, mfastboot isnt tricked into flashing anything.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
If its no secret then it should be disclosed in XDA so a free version can be made. And if mfastboot isn't tricked then "how" is it done? Link to this commit you speak of?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Skrilax_CZ:
To feed my own curiosity, which git on CAF is that (thought it's lk, but doesn't look like so)? :)

(yes I'm lazy)

EDIT: NVM, it's splattered on the 8084 branch throughout more commits.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] dmbtech:
https://www.codeaurora.org/projects...unds-checking-when-flashing-sparse-images-cve
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
Why do you need a link, you already know what it is based on your op.

mfastboot is just a dumb client.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
This is how moforoot flashes over the system partition:

https://www.codeaurora.org/projects...n and Roms since. We need more people rooted.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
I feel like there is a bigger divide between people with the real skills like [MENTION=2376614]jcase[/MENTION], hash, and dhacker and everyone else that claims to be a dev than there used to be. I guess that is a function of how complex and secure android has become. Pretty soon only nexus phones will have any possible development.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] manofwind:
I don't know why there are so many people wish the author to publish the root method freely. Would you please pay some respect to the author's diligent working? If the rooting of Turbo is easy, why don't you exploit the rooting method by yourself? If you dont't care the root, then why there so many people querying the possibility of rooting again and again?

Still I have my own wish, that the mofo tools can be used outside US.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
You don't understand the discussion. The exploit has already been published freely. No one is talking about making a new free tool based upon it. I and many others paid for mofo and love it. What we do want is new discussion on permaroot.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Since it is public knowledge already, I will attempt to release my own tool. One without restriction or cost. This is a hobby, not a damn job. Don't destroy the core value that started open source. We wouldn't even be discussing this if it wasn't for everyone who has contributed to Linux / android. One trick to fastboot doesn't make your own code.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
That's an easy statement to make when you are not the one who found the exploit. The only people that have trouble paying are those who do not comprehend the amount of work involved with this.

Not only is your stance inappropriate, but open source has nothing to do with this. This is about exploiting a bug that Motorola did not open source, so lets leave open source out of this.

To be honest, the idea of paying for stuff like this probably would have never been started if bounties were honored. Blame the lying scumbags who don't pay. They created this brave, new world and you are attempting to reward their behavior.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
He released his "work" publicly by publicly disclosing the vulnerability. Now you want to say that I cannot freely use that information and release my own tool for free? I've compiled and debugged ****, I've created programs that I worked on for years. You don't see me crying. I respect the time he spent, but not the method he wishes to gain from it. And you must not understand open source. It removes every form of oppression be it the separation of classes of wealth, power, control, or the color of your skin. And don't joke about how one has nothing to do with the other. Its the core of it. OPEN SOURCE.

I grew up in this brave new world. I'll do what I think best. And sorry, but fastboot code is public open source knowledge. For all you know, his ONLY knowledge was on the fastboot side. Well... Hmm... Probably was huh. Seems like someone took a gander and wondered, is this variable protected? Let's see.

Because otherwise you'd be implying he reverse engineered private protected boot code, off of which he turned around and SOLD. You CANT call me out while NOT calling him out.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
Don't create a strawman. I didn't say you couldn't do anything. I am simply replying to your self-entitled comments. Fastboot and mfastboot are not the same thing, FYI.

You are trying to be some self proclaimed savior of the android world by releasing work you would have never been able to release if someone else didn't do the work for you. Don't expect everyone to pat you on the back when your stance is an easy one because someone else did the work for you. All the meanwhile, you trash talk them for charging.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
This is exactly what happened in the g3 world. One team released a paid version of an exploit and then someone came around a few months later with a free version. The paid version died in favor of the free version soon after. There was a lot of words exchanged afterwards, but ultimately the free version stuck around and everyone in g3 and g2 land used it.

mofo has probably monetized about 90-95% of what it could possibly get from the turbo market, so a new free tool wouldn't break the back of the dev. I know it's not a real argument, but there it is.

Honestly I just want permaroot with wp off.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
I'm not arguing against the guy releasing it. I'm just utterly ticked off that he has the gall to say this:

It ticks me off because someone did make it their job, worked hard, and discovered it. He did not and the entitlement he feels is ludicrous.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
So your saying I put little or no work into reverse engineering his exploit? Or just not "as much" as he may have? So, he reverse engineered motos boot loader, charges 20$, I reverse his exploit, and charge 0$. And somehow.. I'm the bad guy?

And if you ACTUALLY looked at mofo's code, 99% of it is not his code. He modified existing fastboot.py sources to send padded, larger than expected images.

He threw in already existing RSA.py sources too. Want to get mad that I'm releasing the private/public key?

If he would have added a line or two about "DONT CARE" chunks it wouldn't take so damn long to flash...

Also, I care about this devices potential. Releasing this free, for devs who can work on other things like Roms/Recovery's / kernels ect, can not attempt to make a serious attempt and getting into this device.

Every single one of you saying anything negative needs to leave. Its BEEN known how the exploit works, and NO ONE who knew cared enough to get a sticky on XDA? How about the hint that not only /system potentionally can be flashed?

Mofo = 20$, flashing to system.

Public knowledge = equals the chance that someone has some random idea, better than mofos.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] vazovskiiii:
I have bought turbo and i just can say the phone is monster :) but as one of the user already mentioned it should be rootable without 3 rd party paid solution because of this locked things development of the turbo roms is 2-3 rom and that's very bad lot of people would not buy it for this
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Skrilax_CZ:
[MENTION=1472608]SaschaElble[/MENTION], if your reverse engineering skills are "so impressive", go ahead, do some disassembly of tz.mbn and find a vulnerability to be able to blow the unlocking qfuse (assuming the device isn't permalocked by SBD_EN qfuse Moto uses).
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] 1nfinite_Design:
Finds exploit, charges the masses for it, shows it to Qualcomm/interested parties, gets decent sized bug bounty, bug to be fixed next patch cycle more than likely now. Thanks ****.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
END Thread

No one said "reverse engineering"

screw qfuse, safestrap/kexec will work just fine. Good o xt912 held its own. And safestrap can be changed to "reuse" certain existing partitions while emulating any of them.

Did you know you can get free 3g internet with a 20$ prepaid texting only plan, on verizon, by removing 3 characters from a string in the NVITEMS? I didn't reverse anything. I just kept learning about it and trying different things. Which is what I'm going to do with this Turbo. This is not a pissing contest. This is for all of us.

If I could figure it out own my own, "Moto" would have figured it out in its sleep.

Done. Please close!

Link to proper thread: http://xdaforums.com/droid-turbo/general/xt1254-free-turbo-t3118586
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Skrilax_CZ:
Then go ahead and implement kexec for msm. I'm aware how things were with both omap3 (2nd-boot) and omap4 (regular kexec), and I very much doubt that you'd be able to do it if you don't know msm internals (as QC is very not like publishing the necessary datasheets). Besides, if you bothered to read the init.rc files, you'd see that you can hijack the boot system early enough to disable qe if you're bothered by write protection, since this happens on fs stage:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
Perceptive. That's exactly what I am saying. It is easy to say how free it should be for the masses when someone else does the legwork for you. Your time investment is nothing. You didn't discover it, just want it free for the masses and act like a disservice was done because someone charged for it. Like I said, easy to say when you are not the one who did the work. You say it isn't a lot of work; well thats because you didn't figure it out. Its always easy to see the answer once its there. Quite a bit harder to arrive at it.

I don't care that you want to release it for free. I am just bothered by your attitude against the person who discovered it and charged. Maybe if dbags who make bounty promises had a little more integrity, this conversation wouldn't be happening.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] PILLMUZIK3600:
Hey if u release a free tool more power to u. I'll deff check it out
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
No they didn't, it was a free release that got reverse engineered, bump was never a paid service as far as I can recall.

I'll say it, you put little or no productive work into reversing his exploit. The lk bootloader is open source, he would not have had to reverse motorola's bootloader to find this vulnerability. DMCA actually provides some protection for what they did, however it does not for what you are advocating. You would be breaking US law, you would be pirating his work. So yes you would be the "Bad guy" in this situation.

Based on this statement, I can say you haven't looked at the code. Its certainly not 99% borrowed code.

You are not releasing any private key, since that would be stored sever side, not client side.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] koftheworld:
You're right! I forgot that was the real situation. Honestly I was just hoping for this guy to spur some additional discussion on getting wp-off for the Turbo rather than releasing a new tool. In fact, I thought he specifically stated in one of his first posts that is exactly what he was not doing. Instead he is off on a tangent about a free tool which I think is inappropriate.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
First : (IDC if the exploit was public, it sure wasn't put on the turbo thread or we wouldn't be talking)

So, he "researched" motorola's closed source bootloader for profit, and I "researched" mofo's closed source tool for free.... I'm not sure how I'm the bad guy. Your lacking a logical comparison.

right...

pastebin.com/eFWPjkaG #DroidTurboXDA

[16:29] <Harry44> i wish they would release the source of mofo

...

[16:30] <r3pwn> I looked into it. I'm not 100% sure the specifics of it, but it literally is just a fancy "fastboot flash system"

[16:30] <r3pwn> Most of it's written in python. I can trll you the names and functions of the scripts, but can not get the actual content of the scripts.

...

[16:35] <r3pwn> So back to mofo real quick, there's a few main python files: mofo.py, fastboot.py, and flasher.py. flasher.py and mofo.py seem like just fastboot wrappers. However, one of those two has a SparseEmulator to automatically sparse the ungodly-large system images.

:good:

-----BEGINRSAPRIVATEKEY-----

MIICXwIBAAKBgQDqU2ZCxwUAHwu3NQAaggtRN2dOuoYijnbnbLQaCU6xlrQsCTbm

g0wifBLnIHFOrWpcQzVy9JL/o6ucDbCpTpis+BqpwwKQFpiocxL2aaiPu3clAmSD

JptVBXKTqJ/0IghaEhHPuT4AM93YXSqVa0StvGoxvQ4l0oH6h9vLzSN1WwIDAQAB

AoGAPHCWh9Ldr1JSq0a4aB3y3Vf1BZGG15L3iGm5ap3L9nJwtosJ5hsnoB1worzz

fN+t924+cxAyek21DeNZ1uT6m4Lh1Z2S8oGqOuF6dCm34XEct5E+CANappuyjpwy

hLZGFoS7jkhQwoNytSC4Ew/MMcYEgUYCNKDhTWGPRSH/ycECRQDz9MxHuMfJJWNL

DeUgiRmiIlJ9IYOqC0w/y5qZTyGRgNBHC+co2fDXzUOsWty5/h0Ia7CBQO+cpgTb

VSFQKCYdMUCI5QI9APXk429fg2VvWqjlCDrUh4wwbzIDdfcyouMrE0z6Sx5g54J2

byg+LuAuf+SYwt10lRsPj9MP27OkaadhPwJEZM+CIxk+peZnU7qYNouxJgjc4YyZ

5gjpJ2uxpSzICGKcrt9CVOVK20KddnnNwKY7xSELPT5iRe9tDl3teDw/E80oh+kC

PG/8URRM5JOStjBLNodMeXsAJ/QYHWZ6WjKpUH3zU7i/G1CQTal/QGv64WYjqEOh

L7MGUFMoWr+itjdzkwJERF9dmrp7qwbBXFuJWH30s+FitZDz6GhIEX94d0dtXfBu

dUDBImWSroAzs0Y0RkLwi0zkQzhjtnMjslmbB1ws4rKPStM=

-----ENDRSAPRIVATEKEY-----

-----BEGINRSAPUBLICKEY-----

MIGJAoGBAOpTZkLHBQAfC7c1ABqCC1E3Z066hiKOdudstBoJTrGWtCwJNuaDTCJ8

EucgcU6talxDNXL0kv+jq5wNsKlOmKz4GqnDApAWmKhzEvZpqI+7dyUCZIMmm1UF

cpOon/QiCFoSEc+5PgAz3dhdKpVrRK28ajG9DiXSgfqH28vNI3VbAgMBAAE=

-----ENDRSAPUBLICKEY-----
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] drexhex:
wow, if true
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
Nope, check again, LK is open source, he found the vuln in an open source bootloader that motorola bases their bootloader on, its not specific to their bootloader.

Would like to do a charity wager on all of this? If your not familiar with my work or myself, go as r3pwn who I am. This is the field I live and breath, I ensure you im correct here.

L O L. Sorry no
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Oh, gotcha. I stand corrected. So he is charging 20$ for a bug in open source software?

Alright, I give.

Well, you kinda have to explain... As that key was compiled in mofo.py
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
No, he is charging $20 for the fruit of his education and research, as well as the software product he developed.

I don't have to explain. I don't support software piracy, explaining would put you on the correct path.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Hmm... Lets see... don't need your help. I can just make a usb filter that tricks mofo into thinking its the same phone no matter which turbo is plugged in....

Oh, and the key decrypts the rest of mofo after unpacking the UPX container.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] hotrodwinston:
Can we quit arguing? Piracy is wrong no matter what. But there are several people who feel that the paywall on mofo is wrong for various reasons. No amount of typing is going to move anybody from any position at this point.

Being the exploit is known and is included in open source (gpl) code we can make a free tool if we have someone who can do the coding - I am willing to help test but know nothing about code myself. Let's start from that idea and scrap any idea of pirating mofo.

Also let's drop the swinging contest. I have been involved in a few and it never turns out good.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
I believe your analysis is incorrect, but whatever I'll sit and watch.

Exploit is not open source, the software the vulnerability originates from is open source, and the vulnerability was disclosed.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] hotrodwinston:
I stand corrected.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] sunscape:
Hey, could you two just get back to doing the good work of unlocking / rooting / whatever. In the end all users like myself care about is getting more use of their phone beyond the limitations corporations like Verizon place on the hardware we own.

Of course everyone would prefer a free root tool, so release it. It might help others root other devices. Personally I prefer donating to devs that help the overall cause.

Also, making money on a root exploit, or whatever a paid tool might do, is a risk since the exploit will likely not exist for long and a free method could be released at any time.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Semseddin:
[MENTION=4229979]djrbliss[/MENTION],

i remembered and missed you when i read this discussion.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SaschaElble:
Look, right now I'm guessing what its for, but it IS there. So, either to decrypt the rest of the executable, or to sign the purchase file, or to trick the phone into uploading custom software.

Also he has something else going on like "compressive sampling".

or a "sparse-switch-payload"

"There is a sparse-switch dex byte code that is pointing the Android interpreter at an area of memory that is not actually a sparse-switch statement"

True.... But I can try and figure it out all I want. Its not like even if I guessed it exactly that someone would spend a lot of time reinventing the wheel...

So, like he uploads the padded rom into ram, and uses his payload to get the phone to copy it to /system? Maybe he uses it to confuse the living crap out of the phone, and every cycle, he gets a little bit more data written to /system at a time.

Either ways. I did make a new thread. I did ask to close this one awhile ago..
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] r3pwn:
Not quite -- the exploit wasn't even paid. Someone "rewrote it" because CM wasn't willing to let that script run in their build process. The intent of the original was to have developers make a "developer account" and keep the exploit regulated, so LG would see that it's not such a bad thing having regulated bootloader "unlocks".
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] r3pwn:
And not sure how you got those IRC logs, but I learned a bit since then, I have just mostly kept to myself.

Also, [MENTION=2376614]jcase[/MENTION] is not the type of person you would want to get into an argument with. I know how smart I am, and I know how to tell how smart other people are. I can tell you that jcase is without a doubt at least 100x smarter than I may ever be. Taking my word over his is just plain stupid.

Also, if you are so good at reversing mofo, then you wouldn't even need what I said in that IRC room, you would have known it all already. [emoji14]
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Toledo_JAB:
Thread closed.
[XDA Assist] anyespi:
Why there isn't a discussion about Elephone P5000?

I just bought this phone and have not found things like custom ROM's

and mods; I ask this because the original developers of Elephones are very slow to provide bug fixes, with which usually XDA developers can handle pretty quickly, but there is no thread where you can see information about this phone or which we can talk about it.

If you could open a thread on the P5000 Elephone I would be very grateful to you.
[XDA Assist] Razvan:
Hi there,

I'm sorry but I can't find anything related to your question/device.

Please post that in the thread bellow for more answers from the experts:

[Ask Any Question][Newbie Friendly]

Or open a new thread in this forum: Android Q&A, Help & Troubleshooting

Good luck
[XDA Assist] stipz:
Hi I've recently received a software update for my phone LG L60 Dual/X145

[IMG="screencap of update"]https://scontent-sin1-1.xx.fbcdn.net/hphotos-xta1/v/t1.0-9/11264802_817155385033350_5182325856993409274_n.jpg?oh=2c4a7ceb29d78cec54e7d0e1833da59e&oe=5602CEE3[/IMG]

I charged my phone enough for it to update and after it restarted it shows a No Command screen now and doesnt boot any further.

I couldn't find any downloadable custom ROMs, maybe anyone here knows an alternative to make my phone usable again?
[XDA Assist] stipz:
will do, thanks :D
[Galaxy S6 General] wevocy:
Yesterday the CYO-G920FXXU1AOE3 (cyprus update) was released. People from the region please post your comments on battery life and the overall behavior of your phone after this long waited update

Am not so impressed since last night on standby and 75% battery i woke up and ot was 51%

UPDATED

Also am experiencing some overheating issues. Disaster.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
Just got my replacement note 4,not sure if old one did this,but when after having screen asleep when hitting power or home button to wake screen up the touch keys will sometime lightly blink once before coming completely on with screen,doesn't do it every time,it's a bit random,wondering if anyone else see's this flicker?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
To test if you turn off touch key duration completely in display settings,and then turn screen off and back on u can see the touch keys still ever so slightly light up,at least on mine,just trying to figure out if normal or not.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
It's really faint can't see in normal light,have to be in dark.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
Really?Noone?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ajm786:
Yes, I see this on mine. And it doesn't really bother me.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
Ok lol as long as I'm not alone
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] flipq88:
Mine do as well. Hadn't noticed it until I read this thread. Also, I couldn't really tell until I covered tje the screen and just focused on the touch keys.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Raver27:
I didn't notice till I was up late a few nights ago and all the lights was off.
[Huawei Ascend P7] :
Q&A for [Q] CUSTOM ROM HUAWEI P7 aurora V12.0 UI3.0 B615SP01 PORT L10

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Q] CUSTOM ROM HUAWEI P7 aurora V12.0 UI3.0 B615SP01 PORT L10. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Huawei Ascend P7] chokeeboy:
b120

Does this work on my firmware? Which is b120? I'd really love to try aurora. Any answers would be really appreciated. Thanks a lot :)