Hi,
when I reset my Optimus One with VolDown, Power + Home something got messed up and I received a phone where the desktop is not starting any longer.
After the above reset the setup screen appears where I can choose my language etc, but at the last step I get a force close message for the Setup Wizard every single time. When I then force close, the screen goes dark except for the status bar on the top.
After a while the phone autolocks and I can see the lock screen with moving grass and time etc. When I unlock, again the black screen with only the status bar on top.
The phone receives SMS messages and calls and shows the appropriate screen, just no desktop to choose any apps to start. I can even long press home and then get the recent apps screen with no apps to start.
Can someone help me to get my phone functional again?
Thanks.
Binser
seems like problem with your launcher app. use adb push command to push new launcher in your phone.
no debug
fundoozzz said:
seems like problem with your launcher app. use adb push command to push new launcher in your phone.
Click to expand...
Click to collapse
Yes that would be a good idea if I could enable USB debug. But I cannot get to the settings where I could enable USB debug, therefore ADB push is not a possible option for me.
u can log into your google account on desktop and install any launcher app from playstore , it will automatically get installed on your cell if your data is on.
fundoozzz said:
u can log into your google account on desktop and install any launcher app from playstore , it will automatically get installed on your cell if your data is on.
Click to expand...
Click to collapse
Thanks again for ur input: But the VolDown Menu Power thing did a complete reset and therefore the phone is completely virgin, i.e. no google account is set-up.
While during initial boot the setup wizard comes up, I get the error message:
"The application Setup Wizard (process.com.android.setupwizard) has stopped unexpectedly. Please try again."
So I cannot setup a google account for this phone.
u may be able to go to contacts screen while on call. there u will have an option to add google account. try this n if this doesn't work try resetting your phone again.
Thank you! That did it! I called myself with another phone and during the call via the menu button I was able to go into the account section and add an account. Then the play store updated (some time is needed for registration to take hold on the play store web site) and then I installed the Go launcher via web install.
After I got access to the launcher, I immediately activated USB debugging in Settings > Application Settings > Development and also install from unknnown sources in Application Settings.
I wrote these details so that people with the same problem of corrupted launcher or setup wizard know what to do.
BTW before I tried numerous phone resets but none solved the problem.
Now I still have the following problem: To root a reset is suggested to have a clean file system. A reset however again gives me the above problem. How can I break that vicious cycle?
Again, thanks a million for your help.
Regards,
Binser
binser said:
Thank you! That did it! I called myself with another phone and during the call via the menu button I was able to go into the account section and add an account. Then the play store updated (some time is needed for registration to take hold on the play store web site) and then I installed the Go launcher via web install.
After I got access to the launcher, I immediately activated USB debugging in Settings > Application Settings > Development and also install from unknnown sources in Application Settings.
I wrote these details so that people with the same problem of corrupted launcher or setup wizard know what to do.
BTW before I tried numerous phone resets but none solved the problem.
Now I still have the following problem: To root a reset is suggested to have a clean file system. A reset however again gives me the above problem. How can I break that vicious cycle?
Again, thanks a million for your help.
Regards,
Binser
Click to expand...
Click to collapse
No need of reset or so, just root and install clockworkmod recovery via ROM manager app, choose optimus 1 old baseband even if u r on new coz the recovery for old baseband is much more stable.
NOTE:-
do not choose to boot into recovery from ROM manager,u might end up at emergency mode. instead use the key combo to enter into recovery.
don't choose to factory reset from phone menu once u have installed custom recovery, instead do that from recovery.
Thanks, hephappy's ICS CM9 is running well now.
There is only one problem, possibly because I did not get your advice about old baseband in time: Cannot make or receive calls/texts, but I am being asked for SIM PIN and the phone shows the carrier ID in notifications.
My phone has the 20d baseband - is that the problem? Do I need to upgrade to 20g or would that not matter?
Regards,
Binser
OK, I flashed the 20G baseband and the problems are now history. I can make an receive calls.
There was a problem when flashing: The phone did not reboot into recovery mode. I had to do that manually and disable the LG modem. Then when the process was done I the phone showed 20G baseband, but no IMEI and network. I solved that by using the saved NV2 file in a subdirectory of the LGMDP.exe and the NV Restore button on the program icon bar.
Now everything is fine.
Again, thank you for your help.
Ciao,
Binser
To get rid of Popup dialogs try pressing search button, it works for me
Sent from my sending thing.
My Prime is about to go off warranty so today I attempted to install the Unlock Device Tool app - without success.
The apk opens to the usual dialog - "Do you want to install this application? It will get access to: etc., etc."
The problem is that the Install button at the bottom of the dialog doesn't do anything. (The Cancel button works just fine.) I tried installing from both MicroSD and Internal Storage, with both touch-screen and track-pad, with keyboard attached and without, cold booted too. Nothing helps. And, yes, installation from unknown sources is enabled, though I even tried disabling and re-enabling. Tried installing a different apk and encountered the same problem.
I'm running JB 4.1.1 - 10.4.2.18-20121122. I recall having the same issue on one of the earlier ICS releases but it resolved after a later upgrade.
Can't find any previous discussion on this though.
Would sure appreciate a solution, if there is one. :fingers-crossed:
I found a workaround. Maybe it will help someone else.
I hit the "I" key on the keyboard, hoping that might select the Install option. Instead it selected "Cancel". (WTF?) So I hit the Tab key and the selection highlight shifted to Install. Finally I hit the Enter key and the app installed.
So now I am successfully unlocked, TWRPed, finally rooted again, and ready to try custom ROMs!
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?
Hi guys, new member so play nice
Just pulled my HDX 7 from out of a drawer and thought I could use it for music in my car.
Haven't used it once March of 2014 and it's stuck on software version 13.3.2.2... I remember using a tool to block OTA updates, and whenever I try to check for an update it says 'last update failed'.
Did a factory reset on the device in the hope it'd sort that out, but no avail. What I have now is when I go to set up the device after the reset, it won't come off the language selection screen. I choose a language, press okay, and it just bounces back. Rebooting does nothing. Managed to ninja tap into settings, update still doesn't work, and same problem after another reset.
Can you guys just point me in the right direction in terms of sorting out these problems, and then what I need to do to root, get recovery and install a custom rom (possibly cyanogenmod but I'm unsure if there's a supported build)
Thanks a lot guys, it's much appreciated.
You are actually quite fortunate that your HDX is stuck at 13.3.2.x as you can probably obtain full control over the device and separate from Amazon. I would advise NOT updating as you may get your wish and then be left with fewer options (although Fire OS is not horrible even unrooted). HDX is a very nice device that is somewhat hobbled by Amazon's adaptation of Android.
If you can "ninja tap" into settings try to enable adb (under device). That will allow you to root and block OTAs (do it again just to make sure). See this post and the ones that immediately follow for details.
Assuming you are successful you can install a true recovery (TWRP) and flash several ROMs including stock Fire OS. There are many who would love to get their hands on your device as those with more recent updates are far more difficult to customize.
On the other hand, if you simply want to stick with Fire OS and accept updates as dished out by Amazon you can probably flash one of the various 13.3.x images posted in this forum and then re-enable OTA. Reflashing Fire OS should address the language loop you are currently experiencing.
It's nice to have choices!
Ok so here is what happened. I had everything running fine on 4.5.3 with root, twrp, and google play installed. Then I decided to follow the instructions to upgrade to 4.5.4 OS and followed the instructions perfectly and everything seems fine except I do not have a nav bar. I do have a custom launcher installed but I am not using it at the moment because I am using ADB commands to get back to the home screen when needed. Can anyone assist me with directions to get my nav bar back????
Edit: Another thing I am noticing is when it boots it is always asking for me to choose a language and pick my wifi connection.
junglistknot said:
Ok so here is what happened. I had everything running fine on 4.5.3 with root, twrp, and google play installed. Then I decided to follow the instructions to upgrade to 4.5.4 OS and followed the instructions perfectly and everything seems fine except I do not have a nav bar. I do have a custom launcher installed but I am not using it at the moment because I am using ADB commands to get back to the home screen when needed. Can anyone assist me with directions to get my nav bar back????
Edit: Another thing I am noticing is when it boots it is always asking for me to choose a language and pick my wifi connection.
Click to expand...
Click to collapse
Weird. Not reported before with update. You have status bar? Anyway, the edit sounds like something wrong with settings. First try GatesJunior Debloater (http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294) and unblock everything except otaverifer and then reboot. If that doesn't fix both probs, for nav bar make sure expanded desktop is not on in custom launcher, and if you use Xposed turn off all modules and reboot. Also, you could test expanded desktop by playing a video from Amazon launcher (which expands screen), tap screen and see if nav bar shows. (Guess you know, can use input keyevent 4 from adb shell to send back-button press.)
If this doesn't help, please post OS version from settings, tell what happens after you set language and wifi, and list system apps you deleted, moved or froze before update. thx
DoLooper said:
Weird. Not reported before with update. You have status bar? Anyway, the edit sounds like something wrong with settings. First try GatesJunior Debloater (http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294) and unblock everything except otaverifer and then reboot. If that doesn't fix both probs, for nav bar make sure expanded desktop is not on in custom launcher, and if you use Xposed turn off all modules and reboot. Also, you could test expanded desktop by playing a video from Amazon launcher (which expands screen), tap screen and see if nav bar shows. (Guess you know, can use input keyevent 4 from adb shell to send back-button press.)
If this doesn't help, please post OS version from settings, tell what happens after you set language and wifi, and list system apps you deleted, moved or froze before update. thx
Click to expand...
Click to collapse
Well I was on OS 4.5.4 and I tried everything you just said and had no luck. So I decided to to upgrade to the 5.0 developers preview. Now I am stuck as I can't get to the stock recovery with the volume+ and power button. Now I am stuck. I need the stock recovery img so I can flash via fastboot. If anyone can help me out with that I would really appreciate that. I need it so I can downgrade back to 4.5.3 via the adb sideload method. Please any help will be much appreciated.
I'm also having this issue. On 4.5.4 and when I start the reboot it will get held up at asking my language and then having to reconnect to my router. Basically it acts like I'm installing it for the first time and won't go to the Amazon Launcher. If I go into adb shell and use "am start -n com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher" it drops into the Amazon Launcher but still doesn't bring up the navigation bar. I've tried using TWRP and sideload a different/new copy of the firmware but that crashes shortly after I get around 20-25% through. Anyone got any tips?
ROMAddiction said:
I'm also having this issue. On 4.5.4 and when I start the reboot it will get held up at asking my language and then having to reconnect to my router. Basically it acts like I'm installing it for the first time and won't go to the Amazon Launcher. If I go into adb shell and use "am start -n com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher" it drops into the Amazon Launcher but still doesn't bring up the navigation bar. I've tried using TWRP and sideload a different/new copy of the firmware but that crashes shortly after I get around 20-25% through. Anyone got any tips?
Click to expand...
Click to collapse
This may work: http://forum.xda-developers.com/showpost.php?p=61941315&postcount=45
DoLooper said:
This may work: http://forum.xda-developers.com/showpost.php?p=61941315&postcount=45
Click to expand...
Click to collapse
You. You're awesome. Thank you! Been trying to rectify that all freaking day.
All thanks go to @bibikalka. I just know where b's answer's are!