yashsingh1/xdaforums huggingface dataset:
[Xperia Arc Q&A, Help & Troubleshooting] n3mvn:
Yes, stock GB is smoother than stock ICS. But it miss alot of features, and some new apps dont support GB, e.g: new Gmail app. I have a backup android phone run GB, the last time I check, gmail app is really suck and ugly :silly:

Flash GB if you need performance.

But for something new and fast, you should try custom roms based on Kitkat.
[Xperia Arc Q&A, Help & Troubleshooting] InternationalPlayer71:
I was also thinking about Xperia Hd Ultimate Ics based rom, just to have stock look but without missing performances. I hope it's the right choice.

Thanks for your advices buddy :)
[Xperia Arc Q&A, Help & Troubleshooting] bejunk:
after some time ICS gets always slow. sorry to say that :(
[Xperia Arc Q&A, Help & Troubleshooting] InternationalPlayer71:
So, if we only consider stock SE firwmares, do you suggest to stay with GB instead of ICS?

Thanks :)
[Xperia Arc Q&A, Help & Troubleshooting] popthosegaskets:
GB would be better than ICS in terms of performance.

僕のINO2から送られてきた
[Xperia Arc Q&A, Help & Troubleshooting] Comby_sk:
If you request rooted device, i suggest flashing 0.42, doing root and then OTA update to 0.62. Flashed 0.62 cannot be rooted.
[Xperia Arc Q&A, Help & Troubleshooting] InternationalPlayer71:
I thought a solution was found in the past..an update of one click root script..isn't it?Still no solutions to this root problem on .62??

Thanks
[Xperia Arc Q&A, Help & Troubleshooting] Comby_sk:
I am just reading this thread (http://xdaforums.com/showthread.php?t=2219711), it seems be solved. Thanks for your correction.
[Verizon Samsung Galaxy S III] poppers162:
So, our phones are running Qualcomms msm8960 chips, correct? I'm probably way off with this, but hey, this is the Q&A section. Motopocalypse for Motorola devices (obviously) has recently become very useful when the old bootloader returned on many Motorola devices. I was just wondering what exactly would happen if you installed the motopocalypse apk on this phone and ran it? Probably a brick but bricks are fixable. I am just too curious.
[Verizon Samsung Galaxy S III] BadUsername:
Who knows if it's been tried, I doubt it would work, but it's always possible it might.

You might corrupt your bootloader to a point you can't fix it. Maybe see if you can get a hold of someone who knows more specifically how it works.

Thanks for researching that, try to get as much information as possible.
[Verizon Samsung Galaxy S III] poppers162:
Any suggestions on who to ask?
[Verizon Samsung Galaxy S III] BadUsername:
Developer of the app, experienced users of the app, power users in the Motorola forums.
[Verizon Samsung Galaxy S III] poppers162:
I think I might go ahead and try it. Just for the hell of it. Haha
[Verizon Samsung Galaxy S III] poppers162:
Can't use the apk or Windows method because it only runs through the process if a Motorola device is plugged in. I have no idea how to make it think it's flashing on a Motorola device. But I did find out that motochopper works with rooting your device as well.
[Verizon Samsung Galaxy S III] pball52998:
I accidentally ran it on my HTC Rezound. (Rewriting it the proper way for Mac, for one of my friends.) It started, and went completely through. Bad thing though, didn't know my phone was plugged in... It started, went completely through... Messed it up... Had to RUU, so it should start..? It ran on my HTC lol, so it should? Run on some devices? I thought?

Sent from my HTC One M8 running Liquid Smooth Nightlies. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
I tried using it with it, and it just starts the daemons and that's it. Then I tried rerunning it with my Droid RAZR m and it ran through fine.
[Verizon Samsung Galaxy S III] pball52998:
In here there is no notion that "checks" to make sure you have an Moto.

adb kill-server

echo
[*] Waiting for device...
adb wait-for-device

echo
[*] Device found.

echo

[*] Pushing unlock tool...

adb push unlock /data/local/tmp

adb shell chmod 755 /data/local/tmp/unlock

echo

[*] Unlocking phone...

adb shell su -c /data/local/tmp/unlock

echo

[*] Cleaning up...

adb shell rm /data/local/tmp/unlock

echo

[*] Unlocking complete. Rebooting into bootloader mode.

adb reboot bootloader

echo

[*] Press enter once the phone has rebooted into bootloader mode.
pause

Nothing in there does it ever asks to execute and find out whether its a Motorola or not. Because all those commands will work on any phone with USB debugging enabled. Because the adb push unlock /data/local/tmp is very similar to Firewater's adb push.

To have a moto check I'm pretty sure it would have to be like

if ["$brand" = 'Motorola']; then
break
else
End

That's probably not right, I'm half asleep.

I could possibly rewrite it lol. I made one for all my HTC scripts. They all work great :p but moto I'm a hit and miss on

Sent from my HTC One M8 running Liquid Smooth Nightlies. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
I don't know much about scripts and stuff and how they work, but I'm not completely ignorant to it. I haven't looked at it yet though.
[Verizon Samsung Galaxy S III] pball52998:
Sorry for the confusion :/ basically, the script says. If a device is found, it will push the unlock item/key. Then it does a shell and executes it from the phone with a simple adb shell su -c command.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
I understood what you were trying to say before. I honestly don't know why it wouldn't run. USB debugging was enabled, drivers installed, phone plugged in with a good cord. Another reason why I think this could actually work is the fact that there's a developer edition now. Djrbliss, the developer of motopocalypse, explained how he exploited the bootloader on the RAZR devices. He looked at how the chip reacts when the developer edition is unlocked and found with qfuse is tripped to tell the phone that it is unlocked. But the only thing I'm worried about with it is the trustzone. I don't know if it's the same as the Motorola devices and if it can be exploited the same.
[Verizon Samsung Galaxy S III] pball52998:
Oh, I understand what you mean now. But from there, moto devices vs Samsung devices. I can almost bet, that the qfuse that has to be blown is different on moto, is probably different on Samsung. Unless it uses the same mobo, exact chip, and more to add with that. Im going to ask a noob question. Do all devices, to get the bootloader unlocked, is the qfuse blown?

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
I am not entirely sure, but it seems like it. Both phones have Qualcomm msm8960 chips. So I would assume it would work the same
[Verizon Samsung Galaxy S III] pball52998:
Possibly, possibly not. What sucks though is Samsung doesn't have like a Dev website to try to unlock the boot loader so you can see how Samsung reacts to the unlocking. But there's not :/ but on HTC (sorry for bringing them in) if you get s-off (all security flags off) you can turn the unlocked to locked and back to unlocked with one echo command with a dd. But that's after achieving s-off. I think the way that the guy who created it did it, was just watching how it reacts. Find the common security flaws. And execute it the same way as the Dev edition? It seems logical..? But you would have to find the security flaw in Samsungs bootloader. Simply because it can't be done the same way, same chips, different bootloader. I don't think you could do it the same...

Sorry if I skipped around and didn't make any sense.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
No I see what you're saying, but with the fact that the chips have the same fuses and everything, you would think it could be exploited the same way. And since there is a dev edition for both the RAZRs and the galaxy s3, and there's an official bootloader unlock for those, you would think they'd use the same type of commands when you type in your unique code to unlock it. That's kinda what djrbliss did. He watched the Motorola phones react to having the bootloader unlocked officially, and did some reverse engineering stuff to find which fuse was being tripped. He then discovered that fuse 85? Or something like that is tripped, but if you were to trip fuse 84? In the chip, it would act as the bootloader is unlocked like a dev edition. So I don't think it really would matter how the bootloader is set up, as long as you can trick it into thinking it's meant to be unlocked.
[Verizon Samsung Galaxy S III] BadUsername:
It makes sense. The script would have to be written in some way to recognize the Samsung bootloader. The file isn't being pushed because the trigger mechanism needed for the program to push the file isn't being activated.

And not every bootloader lock is encrypted with a qfuse. Using a Qfuse is an extra security step that prevents changing firmware.
[Verizon Samsung Galaxy S III] poppers162:
http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1

Here's the explanation
[Verizon Samsung Galaxy S III] poppers162:
Dammit I just want an unlocked bootloader
[Verizon Samsung Galaxy S III] pball52998:
I may have you dump some certain partitions/files for me to look at if you don't mind. Just gotta figure out which ones. Would you mind doing some dd commands? Because looking through that article you sent, gives me an idea of where to look for something. I have a lot of research to do when I get home next week... [MENTION=5181150]BadUsername[/MENTION] good point. Although most Qcomn stuff implements that ****.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
What do you need?

Edit: I have an old s3 with a ruined digitizer but the same phone. I could run some tests on it if you need me too. It's still functional besides the screen.
[Verizon Samsung Galaxy S III] pball52998:
Gonna have to get it a little later. Gonna have to get a good path and can't remember anything right now. :( but it wouldn't be much good, as I don't have my computer. Won't be home till next week :( would you mind doing it though? :D

Edit: that would be good! Don't know if I could come up with anything :( but I can sure as hell try! Never hurts to try :)

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
Haha you're definitely right. Thank you for being willing to help :D
[Verizon Samsung Galaxy S III] pball52998:
Anytime! I hope I can come up with something... Nothing is impossible... One thing, on your S3. Can you turn on USB debugging on the broken one?

Edit: Damn it. Wish I could read what motopac uses :( I could bounce off there and try. :/ because what it uses could possibly be similar to what the S3 could use.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
Whoa that's a tough one. The lcd display is completely ruined and I'm in the process of putting it back together
[Verizon Samsung Galaxy S III] pball52998:
That may be needed. :/ that's what most scripts use

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
I don't know what to do from here :/
[Verizon Samsung Galaxy S III] Ekkoria:
I can probably provide some or all of those files, but I'm not running a stock ROM. I can return to stock unrooted if you need to, I would absolutely love an unlocked bootloader as well
[Verizon Samsung Galaxy S III] poppers162:
I'm gonna throw my screen on the old phone real quick
[Verizon Samsung Galaxy S III] poppers162:
Oh my God, I stuck the old motherboard on my phone and its on 4.1.2 :D I'm so freaking happy!
[Verizon Samsung Galaxy S III] BadUsername:
That's pretty lucky.
[Verizon Samsung Galaxy S III] poppers162:
I am still willing to assist with what is needed.
[Verizon Samsung Galaxy S III] Ekkoria:
I might hate you a little bit.
[Verizon Samsung Galaxy S III] poppers162:
Just hope that someone comes up with a new exploit. My idea may even work if someone is willing.
[Verizon Samsung Galaxy S III] Ekkoria:
I'm basically willing to test anything on my phone, I'm pretty confident I can un brick it if it goes bad.
[Verizon Samsung Galaxy S III] poppers162:
Speak with pball. He is the one who is willing to put this idea to the test. By the way, thanks pball for believing!
[Verizon Samsung Galaxy S III] pball52998:
[MENTION=5033954]Ekkoria[/MENTION] [MENTION=4935332]poppers162[/MENTION] I'm thinking I might need some files from both a unlocked 4.1.2 and a locked 4.4.2. Because 4.1.2 is where it was able to be unlocked wasn't it? Then 4.3 and now 4.4.2 can't be unlocked yet at least. I need to compare some files between the two. I may sound like an absolute idiot, and people may think I'm an absolute idiot. But who's to say :p god now I can't wait to get home from vacation. D: can I go home now lol.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
You're in luck! My new motherboard is unlocked on 4.1.2
[Verizon Samsung Galaxy S III] pball52998:
Good.... Very good... Lol, and man you're lucky!! Bet that was amazing to change it and see that it was 4.1.2! Was it unlocked yet? Or still locked?

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] BadUsername:
4.1 was always locked, but it can be unlocked by flashing an unlocked aboot block.

I think the files you're looking for will look roughly the same throughout the different bootloaders. The only reason they are unable to be unlocked through the same process is because 4.3 and 4.4 look for signed files for their respective sequence. 4.1 and 4.0 don't need signed files throughout their sequence. But it's worth a shot looking at them.
[Verizon Samsung Galaxy S III] pball52998:
Yeah, the main thing that'd I'd be looking at is what actually changed. What kept the same. And what does it look like when its unlocked vs a locked one.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
Still locked, but ez unlock fixed that for me :)
[Verizon Samsung Galaxy S III] poppers162:
Maybe you should look for someone with am unlocked bootloader on either 4.3 or 4.4 just in case
[Verizon Samsung Galaxy S III] BadUsername:
OK, just so you know the difference and where to look.

Locked bootloader will have a locked aboot updated from the firmware date.

An unlocked bootloader will have an aboot dated from before the release date of the phone.

If you'd like to see the specific file pushed, download ez unlock and pull the file that it pushes from inside the application, and it would also be somewhere in the casual folder when you download it. Every unlock method uses the exact same file.
[Verizon Samsung Galaxy S III] pball52998:
True. But crap, just gotta find someone with a rooted unlocked 4.4.2 s3. That's pretty easy though.

Sent from my HTC One M8 Google Play Edition. S-OFF.

---------- Post added at 10:22 PM ---------- Previous post was at 10:00 PM ----------

Thanks man. I'll look into it. I wonder if echo commands could possibly do something... Like when a file is pushed. It changes specific files, and goes certain places to change certain things. Like on the M7 and M8, there is a echo command that can automatically change bootloader from locked to unlocked.

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796*

That's looking for one thing, and changing it manually. While if I'm right, the main thing that keeps the bootloader info is mmcblk0p5. Which is where the creator looked and saw. With 0x84 and 0x70XXX its locked. But if 0x85 and 0x70000 its unlocked and blown. I think, this is coming off my head from earlier. :eek: if I/we/someone could find the proper mapping fuse combination on samsungs you could manually change it with special echo commands? Maybe? But 1.Finding the /Dev/block with the right bootloader info. 2. Finding the right qfuse mapping and codes in which a fuse acts when unlocked, and locked. That would be the key in what you'd change. I think? Then finding the right way to script it. If someone has another idea, pitch in! So basically I took [MENTION=3320624]popper1[/MENTION]26 idea. Mixed it with some other stuff from HTC. Along with more stuff from moto. And thinking of adding stuff from the S4's issues/ways.

Someone else pitch in if you see a massive freaking flaw. If there is a few or don't think it would work, pitch in and say what you think!

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
Do you think this could actually go through and work?
[Verizon Samsung Galaxy S III] pball52998:
Possibly? I'm not really sure :( right now I'm just getting out ideas. Seeing if people think it will work...

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
From your idea, it looks very plausible. We just need the right people and files. And knowledge haha. But you seem pretty knowledgeable with all of this. I'm only 16, I'm just now learning about Android and all of its in depth glory. So I'm learning as well.
[Verizon Samsung Galaxy S III] BadUsername:
Well you're certainly on the right track, those are the locations you'd have to change. Or you could simply reroute the boot chain through a different fuse if you can figure out how to make an 4.1 or earlier bootloader boot from that . Problem is if you fail, that phone is absolutely toast with no way to recover, as with any procedure dealing with the earliest stages of the boot directly.

Htc's are actually harder to tamper with because of the s-on implementation. However, once that's turned off, the phone will accept anything you throw at it unless it bricks. Samsungs have no s-off system, so there's no way to turn that security system completely off. Instead, Samsung keeps it's security in place by coding their boot chain to match the processor's expectation. Basically, from my understanding, as long as the boot chain is routed through the same fuse, there is simply no way to boot without the expected firmware and kernel combination.
[Verizon Samsung Galaxy S III] pball52998:
True with the right files and all that stuff lol. But I don't think that would be to hard, a ton of people have the S3.

So, you think I'm on the right track? What ideas would you change, or do you think its an actual plausible idea? So, right now we know that there are certain files. We can find those, that's no issue. So from what you just said. Basically... We have to implement it into the boot chain, and make it think its part of it, by changing some of the files/phones internal boot settings. Causing either a massive brick or a successful run through. Would I be correct on that?

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] BadUsername:
Yes you're on the right track, remember there are multiple fuses in the chip. The boot chain is using the exact same fuse everytime to run the boot. Simply changing the boot to another fuse would completely unlock the bootloader. Problem is if you miss the fuse, the phone can't boot. And it would be so early in the boot a jtag wouldn't even be able to recover it.

Without Qualcomm locations for these fuses, or a leaked unlocked bootloader or unlock keys from Samsung, finding these locations is pretty difficult. Unless you have an endless supply of phones to run through until you get the coding correct.

That's pretty much all I know though, I don't know any actual coding so I don't know what else to change or where to start looking to initiate your idea.
[Verizon Samsung Galaxy S III] pball52998:
Damn.... Good point, that would be simpler, but with that choice you're taking about. Its more of a chance of bricking... Plus... Would you even be able to implement that with the phone on? So... Pretty much, have 1 chance of trying to find a way to switch qfuses. Or actually change the internal boot setting, making the bootloader think its unlocked.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] poppers162:
Which seems more plausible?
[Verizon Samsung Galaxy S III] BadUsername:
Yup, if you're dealing with the processor directly, 1 chance only.

If you're dealing with the actual boot chain you pretty much have unlimited chances with jtag or sd brick repairing in case you mess up. But you'd need a samsung leak of some sort most likely, or find an exploit within the boot chain. This is what every developer unlocking Samsung phones have looked for.

---------- Post added at 08:24 PM ---------- Previous post was at 08:12 PM ----------

Finding a vulnerability in the bootloader sequence.
[Verizon Samsung Galaxy S III] poppers162:
Well, if anyone needs a tester, I have a test device.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do a google search for "sch-i535 service manual" and see if that PDF helps out with what y'all are trying to do.
[Verizon Samsung Galaxy S III] poppers162:
The download is bad for me. Only downloads a couple kilobytes of it
[Verizon Samsung Galaxy S III] poppers162:
Edit: Used es file explorers download manager instead.
[Verizon Samsung Galaxy S III] pball52998:
Okay, so to start this... From what the article on the moto bootloader unlocking says... Its contents are on mmcblk0p5. Looking for 0x85 and 0x84. So would that be the same files we would be looking for? Or does anyone have an idea of where the bootloader info stating locked/unlocked would be? Because if we can find that. We can compare the bootloader of a stock unlocked 4.4.2 and a locked rooted 4.4.2. See where the values and mapping are for both that make the unlocked keep its unlocked value, And the locked keep its locked value. This is what would be the main thing. Trying to find the way to change this/exploiting this. -BUT- we will also have to get around the trust zone, or actually into it, changing values to match what we did in the certain value in /Dev/block/mmcblk0pX (X being the certain one we do not know yet) because each brand has a different place. 3 for HTC. 5 for Moto.

[MENTION=5181150]BadUsername[/MENTION]

So pretty much the overview steps

1. Find the mmcblk0pX that holds the information.

2. Finds what's different and how to change it.

3. Try to get that in with the trust zone, by either getting around it, or mix it in with the trust zone.

What other steps would come after the trust zone, or before the trust zone? If any? Remember that's just a basic overview.

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Just to highlight this, cuz everything y'all are discussing is above my head, we have a few early bootloader discussion threads that y'all may be able to use for reference. These all were during ICS phase of our S3. Any number of software-based factors may have changed courtesy of 4.3 VRUCML1/VRUCNC1 & 4.4.2 VRUDNE1 enhanced security software.

Here's one.

Another.

Annnnd another.

Edit: Just don't post in them cuz they pre-date our initial bootloader unlock and everyone has moved onto newer devices.
[Verizon Samsung Galaxy S III] pball52998:
Thanks man. I'll take a look :good:

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] Ekkoria:
I'd suggest checking out this page of the previously mentioned thread. Seems extremely useful for what we're trying to do here
[Verizon Samsung Galaxy S III] pball52998:
I forgot about that thread! Thanks! Lots of information to save lots of time :)

Sent from my HTC One M8 Google Play Edition. S-OFF.
[Verizon Samsung Galaxy S III] Ekkoria:
So has there been any progress on this front?
[Verizon Samsung Galaxy S III] poppers162:
My friend and I have been busy with vacation and such. This was an idea that I thought of. Me and him haven't had much time to research but there is much potential. If you check out the s4 general forum, there's a thread for talking about unlocking their bootloader. It's similar to ours. Check it out.

Sent from my Unlocked SCH-I535 running AOKP
[Verizon Samsung Galaxy S III] pball52998:
True. ^^ Sucks to say. But development can be slow at times... Very busy lives :eek:

Sent from my HTC One M8 running NuSenseSIX. S-OFF.