I was having problems yesterday, I though my KF was bricked. I got some help and I got my phone to start again. But for some reason even after following this thread http://forum.xda-developers.com/showpost.php?p=19552626&postcount=1 my KF was still rooted when everything was over. I don't know why it was still rooted but when I tried to root it again, SuperOneClick said "Are you sure you want to root, you are all ready rooted".
Anyways I installed Root Explorer, it worked, so I guess I still had root. So now I wanted to install the Android Market. But first I wanted to switch Launcher because I have to anyways in the end.
I installed GoLauncher (GO_Launcher_EX_HDTest_V2.69Beta.apk) from their website. After installation, my KF seemed to lag, almost become unresponsive. Then a popup appear telling me to pick eithier the Amazon Launcher or GoLauncher. I picked GoLauncher and my KF wouldn't turn back on. I have to press the Power button a few times really fast to get back to the Lock Screen. Once I'm their I'll slide the lock arrow across and my screen just shuts off, my KF doesn't power off, just the screen. I turned my phone off for 20 seconds, restarted and back into bootloop with that Kindle Fire splash screen. I cant say for sure that it is GoLauncher but the first time my KF boot looped it was after I installed it and the 2nd time happened immediately after GoLauncher was installed.
I really don't know what I'm doing wrong or missing? Am I using the wrong version of GoLauncher or am I missing a step? Right now I'm following the "Unbricking" guide again to get my KF to work.
EDIT: I just followed steps 1-6 from the Unbricking guide and my KF is working again, but like I said for some reason I still have root. If I can't figure out what I'm having launcher trouble I'm just going to unroot I guess.
Try version 2.68
Droidanian said:
Try version 2.68
Click to expand...
Click to collapse
Does it need to be installed in any certain way? Once installed how do I switch from stock to GoLauncher?
Just install it the normal way and choose "Open" once the installation is complete.
Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation
foxdog66 said:
Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation
Click to expand...
Click to collapse
yeah i had to use fast boot and what not to get the kindle back on, but once i did i just installed golauncher 2.68 the latest stable one and everything works except sometimes widgets will say i dont have any space left but i have plenty.
i guess like you said that HD golauncher was just too much and was messing my KF up.
As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.
ubeezee said:
As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.
Click to expand...
Click to collapse
If he bricks it again, good luck getting help from anyone, period. It's obviously your choice what you do with your device, but it does not mean I or ubeezee (we work together to solve the questions) or anyone else will help you to undo it. However, Amazon seems to be willing to forgive him so I guess he can still go that route.
I told you why your device is still "rooted," do you not listen? Not listening/reading is probably why you ended up in the predicament you were in. You don't read and you don't listen to what people say when you ask questions.
Accidents are forgivable...blatantly doing something you know will probably screw your device up (after you already screwed it up once by doing so) is not so much.
Related
I rooted my hero and tried out a few roms but non seem to polished yet so was wanting to finda stock rom while keeping root of course, Id mainly like the stock one with the ability to run apps from sd card.
have you tried fresh 1.0 its pretty close to stock. If you want you can just return to your nandroid that you did after you rooted but before u installed any ROMs and thats basically a rooted Stock ROM
yeah im gonna try that because now I cant do anything, I hope I didnt mess up my phone, no matter the update I apply(and I try wiping to) it just sits at the htc screen.
How do you apply the nandroid backup?
I just basically have the folder with everything in it on desktop
boot into recovery mode and go down to the listing that says Nandroid Restore.
also when you install a new ROM it isnt rare for it to take up to 10 minutes to boot.
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Nandroid Restore. I assume you did make a nandroid right after you successfully rooted correct?
yeah its doing the nand. restore now. hopefully all is well. just waiting for it to finish restore.
ive never had a problem rooting, my g1 always worked fine.
ah phew, thankfully I had a backup. and i was thinking, is their honestly any reason to go to a rom atm? I mean for my g1 I used one because it was faster, quicker, more features, and had apps2sd.
but atm for hero atm doesnt look like a top notch one yet?
also can the stock rom with root do apps2sd?
and easiest way?
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
samrozzi said:
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Click to expand...
Click to collapse
obelisk79 said:
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
Click to expand...
Click to collapse
He already stated he waited way more than 10 mins....
Fresh 1.0 makes your phone quicker, I wasn't going to ROM until a really customized and polished one came along but after trying Fresh, I'd highly recommend it.
Ok so after succesful GB install every things going fine until this:
every time I install a new or already paid for ap (like re-installing old ap I paid for like TI.backup pro) after it says dl'd it goes to "installing" and then...reboot
every time. any one experience this or have any solutions?
Everything else works perfect: wi-fi , out/incoming calls, internet,3g, etc.
I can get into market np and I can DL, but the minute it goes to install....bam!
reboot.
I expierenced the same thing on a custom gingerbread rom. Thats because I messed some stuff up though. I would say just SBF it back to stock, and if you want to reinstall the gingerbread update then you can.
Also did you wipe your phone before you installed gingerbread?
Download and run Market Fix, reboot and everything should be sweet.
silverfang77 said:
Download and run Market Fix, reboot and everything should be sweet.
Click to expand...
Click to collapse
I was under the impression that the market fix only makes certain apps capable of showing up. Does it fix other things too?
silverfang77 said:
Download and run Market Fix, reboot and everything should be sweet.
Click to expand...
Click to collapse
not my issue also in the op thread I dont see how this is going to help me.
For me when it comes to modding phones DL something "just to see" seems like a good way to brick your phone, and not having enough knowledge to fix bricks I dont want to take a chance.
How will a factory reset affect me? I have never FR. Everything else is running perfectly, I cant believe there is no way to fix this, its has to be a missing file/permission?
anyone?
Edit may 4 2011: so.... I ended up sbf phone back to stock, rerooting and decided Ill wait for the real GB release. Not sure why this bizaare shizzle happened but better to play it safe. too many people with issues with this gb hack, to many peeps BL'd. I still think it was interesting I was able to load the bootstrap from my ap "mini task" yet it would not load from the ap screen itself.
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App
thanks this worked like a charm. Gotta love the XDA community.
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.
Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!
I've suddenly developed a problem with my rooted Nook Color 1.2.
I soft rooted it back in April using ClockWork and apk-enabler-1-1a-signed.zip.
Everything worked as expected.
For the past few weeks I haven't needed any of the andriod apps. I have just been using the Nook as a reader and I have not made any changes to it other than loading and removing books.
Today I realized that it was booting to the stock user interface and pressing the N key did not bring up the menu list of alternate managers that I installed.
I have tried re flashing the NC with apk-enabler zip file. When that didn't give me back access to the andriod apps, I tried flashing with the newer MiniRooter from NookDevs. Now I have a new flyout menu on the right side of the screen, but there really isn't any response to pressing the icons.
I'm sure that I'm leaving out an obvious step or doing something else dumb and I really appreciate it if someone could point it out to me.
Thanks!
katrina.adams said:
I've suddenly developed a problem with my rooted Nook Color 1.2.
I soft rooted it back in April using ClockWork and apk-enabler-1-1a-signed.zip.
Everything worked as expected.
For the past few weeks I haven't needed any of the andriod apps. I have just been using the Nook as a reader and I have not made any changes to it other than loading and removing books.
Today I realized that it was booting to the stock user interface and pressing the N key did not bring up the menu list of alternate managers that I installed.
I have tried re flashing the NC with apk-enabler zip file. When that didn't give me back access to the andriod apps, I tried flashing with the newer MiniRooter from NookDevs. Now I have a new flyout menu on the right side of the screen, but there really isn't any response to pressing the icons.
I'm sure that I'm leaving out an obvious step or doing something else dumb and I really appreciate it if someone could point it out to me.
Thanks!
Click to expand...
Click to collapse
Do a clean wipe and install NC 1.2 followed by ManualNooter
and reply with results.
Dont forget to hit thanks if it helps
katrina.adams said:
I've suddenly developed a problem with my rooted Nook Color 1.2.
I soft rooted it back in April using ClockWork and apk-enabler-1-1a-signed.zip.
Everything worked as expected.
For the past few weeks I haven't needed any of the andriod apps. I have just been using the Nook as a reader and I have not made any changes to it other than loading and removing books.
Today I realized that it was booting to the stock user interface and pressing the N key did not bring up the menu list of alternate managers that I installed.
I have tried re flashing the NC with apk-enabler zip file. When that didn't give me back access to the andriod apps, I tried flashing with the newer MiniRooter from NookDevs. Now I have a new flyout menu on the right side of the screen, but there really isn't any response to pressing the icons.
I'm sure that I'm leaving out an obvious step or doing something else dumb and I really appreciate it if someone could point it out to me.
Thanks!
Click to expand...
Click to collapse
You can download the attached file and flash it from CWM. It will install Launcher Pro, and upon start-up, you will get the option to choose your launcher again. You can then just delete Launcher Pro once you are done.
The reason for installing Launcher Pro, is that anytime a new launcher is installed or deleted, you will get the launcher selection menu to popup again. The packages that you were installing all had the same version of zeam launcher in them, so that is why you get not get the option to popup.
Thanks to both of you!
Last night I found and installed a newer version of Zeam launcher and got access to the apps back. Not because I realized that Zeam was the problem, I was just going through and trying to update the apps I had installed to manage the device.
I'm going to clip and save the thread - just in case!
Thanks guys! Ill give it a try once I get the Nook away from the wife I gave it too her for her Bday and I use it more then her! She LOVES the thing, but I havent found a tablet with the same capabilities without doubling the price and having half the battery life! I love reading Manga on this thing!
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
jombo2323 said:
Ok, so everything was going fine and dandy so i decided to root my nexus 7. it was amazing, i was able to over/underclock. Then i remembered an app that i had called chainfire3d that allows you to force certain things on the gpu such as anti aliasing and full 32 bit color on some things. anyways after an install it needed to reboot. once rebooted, it just sits at the google screen with the little lock thats open at the bottom. going into bootloader by holding down all the buttons gets me to the screen but then it freezes. cant boot, cant get into bootloader. any help?
Thanks in advance.
Click to expand...
Click to collapse
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
jinside said:
sounds like you need to go to the android development list and look for the unbrick thread that has directions to put the original os back on. Then reflash your favorite recovery/rom..etc.
Click to expand...
Click to collapse
ok, but. im no android fixing expert, but i know my way around it really well. anyways, cant you do nothing if you cant at least get to the recovery screen?!
i have no idea.\
*EDIT
Finally got recovery to work by lots of reboots and was able to reflash the whole thing. i guess let this be a lesson to people trying chainfire.