I have a NT and tried a couple of times to do the 1.4.1 rooting procedures found on this forum but never could get my audio back on the device. So, I decided to go another route...go back to stock 1.4.0, root and then block the updates.
I went to here and installed and ran the hijacker:
http://forum.xda-developers.com/showthread.php?t=1419598
However, my software version still shows 1.4.0. Doesn't the hijacker set it to 9.9.9?
Nope
After finding and watching the videos, I see that I had the wrong impression of what Hijack was supposed to do even though I installed it.
So instead I purchased Titanium backup, went in and started freezing DeviceManagerService 2.3.4.
It's been in the process of freezing for 20 minutes now. Any idea how long this should take?
Thanks!
larrynooktb said:
After finding and watching the videos, I see that I had the wrong impression of what Hijack was supposed to do even though I installed it.
So instead I purchased Titanium backup, went in and started freezing DeviceManagerService 2.3.4.
It's been in the process of freezing for 20 minutes now. Any idea how long this should take?
Thanks!
Click to expand...
Click to collapse
shouldn't take that long, make sure usb debugging is checked, both of the usb debuggings. as a precaution check usb debugging once, uncheck it, and check it again to make sure it stays for the rest of the time you have your NT on. This only applies to the top usb debugging option. hope this helps!
Checked
Ok, I went in and noticed that the USB debugging was not checked so I checked it.
The freeze is still running. Should I turn my NT off and retry again?
Update
I restarted the NT, went in once again to confirm the USB debug settings.
When I went back into Titanium backup and checked, the device manager was frozen, so maybe it was the UI that wasn't updating.
The software version now is 'Unavailable'.
Thanks!
larrynooktb said:
I restarted the NT, went in once again to confirm the USB debug settings.
When I went back into Titanium backup and checked, the device manager was frozen, so maybe it was the UI that wasn't updating.
The software version now is 'Unavailable'.
Thanks!
Click to expand...
Click to collapse
Yeah, mine behaved this same exact way. I installed "Button Savior" from the market and not I have a "back" button I can get to when ever I need it.
Button Savior
I also installed Button Savior but can't get it to show up on any of my screens. Not sure what's up with it, didn't have any permissions problems installing it.
Thanks!
Related
I recently purchased an Optimus T and rooted it with z4root and then installed Titanium Backup to delete some of the preinstalled apps, like the Pacman Demo.
As I was removing each app, (~5 at this point) the Home button suddenly stopped working, followed by total phone death. Even after factory reset, when I was trying to access the phone, eventually I was shown a "... setup.exe stopped responding..." (or something like that) message and my phone just stayed stuck on the booting screen (android) every time I restart (w/o entering factory reset).
Does anyone have any ideas, or know which apps can prevent the phone from booting properly? A list of safe apps to delete would be helpful too. I thought I was pretty cautious with removing only non essential apps, but it seem bricked. Thanks again!
daramji said:
I recently purchased an Optimus T and rooted it with z4root and then installed Titanium Backup to delete some of the preinstalled apps, like the Pacman Demo.
As I was removing each app, (~5 at this point) the Home button suddenly stopped working, followed by total phone death. Even after factory reset, when I was trying to access the phone, eventually I was shown a "... setup.exe stopped responding..." (or something like that) message and my phone just stayed stuck on the booting screen (android) every time I restart (w/o entering factory reset).
Does anyone have any ideas, or know which apps can prevent the phone from booting properly? A list of safe apps to delete would be helpful too. I thought I was pretty cautious with removing only non essential apps, but it seem bricked. Thanks again!
Click to expand...
Click to collapse
About list off apps, I have to agree. Even it there is litle problem with dependencies, some minimum describe of these issue will be great!!
So, about your problem - I think, that you will have to download original ROM and do flashing with KDZ_FW_UPdater. (search on xda for more information).
But definitely, if it's possible I would try to install custom recovery throw adb shell (android SDK tools) and do backup of system for possibility to recovery or saving at least few data, and after try wipe and install one of custom ROM.
This happened to me after I tried deleting preinstalled apps on my Optimus One... Sent it in for repairs since it just stopped working. The tech guy said he did a "software update" and everything is good as new (except for the LGMITS error once in a while)
They didn't even bother trying to fix mine. They just told me to send it in and gave me a replacement.
So I finally figured out what I did wrong - basically when I was doing the deleting, I accidentally deleted the LG Home app, which effectively deactivated my (duh) home button and effectively stopped everything from functioning properly. For some reason I thought it was just a simple link from my phone directly to the LG website, as would happen with new PCs very often. Well... won't be doing THAT again.
However, my web2go button isn't working. I have to force quit every time I try to click on it. Can I just get rid of it or will it just give me more trouble later on?
At least you knew what went wrong with yours... I was just erasing CarHome and Layar and the LG App Adviser among other things i wont be using like Twitter and Latitude.
And they even gave you a new one x__x I had to wait 5 days before everything was good as new. After the first fix, USB debugging and mass storage stopped working so I sent it in for another "software update"...
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!
Hi all,
Just had my new S3 for a few days and loving it so far apart from 1 thing.
I updated the firmware the other day via Kies but now the MTP driver fails to install.
I've uninstalled Kies, drivers, downloaded it again and reinstalled but nothing. Cable is fine and its only happened since the update 2 days ago.
Any ideas as i cant connect the damn thing to my PC now to take pics off, put music on
Cheers
Anyone?
neo6776 said:
Hi all,
Just had my new S3 for a few days and loving it so far apart from 1 thing.
I updated the firmware the other day via Kies but now the MTP driver fails to install.
I've uninstalled Kies, drivers, downloaded it again and reinstalled but nothing. Cable is fine and its only happened since the update 2 days ago.
Any ideas as i cant connect the damn thing to my PC now to take pics off, put music on
Cheers
Click to expand...
Click to collapse
wiered
have you tried some other pc ??
I've had the same problems, and seem to have narrowed it down. I originally had work email on my phone and it caused my phone to not connect to the PC due to security policies. I removed the email and it started working again. However at some point it stopped working again. I had rooted my phone and so I thought maybe that had something to do with it. After trying everything, I found a thread that mentioned factory reset may help. I tried this and sure enough it came back. Until the next day. It stopped working again. I did a factory reset once more, and it started working again. This time I skipped google login (restore). I installed an app at a time and reset the phone. All working still, After a while I got the confidence to restore everything and so far, all working.
My best guess, is the google backups was backing up and restoring something that was causing the MTP driver to fail. It's definitely something on the phone that causes this problem (in my case at least). Since I went through a clean backup / restore cycle now, it doesn't seem to be happening.
Hope this helps!
try on another usb port,off/on usb debugging again,reboot phone ,troubleshoot connection error on kies ,then connect to try , make sure to use original data cable
pblagay said:
I've had the same problems, and seem to have narrowed it down. I originally had work email on my phone and it caused my phone to not connect to the PC due to security policies. I removed the email and it started working again. However at some point it stopped working again. I had rooted my phone and so I thought maybe that had something to do with it. After trying everything, I found a thread that mentioned factory reset may help. I tried this and sure enough it came back. Until the next day. It stopped working again. I did a factory reset once more, and it started working again. This time I skipped google login (restore). I installed an app at a time and reset the phone. All working still, After a while I got the confidence to restore everything and so far, all working.
My best guess, is the google backups was backing up and restoring something that was causing the MTP driver to fail. It's definitely something on the phone that causes this problem (in my case at least). Since I went through a clean backup / restore cycle now, it doesn't seem to be happening.
Hope this helps!
Click to expand...
Click to collapse
This workded for me!!!!! I had tried everything for 2 days but only this worked and I didnt loose root...
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
kratanuva said:
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
Click to expand...
Click to collapse
You are not the only one with that problem. I have the exact same issue. Process chewing up the CPU and if you kill it the process comes right back. Hopefully someone has a good answer as to how to fix it. I actually have 2 of the phones and one is rooted, second one is not. The unrooted phone does not have the same issue as the rooted phone.
I'm having the same problem with my Atrix. Phone is stock and unrooted. Never had an issue until I installed the latest update.
Well I got a response back from Motorola about the issue. These were their recommendations.
1. Reboot phone. Duh....
2. Uninstall any apps that you installed when the problem started. Uh, it was the OTA update... Cannot be uninstalled I do not think.
3. Clear Cache partition from Fastboot menu. That did not do anything.
4. Factory reset the phone. I hate doing that. Doubt it fixes anything but I will do it anyway.
I asked them about option 5 if 1-4 did nothing and he said call and talk to support.
Just an update...
Maybe someone knows how to just kill the process. It is obviously doing nothing as the phone is already updated to 4.5.145 according to the phone info.
I've just had a quick look around about the 'apply patch' process. Not that it helps you but this problem has been ongoing since at least android 1.6!!! Unfortunately solutions to the problem were few and far between - the main one would be to roll back the update you received (if you can).
Rooting and then trying to find the process and freezing the 'apply patch' process is another (again, I didn't find much about how to do that) as is unlocking the bootloader and putting installing a custom rom is another option for you. I know you don't feel comfy unlocking your bootloader but it isn't as bad as it sounds.
If you do decide to go the unlocking way then there are guides on here which will help you.
Edit: just seen this over in the 'general' section http://forum.xda-developers.com/showthread.php?t=2145316 ... the very same problem you are having.
Ok, just to hopefully keep this going I have tried these additional steps.
Root phone.
Unroot phone
Re-root phone
Try multiple startup program apps to kill it, none show anything besides installed apps.
None work. applypatch still taking 49% cpu
Maybe there is a way to edit androids startup config file to make it stop? Not a Linux/android guy so hopefully someone smarter than me has the answer to that.
If you've rooted the phone, you might as well have deleted or renamed that program... That's what I would do.
Same problem with my Atrix........I've been following this thread and have found a temp fix that works for me. I say temp as the applypatch process will show up again on reboot
1.) Gain Root Access
2.) Download OS Monitor from PlayStore (this will show you all processes running on Android OS)
3.) Run OS Monitor ...."applypatch" should be at the top of the list with a high Load % (Note: Under Settings enable ROOT mode)
4.) Long press on applypatch process and select kill process and allow superuser/root access...should terminate
This has been working for me so far so I signed up to share with you all.....hope it helps.
And heres to hoping for a more permanent:good: solution to this issue
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?