Anyone have the stock/factory recovery for the xt701? I've been trying to apply the latest OTA update (8.6 mb or something like that) for the longest, and I always get the "failed assert". The only thing I figure now is that it does not check out with the open recovery I'm using now.
I was over zealous for my first root flashed the first recovery that would allow it all without the nandroid backup.
I got the same error when tried to udpate my xt701 by using Factory reset.
Actually i got many wired problems when rooted the phone.
Did you finnaly find the way to update successfully from Motorola site?
Thanks,
Evgeny
ya man. Post 10 behind this link sorted me out after looking for a long time.
http://modmymobile.com/forums/545-motorola-motoroi-milestone-tablet/555486-moto-update.html
With this I've been able to apply that update. It's not Froyo, but it's stability.
you might have to sign up but it's a great resource.
Related
Hello there.
i have a nexus one from vodaphone and im sure you all know (ive only just found out) that the ROM on these devices has a problem installing updates to android and does not recieve OTA updates. i believe this is to do with vodaphone actually releasing these?
any who, i used the superoneclick Root application, worked like a charm.
so then i procede to download gingerbread rom but it does teh whole E: verification error.
so i search the internet a little and come across a post with a person with teh same problem, Fantastic i thought! i follow the steops but am cut at my first hurdle as it says i need to revert from teh Vodaphoen Rom to teh original google shipping rom, the problem is that i cant seem to download it, it never works and i dont know why the D/l is incredibly slow and sometimes never connects. this is from Shipped-roms.com
if any1 could assist me in reverting to the original shipping rom i can do teh rest and update to 2.3.3
Thanks for reading.
Horizon.
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
SalsaForte said:
Root your phone, then install rom manager recovery. With this, you will be able to flash any rom you want.
Click to expand...
Click to collapse
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Horizonspace said:
ive installed the rom manager and installed the cyanogen room, how ever im still on 2.2.1 and the OTA wont update it just downloads then nothing happens. any idea?
Click to expand...
Click to collapse
The OTA won't update automatically, you have to manually flash it. OTA will auto-update only from official version and authorized version. Anyway, why don't you flash CM7 RC4?
Okay I've been attempting to update my girlfriend's phone for the last couple of weekends, without any luck. Before I do any modifications, I do a nandroid backup with clockwork recovery (5.0.2.3), when things go to hell and I try to restore, it gives me an "error writing to /system!" (or something like that) message and fails. This is a huge pain in the ass and every time I have to start from scratch and wait for it to spend another hour trying to download the Gingerbread update over 3g. Is there an update.zip I can get online for it? Or some way to force it to download over wifi? Even an unofficial update would be fine, anything to get gingerbread on this bastard with less than two hours between tries.
4.5.608 is available from multiple sources. Go to RootzWiki for example.
notsosupermario said:
Okay I've been attempting to update my girlfriend's phone for the last couple of weekends, without any luck. Before I do any modifications, I do a nandroid backup with clockwork recovery (5.0.2.3), when things go to hell and I try to restore, it gives me an "error writing to /system!" (or something like that) message and fails. This is a huge pain in the ass and every time I have to start from scratch and wait for it to spend another hour trying to download the Gingerbread update over 3g. Is there an update.zip I can get online for it? Or some way to force it to download over wifi? Even an unofficial update would be fine, anything to get gingerbread on this bastard with less than two hours between tries.
Click to expand...
Click to collapse
I've been on the latest update from Motorola for quite some time. Its the 608 update. IT SUCKS! I can't boot into CWR to install a new ROM. Nothing appears to work. I tried a factory reset..I remained on 608. My next step is to do a full wipe. There's no SBF for Gingerbread that I'm aware of. I'm not new to this, I'm rooted and all, but still no cigar. Its quite disappointing.
you have to reroot after 608 update, how did you root,
I have NEVER been able to get CWM to flash a recovery to my D2G. I'd really love for someone to tell me they've been successful doing so.
D2G's bootloader is locked, so CWM can only be used via the logwrapper hook.
For stock firmware, you need Droid 2 Recovery Bootstrap from the Market.
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
name_the_if said:
So after downloading and trying to install the ota ics update my phone is stuck on the moto splash screen. The update was downloaded successfully and the install was going smoothly up until 30% completed i guess. The normal android update screen disappeared and the 'dead' android appeared, the phone then rebooted and was then stuck on the initial moto splash screen. I was running stock 2.3.6 gb before the install. Pretty lost here as to whats going on with my moto paperweight. I have read the 'noob' thread, downloaded rsd lite, moto drivers, and the fxz to go back to 2.3.5. But am hesitant to pull the trigger on anything as I am far from being sure! Any help would be appreciated!
Click to expand...
Click to collapse
You need to grab the ota files from the post alteredlikeness posted in the general section, and put it on your sdcard.
Here:
http://forum.xda-developers.com/showthread.php?t=1930634
Then boot into stock recovery, and hit both vol + and vol - button, then from the menu select apply update from sdcard.
The dead android you saw updated your recovery binary, give this a try... if you get errors, then keep track of them, so you can post then here. That way we can better help.
Thank you Jim. I will give this a try and report back any results.
So I have been relying on my trusty Nokia e71 for the past few days as I have been very busy with work and have had no time to work on my Atrix 2. Finally found some time tonight and have successfully updated my phone! I tried Jim's method to install from the SD card but it repeatedly failed; the phone gave errors pertaining to the signature or security? I honestly cant remember as I have been drinking for a while now. I then tried installing from cache and found success after a looooong install. I'm now enjoying ICS on my Atrix 2 thanks to Jim!
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.