Develop Bugs

[Q] Kindle Fire 2 is bricked

Hey, I was stupid and tried to install a rom without factory-resetting my kindle. Now I am stuck at the splash logo boot loop. I tried the unbrick utility, but it can't find my kindle. I have access to fastboot commands, but not adb. Don't ask me why, I just can't use adb. I don't know how to restore my kindle to a working state. I have a fastboot cable available. Thanks in advance. Im a noob btw.:crying:

..

Kindle fire 2 bricked
Neeshers said:
I'm guessing it's looping from the kindle fire screen not the cm10.1 screen, correct? If so, you can use the command, "fastboot -i 0x1949 -w". That will wipe userdata and cache. But if it's looping without even loading the rom that's probably not going to fix it.
Click to expand...
Click to collapse
Ok, I am now not stuck on the splash logo. i reflashed the recovery and boot partitions and now it is trying to boot, but there is currently no os installed. Is this a good sign that I can fix it? I am in slc for the weekend and cant flash the system partition yet.
Another question. I tried installing twrp on my recovery, but i cant boot into it. it wont show the blue logo. do i need an os installed to use it?

Dill185 said:
Ok, I am now not stuck on the splash logo. i reflashed the recovery and boot partitions and now it is trying to boot, but there is currently no os installed. Is this a good sign that I can fix it? I am in slc for the weekend and cant flash the system partition yet.
Another question. I tried installing twrp on my recovery, but i cant boot into it. it wont show the blue logo. do i need an os installed to use it?
Click to expand...
Click to collapse
Yes. os MUST be installed for our recovery to function. Specifically a file called 'stack' has to reside on the system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Kindle fire 2 bricked
mindmajick said:
Yes. os MUST be installed for our recovery to function. Specifically a file called 'stack' has to reside on the system partition
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a bunch. i restored the system partition last night, and it fixed. i plugged it in to charge, and this morning, it was back at the kindle fire logo. Did i do something wrong?

Doesn't sound like it.
Were you able to get it to boot back up?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

kindle fire 2 is bricked
mindmajick said:
Doesn't sound like it.
Were you able to get it to boot back up?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I figured out it was a OTA update that re-bricked it. I am downloading a custom rom right now. I finally got it to work! Thanks for all your help.:victory:

Kindle fire 2 cm10 help
Dill185 said:
Ok, I figured out it was a OTA update that re-bricked it. I am downloading a custom rom right now. I finally got it to work! Thanks for all your help.:victory:
Click to expand...
Click to collapse
Another question. I downloaded the CM10.1 zip shown here: http://forum.xda-developers.com/showthread.php?t=2100963
I try to flash it in twrp, but it keeps saying error flashing zip
What do I do?

Sounds like a bad download. Redownload and adb sideload from pc
--
Sent from my mind to your screen.

I've downloaded it like fifty times. I got a ROM I like though. I can finally use otg stuff. Thanks for all your help!
Sent from my Amazon Kindle Fire2 using xda app-developers app

i got similar problems. rooted it, but i got afterwards some problems with superuser applications. ran sveral rooting methods, but at some point, it stucked now with the orange "kindle fire" logo.
tried also to use different recoverys (kindle-fire-ultility2, KF2_SRT_10.2.3) but nothing helped. i cant reach the device anymore. adb says: no device in list and fastboot: <waiting for device>
actually i use the supplied cable. or am i wrong to use it for fastboot. thought the supplied one is similar to the special fastboot cables from e.g ebay
/edit: sry, just realized after reading the FAQs, that the factory cable is a different one. sorry.

[Q] TWRP Unable to mount internal card

A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?

bigbpc said:
A100 rooted unlocked CarbonRom from pio. My rom works fine, I can still boot into it. But I've become a flasher lately, and want to keep trying other roms. When I boot to recovery and try to wipe data. I get an error that it failed, and the log says unable to mount '/data' (tw_mount). But like I said, i can still boot into my current rom"pio's awesome CarbonRom", I just wanted to try some other roms. I tried 'fastboot flashing a100-fstab-fixed-for-twrp-boot.img', that I got from 2nd post on http://forum.xda-developers.com/showthread.php?t=2431506 . I used the command 'fastboot flash recovery a100-fstab-fixed-for-twrp-boot.img' . Then recovery wouldn't boot at all, and just goes straight to CarbonRom, which I am glad it hasn't bricked. So I boot back into bootload from adb with fastboot, and and reinstalled twrp 2.2.2.1 with 'fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img' . So now I got a twrp working again, but I was a 2.6, and this one still doesn't mount data. Any tips?
Click to expand...
Click to collapse
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
You flashed kernel over recovery, you really need to triple check commands like that.
fastboot flash boot a100-fstab-fixed-for-twrp-boot.img
Notice its flash boot, that portion tells where to flash the image to, when you said recovery it wrote it there instead.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much pio_masaki. I should have came to the forums first rather then try to put together fragmented information in my brain. I know little to nothing of adb and fastboot. You are awesome.

[Q] Boot loop on firefirefire as i try to enter recovery

Title basically says it all however here is the long rundown. so I installed twrp and fff using kfu. Everything but the recovery mode boots fine. Using normal boot mode it will go right into the regular kindle and load up so that I can access apps books movies etc. However when I try to enter recovery mode using either the kfu bootmode menu or the fff boot menu on the kindle itself it gets stuck in a boot loop on the fff boot screen. I don't 'need' the recovery part but it would be nice to have especially if I screw something up. Any help would be appreciated.

mike.anderson457 said:
Title basically says it all however here is the long rundown. so I installed twrp and fff using kfu. Everything but the recovery mode boots fine. Using normal boot mode it will go right into the regular kindle and load up so that I can access apps books movies etc. However when I try to enter recovery mode using either the kfu bootmode menu or the fff boot menu on the kindle itself it gets stuck in a boot loop on the fff boot screen. I don't 'need' the recovery part but it would be nice to have especially if I screw something up. Any help would be appreciated.
Click to expand...
Click to collapse
What recovery are you using? (version, build, etc.)

soupmagnet said:
What recovery are you using? (version, build, etc.)
Click to expand...
Click to collapse
umm TWRP 2.6.3.0 touch recovery I think as it says install latest twrp recovery and I am using kfu 0.9.9. I am sorry if I am being a complete idiot and missing something important.

mike.anderson457 said:
umm TWRP 2.6.3.0 touch recovery I think as it says install latest twrp recovery and I am using kfu 0.9.9. I am sorry if I am being a complete idiot and missing something important.
Click to expand...
Click to collapse
Try installing COTR and see if you get the same result

soupmagnet said:
Try installing COTR and see if you get the same result
Click to expand...
Click to collapse
should / can i remove the twrp files before i do that?

mostly wondering because i looked at the cotr page and it said to upgrade you must delete the settings.ini file. Now i know i am not upgrading from a previous version of the recovery however could just installing cotr cause a software conflict with twrp?

I don't know why twrp would not be fine. Are you sure the file you installed was a good download? You may simply need to redownload/reinstall twrp.
Sent from my GT-p511x

mike.anderson457 said:
mostly wondering because i looked at the cotr page and it said to upgrade you must delete the settings.ini file. Now i know i am not upgrading from a previous version of the recovery however could just installing cotr cause a software conflict with twrp?
Click to expand...
Click to collapse
No. By flashing a new recovery, the partition is completely overwritten. The only things that remains are the files saved to the sdcard. TWRP files on the sdcard have no effect on those for COTR and vice versa. The 'settings.ini' for COTR is located on the sdcard, which is why it needs to be deleted when upgrading.

sharonbw said:
I don't know why twrp would not be fine. Are you sure the file you installed was a good download? You may simply need to redownload/reinstall twrp.
Sent from my GT-p511x
Click to expand...
Click to collapse
i re-downloaded the kfu file 3 times and re installed twrp twice each i am reasonably sure that everything is fine unless the upload from this site is somehow corrupted
soupmagnet said:
No. By flashing a new recovery, the partition is completely overwritten. The only things that remains are the files saved to the sdcard. TWRP files on the sdcard have no effect on those for COTR and vice versa. The 'settings.ini' for COTR is located on the sdcard, which is why it needs to be deleted when upgrading.
Click to expand...
Click to collapse
aah okay... thank you both for helping with my problem and with clarification i really appreciate it.
did as suggested with same result no access to recovery but it still boots fine to the normal ui

Bricked Nexus 7 while installing Lollipop - fastboot kinda works

Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.

Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..

kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.

kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now

Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?

This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app

atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!

DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.

Use wugs but make sure you tick tablet is in bootloop, worked for me.

atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!

Soft bricked

Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?

Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?

Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.

Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.

Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.

Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.

Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.

I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:

I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.