yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pookeyster:
if the app itself is updated, open up superuser..on the 'info' tab tap where it says in small letters 'tap to check for updates'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] onurd:
Can we have a "wake on volume button" mod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
If you can find the mod for an older stock release, I can try to port it to LH9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamanaco:
Yeah, it works... my phone is back to "Normal" whatever that means. Thanks for the tip.

EDIT: Spoke too soon. It does not "appear" to be persistent. After a couple reboots I double checked the Status is now "Modified".

EDIT 2: Had to regress to 3.0.3.2 binaries using Voodoo OTA Rootkeeper as the SetDNS app stopped working with the 3.1.1 SU binaries.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daiosama:
failed update and stuck at boot screen

I did the steps to the T from 1 to 9.

On the reboot, It stopped at the boot screen.

I ended up following the steps on this thread to revive it. http://xdaforums.com/showthread.php?t=1739426

So the next time around I skipped steps 1,2, and 8. This time I had success. as far as I know all data stayed in tact.

Thanks guys for providing good tutorials and advice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] onurd:
I haven't found a SGS3 rom that has the option. I know that a lot of the Skyrocket and SGS2 roms had it though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
Thanks, I got the green Toggles by changing the system/framework/lidroid-res.apk file with one from another ROM with Green toggles and It worked. Many thanks, learning something new every day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm a Java developer by trade and very good at deal with patches and stuff like that. I'm not really an Android developer, though. So, if I saw a mod for a SGS3 stock framework that I had, I could figure out what changes the mod was making and try to make the same changes to LH9. That's about the extent of my abilities right now. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamanaco:
Can you attach the green lidroid-res.apk or post a link from where it can be downloaded?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rfb813:
Here is a link to the Green toggles. Just flash the zip file.

https://www.dropbox.com/s/pl9ec7ffnv5wsr3/15Toggles-UCALH9g.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cruzad3r:
frikin awesome! works like a charm! thanks

OP - thanks for all the mods. i had to reinstall the tether, standby fix. i'm now trying out the no increasing ring.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woody1:
Hmm, that's odd. I updated the Superuser binaries as suggested by pookeyster and SetDNS still seems to be working for me. When it stopped working for you, did it crash or what exactly did it do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamanaco:
It didn't exactly crash. A couple bugs crept up. 1. After setting the default DNS to Google DNS the application failed to switch to those DNS during start up. It reverted to only one of the DHCP DNS (DNS1) 2. When I switched from WiFi to 4G or 4G to WiFi the status widget did not update and the Set DNS app failed to start when I clicked the widget or the app icon. It just displayed a popup with the report, stop or wait options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scyzor:
Done on top of MrRobinson stock ROM. Everything works, root is present. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Noob question

Ok, noob question here...I'm coming from rooted stock LG1 and after applying the OTA following the instructions I noticed it apparently didn't apply the update. Everything is still at LG1....modem, kernel, rom. I do think I applied the tether capability via CWM so from what the OP stated this is causing the update to abort? There was no indication that it did abort the update though. If this is true, I should be applying the framework zip he provided? Thanks for helping an previous iPhone noob.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm not sure why the OTA would not apply but not give you some kind of error message.

It might be easiest to flash all the files in the PIECES section instead. Just make sure you flash the kernel after the ROM. This will work regardless of whether you have any mods installed or not.

Good luck and don't forget to make a nandroid backup first. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wataytay69:
hi guys

tried the patchwork method and received the following error on the bootloader

-- Installing: /sdcard/I747UGLH9_OTA_bootloader.zip

Finding update package...

Opening update package...

Installing update...

assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"

E:Error in /sdcard/I747UGLH9_OTA_bootloader.zip

(Status 7)

Installation Aborted.

Thanks in advance.:cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
This means you're using the Team Epic recovery, which reports the phone is from Sprint. Install TWRP or the clockworkmod.com recovery for AT&T.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wataytay69:
I"m using the CWM-based recovery v5.5.0.4

Phone boots fine. About screen says software is up to date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That version is quite old and was put together by Team Epic. It reports the phone is a Sprint phone, which is why the bootloader check fails. The ROM will boot fine with the old LG1 bootloader and report that it's up-to-date.

If you want to update your bootloader too, check out this post: http://xdaforums.com/showthread.php?p=31895569
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duyo:
To the OP. Thank you for this. Followed your directions and phone works great. Did the mods too. Couldn't take the increasing ring tone anymore. The only other thing I would like is call record if at all possible. I found this.

http://xdaforums.com/showthread.php?t=1832991
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Thanks for the pointer. I'll take a look at it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I just added an Extended Power Menu mod to the OP in the MODS section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I added a mod that enables call recording and removes increasing ring to the MODS section of the OP. If anyone wants one with just call recording, please let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duyo:
Thank you so much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wataytay69:
Thanks for helping a total noob. Just migrated over from years of being on iOS. I installed TWRP 2.2.2.0 using GooManager. Then was able to install new bootloader. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkosma:
I'm getting an error when flashing I747UGLH9_OTA.zip. I'm on rooted stock. Don't think I've changed much else, though I did at one point try to freeze some Google Play apps in Titanium Backup.

ClockworkMod Recovery v6.0.1.2

...

assert failed: apply_patch_check("/system/lib/soundfx/libaudiopreprocessing.so", .... followed by various hex code stuff

E:Error in /sdcard/Download/I747UGLH9_OTA.zip (Status 7)

Installation aborted.

I'm guessing this is a result of installing DSP Manager. Haven't been able to figure out how to undo that without a full wipe. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The easiest thing to do is to flash all the files in the PIECES section. Flash them all in recovery before you reboot and make sure you flash the kernel after the ROM.

This will undo any mods you have installed. I'm not sure why the libaudiopreprocessing.so file was modified, but whatever did it will likely be broken until you reinstall it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
Apologies for what will be the most newbish post of your day..

My phone updated already, so I'm already on CALH9 and am totally stock. I'd like to root my phone so that ClockSync will work. I don't need any other mods at all. I pretty much like the phone as is except that it cannot keep time. Is this the mod for me? Can I apply the kernel or do I need to go back, then forward again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Rooting LH9 is apparently a little tricky. This method should work:

Download Odin from here.

Download the attached twrp-2.2.2.0.tar to your computer.

Download the attached remove-OTA-recovery.zip to your phone (internal or external SD card).

Download SuperSU CWM zip file from here to your phone.

Boot into Download mode by turning off the device, then holding Vol. Down and the Home key while pressing Power.

Start Odin. Connect your phone to the computer. You should see a green square come up in the ID:COM section of Odin.

Press the PDA button and select twrp-2.2.2.0.tar.

Uncheck the Auto Reboot option in Odin.

Press Start.

Wait for RESET! to appear in the top left of Odin, then disconnect your phone and pull the battery.

Boot into Recovery by holding Vol. Up and the Home key while pressing Power. Release as soon as you see the Samsung logo flash with little blue text in the top-left.

Flash the SuperSU zip and remove-OTA-recovery.zip. Make sure zip file signature verification is off when flashing remove-OTA-recovery.zip.

Reboot into the system.

The LH9 OTA installs two files that restore stock recovery every time you boot. The remove-OTA-recovery.zip file removes those files. (See this post for more details.)

This process will trip the flash counter, so install Triangle Away once you have root to remove it.

Hope this helps. Please report back if you try it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
Oh my, I never expected an answer that fast! Much less one that is so comprehensive. I will definitely do this when I get home this evening. Thank you so much for all the effort that you have put into this!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Eddiekranc:
just did it and rooted thank you!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkosma:
Great, doing it in pieces got the updates installed and bypassed the DSP Manager issue.

Two issues I encountered next.

1. On reboot, went to check update status, and got the error "DM initialization is not ready." Turns out I had Mobile Data switched off. I switched on mobile data and that seemed to resolve that issue, it report software is up to date.

2. Big problem, however -- I cannot get wifi to turn on. It just says "Turning on..." and hangs there when I try to enable it. Things I tried:

a. reboot into recovery, Fix Permissions - no effect

b. reboot into recovery, wipe cache and wipe dalvik cache. This gave me an "Android is upgrading" message on reboot, "Optimizing application __ of 191." However, still cannot enable wifi when it came back up.

I'm going to keep searching the forums for answers; please let me know if anyone here has a clue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Did you flash the kernel after flashing the ROM? Either way, I'd try reflashing the kernel, then wiping cache and dalvik cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkosma:
Sure enough, I had flashed the original components in the order they were listed, which had the kernel before the ROM. I rebooted into recovery, re-flashed the kernel, and now WIFI appears to be working fine.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
Thank you, I beleive that I have it. At least SuperuserSU asked me if I wanted to extend root permissions to CLockSync now and ClockSync seems to be on rooted mode. I made some minor edits to your instuctions for the next total new person. :) Might save them some time.

Download Odin from here.

Download the attached twrp-2.2.2.0.tar to your computer. Remember where you put it.

Download the attached remove-OTA-recovery.zip to your phone. Remember where you put it.

Download SuperSU CWM zip file from here to your phone. Remember where you put it.

Boot into Download mode by turning off the device, then holding Vol. Down and the Home key while pressing Power then rapidly moving your fingure to volume Up once you see it try to enter download mode.

Start Odin. Connect your phone to the computer. You should see a green or pale blue square come up in the ID:COM section of Odin.

Press the PDA button and select twrp-2.0.0.0.tar.

Uncheck the Auto Reboot option in Odin.

Press Start.

Wait for RESET! to appear in the top left of Odin, then disconnect your phone and pull the battery.

Wait a minute and put the battery back.

Boot into Recovery by holding Vol. Up and the Home key while pressing Power. Release as soon as you see the Samsung logo flash with little blue text in the top-left. It's very quick and you might miss it. It's ok if you do, just try hold the 3 keys again.

Once twrecovery mod starts, select Install, then find the SuperSU zip and remove-OTA-recovery.zips and install them.

Reboot into the system.

I received a signature error for the remove-OTA.recovery.zip however I was able to remove the 2 files that were described in the post that you linked to. Just had to figure out that I needed a rooted file explorer, then it was easy.

Again, thank you so much for the time and effort you put into helping me out. I truly appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I've never figured out how to sign my recovery zips. You can disable checking the signature in recovery. If you do that, the zip will do the right thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
Ah, thank you. I wasn't sure if that was the issue or the zip was corrupted moving it around. Is there more to it than the two files removed? should I run that or am I good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
No, it just removes the files. I made the zip because it has to be done before you boot into the ROM or you'll lose your custom recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
Hmm. I got to them after I booted into the rom and downloaded a root file view and used superuser to give it permissions.Should I do it all over? I'm not clear on what I have to lose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I suspect you've lost your custom recovery and now have stock recovery. All you need to do is re-install the custom recovery. If you don't mind, it would be helpful if you could check your recovery first and report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] navaho99:
You were entirely right, I had lost twrp. I flashed it again and I'm set now. Good catch and thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] laanrobe:
Worked very well for me!

Managed to get to H9 following these instructions. This is great job by drothenberger and really appreciated. I have a rooted S3 with TWRP and of course the OTA update failed for me first and I was at a loss. Interestingly enough (as observed by another poster) I also lost root following the approach described here, but with VooDoo OTA Rootkeeper I managed to restore a backup of root without a problem. Also, I observed upon rebooting that I had a screen showing something like 'Android update, optimizing applications' for quite a while as it was going through about 140 applications. For clearing the data of the AT&T Software Update app I had to force stop the app first before I could clear the data. Apparently the app had already started checking for the update again (app icon with the blue and red arrow was showing in the notification bar as soon as I rebooted).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm glad it worked for you.

I'm not sure why you lost root. The OTA zip does not remove either /system/app/Superuser.apk nor /system/xbin/su. That should be sufficient to keep root. Can you check if your "su" binary is installed in /system/xbin and not /system/bin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] laanrobe:
su binary is in /system/bin... Is that a problem? I rooted following a method on galaxys3root.com.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
It's not a problem for you but it explains why you lost root when you ran my updater. I'll fix it ASAP so others don't encounter it. Thanks a bunch for checking for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Fixed issue causing loss of root for some

Okay, I've updated the zips so they will preserve the permissions on /system/bin/su as well as /system/xbin/su, so hopefully nobody else will lose root by flashing any of them. Sorry about that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statusnone:
Okay so I have the un-rooted, bone stock I747UCLH9 OTA update from AT&T. I want to do a stock rom flash with root laced into the ROM. Will flashing just the ROM from the OP give me root access without triggering the flash counter? I really don't want to brick my phone either so if I can flash this with Odin, I'll be good to go. Thanks for the help guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ppablo21:
assert failed: apply_patch_check("EMMC:/dev/block/mmcblk0p7:5712128: fb95a5d43d651be3972f96e8d6d2eb181a9fc66b:5703936:c1662e87c5d06b735cb46b9673876727f65cb48b", "c1662e87c5d06b735cb46b9673876727f65cb48b", "fb95a5d43d651be3972f96e8d6d2eb181a9fc66b")

E:Error in /sdcard/clockworkzips/I747UCALH9_OTA.zip

(Status 7)

Installation aborted.

result was NULL, message is: assert failed: install_zip("/sdcard/clockworkzips/I747UCALH9_OTA.zip")

I:using /data/media for /sdcard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I don't think I understand. You are already on UCALH9 and need to root? If so, you can follow the directions in this post. Otherwise, tell me what version you're on now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
See this post: http://xdaforums.com/showpost.php?p=31814825&postcount=21
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bronos:
Does this method clear and reset my phone?
[HTC EVO 3D] viehburg:
Hello

im from germany so sry for my bad english.

i have a quation is it possible to root a evo 3d wit hboot 1.5.. without to use HTCdev for open the bootlocker ? becouse i dont want to loose my warenty;)

thanks

viehburg
[HTC EVO 3D] beneath-a-burning-turtle:
Well even if you did root without htcdev unlock, it still voids your warranty regardless
[HTC EVO 3D] viehburg:
so it is the same if i do it with or without htcdev ?
[HTC EVO 3D] beneath-a-burning-turtle:
Yep
[HTC EVO 3D] johnmarshton:
IT IS NOT THE SAME!believe me!if you don't unlock via htcdec(with other method) you can revert back to locked s-on.if you unlock with htcdev you can only go to relocked s-on so they know you messed with your phone.unfortunately,for hboot 1.5 there is no other method.only for 1.4
[HTC EVO 3D] cupliz:
Just downgrade your hboot using cd method, use 1.40+revolutionary, use powduh/commonsens/meanrom and custom kernel and you will find your phone flying high... And at last you still can get back to haboot 1.50 locked

This phone is imortall... Lolz

Sent from my PG86100
[HTC EVO 3D] ramjet73:
I don't know if the same is true for the GSM model, but doing the JuopunutBear (wire trick) method for S-OFF left the two CDMA Evo 3D's that I have with a ***LOCKED*** bootloader even though it was ***UNLOCKED*** previously, and those were both on hboot 1.5. The bootloaders are still ***LOCKED*** and I use custom hboots to be able to use the fastboot commands that a locked stock bootloader doesn't allow.

ramjet73
[Eee Pad Transformer General] erups:
Hi guys.

I myself have just got a new gnexus and am incredibly happy with it: i can watch full-hd mkvs with AC3 audio using DICE player without so much as a hiccup.

Even through hdmi!

Now my fiancee's tf101 was never capable of the same even after i updated it to AndroidRevolution 3.5.1

The very same file my gnex plays fine, is totally crap on the eeepad.

Any hints?
[Eee Pad Transformer General] sidneyk:
If you are rooted, then you might try K900's AOKP JB in the Rootzwiki forum. It works great with Netflix video and Youtube. I don't know about the file type you're talking about, but it would be worth a try and it performs well without any overclocking, too.
[Eee Pad Transformer General] JoinTheRealms:
Some people have reported this issue, as for me mine played 1080p, 720p video fine, even on stock rom/kernel. You might want to try MX player
[Eee Pad Transformer General] sbliner:
Yeah...a lot of people initially think their TF101 can play anything, but it's usually because they are not testing the same file as the person with issues.

Here's an example file:

http://www.transformerforums.com/fo...touchpad-android-vs-tf101-video-playback.html

Bottom line..highprofile mkv's (a common downloaded format) don't play well on TF101.
[Eee Pad Transformer General] sidneyk:
I can't play that sample video at all, not with MX Player w/HW+ decoding enabled, not with ES Video Player, not with stock video player. All say can't play this video.
[Eee Pad Transformer General] erups:
Well the tf101 has a tegra2 which is similar to the dual core A9 powering the Galaxy Nexus (I believe the Tegra2 is a dual core A9 too).

Screen resolution is the same (1280x720).

So why, technically, the tf101 shouldn't play the same files the same way a Galaxy Nexus does?

The fact that it doesn't happen is not a justification as to why it doesn't happen.

Also I suspect this has to do with kernel still being version 2.x.

If there ever is a kernel v3.x that will probably give a big help in this department.

But I'm pretty pissed at this right now.
[Eee Pad Transformer General] C.Flat:
I've seen it mentioned that it's because tegra2 doesn't support neon while the gnex's processor does.
[Eee Pad Transformer General] sbliner:
Heh..I'm not justifying the TF101's failure at playing video files. Heck I am the author of the post in the other forum showing the issue. What I was pointing out is people's incorrect statements that their TF101 can play any file, and that it's just a 'wrong player' issue. (which it isn't)
[Nexus 7 Q&A, Help & Troubleshooting] chris.wueste:
I am the OP of the thread on unbricking your nexus 7. I have had several people have a problem and am trying to find a solution. It should be fairly easy to do but it is not flashing the stock system and instead just hangs on the cmd prompt window. This happens whether you do it manually or try one of the toolkits. Please help!!!
[Nexus 7 Q&A, Help & Troubleshooting] chris.wueste:
I can verify first hand that there is a problem and it wasn't there at the time of writing my guide on unbricking. I attempted to restore to factory so i could RMA my tablet due to a broken back speaker. However, I am unable to get my tablet back to stock. It will just sit on "sending system" for hours.
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Try "fastboot erase system" then flash the stock ROM.
[Sony Xperia P, U, Sola, Go] nathan96:
in a good situation I have like 140 free ram and when I game it goes to 10-40 available ram...
[Sony Xperia P, U, Sola, Go] noim:
In my Xperia P I get 475mb free ram & 570 mb ram when all task is killed..
[Sony Xperia P, U, Sola, Go] nathan96:
forgot to mention that I own the xperia u :)
[Sony Xperia P, U, Sola, Go] XperiaU:
180-210mb.

And it depends on what game are you playing

If you play HD games like ShadowGUn the ram left will be like 20-30

When you're playing normal games like Angry Birds etc ram will be like 100mb left etc.

If you think I helped you please press thanks button :)
[T-Mobile Samsung Galaxy S II SGH-T989] paezscamardella:
I tried UNOFICIAL CM10, AOPK all build, CM10 TeamChopsticks.

and the only thing and could not do with all these roms is playing ASPHALT 7, I do not know why? everything else works fine.

I need some fix, or something else?

:confused:
[T-Mobile Samsung Galaxy S II SGH-T989] angellsl:
Stay with stock legal based rom, you'll be fine. I've the game running on darkside rom v8
[T-Mobile myTouch 4G Slide] K7Cobb:
Hey did anyone get face unlock to work 100% on virtuous infinity beta 1?

Sent from my OverDosed 4G Slide