Hey Guys,
So..... I'm trying to fix my friend's TouchPad and having no luck what so ever. I'll describe the problem the best I can and then tell you what we've tried so far.
In a nutshell, it seems almost like the drive inside the touchpad is write protected.
I can delete and add files no problem but if I either
Restart Luna: It does a sort of "half reset" and start acting weird. Preware might not work properly or sometimes the app catalog won't connect. Plus all the icons rearrange themselves to their factory setting with my downloaded apps (both store and preware) being bundled together under the downloads tab.
or
Restart Touchpad: Any changes made during the previous session get reverted back to a point about a week ago (not factory default). Everything from icon positions, apps installed to even content on the touchpad. For example I could delete a movie or a song from my library, restart the device and the file would reappear. It's like it reflashes an earlier image of itself. (Skynet has become self aware?)
So here is what I've tried so far.
Full Erase: Nothing happens. Device restarts and we're back to square one.
Secure Full Erase: Same thing.
WebOS Doctor: Doctor starts up... I click through the screens, progress bar appears. Usually somewhere before 28% Doctor just quits and says it had an issue resetting my TouchPad and to go to the support page. The support page is useless, just tells me to re-download and restart/connect both my devices. Which I have done.
(I'm also using the latest version of WebOS Doctor and the ToucPad is on 3.0.2)....
I also tried running WebOS Doctor from Dev. mode (Hard Reset TouchPad and then hold Power+VolUp)
When I restart the device after a WebOS Doctor attempt, things revert back to the same state as before.
help?
ps: The touchpad functions fine otherwise. Everything runs it's just....stuck....
did he have 3.0.3 and/or the chomper android ipk installed?
if so, the kernel could be stuck on there. i'd try going back to 3.0.3, install chomper 0.1, uninstall through menu (NOT THE X-OUT UNINSTALL), and then try another doctor (3.0.2 or 3.0.3 shouldnt matter)
to be honest i don't have to much know how with tablets. my guess is if you have issues with webosdoctor
you have hard drive issues. maybe googling hard drive problems will eliminate that.
Sent from my HTC HD2 using XDA App
Just triple checked..... not on 3.0.3 (he's running 3.0.2) and no chomper/android ipk....
He did have the Warthog Kernel OCed at 1.7ghz installed. Though that ran perfectly fine for the the last few weeks. We just tried uninstalling the kernel just to double check and see if it has any effect, but no luck. Still back to previous state after restart, with Warthog Kernel back in place.
Update: Just flatout reinstalling the stock kernel on top does nothing either.
lehel.babos said:
Just triple checked..... not on 3.0.3 (he's running 3.0.2) and no chomper/android ipk....
He did have the Warthog Kernel OCed at 1.7ghz installed. Though that ran perfectly fine for the the last few weeks. We just tried uninstalling the kernel just to double check and see if it has any effect, but no luck. Still back to previous state after restart, with Warthog Kernel back in place.
Update: Just flatout reinstalling the stock kernel on top does nothing either.
Click to expand...
Click to collapse
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
http://www.webos-internals.org/wiki/How_To_Recover
webOS doctors reinstall
Nburnes said:
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
The best way per HP support to reload the webOS doctor is to go to the HP profile manager from a Windows PC and you can download and install clean webOS doctor. I have successfully reloaded a clean webOS on my touchpad using the following steps.
You will need to put your touchpad into recovery mode, first turn off you touchpad then hold down volume up and power button and will go into recover mode
Connect USB cable between Windows PC and Touchpad
Go to the HP profile manager website and select download webOS Softer
Follow the steps on screen
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
Nburnes said:
Have you tried membooting the device off a kernel you ripped from webOS Doctor?
http://www.webos-internals.org/wiki/How_To_Recover
Click to expand...
Click to collapse
Best way to reload the webOS doctor is to go to the HP profile manager from a Windows PC and you can download and install clean webOS doctor. You will need to put your touchpad into recovery mode, first turn off you touchpad then hold down volume up and power button and will go into recover mode, connect USB cable between Windows PC and Touchpad.
Click to expand...
Click to collapse
I have the same problem as the OP. Also running 3.0.2, updates fail, doctor fails. Nova booted the image extracted from doctor, can't write anything, can't wipe LVM. It's like the whole thing is write protected.
If anyone finds a solution, please post!!!
try reinstalling novacom drivers, also, try just rebooting the pc, you'd be surprised how often that works (i had the same problem, rebooted, was able to doctor with no problem after that. seems like you have to hard terminate the connections)
Solidus_n313 said:
try reinstalling novacom drivers, also, try just rebooting the pc, you'd be surprised how often that works (i had the same problem, rebooted, was able to doctor with no problem after that. seems like you have to hard terminate the connections)
Click to expand...
Click to collapse
TouchPad says it can't umount the log volume (as a matter of fact it can't even mount it to begin with), so its entirely unrelated to any computer the doctor runs on.
Eh, if only doctoring was the key. I'm not able to make persistent changes to the block device or the filesystems while I am working in a terminal, both the developer mode in WebOS or the nova booted rescue image. System executes write commands, but then I check things didn't get written.
As for computer, HP made me do doctoring on two different computers. Unsurprisingly the result was not any different.
HP is taking their sweet time to call me back from Level 3, personally I'm quite ready for the replacement, as at this point I am certain that I won't be able to fix it short of opening it up, and programming the flash using other means.
I just found that i have the same problem. Worst of all, it seems it's doing this on cyanogenmod also. I have android and webos on dual boot, tried to erase the android part with ACMEUninstaller, after reboot android was back. Erased the cm particions with novaterm, same result after reboot. I would really appreceate some help please, really desperate ...
I have the same problem with my touchpad. do you find any solution.
rai177 said:
I have the same problem with my touchpad. do you find any solution.
Click to expand...
Click to collapse
I also have the same problem and I've ignored my Touchpad for months as a result. I read somewhere that a person with the same problem got it replaced by HP under warranty, but that was a long time ago.
I got the itch to work on this problem again. I will report any solutions I discover.
You guys ever figure out this issue?
Sent from my HTC One using Tapatalk
read only
A friend of mine has the same read only problem on her touchpad, and she doesn't have android or has never tried installed android. I tried factory resets and webos doctor and nothing works, after reboot it reverts back to last known good configuration. I haven't tried to do a complete data reset through the tptoolbox v41, has anyone tried that method? Any other ideas that may work, or is this really a hardware issue? Thanks
Related
Proud owner of my first tablet as of about noon today (got hooked up through my guy at CDW-G just before their inventory blew up). Since then I've been trying to get the system update to complete with no luck.
I've had it unpack to what appears to be about 90% (or less several other times). But each time it hangs and says "Unable to Connect. Try Again Later."
My internet is solid with no connectivity issues at all from that end. I've tried rebooting multiple times as well. No luck. Haven't found anything useful searching the web either.
I was really hoping to find an actual copy of the update that I could load manually (though USB maybe). But no luck at all.
I've also had it tell me that my device is up to date, but the version listed in system information says 3.0.0..... And then if I go back into System update it says 3.0.2 68 is available again.
Any ideas?
I was unable to perform the update as well. One website attributed it to server overload. I'm just going to wait a while.
I had the same problem. I left my touchpad on over night and it prompted me to reboot when I woke up, then took about 10 minutes with a circular progress...bar...wheel?
That was my assumption as well... I was hoping others has the same experience so I know it wasn't just me.
I had the same problem and did this:
Go to the Hp WebOS Account page on your pc and login with your info.
Go to Device Options
Download WebOS Doctor
Install
Put your Touchpad in Developer Mode: enter "webos20090606" in the Just Type box
Just skip the password option.
Run WebOs Doctor and plug in your Touchpad when prompted.
You'll have the update in about 20 minutes total time.
awesome man. I'll have to dig into that after I tuck the kids in for the night. Thanks for the help!
Be advised, updating via WebOS Doctor will reset your device and you will have to enter all of your accounts again. It does however automatically reinstall all of the apps you downloaded from the market.
Here's a link for downloading WebOS Doctor:
http://www.webos-internals.org/wiki/Webos_Doctor_Versions#Wifi_Only
Why am i getting this error from updating
if its unpacking why am getting the download error?
shouldnt it already be downloaded?
tomv9302 said:
I had the same problem and did this:
Go to the Hp WebOS Account page on your pc and login with your info.
Go to Device Options
Download WebOS Doctor
Install
Put your Touchpad in Developer Mode: enter "webos20090606" in the Just Type box
Just skip the password option.
Run WebOs Doctor and plug in your Touchpad when prompted.
You'll have the update in about 20 minutes total time.
Click to expand...
Click to collapse
I take no credit I just followed tomv9302's instructions.
i had that crap too. It was the slowest 38mb update EVER.
it kept crashing and going to that page. I put this broken LED light to track progress and sure enough it would disconnect but then start back up from where it left off if you reinitiate.
Took like a dozen times (at least) but it finally did it successfully.
I'm sure there's quite a bit of people trying the same thing.
updater working now, it was indeed the slow server, managed to update to 3.02 just now
Did the updater affect any of your existing accounts or make you have to go through the initial setup?
no initial set-up again, just updating
Can't Download Anything :-(
Web works fine but I can't Download any apps or upgrade. I guess its because of the high demand and the amount of people who have this now.
Anybody having problems with the market?
What did u do to fix it?
I had problems with the catalog too. I checked my wife's TouchPad and her's worked fine. I did install a bunch of patches and the OC'd kernal.
I went into Settings/Device Info/Reset Options/Full Erase and that fixed my catalog. After the reset I slowly started adding patches and the sort while checking the catalog functionality after every few installs.
B
nautalis said:
I had problems with the catalog too. I checked my wife's TouchPad and her's worked fine. I did install a bunch of patches and the OC'd kernal.
I went into Settings/Device Info/Reset Options/Full Erase and that fixed my catalog. After the reset I slowly started adding patches and the sort while checking the catalog functionality after every few installs.
Click to expand...
Click to collapse
I'll give that a go...everytime I tried to download it just failed
Still nothing keeps saying try again later
what does "unpacking" mean? Sometimes it gets that far, then says that it's updated, but in system info it still says 3.0.0
Maybe an obvious one but have you tried switching it off and on again. worked for me
I had the same issue for a while - here's how I solved it
Be warned this will wipe your accounts and reset your touchpad - your apps will remain but only because webos is awesome and just goes and redownloads them once you sign back in
Go to the hp touchpad site and sign in - click device options and select download webos doctor. Run that. Meanwhile turn your touchpad off and put it into usb mode (hole the power button and volume button whilst a usb cable is plugged ONLY into your touchpad)
webOS doctor should be asking you to plug your device in now - plug it in (with the USB symbol on the screen) This will then flash your device and but the latest firmware on it.
Then turn it back on sign back in...etc and you should be sorted! I know it is a bit annoying, but it was the only way I could get my market working - the OTA worked, but seemed to not fix the underlying problem - also allowed me to install preware, which has made the device a contender to keep webos on it!
I purchased a 32Gb Hp Touchpad from ebay. When I try and go through the first startup settings, the setup always stalls at the wifi portion. I have read and tried all of the suggestions I could come across.
1) Unit powers on
2) Select Language
3) Select country
4) Confirm country
5) Wifi Setup, Choose a network.
6) Select network and input key if used.
7) Device shows a check mark that is is connected to the network.
8) Get message "No Internet Connection" "Cannot connect to the internet through this connection. Try another network."
I have tried many different networks, My home wifi, work wifi, McDonalds wifi. No network will connect to the internet.
I reset my home to Open with no security. No Internet Connection.
I tried using webOS Doctor, does not finish. I tried several versions. 3.0.0, 3.0.2, 3.0.4, and 3.0.5. webOS Doctor always stalls at 8% with message "We are unable to reset your device."
Any suggestions would be greatly appreciated.
Thank you.
Sorry to hear your TouchPad isnt working. I would hate to think you got a TouchPad with broken wifi hardware. If thats the case, it cant be fixed. I dont know why your doctor isnt working. Did you make sure you had all the necessities before running it?
Thanks for the response.
I don't think the wifi is broken. I can see and even connect to all of the wifi networks that I tried. Every connection said no internet connection.
I click "Start Over" and go to the beginning screen. Click the "HP webOS" in the upper left corner and select "Device Information".
I see the following:
Device ID, 8 sets of 5 digit numbers,
MAC Address, (not all zeros)
Device Model, HSTNH-129C
Product Number, FB539UA#ABA
Serial Number,
Handset, 180-10871-00
Hardware Version, A
webOS Version, HP webOS 3.0.4
I have connected with novacom and ran some Linux commands even tried rm -r *
Is there a way to flash a "New" Never setup Touchpad?
I remember reading somewhere that the wifi software in version 3.0.4 had an issue. Would this cause the setup to not connect to the internet?
Would the wifi need to be 802.11a?
Just looking for a way to reset or get working.
Thanks.
I would just use the AcmeInstaller 2 all over again with the latest edition of the ROM you want and see how itbgoes
Sent from my cm_tenderloin using Tapatalk 2
Is it possible to install Android on the Touchpad even if the Touchpad has never been activated? This is the first time that the Touchpad is to be activated.
Is there a way to erase the flash drive on the Touchpad?
I don't want to give up just yet.
Thank you.
There's a thread HERE that talks about what to do when you get the 8% hang using WebOS Doctor. There's also a thread HERE on how to do a full downgrade factory reset to 3.0.0 that SHOULD have you back and running without too much difficulty. I would suggest trying the second, as it tends to fix most peoples' problems. From there, Doctor up to 3.0.5, install Android again, and you're golden. If you have the Doctor files downloaded, it takes about 20 minutes to do the reset => flash to 3.0.0 => Flash to 3.0.5 => install Android
This Touchpad is new and has not been setup before. I have been trying to do the initial setup. Is there a way to wipe everything clean.
I have not installed Android or anything else on this tablet. I am unable to get it setup to any degree.
I have attached a log file from running the webOS Doctor 3.0.0
Please take a look and see if there is something that may help.
Check out webOSNation, there are a few threads about these issues over there.
Sent from my very "non-stock" TP.
Shortly after Team DRH's last update for their ICS 1.2 I installed it no problem and it ran for a few weeks. Then I left the tablet alone for a week or so and when I turn it on now the wifi is not working, it just says "turning on wifi" but never actually does. I've followed the reflash instructions here: http://forum.xda-developers.com/showpost.php?p=23147934&postcount=4 and I can re-install ICS endlessly. But even after following those instructions, and even after RayWaldos NVFlash for dummies, it still always says "turning on wifi" but doesn't.
When, during the above flashing, I let the stock tapntap boot, wifi works no problem. It's only when i install a ROM that it stops working. I even tried installing Gtabcombover and it gave me the same "turning on wifi" problem.
I did try searrching the forums, but I see no mention of this anywhere.
Thanks.
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Slightly Askew said:
If I can be more to the point: does anyone know of a way to completely reflash stock everything? I thought I was doing that, but obviously not enough.
Or do I need to crack open my case and push that Dirty Little reset button?
Click to expand...
Click to collapse
I was able to use the DHR NUFLASH.. It worked real well for me.. download the right file (bootloader 1.1 or 1.2) to your pc, for your g-tab.hook up your USB cable Turn on your tab wile holding your volume (-) key , the logo will come on and then go black. Then go to the nuflash- win file, you downloaded to your pc and run.. The instructions are on the DHR site are vary good I read them a few times before I tried. Its worked great for me.. I'm a noob. Lets just say its just about makes the gtab un-brickable...
Sent from my G Harmony v2.8 using xda app-developers app
graftonrod said:
I was able to use the DHR NUFLASH. . .
Click to expand...
Click to collapse
Well the good news is that after reading your post I went straight to the DRH website and lo and behold they had just posted Beta 1.3 that morning. I redownloaded their Full Stock CWM 5504 NVFLASh file even though I already had it, and the Beta 1.3.
I flashed the stock file and let it boot just like they said but the setup process began a FC loop and would not complete. I simply rebooted and the setup was able to complete. The I installed the Beta 1.3 with no Gapps and it worked like a charm. Wifi was working and everything, except there was no Market. So I did a wipe/FR and installed again this time with Gapps and everything is back, wifi, market, all good. And I have noticed that it all seems to work a ton faster and smoother.
I rooted and installed custom recovery on my HDX7 using the HDX Toolkit according the the given instructions. After a few days I decided to uninstall recovery and moved the TWRP backup to external storage. I hadn't installed any custom roms or created any rom slots. I had no problems for days until these changes I made last night.
I uninstalled towelroot, reading that it was safe to do so. I installed a flashlight app. I installed Greenify and auto-hibernated some some third-party apps - including ES FileManager and Safestrap, which I considered safe since I had already uninstalled recovery. I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well. I also turned WIFI off before shutting down.
The device is now stuck at the second splash screen with the animated white and gold Kindle Fire logo. The screen is also slightly dimming and brightening repeatedly. I can't get into safe-mode/ recovery mode. I looked up what I was disabling but think I goofed using NoBloat and Greenify and screwed myself by uninstalling recovery.
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Segue2 said:
...
What should I do and how? Will uninstalling nobloat, greenify and flashlight through adb RENABLE the disabled and hibernated apps and revert to previous settings? I have the TWRP stock rom backup on my computer! Can I flash that if nothing else works?
I'd appreciate the help and instruction, thank you.
Click to expand...
Click to collapse
Did you try hard reset? Press power button for more than 20 sec. Your kindle should then restart itself hopefully without bootloop. I was once messing with rooted stock fire OS trying to add one app to system apps (live wallpaper support I think), after restart I get neverending bootloop, but I was able to get out of this by doing hard reset, then Safestrap showed again and I was saved.
If you can manage reverse all your changes on system through adb, good for you, but without installed Safestrap ... well, maybe someone with better skills can manage you through this ...
I have tried but hard resets aren't working.
Can you still access it through ADB?
EncryptedCurse said:
Can you still access it through ADB?
Click to expand...
Click to collapse
No, looks like I am having trouble getting adb access. Command adb devices is returning nothing. Windows is recognizing the Kindle, however, but only as a portable device. Definitely had adb access before (established to use the HDX Toolkit). Now, I am wondering whether I disabled adb support on the kindle at some point beforehand.
On a sidenote, I just unplugged and reconnected the usb cable a few times and was able to hit the lockscreen for a few seconds before falling back into the bootloop. I have been able to repeat this.
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Segue2 said:
I have tried to follow GSLEON3's steps, http://forum.xda-developers.com/showthread.php?t=2588608&page=8, to regain ADB access. I haven't had any luck - windows keeps recognizing it as a portable device. Any other suggestions for driver installation?
Again, occasionally the lock screen comes up. It was up long enough for me to swipe open and see my installed apps on the carousel, at one point, before falling back into the bootloop!
I'll keep reading and trying to establish ADB, but I have a question. Given that I have only rooted and disabled some processes, without any other serious modifications (no build prob edit, no new partitions, no roms, no custom recovery anymore) do you think a factory reset would be safe at some point if I can't get adb access?
Click to expand...
Click to collapse
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
EncryptedCurse said:
From what you're saying, a factory reset does sound sensible but I honestly don't want to guide you in the wrong direction.
Click to expand...
Click to collapse
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
jimyv said:
doing a factory reset do not believe will remove something from system files if that is where he has pushed itand may cause complications. I do know from personal experience a factory reset with xposed framework gets really nasty really fast.I would keep trying to get ADB back...once you see it on your PC in any mode you must go to your device and device managers and uninstall all drivers. and reboot PC. Do not plug your device back in 2 PC till you have installed correct drivers
if nothing has been pushed to system and you have not install xposed framework...greenify will work with and without it I'm not sure about nobloat. Hdx signature bypass module requires xposed...did you attempt gapps installation? but if you know those two things for sure and for sure nothing pushed to system files you are safe to do a factory reset under factory recovery. The opposite button combination for recovery will result in safe mode boot...
more information?
Click to expand...
Click to collapse
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Segue2 said:
Thanks.
I did not install Xposed nor GAPPS. The only system modifications to device were 1) manual update to stock firmware 13.3.2.4. 2) Towelroot 3) Super SU 4) Safestrap, which is no longer installed 5) Disabled OTA updates using HDX Toolkit and 6) Greenify and Nobloat to disable 3rd party and system apps.
I havn't pushed anything else to system.
I am currently on Ubuntu trying to get adb access. I am NOT familiar with linux but I have gotten JDK and Android SDK installled. Still, no access and no device id number listed. Should I go back to windows and try again?
Click to expand...
Click to collapse
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
jimyv said:
well it definitely would not hurt anything to try Windows again don't bother with a factory cable does not apply to this device we do not have the proper tools / softwareware
you might do a little reading over in toolkit thread and that you till the thread at last few pages anyway I do not believe that you will get negative effect from just having OTA block with a factory reset. personally a factory reset per stock recovery that would be my next option.. as long as you know the only thing that has been pushed to system is su, and no xposed framework.
you may even have to re disable OTA updates.
remember plug in your device. Allow it to boot as far as it will boot if you can get it to boot into the running system that would be great just do not attempt to unlock it if that what crashes it. Go to Device Manager and uninstall all drivers for your device.
unplug it from PC and reboot PC. Then install correct ADB drivers and reconnect
Click to expand...
Click to collapse
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
lol
Segue2 said:
I will try fresh installs on Windows again, then. I did read and interested tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop.
Click to expand...
Click to collapse
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
Segue2 said:
Ok, thank you. I will try fresh installs on Windows again, then. I did read an interesting tip by GSLEON3 about having a copy of cmd.exe in the sdk folder, which I didn't try.
Also, I can't get into safe mode. And one more question - is it normal that the HDX can only be powered off while unplugged? If I plug in any power it automatically turns on and starts bootloop and won't turn off, even on wallcharger.
Click to expand...
Click to collapse
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
jimyv said:
yes and personally I find it annoying as hell. The HDX does not charge powered off unless it is completely dead and it only charges for a few seconds and as soon as it has enough power to power up it powers up. completelynormal for this device
---------- Post added at 12:09 PM ---------- Previous post was at 11:47 AM ----------
there are a couple of minimal adb and fast root utilities around XDA that's all I use...have you been able to get into stock recovery?
to enter SafeMode on thor...
hold power and volume down until grey logo cycles at least twice release power and continue to hold volume down until device completely boobs. if it works it should stay booted and allow you to uninstall third party apps it should say safe mode in left lower corner
Click to expand...
Click to collapse
Ok, good to know about the power.
Yes, I have used the Minimal Adb and Fastboot utility before and couldn't get access.
I can get into stock recovery for a factory reset.
I can not get into SafeMode. It ends up booting to the lockscreen for a second or two before falling back into bootloop - sometimes flashing the lockscreen again.
okay well I do believe you have run out of options..in a nutshell you are looking at a replacement device anyway so you should be on the go for a factory reset
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
by
Segue2 said:
So, I tried establishing ADB in Windows and Ubuntu again with no luck. I went ahead with the factory reset. Now, it is just flashing the lockscreen repeatedly without the kindle fire logo bootloop.
Thank you for the help but I guess there is nothing more to be done?
Click to expand...
Click to collapse
nope you are out of options before you got to the factory reset.apparently something was done to the system that nobody knew about. Or there is a hardware problem anyway.you can try to hold the power for over 20 seconds or another factory reset but sounds like you need to give Amazon a call anyway you might have had a bad unit. Because nothing you described in above paragraphs should have gotten you to this point.
Segue2 said:
... I installed NOBLOAT and disabled (not uninstalled) a few other processes and preinstalled Amazon apps as well.
Click to expand...
Click to collapse
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
jeryll said:
Well, I think this is the main reason for your problems. In the past, when there was no alternatives I run modified FireOS + gapps from cpajuste and after a while I find that running all this amazon bloatware consuming so much memory and cpu power, so I did the same, installed greenify, some utility to disable running background services, through another utility (I dont remember the name) disabled several amazon apps I didnt use ... I was trying to make more space for running google tools ... Ofcourse I didnt do changes on stock rom, only on extra slot always with backups in case something went wrong. And it always did. FireOS is sure not your typical Android - at some point we all learn this.
So after several mostly not successfull experiments with disabling amazon apps (fireos ends in bootloop, or didnt start at all) i decided to give up and later when alternatives from ggow was available I completly switch to his rom and (not using amazon services at all) I am happy with his Nexus 2.0.2 till today.
So from my point of view you disables some (one or more) critical process which fireos really really need to complete startup sequence and thus bootloop you are experiencing. Without safety net (safestrap + using extra slot) there is not much to do, unless you somehow gain adb access, but this is now probably not an option after factory reset you did...
Click to expand...
Click to collapse
the loop he was in would not allow him ADB either ,something was done here other than what has been stated whether it was known or not.
correction I also use greenify it on all my devices. And to be able to do anything to system you must have had exposed framework installed....in which case I would have never have recommended a factory wipe. as stated several times already. simply hibernating a few apps even hibernating a few apps ( which is about all you can do without framework) would have not gotten him here. he had to have permanently removed something from system or permanently disabled iteither way without knowing exactlywhat service he appy that too it would be a guessing game even with adb.in short like you said lesson learned for another person that bothers to read this thread not to tamper with your stock system without safestrap at bare minimum and a backup
I wonder if he has had any luck with ADB now that he is no longer in a perpetual boot loop. May be able to come up with a reenable command for system apps? Su should still be in systemat least the binaries will be in case the app wasn't. And I think in this case it would be better if the app was not in system but the binaries remained since he cannot get into the OS he will not be able to grant permission..but without. su command should work still
Thanks for the input. Wiithout a doubt, lessons learned here. At the very least, I never should have uninstalled Safestrap even if I wasn't planning on doing anything else to the system. I have the TWRP backup of my rooted stock, but with no way to use it now - useless.
I must have disabled some critical app or combination of apps that lead to the conflict, despite the care I thought I was taking. As far as Xposed framework goes, I never installed it manually. Maybe it is packaged in with one of those apps? The other thing I wondered about was whether disabling wireless could have led to a conflict. Using the Toolkit has been reported to lead to a bug where the system can crash when trying to enable wifi without first enabling bluetooth.
Either way, all I had to do was leave safestrap alone, just in case. F.
All of your help and feedback has been appreciated!
Wow. Well, I have adb access. After mutliple unsuccessful attempts on Windows and Linux, I was able to fire up an old MacBook and established an adb connection in 10 minutes. Unbelievable! The list of installed packages doesn't show any third party packages. Can I push and install Safestrap through adb to get my backups up and running? Whar is the correct syntax for those commands? I have already got a replacement on the way, but I would like to try to bring this one back and unroot. On second thought, maybe I should just leave it?
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.