I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
First of all glad your using my theme
If you want to remove the classicnerd option from the menu then do :
Open terminal and type : rm /boot/uImage.ClassicNerd
Or if you have root browser go to /boot/ mount as R/W and delete the uimage.ClassicNerd
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
jowyboy said:
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
Click to expand...
Click to collapse
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
Click to expand...
Click to collapse
I like your post.
Just sayin.
Sent from my SPH-D700 using XDA
TedSamaha said:
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
Click to expand...
Click to collapse
Meh. It's not a big deal; it would just be nice to order it however I please. My CyanogenMod Nightly installation is now set as default, so meh.
gregory15 said:
I like your post.
Just sayin.
Click to expand...
Click to collapse
Thanks, dude!
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
bassrebel said:
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
Click to expand...
Click to collapse
You tried updating binaries?
Sent from my cm_tenderloin using Tapatalk 2
if by updating binaries u mean updating SU then I tried but it didn't let me because it says I need root... WTF? I tried checking under options -> developers options and put it to root abd+apps and still nothing is happening... :/
Open the SuperUser app itself, and check your settings there. Something might be changed.
Me, I use the Prompt option, and every once in a while I have to remove an app from the accepted list and let it load itself up and prompt me again. Maybe that'll help you (I hope).
THANK YOU!
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups...
--[Solved]--
Click to expand...
Click to collapse
Wow. Dude. Where do I start?! Thank you!!! This has plagued my kids tablet for months. Finally, this evening, I thought I would try and do something about it. This boot loader has been causing this tablet to force close after boot for months if it was left to boot up on the 'default' Classic Nerd ROM option (after I flashed another ROM).
Finally fixed.
Related
I REALLY need some assistance, think I screwed my phone, really want to avoid a hard wipe.
I installed Lockbot the other day, has some issues with dual lock layers (i.e. the lockbot app wasn't disabling my HTC lock so I had two unlocks.). emailed dev and he sent me a beta version to hopefully correct issue. I only received an apk file from him.
FYI I am on fresh 1.1, rooted.
I used the kitchen to puch this file: "LockBotPro_1.10.0_beta.apk" to /system/app.
The install went successfully, but later after a reboot I face a HUGE issue. The lockbot app is hanging upon reboot and will not unlock. At first I thought i would still be okay, I had ATK and Advanced Task manager both running at start up, so I can enter both of them through my notification drop down menu. I used both to kill the task-to no avail it is still locked. I tried to use advanced task manager to uninstall lockbot - to no avail, it cannot be removed.
Then I tried to pull back the file through kitchen, to no avail.
I don't know what to do. I cannot get my phone to unlock and i cannot pull the file off through adb or kitchen. DOES ANYONE HAVE ANY IDEA ON HOW TO FIX THIS??????
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
wtphoto said:
I would suggest pulling the battery and rebooting into recovery then use adb to cd to system/app and use rm to remove the apk that way and then boot the phone
Click to expand...
Click to collapse
I have tried to pull the file in both adb and in kitchen. Would it have installed as something other than the name I pushed it under?
Even if the phone is hard locking (kind of rare of android. even in all the stupid f'd up things I've done I've only hard locked my phone to the point that I couldn't even get in to adb once or twice) then the file system is still completely accessible while it's booting up. You can use the "pull any file" from the kitchen and check off that you want it to delete it after it's done. Just get it all queued up in the kitchen and then power on your phone. Once it gets passed the HTC logo wait a few seconds and then run the pull file from the kitchen. Should work just fine for you.
The alternative (if you are comfortable with adb) would be to boot your phone in to recovery (can also be done through the kitchen, even when it's in the middle of booting) and then type the following from a command prompt:
adb shell mount /system
adb shell rm /system/app/your-application.apk
FYI for future reference you should push these types of applications to /data/app. Your hard locks could either be caused by the fact that the beta just broke things, or it could be that you have a copy of it in both /data/app and in /system/app.
the problem is that you dont want to just pull the file all that does is create a copy of the file where ever you pull it to you need to use the rm cmd to actually remove the file and have you tried to do this from the recovery menu before the phone boots? I mean I am by no means an expert but commonsence says that if you do it in the recovery menu that it would be gone when the phone actually boots and the problem would be gone.
edit: sweet im not a complete noob anymore I was right about removing from the recovery. flipz explained it better though.
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
TF1984 said:
thanks flipz, I'm going to try this. I will try via adb first, then via kitchen. Last time kitchen gave me a message to "post" but I didn't figure I would catch you online. Hope you're still around in 15-20. thanks for the how-to!
Click to expand...
Click to collapse
I'll be here.
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
You have a nandroid backup... don't you? Actually what you can try doing is flashing fresh right on top of itself. You won't lose any settings and it will overwrite everything in /system/app.
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
TF1984 said:
I haven't made a recent Nandroid backup.
All of my third party apps are giving FC upon trying to execute any action within them. I think I might just reinstall each. I think something happened with my sdcard through this process trying to get rid of lockbot. Not sure.
If I flash fresh it wouldn't remove any data right, will anything change? I think I remember last time I flashed it I even retained my scenes and all, but I have a bad memory. I guess I'll give it a go.
Click to expand...
Click to collapse
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Flipz I swear one day I am going to make a sizeable donation to you. If I can only find some extra money.
I think you have helped in every issue I have had after rooting, there haven't been many but you are always helpful when I run into trouble.
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
TF1984 said:
Well I flashed 1.1 again, but it didn't help to fix the FC on every app.
Guess I will just remove and install each one by one. This will make for a good time to review each app and decide which I should part with for non-use.
Thanks again, my lock issue is resolved!
Maybe I'll try the lockbot again but install to app/data as you suggested in earlier posting.
Click to expand...
Click to collapse
Might be worth it for you to try clearing your dalvik-cache to see if it fixes your FC's. If that doesn't work then my guess is you are using apps2sd and the symlink got broken somewhere along the way.
And no problem.
Yes I am using apps2sd. I tried the davlik clear cache in kitchen earlier today in attempt to fix the lockbot (I don't know, figured maybe it would work since i have no idea what that does to begin with).
Question, I did pull my sd card out earlier while the phone was off. Then booted and it only went into a boot loop, is that likely to have caused the FCs?
Does that mean that I cannot ever remove the sd card at all or will always cause this problem...cause that would friggin suck a big one!
flipzmode said:
Yea so in general when it comes to the phone /system should remain untouched and /data is where all saved settings and market apps go. Obviously we change that by rooting the phone and creating custom roms. But that concept still applies when flashing a rom. It will only wipe /system and not /data (unless the rom dev does something wrong heh).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4942088&postcount=2 -- post #2 from the fresh rom thread from back in november.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
Click to expand...
Click to collapse
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
TF1984 said:
yikes.
I guess it is a gamble, do I want the space provided while keeping apps on my card (I do have A LOT of apps) or do I go the safe route?
Hmmm. thanks again. Quick question, earlier you said I needed to install that apk in data/app, not system/app. I pushed it back via kitchen to data/app and it isn't showing up anywhere. Was there an additional step I am not aware of?
Click to expand...
Click to collapse
Make sure you aren't forgetting the leading slash. /data/app not data/app. But no, nothing special. That should work. Although if using apps2sd you might want to push to /data/sd/app. It should work regardless because a2sd sets up a symlink but if your stuff is messed up then it might not be working right.
TF1984 said:
hmmm. I think I've really screwed something up.
I opened CMD, ran adb, here's where I am and what I have (fyi I get the same thing no matter in Recovery, boot or after normal start up)... and I use apps2sd
C:\android-sdk-windows\tools>adb shell mount /system
mount: cannot read /etc/fstab: No such file or directory
If I use Kitchen to pull file: It says "Files Deleted".
Now on my Hero, after fresh reboot...
Well maybe it's okay. But now many of my apps are giving FC error. AHH Crap!!!
That app is demonic... LockBot, I'm gonna get my moula back!
Click to expand...
Click to collapse
Type this command in to mount:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
That will mount the /system volume and put it in read-write mode.
Once you are finished deleting the file, type:
umount /system
Then reboot the phone.
Edit: If you want to mount the /data volume, type: mount -o rw -t yaffs2 /dev/block/mtdblock5 /data
Hi there
new to the touchpad and moboot and such but not new to hacking etc etc
i have searched and havent seem to find anything that is related to what i did....
i have successfully got android and such on my touchpad...
now my issue is i booted back into webOS and downloaded preware and cyboot... in cyboot i set it to default to boot into android. and the time out of moboot i set to 1 sec... the issue i am having is i cannot get into moboot anymore... its there but because its set to go into android right away there is no way for me to get into recovery or moboot at all
anyone know how i can reset moboot and get the timeout back to 5 secs or longer so i can choose my boot method, ex so i can get into recovery or webOS again...
thanks in advance everyone!
I think the cyboot app in PreWare will let you change the moboot settings from within WebOS.
Not sure if the timeout is one of the settings available though.
Edit: Sorry - didn't read original post properly. Now see you have used Cyboot but can't get back into it.
dmarchant said:
I think the cyboot app in PreWare will let you change the moboot settings from within WebOS.
Not sure if the timeout is one of the settings available though.
Edit: Sorry - didn't read original post properly. Now see you have used Cyboot but can't get back into it.
Click to expand...
Click to collapse
correct... i cant get into moboot...
i hit reboot or power down, and it just cycles right back into android... no way for me to get into moboot... thats my issue... i need to reset it in a way so i can get back into moboot
I recall there are some posts around on how to edit the moboot settings directly in android. One option may be reinstall moboot using ACMEInstaller?
dmarchant said:
I recall there are some posts around on how to edit the moboot settings directly in android. One option may be reinstall moboot using ACMEInstaller?
Click to expand...
Click to collapse
everything i have read, they say that reinstalling moboot and ACMEinstaller doesnt solve the issue
got a link to how to edit the files/settings on android?
This thread may give some pointers, but it looks like it is fairly advanced - http://forum.xda-developers.com/showthread.php?t=1399566&highlight=moboot+edit
I just did a search for 'moboot edit' - that may give you some more threads to follow.
Ok got it working now!
So what i needed to do was use root explorer to delete the moboot.next file and then edited the moboot.timeout file with text editor in root explorer and reset the time from 1 to 10
did a hard reboot with the power button and home button holding for 15secs and it booted into moboot!!
woohoooooo!!!!
I had to hose my Touch pad, and reinstall CM9 and moboot. Now it default boots to WebOS. I would have edited moboot.default but it's not there. The path im looking in is /boot/ which has other moboot files, but neither moboot.default nor moboot.timeout are there.
I'm using X-plore for root browsing, fwiw.
Ideas?
Thanks!
the john said:
I had to hose my Touch pad, and reinstall CM9 and moboot. Now it default boots to WebOS. I would have edited moboot.default but it's not there. The path im looking in is /boot/ which has other moboot files, but neither moboot.default nor moboot.timeout are there.
I'm using X-plore for root browsing, fwiw.
Ideas?
Thanks!
Click to expand...
Click to collapse
i assume can still boot into android , DL an app called Rom Toolbox Pro (free version) That should show the files and allow you to edit . Or in webos DL Cyboot from preware as that will also allow you to change default boot and time out.
I hope this helps
the john said:
I had to hose my Touch pad, and reinstall CM9 and moboot. Now it default boots to WebOS. I would have edited moboot.default but it's not there. The path im looking in is /boot/ which has other moboot files, but neither moboot.default nor moboot.timeout are there.
I'm using X-plore for root browsing, fwiw.
Ideas?
Thanks!
Click to expand...
Click to collapse
You can just create the files yourself. It looks like you know what to edit and how to edit it from there.
bananagranola said:
You can just create the files yourself. It looks like you know what to edit and how to edit it from there.
Click to expand...
Click to collapse
Thanks. I thought about creating it myself, but I don't actually know what the syntax should be. Would someone mind pasting the contents of theirs into the thread?
sstar said:
i assume can still boot into android , DL an app called Rom Toolbox Pro (free version) That should show the files and allow you to edit . Or in webos DL Cyboot from preware as that will also allow you to change default boot and time out.
I hope this helps
Click to expand...
Click to collapse
Thanks, but it's not an issue of being unable to see the files. I'm using a root browser. It's just that they aren't there at all...
the john said:
Thanks, but it's not an issue of being unable to see the files. I'm using a root browser. It's just that they aren't there at all...
Click to expand...
Click to collapse
What about just reinstalling moboot to see if that will generate them ?
the john said:
Thanks. I thought about creating it myself, but I don't actually know what the syntax should be. Would someone mind pasting the contents of theirs into the thread?
Click to expand...
Click to collapse
moboot.default (note capitalization):
Code:
CyanogenMod
moboot.timeout:
Code:
5
Sorry to double post, but another thing you might want to know: I think the timeout can only be a 0-9 value. I may be incorrect, but I think that a value above 9 will be ignored.
bananagranola said:
Sorry to double post, but another thing you might want to know: I think the timeout can only be a 0-9 value. I may be incorrect, but I think that a value above 9 will be ignored.
Click to expand...
Click to collapse
You can set a higher value for the timeout (mine is 15). I think it's 10 that you can't use, but not sure.
Make sure you have a CR/LF (press enter) at the end of the first line of each of those files. If it's just that, no enter, it could cause problems. They like the newline in order to work.
I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
richard head said:
I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
Click to expand...
Click to collapse
In webos, in pre ware, download cyboot. You can set the order of booting, and you can even set the time to first boot using this.
richard head said:
I have a touch pad that runs cm9 more or less without issue. However I used to rum a kernel known as bricked and it boots to that build automatically, even though it isn't there anymore. How can I set moboot to automatically run cm9 stock without having to hold the buttons, reset the tab and manually select it?
Click to expand...
Click to collapse
like above, install Cyboot from preware in Webos.
You can set all the defaults for moboot including time out and which os to boot by default
i tried it without issues.
Or, if you're comfortable, you can edit the moboot.default file in the /boot folder.
Using a file explorer with root privileges, make sure you are in r/w mode, long press on the file and select edit/open in text editor. Change the name to your current rom, guessing it's CyanogenMod (caps matter), double check that name though, you want it to be the same as it appears on your moboot menu.
Save the changes and you're done
Sent from my ThunderBolt using xda premium
you also should delete the uImage.* for the the old Bricked rom that you dont have installed anymore. it will be in the /boot directory.
chicle_11 said:
In webos, in pre ware, download cyboot. You can set the order of booting, and you can even set the time to first boot using this.
Click to expand...
Click to collapse
Where is this? I am having a tough time with this instruction. Are you referring to the Preware Homebrew Documentation app?
apicia said:
Where is this? I am having a tough time with this instruction. Are you referring to the Preware Homebrew Documentation app?
Click to expand...
Click to collapse
You have to install preware if you haven't already done so using webos quick install. ,after installing preware you will see it as an app that allows you to install lots of custom apps and tweaks..
https://www.box.com/s/4fe8d60f353300d91e2a
webos quick install
I am so confused . . .
I have a kindle fire hd 7. I rooted it today using the one/two step method and it worked beautifully. I tried a couple of different launchers (go launcher hd, adw launcher and apex launcher) and all worked fine. I decided to go back to using go launcher hd since I liked it the best. No problem. Switching and uninstalling worked great. Before I could finish reinstalling the go launcher hd and moving to the system app folder, I stupidly saw the new Next Launcher and tried that. Now my kindle is stuck on an endless "Next Launcher has stopped" cycle and I can't get it to stop. I have tried resetting to factory default and that didn't work.
The odd part is, even though I get the same error message every second (literally) the kindle will still work if I'm fast enough pushing the ok button on the error. I have taken 4 hours and navigated to the menu where I force it to close (didn't work), tried to find the es file explorer (didn't work) and no matter what I do, I can't get it to stop.
I hope that was thorough enough. Any tips?
Kindle 7" HD Safe Mode
twhitehead1081 said:
I am so confused . . .
I have a kindle fire hd 7. I rooted it today using the one/two step method and it worked beautifully. I tried a couple of different launchers (go launcher hd, adw launcher and apex launcher) and all worked fine. I decided to go back to using go launcher hd since I liked it the best. No problem. Switching and uninstalling worked great. Before I could finish reinstalling the go launcher hd and moving to the system app folder, I stupidly saw the new Next Launcher and tried that. Now my kindle is stuck on an endless "Next Launcher has stopped" cycle and I can't get it to stop. I have tried resetting to factory default and that didn't work.
The odd part is, even though I get the same error message every second (literally) the kindle will still work if I'm fast enough pushing the ok button on the error. I have taken 4 hours and navigated to the menu where I force it to close (didn't work), tried to find the es file explorer (didn't work) and no matter what I do, I can't get it to stop.
I hope that was thorough enough. Any tips?
Click to expand...
Click to collapse
This is a shot in the dark but try a few things:
1) Hard Reset. While the Kindle is turned on Press and hold the Power button for 20 seconds, ignoring any Shutdown Message. The Kindle will power off on a hard reset.
2) Safe Mode. Power the Kindle in Safe Mode. When the Kindle is OFF press the Volume Up and Down together. While pressing the Volume keys, press the Power Button button to turn on the Kindle, release the Power button within 3 seconds. Just don't let go of the Volume keys until the Kindle is fully powered up. You will see "Safe Mode" in the left hand corner of your screen.
What is the error?
prokennexusa said:
This is a shot in the dark but try a few things:
1) Hard Reset. While the Kindle is turned on Press and hold the Power button for 20 seconds, ignoring any Shutdown Message. The Kindle will power off on a hard reset.
2) Safe Mode. Power the Kindle in Safe Mode. When the Kindle is OFF press the Volume Up and Down together. While pressing the Volume keys, press the Power Button button to turn on the Kindle, release the Power button within 3 seconds. Just don't let go of the Volume keys until the Kindle is fully powered up. You will see "Safe Mode" in the left hand corner of your screen.
What is the error?
Click to expand...
Click to collapse
Tried the Hard Reset and the Safe Mode, neither worked. The message continues to pop up repeatedly.
The error itself is that after I tried to use the Next Launcher by putting it into the system/app folder like you would any other launcher to get it to do its things, it didn't work and now I get a continuous "Next Launcher Has Stopped" message that no matter how many times you press "OK" it keeps coming up, literally every second. The odd part is, I have been able to re-root the kindle and navigate it so I know I'm not bricked and I am 95% sure I am not soft bricked, though I could be wrong. I have managed to get ES Explorer back onto the Kindle and can navigate my way over time to the system/app folder. I have tried deleting the file and I get the "Error Deleting File" message and it continues. From what I can see, all I need to do is get this file deleted (and not try random untested things of course ) and if I can do that, it will be fixed. I just can't seem to get it deleted. I have tried both ES File Explorer and Astro File Explorer which are both still on my kindle. I have tried deleting it with the multi-select option in both but get that previously mentioned "Error Deleting File." I have tried moving it back to the sdcard/download folder with the same error. I have tried killing the task with Astro and ignoring it as well and that doesn't work. I am still working on this. I do realize as well that when this first happened I should have cleared out some files before I did the factory reset which also didn't work. However I was unable to get that file (Next Launcher) deleted which is why I went to the factory reset. After I managed to get the Kindle re-rooted, the only I haven't been able to do is get Superuser root access to the system/app folder to change permissions, again because of the repeated error.
It all comes down to the Next Launcher.apk file in the system/app folder that I can't get out. Long pressing anything doesn't work because of the repeated pop-up "Next Launcher has stopped." error mentioned above. The only way I can show you what it is exactly is to screw up your Kindle Fire HD 7 by downloading and putting the Next Launcher.apk file in the system app folder. That's literally all I did and now I can't get it to stop. I've even tried adding a second and third launcher to see if I could pick one on start up but that didn't work either. I even got ADW Launcher running and the error still came up. I'm running out of ideas. I'm open to any ideas at this point. Thanks for your time with this btw. I really appreciate it. :fingers-crossed:
Since you have root access you can use adb to remove a system apk,
Use these commands:
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up a list of apk names on the device:
Code:
cd /system/app
ls *.apk
Hope this works for you.
adb shell
twhitehead1081 said:
Tried the Hard Reset and the Safe Mode, neither worked. The message continues to pop up repeatedly.
The error itself is that after I tried to use the Next Launcher by putting it into the system/app folder like you would any other launcher to get it to do its things, it didn't work and now I get a continuous "Next Launcher Has Stopped" message that no matter how many times you press "OK" it keeps coming up, literally every second. The odd part is, I have been able to re-root the kindle and navigate it so I know I'm not bricked and I am 95% sure I am not soft bricked, though I could be wrong. I have managed to get ES Explorer back onto the Kindle and can navigate my way over time to the system/app folder. I have tried deleting the file and I get the "Error Deleting File" message and it continues. From what I can see, all I need to do is get this file deleted (and not try random untested things of course ) and if I can do that, it will be fixed. I just can't seem to get it deleted. I have tried both ES File Explorer and Astro File Explorer which are both still on my kindle. I have tried deleting it with the multi-select option in both but get that previously mentioned "Error Deleting File." I have tried moving it back to the sdcard/download folder with the same error. I have tried killing the task with Astro and ignoring it as well and that doesn't work. I am still working on this. I do realize as well that when this first happened I should have cleared out some files before I did the factory reset which also didn't work. However I was unable to get that file (Next Launcher) deleted which is why I went to the factory reset. After I managed to get the Kindle re-rooted, the only I haven't been able to do is get Superuser root access to the system/app folder to change permissions, again because of the repeated error.
It all comes down to the Next Launcher.apk file in the system/app folder that I can't get out. Long pressing anything doesn't work because of the repeated pop-up "Next Launcher has stopped." error mentioned above. The only way I can show you what it is exactly is to screw up your Kindle Fire HD 7 by downloading and putting the Next Launcher.apk file in the system app folder. That's literally all I did and now I can't get it to stop. I've even tried adding a second and third launcher to see if I could pick one on start up but that didn't work either. I even got ADW Launcher running and the error still came up. I'm running out of ideas. I'm open to any ideas at this point. Thanks for your time with this btw. I really appreciate it. :fingers-crossed:
Click to expand...
Click to collapse
What about using ADB to communicate to your Kindle? That is, using "adb shell" thus allowing you shell access to your Kindle. Then using the shell to first kill the Next Launcher service and then finally rename it to Next Launcher.bak - Maybe?
Follow Up
twhitehead1081 said:
Tried the Hard Reset and the Safe Mode, neither worked. The message continues to pop up repeatedly.
The error itself is that after I tried to use the Next Launcher by putting it into the system/app folder like you would any other launcher to get it to do its things, it didn't work and now I get a continuous "Next Launcher Has Stopped" message that no matter how many times you press "OK" it keeps coming up, literally every second. The odd part is, I have been able to re-root the kindle and navigate it so I know I'm not bricked and I am 95% sure I am not soft bricked, though I could be wrong. I have managed to get ES Explorer back onto the Kindle and can navigate my way over time to the system/app folder. I have tried deleting the file and I get the "Error Deleting File" message and it continues. From what I can see, all I need to do is get this file deleted (and not try random untested things of course ) and if I can do that, it will be fixed. I just can't seem to get it deleted. I have tried both ES File Explorer and Astro File Explorer which are both still on my kindle. I have tried deleting it with the multi-select option in both but get that previously mentioned "Error Deleting File." I have tried moving it back to the sdcard/download folder with the same error. I have tried killing the task with Astro and ignoring it as well and that doesn't work. I am still working on this. I do realize as well that when this first happened I should have cleared out some files before I did the factory reset which also didn't work. However I was unable to get that file (Next Launcher) deleted which is why I went to the factory reset. After I managed to get the Kindle re-rooted, the only I haven't been able to do is get Superuser root access to the system/app folder to change permissions, again because of the repeated error.
It all comes down to the Next Launcher.apk file in the system/app folder that I can't get out. Long pressing anything doesn't work because of the repeated pop-up "Next Launcher has stopped." error mentioned above. The only way I can show you what it is exactly is to screw up your Kindle Fire HD 7 by downloading and putting the Next Launcher.apk file in the system app folder. That's literally all I did and now I can't get it to stop. I've even tried adding a second and third launcher to see if I could pick one on start up but that didn't work either. I even got ADW Launcher running and the error still came up. I'm running out of ideas. I'm open to any ideas at this point. Thanks for your time with this btw. I really appreciate it. :fingers-crossed:
Click to expand...
Click to collapse
How did this work out? Were you able to fix the issue? If yes, post the resolution just in case one of us has the same problem.
I hope adb shell worked.
prokennexusa said:
How did this work out? Were you able to fix the issue? If yes, post the resolution just in case one of us has the same problem.
I hope adb shell worked.
Click to expand...
Click to collapse
Hi Guys,
I tried your method and it kept giving me an error saying the file doesn't exist. I went through some of the forums and somehow managed to get the kindle stuck in System Recovery mode. After a few more hours of playing with it, I called Amazon Customer Service and they are sending me a new one. Thanks for all your help. I'm sorry the directions above didn't work. I know now for future reference what not to do.
Application Stop
twhitehead1081 said:
Hi Guys,
I tried your method and it kept giving me an error saying the file doesn't exist. I went through some of the forums and somehow managed to get the kindle stuck in System Recovery mode. After a few more hours of playing with it, I called Amazon Customer Service and they are sending me a new one. Thanks for all your help. I'm sorry the directions above didn't work. I know now for future reference what not to do.
Click to expand...
Click to collapse
Well I am glad you are getting a new Kindle! Follow our Noob instruction series when you get the new Kindle.
Bummer, because that Next launcher looks nice. I hope someone can figure out how to make it work.
Next Launcher and Apex Launcher
Krsmqn said:
Bummer, because that Next launcher looks nice. I hope someone can figure out how to make it work.
Click to expand...
Click to collapse
We will be working with Go Launcher team to get this done.
We will create a How to: once we have cleaned out the bugs.
prokennexusa said:
We will be working with Go Launcher team to get this done.
We will create a How to: once we have cleaned out the bugs.
Click to expand...
Click to collapse
Pls help me, i have the same problem here, i don't know what to do. Can i do a factory reset, i just rooted my kindle today
ariks2012 said:
Pls help me, i have the same problem here, i don't know what to do. Can i do a factory reset, i just rooted my kindle today
Click to expand...
Click to collapse
Just fixed it guys, sooo happy now
Why.You could of bought factory cable 12$ for your time and reflashed stock with the kindle fire first aide kit
Sent from my KFTT using xda premium
I ran into something similar when I was dealing with an input method app.
http://forum.xda-developers.com/showthread.php?t=2127949
I was able to solve it on my own thanks to aLogcat. A little access to logcat goes a long way - it lets you see what app is crashing and how.
Thanks
onemeila said:
Since you have root access you can use adb to remove a system apk,
Use these commands:
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up a list of apk names on the device:
Code:
cd /system/app
ls *.apk
Hope this works for you.
Click to expand...
Click to collapse
Guys: I had the exact same problem today. I followed your instructions and I could get rid of the Next Launcher successfully. You don't know how grateful I am. I was afraid I was to loose my Kindle, too. But this worked. Thank you very much. :highfive:
Kindle Fire HD 7 stuck on 'application stop'
danyluis said:
Guys: I had the exact same problem today. I followed your instructions and I could get rid of the Next Launcher successfully. You don't know how grateful I am. I was afraid I was to loose my Kindle, too. But this worked. Thank you very much. :highfive:
Click to expand...
Click to collapse
danyluis,
You deserve some credit too! Great work danyluis!
a little help?
This is a little different than the original issue but I believe I may have messed something up while trying to root. I don't have a lock screen anymore and my top and bottom bars keep disappearing with a blink once and a while but no touch interaction when they do come up for that brief second. since I am rooted, is there anyway to replace system files to override the ones I may have messed up, or can someone point me in the direction of restoring a stock system without having access to the traditional method of factory reset through the settings menu? Everything seems to work fine just I have no access to the home button, back button, notification bar etc...
I've been searching the forums for an hour or so and haven't been able to come up with a solution.
I've tried using binary's rooting method again to try and restore but it never comes up to the restore screen since I don't have a lock screen. At the end of that process I get a message saying no backup-restore.apk.
I just noticed the first aide thread and I'm going to read through that in hopes that there is a way to bring this thing back.
[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software - UPDATED 02/13/2013 1:30
Ssantos6981 said:
This is a little different than the original issue but I believe I may have messed something up while trying to root. I don't have a lock screen anymore and my top and bottom bars keep disappearing with a blink once and a while but no touch interaction when they do come up for that brief second. since I am rooted, is there anyway to replace system files to override the ones I may have messed up, or can someone point me in the direction of restoring a stock system without having access to the traditional method of factory reset through the settings menu? Everything seems to work fine just I have no access to the home button, back button, notification bar etc...
I've been searching the forums for an hour or so and haven't been able to come up with a solution.
I've tried using binary's rooting method again to try and restore but it never comes up to the restore screen since I don't have a lock screen. At the end of that process I get a message saying no backup-restore.apk.
I just noticed the first aide thread and I'm going to read through that in hopes that there is a way to bring this thing back.
Click to expand...
Click to collapse
Ssantos6981,
First let me apologize for the delay.
You caught us before we could recommend the solution! Please go to our Backup and Restore Software Kindle Fire First Aide here:
[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
We just deployed a new update, so please download the latest copy which was updated 02/13/2013 at 1:30am PST GMT -8.
Here we go, for the complete Windows 32-bit Package: KFFirstAide32.zip
For the complete Windows 64-bit Package: KFFirstAide64.zip
Be sure to update Java here: Java SE Development Kit 7u13
When you extract the package, be sure to rename the folder to C:\KFFirstAide and add an Environment Variable.
twhitehead1081 said:
I am so confused . . .
I have a kindle fire hd 7. I rooted it today using the one/two step method and it worked beautifully. I tried a couple of different launchers (go launcher hd, adw launcher and apex launcher) and all worked fine. I decided to go back to using go launcher hd since I liked it the best. No problem. Switching and uninstalling worked great. Before I could finish reinstalling the go launcher hd and moving to the system app folder, I stupidly saw the new Next Launcher and tried that. Now my kindle is stuck on an endless "Next Launcher has stopped" cycle and I can't get it to stop. I have tried resetting to factory default and that didn't work.
The odd part is, even though I get the same error message every second (literally) the kindle will still work if I'm fast enough pushing the ok button on the error. I have taken 4 hours and navigated to the menu where I force it to close (didn't work), tried to find the es file explorer (didn't work) and no matter what I do, I can't get it to stop.
I hope that was thorough enough. Any tips?
Click to expand...
Click to collapse
how did you brick it im having same issue
Thanks a lot
onemeila said:
Since you have root access you can use adb to remove a system apk,
Use these commands:
Code:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up a list of apk names on the device:
Code:
cd /system/app
ls *.apk
Hope this works for you.
Click to expand...
Click to collapse
I had the same issue, but now it is solved thanks a lot