Database Users

Stuck at boot screen

Hi.
It all happend when i wanted to replace the libwebcore.so file in the /system/lib.
So i did it. but its properly the wrong libwebore.
so i restarted the phone, but now, its stuck at the tattoo screen.
I can connect it to the computer. adb can see it. but i cant su neither mount which requires su.
It's the custom rom. i have no recovery image installed.
i CAN access fastboot AND recovery mode
I tried flashing a rom via HBoot by renaming the rom to CLICIMG.zip. but it doesnt work. phone says no image or wrong format.
Any suggestions?

Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(

Do you have a backup?
Have you tried to install recovery img via adb? If you can do this you can just do a backup of your current rom, try somehow to get your sd-card seen by the computer and copy the files of your old backup files to your new backup, asked to replace select yes.( I used a different phone to copy my backup files to the sd card when I couldn't get past startup screen.)
Good luck.

XabdullahX said:
Well, this really sucks
Now i cant even access adb. I pressed home+back key to reset the phone.
now its just stuck on the tattoo screen like just before but adb devices dont see anything.
Pleassee someone? i really need help on this one!
Hboot doesnt seem to help much. it cant detect anything. i had 3 files on the sdcard (all is amon_ra), just named differently: CLICDIAG.zip, CLICIMG.zip and CLICIMG.nbh
but it doesnt do anything :'(
Click to expand...
Click to collapse
Where you found these files?
To flash the rom from hboot you need the rom.zip file of your stock rom(renamed as CLICIMG.zip)

I have the same problem! stuck on "Tattoo" screen and boot again and again.
I have the goldcard with CLICIMG.zip and it loads on HBOOT and install all (boot,radio,recovery,etc.. ) but when it ends, returns to the same....
HELP PLEASEEE!!!

Do you have Amon_Ra or Clockworkmod recovery installed? If so you can try wiping the Dalvik cache and try rebooting. Most boot loops I had were resolved this way. Wiping data and cache totally might also help.
If you can access adb and device is rooted, you should be able to use "adb shell" command and have a rooted terminal with the "#" sign after running su. In that case you can also manually wipe Dalvik cache by deleting everything under /data/dalvik-cache/
$su
#cd /data/dalvik-cache
#rm *
#exit
$exit
Click to expand...
Click to collapse
Good luck!

tihe problem is that i can´t access to the phone by adb
i put "adb shell" and it says: "error: device not found"
the phone screen shows a phone and triangle with exclamation

[Q] Fire Bricked; No shell root

I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.

Did you try the lastest KF utility v.7? Your not alone with this problem...

I'm in the same boat as you. I tried for 2 days to fix it to no avail and finally decided I was SOL without one of of these "factory cables". The other day I did a support chat with amazon and they are sending me a new kindle. My main gripe with the kindle is there is no way to easily factory reset because of the lack of hardware buttons. Think I'm gonna wait for a cyanogenmod 9 rom before I mess with the replacement... Good luck.
Sent from my HD7 T9292 using XDA Windows Phone 7 App

Had this problem last night
Already trying to hack your Christmas present?
I had this problem last night. Stuck on boot screen and powering down and up didnt fix. This is what what fixed it for me.
Go into CMD and type this, with the kindle connect via usb,
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

Used KF Utility 6
I haven't had success with v7 yet, but will try when I get back. I had trouble with KF Util on Windows 7 so went back to XP. Will try Ubuntu next because it's easier to navigate the command line. Is there any difference between v6 and 7 with respect to elevating shell privileges?

Yeah follow the command... I think we are stuck on fastboot!

Well at least I'm not the only one who did this. Same issue... Tried to copy the marketplace APK and it wouldn't appear. Changed permissions and am now stuck at boot splash. Executing "fastboot -i 0x1949 oem idme bootmode 4000" simply hangs at "<waiting for device>".

No shell root, no progress
I've tried unrooting with KF utility v7 to no avail. One problem could be that I had Burrito Root on the Fire prior to the bricking, but how I can remove it at this point is beyond me. I can't run the fastboot commands without being in shell root, and KFUtilityv7 doesn't work without those credentials.
Some errors: "(idme) Invalid permission"; "reboot: Operation not permitted". These are seen when I try to put it in recovery mode. FYI, my ADB status is online and my computer sees it, the ADB Rooted status says "No" and I'm in Boot Status 4000 (Normal).
When I try running BurritoRoot it goes through a process, says "Elevating the Shell" and then errors out with "adbd cannot run as root in production builds"
Then below this it says "Root Activated" and "The Kindle is successfully in root mode."
Here is the output from my attempts at installing Permanent Root with KFUtility v7:
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
2114 KB/s (843503 bytes in 0.389s)
Error: Could not access the Package Manager. Is the system running?
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
It is HIGHLY recommended you have TWRP installed before using root.
****************************************************
At this point you can see the mount operations were not successful because you cannot gain root in the shell with su. I am going to try this through my Ubuntu build and see if I can gain privileges through Linux.

Hi. Same problem here. Changed the /system/app permissions by mistake and the Fire won´t pass the loading screen.
I think the only hope we have is that someone finds a way to root from adb.

According to GregDDC:
GregDDC said:
I had the same issue and fixed it with a recovery cable.
The process was simple, just short the 1st and 4th pins on a microUSB cable and boot into recovery/fastboot. You can find all the information here (link) and here (http://forum.xda-developers.com/showthread.php?t=1392693&page=3). I accomplished everything using Kindle Fire Tools.7 I hope this helps.
Click to expand...
Click to collapse
I just don't have the dexterity to fashion my own cable.
Sent from my SPH-D710 using XDA App
Sent from my SPH-D710 using XDA App

I have the same problem. I get the boot-loop with the kindle fire logo. I can access the file system, but most commands give me a seg or permission error. ZergRush doesn't work so fast boot won't work.
I'm trying to get a factory programming cable off here or make my own. That should bypass the whole root issue and put you directly into fast boot so you can load a kindle rom or cm7 or whatever.

Think I'll wait for my wife to go to work tomorrow so I can spend the day working on a cable without distraction. ;-)
Sent from my SPH-D710 using XDA App

Seriously, you most likely don't need the Factory cable to fix your problems. Just do some more reading. There are more than enough threads on these issues to provide you with a clue on how to get out of or into what you are trying to do.

Care to give us a clue on the solution then? I have scoured both this and other threads.
Sent from my SPH-D710 using XDA App

If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.

Exactly correct (unfortunately) Vasheypooh. At the crossroads of waiting for another temp root through adb our practice my soldering skills.
Sent from my SPH-D710 using XDA App

Factory cable will be the solution for me i'm from canada.

Vashypooh said:
If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.
Click to expand...
Click to collapse
i've come to the same conclusion unfortunately. this is only my second attempt at rooting an android device and it's wildly different from the process for the previous device i was working with, so since the instructions i was using didn't mention installing a recovery, i failed to do that myself. my kindle is going to the "Your kindle had detected a problem and must clear App storage" on every boot and all attempts to communicate with it have failed. looks like a cable or a new device are my only options at this point. i will definitely be using a recovery of some kind from now on!

rcabls said:
I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.
Click to expand...
Click to collapse
I have exact same issue. Can someone help. I can't get rooted using any of the tools available today.
HELP!

This is because you changed the properties on all the files in /system.
Why would you do that?
su no longer has permissions to run.
If you can't get into recovery, you likely need a factory cable to fix.

[Q] Super Ultra Brick (WITH VIDEO)

UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?

looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state

b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.

maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer

b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.

Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.

ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.

skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.

Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?

at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...

b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.

fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...

b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.

great idea with the video !!!

b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?

I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.

with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...

b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!

The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)

foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.

[Solved] Anyone have any success with a factory cable?

Solved
thanks to all for the great info
i have a fire that is stuck on the static kindle logo. was rooted and had fff and twrp. while messing with flashing different roms i used a custom rom that had several apks removed. after booting i still had fff and twrp but my wifi stopped working. i flash the 6.2.1 stock rom that removes fff and twrp, but did a stupid and wiped some stuff before i booted the stock rom. now im stuck with kfu showing online but under status says unknown. i can use adb to reboot but that seems all i can get it to do. im at work now and cannot quote the messages i get. something like /systme/whatever is not there. seems like i wiped the sd card and all. now with that information can i still use a factory cable to fix this? im working on one now to try and see. just wanted to hear from someone who has maybe done the same.
thank you very much for any info

I was in the same exact situation and with the factory cable i managed to fix my brick. Don't worry, your Fire is fine.

The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.

lmntone said:
The same thing happened on mine 20 minutes ago. I worked it out with the method used in this thread.
Click to expand...
Click to collapse
That won't work without a working adb shell (http://forum.xda-developers.com/showthread.php?t=1418080), whik i think is the case.

man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -

It won't show up in kfu, just select flash twrp anyway.
Sent from my myTouch_4G_Slide using XDA App

Use fastboot.exe located in the tools directory and run "fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.image". But you have to download the TWRP image and place it in the same folder as fastboot.exe.

Iguanadon said:
man i hate being a noob fire owner i have my cable done 5v on 1 and 4 but not getting what i was looking for. kfu still shows
adb: online
adb rooted: no
boot status: unknown
im on windows 7 and can reboot the fire with cmd window adb reboot. but i have no idea where to go from here.
i thought the factory cable would put it in fastboot, but not sure how to check or what to do.
adb shell gets this:
-exec '/system/bin/sh' failed: no such file or directory (2) -
Click to expand...
Click to collapse
you know you're in fastboot mode when your kindle fire logo is static instead of glimmering

maybe you want to take a look here:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38

Please help soft-bricked

Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated

Wow I expected people to jump on this one. I guess I'll just keep messing around with it

Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt

Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.

So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?

hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?

gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.

Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery

Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct

Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks