heres my boggle now
when the touchpad searches for the update it finds it and says i should install
when i do that it reboots and comes up saying update failed, any idea why this is
happening......... id rather not doctor it
EDIT: i have cm7 installed with moboot
I had the same issue. Are you running an overclocked kernel? I tried to OTA update 3 times and failed. I then removed my kernel (uberkernel) in preware and it done the OTa no probs.
Remember u will loose you moboot. so you need to dump the moboot 303 into a cminstall folder and rerun ACMEInstaller
Related
I downloaded 1.83 signed and flashed it to my atrix. when it rebooted it says my system is running 1.83 but it still says its trying to download the update and it cant because it is not available at the time. Just curious if i should proceed with the root or if i need to wait untill the download is available again
hmm same thing happened to me, and it wouldnt go away... I than flashed to 1.2.6 and connected my phone to teh comp than updated with motorola software updater to 1.8.3 and its fixed now
I tried installing CM7 before, and screwed up the recovery but managed to fix it using NVflash. I then updated to 1.1 3588 or whatever, then flashed CM7, worked fine.
Saw Vegan ROM so I wanted to try it, and flashed it. I then wanted to check out the new market but the Market kept Force closing. So I tried using CWM to restore the previous Vegan rom but I got a boot loop.
So I nvflashed and tried over from the very beginning but now I can't even get the stock firmware to load. And now I can't even connect in APX mode.
NV Flash says USB device not found.
What do I do...
barqers said:
I tried installing CM7 before, and screwed up the recovery but managed to fix it using NVflash. I then updated to 1.1 3588 or whatever, then flashed CM7, worked fine.
Saw Vegan ROM so I wanted to try it, and flashed it. I then wanted to check out the new market but the Market kept Force closing. So I tried using CWM to restore the previous Vegan rom but I got a boot loop.
So I nvflashed and tried over from the very beginning but now I can't even get the stock firmware to load. And now I can't even connect in APX mode.
NV Flash says USB device not found.
What do I do...
Click to expand...
Click to collapse
So, you can get ot APX mode on the Gtablet, right? You might need to reinstall the drivers on your PC. This happened to me before. Try reinstalling the drivers and see if it detects it.
Okay I'll try that, thank you!
I don't think I'm going to attempt getting the newer market if I manage to fix this lmao
Update: I got stock firmware loaded and it turns on now thank god. But when I go to update the tablet to bootloader 1.1 3588, it downloads then reboots, but when it reboots it just shows an android guy with an exclamation mark in a triangle.
Anyone know what this means?
Edit:: Apparently you need an SDcard inserted. Maybe that was my issue this entire time :S
I'm stuck in a boot loop at the Vegan-Tab GingerEdition screen. I think I'll just leave it for a while? It's been playing the same animation for the past couple minutes.
Or is there something wrong with my installation?
Okay last update, finally fixed the tablet.
For anyone else having the same issues here's what I did to fix it.
I put in an SDCARD so that I could fix my nvflash of stock boot loop error. Finally loaded that ROM, rebooted and got bootloader 1.1 and moved vegan zip to my sdcard. I rebooted, installed vegan ROM, then as I was restarting my tablet I removed my sdcard and it works perfectly.
Of course I tried a bunch of random stuff in between, but I think that's what did it for me.
Thanks for your help TJ
Okay so I wanted to try Brilliant Corners 1.3 ROM so I decided to flash back to stock TNT, update to 1.1 3588 then flash 1.2.
But when I flashed stock TNT it now gets stuck in a bootloop and I have no access to boot into recovery. Just shows a triangle with an exclamation mark. I tried with and without a memory card inserted. Anyone got any clues what I should try flashing now?
Edit: reflashing CWM finally worked. Repartitioned the SDcard now trying to reflash stock TNT
It's curious to me why sometimes I have to flash 3 or 4 times before it will work?
Okay, here's the story.
I rooted my phone, turned S-ON, and installed Cyanogen 7 RC-1. So far so good.
Next I threw on ROM Manager, and got the premium version. I updated CWR to 5.0.2.0. And then went to play.
Well, first thing I noticed was ROM Manager kept erroring out when it rebooted into recovery. The error report is something about being "unable to locate dev/tty0". That was when I noticed something.
In ROM Manager, it says Clockwork is updated to 5.0.2.0
But in Recovery Mode it says 2.5.1.2
So far, I've tried "Erase Recovery", flashing to 3.0.0.8 and seeing if that worked (it didnt'). Then i tried going back up to 5.0.2.0. That didn't work either.
I tried a manual instal of 5.0.2.0 and the system didn't even recognize the file, so I probably did something wrong there.
I'm just lost. Can anyone help me figure out what I'm doing wrong? I just want to flash some ROMs with up to date soft-/firm-ware.
new version is buggy
i had an update for my clockwork mod when i tried to download a rom so installed the updated clockwork but in the end i found the new version 5 to be very buggy but if you want to try just try installing another rom (do a nandroid backup first) and it should install the new recovery but in my oppinion i wouldnt bother upgrading why update something that works thats the common saying
Well, in this case, I'm trying to upgrade from Cyanogen (which I've backed up), to Synergy's GingerSense RS1 for the Droid Incredible. However, while it flashes the ROM, it hangs on the boot up screen when rebooting, so I have to go back to Cyanogen. What got this whole thing started was figuring out what I had to do to get that working.
I'm on HBOOT 079, CWR 2.5.1.2, and none of ROM Managers automated features work because of the "Can't located /dev/tty0" function. The only advice I could find online for that was that 2.5.x is too old, and I need at least 3.0.0.8 to load some of these ROMs.
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
shadowfyre26 said:
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
Click to expand...
Click to collapse
You did say you "turned S-ON" but really you just, as you said, didn't have S-OFF. So I'm guessing your problem was solved when you got S-OFF and tried again right?
Yup, I just fixed the S-ON issue into S-OFF, and lo and behold it worked.
*looks around sheepishly* Let us never speak of this again.
I have 3.0.0 on it, as it wouldn't update the first couple of days I had it. So, I installed CM7 Alpha 3.5, moboot, etc. Will updating webOS require anything special before/after? Will I have to reinstall android afterwards?
Sent from my Legendary RC 2.2 infused device.
Doing a webOS update will butcher your /boot partition, but not the actual android install.
After the update, you will need to run the ACMEInstaller again just to reload moboot onto the device.
Ok, just moboot. Thanks. Guess I'll wait till tomorrow when I have my dads laptop.
I have an XT912 flashed to PagePlus. I want to update it to .165 but it's not letting me.
First, the OTA nags stopped the second I connected to PP so I found an update zip to manually flash it over at Droidrazr.com. From Howardforums, people said they were able to do the OTA by reverting a setting in the buildprop that was changed during the flashing and temp unrooted with Voodoo. Then just put everything back when it was done.
I went into recovery and attempted to flash it. There were errors about Acousticwarning.apk. After some reading, it seems there was a conflict that the update couldn't find the bloatware that I removed. One thread said to copy/paste the apks from the system/app file in the stock rom elsewhere to my phone (I took them from the stock rom in Matt's utility). Didn't work. So, I used Matt's utility to flash stock (without data wipe) and tried again. No dice. The phone started downloading the OTA and then aborted the install. Twice. During all of this, I had lost the settings for the PP flash. I reflashed for PP and got everything working, but I still can't get the .165 update to install.
Any ideas?