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.

[Q] Went back to stock, unrooted, can't update ROM

Like the title says, I went back to stock and unrooted my phone. I got a message from Tmo today that an update for my phone was available, but on trying to update, the phone just sits at the "checking for software updates" screen and nothing happens. Any suggestions on how to fix this?

JazzMac251 said:
Like the title says, I went back to stock and unrooted my phone. I got a message from Tmo today that an update for my phone was available, but on trying to update, the phone just sits at the "checking for software updates" screen and nothing happens. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Kies.

Yep use Kies to update. Worked perfectly and then just reroot.

Have your tried going into stock recovery (after unrooting) and doing a factory restore? If the option is present, you may alsi want to wipe your cache. Hope that helps.

I am having the same issue as OP. Was rooted by CF auto root plus triangle away (deleted after use). Always stock ROM/recovery. Got OTA update notice so delayed it so I could unroot first. Checked temporary unroot option in SuperSU, no luck. Chose permanent unroot, no luck. Deleted SuperSU, no luck. Ti Backup confirms not rooted. Kies doesn't show update available and selecting upgrade through Kies tools menu fails as well. Do I need to clear my cache (which I have never done). Don't want to wipe and start over. Need to learn how to do this for future updates. I thought my basic root method would allow updates with little effort. Am I missing something? Thanks in advance.

I wiped cache and still no luck. It tells me update available and when I say install it just sits on checking for updates...
Hey OP, did Kies work for you? I installed the most recent Kies and it wont even finish connecting with my phone. God I hate being a noob at this stuff. I don't have a clue why this update wont happen or Kies wont connect. Im using the OEM USB cable. Everything says official and nothing custom. Somehow, T-mobile update knows I was once rooted or something. WTF
I should of tried OTA rootkeeper but too late now.
Any advice??

Kies finally worked. No idea what was different from previous 10 attempts...

Any suggestions how to go from TWRP back to stock recovery and keep root? I can't use the Toolkit since it's missing the stock recovery Tar file...

Screen rotation stops working?

I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?

Wow, nobody else has seen this?

WatermelonSlim said:
I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?
Click to expand...
Click to collapse
hello
i had a few issues when i upgraded from 4.4.2 to 5.0 stock lollipop... first of all check if the baseband shows same as the build name.. it should both finish in OB6 ....also try booting the phone in safe mode to see if its and app/tweak error... u could also try a factory reset or a full factory reset from recovery screen with a full wipe and cache and dalvik cache erased but i dont know if its possible in stock android recovery since first thing i do when i unbox the phone is to root... always running rooted and with custom recoveries since i like to mod and tweak my phone i suggest you to try to root and release your phone full potential hope this works for you.
Sent from my SM-N900T using XDA Free mobile app

Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.

PanchoPlanet said:
Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.
Click to expand...
Click to collapse
I just went to Settings, General, About Device, Check for Updates and installed it from there. When I go there now it says the device is up to date, so no way to do it the same way as the first time.

Tostido has a full firmware zip available, you can download extract and reflash using Odin 3.09.
Find it here http://forum.xda-developers.com/showthread.php?p=59257327
This will reinstall the latest update and should correct rotation problem.
Pp.

Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.

WatermelonSlim said:
Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.
Click to expand...
Click to collapse
sure there is... i suggest you to root your device... its very easy and means no harm unless you start playing with system stuff but basically it just unleash your phone full power.... and once you rooted you just install titanium backup which is the best back up ever (in my opinion) and u do a full system data/user data back up which it will save ALL phone and apps settings and data and you just save the titanium back up folder to your pc and then put it back once you done flashing... also be careful once u flash and you are reverting the back up since the error might be a misconfiguration somewhere... but u can choose manually which stuff u wanna restore like accounts messages phone call history and more... also remember to root back again and installing a custom recovery like TWRP or CWM so i can flash stuff and back up and get a better recovery experience and also u could flash the SD card write fix since on newer versions phone wont let you write data directly to a SD card.... hope it helps at all and good luck
Sent from my SM-N900T using XDA Free mobile app

Lollipop Update issue

I have a Note 4 on Sprint, still running KitKat. Here's my problem:
I really don't want the Lollipop update. I don't want it because I love KitKat so much and I tried Lollipop out on my friend's phone and hated the look and feel of it. I don't want it to finish downloading because I hardly have any space on my phone as it is.
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry because I'd like to use WiFi, but can't because every time I turn it on the update starts to download. I tried going into settings and turning off auto update, but that didn't stop it. I also tried filling my device storage so that there were less than 800 megabytes left, but that had no effect on the update either, it just continues downloading. I realize that there are similar posts on this issue, but none of them really apply to me. Thank you in advance for any help.

Just update it then use a kk theam the update will help i dont think you can stop the ota update

chad.420.419 said:
Just update it then use a kk theam the update will help i dont think you can stop the ota update
Click to expand...
Click to collapse
Thank you for replying, but that really doesn't help me at all. As I said several times over in my original post, I don't want the update at all. I'm constantly hearing about people choosing to keep KitKat, so there must be some way. And even if I could apply a theme to my whole phone without being rooted, it wouldn't fix all the other problems that I have with lollipop.

But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk

7H3N3RD said:
I have a Note 4 on Sprint, still running KitKat...
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry...
Click to expand...
Click to collapse
That's a tough ask for a definitive answer, IMO. IDK if it can be done but I'll offer an idea for discussion. Consider pros and cons and alternatives and even constructive differing because l don't know if it's been tried and proven to stop the persistent update on stock KitKat. There are root alternatives but your request is taken into some consideration below.
Odin stock tar will not trip Knox or require root. There are 2 stock tars for KitKat (those end with NIE and NK2, last 3 letters only, NIE being the original, NK2 the last KitKat update).
My theory is that you could...
1) Odin the first tar, NIE stock tar is linked below, let it download the OTA for NK2 but postpone the update long enough to go into Settings/System update/Auto update and uncheck the option.
2) Turn phone off and boot into recovery. It should find the NK2 update and prompt to apply it. If not there's an option to apply from cache, I think.
3) Once booted, make sure the auto update is still unchecked.
https://www.androidfilehost.com/?fid=95784891001612590
The instructions for Odin stock tar are found here but early posts in that thread may be relative to Odin if stock KitKat tar. The stock tar above is actually linked in post #2
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If auto update resets during the process, it most likely promptly starts the OTA download, negating the effort. No guarantees but reason the risks before you proceed. That's the whole theory, if someone knows the system update gets reset to auto or if that's not enough to prevent it, please advise. On a rooted Lollipop phone, uncheck auto update seemed to be enough to prevent the OK1 update from downloading and being persistent to update... I may have overlooked something in my simple theory. Did I?
Don't be angry with me if it doesn't work. Your data may not be lost but backup what you can on PC via USB, particularly photos, media and downloads on internal memory before you start. KIES may actually work to backup a lot on a stock un-rooted phone but be careful about what you restore; don't want to start the persistent update again if you succeed in preventing it.
Sent from my SM-N910P using Tapatalk

You definitely can stop it from nagging you to update by turning off notifications (I think you turn it off for Google services framework, and if not that, it's Google play services). This worked for me when I stayed on kitkat.
But deleting the downloaded update file is an issue without root. It lies in /cache or /cache/FOTA directory I believe, which you can't access without root. You may be able to wipe cache with stock recovery, but I'm not sure if it has that option (I'm not on stock recovery so can't check) or if it even works for what you want. Perhaps you can try deleting the cache for Google services framework or Google play services, not sure if the works either. Just some thoughts which may help you

No wifi after flashing, either on BPA1 or CPD1 firmwares

I was trying to get rooted, I've downgraded and am on 5.1.1 on the CPD firmware currently, but I can't get wifi back. I had the boot loader unlocked but somehow lost it after flashing to the CPD firmware. I was using this guide: https://forum.xda-developers.com/no...guide-step-step-stock-n910v-6-0-1-to-t3426905
I've made it to step 35 from there, but I can't get Kingroot to work on this current firmware because of no wifi, I guess. It tries but it keeps failing.
Any ideas or suggestions? At this point I don't care if I have root or not, I just need a workable phone with wifi

At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.

BeckPC said:
At that point, you need a SIM card because you are on the updated bootloader (CPD1) for 6.01 and will not have WiFi. You have upgraded the bootloader, but you're still on the older 5.11 baseband. Pop a SIM card into the phone and root it once again. Then follow the rest of the instructions. It works. I've done it on multiple devices.
Click to expand...
Click to collapse
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.

hondaatc said:
Unfortunately, I've pulled the sim from my working phone and put it into this one, and despite running KingRoot about a dozen times now, I can't ever get it to go through. I don't know if I don't have enough data bandwidth here in the area for it to work entirely correct, or what, but I can't seem to get past this stage or get any wifi up and going again.
Click to expand...
Click to collapse
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.

BeckPC said:
It sounds like you're stuck on a 6.01 ROM with a 5.11 bootloader. You have a few more steps to complete before you're ready to flash to your hearts content. King Root doesn't download much.
I had the same problem once. Go to setting and do a hard reset on the device, wiping all data and let it boot up for the first time (with the same ROM installed. Don't sign into Google, just skip all the setup routines. Install King Root and try again. It should work. It might take a few times. It's extremely unstable. As soon as you get root, run the ADB routine quickly and unlock the bootloader. Now you can use ODIN to flash the final file N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar. That will update you to the new firmware and restore your wifi. Don't let the phone reboot automatically. Once it's done, pull the battery. Leave it out for a minute at least. Then start up the phone in bootloader mode (vol down, home and power). Immediately after that, you want to use ODIN to install the twrp 3.0.20 file as well.
Now boot up the phone and enter TWRP. Do a standard wipe (cache/dalvic/data) but not System. Do it twice. Now reboot. You should be unlocked (open padlock on the screen) and booting into 6.0.1. You can check for root. At this point, you should be good. Now you can flash any ROM that requires the CPD1 firmware. You can always update the modem, but your firmware will remain at that version. Personally, I recommend Modest Rom 8. It's as close to stock as you can get, with a few nice tweaks and addons that makes life a bit better. From there, you can experiment all you want.
Two more bits of advice ... once you have it rooted and fixed up, you need to do two things.
1. Use Root Explorer to completely delete all files from /systems/efs folder. Why you ask, this folder will contain chinese junk that will slow down your phone. Trust me. It works and hurts nothing. Do this especially after rooting.
2.Use TWRP to make a backup of the complete system to your memory card. It's so much easier to go back and restore, than it is to redo all the work you just did.
Click to expand...
Click to collapse
Well that gives me some hope I'm on the right track, I guess I'll keep trying. I've done much of that, and the thing is every time I do a factory reset (Like before an odin flash), I get stuck in a boot loop again until it seemingly randomly comes out of it and starts up normal again, so its kinda spooky doing that. All the steps and finagling makes me yearn for my old Samsung Moment that was a simple drop a rom onto the SD card...lol

If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.

BeckPC said:
If you have the SD card installed, remove it. It may need to be cleaned for the phone to boot properly.
Just do the wipe and reboot normally. See if it will continue. You'll need the SD card later, but it needs to be formatted if it was used during the bootloader backup. It looks like you are almost finished. Just one more round with the ADB command and you'll be complete.
Click to expand...
Click to collapse
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?

It sounds like you missed a step unlocking the bootloader. You have to do it three times, with each firmware update you do. A factory reset should not have rolled back to BPA1. Why don't you take a look at the other thread on rooting and use it. When I got to the bottom of the one you're using, I knew I didn't want to do the Jasmine ROM, so I followed this one: https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Just take it slowly and it will take a couple of hours, but once it's done, you'll be rooted.

hondaatc said:
Okay, so I went back and did factory reset from recovery console to retry Kingroot. I noticed though, it set me back to BPA, and not CPD1. So now I'm trying to use odin to back back up to CPD1.
Was this normal, for a factory reset to go back to BPA, or should it have kept me on CPD1?
Click to expand...
Click to collapse
If you have rooting issues try inputting the proper APN manually before attempting to root. That was my issue. Even tho it recognized my sim it wouldn't root until I put in my actual APN settings for Koodo.
Try an older version of the root apps also.