Related
Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App
trumsey2005 said:
Got the firmware today.. when it loaded it ran the entire progress bar and later said that it failed.. however in the settings it say jh7 and additional attempts to update says no updates available. Also.. after the update the superuser app is still installed and appears that root is still there. Any thoughts?
Sent from my SAMSUNG-SGH-I897 using XDA App[/QUOTE
I take it back.. after changing clock and checking again the update is available again...
Click to expand...
Click to collapse
You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.
I read somewhere that people have had to flash back to complete original. I've rooted and removed AT&T crapware. Also, being new to the Android platform I need some guidance on how to go back to factory orig. I've heard of odin.. but base on my limited research I haven't seen if it is available to mac. I am familiar with Unix/Linux.. they are my primary OS'.. but messing with a phone OS is just a different animal altogether.
I had to redo the phone but the update never showed up.. So what I did was just flash the update from samfirmware and it is working even though I have to redo everything...
HTH,
Charlie
evil5826 said:
You have to unroot before you can do a ota upgrade. Rooting is suppose to block ota upgrades because a ota upgrade would remove superuser.
Click to expand...
Click to collapse
My phone is rooted and I updated without issue.
Well i just tred to update mine this morning, i finally got past the communication errors. The download went fine, but when it was installing it went from 0 to 50% percent in about a second and then said update failed and rebooted.
I'm on the stock JF6 rom, however i used odin to get there.
My Sim card and sd were left in, however my sd is blank
And i don't know what any other info i can post to be helpful
2.1 update
just did the update with one click root loaded.went though with no problems phone is faster with less lag.also i can still use as wi fi hot spot. new Quikoffice,Media hub,Mobile Video and you tube. well this may mean no 2.2?
I also did the ota update with root installed, allowed 3rd apps, with wireless tethering, and it went through fine for me but I still have poor gps, did not seem to do anything for the gps except removed the option to enter lbs test mode. Anyone know how to get to the lbs test mode after update?
Samsung Mini-Kies Updater
If anyone is having troubles with Mini Kies (I had the problem where the application crashed, using Win 7 x64), I'd recommend using the regular Samsung Kies application. I was unable to do the JH7 update even after restoring to complete stock with Odin (50% update failed error). This was easy, and now I am fully in JH7, and so far the GPS lock is much, much faster.
I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium
Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app
Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD
KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.
I am trying to update my Note 4 OTA and am running into an issue..
Both my phone and SD card are encrypted. My phone is stock. Previous updates I have done via Samsung Kies.
When I update it, it downloads the package and goes through the reboot sequence. When it starts the update process, it gets to about 2% and then says that the update failed and reboots and restores the previous settings. If I try to update via Kies, it goes through all of the screens and when I click the OK on the screen that says to not try to use the phone during the update, it just goes off into lala land and doesn't do anything at all..
Does anyone have any ideas as to what could be going on?
Thank you for your assistance.
Do you have reactivation lock enabled
BAD ASS NOTE 4
No. Reactivation lock is disabled. I verified it just in case, I have never used the feature.
ftanner said:
No. Reactivation lock is disabled. I verified it just in case, I have never used the feature.
Click to expand...
Click to collapse
I dunno man. By encrypted what do you mean. Knox or ????
BAD ASS NOTE 4
No. I mean I used the on-board encryption tool to encrypt the SD card and the internal phone storage. In the Security settings. I encrypted the device and the external SD card.
U might want ask a dev. U might get faster answer
BAD ASS NOTE 4
Have you tried to Odin the update?
ftanner said:
No. I mean I used the on-board encryption tool to encrypt the SD card and the internal phone storage. In the Security settings. I encrypted the device and the external SD card.
Click to expand...
Click to collapse
You will need to disable the encryption before going forward. The encryption is doing what it's supposed to do; preventing writing new code.
Sent from my SM-N910T using XDA Free mobile app
Will I be able to decrypt it without losing the data?
Disabling the encryption was the answer. I did not lose any data.
I would like to thank everyone for their assistance.
ftanner said:
I am trying to update my Note 4 OTA and am running into an issue..
Both my phone and SD card are encrypted. My phone is stock. Previous updates I have done via Samsung Kies.
When I update it, it downloads the package and goes through the reboot sequence. When it starts the update process, it gets to about 2% and then says that the update failed and reboots and restores the previous settings. If I try to update via Kies, it goes through all of the screens and when I click the OK on the screen that says to not try to use the phone during the update, it just goes off into lala land and doesn't do anything at all..
Does anyone have any ideas as to what could be going on?
Thank you for your assistance.
Click to expand...
Click to collapse
maybe try to desencryption i think the virtual machine dalvilk and art are not compatible in some functions
So, I've got a hard task that I cant seem to figure out.
My phone sometimes will say "Invalid Card" When I look at the lockscreen and wont let me use Data.
I've got the L90 Variant and have NOT done the 2nd Lolipop Update which would remove my root access.
My Question is, If I were to flash stock Lolipop and update, would I be able to root anymore?
And If i dont have to, How Do i fix this problem?
My Phone will sometimes even get a Toast Notification saying that android.phone has crashed and then it wont connect to T-Mobile and say Invalid Card too.
Any help?
I would factory reset first (backup your data preferably using custom recovery to get a full backup) to make sure it's not a hardware issue.
You can root with Kingroot, I've used it with 20b and 20c, then used a script to replace it with SuperSU. Or install a custom ROM layer.
Sent from my LG-D410hn using XDA Free mobile app
Hello,
I'm trying to update my rooted nexus 6 using OTA updates with FlashFire. It detects I've downloaded the OTA (I am currently on build LMY47M), but when I click flash, it says, "Warning: it has been detected that you may be trying to flash a block-level OTA, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail.
It's been a while since I last upgraded and rooted my phone. I used the nexus toolkit when I did so. Now, I know that build number is for t-mobile phones, and I do have a t-mobile sim and network, but I got the phone straight from motorola, so it should be unlocked. Is this a case where the wrong image got placed on the phone way back when? What can I do to fix it, so I can upgrade? My goal is to get to Marshmallow, and ideally not lose all my stuff. Any ideas?
cptInsane0 said:
Hello,
I'm trying to update my rooted nexus 6 using OTA updates with FlashFire. It detects I've downloaded the OTA (I am currently on build LMY47M), but when I click flash, it says, "Warning: it has been detected that you may be trying to flash a block-level OTA, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail.
It's been a while since I last upgraded and rooted my phone. I used the nexus toolkit when I did so. Now, I know that build number is for t-mobile phones, and I do have a t-mobile sim and network, but I got the phone straight from motorola, so it should be unlocked. Is this a case where the wrong image got placed on the phone way back when? What can I do to fix it, so I can upgrade? My goal is to get to Marshmallow, and ideally not lose all my stuff. Any ideas?
Click to expand...
Click to collapse
That message will show up any time FF detects the system has been modified. Mounting the system r/w or using system root (as compared to systemless) will trigger the warning. If you are using the full OTA downloaded from Google's website, then Chainfire indicates you can ignore that warning.
ktmom said:
That message will show up any time FF detects the system has been modified. Mounting the system r/w or using system root (as compared to systemless) will trigger the warning. If you are using the full OTA downloaded from Google's website, then Chainfire indicates you can ignore that warning.
Click to expand...
Click to collapse
Awesome. That is helpful. I did download the full OTA onto my computer, but unfortunately, I can't get my phone to recognize on any computer, not even the one I usually use. Oh well. The factory restore got my data connection back for the time being (I heard about the issue being widespread after I had already done this). I will most likely just wait until the Marlin comes out in a couple months.