Related
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.
Personally I think I'm gonna wait till some one uploads the update and does some testing to see what is making the phone soft brick .
Sent from my SGH-T959 using XDA App
parahelium said:
I searched and found no answer. My Vibrant is just rooted to turn off the boot up and turn off sounds. Nothing else has done, is the OTA safe for my phone?
Click to expand...
Click to collapse
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.
dublued said:
Root is ok but you will have to undo any lagfixes if you applied them.
It will most likely unroot your device but you can use the same method to root again.
Click to expand...
Click to collapse
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
What a bummer...I'm rooted w/ Ryans LagFix....hope to hear some good news in a few on a solution...
lqaddict said:
There are reports that it works with RyanZA's lag fix and root in some instances.
There are reports that the OTA update bricks even virgin stock phones, so it is a shot in a dark.
Click to expand...
Click to collapse
does the virgin stock phones mean that it is unrooted or nothing is changed in the out of the box phone?
No Success Here
My Rooted Vibrant that also went through OCLF failed to boot and hung on the Vibrant splash screen. Had to use Odin and the stock build to get it back and running. Thankful I had made backups prior to trying the OTA.
I've since renamed /etc/system/otacerts.zip to stop the OTA update but I would love to get rid of the OTA update icon. Anyone have any ideas?
mine was rooted with just the ji6 modem flashed from odin.. and some other mods like mobile ap and metamorph..
so i got the update.. and it failed on install... ahhh.... flashed back pure stock on odin.. waaaaiiitning.. praying it comes back again!
Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.
Updated ok with root
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)
d01100100 said:
Stock phone, rooted with no lagfix ever applied.
Phone is toast. I'm at work so waiting for Odin to download slowly so I can reflash the phone to stock.
Might just say skip it and apply one of the custom roms. It seems neither TMO or Samsung can get their **** together. I waited patiently for the OTA and got screwed.
Click to expand...
Click to collapse
That's what I ended up doing. I didn't want to potentially wait until the end of October so I just went ahead and flashed Bionix. I don't think I'm going back to stock ever.
atatistcheff said:
My phone had the OCLF v 2.1 plus root installed. Yesterday I removed the lag fix since most folks recommended this prior to updating. Crossed my fingers and hoped my update would arrive soon.
Today my update arrived. It installed with no issues, after which my phone is still rooted. It did pause for several minutes at the Galaxy S screen, I was wondering if I had bricked it but I waited and it came through ok.
I'm not planning to reinstall the lag fix anytime soon as I don't notice that much of a change - except in the Quadant scores ;-)
Click to expand...
Click to collapse
How many "minutes" did you wait? The notice before the update said it would take 10 minutes. I'm willing to wait, but not all night
The update portion with a status bar went my pretty quickly. My phone's been sitting on "Vibrant" for about 5 minutes and I'm starting to sweat.
I had been rooted and had OCLF but reversed both before applying the update. I also had the mobile AP, customized swype skin and custom battery meter but everything else was stock.
gancho said:
Not to be a downer but not necessarily. I was rooted with no lag fix (currently or prior) at all and it soft bricked my phone. I had the Samsung AP installed but that is about it, didn't remove bloatware or change the startup/shutdown sounds.
Got the phone running again with ODIN so I am back to stock now, without the update
Click to expand...
Click to collapse
i want to remove mobile AP just incase that is what is causing the soft bricks. ive noticed many people have problems have flashed the mobile ap. is there a way to remove with like uninstalling an application?
--without odin or flashing back to stock
I was rooted and removed some of the Samsung bloatware apps such as MediaHub etc...saw the update was available this morning and started it, phone was stuck on the Samsung Vibrant screen ever since. I put in for a replacement, could probably fix it with ODIN but new phone should be here tomorrow. I was actually having issues before that, so it could have been the phone itself...no way to be 100% sure.
For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.
That is what I am thinking as well. I have removed the update.zip from the internal storage now. The OTA is here and I postponed for a day just to be safe. I really need the GPS fix.
d01100100 said:
For the people who had issues with their OTA, did you have a file named update.zip previously on the /sdcard directory? It's the only thing I can think of that might interfere with the OTA download, causing it to truncate. Phone is recovered and re-rooted, but the Update Firmware shows no update available. I'm going to Odin flash the 9-28 JI6 image.
Click to expand...
Click to collapse
fine over here
My phone is rooted with RyanZA's one click lag fix and the update worked fine for me. I've never removed bloatware or anything though. Total I think it took about 8 minutes from start to finish.
I received the update this morning but my battery was below 10% and said I need more juice in order to install. I recharged and it kept saying the same thing after postponing a couple times. I restarted my phone and all works good now.
I'm noticing very good improvements in signal strength and flawless gps now. Maybe a speed increase also? I'm not sure about the speed thing just yet. Seems a bit snappier to me.
Lost Root
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back
Nightfall983 said:
I updated to JI6 using odin based on the info in android development section, and I most definitely lost root.
Trying one click root/unroot to see if I can get root back
Click to expand...
Click to collapse
Using the recovery mode / update.zip (the classic root method) worked for me after Odin flashing JI6.
Just got a system update notification... taking forever to install... anyone know what it entails?
Edit: SO I see that Sprint ID / EW!!!) was installed, and my Firmware is 2.2.1, and baseband is S: P100.08 S: EB28, and Build is SPH-P100.EB28...
Problem is, I can't remember if that's new or not...lol. Damn me for not paying attention, and DAMN ME for thinking that the possibility of a HC release was possible... stupid hopes and dreams....
Edit II: Just found this report... compared to the rest of the updates, the SGT got the short end of the stick YET AGAIN!!!
http://www.wirelessandmobilenews.co...epic-4g-tab-transform-updates-coming-321.html
"The Samsung Galaxy Tab update adds Sprint ID features."
I updated also and 2.2.1 is new, also ot updated the modem as seen by hitting the soft menu key during the update and looking under about phone, baseband. I would like to see if the update package had a whole modem.bin in ot but i installed the update before I got the temp file. The last update only had a modem file of a few kbytes so it just patched the modem. It would be great to get hold of a whole modem.bin as there are none for the sprint tab currently.
Sent from my SPH-P100 using XDA App
I was just going to as if anyone was able to grab the modem.bin. Hopefully we get luck and someone is able to do so.
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
I updated my rooted Gtab and the root seems unaffected. I use mine without a data pack - wifi only. I used the root to get rid of the activation nagger in the notification bar - and it's still gone and SuperUser is still operating.
However: Sprint ID only works through a Sprint Subscriber Data Pack - not over WiFi, unless you have a company "Keyword". Alas - I don't like Sprint ID anyway.
sprint tv
i installed the "sprint" id, and it says in the description about sprint tv. i had this on the evo, but i feel like i'd make better use of it on a 7 inch screen. any ideas how to get it on the tab? i searched the market under the sprint tab and had no luck finding it.. any suggestion would be great
I got the OTA shortly after trying to install clockwork and patching an overclocked kernel. I wasn't expecting the OTA until Monday, but I went ahead and try to install it (it failed, of course).
I managed to pull the downloaded zip file out of my cache and check if there was a modem.bin. Unfortunately, once again, there's only a modem_delta.bin, so no luck there.
I tried running the update again manually after rolling back my kernel, and apparently I still had a modified boot.img, so after doing a full wipe, rolling back to DJ30, and then manually updating to EA24, I was able to get the EB28 update installed, with all of its Sprint ID goodness. It's very late now so I don't have time to actually play with it much, but I'm actually happy to be back to an official build. I'm hoping they fixed a few of the bigger issues I had with EA24, but I somehow doubt it.
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
matt6x7 said:
Previously I was rooted and had the Bauxite kernel. I flashed the original kernel back and then installed the EB28 update. I lost root, so I tried superoneclick again. It said it rooted but superoneclick locked up while "Remounting system with read-only access..." My tab is unresponsive but the buttons are still lit up.
Update: I finally got it to reboot and I am rooted again.
Click to expand...
Click to collapse
Would you mind attaching your file for the original kernel? I forgot to make a backup when flashing Bauxite.
powermatt said:
What about root status? I'm hesitant to update if it breaks root because of the issues I've had with the stock gallery app (removed it via a root file explorer).
Click to expand...
Click to collapse
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Unfortunately, what is also intact is my long standing issue with the stock Gallery app (rogue sensor usage causing massive battery drain). Ah well, removed with Titanium backup, replaced with Just Pictures, problem fixed. Again.
Other than the addition of Sprint ID, this seems to be a pretty minor update. Could be my imagination, but it seems a tad snappier than the EA24 update. Could be the incremental increase to Android 2.2.1. But other than Sprint ID, there are no major new features.
powermatt said:
I applied the update last night and can confirm that root is still intact, so the super one click method should still work if you haven't rooted your tab prior to this update.
Click to expand...
Click to collapse
Thanks for the useful info. I was hesitant to run the update after the previous hassles. I've just updated mine without any noticeable detrimental effect.
regards,
Tony C.
Root was not intact for me after upgrade. I tested with root explorer, and font changer. Both failed after trying to get root permission. I just used SOC after upgrade. All was good...
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
matt6x7 said:
@lloydcabraham
Here is my backup kernel prior to the new EB28 update. Sorry for the delay, I've been engrossed in basketball.
Click to expand...
Click to collapse
Thanks I really appreciate it!
I was previously rooted with SuperOneCLick (rageagainstthecage method). I did not unroot prior to the upgrade. The upgade said it failed but a look at About Phone proved otherwise. I would suggest that people unroot before the upgrade but it did not matter for me.
After the update I no longer had root access. But I was able to root with SuperOneClick again. I have had no problems since the upgrade/reroot. There are no interface differences that I have spotted so far.
Can someone please post the application name for the Sprint ID so I can remove it. I had gotten rid of all the Bloatware and now after this update I get this which I will not use.
By the way I was rooted with Super One Click and using the Once Click lag Fix and after update I did lose Root. Just re-rooted and am fine now. Got scared because the orientation was not working and I thought it broke it. Sohow the update set the orientation lock.
Also I deleted a couple files hoping these were the new Sprint ID update.
Does anyone know what they are and if I need them can somone please post them? I will take the best guess of what I remember them being called.
Perhaps someone can post there Sprint file names.
SprintAndroid
SprintUpdate
Thanks,
Mark
Can someone post the update.zip for the update? I got the OTA notification but when it attempted to install (using Stock recovery), it failed, somehow.
Thanks in advance.
I need the update.zip as well.
Hell, mine still tries to update my tab to EA24 which always failed. Can't even get the notification for 28. Time to go to Sprint and raise some hell....
Sent from my SPH-P100 using XDA Premium App
My sprint galaxy tab was updated the EB28 the day I got it (two days ago), today I was trying to get CWM on the tab, got stuck at Samsung screen, so I used odin and flashed back to DJ30 (without baseband, which is already at EB28) and have been trying to get back to EB28 since.
Can any of you kind gentlemen who updated to EB28 do a roto backup and upload the file? I think this is the only way I can get back into EB28 at the moment.
Many thanks!
I've been searching the net for the past few days and can't find anything specific to my issue. I'm hoping one of you guys can help me out, or at least point me in the right direction.
I'm currently on 98.15.66.xt907.en.us and I've gotten the OTA message, but any attempt to update fails. I had some bloatware frozen, so I unfroze it, pretty much back to stock, but the OTA update still fails. I have always been rooted, and I attempt to protect the root with Voodoo.
Yesterday, I took the further step of UNLOCKING my bootloader. So, now I'm unlocked, rooted, and I'm running TWRP 2.5 for recovery.
Here's what happens now, if i attempt to install the OTA. The file downloads, it reboots my phone, which immediately launches into TWRP. I don't really know what I'm supposed to do at this point, so I just click "Reboot system".
It gets stuck in a boot loop...it loads all the way up, but goes back to "Shutting down" (assuming to perform the OTA upgrade again) within a minute or so.
At this point, I have to do a Restore in TWRP to make my phone stop looping.
What I would like to do is get the upgrade to 98.18.78 and be on my merry way. I can't seem to find the OTA file for download, so I can attempt to install it in TWRP. Not even sure if that's possible.
Any help would be hugely appreciated.
lostpilot28 said:
I've been searching the net for the past few days and can't find anything specific to my issue. I'm hoping one of you guys can help me out, or at least point me in the right direction.
I'm currently on 98.15.66.xt907.en.us and I've gotten the OTA message, but any attempt to update fails. I had some bloatware frozen, so I unfroze it, pretty much back to stock, but the OTA update still fails. I have always been rooted, and I attempt to protect the root with Voodoo.
Yesterday, I took the further step of UNLOCKING my bootloader. So, now I'm unlocked, rooted, and I'm running TWRP 2.5 for recovery.
Here's what happens now, if i attempt to install the OTA. The file downloads, it reboots my phone, which immediately launches into TWRP. I don't really know what I'm supposed to do at this point, so I just click "Reboot system".
It gets stuck in a boot loop...it loads all the way up, but goes back to "Shutting down" (assuming to perform the OTA upgrade again) within a minute or so.
At this point, I have to do a Restore in TWRP to make my phone stop looping.
What I would like to do is get the upgrade to 98.18.78 and be on my merry way. I can't seem to find the OTA file for download, so I can attempt to install it in TWRP. Not even sure if that's possible.
Any help would be hugely appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=44213644&postcount=5
Just do my restore in the Dev section.
I did not notice your handle Hi again.
lostpilot28 said:
I've been searching the net for the past few days and can't find anything specific to my issue. I'm hoping one of you guys can help me out, or at least point me in the right direction.
I'm currently on 98.15.66.xt907.en.us and I've gotten the OTA message, but any attempt to update fails. I had some bloatware frozen, so I unfroze it, pretty much back to stock, but the OTA update still fails. I have always been rooted, and I attempt to protect the root with Voodoo.
Yesterday, I took the further step of UNLOCKING my bootloader. So, now I'm unlocked, rooted, and I'm running TWRP 2.5 for recovery.
Here's what happens now, if i attempt to install the OTA. The file downloads, it reboots my phone, which immediately launches into TWRP. I don't really know what I'm supposed to do at this point, so I just click "Reboot system".
It gets stuck in a boot loop...it loads all the way up, but goes back to "Shutting down" (assuming to perform the OTA upgrade again) within a minute or so.
At this point, I have to do a Restore in TWRP to make my phone stop looping.
What I would like to do is get the upgrade to 98.18.78 and be on my merry way. I can't seem to find the OTA file for download, so I can attempt to install it in TWRP. Not even sure if that's possible.
Any help would be hugely appreciated.
Click to expand...
Click to collapse
I would NOT accept the OTA - the main purpose is to install a security patch to prevent you from unlocking the bootloader.
jco23 said:
I would NOT accept the OTA - the main purpose is to install a security patch to prevent you from unlocking the bootloader.
Click to expand...
Click to collapse
I was under the impression that once the Bootloader was unlocked it could never be "re-locked". Are you saying that's not the case? My BL is currently unlocked. But, I would like the bug fixes that come with the OTA update.
aviwdoowks said:
http://forum.xda-developers.com/showpost.php?p=44213644&postcount=5
Just do my restore in the Dev section.
I did not notice your handle Hi again.
Click to expand...
Click to collapse
OK, thanks...just wasn't sure about the other one since you said it fixes the 4G and WiFi. I didn't think they were broken with the OTA, so I thought yours was a custom ROM or something.
lostpilot28 said:
OK, thanks...just wasn't sure about the other one since you said it fixes the 4G and WiFi. I didn't think they were broken with the OTA, so I thought yours was a custom ROM or something.
Click to expand...
Click to collapse
Once you blow the UL fuse no way back.
lostpilot28 said:
I was under the impression that once the Bootloader was unlocked it could never be "re-locked". Are you saying that's not the case? My BL is currently unlocked. But, I would like the bug fixes that come with the OTA update.
Click to expand...
Click to collapse
correct. however, in accepting the OTA, the phone tries to enter it's own recovery, and since you have replaced it, you are getting the error picture.
I think I read somewhere that some got a hold of the updated radio, so you can flash that if you like. but otherwise, no "real" bug fixes.
aviwdoowks said:
Once you blow the UL fuse no way back.
Click to expand...
Click to collapse
Actually, not exactly the case. Since we haven't had something like this (retail phone getting unlocked by exploit) involving moto phones, we don't know that it can't be relocked. For all we know, moto could OTA an update to the bootloader that makes it ignore the fuse entirely. We just don't know. Hence the warning about taking OTAs
Sent from my XT907 using Tapatalk 4
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
This is my problem too. Hopefully there is a way.
Sent from my LG-D800 using xda app-developers app
Maybe doing a factory reset from stock recovery?
Sent from my LG-D805 using xda app-developers app
rohan611 said:
Hey all. I have a rooted D800 (AT&T variant) with stock recovery and on firmware version D80010q. I am trying to update to the KitKat, but It's giving me an error every time I download and try to update. The error is: Err: 0x1111004. When the phone reboots, it says "This device is suspected in rooting. Software update is not available for rooted device".
I have tried using OTA rootkeeper to temporarily unroot, but it doesn't seem to work. Is there any way for me to get the update without having to flash back to stock?
Click to expand...
Click to collapse
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
antawnm26 said:
Its due to the custom recovery you have on it..Go back to stock dont root and update...maybe try root keeper to see if that can help
Click to expand...
Click to collapse
nope. as i said in the OP< i have a stock recovery.
rohan611 said:
nope. as i said in the OP< i have a stock recovery.
Click to expand...
Click to collapse
then try root keeper it will disable root but back up root path and reinstate it once the update is done
antawnm26 said:
then try root keeper it will disable root but back up root path and reinstate it once the update is done
Click to expand...
Click to collapse
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
rohan611 said:
as i said in the OP...I tried root keeper to temporarily unroot and it didn't work. I'm going back to stock and going from there.
Click to expand...
Click to collapse
lol..yeah i read each statement in your OP just wanted to get to that last part of you saying your going back to stock and going from there, because thats your next option....
Let us know if you went back to stock then did the update and it worked.
I've read that some people kept root through their OTA. Why are some people able to update and others aren't. I've been reading up on this for the VZW update whenever that happens. I hope I haven't kept all this bloatware on my phone for no reason!!
Sent from my VS980 4G using Tapatalk
hinduboy74 said:
Let us know if you went back to stock then did the update and it worked.
Click to expand...
Click to collapse
I reverted back to stock using the instructions in the Stickied post. I was then able to update to D80010o. I had to call to request a rep to push out the D80010q update again though. They're calling it a "security update" so you should use that phrase when talking to the rep so that they don't get confused and think that you're just requesting that they push out the KitKat update.
Once I got the D80010q update, the KitKat update was available and I was able to update. Unfortunately, I didn't try to root it prior to updating - though to be honest, I don't really feel the need to root anymore. Only reason I had it rooted before was to get the multitasking button, but I'm okay with using an S3 layout (Menu, Home, Back) since that's the phone I'm coming from.
I have posted this in Other thread too.. may be this helps (Or save some time)
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
streetsmart999 said:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
rohan611 said:
I used ioroot to root while on D80010d. I think some people who have had success rooted while on D80010o
Click to expand...
Click to collapse
That is correct. I was on D80010o all four times I updated to Kit-kat and kept root everytime.
streetsmart999 said:
1.What ever the phone came with (never saw the version)
2. Rooted: Then just froze the apps I don't need (DID NOT DELETE) NO Exposed Or anything fancy. PURE STOCK just at&T bloat froze.
3. Then the Silent update came... I guess it was 10q (few weeks back), It was fine... ROOT remained.
4. Kitkat update came..
5. I de-froze all the apps before the update..
6. Tried to installed KITKAT after download... (After 1 of 2) it says Err: 0x111004
Once booted it said this update is not for rooted device. (or something similar)
7. I thought may be it recognized SuperSU/Super USer so I Uninstalled (Removed complete ROOT through the app) Download again the Kitkat.. Same ERROR And SAME message. I went it Recovery (Button combo) to complete wipe (Noticed RED Rooted below on the screen on Recovery) did the complete wipe and Still No Luck.
8. Go back to Complete stock through flash method as I realized ROOTED written on recovery so no wipe will help that...
9. chat with AT&T asked them to push 10q the silent updated.
10. once it was done I asked her if she can push Kitkat too.. she did.
The only thing was lost all the data in the process.. But I kept my pic's Auto backup through g+ so they are safe.. rest everything I lost which I don't care anyway. (Chat etc)
SO the BOTTOM LINE IS... If you see ROOTED on your stock recovery NO matter what you do... It will not update. If you dont see it.. then your are fine I Guess ("I guess" is the keyword)
Edit:
Also I'm not sure if there are 2 versions of root methods... So if anyone has Root and was able to update to kitkat.. Can you link which Root method you guys used.. Thanks in advance.
Click to expand...
Click to collapse
Same thing happened to me. I followed your advice in the other thread and did a reset using the LG flash tool, following rootjunky's guide on youtube and using the files from his website. Everything went smoothly except for at the end I got the same check flag error thing, but it completed the reset perfectly.
I then chatted with ATT and had him push the update to my phone which brought me up to d80010o. It finally went through the update and didn't get me the root error. So I think I'm in the green now. He said that he didn't have an option to push the kit kat update to my phone but it told him to have me do it through the software update in the settings. Which I tried and it said it was up to date. But he said that since they roll out in batches my phone might just not be ready for it yet. I will keep trying though and I'm one step further than I was before. At least it let me update. Shout out to ATT though, chat service is on point.
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )
Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it