Database Develop

HOW TO: Webtop 2.3.4 HKTW fix

Tested and works (thanks jnl) I'm posting a link to CG61.img for easy loading extracted from 1FF-olympus_hktw-userdebug-2.3.4-4.5.2A-5_OLH-3-110614-test-keys-Retail-05.sbf
Download moto-fastboot for your os from http://forum.xda-developers.com/showthread.php?t=1138092
CG61.img Link - MD5 = 9151fca5183b85953d7afed83364802a
https://www.rapidshare.com/files/4119742271/CG61.img
Steps I followed on OSX:
Download CG61.img (placed in same directory as moto-fastboot)
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with ./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
You might have to reboot the device 2X after this is complete before the webtop option shows up when docked
----=== NO NEED TO FOLLOW THE BELOW STEPS UNLESS YOU EXTRACT FROM THE SBF ===----
Below is from JNL:
Since I have the lapdock and did not want to revert to Froyo, I thought I'd give a more detailed explanation than the hint I worked from to re-enable webtop (with firefox 4.0.1!):
Download the leaked HK/TW sbf file and the 'sbf_flash' for linux (I did this under 32-bit ubuntu).
use sbf_flash -x 1FF-olympus_hktw...sbf
This will extract a collection of .img files.
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with:
sudo ./moto-fastboot32 devices
Then:
sudo ./moto-fastboot32 flash webtop CG61.img
This will run a 3-step flashing process. Once completed, do:
sudo ./moto-fastboot32 reboot
Voila. Webtop works and actually seems faster.
Hope this helps.

mburlingame said:
Steps I followed:
Download CG61.img
./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
Click to expand...
Click to collapse
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?

s1mpd1ddy said:
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
Click to expand...
Click to collapse
I ran this from OSX using the commands I listed jnl ran it from 32-bit ubuntu it looks like via the commands he posted
I placed the image in the same directory as moto-fastboot

Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App

sifon187 said:
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am guessing this should work in Windows as well I am currently installing Windows 7 under VMware Fusion on my mac to confirm.
confirmed I could run this from Windows and did not get any errors back so performing this via the windows moto-fastboot should work as expected

Updated CG61.img link from DropBox to RapidShare due to DropBox shutting the link down due to excessive downloads (according to them)

So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?

brunnogama said:
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
Click to expand...
Click to collapse
You only need to follow the first section (Download the img file and download moto-fastboot for your os)
Are you saying that after you download the img and run moto-fastboot devices you do not see your device listed?
Can you post exactly whats happening when you run moto-fastboot devices then try to load the image on your device via moto-fastboot flash webtop CG61.img (make sure CG61.img is in your moto-fastboot directory)

So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:

brunnogama said:
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
Click to expand...
Click to collapse
Are you running the HKTW 2.3.4 image? ( Image from the following thread http://forum.xda-developers.com/showpost.php?p=15020775&postcount=2 )

Yes! I do!
It isnt correct?

brunnogama said:
Yes! I do!
It isnt correct?
Click to expand...
Click to collapse
Hmm yes that is correct - Can you tell me what OS you are using? maybe try another USB port I will do an md5 checksum on the file and post it maybe a bad download?
MD5 = 9151fca5183b85953d7afed83364802a

Did everything correct... Pretty damn sure. Phone won't even power up now.
Pull battery, plug back in usb cable, get green light, it goes out. Got it to fire up once with no sim.
F*ck !
EDIT: Dumb ass. Don't know how battery drained like a MF. Powered up in wall jack.

So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/

brunnogama said:
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
Click to expand...
Click to collapse
Hmm I have not been able to duplicate this issue - Can you confirm the MD5 checksum? Has anyone else seen this issue with Windows 7 and trying to flash this?

does this fix multimedia dock too? i dont get clock option when my phone is on the dock.

So, I tried on Ubuntu and doenst change anything. I still havent the webdock.
I have the clock issue too. When I plug on lapdock, the clock doenst fit on horizontal position.

Does this work with hdmi cable without any dock?

xabierd said:
Does this work with hdmi cable without any dock?
Click to expand...
Click to collapse
No this requires the Media Dock or the Laptop dock in order to work

Any chance to get the Debian 0.2.5 Webtop back?
Cheers

.621 Root Method - For new OTA Update

***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.

You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk

If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.

link not working
anyone have updated link that works to download this?

yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra

I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks

bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk

nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .

I am going to update the post and host the files. There is also some extra stuff i will put up for download.

For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.

Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse

using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.

BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA

landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk

infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?

BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk

What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...

BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5

This worked great.

Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.

Chromecast won't root

Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help

Patched
Hell.Knight said:
Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help
Click to expand...
Click to collapse
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)

Bild 12072
BusterChestnut said:
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)
Click to expand...
Click to collapse
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?

Hell.Knight said:
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?
Click to expand...
Click to collapse
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.

HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?

Donteventrii said:
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?
Click to expand...
Click to collapse
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.

HowardZ said:
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.
Click to expand...
Click to collapse
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?

Donteventrii said:
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?
Click to expand...
Click to collapse
You live in Baltimore.
I am about one hour drive away.
If you are having so much difficulty, you can come over and I can do it for you.
Howard

HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I used another program and got the exact same lines and loops. I used Win32DiskImager.exe with the same bin, cable and USB stick.....All I was asked when everything was done was to set up my chromecast

Rooted
HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
Thank you man! In fact after using dd my pc would tell me that my usb had no format and I thought it was normal but with win32diskimager.exe it was faster to write to the usb stick and the Chromecast was rooted in no time.
I really appreciate you're help, thanks a lot.

[Q] Total Newb, Question about Soft Brick

EDIT: Many apologies, I now see this belongs in a different thread, specifically the "7" Kindle Fire HD Q&A, Help & Troubleshooting" one... very sorry. I don't know how to move/delete this, and I don't want to repost it there without deleting this one, because double posting = bad. I don't know how to ask a mod to do it, if you can. Sorry for not knowing the forums. Many apologies.
So I'm pretty sure I Soft Bricked my Kindle Fire HD 7". I'm not too mad, but I would like to try and fix it. To be exact, it redscreens on boot.
I was attempting to install TWRP and was at the last few steps when I did it, which seemed like the ones that would brick it. From all my looking around based off what was going on and the log I have from the command prompt.
These where the last steps I took before the problem. pastebin.com/BqGGKziP
My questions are:
Is this a soft brick?
Is it fixable?
If so, any ideas?
I already know if this is fixable to expect to be told I need a developer cable, but please tell me anyways if I do.
EDIT: If I do need one, which I assume I do, where can I get one? Sorry for being a newb, I knew I would probably brick my device, but I really don't know too much about these things and would like to make sure I am getting the right thing.
I apologize for being new and not knowing my way around this forum, and if this is the right place exactly to post this, as well as if I accidentally broke any rules. I'd simply like to know if anyone who knows much could help. Again this isn't a big deal to me, but I would like to get it at least back to it's original state. I will do my best to provide any information asked for.

TecmagDiams said:
So I'm pretty sure I Soft Bricked my Kindle Fire HD 7". I'm not too mad, but I would like to try and fix it. To be exact, it redscreens on boot.
Click to expand...
Click to collapse
Get a tip for your USB cord here to http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm otherwise get a fastboot cord from ebay.
Download the SDK package https://developer.android.com/sdk/index.html
Take take your SDK file and look for the folder that has the ADB.exe in it. I think this is the tools folder. Now open it and stick the drivers stunts has in that folder. Drivers here http://forum.xda-developers.com/showthread.php?t=2477379
Now go install that driver for the Kindle in the device manager. Remember that where ever you CD from, that USB driver has to be in that folder as well. Now open that folder with the drivers in it again and stick the stock Amazon images needed in it (get from restore tool if want or Hascode has some in his OP for this) and hold shift and right click on "open command window here." Now you are in CD cmd. You can probably just as easy CD from inside the system restore tool as well (unzip it.)
With your tablet in fastboot, open a command window and type "fastboot devices" with no quotes and you should be able to see a number and your device. This is good and means there is communications. if not then you need to install the proper drivers.
You need three files. boot.img, recover.img and system.img get them from here http://forum.xda-developers.com/showthread.php?t=2128848
issue these commands
fastboot -i 0x1949 flash boot "your boot image name here."
fastboot -i 0x1949 flash recovery "your recovery image name here."
fastboot -i 0x1949 flash system "your system image name here"
Make sure you end the commands with .img
Wait a little bit for it finish
fastboot -i 0x1949 reboot
Your bootloader crashed and that's why the red screen. You forgot to tick the the option to flash Amazon OS 7.2.3. always works better to downgrade to 7.2.3 first (for 7" KFHD)

Thanks a ton, and sorry for posting this in the wrong spot, I did find how to report it for a move.
I will hold onto this information and get myself the cable, try it out, and see where things go. Again, thanks for helping someone who hasn't a clue. ^.^

TecmagDiams said:
Thanks a ton, and sorry for posting this in the wrong spot, I did find how to report it for a move.
I will hold onto this information and get myself the cable, try it out, and see where things go. Again, thanks for helping someone who hasn't a clue. ^.^
Click to expand...
Click to collapse
No worries. If you get hung up, hit "reply" under the post above and respond. That way it goes to my email. Good luck and don't get overwhelmed.

So I recently got the head piece from the store you linked me to, and I have been attempting to follow your steps, but I am having trouble at one I thought would be fairly straightforward. Installing the drivers.
My device manager shows no device to update the drivers for. I'm sure I'm just not knowing something really simple, but I'm not sure how to install the drivers you showed me without having the device to update in the Device Manager.
Additionally I would just like to ask that once I have the drivers installed, how do I get the device into fastboot? Is it just running a line of "fastboot -i 0x1949 getvar product" and then plugging it in?
Thanks again for all the help.

TecmagDiams said:
So I recently got the head piece from the store you linked me to, and I have been attempting to follow your steps, but I am having trouble at one I thought would be fairly straightforward. Installing the drivers.
My device manager shows no device to update the drivers for. I'm sure I'm just not knowing something really simple, but I'm not sure how to install the drivers you showed me without having the device to update in the Device Manager.
Click to expand...
Click to collapse
Try these drivers http://forum.xda-developers.com/showthread.php?t=2477379 Update them through device drives.
Make sure you have the SDK package downloaded and the paths set. watch this video for a great tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw
Are you using a Windows7 X64 or Windows 8? If you are, you need to disable driver enforcement as well. You will want to do this first.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
bcdedit /set nointegritychecks ON
bcdedit /set nointegritychecks OFF
Possible Windows 8 cmd
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
Additionally I would just like to ask that once I have the drivers installed, how do I get the device into fastboot? Is it just running a line of "fastboot -i 0x1949 getvar product" and then plugging it in?
Click to expand...
Click to collapse
With the tablet powered completely down, plug the USB cord (with tip) into the USB port and also the tablet. The tablet should lit up and say fastboot. At this point, the tablet will stay energized and in fastboot.
Thanks again for all the help.
Click to expand...
Click to collapse
You're welcome
Click to expand...
Click to collapse

So I booted up with the driver security disabled, however I'm still having the problem that no where in the device manager can I find my device to update the drivers for.
I'm super sorry if I'm missing something obvious and simple, I just don't see what it is, and thusfar all my attempts have simply resulted in plugging in the usb to the tip and tip to the device and having absolutely zero reaction.
I am running Windows 7 (64bit) to answer that question, sorry I didn't think to say that before.

TecmagDiams said:
So I booted up with the driver security disabled, however I'm still having the problem that no where in the device manager can I find my device to update the drivers for.
I'm super sorry if I'm missing something obvious and simple, I just don't see what it is, and thusfar all my attempts have simply resulted in plugging in the usb to the tip and tip to the device and having absolutely zero reaction.
I am running Windows 7 (64bit) to answer that question, sorry I didn't think to say that before.
Click to expand...
Click to collapse
I just looked on your pastebin link. That is an incredibly old TWRP. The most recent one is 2.6.3.1
The reason you had the red screen is because you never flashed a bootloader. I see a boot.img and a recover.img
If you are getting no response at all, even with the fastboot tip on the USB cord, you could have a hard brick. If you can try another USB cord first to make sure. Maybe another port on your computer.

LinearEquation said:
I just looked on your pastebin link. That is an incredibly old TWRP. The most recent one is 2.6.3.1
The reason you had the red screen is because you never flashed a bootloader. I see a boot.img and a recover.img
If you are getting no response at all, even with the fastboot tip on the USB cord, you could have a hard brick. If you can try another USB cord first to make sure. Maybe another port on your computer.
Click to expand...
Click to collapse
Welp, as I said, I'm not too mad, and I knew going in that I would never be sure enough to know what I was doing.
From the seems it would be hard bricked then, because with the tip I get no response, I've tried all 3 of my cables, and all of my ports. Thanks for all the help though, it's very much appreciated. ^.^

TecmagDiams said:
Welp, as I said, I'm not too mad, and I knew going in that I would never be sure enough to know what I was doing.
From the seems it would be hard bricked then, because with the tip I get no response, I've tried all 3 of my cables, and all of my ports. Thanks for all the help though, it's very much appreciated. ^.^
Click to expand...
Click to collapse
Bummer. Maybe next time eh???
Sent from Nexus 7 flo running SinLess ROM 4.4.2 with ElementalX kernel using xda app-developers app

using osx to unlock bootloader???

first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter

If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.

I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.

You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237

geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter

geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter

pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike

Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter

sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!