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.
Related
So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton
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
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.
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
Here's the background story. I had been running Team EOS 4 for quite some time with no problems at all. I decided to encrypt my device. After encryption an update for the Team EOS rom became available and I went to flash it only to find out I could not get into TWRP recovery console. I was running twrp 2.5 and decided to try an earlier version, so I hooked up the Xoom and fastboot flashed an older version. I was able to get into twrp recovery using version 2.4.4, but it would not mount /data. With great help from the TWRP team, I was able to get /data mounted and was able to perform a factory reset to remove the encryption. I then flashed the latest version of twrp, 2.6, and installed the latest Team EOS rom. I then rebooted, but I can not get past the Motorola splash screen. I let it sit at that screen for 2 hours before I went to bed and when I woke up, the battery had died, so I'm assuming it never booted. During the 2 hours I was up, I tried to get into adb, but it told me the device was offline. Is there any way to fix this or did I just make myself a brand new paperweight? I am kind of a noob when it comes to the android stuff. Thanks in advance.
Edit-
Nevermind. I broke the cardinal rule of not reading other threads before posting. There was something wrong with the latest version of the Team EOS rom and once I want 2 versions back, it booted up. Sorry for the post. This thread can be deleted.