• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

WebOS 3.05 is here (yawn)

After update, it looped on the hp logo. Did a doctor to 3.0.5. Fortunately it took only 17 minutes to do that.

It hosed my moboot. Reflashing moboot did not help. I reflashed cwm and at least it got me to recovery. Fortunately, I did a backup of CM7 before I did the webOS update.

I did a restore and the boot option for CM7 came back and I was able to boot into CM7. Whew.

So, in summary here is what happened and what I did to fix it:

booted into moboot and did a backup of Android.
booted webOS 3.0.4
updated to 3.0.5
rebooted and it looped on the hp logo <--- this is where it broke.
Doctored to 3.0.5
booted into webOS 3.0.5 and let it restore all my apps
copied moboot and cwm to cminstall directory in the SD (USB) under webOS
did novacom/acmeinstaller
Did a restore from moboot
All is good.
 
Glad you got it figured out.

I 'looped and had to DR when 3.04 came out.

I left out the 4th option.... failed install message after rebooting. Got that twice. Still on 3.04

I'm not bored any more. :D
 
I think I'm through updating webOS. I haven't even used it in about 2 weeks. No point in going through the hassle.
 
I'm done updating webOS.

3.0.4 came out and bootlooped when I updated. Had to doctor back to stock.

3.0.5 came out and update failed until I removed TWRP (4 megs) from my /boot partition, then it bootlooped. Doctoring again since I need webOS to update CM9 files.
 
I'm done updating webOS.

3.0.4 came out and bootlooped when I updated. Had to doctor back to stock.

3.0.5 came out and update failed until I removed TWRP (4 megs) from my /boot partition, then it bootlooped. Doctoring again since I need webOS to update CM9 files.


Why do you need WebOS to update your CM9 files?
 
The only option I saw was usb debugging, which we know won't let me transfer files. I remembered reading something about usb broken so didn't pursue it.
 
Back
Top Bottom