Quick update:
If you have moboot 0.3.5 already installed on your device, this update will NOT break anything Android related.
If you are still on moboot 0.3.3, then it WILL break and need to be reinstalled.
Related
I have been running Vegan 5.1 for a while, but I wanted to try the gingerbread version as well as CM7. I boot into recovery and wipe data/cache/dalvik and install the rom. After everything instals and I reboot it just stays on the viewsonic splash screen.
Any thoughts as to what I am doing wrong?
Did you do this.
After the first boot, and all the setup screens, PROMPTLYreboot the tablet to finish installation.
If your stuck on the birds on boot after flashing any gingerbread rom you must nvflash your tablet using the instructions provided on the dev page. It will fix your partitioning and you wont have further problems moving between froyo and gingerbread roms......unless your on the 1.2 branch of tnt. Then you have to flash back to 3588 or nvflash to stock.
I had the same problem
Jonni Nitro said:
I have been running Vegan 5.1 for a while, but I wanted to try the gingerbread version as well as CM7. I boot into recovery and wipe data/cache/dalvik and install the rom. After everything instals and I reboot it just stays on the viewsonic splash screen.
Any thoughts as to what I am doing wrong?
Click to expand...
Click to collapse
Apparently you can't easily go from different android versions, that VEGAn 5.1 is 2.2, but the GingerEdition is 2.3
So you have to Nvflash, and after that it will work easily
Djapatos said:
Apparently you can't easily go from different android versions, that VEGAn 5.1 is 2.2, but the GingerEdition is 2.3
So you have to Nvflash, and after that it will work easily
Click to expand...
Click to collapse
Not all tablets have this problem. Just some of them
Ok, I will look into the nvflash. Thanks! I have been running CM7 on my Evo and want to see how it would do on the G Tab.
After I installed the CWM application, my GTablet will not go to the CWM menu. For the CWM install, I went to GTablet for Dummies and followed the instructions exactly. I have a Tap UI version 1.1-3588 GTab, and downloaded the 1.1 Branch (3588) from the site, but after downloading the CWM link, it continually boots to the factory OS. I had planned on moving forward with a new OS (possibly VeganTab Gingerbread), but can't get there. I received a suggestion to move forward and install nvflash, but that didn't work either.
Any suggestions would be greatly appreciated. Thanks!
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
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.
So, I already had CM9 Alpha 0 installed at some point.
Few days ago i decided I'd like to try the cornerstone mode. I flashed it with cm9 and that screw up my TP to the point where it constantly would restart after the loading screen. The only place I could get to was CWM recovery (not even team win recovery which I also had installed) and webOS
I figured I'll just reflash back to the CM9 alpha 0 but TP would restart mid flashing.
After that I decided it's time for serious action and wiped the whole thing with webOs Doctor 3.0.5.
That wipe went successfully but now when I run ACMEInstaller2 ( i put cm9 alpha 2 , moboot, gapps, and cwm zips in cminstall folder on TP) to get android back on my TP it takes a while to start installation and once it does TP restarts after literally 3-4 seconds into it.
WebOS still boots fine. I am sort of at a loss here and I'd appreciate any help. Thank you
It looks like the problem might be rooted in the fact that I am unable to flash anything in the CWM recovery.
I used novacom.exe boot mem:// <uImage.ClockwordMod command and that brings up CWM on the TP. When I got there, I decided to see what happens when I try to flash something and attempted flashing CM9 Alpha 2. The process got to the "Installing update" phase and TP restarted again.
What could be preventing it from flashing things?
What I would do, if I were you, is check out this thread: http://forum.xda-developers.com/showthread.php?t=1426244
What it does is allows you to factory-reset your TP to 3.0.0 (what most of them had when they were shipped), and then you can go from there to 3.0.5, then install CM9 again with AcmeInstaller2. I've done this procedure a few times, it works like a hot damn, and (if you have the 3.0.0 and 3.0.5 already downloaded) takes only about 20 mins to run both, and install Android.
Hope it helps, mate.
Interesting...I thought webOS doctor is as hardcore of a reset as it gets.
Thank you I'll try that.
Two questions
1. Do I need to have 3.0.5 on TP to install CM9
2. Do I need to have TP "jailbroken" to install CM9. Last time I had a custom kernel running on TP before CM9 but it was because I played around with webOS for a while before jumping to android. So basically I am not sure if it's a requirement.
Thanks for your help.
No, you don't need to have 3.0.5, but it makes it a lot simpler without having to do the upgrade after the fact (even though the actual OTA upgrade for it is like 20-30 megs or something - takes about as long to do it OTA through Software Manager as it does through WebOS Doctor.
As for your second question, you don't HAVE to, but it makes it easier if you turn on developer mode - in the JustType, type: upupdowndownleftrightleftrightbastart - then turn on Dev Mode. As I said, not mandatory, but it does simplify a few things.
You're more than welcome, mate !
All hail, ve6ay, savior of all the touch pads!
Thanks man that method worked.
Its people like you and rr5678 who actually figured that crap out, who make this community great.
Thanks again