I'll start from the beginning:
I've put the F4 Kernel on my Touchpad, and all was running fine. I recently put it on eBay, today I've gone into 'device options' and done a 'full security reset' on the device as I'm sending it off in the next 2 days.
It went through this, rebooted through the F4 Kernel boot screen and gets stuck just after that (pic is where it gets stuck)
I've booted into USB dev mode, but WebOS Doctor is 'unable to reset your phone'.
It gets to 8% before it gives me this notification.
I've tried multiple reboots, even left it for a period of time but noting happens.
Any advice or help would be appreciated before I have to send it off!
Thanks.
my touchpad had kind of a stroke this week end
I've been using the hp tablet for a little over 2 weeks and it was working very well putting aside the limited app market.
saturday morning, I left it on my coffee table with 50%+ of battery left when I left the house.
when I came back a few hours later, the tablet was off so I turned it on.
It took forever and instead of booting up using my user account, it showed the setup process. I could log in using my existing account but webos couldn't restore the data. I don't understand why it had to restore the data in the first place but whatever.
I could create a new account but then everytime I reboot I get to the setup process (and I'm losing all the apps from my existing account)
Something happened/broke while I was out and my touchpad is now useless.
I tried webos doctor but it fails at 8% (can't reset device)
I've sent a log to the hp support but I've not been given any other directions other than that so do you guys have any idea of things I could try?
After hours of tech support, making me try stuff I already tried, it is going back to hp for repair/replacement.
the lvl 4 tech support has never heard of similar issues so it's apparently an isolated case.
http://www.webos-internals.org/wiki/How_To_Recover
Check the webOS failing at 8% entry. It worked for me.
I saw that but I never found uImage from the webOS Doctor jar :/
nks2105 said:
I saw that but I never found uImage from the webOS Doctor jar :/
Click to expand...
Click to collapse
Yea, you have to dig for it.
Open the .jar > resources > webOS.tar > nova-cust-image-topaz.rootfs.tar.gz > nova-cust-image-topaz.rootfs.tar > boot > uImage-2.6.35-palm-tenderloin
*whew*
It was indeed hidden deeply and I haven't been that far in the tree...
I might give it another try then
Related
Before posting here, I looked extensively for someone with a similar issue reported and came up empty. I also tried PPCGeeks a couple days ago and got no response. I thought I'd run this issue by the real experts before taking my phone to Sprint "experts" so that they can swap it out. Here are the details:
My Photon 4G has been rooted since right after I got it about 8 months ago and has had no problems like this until now. The only app that has updated in the last couple days is Busybox and that was the night before this all happened. My battery died and the phone did a forced shut-down that night. I plugged it in, powered it up, and let it charge all night & then noticed the problem the next morning.
I'm using DejaOffice for my calendar and contacts (contacts are also synced to the native phone list) and I use companionlink to sync everything from my desktop (Windows Vista). When I looked this morning, everything in DejaOffice was purged including my preferences (screen color, alarm defaults, etc.). I re-synced everything, powered off and then back on, and had the same problem with everything being gone.
Next, I tried purging DejaOffice data and un-installing it, re-installing it, re-syncing and then powered off/on and once again everything was gone. Finally, I did a factory reset on the whole phone (and forgot to backup my voicemails in the process...grrrrr), re-installed DejaOffice, synced, and had the same problem once I power-cycled.
One more thing to note is that before doing any of this, I attempted a backup with "My Backup Root" and got a message that my phone was no longer rooted.
It seems like the internal memory on my phone is being wiped every time it's shut down. I know the quick fix is to not shut the phone down however I'd like to get to the bottom of this and see if I need to get my phone replaced.
Any ideas??? Thanks in advance for any help/advice.
<bump> and update:
I noticed that my "webtop version" is "unavailable"...not sure if that makes a difference to my problem. Also, when this problem first presented itself, I noticed it because the ringtone that I usually use (which was stored on the phone's internal memory of course) was gone.
Once again...any help or replies would be much appreciated.
Thanks!
Hi folks,
I had just picked up the ZU last night, first thing I tried to do was to configure my office email. First it made me charge the phone to a decent amount of juice for the encryption part. Once I did that, I hit next, it prompts me to key in the pin and I do see the Android Encryption for a bit, before it reboots and after that I am setting up my phone all over again (like it went thru a factory reset).
I've tried doing it again but the same thing happened. I am now using an app called Divide which is really good, but somehow I would like to have the default email app working.
Any ideas?
Thanks a lot!
Hi!
I'm using it now a little less than one year. This morning everything still normal, used the phone and then all of a sudden, I get a screen saying something like "Your device is setup and ready to use. Okay" and I see a screen that immediately makes me worry: no accounts, another launcher, my icons, data and accounts all GONE. What?
I made a screenshot and without much hope hit "reboot". After that, voila, my OLD setup is back again. But after less than 20 minutes, I get yet ANOTHER screen: "Welcome back, guest. Do you want to continue where you left off or ...." you get the point, don't you? Rebooted again.
Now I'm copying all my stuff to SD card (fortunately there's one supported), along with the two screenshots that were not accessible in my setup, but got them copied when the second "wipeout" happenned. What's going on?!?
Thanks!
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk
Hey guys.
I own a N9, which I lent to a friend for a while. He logged in and used it as if it was his own for a while. He returned it to me on monday, and with him in tow, we tried to restore to factory settings - he mentioned that it was running a bit slow, which I though was just it being older now.
When we tried to factory restore from the OS, it just hung, and never actually reset (tried 3 times).
I then booted from recovery, and chose factory reset from there. Done.
However, when it finally booted into the OS, the set up wizard wanted the previous account, fine, no issues. we put 1 account and its password in, only to be presented with a 24 hour lockout (due to password change) - but we didnt change a password.... We left it for a couple of days (both busy) and we just tried it again, still saying 24 hour lockout.
What can we do now? I understand this being there as a deterrent from theft, but I am the actual rightful owner!
This is called an "FRP lock" that is on a majority a android device that is similar to that of an icloud. Good news, there is definitely a way to bypass it. Bad news, might be a pain in a**. So lets I guess start with getting some system information like, what version is it running? Can you boot into recovery fine? Can you access the accessibility setting somehow on the main welcoming screen?