Develop Bugs

Android update!

Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend

Throws a signature verification failed error.

Try again with the new method

Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.

Why go to 2.3.6? It´s better than 2.3.5 customized?

Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara

AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.

narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.

narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.

Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.

need to unroot

When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance

Boxa786 said:
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Click to expand...
Click to collapse
You in the right thread?
Sent from my SPH-L710 using xda premium

[Q] Official stock rom Help?

First of all, yes, I am an idiot, and yes, I have looked through the forums but just have to make sure I am downloading the correct thing.
So, a while ago, I rooted my t-mobile galaxy s3.
Today, I wanted to download a root-compatible app, it didn't work, turns out that my root somehow became disabled ( I might have accidentally wiped the superuser binaries)
So, I try to re-root my phone...several times. I finally think I have it rooted (using the official xda guide on how to root), and everything was fine, until i try to use superuser and it turns out that I am not rooted...for whatever reason. I do a hard reset a couple of times, it still shows that I am running alternate software and cannot update. I try to flash a stock rom to my phone, and that just simply fails on odin.
Now, I have completely formatted the SD and internal storage (probably very stupid), and I am just wondering how I could possibly flash a stock rom onto my phone, and if you could please link one because I believe the one I tried was not for my device.
If not, please provide some suggestions on what I should do. My device works, so it's not really time-sensitive, but I do want to re-root my android after I revert to stock roms, properly this time.
Thank you for your time and help!

Fixed
Fixed the problem, will be posting tutorial in the morning for anyone who might have the same issues!

Waiting for u!!

New problem

I'm trying to instal Cyanomodgen, and have it working properly, thats my ultimate goal
I wiped my phone completely
I do CANNOT physically put my SD card to a computer atm, I'm trying to work around it
Odin does recognize my device, I can only install TWRP for some reason and not CWM with Odin ( program stops working with CWM and crashes ) I have tried different types of CWM, to no avail. I used to have it, then switched to TWRP for testing purposes
I would much rather use CWM, honestly. Any ideas why thats not working?
I am using ADB push filename.zip /sdcard/ for my cyanomodgen and when I go into my file manager I do not see my files anywhere at all, but when I go to wipe stuff, I can see there is 200mb in there( obviously its there but i cant see it )
There's a sideload.zip in there idk what that is
I've tried sideloading the cyanomodgen.zip and I get a radio error ( maybe its just the nightly file messed up, not sure )
I have tried installing CWM with heimdall, and I have to replace my phones drivers with theirs and it tells me it was successful but when I reboot I get stuck in firmware upgrade encountered an issue and the only way to fix that is to re-install the original drivers
I just tried heimdall again, failed, bout to reinstall TWRP and await further assistance.

Got CWM working, converted back to stock image and now I'm going to try this all over again, just keeping everyone updated

I fixed my phone completely, full updated and functioning properly except video not working on snapchat, other than that its perfect, i think the nightly build has something to do with my camera.
I'll leave this thread here in-case anyone has the same problem I can come back and help them.

Wrong Test Keys - OTA update failed

Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give

That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.

Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk

Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.