Related
Every time I install a launcher, either ADW and launcher pro and restart, I get the Galaxy S logo, then an infinite black screen. The only way (I know of) to fix it is to do a factory reset, which obviously sucks. I have never gotten a launcher to work.
Anyone know what my problem is and how to fix it?
I have a US Cellular Mesmerize, rooted, clockwork mod, and the 1124_test_novoodoo kernel.
Thanks!
Update: I tried again to install Launcher Pro, but this time installed Home Switcher before shutting down. I set LP as my default launcher in Home Switcher, and launched it. It worked fine. However, after restarting the phone, I again have the black screen and lit up keys.
I had this happen the other night on my rooted superdark superfast fascinate. I just pulled the bat, held down both volume keys, held power until I saw samsung and let go of the power. then I loaded a backup and all was fine...
[SOLVED]
It's working now, I recovered again, restored with Titanium Backup, and tried again with Home Switcher, and this time it worked. Not sure what was up, but problem solved.
Same problem with additional wrinkle
I'm having the same problem, except that I haven't yet successfully got CWM to work on mine (so no ROM backup yet). Do you know of any way to fix this without restoring a backup first?
I500 Mesmerize
Rooted
OCLF v1+
Home Switcher
Launcher Pro
Visual Task Switcher
(Problem started after installing VTS)
All you have to do is hit search button on soft keys and find launcher pro or adw and open it and set it as default.
Sent from my SCH-I500 using XDA App
Hello all,
Admittedly, I am a noob. Ive searched the boards for similar solutions to mine, but to no avail. Here is my situation:
I rooted my kindle fire using burritoroot3 and worked beautifully. I had no problem with the root or the process. I came across an ICS launcher that I found good enough to install on my device. I installed it, and instead of testing to see if it would crash, I checked the "use this as default launcher" or something similiar box and now even after hard resetting m KF, and rebooting multiple times, every time it starts up, I get the message
"Sorry
The application ICS 4.0 Launcher (process android.process.acore) has stopped unexpecedly. Please try again
Force Close. "
m
I would like to know if this is fixable or if there is a way to revert back to the other launcher or uninstall the ICS 4.0 one and be able to use it again. I guess this is a "semi-brick" because it loads up fine, doesn't bootloop or anything.
I want to thank you guys in advance even if you are unable to help me!
Use root explorer move the apk from data/app to system/app then reboot
How would I do that? I cant access anything on my device. As soon as it starts up, it force closes on me right after i slide to unlock...
if you have twrp installed you can boot into twrp and have adb commands available
then you can use adb to copy the file ...
Many of us have know that the newest update that was push 2.0.5 break root. Well, for those who didn't know, now you know. Let's me be clear, there is NOTHING TO BLOCK THE OTA UPDATE, unless you build your own firewall. That said, the mod that we had was to use sql and turn automatic OTA into manual thus unless you were looking for it, it shouldn't. Or something you did may accidentally turn it back to automatic.
That said, we had one report of successful revert back to the older firmware here from 2.0.5. I have made a suggestion to manually force the system to fail the boot 8 times and do a full wipe. And this should revert it back to the original firmware that came with the Nook HD/HD+. Well, in the future, this may no longer be the case, as newer Nook may come with 2.0.5 out of the box, but let's do this one step at a time, we aren't there yet and maybe better solution will come later. So, if you accidentally updated to 2.0.5, you should try the following.
Backup your naughty stuff that's on the internal storage (even if they are not naughty, do it so anyway)
Force the nook to fail at least 8 times. First you power the device off then hit the power button, and when it's trying to boot, hold on to the power button, and I think about 10sec after it will force poweroff. You timing have to be quite good and make sure it's not getting a success boot. You basically have to do that at least 8 times.
If you successfully did all that, it should revert back to the original firmware. I know that the 8 boot loop will reset it back to 2.0.0 from 2.0.2 because I did that before.
Try rooting it again.
I hope this help.
Interesting, I'm going to try and force the 8-loop reboot and set if I can get back to 2.04. I think then I also have to skip the out of box registration process as this automatically updates?
it Works
Confirmed !!
I have got my new Nook HD+ yesterday, and before I could root it, it was automatically updated to 2.0.5 by itself today.
So I did the 8 times boot manually, and the system was reset to the original firmware--2.0.4.
After the first boot by skipping the OOBE, I followed the "All-in-one" from someone0, and it works perfectly now with ADW launcher.
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
haym said:
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
Click to expand...
Click to collapse
You still need to run superuser once, did you do that?
Thank you for this very much. Is there no way to prevent updating to version 2.0.5 again? I came home, and my brother was playing on it, he told me something happened. I took a look, and it was updated to 2.0.5. Is there anyway to prevent it again in the future? Will the all-in-one basically disable updating? Since I did install that previously, and the version was still updated.
Sorry for the bother, and thank you very much. I will look into setting up a firewall.
Thank you again.
EDIT: I've conducted the 8-boot loop, and it should have loaded an earlier firmware; however, how would I bypass registration, or the version update check after the 8-boot loop? Thank you.
hiddenG. I had similar issue, I wanted to avoid update so I did a reset, but let it go too far and it updated me to 2005. I then did the 8 time interrupt and got back to 2004. I read here to google "nook color bypass OOTB" as the steps are the same for HD+.
It works
Only thing I'm having trouble running allinone. I don't think I'm doing it right. THe unregistered hd+ lists you as "test" and you have connectivity but no browser. I'm figuring I need to sideload a launcher and I'm looking into how to do that. I do have adb.
If you've registered you might have to reset and catch it as soon as you get to the language screen. You hold volume up. and touch lower left, then lower right to bring up "factory" screen. Then, holding vol up, touch lower right to bring up bypass OOTB.
Dave
Mine automatically updated even though I had automatic update blocked with sqlite. Furthermore, I no longer have access to content I previously purchased on that nook! I can't even download the nook app to fix, it keeps crashing when trying to sync.
Ps, if I re root using reset and skip oobe, then I still won't have access to my content, no?
Sent from my BNTV600 using xda app-developers app
I guess not, you're not registered at all.
dave
Thanks dbrons, that solved my problem. Thank you very much.
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
I also have the same question.
In addition, is there any way to get the "TEST's NOOK" text in the notification bar to be replaced with my own name?
someone0 said:
... unless you build your own firewall.
Click to expand...
Click to collapse
I'm actually curious if this would work. When it suddenly went into 'must get 2.05' mode and I 8-reset it, I disconnected internet right after letting it register...and it pushed me into a loop trying to check for updates and wouldn't proceed.
Any suggestions on domains to be blocked if I were to try this again?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
+1
And also, is there any way to get rid of the App Update notifications. There are some that I don't want to update but the notifications keep coming back after clearing them.
So pissed off now....for no reason, when booting up this time my Nook went into a boot loop and reset itself! It wiped everything from internal storage, effectively killing off hours I had spent last night getting everything set on it with apps and root. (this was all after using the All-in-one batch file which supposedly turned off automatic OTA updates)
someone0 said:
You still need to run superuser once, did you do that?
Click to expand...
Click to collapse
Yes, I did, and it works now, Thank you
I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root.
Quote:
"I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root."
This was the exact procedure that worked for me, other than the fact that my Nook HD+ 8 boot reset to 2.0.4. So its definitely a workable solution until the awesome devs come up with a true solution!
Sent from my BNTV600 using xda premium
can connect to pc
i got it to connect once and adb reconized it i was able to see its serial number by doing adb devices and then tries root and after the first boot my computer would not fully see it it would pop up in my computer and then dissappear it would continue to do this while i had adb enabled after i turned this off it would stop and the nook would show up in my computer but as soon as i turned adb on it would go all crazy and show and dissappear in my computer any help here would be great
Just sit tight I'm sure people are working on root for 2.0.5.
someone0 said:
Just sit tight I'm sure people are working on root for 2.0.5.
Click to expand...
Click to collapse
i have bypassed the update im on 2004
I've always been a fan of the stock launcher since I never cared much to use settings available in custom launchers to tweak settings. However, with the new Nova Prime I really wanted to give gestures a try. After hearing great things about the launcher I decided to purchase the app and start fiddling with it. Overall the launcher is very fast, stable, and the homescreen gestures are awesome.
However, I'm noticing that immediately after unlocking the phone the screen flickers once before opening the homescreen. I've tried disabling Nova launcher to see if the stock launcher did this as well. However, as I suspected, the stock launcher fluidly fades from the lockscreen to the homescreen with no flicker at all.
Is anyone else experiencing this issue? Is there a setting I can adjust to fix this? I'd love to keep using Nova but unfortunately this flicker is annoying me.
Thanks in advance.
No issue's to report with nova launcher that's the only launcher i use:good: don't like stock I uninstall it whenever i flash a new rom. Some guys put nova into there roms. I have the prime version. Do you have your animations on? You could try disabling the animations if that helps..
yyz71 said:
No issue's to report with nova launcher that's the only launcher i use:good: don't like stock I uninstall it whenever i flash a new rom. Some guys put nova into there roms. I have the prime version. Do you have your animations on? You could try disabling the animations if that helps..
Click to expand...
Click to collapse
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
sn0warmy said:
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
Click to expand...
Click to collapse
Nice I'm glad it worked for you that's the best launcher:highfive:
sn0warmy said:
Thanks for the advice. I just disabled animations and it made the transition a lot faster, which I suppose I can live with. I just wish it was fluid during unlock like the stock launcher is. Aside from that it's perfect.
EDIT: I decided to follow your tactic and uninstalled the stock launcher, then wiped cache, dalvik cache, and fixed permissions. After restarting I'm happy to report that the unlock flicker has completely gone away. This is the case even with animations set back to 1x. I'm guessing the phone was trying to load the stock launcher for a split second before loading Nova Launcher, causing the slight flicker/delay. I'm a happy camper now, thank you!
Click to expand...
Click to collapse
I am experiencing the same issue now. i tried uninstall the stock launcher and then wiped everything else. but still didn't work for me. i was wondering what permission did you fix?? could you please tell me? thank you
indomi said:
I am experiencing the same issue now. i tried uninstall the stock launcher and then wiped everything else. but still didn't work for me. i was wondering what permission did you fix?? could you please tell me? thank you
Click to expand...
Click to collapse
I get this issue on all launchers, when using stock AOSP 4.3 and CM 10.1
Has anyone deduced what the problem is caused by?
patsmike said:
I get this issue on all launchers, when using stock AOSP 4.3 and CM 10.1
Has anyone deduced what the problem is caused by?
Click to expand...
Click to collapse
Ha! Forgot all about this thread. For me, every time I install a fresh ROM the first thing I do after initial setup is install Nova Launcher. After doing this I uninstall the stock launcher or the trebuchet launcher (on CM10.1 ROMs) and wipe cache/dalvik and fix permissions. After doing this I never see the initial screen flicker anymore and I've used this method with all sorts of ROMs.
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
sn0warmy said:
Ha! Forgot all about this thread. For me, every time I install a fresh ROM the first thing I do after initial setup is install Nova Launcher. After doing this I uninstall the stock launcher or the trebuchet launcher (on CM10.1 ROMs) and wipe cache/dalvik and fix permissions. After doing this I never see the initial screen flicker anymore and I've used this method with all sorts of ROMs.
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
Click to expand...
Click to collapse
You're kidding, seriously? That's it? That's so sad on Google's part (for such a terrible launcher)
But thanks for the hint, I've been searching far and wide for this answer - ill let you know if it works in 4.3 (I'm rooted). I'm surprised so little users notice this annoying stuff!
Sent from my Nexus 10 using xda app-developers app
sn0warmy said:
However, now that I'm on the stock 4.3 JWR66V image, without root, I am getting the same screen flicker again. I'm just dealing with it until an updated SuperSU or Super User zip is available which will allow me to root, install root explorer, and uninstall the stock launcher. I'm confident that going with the same procedure I mentioned above will solve the issue once again.
Good luck!
Click to expand...
Click to collapse
I followed your instructions but I still get flickering from time to time on stock rooted 4.3, though maybe less than before... Any other step that I may be missing that you didn't mention?
Sent from my Nexus 4 using xda app-developers app
Hi All,
Hope someone out there can help me.
So I have a Fire HD 10 that is about 1 year old and used fire Toolbox to have Microsoft launcher as a custom launcher and also did all the usual stuff like disabling ads etc and it worked perfectly.
Yesterday I got a new Fire HD 10 Plus for my wife (the latest version) on the black Friday offer
I have tried to do the same and install Microsoft launcher on it and everytime I hit the home button on the tab it just defaults back to the stock launcher.
I also have a problem with installing google services when it gets to installing Play store I get INSTALLATION FAILURE:[INSTALL_PARSE_FAILED_NOT_APK}
I am also unable to disable the OTA updates in the modify system settings menu.
The only thing that has worked so far is that the ad screen has been disabled.
Any help out there would be welcome.
Thanks
Does anyone have any information on when there will be an update to fire Toolbox so it works with the latest Fire HD's?
Just got a new one yesterday and it came with 7.3.2.2 version it will not load the custom launcher and reverts back to the stock launcher also unable to disable OTA updates.
Robnoon said:
Hi All,
Hope someone out there can help me.
So I have a Fire HD 10 that is about 1 year old and used fire Toolbox to have Microsoft launcher as a custom launcher and also did all the usual stuff like disabling ads etc and it worked perfectly.
Yesterday I got a new Fire HD 10 Plus for my wife (the latest version) on the black Friday offer
I have tried to do the same and install Microsoft launcher on it and everytime I hit the home button on the tab it just defaults back to the stock launcher.
I also have a problem with installing google services when it gets to installing Play store I get INSTALLATION FAILURE:[INSTALL_PARSE_FAILED_NOT_APK}
I am also unable to disable the OTA updates in the modify system settings menu.
The only thing that has worked so far is that the ad screen has been disabled.
Any help out there would be welcome.
Thanks
Click to expand...
Click to collapse
I have the same problem. Did you find something on how to fix this?
Robnoon said:
Does anyone have any information on when there will be an update to fire Toolbox so it works with the latest Fire HD's?
Just got a new one yesterday and it came with 7.3.2.2 version it will not load the custom launcher and reverts back to the stock launcher also unable to disable OTA updates.
Click to expand...
Click to collapse
I just got my Fire 10 9th gen replacement today and it came with 7.3.2.2
Luckily, my HD 10 Plus was bought in June worked great.
Hi,
The only fix I suggest is if your fire hd is less than 1 month old return it back to amazon for a full refund and get another and make sure you connect it to fire toolbox as soon as you get it to disable ota updates.
Have the same issue here, complete wipe of data and still there is the 7.3.2.2 installed. Really creepy that it directly came with my WIFI Setting INSTALLED...
Robnoon said:
Hi,
The only fix I suggest is if your fire hd is less than 1 month old return it back to amazon for a full refund and get another and make sure you connect it to fire toolbox as soon as you get it to disable ota updates.
Click to expand...
Click to collapse
I just got a new fire hd (8-10th gen) and will do this. Thanks. Two questions. 1) I already have downloaded the toolbox. Once I connect my new Fire will the toolbox see it and activate or do I have to do something (e.g. reinstall it)? 2) Does the toolbox prevent Fire from auto installing new s/w versions? TIA
Robnoon said:
Hi All,
Hope someone out there can help me.
So I have a Fire HD 10 that is about 1 year old and used fire Toolbox to have Microsoft launcher as a custom launcher and also did all the usual stuff like disabling ads etc and it worked perfectly.
Yesterday I got a new Fire HD 10 Plus for my wife (the latest version) on the black Friday offer
I have tried to do the same and install Microsoft launcher on it and everytime I hit the home button on the tab it just defaults back to the stock launcher.
I also have a problem with installing google services when it gets to installing Play store I get INSTALLATION FAILURE:[INSTALL_PARSE_FAILED_NOT_APK}
I am also unable to disable the OTA updates in the modify system settings menu.
The only thing that has worked so far is that the ad screen has been disabled.
Any help out there would be welcome.
Thanks
Click to expand...
Click to collapse
I had the same issue on my Fire HD 10 with Fire Toolbox V25.2. I reran the install by reopening TB and clicked on the Google Services option and it installed completely on Fire OS 7.3.2.2. Hopefully, this will solve your Plus install.
Hi - I need to remove everything Amazon on my tablet - disable OTA - flash it completely out of this universe. Whatever it takes I must turn this amazon tablet into an Android one. Please, has anyone got the guide for me to do this properly? I am aware of some update that disabled the feature to disable OTA in toolbox.
Thank you
Hi - I need to remove everything Amazon on my tablet - disable OTA - flash it completely out of this universe. Whatever it takes I must turn this amazon tablet into an Android one. Please, has anyone got the guide for me to do this properly? I am aware of some update that disabled the feature to disable OTA in toolbox.
Thank you
Would require you find both a Custom Recovery and a Custom ROM, both suitable to tablet.
I have a Fire HD 10 (9th gen). I did a factory reset.
Using Toolbox V26.1, after I install Disney+ from Hybrid apps it is asking me to signup and pay a monthly fee.
The toolbox says it could be used without having to register.
Am I doing something incorrectly or am I not doing something I'm supposed to do?
I received my Fire 10 yesterday. When I booted it, it scared the hell out of me how they already knew everything about me. I immediately thought it was the most disgusting device I've ever purchased, because of the software, but then I used fire toolbox and thought I was in heaven, except when I opened it today, I realized that I was in hell. Amazon had reset the whole tablet but left the Google apps. I should have known it was too good to be true. I stopped rooting after marshmallow and will now have to learn it all over again.
picassokat said:
I received my Fire 10 yesterday. When I booted it, it scared the hell out of me how they already knew everything about me. I immediately thought it was the most disgusting device I've ever purchased, because of the software, but then I used fire toolbox and thought I was in heaven, except when I opened it today, I realized that I was in hell. Amazon had reset the whole tablet but left the Google apps. I should have known it was too good to be true. I stopped rooting after marshmallow and will now have to learn it all over again.
Click to expand...
Click to collapse
Same problems here! I got the 9th gen hd10. They know everything about me! Please let me know if you find a solution. I am interested in the fire toolbox, and would like to try it. Where to download the latest version and instructions? Thank you!
can u also help me i have an amazon 11th gen 2021 tab. bought just this month from lazada Phils. i already disabled the OTA and change the screen lock unfortunately I cannot downgrade the fire launcher and change it from the launcher from fire toolbox. it has the latest version of android because i accidentally clicked the update button. what could be the problem?
russell montojo said:
can u also help me i have an amazon 11th gen 2021 tab. bought just this month from lazada Phils. i already disabled the OTA and change the screen lock unfortunately I cannot downgrade the fire launcher and change it from the launcher from fire toolbox. it has the latest version of android because i accidentally clicked the update button. what could be the problem?
Click to expand...
Click to collapse
The update is the problem. So no custom launcher as standard launcher anymore.