http://www.mediafire.com/?wkhvh91lp7792yr
Requirements:
1. A custom recovery.
2. A nandroid backup.
3. Stock files, sans root.
4. Optional, but recommended that you use this to backup root access first:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
It shouldnt hurt root either, but make a nandroid to be safe.
If you lose root, try flashing this:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Updated: Removed tz.img because I don't think its needed.
So this is the OTA minus the new bootloader? So basically the new radios and the kernel patch only?
Trying this out but back up to two different locations just in case.
SeanPlunk said:
So this is the OTA minus the new bootloader? So basically the new radios and the kernel patch only?
Click to expand...
Click to collapse
Yep, and whatever else it patches.
So I can just make a nandroid and flash it over Beans v6 and it should install the radios just fine right?
nnnnr14 said:
So I can just make a nandroid and flash it over Beans v6 and it should install the radios just fine right?
Click to expand...
Click to collapse
Nope. Check requirements
I added a third one in anticipation of that question.
1) Will this work for the Verizon version of CleanRom?
2) Do I have to unroot? The directions aren't clear to me. Sorry about that.
3) If I do have to unroot, can I just use OTA rootkeeper to root again afterwards?
SeanPlunk said:
1) Will this work for the Verizon version of CleanRom?
2) Do I have to unroot? The directions aren't clear to me. Sorry about that.
3) If I do have to unroot, can I just use OTA rootkeeper to root again afterwards?
Click to expand...
Click to collapse
All answered in first post (requirements).
Thanks
1. No
2. No
3. If you lose root.
So ill have to be on stock rom...
nnnnr14 said:
So ill have to be on stock rom...
Click to expand...
Click to collapse
Yes. There is no safe way (that I know of) to force patch files on a custom rom.
When I get home, I can make a deodexed patch file, but it will overwrite any custom changes you have.
adrynalyne said:
Yes. There is no safe way (that I know of) to force patch files on a custom rom.
When I get home, I can make a deodexed patch file, but it will overwrite any custom changes you have.
Click to expand...
Click to collapse
Custom change? As in rom or themes cause I could always flash beans or another rom afterwards right?
nnnnr14 said:
Custom change? As in rom or themes cause I could always flash beans or another rom afterwards right?
Click to expand...
Click to collapse
Sure but if you flash a rom after, you just overwrite the OTA anyway.
Hey adrynalyne, thanks for all the work!
I'm about to apply this now and I have a quick question. I "Deferred" the initial update for a few days, so if apply this, will my phone still try to do the update after the deferred time? Or will it do a check on the version and see its already updated?
Thanks,
Niko49 said:
Hey adrynalyne, thanks for all the work!
I'm about to apply this now and I have a quick question. I "Deferred" the initial update for a few days, so if apply this, will my phone still try to do the update after the deferred time? Or will it do a check on the version and see its already updated?
Thanks,
Click to expand...
Click to collapse
It will stop annoying you if you apply this.
adrynalyne said:
Sure but if you flash a rom after, you just overwrite the OTA anyway.
Click to expand...
Click to collapse
Ohhh... :/
Everytime I try to apply this I get "assert failed: apply_patch_check("/system/app/SystemUI.apk", "<insert some hash>", "<insert different hash>")"
I am running CWM v6.0.2.5, and I am running the stock Verizon ROM with a few mods applied.
Yeah you have modified SystemUI.apk. You will need to put it back to stock. The original files must be in place.
Also, this might not remove an update if its been deferred. But the new one can't install over this one so... make sure you have a custom reovery flashed, run it and it won't be deferred anymore.
adrynalyne said:
Yeah you have modified SystemUI.apk. You will need to put it back to stock. The original files must be in place.
Also, this might not remove an update if its been deferred. But the new one can't install over this one so... make sure you have a custom reovery flashed, run it and it won't be deferred anymore.
Click to expand...
Click to collapse
Thanks, My "Wifi-Toggle" mod had modified it. It looks like we will also loose "All apps to Multi-Window mode" too, as the services.odex file has to be restored as well.
Niko49 said:
Everytime I try to apply this I get "assert failed: apply_patch_check("/system/app/SystemUI.apk", "<insert some hash>", "<insert different hash>")"
I am running CWM v6.0.2.5, and I am running the stock Verizon ROM with a few mods applied.
Click to expand...
Click to collapse
I am running TWRP and getting an error message as well:
assert failed: getprop("ro.product.device") == "getprop("ro.build.product") == "t0ltevzw"
E: error in /sdcard/safe_update.zip
(Status 7)
Error flashing zip '/sdcard/safe_update.zip'
cphastings said:
I am running TWRP and getting an error message as well:
assert failed: getprop("ro.product.device") == "getprop("ro.build.product") == "t0ltevzw"
E: error in /sdcard/safe_update.zip
(Status 7)
Error flashing zip '/sdcard/safe_update.zip'
Click to expand...
Click to collapse
Old versions of twrp have broken asserts. You will need to update twrp to the latest version.
Related
WARNING... Proceed at ur own risk... this will break root...
Okay... so i have gotten enough complaints about me having this being unfair and i guess i was trying to be the "overly protective mother" of the slide community... So i have decided to release this and let u guys run wild with it... That should end discussion on whether my initial choice was right... I do this with a GIANT DISCLAIMER: THIS WILL IN FACT BREAK YOUR ROOT!! I am in no way responsible for anything u do with this, what happens to ur device or if ur girlfriend breaks up with u ect... So with that said... here u guys go... have fun with it and those who do flash it post some noticed changes/results.... CR
Instructions: DL the package, unzip the "nothing" folder... rename "OTAPkg.zip" to update.zip and put it on the root of ur SD card... apply this update in stock recovery, reboot, done...
OTAPkg
and i just got my slide rooted 10 mins ago lol !! do u know if this makes it easier to read adb in recovery?
I would NOT flash this if i were u... it will kill root and contains an untested recovery.... If u want the latest and greatest, grab the radio update from this in my other thread.... CR
dcowboys2184 said:
and i just got my slide rooted 10 mins ago lol !! do u know if this makes it easier to read adb in recovery?
Click to expand...
Click to collapse
Dude...this BREAKS YOUR ROOT. That means once you do it, not only are you unrooted, you can't reroot as of yet. So no, it doesn't make it easier to read adb in recovery.
dcowboys2184 said:
and i just got my slide rooted 10 mins ago lol !! do u know if this makes it easier to read adb in recovery?
Click to expand...
Click to collapse
no it does not. it was just stated that it breaks your root. it puts a new recovery that patches the current way to root!
as stated to you before, i'm not applying this. however i was curious to something and had a question.
you say to rename to "update.zip" and place on root of sd. i already have a file named such in that location (i'm assuming it's clockwork). would i place the ota there for the time being since it is only needed to boot to stock recovery? and then when done, replace clockwork update.zip?
also, poking around in the files, i noticed a new or updated mytouch music file. it was the only one that stood out to me, as i know nothing about the other files lol.
new radio it is !!!! hey go easy i don't ask much on here cause i have common sense just one of those maybe questions !! lol !!!
poetik517 said:
as stated to you before, i'm not applying this. however i was curious to something and had a question.
you say to rename to "update.zip" and place on root of sd. i already have a file named such in that location (i'm assuming it's clockwork). would i place the ota there for the time being since it is only needed to boot to stock recovery? and then when done, replace clockwork update.zip?
also, poking around in the files, i noticed a new or updated mytouch music file. it was the only one that stood out to me, as i know nothing about the other files lol.
Click to expand...
Click to collapse
yes, if ur rooted, which i know u are , then the update thats on the root of ur SD is CW Mod... IF u were to flash this, just back up ur update.zip from ur card and put it in a folder, then put this OTA on the card in its place and apply accordingly... CR
PS: Dont do it lol...
Am I the only one waiting to see how long it takes for someone to "HELLLLLP I lost root!" in here? lol
i tried to install but it says assert failed E:Error i /sdcard/update.zip (Status 7) install aborted
Removed, thought I was in the thread about the new radio. Do NOT apply this if you're rooted.
Whoareyou said:
i tried to install but it says assert failed E:Error i /sdcard/update.zip (Status 7) install aborted
Click to expand...
Click to collapse
Rename it to update without the .zip. It should work then.
its not update.zip.zip its just update.zip also i dont hve clockworkmod i un rooted also im on Champion build,... will that effect anything
migueltherocker said:
Flash it from ClockworkMod recovery, named the way it was when you downloaded, don't rename it to update.zip
Then in ClockworkMod, press install zip from sd card, go to the radio update, select it, click yes, and wait a few seconds. It will tell you to reboot to finish installation. Press the back button, select reboot, and it will finish installing. Give it 2-3 minutes to finish installing.
Click to expand...
Click to collapse
that would be the method to flash the radio update... if ur trying to flash this full one the process will work but ur gonna lose root
Whoareyou said:
its not update.zip.zip its just update.zip also i dont hve clockworkmod i un rooted
Click to expand...
Click to collapse
Then yes, the person above us is right. update.zip, from stock recovery just select apply update.zip. It should work, but I can't really test it out for you since I'm rooted.
I ran the update.zip it worked 100%
i cant flash this so i tried to get into clockwork but the root method doset work for some reason
Its a patch update... ur build cant be the champion because it patches UP from 1.27.531 to 1.35.531.... ur current build is 1.18.531.... u need to update to the release software then apply this...
ChiefzReloaded said:
Its a patch update... ur build cant be the champion because it patches UP from 1.27.531 to 1.35.531.... ur current build is 1.18.531.... u need to update to the release software then apply this...
Click to expand...
Click to collapse
and where do i get this
if you want to reroot after flashing this cant you just reflash the ESPRIMG.zip from hboot and then redo the root process?
Hey all,
apologize in advance if this was asked before. i have performed a search and could not locate a definite answer.
i have SG3 ATT1747ucalem rooted using the guide on this forum.
since 2 days ago i have a notification for an OTA from ATT.
i have read the thread here and from users instructions installed voodoo OTA keeper.
i then tried to perform the OTA,
it keep going into recovery and then fail on "e: signature verification failed"
i have tried to temp unroot the device and try again - fail.
tried to toggle the verification off and apply the OTA - fail.
my question is this:
is there any way (or a thread to read) where there are instructions on how to apply the OTA update without loosing your root?
please let me know, thank you.
m.a.s.e said:
Hey all,
apologize in advance if this was asked before. i have performed a search and could not locate a definite answer.
i have SG3 ATT1747ucalem rooted using the guide on this forum.
since 2 days ago i have a notification for an OTA from ATT.
i have read the thread here and from users instructions installed voodoo OTA keeper.
i then tried to perform the OTA,
it keep going into recovery and then fail on "e: signature verification failed"
i have tried to temp unroot the device and try again - fail.
tried to toggle the verification off and apply the OTA - fail.
my question is this:
is there any way (or a thread to read) where there are instructions on how to apply the OTA update without loosing your root?
please let me know, thank you.
Click to expand...
Click to collapse
did you install clockworkmod recovery?
mrRobinson said:
did you install clockworkmod recovery?
Click to expand...
Click to collapse
Yes Sir,
i do have it installed.
??????????
So if we didn't move to another rom and just rooted is it ok to do the update.
OK tried it didn't work because of Clockwork
m.a.s.e said:
Yes Sir,
i do have it installed.
Click to expand...
Click to collapse
you need stock recovery to do it. you can either reflash root66 to get stock recovery back, use voodoo ota root keeper and do the ota update. or i think someone make the update into a cwm flashable zip and you can just flash that in cwm.
rgtorres09 said:
So if we didn't move to another rom and just rooted is it ok to do the update.
OK tried it didn't work because of Clockwork
Click to expand...
Click to collapse
yea you need stock recovery. I forget if it was att or verizon (all these forums jumble in my head) but someone made the update into a cwm flashable zip. its not hard to do if you can find that.
mrRobinson said:
you need stock recovery to do it. you can either reflash root66 to get stock recovery back, use voodoo ota root keeper and do the ota update. or i think someone make the update into a cwm flashable zip and you can just flash that in cwm.
yea you need stock recovery. I forget if it was att or verizon (all these forums jumble in my head) but someone made the update into a cwm flashable zip. its not hard to do if you can find that.
Click to expand...
Click to collapse
thank you for your reply. i think its best if i will wait for a CMW update version. hope soneone will do it fast enough thank you,
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
fa7592 said:
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I appreciate the quick response and the help.
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
would I just have to reflash the kernel I'm on now if I were to update that way?
Sent from my SAMSUNG-SGH-I747 using xda premium
jrbaker624 said:
would I just have to reflash the kernel I'm on now if I were to update that way?
Click to expand...
Click to collapse
No. There's a zip file there with the OTA but with the bootloader and kernel updates removed. You can flash that to keep your kernel. There's another zip file there with just the bootloader if you want to update that, too. Just flash both (No Bootloader No Kernel, the Bootloader).
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
UPDATE:
okay so I followed the steps in the thread you provided, and when I go to flash the update zip in recovery mode, i get an error and it aborts the installation. Heres the error:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
I am also getting same error I was on team epics recovery then saw it wouldn't work for that recovery so I flashed a new recovery and still get the same error.
Tried flashing the no boot loader zip. And the no boot loader and no kernel zip
Sent from my SAMSUNG-SGH-I747 using xda premium
fa7592 said:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
Click to expand...
Click to collapse
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
fa7592 said:
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
Click to expand...
Click to collapse
Download OTA Rootkeeper from the play store, save root, then install the OTA. Reboot and OTA rootkeeper restore root.
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded that one instead of the third one you had linked all together and it worked. Thank you
Sent from my SAMSUNG-SGH-I747 using xda premium
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
fa7592 said:
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
Click to expand...
Click to collapse
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
drothenberger said:
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
Click to expand...
Click to collapse
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
fa7592 said:
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
Click to expand...
Click to collapse
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
drothenberger said:
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
Click to expand...
Click to collapse
Oh okay. In that case I'll go ahead and put in that custom ROM and report back when everything is done. Again, thanks for the help and patience.
Okay, so I have applied the ROM and everything is good! Well for the most part. At times when there isn't a WiFi signal available and it has to use mobile data, the 4G LTE doesn't work. It will connect to HSPA or 3G. And it happens in areas I know has 4G LTE available. But other than that everything seems to be working good. Just thought I'd share in case anyone was thinking of using the AOKP ROM.
I did the root update (flashed in TWRP) to:
HTC6435LVW_2.04.605.2-1.15.605.2
BUT...now Verizon is telling me I need to update OTA to:
HTC6435LVW_2.04.605.2-1.15.605.4
...Is there a .4 version rooted somewhere?
Also, the .2 version is causing my screen to flicker every 20 seconds or so for some reason.
How about this: Are there just instructions somewhere telling me how to lock the phone so I can do the stupid OTA update...and then re-root? I've seen like partial instructions but not sure the best method.
Thanks.
Thanks.
Wrong section buddy
commandlinekid said:
I did the root update (flashed in TWRP) to:
HTC6435LVW_2.04.605.2-1.15.605.2
BUT...now Verizon is telling me I need to update OTA to:
HTC6435LVW_2.04.605.2-1.15.605.4
...Is there a .4 version rooted somewhere?
Also, the .2 version is causing my screen to flicker every 20 seconds or so for some reason.
How about this: Are there just instructions somewhere telling me how to lock the phone so I can do the stupid OTA update...and then re-root? I've seen like partial instructions but not sure the best method.
Thanks.
Thanks.
Click to expand...
Click to collapse
as he said this should go in Q&A Sections, but to answer your question. The flickering is becuase you did not flash the kernel to go a long with 2.04.
Also what do you mean by you flashed 2.04 in twrp? can you give me a link to what you flashed?
Woops sorry. Too bad I can't move it or I would.
From my phone: the kernel from Settings>About>Software Information>More is:
---------------------------------------
Kernel version
3.4.10-g4d47dce
[email protected] #1
SMP PREEMPT
Build number
2.04.605.2.CL147796 release-keys
/---------------------------------------
Also note: The pop-up that still keeps popping up on my phone from StupidVerizon that it wants to upgrade to is:
HTC6435LVW_2.04.605.2-1.15.605.4
MustafaHadaKing said:
as he said this should go in Q&A Sections, but to answer your question. The flickering is becuase you did not flash the kernel to go a long with 2.04.
Also what do you mean by you flashed 2.04 in twrp? can you give me a link to what you flashed?
Click to expand...
Click to collapse
I flashed this file (put file on sdcard, boot into TWRP, installed, and rebooted):
http://forum.xda-developers.com/showthread.php?p=38015322
utkaar099 said:
Wrong section buddy
Click to expand...
Click to collapse
commandlinekid said:
I flashed this file (put file on sdcard, boot into TWRP, installed, and rebooted):
http://forum.xda-developers.com/showthread.php?p=38015322
Click to expand...
Click to collapse
#1 that is called a custom rom.
#2 do not take the .4 ota
#3 to fix your flickering issue go into adb with your phone connected with usb debugging on and type
download the rom on your computer and extract the boot.img out. place it in a folder in your computer called android
Adb reboot bootloader
then type
fastboot flash boot C:\android\boot.img
then your done..
MustafaHadaKing said:
#1 that is called a custom rom.
#2 do not take the .4 ota
#3 to fix your flickering issue go into adb with your phone connected with usb debugging on and type
download the rom on your computer and extract the boot.img out. place it in a folder in your computer called android
Adb reboot bootloader
then type
fastboot flash boot C:\android\boot.img
then your done..
Click to expand...
Click to collapse
So...Are you saying to do "something" with the file I already flashed?
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
.......
yes.... something as in take the boot.img out of the file...
https://www.youtube.com/watch?v=wwleOote5M0
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
What he is saying is that the file you downloaded is called a "rom" and that you are supposed to extract the boot.img from the .zip, and flash it using the procedure he told you
Does this update the radio too? I heard that was updated.
Also, what about the .4 version....This is .2. Do I need .4?
MustafaHadaKing said:
.......
yes.... something as in take the boot.img out of the file...
https://www.youtube.com/watch?v=wwleOote5M0
Click to expand...
Click to collapse
commandlinekid said:
Does this update the radio too? I heard that was updated.
Also, what about the .4 version....This is .2. Do I need .4?
Click to expand...
Click to collapse
You don't need .4, and from the thread you linked it even says:
This does not have new radio or firmware.
Click to expand...
Click to collapse
I read somewhere else there was indeed a radio upgrade.
So if you had a DNA, would you be doing what I'm doing here? Or is there a better way?
My goal: Get the latest software and firmware that VZ has.
utkaar099 said:
You don't need .4, and from the thread you linked it even says:
Click to expand...
Click to collapse
Seems to have worked! Thanks.
Can you tell me please why?
What I ended up doing:
1.) Booting to TWRP and flashing the .zip file. Then I noticed the flickering, but everything seemed to work fine.
2.) Then I posted to the forum here, and you gave me those instructions.
3.) Then I tried them and updated just the boot.img file as you said. ...And it seems to be working.
commandlinekid said:
So...Are you saying to do "something" with the file I already flashed?
Click to expand...
Click to collapse
It worksbecause you flashed the update in recovery and flashedthe corresponding kernel and modules.
So are you saying that if you flash the update, that it won't "do the kernel part"? And the only way to do the kernel upgrade is to use the method described herein?
Did I do the process correctly then? Meaning, in the future, is this how it's done?
Thanks.
orangechoochoo said:
It worksbecause you flashed the update in recovery and flashedthe corresponding kernel and modules.
Click to expand...
Click to collapse
What you first flashed was the rom someone created out of the update. Flashing it does not flash the kernel (boot.img) and probably not the modules either. Some developers have been incorporating the kernel and modules into the rom, but in your case it didn't work. You should also flash the new radio, that was not flashed when you flashed the rom.
If you accept the OTA via the normal process it will do everything itself.
I can't accept the OTA because it will just boot into TWRP and sit there.
Did you see the radio anywhere? I didn't see it.
Also, I think it did flash the modules probably: Because my custom new photosphere-capable camera and new Android keyboard are now gone.
Thanks.
orangechoochoo said:
What you first flashed was the rom someone created out of the update. Flashing it does not flash the kernel (boot.img) and probably not the modules either. Some developers have been incorporating the kernel and modules into the rom, but in your case it didn't work. You should also flash the new radio, that was not flashed when you flashed the rom.
If you accept the OTA via the normal process it will do everything itself.
Click to expand...
Click to collapse
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is also available.
NOTE: if you flash the deodexed version and have problems with root, flash UPDATE-SuperSU-v2.02.zip from here. I don't anticipate any root problems, but just in case, this will fix it.
100% stock: STOCK-4.4.2-P5200(fixed).zip
Deodexed + rooted: STOCK-DEODEXED-ROOTED-4.4.2-P5200(fixed).zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
Very good work done by you! Yesterday I spent hours to unzip the file but unsuccessfully. I will try it right now! Thanks a lot!
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
edsoedso said:
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
Click to expand...
Click to collapse
I've got the same problem.
Hold on, I'm working on it
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Restl3ss said:
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Click to expand...
Click to collapse
Do not worry, I installed stock 4.4.2 using odin, than TWRP and superuser. It looks great! Please work on 4.4.2 Pimpdroid and let us known the results. Regards!
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
just uploaded a deodexed + rooted build. If you have any troubles with root flash SuperSU from the link in OP.
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I always do a factory reset, format data, and full wipe with any ROM Can you move your files to your PC via USB cable?
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I flashed without wiping and had big problems. You should really do a full wipe.
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
I just saw your note. I am downloading both versions, flash them and let you know.
i have downloaded both versions but instal failed
any way does any one know which site i can download the MD5 of the software without corruption ?
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
It seems that battery is draining faster than 4.2.2. Does anybody note it? Any solution? Thank you!
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
jamalau said:
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
Click to expand...
Click to collapse
hey man you need to wipe system, data,cache and dalvik-cache
then flash the zip and it should work
edsoedso said:
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
Click to expand...
Click to collapse
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
quitschibu84 said:
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
Click to expand...
Click to collapse
Can you post the link for the Philz 5200 recovery?
thks