446 replies to this topic

[networkdood]

ok, so, I was on .211 and trying to go to .214 - I kept getting an E:Error in /tmps/sideload/package.zip and some error involving the boot.img image upon verifying the update package. I switched my boot image back to the original logo and now I am getting:
assert failed: mount("ext3", "MTD", "system", "/system") along with the E:Error in /tmps/sideload/package.zip (Status 7) Installation aborted.

Now, since I had been getting similar errors I decided to re-image .211. So, I have the .211 file on my external SD card and I used Matt DroidUtility to 'prepare' my phone to flash the .211 file.
I still have the same errors...anyone have any suggestions?

Thank you.

[trikotret]

Hows everyone battery life on new rom?

Sent from my DROID RAZR using Tapatalk 2

[spid1]

I'm going 1 and 3/4 days and that includes a full day of texting, email, and surfing the internet. Wifi is fast. GPS grabs quickly. Took 2 days to burn in the.214. The key for me was to do a full wipe from moto recovery.

[apquijano]

Huge fan of Matt's work. I successfully installed this via .zip/Recovery method earlier this afternoon and this is how it's been. About to sleep so here's my findings.

- Brightness set to auto
- About half an hour used on calls
- Around forty-five text messages sent
- Sync on all day
- Cellular data set to LTE/CDMA/Evdo
- Wi-Fi on for about six hours
- Watched two episodes of Doctor Who via Netflix
- Watched a couple videos on YouTube
- Moderate use of Facebook and Instagram (checked each for about two minutes at a time, about ten times)
- Moderate amount of Web surfing
- Constantly looking through forums

This is about normal for me, if just a little better. I'm interested to see if a data wipe from recovery would help me.

[Mr. Orange 645]

ok, so, I was on .211 and trying to go to .214 - I kept getting an E:Error in /tmps/sideload/package.zip and some error involving the boot.img image upon verifying the update package. I switched my boot image back to the original logo and now I am getting:
assert failed: mount("ext3", "MTD", "system", "/system") along with the E:Error in /tmps/sideload/package.zip (Status 7) Installation aborted.

Now, since I had been getting similar errors I decided to re-image .211. So, I have the .211 file on my external SD card and I used Matt DroidUtility to 'prepare' my phone to flash the .211 file.
I still have the same errors...anyone have any suggestions?

Thank you.

After using option 2, when you reboot to the stock recovery, do a factory reset and wipe cache.

[networkdood]

After using option 2, when you reboot to the stock recovery, do a factory reset and wipe cache.

Hey, saw you on the chat and yeah I did try that :-(

[networkdood]

Anyway I can transfer a file using fastboot, from my PC to the external memory of my phone? It could be that that the file is bad since the assert always fails.

NM, lol, I can just pull the card out and transfer the file directly...lol

Edited by networkdood, 09 July 2012 - 09:39 PM.

[networkdood]

Anyone have a link to a "GOOD" .211 update file - one that you have personally used - I have 2 and one of them has a sig ver failed while another one gives me the original error I had in the first place. Thanks

[xlightwaverx]

Please Login or Register to see this Hidden Content

Sent from my DROID RAZR using Tapatalk 2

[diesel84]

My battery usage has been greatly improved after updating to .214. I did do a factory reset, System Settings > Privacy > Factory Reset and now my screen is showing 95% battery usage. And yes I have launched applications since powering on my phone.

[networkdood]

Please Login or Register to see this Hidden Content

Sent from my DROID RAZR using Tapatalk 2

Thanks, it seems like every .211 update file I find is bigger than the next.....in terms of KBs.

[ibolski]

Battery life for me seems pretty good, better than 211 and this was just taking the boot image file. I'm going to go back to factory 211 and apply the update via the stock recovery just to be sure, but I'm liking 214.

I did run into one problem that I haven't seen. My 4g network was refusing to work today. The 4g signal indicator was up in my status bar but was grey and would never turn blue. I had to turn the phone off and on to get it to work again. I've never had this problem before with my RAZR before 214. Not sure if that's the reason or ICS Eclipse 1.2RC1. In any case, I do see an improvement in both responsiveness in my phone as well as better battery life.

[cw0725]

i must be losing my mind.. i'm on a leaked version of 211 and keep trying both links. did the utility and still not on the 214. any input would be greatly appreciated.

[phaim]

I did run into one problem that I haven't seen. My 4g network was refusing to work today. The 4g signal indicator was up in my status bar but was grey and would never turn blue. I had to turn the phone off and on to get it to work again. I've never had this problem before with my RAZR before 214. Not sure if that's the reason or ICS Eclipse 1.2RC1. In any case, I do see an improvement in both responsiveness in my phone as well as better battery life.

I actually experienced a similar problem in NYC/Northern NJ. My 4G connection with .214 has been very unreliable the last few days and all the radio trouble I've been having with an inconsistent signal actual seemed to hurt my battery life compared to .211 (Cell Standby has drained a relatively large portion of my battery, around 10% on .214). Maybe if I was in Chicago it would be better (where I found the 4G coverage is excellent) but in the NYC area I'm sticking with .211 which seems to get a better more stable lock on 4G.

[jonwgee]

i must be losing my mind.. i'm on a leaked version of 211 and keep trying both links. did the utility and still not on the 214. any input would be greatly appreciated.

If you used option 2 , the pc utility, your system version will still say .211. Your kernel version should show June 29 . It's it does, you're all good.

Maxx

[orateam]

ok, so, I was on .211 and trying to go to .214 - I kept getting an E:Error in /tmps/sideload/package.zip and some error involving the boot.img image upon verifying the update package. I switched my boot image back to the original logo and now I am getting:
assert failed: mount("ext3", "MTD", "system", "/system") along with the E:Error in /tmps/sideload/package.zip (Status 7) Installation aborted.

Now, since I had been getting similar errors I decided to re-image .211. So, I have the .211 file on my external SD card and I used Matt DroidUtility to 'prepare' my phone to flash the .211 file.
I still have the same errors...anyone have any suggestions?

Thank you.

I got this same issue. I couldn't get past it. Spent 10 hours with the phone and finally gave up. Called Verizon and told them that thier ics upgrade did it. my new Razr comes tomorrow. I will not be doing this upgrade again. I will just root it, install safestrap and use custom roms. Something about this kernal upgrade seems to have locked my phone from getting any standard recovery. It senses that the kernal is not right. I assume only a fastboot of .214 or higher will work.

[cw0725]

Edit <> got it to work all is good.

<P>Jon actually my kernel version says thurs jun 14. if i run the first option and try flash it i get a bunch of errors but then if i try the utility it looks like it runs but doesn't change? and im pretty sure i did it correctly.<BR><BR>

<BR>If you used option 2 , the pc utility, your system version will still say .211. Your kernel version should show June 29 . It's it does, you're all good.<BR><BR>Maxx<BR>

</P>

[fdisker]

I got this same issue. I couldn't get past it. Spent 10 hours with the phone and finally gave up. Called Verizon and told them that thier ics upgrade did it. my new Razr comes tomorrow. I will not be doing this upgrade again. I will just root it, install safestrap and use custom roms. Something about this kernal upgrade seems to have locked my phone from getting any standard recovery. It senses that the kernal is not right. I assume only a fastboot of .214 or higher will work.

Real men call that fraud.

[Arak-Nafein]

I got this same issue. I couldn't get past it. Spent 10 hours with the phone and finally gave up. Called Verizon and told them that thier ics upgrade did it. my new Razr comes tomorrow. I will not be doing this upgrade again. I will just root it, install safestrap and use custom roms. Something about this kernal upgrade seems to have locked my phone from getting any standard recovery. It senses that the kernal is not right. I assume only a fastboot of .214 or higher will work.

Shame on you. That's fraud, and it's also why we can't have nice things. When I break my stuff, and it's my own fault. I man up and pay for them myself.


I understand that a new phone is a lot of money.....but you shouldn't be playing with expensive toys if you can't afford to buy a new one. I'm only saying all of this because Droidrzr.com doesn't not condone fraud.

[orateam]

Shame on you. That's fraud, and it's also why we can't have nice things. When I break my stuff, and it's my own fault. I man up and pay for them myself.


I understand that a new phone is a lot of money.....but you shouldn't be playing with expensive toys if you can't afford to buy a new one. I'm only saying all of this because Droidrzr.com doesn't not condone fraud.

THIS is fraud? So using WiFi tether without paying as most hackers do, is not.? Sideloading paid apps which many do, is not? I can go on and on. I have given the telcos tens of thousands of dollars and many times have barely touched their network. Using my phone for a handful of minutes with wifi data. And they've never given me no discount.

As a side mention. I told the Verizon guy later on after we talked for an hour exactly what I did for proactive reasons and he didn't care. He said all raze moto are under a 1 year warranty and Verizon want to keep me as a customer. He went on to say that once a customer is eligible for an upgrade, they have more leniency. So full disclosure, nothing dishonest on my part. If they are with moto, its on them.