[Q] No status/notification bar on KF - Kindle Fire General

I have a rooted Kindle Fire running 6.2.2 and after I rebooted I discovered there was no Status bar or notification bar. I have no access to a computer at the moment so i cant restore but how do i get the bars back?
Thanks

As an initial response, I'd say that it all depends on how you upgraded to 6.2.2 and how you're rooted. I myself have never seen any issues like this after upgrading, so it seems to be something specifically related to your setup/process. We (and when I say we, I mean the other more experienced people on xda, than I) will need more into to attempt to help you diagnose this issue. As a final thought, I'd suggest rebooting a few more times and seeing if they somehow return.

I got the kindle with 6.2.2 alredy loaded. I had already been rooted for about a week before this happened. I am sure I rooted correctly, with Burrito3. Might this be related to having GoLauncher?

Did you use nolock or something of that sort to bypass the amazon lock screen?

Jdommer, that is what I was going to suggest. Did exactly that upon reboot after trying to change the lockscreen and installing nolock. No status bar Or back button.

Revolted 5 times, everything is A-OK now! Thank you.
Sent from my Kindle Fire using XDA

Related

[Q] auto-nooter 3.0.0 question

complete noob here, so sorry if i am posting i the wrong place. I tried rooting my nc 1.2.0 but it didnt take, i think i unplugged it too soon. so I did a complete wipe and afterwords the nc was showing my software rev as 1.1.0. I then followed the instructions for auto-nooter 3.0.0 and i got to this point:
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
so here is my problem. After enabling location services(step 9), when i hit next I get a prompt saying:
complete action using
home
softkeys
home simply takes me to the normal nc home screen and softkeys asks for superuser permission the first time and afterwards also goes to the nc home sceen. i have wiped and re-rooted 3 times now with exactly the same results. am i missing something or doing something wrong? is there a different method for rooting that I should be using instead? should i attempt to go back to vers. 1.2.0(not sure how I would do this)? any help anyone could give me would be greatly appreciated as my kids are dying to use the nook and for me to be done "hogging it" thanks in advance
its fixed
ok not sure what gives, but i rebooted again and it seems to work fine now, other than not many apps in the market. I dont know how to delete this post so i just replied. mods feel free to delete

[Q] Hit a snag

Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
tangler27 said:
Hey guys. I rooted my M a couple days ago (5th or 6th device ive rooted) and am having some trouble this morning.
Everything seemed to be fine, I got rid of some crapware, grabbed droidwall, font installer, etc. The only major(?) change i made was putting safestrap on the phone. Afterwords, I rebooted and seen that there was no "splash screen" show up like the directions said there would be, so i figured it didnt work. This was a couple days ago. I didnt have any problems with the phone starting up at all until I changed the font a couple times. The first time, I changed it, rebooted normally, and everything changed over and appeared normal. After a few minutes of looking through the options again, I found one I liked better and installed that one. Reboot - stuck on the boot screen. Bummer. Tried to get it to start back up and it always does the same thing.
So I did some reading and am currently charging up my phone and downloading the razr_M_utility to restore and start over. Not sure what I did or why this happened. I dont recall making any other changes that could have caused it. I did use uninstall master to uninstall some of the bloatware, and thought that maybe I got rid of something that i wasnt supposed to. However, I have rebooted a few times since then and its been fine until now. Plus I'm pretty sure that I didnt uninstall anything to cause a problem.
Any additional thoughts on this would be appreciated. Like everyone else, im learning as i go! thanks
Click to expand...
Click to collapse
Utility is gonna take care of it for you...I'm certain. I cant think of anything that caused it though. That's kinda weird. But if I were you I would just stick with the stock ROM with that issue and just troubleshoot it and if it happens again...hit it with the utility again
Also if you don't mind losing camcorder the 4.2.2 ROMs are great and don't require safe strap as Kong as you unlock boot loader through the utility. But will void your warranty.
Good luck! And follow those instructions on Matt's utility perfectly!
Sent from my XT907 using xda app-developers app

[Q] Tried to update to cm10, couldn't boot, tried to restore to mnooter or cm7, help?

Hi all. I used to mess with my Nook Color a lot around a year and a half ago but recently was just using it to read and occasionally browse. I'm 99% sure I was working with just a nook which was used with manual nooter, so that I had the Google Play store and Zeam launcher with stock B&N as well. I was having issues with things "not being able to update" so I tried to mess around, only realizing too late that I wasn't really interested in cm10 and wanted to stick with zeam. Since then I've been trying to get back to how I started but I'm failing miserably. I've so far tried wiping/factory resetting my device. Installing cm7 from zip, resetting everything using the guide here and installing 1-4-1 cam oc zip from here and still I fail. I can get into the set up screen, but when the device will not find any wifi signal and then freeze without allowing me to type it in under "other". Honestly I'm not sure what else to do now. I just want my nooted device back -__-.
Please let me know if I can submit any more information that can help solve this problem. Thank you for your time.
I'm literally infinitely stuck staring at this screen.
Managed to fix everything. Used section A15. Enjoy anyone who ran into similar trouble.

How I got rid of constant reboots

Hi guys!
My Note 8.0 had the problem of rebooting whenever an app crashed. The screen would just display the status bar, the rest of the screen filled black. The device did not react to taps on the touchscreen, and after some 30 seconds, the device just started to reboot.
A quick Google on the topic led me to a few threads where people seemed to have had similar problems, but only resolved them by changing their device - but I did not want to give my new Note away
I had rooted my device right after I had bought it using the simplest possibility - Framaroot. The Aragom exploit had worked immediately and I was enjoying root on my new Note 8.
As I realized that the rebooting problem was not just a random event, but happened every time an app crashed, I started suspecting my root of being the problem. I unrooted the device again using Framaroot, and run a small app I wrote that does nothing but crash with a NullpointerExpception. This test app had led to a reboot on the rooted device, but after the unrooting, the screen only froze for a short amount of time, then a message was displayed saying the app crashed - hurray, no reboot.:victory:
Just to test, I rerooted using the same procedure as before, and the reboot returned.
At that point, I knew how to get rid of the reboots. But still, I wanted to have root access on my device.
Solving the problem was as simple as choosing SuperSU in Framaroot instead of Superuser. Once I had chosen this option in Framaroot, the reboots seem to have gone.
I don't know if that was a known bug of SuperSU (don't know the version that came with Framaroot).
I hope this helps anyone with similar problems.
Also, I am curious to hear if anyone else has made the experience that rooting with Framaroot, choosing the Aragom exploit and Superuser as the superuser app led to frequent crashes?
There are two different proven and stable root methods posted in the note 8 original development subforum by trusted and well known devs. If you use rooting methods posted outside of xda or elsewhere, you are looking for trouble.
Sent from my GT-N5110 using Tapatalk 2

Help bootloader error 01 reset device

Hello,
I bought the Android yoga book a week ago and was really happy with it. I unlocked the bootloader and rooted it.
The last few days I have been getting a lot of issues with the holo keyboard and the speakers and want to return/replace the yoga book.
I unrooted the tablet, re locked the bootloader, turned off the option under developer settings and reset the device.
However evegytime I boot, I am getting the bootloader error 01 device integrity cannot be verified.
How can I fix this issue?
Is there a stock firmware I can flash that will reset the device?
Thanks
Karthik
Why are intrusive ads - such as have begun to appear here on XDA - always so stupid and irrelevant? Always micky mouse oufits pushing micky mouse products? Really lowers the tone of the XDA website, yes?
zamzenos said:
Why are intrusive ads - such as have begun to appear here on XDA - always so stupid and irrelevant? Always micky mouse oufits pushing micky mouse products? Really lowers the tone of the XDA website, yes?
Click to expand...
Click to collapse
How about giving uBlock a try?
Before anybody starts to bark. I know Newspapers, Magazines or this kind of sites live from Advertising. But one thing is adding some Ad's, another having almost more Ad's than content... IMHO
Hey guys,
There are other threads where you can talk about ads, can anyone help with my issue?
Currently stuck with an unusable tablet.
karthikc24 said:
Hello,
I bought the Android yoga book a week ago and was really happy with it. I unlocked the bootloader and rooted it.
The last few days I have been getting a lot of issues with the holo keyboard and the speakers and want to return/replace the yoga book.
I unrooted the tablet, re locked the bootloader, turned off the option under developer settings and reset the device.
However evegytime I boot, I am getting the bootloader error 01 device integrity cannot be verified.
How can I fix this issue?
Is there a stock firmware I can flash that will reset the device?
Thanks
Karthik
Click to expand...
Click to collapse
for clarification...does it boot after the message or does it stop with that bootloader error?
danjac said:
for clarification...does it boot after the message or does it stop with that bootloader error?
Click to expand...
Click to collapse
It boots up, but my holo keyboard has a hardware defect. I can only use it in tablet mode with the keyboard disabled.
As soon as I switch it to laptop mode and the keyboard is enabled it starts acting wierd. Even without touching it random key presses occur, it keeps opening Google app closes my other windows etc
I have already done a factory reset but same problem.
When I return it, because of that bootloader error they will say that they won't exchange it
I want to restore the device to factory state so I need help how to get the bootloader back to stock.
Thanks
karthikc24 said:
It boots up, but my holo keyboard has a hardware defect. I can only use it in tablet mode with the keyboard disabled.
As soon as I switch it to laptop mode and the keyboard is enabled it starts acting wierd. Even without touching it random key presses occur, it keeps opening Google app closes my other windows etc
I have already done a factory reset but same problem.
When I return it, because of that bootloader error they will say that they won't exchange it
I want to restore the device to factory state so I need help how to get the bootloader back to stock.
Thanks
Click to expand...
Click to collapse
see here: https://source.android.com/security/verifiedboot/verified-boot
maybe unlock it again, flash a complete stock rom (with all its seperate partitions) which wasn't touched by root at all (did you make a backup using twrp). relock.
you could also download a stock rom from a website called 'easy-firmware.com', but you probably need to purchase it. still then i don't know whether just unlocking and locking the bootloader has already been enough to trigger the warning
if it doesn't work, well, then that's exactly what 'verified boot' is for...
hope it works.

Categories

Resources