Database Users

[Q] Kindle fire totally dead

Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
Make/buy a factory cable and fastboot the proper bootloader from the stock update package.
Sent from my myTouch_4G_Slide using XDA App

I was a little confused about this myself at one point... There are a bunch of 'low-level' partitions that are really important not to mix up.
'bootloader' contains the basic bootloader, which loads everything else and you should pretty much never touch it, except to install FireFireFire.
'recovery' is the partition where TWRP or ClockWorkMOD should go.
Finally, 'boot' is what launches Android.
I almost made the same mistake last night installing CWM (it was 2am and my brain+fingers were being stupid)
Anyway OP, it sounds like a factory cable would be your best bet, unless that just tells something to the bootloader, in which case getting a warranty replacement from Amazon might be your only option...
Just remember next time that you want to flash recovery ;-)

dietomant said:
Sorry to open a new thread...I've been searching for a similar problem with no result...
My KF was bricked in a bootloop with acces through adb or fasboot but i can't solve the problem via KFU o Unbrick tool, so I was trying to install TWRP
The last command a typed in cmd was (big mistake):
"fastboot flash bootloader twrp-blaze-2.0.0RC0.img"
after that the KF shuts down forever... no charging light, no adb, no fastboot, nothing...
plz any idea to revive my KF???
Click to expand...
Click to collapse
I have had a similar situation on my KF. I used a factory cable to solve my issue. Send a private message to SkOrPn with Factory Cable in the subject. His cable is well built and arrived very quick via USPS. Not to mention he sells them at a good price.

Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...

Try adding the device ID 0bb4:0c01 to your USB configuration
Sent from my Amazon Kindle Fire using Tapatalk

dietomant said:
Finally I got my factory cable.... but the problem is not fixed..
I connect the Factory cable to KF...in am at the command prompt and no matter what fastboot instruction I put always the same message "waiting for device"
If anyone knows what I should do I really appreciate it...
Click to expand...
Click to collapse
I think you've gotten somewhat misleading information from the previous posters. The factory cable will always put the KF into fastboot mode if (this is a HUGE if) the device has a working bootloader. The bootloader is the piece of software that will put the device into fastboot mode, so without that the factory cable cannot do its job.
I'm quite surprised you were able to break the bootloader by trying to flash that image onto it. In my experience, fastboot flash checks for the size and would fail when I tried to give it something > 256KB for the bootloader... but that's neither here nor there...
If you cannot get a "kindle fire" or the "yellow triangle" to come up on the display, your bootloader is broken. Your last hope is to open up the case and use usbboot to temporarily load a bootloader into memory via USB and use that to flash a permanent bootloader. You'll probably need a case pry tool to do this fairly safely and linux installed because I don't believe usbboot was ever ported to Windows.
Additional information: http://forum.xda-developers.com/showthread.php?t=1405052

[SOLVED] My Nexus 7, helpless or still hope?

Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.

quocviet114 said:
Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.
Click to expand...
Click to collapse
Get the FACTORY IMAGE for your device from here...
https://developers.google.com/android/nexus/images
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.

GedBlake said:
Get the FACTORY IMAGE for your device from here...
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?

There have been many similar cases like yours on this forum and I see it usually after the use of toolkits. Not that toolkits are badly written, but people who usually use them don't know what to do when things go wrong. As long as you can get into bootloader mode (=fastboot mode), you can restore your device with fastboot. Take this time to learn a bit about your device and the two only programs you'll ever need for it: ADB and FASTBOOT. You use fastboot when in bootloader mode and adb outside the bootloader.
Use this sticky to return to stock: http://forum.xda-developers.com/showthread.php?t=1907796 . You can skip a few steps in it though. For example, if your drivers are already set up and you have adb en fastboot somewhere (you can find them somewhere in the installation folder of the toolkit) then you don't need to download java and the android SDK. You also don't need to reflash the bootloader if you already use the latest version. Just read and think while you follow one of the best guides you can find on this forum.
To learn more about adb and fastboot, just type the name of the program in a terminal window and you will see a list with all commands associated with it. My recommendation is to flash a custom recovery (for example TWRP): you can type fastboot flash recovery name of recovery. You can use TWRP to root your device afterworths (TWRP will present you with a warning when you reboot your device through it). You can also make nandroid backups with it. In the future, make nandroid backups, because they will help you when you soft brick your device again.
Good luck!

quocviet114 said:
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?
Click to expand...
Click to collapse
FASTBOOT.EXE and ADB.EXE are part of the Android SDK and as such should be on your PC... so you don't need to access internal storage on your Nexus 7.
(In fact you can't, if the N7 is in BOOTLOADER MODE, which of course it needs to be to flash back to STOCK).
The Flash-all script is part of the Factory image, and is run in a COMMAND PROMPT window... to completely reflash back to STOCK.
-----
The toolkit you're using must use FASTBOOT to accomplish flashing... so you must have FASTBOOT somewhere on your PC.
Rgrds,
Ged.

Are you using twrp to flash your custom rom? Some of the custim rom must be flash it with cwm.
Try to install cwm thru fastboot or adb. Then flash again.
Good luck mate.
Sent from my GT-N7100 using xda premium

I'll try your instruction as soon as I go back from work. Thank a lot you guys. I appreciated!

I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!

quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Awesome! Hopefully it was an informative (an maybe even fun) experience.
Also, as long as pushing all three buttons on the side of your nexus simultaniously (for up to 15 or more or less) seconds enters bootloader/fastboot mode, nothing is ever bricked and your nexus can (almost allways) be safed. The only ways to really hard brick and ruin your nexus is to flash wrong or corrupt bootloaders (so always be extra carefull if that ever needs to happen).

quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Well, that's very good news indeed, quocviet114... glad you got it sorted.
I remember when I was a beginner and had similar issues to yours,... upon resolution, the relief was palpable.
-----
ps. you should edit your thread title to include the word SOLVED...
Rgrds,
Ged.

[Q] I have a broken N7.

*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...

filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.

Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....

filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.

An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?

sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....

Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:

yoga 2 1050F can only access BIOS, let's go to RMA?

Hello everybody, I was trying to revert to a 4.x rom because bluetooth tethering was not working... anyway I used Intel Phone Flash Tool and it seems like he failed to flash boot.bin but restarted anyway
SO I only have the Intel BIOS, I can access all the settings, but I cannot start it in Fastboot mode (it just hangs on FastBoot Starting...) or anything that resembles Android.
Still this BIOS seems more a PC to me than a tablet so I am posting here because maybe there is someway to attach an USB OTG (for example) and boot something from there.

@ionioni is working on a safe downgrade path. We did mine but it could be a disaster if not followed correctly. Your other choice is Lenovo repair support. When i bricked mine, it only took 6 days to get it back in my hands. You could also try the steps here... http://forum.xda-developers.com/showpost.php?p=62237383&postcount=5
Sent from my YOGA Tablet 2-1050F

Thank you very much @workdowg, I passed by that thread, just "DNX" mode does not work on my tablet.
So Repair Support it is.
It's very sad such an awesome tablet has so poor ROM that people has to downgrade it...

Mr.Gamer said:
................but I cannot start it in Fastboot mode (it just hangs on FastBoot Starting...) ..............
Click to expand...
Click to collapse
that is DNX mode!!! that message translates to: i DNX have started and now i am waiting for YOU to give me a (fast)boot image to start... so that message is exactly the message indicating that you ARE in dnx mode.
updated: read this http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487
edit:
before anything:
1. download/extract the files attached to this post, now start your tablet (using the Pwr+VolUp+VolDown) to get to that somehow confusing "Fastboot starting..." message = DNX mode (you must get to that message before continuing!)
2. run the extracted tmp-root-1050F-lollipop.exe file (i am assuming you are on the X64 = Lollipop firmware as that screen pictures you attached shows), should do some stuff and in the end if all well will drop you to a root shell (in that post theres a PrtScr for reference), just follow the messages it's pretty easy. should the exe get stuck/not work put your tablet again in DNX mode and try the other file tmp-root-1050F-kitkat.exe. (this means somehow the bios got downgraded partially on your attempt to return to kitkat). this is just a test to see how to move on, it will not fix nor change anything on your tab, after you reboot it will be in the same state as before (that is if you don't do stuff in that root shell of course)
- report back which one worked (gived you a shell)
- also do you want to go back on kitkat or do you want to stay on lollipop? is important to know as the steps are different

Fastboot broken?

I'd installed TWRP and was playing with some ROMs/Kernels when I hit a boot loop. I then used Flashtool ("Emma") to restore to factory. I haven't been able to send Fastboot commands since. I was wondering if anyone here might be able to point me in the right direction to help me sort this out.
When I connect the phone while holding volume up I still get a blue LED, but when I try to send a fastboot command besides "help", I get "waiting for any device" on Windows. On Mac, Terminal just hangs. I've been able to get the Mac to return the device ID using the "devices" command, but this is intermittent. Normally even this command causes Terminal to hang.
ADB debugging is "on". Flashtool works. ADB commands work. The phone can boot without issue. I can successfully get "fastboot help" to work.
What I've tried:
wiping the Mac HD, installing a fresh OS and installing the latest version of Fastboot from the SDK
Installing the Windows drivers directly from Sony and the latest Platform Tools directly from Google
Running "sudo fastboot" from Terminal on the Mac
Using various usb ports on both machines
Rebooting both machines between steps
Reflashing both Marshmallow and Nouget using Flashtool.
The USB cable I'm using is the one included with the phone. I could issue fast boot commands over this cable a few days ago.
Anyone got any ideas about what I've done wrong here? I'm really confused and I'd like to get rooted again if at all possible.

Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.

ondrejvaroscak said:
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
Click to expand...
Click to collapse
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.

I got that error last time I updated, and was puzzled but tried to leave the phone in flash mode (green led) and flash it again. (I did not unplug the phone so I did not see the result of the first flash) This did leave flashtool without the initial phone info, checking for root and all that but this time the firmware flashed. I did include the fsc file into the ftf, I have no idea if it was a fluke or something but second flash with the phone already in flash mode worked. I know it sounds crazy but It might be worth a shot. Other than that it sounds like a bad cable with the inconsistent fastboot behavior but then again you could flash with Emma, which in turn should not affect fastboot. Odd.

88% said:
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
Click to expand...
Click to collapse
I would definitely try diferrent cable!
The Software update error means there is inconsistency in flash memory and bootloader fails to load initial image after flash. Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode. Then let it boot and when it work, flash your desired version of firmware..

So I tried a number of images built from Xperifirm downloads and finally got one of them to flash properly. I'm not sure if this was due to the specific image or if I just got lucky, but my phone can boot again!
ondrejvaroscak said:
I would definitely try diferrent cable!
Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode.
Click to expand...
Click to collapse
OK, I can try that. Just to confirm, is this a step that I should still take given that I can boot now? While I can boot, I still can't get into Fastboot through Terminal. I was successfully able to get a device ID using the "fastboot devices" command once, but running this command a second time caused a full system freeze on my desktop.

I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
edit: I ran into this issue again and noticed that I missed a step in my original reply. In order to get Fastboot working again, I needed to connect using adb and tell the phone to remember my computer on the prompt.

88% said:
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
Click to expand...
Click to collapse
thanks for posting the cause/what you did to fix it.
it might help others, which is what the community is about.