Develop Bugs

[Q] tmobile OTA and rooted phone

i have a T989, rooted, Clockwork Mod, and installed some stock Android (sans bloatware) MOD.
i had updates set to automatic and am now being bugged to install the new TMobile update, which doesn't seem to be able to install with Clockwork, and i can't turn off the persistent Update prompts.
i've already bricked one GS2, and obviously fear doing it again. I wouldn't get another chance, i don't think. (i do have insurance on the phone, not sure if it would cover a rooted phone?)
what can someone tell me about the TMobile update and Clockwork, or whatever i need to do, go with the update or stop it somehow...?
thanks for your help.

Ota update requires stock recovery.
Grab one of the updated stock roms and flash via cwm. Then Odin the new baseband.
Sent from my SGH-T989

i think i have one of those stock roms - i chose one that was just 'the same thing but without some of the standard apps'. how can i check to see what rom i have...?
and what do you mean by baseband? the new update? is it already dl'd to my phone? i've searched through the phone's dirs (rooted File Explorere, i guess) and could not find anything...

sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?

glennnall said:
sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?
Click to expand...
Click to collapse
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989

ok, found Deodexed_KL1_T989 (T989UVKL1 by Whitehawkx) is that what i'm looking for? -
couple of questions:
he says on the post:
"DONT FLASH - add files to the zip in the app folder, then flash. Or usb connect drag to sd the use some rooted file explorer to place in system/app then reboot."
Flash or don't Flash? I'm transferring the zip to sd now, then i need to move it to system/app...?
once i've 'flashed' what do you mean "Odin the baseband"? i have Odin, used it last time...
thanks

GideonX said:
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989
Click to expand...
Click to collapse
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?

I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.

Genesis3 said:
I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.
Click to expand...
Click to collapse
ok, thanks - this is what i didn't understand - i can Odin back to Stock recovery?

for some reason Odin doesn't recognize my phone in download mode, but it does when i'm connected and the phone is on... any reason for this? i don't use odin in any means but download mode, right?

glennnall said:
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?
Click to expand...
Click to collapse
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.

GideonX said:
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.
Click to expand...
Click to collapse
did all this, nothing's changed. i'm unable to get Odin to see my phone in DL mode. when i boot into DL mode, the device manager shows an alert on my phone. in normal, the drivers work fine and Odin sees the phone.
damn.

Stuck on boot animation after flashing rom

Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!

Flash the stock ROM on the phone. You have access to recovery so use it then after you verify you can boot with the stock ROM then try flashing another ROM on again.
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
No idea what caused you from being able to boot to this issue but this is my advice.

by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
Click to expand...
Click to collapse
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it

polish_pat said:
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
Click to expand...
Click to collapse
Go into cwm, do a wipe and also go into advanced and wipe dalvik. You should then be able to reflash your custom rom to fix your boot loop. If thats successful then go back to cwm and make a NANDROID backup so they have a restore point if anything goes wrong in the future.
If you want to flash back to stock its quite simple and can all be done from my ToolKit. Its basically going to http://code.google.com/android/nexus/images.html and downloading the latest factory rom for your model, moving it to the correct folder in the ToolKit and then selecting option 8 from the ToolKit to extract the images and flash it.
Mark.

polish_pat said:
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Click to expand...
Click to collapse
I've run into the same issue tonight going back to Apex 1.0.2 from the 4.0.4 leak. I'm trying the suggestion below to wipe and re-flash the ROM. I'll report back when I'm finished.
Edit: Yep, it worked!

T-Mo S3, was 4.3, reset to 4.1.2. Trying to root for the first time.

Stock T-Mobile S3 started getting slow, so I decided to rebuild. I reset the device, and attempted to root it for the first time and install Archidroid 1.x. Odin 3.09 loaded CWM Recovery and PhilZ (or at least claimed to), but the system booted into the standard Android manager, and it won't install from the media, claiming the file fails verification.
I'm pretty sure the phone was upgraded OTA to 4.3 before I wiped it, but now claims to be 4.1.2. Does this mean that I'm suffering the effects of Knox, or is there something very basic that I'm missing?
Thanks for any replies; this isn't my first rooted phone, but I'm no pro.

So Archidroid was a bad call; it's for another verndor's version. Regardless, I've only gotten an aftermarket recovery to load once, after disconnecting from the Odin session without a reboot, pulling the battery, and going straight into recovery.
Is anyone else seeing this, and is it Knox related, or something else? Is there a fix for it?

Just go into recovery and flash a ROM, Knox is not going to prevent you from flashing ROMs or recoveries
Sent from my SGH-T999 using Tapatalk

[Q] Rooted phone accepted KitKat OTA and Bricked Phone

Hey guys, I'm REALLY hoping someone can help me. My phone was rooted on 4.3 and I stupidly accepted the KitKat OTA update without unrooting, and now my phone wont boot pass the AT&T logo. I have tried factory data wipe, doing an emergency firmware recovery on kies, tried flashing a stock rom on odin, and tried putting stock update on sd card and doing it that way, but it either wont flash or STILL wont boot past the at&t logo. Besides the root access, everything on my phone was stock. I just want to be able to use my phone again! Can someone please help me? I NEED my phone lol

I just installed a custom recovery. Now what?

Have you waited a bit for the boot process to go through it took me like 5 minutes after a ota to KK.....IF the little att chime at the att logo by all means it should boot

yeah I let it sit like half an hour...

Did you get the att chime?

KillaMike99 said:
I just installed a custom recovery. Now what?
Click to expand...
Click to collapse
Can you boot into your custom recovery? If you can, try flashing a custom KK ROM.

yes I get the AT&T chime. sometimes the chime is real choppy tho. what KK rom should I flash?

Any of your choice

do you recommend any? Im new to custom firmwares on android

Try Carbon or Valudus.

Thanks Guys! I installed a custom ROM and its working like new! I dont think I can ever get stock back, but I dont see much of a difference. Now that my warranty is gone, whats the benefits of having a custom ROM and what one has the best features? I am on hyperdrive ATM, but I would like a good kitkat rom

same issue, only....
I can not get ANY rom to get past the boot screen,.... I have no idea why it is getting stuck...
I have tried CM - various nightlies and screenshots. validus, c-rom, all to no avail.
i am going nuts over here...any one know what I might be doing wrong?
i have tried all the formating, cache, dalvik wipe, format system, reset all user data etc....
could it be a kernel I need?

[Q] TWRp can't restore backup/wipe cache.dalvik.etc

I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ

If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.

PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve

The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.

PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.