Develop Bugs

[Q] How to pull photos from Boot Looping Galaxy Nexus? HELP!

Help! My Galaxy Nexus sudden going through BootLoop (Google logo kept coming back).
I have new born baby photos and video that I need to pull them out to my PC.
SO I read Mike 's Toolkit 7.8 and trying it.
I do not know what extract model and built is my phone. This is original phone so I bootloader is still LOCKED.
With Mike toolkit I followed up his Toolkit instuction #14.
Here is what I done.
1) In GNex TOOLKIT V7.8. I choose from 4.0.1 to 4.0.4 android build and model version (Yakju-Maguro since I am in Canada using Rogers/Fido as Carrier). Then I chose option#1 to install Nexus Window 7 drivers. This didn't work. My Window 7 did'nt regconize it.
2) During the installation of PDaNet. I hold Power On Buttom + Up Bottom (I think) Fastboot mode. I am able to get a page that shows me my "bootloader version", "Baseband version" etc...Only then PDaNet then installed Android driver successfully to my WIndow 7 Device Manager.
3) Go back to Toolkit V7.8 menu. Choose all 4.0.1 to 4.0.4 android build and model version.
I can now see my Serial Number on then top left side onw.
4) Then I chose #14 pull data from my phone.
It said the Device not found/regconized. Choose 4.0.1 to 4.0.4 android build and model
So I don't what I did wrong..
Please help..me..
I can only access to fastboot mode? Can I still files/photos pull?
Help me
Thank you very much! Your help is greatly appreciated!

step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9

Zepius said:
step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9
Click to expand...
Click to collapse
Thank you Zepius! Got few question..
My phone is in bootloop .so I can't go to android market and install Android SDK. I can't turn debugger mode on..
"assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager."
Installation of Android SDK to my window 7 pc?
Please tell me what I need to do. Much appreciated!

First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.

Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
This will not flash the custom recovery but it will boot it once. The adb command will copy your entire sdcard contents.
Sent from my Galaxy Nexus using Tapatalk 2

strumcat said:
First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.
Click to expand...
Click to collapse
Thank you for your help!
1wayjonny's driver is called "Universal Naked Driver 0.7"?
http://forum.xda-developers.com/showthread.php?t=1161769
Where can I find efrant's threads about adb + fastboot zip file(s)?
Sorry to keep bothering you.
Thank you!!

Petrovski80 said:
Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
Click to expand...
Click to collapse
Thank you!
My first and most priority is not to fix my bootloop issue but I need to get my phone photos+video backup.
So can I just make sure I get adb (Android SDK development and tools install) and adb my device?
then adb pull /sdcard c:\somepaththere?
I just want backup it first .. before I fix my phone or fastboot boot recovery nameofimage.img.
Thank you again.. I already lose some nights of sleeps because when I thought of photos that I took with my baby.
Gosh.. what a nightmare!

May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2

Duce HD2 said:
May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. Once I get my photos and phone fix. I will.
Actually my coworker just said the same thing to me.
He has Samsung Nexus phone as well.
Thank you.

Someone please confirm me.
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?

jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879

jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
Click to expand...
Click to collapse
Yep.
2) Install Android SDK with adb and fastboot commandline to my PC?
Click to expand...
Click to collapse
You don't need the entire SDK. You can if you want to, but unless you're planning on developing apps on Android, the SDK is overkill for just fastboot and adb. I suggest using the package efrant links to in his 101 & FAQ: http://forum.xda-developers.com/showthread.php?t=1812959
3) Boot my Nexus to bootloops (power buttom+volume)
Click to expand...
Click to collapse
Into bootloader: volume up+down+power.
4) Then connect my phone with USB and connect to my PC
Click to expand...
Click to collapse
Yes.
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
Almost. Adb won't work in when booted into bootloader. When you are in the bootloader, use the steps I mentioned earlier. In custom recovery, you do have the adb interface.

efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data? Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!

jurassic98 said:
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data?
Click to expand...
Click to collapse
No, it won't wipe anything.
jurassic98 said:
Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!
Click to expand...
Click to collapse
Yes, that's exactly like what it is.

efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
From my understanding you can't pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good

henno87 said:
From my understanding you can pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good
Click to expand...
Click to collapse
Nope, you cannot. fastboot = fastboot, adb = adb. Different interfaces.
Try it.

efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.

strumcat said:
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.
Click to expand...
Click to collapse
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.

efrant said:
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.
Click to expand...
Click to collapse
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!

jurassic98 said:
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!
Click to expand...
Click to collapse
You said your bootloader was unlocked in the first post, no???
jurassic98 said:
[snip]
I do not know what extract model and built is my phone. This is original phone so I bootloader is still unlocked.
Click to expand...
Click to collapse
If your bootloader is locked, which it obviously is, you canNOT use what I had suggested. You need to try using ADB backup (use copkay's guide). However, as I mentioned before, given that you have a bootloop, it may not work...
This is a prefect example of why you should leave your bootloader unlocked -- if it was, you'd easily be able to recovery your data.

[Q] Trouble with flashing new recovery

Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-

Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app

Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery

Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.

It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.

I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.

zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img

spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u

Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.

Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.

Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app

[Q] Eeek, help!! In TWRP, can't get rom onto kindle to flash!!

Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys

6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL

Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.

Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL

Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next

I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL

I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!

You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL

GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx

Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL

Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help

Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:

HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!

OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!

HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!

OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.

[HOWTO] Complete guide stock 4.3, root and recovery - Samsung Gnx GSM (Linux/Win 7)

Hi All,
I have spent this afternoon rooting stock 4.3 yakju and thought that I'd share the latest on how to go about doing this manually for the maguro GT-I9250. This is a complete guide which brings all the information you will need under the one thread which doesn't seem to have been done before except as separate guides and scattered information all over the internet.
NOTE: Unlocking and Rooting your device will void your warranty and can in some instances if not performed properly brick the phone. This process will also wipe your phone back to factory defaults so any personal files and applications will be lost. You should backup the device using the backup options in the recovery environment or by saving any personal files off the device via the USB cable, prior to unlocking your device. You follow this procedure at your own risk!!
With that disclaimer out the way there, We can begin.
NB: I ran all linux commands in this tutorial as root, I am not able to say if running as a standard user may cause issues, although one forum suggested to run as root or sudo up if you have a bootloop issue so I did this to avoid problems. This tutorial assumes that you have some experience with using basic Linux commands including but not limited to copying and moving files, changing directories, listing files, running scripts and executables using './' and using the console
So Firstly I am running Fedora 19 x64 with the latest kernel. It's a lot easier than trying to muck around with Windows 7 drivers and there are tutorials for installing these. To update on that tutorial you can use the official samsung drivers to install the adb and mtp drivers (may already be noted in the thread, but I might as well state it here also.) and the best place to get the official samsung drivers is by installing the Samsung Kies application.
You need to enable 'USB debugging' in order for ADB to work, you do this from 'settings --> developer options' if you can't see 'developer options' you may need to enable them, to do this, select 'settings --> about phone' and tap 'build number' until it says 'you are now a developer' which takes around 7 taps. In 'developer options', you may need to turn them on by clicking the 'on' button at the top. Once you have turned them on, select 'usb debugging' and this will then tell you that 'this may make your device less secure', agree/accept this, and continue. You can always turn it off later if you need to. Once you enable this, within linux you may get prompted when running adb to authorize (e.g. you are not authorized, check the device screen). You need to authorise from the phone, so allow the connection and select 'remember this computer' to save having to do it again.
Now for the bootloader driver it's a bit trickier to install. You need to reboot into the bootloader, by powering off the device and then powering back on again while holding the volume + and volume - keys at the same time. You will then probably get a failed driver install for 'Android 1.0'. At this point, you will need the universal Naked driver from this thread. Download and extract it to your 'Downloads' folder. Now go to device manager, right click on the 'Android 1.0' device and select 'update driver...' and then select 'browse my computer for driver software' and then select 'let me pick from a list of drivers'. Click 'have disk' and you will be able to install from the folder you extracted the 'Universal Naked Driver' into. You will now be able to use the fastboot command in Windows.
Ok. Now we have the windows users covered. In Linux, All I needed to do was download the android sdk adt tools. I'm using the 64 bit version, so I downloaded the 64 bit version from the adt bundle section here. Once I had downloaded and extracted these into a folder in my Downloads folder under my user profile, I copied the adb and fastboot files to a separate folder as these are the only things I needed in the bundle. you do this by typing
Code:
cp /home/<your_username>/Downloads/Androidadt/adb /home/<your_username>/Downloads/Nexusroot/
cp /home/<your_username>/Downloads/Androidadt/fastboot /home/<your_username>/Downloads/Nexusroot/
From here on you will want to be working from the 'Nexusroot' folder, so type
Code:
cd /home/<your_username>/Downloads/Nexusroot
.
From here, you need to obtain the recovery you wish you use, I chose to use the CWM v6.0.4.3 touch recovery which can be obtained from here. Once it's saved to your downloads folder you should copy it to your previously created 'Nexusroot' folder where we saved adb and fastboot.
The next item on the list is something I did because I was running the yakjuxw firmware and is the reason I did everything in Linux for this tutorial, as the firmware files are tarballed and opening the tar in 7zip shows 'unix filesystem' as the base folder. I installed the stock 4.3 firmware from google. I used the extracted files for the firmware as my 'Nexusroot' folder and copied fastboot and adb into this folder as well as the recovery image. I then ran ./flash-all.sh with the device in fastboot mode (you will need to have unlocked the bootloader prior to doing this, instructions are below in the next paragraph. The script basically just flashes the firmware with the fastboot command, if you want to flash the CWM recovery at the same time, you will need to rename the recovery file to the same name as the recovery image in the tarball and replace or rename the one that came with the tar file from google), If you have setup your environment in Windows 7 as described above, there is also a batch file that will do the same thing ensure the device is in fastboot before running the batch file/script or it will sit there and say 'waiting for device' and make sure the fastboot application is in the same folder as the script. Once the flash is complete your device will be running the stock 4.3 firmware. (edit: I have since extracted the entire image out of the tar with 7zip from Windows 7, you will be able to flash the base once you extract it all to a folder but you need to open the secondary container file in 7zip separately)
The next step is to flash the recovery. To do this, put the device into fastboot mode and unlock the bootloader using the command
Code:
fastboot oem unlock
select 'Yes' at the prompt, your device will now reboot twice and perform a factory reset which will wipe all data, at this point you may need to re-enable 'usb debugging' from your settings (see above for instructions), re-enter fastboot mode by typing
Code:
adb reboot bootloader
next type in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-maguro.img
Your device will now install the touch recovery we downloaded earlier. Once done, type the command
Code:
fastboot reboot-bootloader
.
Now to root the device, download the SuperSU zip file from the link and copy it to your 'Nexusroot' folder. Now boot into your recovery environment by using your 'Volume -' key to select 'boot recovery' and allow the device to boot into the recovery environment. This will allow you to use the adb command. Change directory into your 'Nexusroot' folder if not already in it, and type
Code:
adb push UPDATE-SuperSU-v1.43.zip /sdcard/0
This will copy the zip file to the internal memory card. From the recovery environment on the phone, select 'install file from sdcard' and then 'choose zip from sd card'. Select '0' and then select the 'UPDATE-SuperSU-v1.43.zip' file and select 'yes - install...' and the zip file will install the SuperSU application and binaries. Your device is now rooted, however you will need to run the SuperSU app to update the binary again. We will discuss this further after the next step.
Now we should lock the bootloader again to prevent tampering with our recovery and other firmware images however if you wish to flash other ROMS you will want to leave this unlocked, or you will need to unlock it again next time you want to flash a rom. To lock the bootloader, with the phone in fastboot mode, you simply type
Code:
fastboot oem lock
and this will re-lock the bootloader. Note you will not be able to flash any radios, kernels, or other .img files while this is locked. Now reboot your phone back into Android.
Now that you know how to unlock your phone, it's rooted, and has a recovery environment installed, you need to activate your SuperUser install. To do this, open the SuperSU app, and when prompted to update, click 'continue'. You will at this point be asked how you want to install it, select 'CWM/TWRP Recovery' and your phone will reboot, you will see an update occur on the screen and SuperSU will now be correctly installed.
You can now begin experiencing the freedom to use whatever ROM you want, customise your device how you want, and even change which applications you want installed regardless of whether they are system apps or otherwise.
I hope this guide is helpful.
References:
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=1830108
http://forum.xda-developers.com/showthread.php?t=2117822
http://forum.xda-developers.com/showthread.php?t=2065470
http://www.ibtimes.com/how-root-galaxy-nexus-i9250-nexus-4-android-43-jelly-bean-official-firmware-tutorial-1362063
http://www.clockworkmod.com/rommanager
https://developer.android.com/sdk/index.html
http://www.ubuntu.com/phone/install
https://developers.google.com/android/nexus/images
Thanks:
@1wayjonny
@TECK
@samersh72
Without your guides I wouldn't have been able to do this.

commandprompt does not work

Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastboot getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John

Joheee said:
Hi all,
maybe a very silly question, but when I followed the instructions on https://wiki.cyanogenmod.org/w/Install_CM_for_amami, one of the steps is to open a cmd and type: fastbood getvar version. And well, when I do that and press enter, it says that: fastboot is not recognized as an internal or external command, program or batch file.
The phone is in fastboot mode (a blue light is on), and i have installed sdk and jdk 8u60 on my computer, which runs on windows 7.
Also my computer says that the device driver program is installed.
By the way, when installing jdk, it said I should enter "javac -version" in cmd, but that gave the same notification, howver jdk is installed on my computer.
Who can help me out?
Thanks in advance,
John
Click to expand...
Click to collapse
Probably just a typo, but you wrote 'fastbood' in your post. Computer definitely won't recognize that. If you are spelling it right, either 1) you're in the wrong directly in terminal, (cd /(wherever adb is installed), or 2) adb package didn't install correctly, (reinstall). While you're testing it, you can just type 'fastboot', and you should get a list of command options, showing that it is installed.

Sorry yes fastbood was a typo. But what do you mean with: you're in the wrong directly in terminal, (cd /(wherever adb is installed).
A terminal is the same as a command prompt right?
And to reinstall adb package, i would have to delete the platform-tools right? And when i click on delete package, it asks if Im sure about it, bacause it can not be undone.

When you open command prompt, you're 'in a directory', usually in Windows, it's C:/(user)/desktop, or something. You need to get to the directory where adb is. If you installed it with defaults, it's probably C:/adb. If so, once you open command prompt, type 'cd /adb', and hit 'enter'. Then you'll be 'in the right directory'. If adb installed somewhere else, you'll have to find out where, then type 'cd /(whatever)/(whatever)/adb.

I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!

Joheee said:
I still did not get it working. I deleted the whole android studio package and intalled the sdk tools only now, and installed platform tools in it and tried it all again.
My initial goal was to enter 'fastboot getvar version' in commandprompt. What I tried thus far:
This page (https://wiki.cyanogenmod.org/w/Doc:_adb_intro#Popular_adb_commands) said I should paste ;<path-to-sdk>/platform-tools behind the word Path in Environment variables so I did.
When I open commandprompt it already gives automatically: C:\Users\BTO>
When I just type adb there and hit enter, it says it is not recognized. When I hit cd /adb it says it can't find the given path. (why should I type adb at all by the way, and not fastboot getvar version?)
When I do first 'cd /' it gives C:\> and then adb it also says it can't find the given path.
When I hit C:\>Program Files (x86)\Android\android-sdk\adb it says it can't find the given path.
Deletion of the ;<path-to-sdk>/platform-tools behind Path in the Environment variables does not help.
Thanks for helping me!
Click to expand...
Click to collapse
First thing you have to do is find out where on your PC the adb files are. The computer won't recognize anything you type with fastboot, adb, etc., unless you're in that directory. I believe adding the environmental variable path is supposed to make that easier, but obviously it's not working out for you, so I would just skip that and find out where the files are, then you can just use 'cd', and go there. It should be easy to do a search in Explorer if you can't find it.

Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.

Joheee said:
Thank you that you keep helping me.
I worked already 6 hours on it now in total and did not really get any step further. I found the adress of the adb files (the maps were hidden).
I found this page on internet: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
So I followed those steps very precize, I installed the google usb driver in sdk.
Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same case when it's just turned on.
Still when I run fastboot getvar version it says <waiting for device>...
The https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro page gives some poor troubleshooting info about this error. When I hit fastboot devices in the right directory it does not even give the waiting for device error. Changing usb ports does not help either.
Maybe it's something with the 'elevated privileges', I dont't know what they mean with that. But I have Administrator rights.
Click to expand...
Click to collapse
Can you tell me what directory on your PC the adb files are located? As far as drivers, best bet is usually PC companion, or Flashtool.

Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks

Joheee said:
Hi,
I found some time again. I have installed PC companion, but it doesn't show me how to install drivers. It says the software is up to date.
The location of the driver is C:\Users\BTO\AppData\Local\Android\sdk\extras\google\usb_driver
The location of the ADB files is C:\Users\BTO\AppData\Local\Android\sdk\platform-tools
Thanks
Click to expand...
Click to collapse
If PC Companion is giving you that msg, you might be OK w/ drivers. With that being the location of your adb files, you would open command prompt, and type - cd \Users\BTO\AppData\Local\Android\sdk\platform-tools\adb - then you'll be 'in' the right directory, (just to make sure, look in the 'adb' folder and see if fastboot exe is in there). Your command prompt should show - C:\Users\BTO\AppData\Local\Android\sdk\platform-tools\adb. Then type 'fastboot', and you should get output of command options.
If all goes well and you want to make it easier in the future, just move the whole 'adb' folder to C drive root. Then you'll only have to type 'cd \adb'.

Or you could just open a window in the correct directory, hold right shift button on keyboard and click right mouse button and select "open command prompt here "
Easy peezy

I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."

Joheee said:
I already found how to fill in the commandprompt from the link from my post of 27 september (you can also go to the map, and shift+rightclick > open command here, then you can misspell anything). But the problem is it doesn't recognize my device. When I go to the right directory and fill in:
fastboot devices > nothing at all
fastboot device > <waiting for device>
fastboot getvar version > <waiting for device>
fastboot > a lot of stuff
adb devices > list of devices (but no items show up)
adb device > a lot of stuff
But to repeat a previous post: "Because the commandprompt still did not recognize the device (list of devices did not give any results) I was trying to force installation of the driver on my phone, but that is the step I now got stuck on. When I try to install it in fastboot mode (my device is then called S1Boot Fastboot in device manager) it says it can't find any drivers for my device (while I selected the right folder and clicked next??) and the same is the case when it's just turned on."
Click to expand...
Click to collapse
Sorry i missed that... How about Flashtool driver installer? If you DL Flashtool, there's an exe in the 'drivers' folder that will install for you.

Hey you might be using windows 10,8,8.1 if so follow this guide http://forum.xda-developers.com/xperia-u/issues/guide-how-to-install-fastboot-xperia-t2170114
All The Best

Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.

Joheee said:
Finally getting somewhere, flashtool worked, so fastboot getvar version and all stuff gave some answers.
I extracted the CM11 files, but when I enter fastboot flash boot boot.img in the platform tools directory, it says error: cannot load boot.img.
The CM11 map is in downloads, is is going wrong there? Or something else. The phone is in fastboot mode.
Click to expand...
Click to collapse
Try different files. Here's a boot IMG that I've used successfully - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM - and try this for recovery - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
Use 'fastoot devices' before flashing to confirm connection.

That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?

Joheee said:
That didn't work either. I downloaded the files of your links (btw I wouldn't also know what to do with the recovery file), so they are in my Downloads map of my laptop (can I just leave it there?). Then I wrote in the platform tools directory 'fastboot devices' and it gave an answer. When I filled in 'fastboot flash boot boot.img' it said it cannot load boot.img
And maybe I'm getting it wrong, but the size of the CM11 download is 262.87 MB (I took the first snapshot in this list: https://download.cyanogenmod.org/?device=amami), and the size of that boot.img is just 12.1 MB, so I think that that single .img can never be enough for the whole installation of CM11 though?
Click to expand...
Click to collapse
The boot and recovery files will just enable you to get into recovery. You'll need a ROM file to put a ROM on your phone. There are many to choose from in the 'android development', and 'original android development' threads. To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img'). Then you can reboot into recovery. Once you download your ROM file, you want it to be on your SD card in the phone. When you get into recovery, you go to your ROM file and install.

Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.

Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 40 minutes on the blue 'waving' startscreen, and getting quite hot even.
Click to expand...
Click to collapse
If your phone is stock, it won't boot with the new IMG you flashed. That's also why the computer doesn't recognize it. You can copy your ROM onto the SD card with your computer, using a card reader or adapter. Just flash both IMGs, then unplug, then turn it on, and hit vol up when you see purple. Make sure you type flash 'boot' for the boot, and flash 'recovery' for the recovery, not 'boot' for both. Also, if you want, there are custom IMG files with recovery on xda for stock ROM that you could flash the same way, if you just want to use your stock.
---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------
Joheee said:
Ok so I did this: "To flash with fastboot, put the boot.img and recovery.img files on your PC in the same directory as your adb files, (fastboot, etc). Then type 'fastboot flash boot boot.img', and when that's done, type 'fastboot flash recovery recovery.img, (make sure yor files are named 'boot.img, and 'recovery.img')."
Then I typed fastboot reboot, and it gave: rebooting... with total time 0.008 seconds, and I hit a couple of typed volume down (it said volume rockers on the how-to-wiki, so i guess it doesnt matter up or down) and then the screen turned black (but it's on), and the notification light is off. Battery was 80%, but phone is getting quite warm.
Furthermore, in 'my computer' the phone is not present. So I can not put the download (the CM11 folder of 262.87MB) on the sdcard. When looking into device manager, it could find it at portable devices but with a yellow exclamation mark, with as reason the device does not start (code 10). PC companion also said there is a mistake in the connection between the phone and the computer and advises me to get the phone off the computer and restart it. Good idea?
Update, it's now already over 1,5 hours on the blue 'waving' startscreen, and getting quite hot even. So it is stuck.
Click to expand...
Click to collapse
Try this for stock - https://mega.nz/#!k0cTUQbS!5XUZhTEK4xBKVBSeO83TEHE3xs9JEpvxt3g1Sc8tVH8