Pre 3 stuck at boot

[allen832008]

I had an issue with my Verizon Pre 3 shutting down when trying to use the camera app so I doctored last night. Now I'm unable to boot the device. It just shows the HP logo. I've forced a reboot a few times using both the toggle the ringer trick as well as the sym, shift, and r keyboard shortcut. Sometimes I get just the logo and sometimes it glows, but neither leads to the device booting. I am running out of options that I'm aware of and any suggestions are welcomed for fixing my most prized gadget.

-- Sent from my TouchPad using Communities

[mattho88]

have you tried re-doctoring yet? btw are you using the right doctor (see link below)

WebOS Doctor Versions - WebOS Internals

[allen832008]

have you tried re-doctoring yet? btw are you using the right doctor (see link below)

WebOS Doctor Versions - WebOS Internals

Yes. I've doctored several times with no success. With the correct version;-)


-- Sent from my TouchPad using Communities

[John Steffes]

Originally Posted by aia832003

Yes. I've doctored several times with no success. With the correct version;-)


-- Sent from my TouchPad using Communities

Have a Vzw Pre3 (not activated yes) but you might have a partition that needs to be fixed. Look for dosfsck and f s c k issues in linux. (remove the spaces).

If there are issues you can memboot and look at the boot logs...

[broncot]

I have taken this project over, having bought the Pre 3. Novaterm won't connect, no way to know if developer mode is on. I've run the 2.23 and 2.24 Verizon webOS doctors, which complete successfully, but the Pre 3 never boots.

[John Steffes]

Originally Posted by broncot

I have taken this project over, having bought the Pre 3. Novaterm won't connect, no way to know if developer mode is on. I've run the 2.23 and 2.24 Verizon webOS doctors, which complete successfully, but the Pre 3 never boots.

I would memboot and check the boot file system, uImage?, then check the rest of the file systems...

[broncot]

I followed the memboot steps on webos internals page, it still won't boot. How can I check the boot file system, uImage and other file systems?

[broncot]

Problem solved-I went through the steps here:
Pre won't boot up after failed Uberkernel installation
and it worked!

[elvispre]

"Funnily" enough, my (UK) Pre3 got stuck at boot too this afternoon. HP's support site denies that my serial number exists (it certainly does) but thanks to WebOS Internals I was able to lay my hands on both a 2.2.0 and 2.2.4 doctor package. I can memboot it. I can run novaterm and mount all the /dev/mapper/store-* filesystems. Unfortunately I cannot successfully run either doctor nor can I repair the corrupt store-media filesystem. I get I/O errors. It seems to me my Pre3 has died of flash memory fatigue (just like my old Palm T|X did).
Sad face. What do I do now? Decide which Android phone tobuy, I suppose.

[GMMan]

Originally Posted by elvispre

"Funnily" enough, my (UK) Pre3 got stuck at boot too this afternoon. HP's support site denies that my serial number exists (it certainly does) but thanks to WebOS Internals I was able to lay my hands on both a 2.2.0 and 2.2.4 doctor package. I can memboot it. I can run novaterm and mount all the /dev/mapper/store-* filesystems. Unfortunately I cannot successfully run either doctor nor can I repair the corrupt store-media filesystem. I get I/O errors. It seems to me my Pre3 has died of flash memory fatigue (just like my old Palm T|X did).
Sad face. What do I do now? Decide which Android phone tobuy, I suppose.

Have you tried formatting the media partition? Also, you can dd to /dev/null and see if it can read all parts of the media partition.

[elvispre]

Originally Posted by GMMan

Have you tried formatting the media partition? Also, you can dd to /dev/null and see if it can read all parts of the media partition.

I believe I have tried formatting the media partition, yes. mkdosfs reported success instantly but I am far from convinced it did anything because the subsequent fscks reported problems with files that ought not to have been there any more.

Perhaps I shall try again in the morning, and that dd idea is a good one.

I am not optimistic, but thank you for the suggestions.

[elvispre]

dd if=store-media of=/dev/null

results in

dd: store-media: Input/output error

I think that's bad, isn't it?

[GMMan]

Try with /dev/mmcblk0p9. IIRC that should be the LVM section of the flash. You might also try opening another shell and watch dmesg.

[elvispre]

Originally Posted by GMMan

Try with /dev/mmcblk0p9. IIRC that should be the LVM section of the flash. You might also try opening another shell and watch dmesg.

Interesting. Actually, it seems to be /dev/mmcblk0p15 that's killing me. I ran dd to /dev/null on all of them, but only that one results in I/O error. dmesg goes berserk:

[131657.711242] Buffer I/O error on device mmcblk0p15, logical block 147163
[131657.711242] Buffer I/O error on device mmcblk0p15, logical block 147163
[131657.723052] mmcblk0: error -110 setting mmc block length
[131657.711242] Buffer I/O error on device mmcblk0p15, logical block 147163
[131657.723052] mmcblk0: error -110 setting mmc block length
[131657.723358] mmcblk0: card status 0x400b00
[131657.711242] Buffer I/O error on device mmcblk0p15, logical block 147163
[131657.723052] mmcblk0: error -110 setting mmc block length
[131657.723358] mmcblk0: card status 0x400b00

etc...

[GMMan]

I can't remember what all the partition numbers are, and ASCIIbetical order made me miss partitions higher than 9. Yeah, that's probably the LVM partition. Is it that same logical block all the way across?

[elvispre]

Originally Posted by GMMan

I can't remember what all the partition numbers are, and ASCIIbetical order made me miss partitions higher than 9. Yeah, that's probably the LVM partition. Is it that same logical block all the way across?

No, there were higher numbers as well. There were pages and pages of that.