So im rooted and running a stock rom i havent unlocked my boot loader but i cant update from mr1 my phone downloads the update but when it goes to reboot and apply it the status bar goes about have way and reboots and when it restarts is says update failed anyone have a solution
Sent from my MB855 using XDA Premium App
I have the same issue...
Sent from my MB855 using XDA Premium App
I was having the same issue. I was on stock and rooted. I had removed a ton of bloat from /system/app. I had to put all of my files I removed back into /system/app and voila the update went through.
Ughhhhh ......forget that i guess im waiting for a flashable zip thats to much work
Sent from my MB855 using XDA Premium App
smoothone said:
I was having the same issue. I was on stock and rooted. I had removed a ton of bloat from /system/app. I had to put all of my files I removed back into /system/app and voila the update went through.
Click to expand...
Click to collapse
I had renamed sprint_worldwide, sprint wallet and the stock news app to ".bak". When I made them ".apk" again the OTA went through.
I am rooted with a locked bootloader with all the sprint bloatware removed and the updated went flawless for me......Still have not made a call yet to see if the "muted call" issue is resolved. But I just wanted to speak up and let others know to at least try to run the update, it could work.
I am in the same situation. I am rooted with a locked boot loader and using the stock rom and cannot apply the ota update. Here is what I gather from the recovery log:
Finding update package...
I:Update location: /cache/
Blur_Version.45.2.1.MB855.Sprint.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1469 bytes; signature 1446 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing Etna updater extensions
installing NV updater extensions
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed:
apply_patch_check("/system/build.prop", "8250ac16a9fab966853d763e7e02db69fd1499df", "85bbed34360609e4bbf50f01b6f0519c02fccfcc")
assert failed: apply_patch_check("/system/build.prop",
"8250ac16a9fab966853d763e7e02db69fd1499df", "85bbed34360609e4bbf50f01b6f0519c02fccfcc")
E:Error in /cache/Blur_Version.45.2.1.MB855.Sprint.en.US.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I could be wrong, but it seems like there is something wrong with either my build.prop or the patch itself.
Im not to sure but i think this may be the ota ..........has anyone tried and know ............http://forum.xda-developers.com/showthread.php?t=1202666
Final build courtesy of the fine folks at MOTOROLA 8/11/11
Sent from my MB855 using XDA Premium App
ajoerivera said:
Im not to sure but i think this may be the ota ..........has anyone tried and know ............http://forum.xda-developers.com/showthread.php?t=1202666
Final build courtesy of the fine folks at MOTOROLA 8/11/11
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
NextEQ said:
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
Click to expand...
Click to collapse
Make sure you installed the drivers i had the same issue worked for me
Sent from my MB855 using xda premium
I've tried the official OTA 3 times with no success. Anyone have any suggestions as to what might correct the issue?
Photon is rooted but otherwise stock w/alternate launcher. Battery level is around 65. Have only deleted one stock app but can't remember what it was and don't have a backup of it.
I would rather not do the manual *leaked* update. Seems like too much work with having to actually re-activate.
NextEQ said:
For me, the problem with the manual update is RSD lite will not show my device when I plug it in. I have tried 2 different computers and multiple USB ports. Both computers install the drivers but that’s as far as it will go.
Click to expand...
Click to collapse
I had the same issue...you have to go into device manager and click on android usb devices and manually reinstall the driver.....atleast thats how I ended up getting my rsd working and connecting to my photon
unsane said:
I had the same issue...you have to go into device manager and click on android usb devices and manually reinstall the driver.....atleast thats how I ended up getting my rsd working and connecting to my photon
Click to expand...
Click to collapse
Thanks, I will try that next time. I ended up trying my luck to manually update the full SBF on my wife’s netbook while she was away. The stupid thing worked with no problems! Nearly pulled my hair out trying to get my main PC to recognize the phone.
OTA update error problem fixed
sigabrt said:
I had renamed sprint_worldwide, sprint wallet and the stock news app to ".bak". When I made them ".apk" again the OTA went through.
Click to expand...
Click to collapse
I tried installing the OTA update 3 or 4 times and received the same error each time. After reading this I realized that I had renamed 4 apps (news.widget, swype, vtt-sprint, and weatherwidget) to .bak. I went in and changed them back to .apk and the OTA went through on the first try. Not sure what would have happened if the apk's were deleted, but I'm guessing just about any apk that gets modified in the system folder will throw off the OTA update. Unless of course it was entirely coincidence that on my 5th try the OTA suddenly started working (did all of these within about an hour).
Related
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
im guessing no ones had this problem before?
Re: E: cant symlink
I had this problem on clock work recovery and wasn't able to fix it had to get a me new phone
-------------------------------------
Sent via the XDA Tapatalk App
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
bigslanki said:
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
Click to expand...
Click to collapse
Yep that's way happened with my first Eris. ... I'm on BACK TO Droid now as you can see. Going to limit my flashing for now on.
-------------------------------------
Sent via the XDA Tapatalk App
bigslanki said:
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
Click to expand...
Click to collapse
You over reacted
jetmclean said:
You over reacted
Click to expand...
Click to collapse
You bumped an old thread
jetmclean said:
You over reacted
Click to expand...
Click to collapse
how so? stating my experience and providing details for other users?
Old news......
EDIT: New problem I am using this root method:http://forum.xda-developers.com/showthread.php?t=1046855 However, no matter how many times I attempt to perform step 9, it keeps giving me the exclamation point. Any ideas?
The only way I could get root was to use super one click. Version 1.7 worked for me on two fascinates.
Sent from my SCH-I500 using XDA App
Were those two running 2.2.1? ED01?
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
spartan.062 said:
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Looks like I wont figure it out today (too tired to think straight)
Click to expand...
Click to collapse
Sometimes I download multiple files at one time. For instance, to get the ED01 modem I downloaded the 2 update.zip's from adrynalyne's thread. The second update.zip had a "(2)" at the end of it. Erase that. On your PC the files needs to only say "update", not "update.zip". The phone adds a ".zip" to each file. Make sure you are doing that.
Sent from a depraved XDA junkie and flashaholic
superchunkwii said:
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Click to expand...
Click to collapse
This isn't true. You are thinking about installing CWM recovery, that gets overwritten with the stock recovery by the stock kernels. I've used this method on many of the stock builds including ED01: http://forum.androidcentral.com/ver...d-post-1-before-posting-forum.html#post699944
I know of a VERY simple root method. If you want to know it, hit me back. It seems to me that no one is using it but it is posted in these forums.
Sent from a depraved XDA junkie and flashaholic
What method is that kidserious?
spartan.062 said:
Ok... Every time that I attempt the adb root, I get this in the command prompt:
'adb' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Are you on stock 2.2?
spartan.062 said:
What method is that kidserious?
Click to expand...
Click to collapse
Click on this and then once you are there download linked file. Then place it on your SD card. Let me know when you have done that.
http://forum.xda-developers.com/showthread.php?t=1045048
Yep. And I am still somewhat confused when it comes to flashing a kernel. And I already have the su file, however, when I try to apply the update to get to CWM, It won't take the update. I'll try adding .zip to the end of the name.
spartan.062 said:
Yep. And what was that method you were mentioning?
Click to expand...
Click to collapse
Yes, but I see you have had problems with this method already. Are you able to get odin properly set up on your PC? I mean have you been able to flash anything via odin? Did you see my link in my above post? And don't worry about a kernel just yet. Lets get this taken care of first.
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
spartan.062 said:
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
Click to expand...
Click to collapse
Did you see a Green "Pass" when it finished in odin? And when you put the battery back in were you unplugged first? You may know this but you cannot allow the phone to boot normally before booting into recovery. Try using this recovery instead: http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Flash that the same way in Odin?
spartan.062 said:
Flash that the same way in Odin?
Click to expand...
Click to collapse
Yes, but boot into recovery FIRST before the phone turns on normally. Not trying to sound condescending but do you understand what I am saying about booting into recovery first?
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
spartan.062 said:
Yeah I understand.
Click to expand...
Click to collapse
The way it always works for me is I don't even boot into the blue recovery, it boots straight into red. Let me know what happens.
spartan.062 said:
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
Click to expand...
Click to collapse
GOOD! With that menu find the superuser root package from nemesis2all on your SD card and install it. Let me know what happens.
followed the root step by step. I have S-off, and SU installed... but when i go to install certain roms, I get this.
--install / sdcard ...
finding update package..
opening update package...
E:cant open /tmp/sideload/package.zip
(bad)
not sure whats up with that, someone said its cause I dont have SU, but I followed the root process exact, so what else does this mean? and how can I get other these roms to work -
this rom is Viper 1.2
Did you flash a su zip?
Sent from my PG86100 using XDA Premium App
Try the latest twrp 1.0.2 I had the same problem as you, and I redid the recovery tonight, and the problem is gone, for me, at least on the one rom I flashed tonight. I tried cwm yesterday and got an error with that recovery too, but it was a different error, but I am sure it meant the same thing.
Another way around it is to just do a reboot. Your system wont be there so reboot into bootloader and go back into recovery. This worked yesterday for me....
yes neopolotin75 , I did flash the SU file, signed and unsigned....
and yes B-Mod, got 1.0.2 installed, and also again did the signed and unsigned, wiped everything, formatted everything, and still no go....
not sure what the heck. maybe take my phone back to stock, and start over...
thanks anyhow...
disconnect the cable from the phone.....
FIGURED IT OUT - i got my file from mega upload, 2 times..... along with some of the other roms, and they always gave that error...
I now got viper 1.2 from hostfile. it is installing, after comparing the files, mega upload said it was good, but was missing about 2 megs of data.
hope this will help anyone else who gets this error, just try different sites for your roms as they seem to be getting hit hard with lots of downloads.
I had the same issue. If you re-apply the ZIP a second time it works without an error message.
goodluck69 said:
I had the same issue. If you re-apply the ZIP a second time it works without an error message.
Click to expand...
Click to collapse
Sometimes. If it's a status 0, 1, or 2 that is usually accurate. Just reboot back into recovery and it works. But if it says "bad", the .zip is corrupt and it needs to be redownloaded.
Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!
Sorry for my poor English!
All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...
I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o
Sent from my Sony Tablet S using xda premium
mikajo said:
All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...
Click to expand...
Click to collapse
Thanks, but reset so many times.
andyabc said:
I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.
Topery Chiang said:
But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.
Click to expand...
Click to collapse
What do you mean 'Stopped'?
It is stuck on the Sony screen?
Sent from my Sony Tablet S using xda premium
andyabc said:
What do you mean 'Stopped'?
It is stuck on the Sony screen?
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Topery Chiang said:
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Click to expand...
Click to collapse
Can you access the recovery partition?
Sent from my Sony Tablet S using xda premium
Topery Chiang said:
Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!
Click to expand...
Click to collapse
OK Do you have adb debugging enabled??
DO NOT FACTORY RESET!!!!!
Try to flash a rom and use adb pull /tmp/recovery.log
Then post here
Stifilz
andyabc said:
Can you access the recovery partition?
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
Yes.
I learned that this is not just a Sony Tablet S problem but can happen on every device.
Furthermore I learned that the Update is not getting the correct device name from the build.prop.
This is very interesting as I can't remember that I would have changed the name of the tablet in the build.prop. However, maybe it's helpful for someone of you
Topery Chiang said:
Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!
Sorry for my poor English!
Click to expand...
Click to collapse
ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:
Code:
adb pull /tmp/recovery.log
attach it here, let me see.
condi said:
ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:
Code:
adb pull /tmp/recovery.log
attach it here, let me see.
Click to expand...
Click to collapse
Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Topery Chiang said:
Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Click to expand...
Click to collapse
similar? so thats not your log?
condi said:
similar? so thats not your log?
Click to expand...
Click to collapse
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Topery Chiang said:
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Click to expand...
Click to collapse
try this fw.
condi said:
try this fw.
Click to expand...
Click to collapse
nbx03_016?
What the region is?
condi said:
try this fw.
Click to expand...
Click to collapse
Like UK version, if the wifi only and wifi+3G can flash mutually without rescue-backdoor?
Topery Chiang said:
nbx03_016?
What the region is?
Click to expand...
Click to collapse
Have a look and see for yourself. Click Update Links in my signature then search for nbx03_016 on that page.
Stifilz
Topery Chiang said:
This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!
Click to expand...
Click to collapse
ok now try to flash this fw, and post results - if error, post recovery.log just after flashing try.
I am currently on software version 3.09.605.2. Verizon just forced downloaded a new firmware update to me. The question I have is: is it safe for me to apply it. I have the TWRP custom recovery installed and used Sunshine to unlock and S Off my max. Will applying this update hose me over in any way?
Update to my post.
I decided to try the update after talking to the folks in the Sunshine support forum (I installed Sunshine last year to unlock and S off ).
I have TWRP installed as a custom recovery and when the OTA tried to apply, I received the following error:
Updating partition details...
...done
Full SELinux support is present
Processing AOSP recovery commands...
Unable to locate zip file '[email protected]}@yBugwGuAtA'.
Installing '[email protected]}@yBugwGuAtA'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file douns
E:Failed to sysMapFile '[email protected]}@yBugwGuAtA'
E:Error installing zip file '[email protected]}@yBugwGuAtA'
Done processing script file
MTP Enabled
I rebooted the phone and everything seems to be working normally, but the OTA obviously did not install. Anyone have a tip as to what I can to to get it to install?
thafrogggg said:
Update to my post.
I decided to try the update after talking to the folks in the Sunshine support forum (I installed Sunshine last year to unlock and S off ).
I have TWRP installed as a custom recovery and when the OTA tried to apply, I received the following error:
Updating partition details...
...done
Full SELinux support is present
Processing AOSP recovery commands...
Unable to locate zip file '[email protected]}@yBugwGuAtA'.
Installing '[email protected]}@yBugwGuAtA'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file douns
E:Failed to sysMapFile '[email protected]}@yBugwGuAtA'
E:Error installing zip file '[email protected]}@yBugwGuAtA'
Done processing script file
MTP Enabled
I rebooted the phone and everything seems to be working normally, but the OTA obviously did not install. Anyone have a tip as to what I can to to get it to install?
Click to expand...
Click to collapse
You'll need to be completely stock in /system and stock recovery.
Ahh ok. that might be more of a pain than it is worth.
thafrogggg said:
Ahh ok. that might be more of a pain than it is worth.
Click to expand...
Click to collapse
I'll flash back to stock and maybe get a more simpler way later this week.
Thanks Flyhalf, I would appreciate that. Also, thanks for sticking around so long on the One Max. It is way cool of you to keep up with this older model phone.
thafrogggg said:
Thanks Flyhalf, I would appreciate that. Also, thanks for sticking around so long on the One Max. It is way cool of you to keep up with this older model phone.
Click to expand...
Click to collapse
Do you still have the OTApkg.zip? Will be located in /cach/fumo
Any idea if this is Verizon pushing a fix for the stagefright exploit?
Tenounce said:
Any idea if this is Verizon pushing a fix for the stagefright exploit?
Click to expand...
Click to collapse
Probably getting ready for an LP release.
Oh Yea, probably. Eh not that big a deal for me then. Been running your beta NuSenSeven since you posted it and other than the few bugs I posted I'm happy with it for daily use.
Flyhalf205 said:
Do you still have the OTApkg.zip? Will be located in /cach/fumo
Click to expand...
Click to collapse
I am looking for it now.
Flyhalf. Sent you a PM about the OTA file.
Flyhalf I have the OTA.. I wanted to update too but will have to sideload it.. I dont know how to repackage to make it an update.zip where can i upload it to?
Brain dead: what do I freeze in titanium to get rid of the ota notification again??
NVM: FOUND IT!
Sent from my Nexus 6 using XDA Free mobile app
markwebb said:
Brain dead: what do I freeze in titanium to get rid of the ota notification again??
NVM: FOUND IT!
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
What did you freeze?
thafrogggg said:
What did you freeze?
Click to expand...
Click to collapse
It didn't work after all. Need to find the right one.
Sent from my Nexus 6 using XDA Free mobile app
My sprint one is annoying me to flash the update. I'm debating on not as I don't have an issue with my one max except a hardware / software bug that plagues all the HTC One Max's on sprint... ( using bluetooth for streaming sounds works fine but if I use it for calls it will freeze my wifi internet connection but using a dinosaur wired headset for calls doesn't kill the wifi on the phone)
I can't remember what to freeze in titanium either to get around the nag screen to update..
Has there been a flashable zip created Yet? I have the update prompt for about two weeks now on Sprint One max
markwebb said:
It didn't work after all. Need to find the right one.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I erased the otapkg.zip in the cache/fumo and renamed otacerts.zip to otacerts.zip.bak in the etc/security
Worked for 3-4 days.
Every few days ill get the pop ups and go back into fumo and erase the otapkg to make the pop up go away.
I don't care so much about apply it, but would like to figure out a way to block the ota pop up
Has anybody made any progress either blocking the update or coming up with an update.zip? I've been on test devices for a few months and am now going back to my personal One max. I turned it on today just to see the dadgum update popping up.