Database Users

kf format

Ok, still have prob with kf...I think all i have on here is TWRP, so with some help from ppl on here i now have the KINDLE FIRE on screen. Still cant get anything else. So is there any way i could format & load any other program on here. I dont care about kindle fire i was going to root it again anyways. Please help .....

as long as you don't get adb working there is'nt much you can do
allready tried firekit ?

I see i tried the things you said well i think i did them right. iam not sure...
I done so much. I just dont know why it wornt pick it up, i can get it to see it on one computer but it has the yellow mark on it & then the other computer dont see it as kindle just as the phone. so even if it format it still wont help (its not like a computer you can load a program on it)

what is it when they get a cable when they brick them?

that is a factory cable - it forces the kf to fastboot mode
that will not help in your case because you can get to fastboot mode
and fastboot commands are working
you can't get adb commands to work - this is the problem !
firekit is'nt working eighter ?

ok i see i dont understand i had it on both of my compter and they work fine because i rooted the kindle on these. ther must be something with the way its loading on here. maybe i can try the other compter i have....

you'r talking about firekit ? other computer is a good choice anyway
did you allready read this one :
http://forum.xda-developers.com/showthread.php?t=1552547
it clears up how the kf is working

someone said something about turning off debuging on the computer what do you think?

???
don't know such a option on a computer/win system

Well someone said to mount and download Kindle OS 6.3 and it sould let me boot up. I loaded it backed it up installed it did averything i was told to......but still no work. it still boots up to kindle fire on screen but wont do anything else.
So anybody got anything else i can try?

you where able to copy a new rom to the kf ?
if so that is a great progress - would recommend this one:
http://www.mediafire.com/?8h485buu55cawc5
to clean up partitioning/restore factory partitioning you can use this, just use the newer rom linked above:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
btw first boot after flashing can need up to half an hour

Hi, yes i was able to get the 6.3 update on here by doing mount and sending it as a drive F and it seam to be there. you say it mite take a long time to boot up with this one i wounder it its takes a long time with what i have on there now. maybe it just didnt have time, i did leave it for about 45 min.

This is the one i loaded on here already is this the same one? http://forum.xda-developers.com/showthread.php?t=1569298
the other download you have here sould it be done after the frist or before, I can do a lot of thing on here but some iam not sure if iam doing them the right way, i think that why it didnt get backup the frist time....

that is realy too long - would try to restore factory partitioning as suggested in my last post:
1. set bootmode to fastboot -> fastboot oem idme bootmode 4002
2a. if you'r not in fastboot now pwr off / on the kf - the command should resume and finish - a second pwr off / on should boot fastboot
2b. boot to fastboot -> fastboot reboot
3. download fff 1.2 and extract to your tools folder
4. update fff -> fastboot -i 0x1949 flash bootloader u-boot.bin
5. reboot -> fastboot reboot
6. restore factory partitioning -> fastboot oem format
7. set bootmode to recovery -> fastboot oem idme bootmode 5001
8. boot to recovery -> fastboot reboot
9. flash new rom in recovery -> look at the op of the rom what and when to purge something
10. set bootmode to normal -> fastboot oem idme bootmode 4000
11. pwr off / on the kf - the command should resume and finish - a second pwr off / on should boot up the new system
btw yes it is this one - i recommend and linked in the unsecure version

ok got this thing to this point and dont want to mess up but not sure what to do with bootmode, fastboot not sure where i need to go to get into them

updated my last post and gave you a pm

b63 said:
updated my last post and gave you a pm
Click to expand...
Click to collapse
YEAAAA iamback up and running.....thanks to b63......I want to give a big thanks to b63 for a lot of help with this. Work with me to get it going, getting on my computer and doing what needed to get done. I tried all the things others had said but didnt work. If anyone else is lucky to get help from him then get it, He is very helpfull. Again THANK YOU for all your help.

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

Can't update

So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.

OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse

cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"

dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.

cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?

WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!

For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.

Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator

X800 Fastboot brick

Hi guys I tried to root my LeTV 1 Pro but it didn't worked.
My phone keeps rebooting in fastboot ( I see the penguin 10-15sec and it reboot again and again) or it stays alight with the penguin.
Computer doesn't recognize it.
Thanks.

Try and plug it to your computer then keep power and wol down pressed for like 15 sec: now fastboot should stick and device shouldn't reboot, so you can flash a recovery (TWRP?) and start over with a new ROM.

Thank you for your reply,
It still doesn't work, penguin stays on screen but it's not recognized by computer ( before the brick it was)
I'm not very experienced in rooting btw.
Edit : The recovery.bat in the file X1_X800_TWRP_Recovery2.8.7.0 says "Complete! The device is ready to reboot into Recovery." which I do but it keeps reboot with the pinguin on.

I recieved my phone today and it just wont stay in fastboot mode. I can do anything I want but it just keeps rebooting before I can flash anything. Any suggestions on how I should keep the Phone in Fastboot mode?

You need to install drivers. After that it will not reboot anymore. That worked for me atleast.

What kind of drivers do I need? Please link them to me I have tried a lot of drivers. The thing is that the phone also does not stay in Fastboot mode when not plugged into the PC.

It's my topic for my problem so don't ask questions for you on it please u_u

zamul said:
It's my topic for my problem so don't ask questions for you on it please u_u
Click to expand...
Click to collapse
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.

DatNoob said:
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
Click to expand...
Click to collapse
Zamul don't be mean. He just asked for help as you did...
I have downloaded drivers (I think) from https://twrp.me/devices/letvle1pro.html where I also get twrp 3.0.2.0
Btw if you are using Windows you can open Device Manager and there you will see your device and what drivers it has installed (you can always use update drivers function, maybe that will help too).
Here is a little guide how I managed to get twrp:
Just download it (drivers and intall them) (and download twrp also). Place twrp file to the folder where you have your adb installed.
In phone settings go to developer menu (first you need to unlock it) and you need to switch on usb debugging.
Connect phone to the pc via usb.
Open command prompt in your adb folder and type Adb devices (if you have drivers installed corectly you will se your devices connected under some code).
Then just write Adb reboot booloader and phone will restart to the recovery.
Type into the comand prompt: fastboot flash recovery name***.img (where the name is the file name of twrp you have downloaded- just a tip: rename it so it is easier to remember for example to twrp. Then the command will look like: fastboot flash recovery twrp.img)
If succesful, write fastboot reboot and that is all.
Btw for me it did not work first time. I had to load twrp for second time and when I wrote fastboot reboot then I immediately pressed volume up so It went directly to twrp recovery.
Hope it helps. Cheers

I have this problem
Hello
I have your problem have you solve this?
Thanks

Hi guys. I have a problem! My letv x800 CN boots to TWRP but doesn't start the system (EUI logo loading all the time) I don't know how to transfer ROM into the phone in order to flash it. I installed all the drivers and PC recognize it. PLEASE HELP!!!

Oneplus 6T hard brick?

Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?

FrancescoPtr said:
Hello guys I have a problem, yesterday I was putting the twrp to my one plus 6t via fastboot and as soon as I entered the bootloader I put the command "fastboot boot twrp.img" and it said "fastboot unknow command". So I searched on google for the commands to start the twrp via the PC terminal and I found this command "fastboot flash recovery twrp.img". Everything ok, the screen resumes, 3 minutes later it died. This is hard brick?
Click to expand...
Click to collapse
You are not supposed to flash the image. Make sure you have the latest version of sdk tools. AND if you are new to this kind off stuff READ careful before executing random commands not specific to your device. You might be better advised asking in twrp thread. That would also help keeping the forum clean.