Database Info

[OTA] 1.17.531.2 update extracted from device.

.... or maybe download link from google?

Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4

You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.

Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?

Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.

I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.

travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?

Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.

travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now

Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.

travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.

It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.

I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.

bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?

If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.

Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App

I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...

I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.

downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.

johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"

"Failed to unlock your device, Please try again later"....ugh

OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.

its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.

Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.

EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?

turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.

OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably

ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)

Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.

Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.

I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.

EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.

mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!

Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now

OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?

still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?

turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).

bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.

Did you manage to get this working?

[Q] OTA Update got me stuck in semi-bootloop...

I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.

pintyguy said:
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Because you installed it over a rooted phone (which is strange, as it shouldn't work) you're best bet is to flash it back to stock KK, especially if it already applied the trusted zone updates.
Of course, updating to KK 4.4.2 will then allow you to unlock your bootloader.
So, the first step is to flash to KK 4.4.2. Go here and follow the steps (it should keep your data so you won't lose what is on your internal SD card but you WILL lose all other app settings) -> http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Once you have followed all the directions (read, read and read again BEFORE you attempt to do anything), then go here to root and unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-info-status-of-root-for-kitkat-build-182183/
Hopefully, you didn't get the latest OTA, If so, you might be hosed as far as getting your bootloader unlocked, but I don't think they've pushed out the latest patch to KK for the XT926.
That should get you back up and running. Again, you will lose your app data (that is not stored on the internal SD card), but your internal and external SD cards will be left alone and intact.

I'm going to try, only problem i foresee is that i need to boot into AP Fastboot to be able to flash, but everytime I try it brings me back to the same error screen. Since that screen is technically AP Fastboot Flash Mode, Im going to try an flash it from there, but Im not sure. Will let you know what happens.

update
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.

pintyguy said:
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
Click to expand...
Click to collapse
do you have xt926 or xt925

Sorry, but what's the difference?

1 :angel:

pintyguy said:
Sorry, but what's the difference?
Click to expand...
Click to collapse
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?

Yes it does

pintyguy said:
Yes it does
Click to expand...
Click to collapse
then you must have previously done the modem unlock you will need to redo it that is all
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
pintyguy said:
Yes it does
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2389740
that should be the thread for how to do it tell us how it goes, i have no experience with this i am still on Verizon but others say after writing to the phone wait 5 minutes not seconds sorry i rembered wrong before rebooting other wise the settings will not stay

Awesome I was just about to ask for a link, thank you. And I actually got this phone pre-rooted and everything, so the guy before me must have flashed the modem. When I got it I just dropped T-Mobile sim in and it worked just fine. Luckily I'm not new to any of this, I just had a Galaxy s3 running CM11 I believe, but got rid of it and got this. Again, appreciate all the help. Gonna give it a go now and I'll report back soon.

billycar11 said:
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Click to expand...
Click to collapse
Well I'm about at my wits end on this one. I couldn't get the Moto Diag driver to correctly install to port, so I went with the RadioComm method instead. I followed a tutorial off this site, which I can't link to just yet asbi do not have enough posts. But followed it to a tee, and it seemingly was successful. But after reboot I only showed bars for about a minute, then right back to no service, T-Mobile could not be registered at this time. Nowhere in the comments or in the guide did they mention to wait the 5 minutes after writing with this method, could that possibly be why? I'm really starting to get frustrated at this point...

Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.

pintyguy said:
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
Click to expand...
Click to collapse
it is worth it also i told you about the 5 minute thing

billycar11 said:
it is worth it
Click to expand...
Click to collapse
I thought I was going to lose my data, didn't realize motopoc would do it without losing everything, so I figured might as well.

Any metod to update H950 ATT To 5.1.1?

I Have H950 G Flex2, But i didnt get android 5.1.1 , i love this phone even it get hot somethimes, its good for me.
I want to know if maybe someone can help me to update to 5.1.1 because i dont have ota Update avalible and if is possible, try a stock or international room of 5.1.1 for the H950 Because att have a lot of bloatware.
Thanks all!

Yes
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!

Cmcarboni said:
The various threads around here are quite helpful. If you're rooted, you're going to have to go back to stock. The OTA update should then kick in.
There's a thread over in the Android Development Section (It's at the top) that is exactly what you're looking for.
So, yes there are certainly methods by which you can update to 5.1.1!
Click to expand...
Click to collapse
Can you help me with the link please? im searching since i buy it. Thank you

Of course I can help
kiscvik said:
Can you help me with the link please? im searching since i buy it. Thank you
Click to expand...
Click to collapse
This is a detailed tutorial on how to return your phone to stock. You'll end up with a data wipe, so make sure to back up anything you want to keep. You'll want to do this first. Nothing should go wrong (no guarantees though, as always), just make sure you pick up the H950 version of the system file (and put this in the root directory of your internal storage, and rename it to "system.img" if isn't already.)
Easy Restore/Recovery/Unbrick Tool for LG G Flex 2
You'll reboot to your bloated stock system, and you should be able to get the OTA update. If you come across the "Please wait 24 hours and try again" message, just go manually set your date and time ahead, that should get it working.
Then you'll want to use this link to update to flash a 5.1.1 (rooted) system file (similar to the way you did it before).
http://forum.xda-developers.com/g-flex2/development/root-easy-root-att-flex-2-5-1-1-t3178354
After a great deal of tediousness, you can install Titanium Backup and remove all of the bloatware. Obviously, be cautious, you might break things (and then you'll need to factory reset, yet again). In the near future I'll post a thread of all the bloatware I removed without any issue.
EDIT: I've created a freezable bloatware list for those of you unsure what's safe and what's not. The thread is here:
Ti Backup Bloatware Freeze List
Once you're done with that, if you're brave enough, you can install the XPosed framework (even though the bootloader is locked) using this link:
XPosed G Flex 2
The process is a bit sketchy, the extended periods of black screen are a bit foreboding, but it worked like a charm.

I am also in the same boat. Not receiving OTA, tried factory reset and date+1 doesn't work

Has anyone outside the US or AT&T network been able to update? Perhaps it works with a VPN? I haven't been able to update my brand new phone with zero modifications.

Im outside US, and i haven't got the OTA, i been trying changing the date and factory reset every now and then...
I will try a VPN and see how it goes.

Yes
When I returned to stock 5.0.1 I got the ATT OTA update. I'm in the US.
I don't claim to know the intricacies of flashing, but there are H950 5.1.1 system images floating around these boards. Could you flash one of those while on stock 5.0.1? I'm not sure. We do have an unbrick tool though so you'd probably be able to recover.
Let me know if anyone skips the part where they let the phone update itself, and go straight to flashing 5.1.1.

I just bought this phone brand new in the box because I heard the update was out on ATT, not for me I guess.

If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.

Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
Sounds like a direct flash upgrade is a no go then. I also set my device forward a few days (like a week) to get the update.

I Just ordered this phone and will be using it on cricket wireless, does anyone know if I'll need an active at&t sim card to get the 5.1.1 update or will I be able to get the update with my cricket wireless sim card?

Nope
Using a Straight Talk SIM myself and I got the OTA update just fine.

Tikerz said:
If you're already on 5.1.1 and you try to recover with the 5.0.1 image you will brick your phone.
As far as receiving the update notification on the AT&T version, I had to change the date forward a few days. I would check for updates after each date change and eventually got the notification. If that doesn't work, do a factory reset and try again.
Click to expand...
Click to collapse
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !

errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
Did you already update?
if not wait!! and send me a mp

Sj12345 said:
Did you already update?
if not wait!! and send me a mp
Click to expand...
Click to collapse
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid

errcyco86 said:
Sorry I am new as of today.. I just bought the xda app. I don't know what an mp is. Please tell me what I did wrong tho now I am paranoid
Click to expand...
Click to collapse
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk

Sj12345 said:
Nothing is wrong, (pm is private message), did you already update your phone?
Sent from my Z812 using Tapatalk
Click to expand...
Click to collapse
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.

errcyco86 said:
Yes, went from 5.0.1 to 5.1.1
I used the method above of changing the date a month forward.. It went from saying up to date to giving me the ota
I hope the update isn't crop because I don't know much of rooting and roming. Hoping to learn stuff here as xda is full of some smart folks.
Click to expand...
Click to collapse
No, you're fine. I think he just wanted the OTA file.
Sent from my LG-H950 using Tapatalk

??
errcyco86 said:
THANK YOU! after 7 painful days this solved my issue! you are awesome I never would have thought to take off auto time and date and jump forward. In one day increments it wouldnt grab the OTA. First time i went to september and boom, I got it. !
Click to expand...
Click to collapse
So how? Just change the date and what? i didnt understand, im outside US

Unlocked T-Mobile Note 5 not getting signal

Hello everyone!
I bought a Unlocked note 5 like a week ago and it was working perfect I was using it with At&t, since I root every phone I buy I decided to root this one, after rooting; the phone started rebooting by itself ( I used Max's High on android root process ) since it was buggin me out and rebooting too many times I decided to flash another stock image ( being this 6.0 Marsmallow test http://forum.xda-developers.com/tmo...eral/note-5-t-mobile-marshmallow-tar-t3250744 ) to see if it fixed the issue, gues what? it didn't! And on top of that I got this message:
"Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost"
So it gave me the option to restart, I did, but I had signal and my messages were coming through, after it rebooted ( by itself ) like a 3rd time I stopped getting signal, when I have my at&t sim in it stays (Searching), I've tried everything I can think of, Changing apn's, I downgraded to 5.1.1 Stock and still get the same Security Error and still have no signal.
Please anyone that can help me, I've never had this issue when rooting any other phone, does this have a fix?

iYuseffitou said:
.
Please anyone that can help me, I've never had this issue when rooting any other phone, does this have a fix?
Click to expand...
Click to collapse
Robot to recovery. Backup your stuff to an otg USB and then wrote the phone completely. Flash COD6 with Odin and see what happens
Wait, before you rooted the device, did you turn on OEM Unlock in developer menu?
Sent from my SM-N920T using Tapatalk

Jammol said:
Robot to recovery. Backup your stuff to an otg USB and then wrote the phone completely. Flash COD6 with Odin and see what happens
Wait, before you rooted the device, did you turn on OEM Unlock in developer menu?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Yes I did my good sir, will try this now.
Edit: COD6 is for Note 4 lol or at least I can't find it.

iYuseffitou said:
Yes I did my good sir, will try this now.
Edit: COD6 is for Note 4 lol or at least I can't find it.
Click to expand...
Click to collapse
Crap my bad. Note 4 was last device I had before this. COD6 was pretty popular and most likely still is. Good thing you caught that! @TEKHD has a thread that has instructions on how to Odin the latest firmware for the Note 5. It's in the General section I believe. Do a full wipe first though before you flash with Odin.
Oh yeah, and I advise staying away from the Marshmallow Beta build for now.