WebOS Internals Meta-Doctor

[matteebee13]

Originally Posted by Sanjay

I am trying to get rid of the AT&T junk on my AT&T Veer. For this I used the 'meta-att-veer-impersonate-wr-2.1.1' script.

1. How does one know that the script is finished running? The process seems to get stuck for a long time on "INFO: device runner done". But if I try to close the terminal window, I get a message stating that a process is still running. Why does the script seemingly get stuck?

2. After the script is finished, it does not automatically run the metadoctor. This does not seem to be normal. What could be causing this? I have even tried running the newly compiled meta-doctor manually, but I end up getting the following error:
"The file '/home/sanjay/meta-doctor/build/meta-att-veer-impersonate-wr-2.1.1/webosdoctorp160una-wr-2.1.1.jar' is not marked as executable. If this was downloaded or copied from an untrusted source, it may be dangerous to run. For more details, read about the executable bit."

3. How do I mark the metadoctor jar file as executable?

Thanks.

PS: Please ignore # 3. I changed the settings in the properties to make the file executable and am now running the meta-doctor. Hopefully all will be fine.

Sounds like you're on the right track. I've used the same script and had it installed using H2O for about a week without incident and all the ATT bloatware is gone

[ice8lue]

I just created a doctor using meta-wr-pre3-vanilla-2.2.3, did any of you guys already test this on a EU Pre3?

[domb]

Originally Posted by ice8lue

I just created a doctor using meta-wr-pre3-vanilla-2.2.3, did any of you guys already test this on a EU Pre3?

Works fine flashed on my EU Pre3 (UK QWERTY). I did however notice the webos.tar resource in this meta-doctor includes the 3004 ATT UMTS firmware. EU are running 3500. My device works fine on either.

You can disable the modem update in the meta-doctor Makefile to ensure your device remains on 3500 if you desire.

[dslunceford]

Wondering if I have what could be considered a "bricked" Pre (Sprint original).

Used Metadoctor this time last year via Cygwin successfully to make the device a wifi only device for my daughter (I see Cygwin support was since pulled). Everything seemed fine, but after a week she dropped the Pre and it went into an infinite loop where it's stuck on the "Palm" screen. You can see the screen flicker as it tries to start a process, but it stays stuck.

Phone taken away from daughter as she didn't treat it well. I just picked it back up to see if it's salvageable. In trying to Doctor (Sprint stock image), I can force it into USB mode and it will make it to roughly 8% before the phone is forced to reboot and again gets stuck at the Palm screen. Thought I'd post to see if anyone had thoughts...

[rwhitby]

Originally Posted by dslunceford

Wondering if I have what could be considered a "bricked" Pre (Sprint original).

Used Metadoctor this time last year via Cygwin successfully to make the device a wifi only device for my daughter (I see Cygwin support was since pulled). Everything seemed fine, but after a week she dropped the Pre and it went into an infinite loop where it's stuck on the "Palm" screen. You can see the screen flicker as it tries to start a process, but it stays stuck.

Phone taken away from daughter as she didn't treat it well. I just picked it back up to see if it's salvageable. In trying to Doctor (Sprint stock image), I can force it into USB mode and it will make it to roughly 8% before the phone is forced to reboot and again gets stuck at the Palm screen. Thought I'd post to see if anyone had thoughts...

If you see a logo at boot, then it is not bricked, and the techniques on our recovery wiki page will fix it.

-- Rod

[stealthghost]

Hi, is there anyway to generate att-vanilla 2.2.4 for pre 3 using meta doctor currently? i can't find the script in meta-doctor script folder

Thanks

[greenawayj]

Just wanted to post some recent experience in bringing my Sprint Franken-Pre2 back to 2.1.0 from 2.2.4. I definitely saw some behavior I've never come across before (10-12 Franken-Pre/Pre+/Pre2 MetaDoctors over the last year plus).

In short, at some point during / after my 'restore' process to get my phone back to full operating capacity, the Phone App would stop working. Tapping the icon would make it glow, but it would never launch. I could receive calls (and make calls using speed dial), but there was no "Phone" app... hence I couldn't terminate calls on my end. Reboots would NOT work to fix the issue. The Phone app just didn't work to be shown as a card. JSTOP did reflect two instances of "Phone" were running as background apps, but I couldn't terminate them.

MetaDoctor File for my Unlocked Pre2 with Sprint comm board was created in early January using this script ./scripts/meta-sprint-franken-unlocked-pre2-2.1.0

I didn't have time to use it until this past weeekend and the first MetaDoctor run led to the Phone App issue described above.

Thinking there were some lingering issues because of not erasing the /media/internal partition, I then ran a "Full Erase" (which never completed -- Phone was constantly glowing at the HP logo for 30-40 minutes, never rebooted).

Pulled battery and Ran MetaDoctor 2.1.0 a 2nd time. After profile log-in I ran "Full Erase" again, just to be safe. Erased USB and rebooted fine this time. Ran through my reinstall process (Apps --> Mail & Cal Accounts --> Turn Off UpdateDaemon -->USB partition files ---> Preware ---> SaveRestore --->HB Apps and patches --> "Other" accounts: Facebook and LinkedIn), each time checking the phone app along the way and didn't notice any issues until after the last step: Facebook and LinkedIn accounts.)

Finally, ran "Full Erase" again -- same as before it did not complete. This time, I installed MetaDoctor 2.1.0 again and so far so good. (~24 hours later). I have yet to add LinkedIn or Facebook accounts... The only other thing I did differently was to delete some unused App Cat / HB apps and a few less important patches. Not that I suspected any of these things could be responsible, mainly, I just figured I'd do some early spring cleaning.

I really don't need any help, since I appear to be working just fine -- using the same MetaDoctor file as before, but I thought I'd post my experiences here in case this ever happens to someone else. In case I ever need to Dr again, I'm happy to hear any ideas about what might have caused this or potential steps to take if it does.

[scratchNsniff]

Can you still make calls or text?

[duncano]

Got hold of a UK Touchpad with SIM card slot (marked on the back as a prototype) - friend of mine had wiped data and now cant get it to start. All versions of standard webdoctor report it's the wrong version so here I am at meta-doc.

Meta doc seems to run OK, have changed makefile to remove model check, but every time i run the modded webdoctor it continues to tell me i'm using the wrong version for the device. Using the ATT3.0.4 script.

Any thoughts or advice greatly appreciated.

[csrow]

I bought an unlocked AT&T Pixi Plus and I'm trying to make it so that I can use it in Europe trip as just a phone plus wifi.

First of all, I need to bypass the Palm activation and somehow still have the phone be ready for a SIM card overseas.

1) If I use meta doctor to bypass the activation using the AT&T webos Doctor image, will it lock the phone again?

2) So, after bypass, will the phone work without any 3G data when I plug in a SIM card?

*edit*
So, instead of messing with webos doctor, I just got an AT&T Go-Phone prepaid plan for $2/day and $5/10M data. I was able to set up the Palm profile and enabled the phone. Once the phone was enabled, I set up the wifi and then switched over to tmobile SIM card without any problems.