can someone point me in the right direction on how to put factory recovery and rom back on my neighbors kindle fire so he can return it im not familar with kindle fire but did many android and windows before thanks
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
powerpoint45 said:
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
Click to expand...
Click to collapse
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
maxtcee said:
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
Click to expand...
Click to collapse
yes it will remove twrp make sure you do a full wipe before attempting or you could get some mild brickage requiring a factory cable. wipe factory reset,wipe cache,wipe dalvik, wipe system, flash update.zip reboot then system if prompted...
i wipe everything like you said and for some reason it boots into logo screen then a black screen and stays black i cant seem to get it back into recovery
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
soupmagnet said:
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
Click to expand...
Click to collapse
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
EDIT i d/l pokeys fbmode and replaced it in kfu and tried to change the boot mode to fastboot but still hanging am i doing anything wrong ?
any other suggestions
maxtcee said:
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
Click to expand...
Click to collapse
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
soupmagnet said:
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
Click to expand...
Click to collapse
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
im not seeing that option to open cmd prompt here
im using kfu 9.6 dont know if that makes a difference
maxtcee said:
im not seeing that option to open cmd prompt here
Click to expand...
Click to collapse
Shift + right-click...at the same time
soupmagnet said:
Shift + right-click...at the same time
Click to expand...
Click to collapse
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
maxtcee said:
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
Click to expand...
Click to collapse
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
soupmagnet said:
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
Click to expand...
Click to collapse
i know but its telling me
its not recognized
maxtcee said:
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
soupmagnet said:
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
Click to expand...
Click to collapse
thanks dude time to get drunk and worry about this in the am
Nevermind
Thepooch said:
Nevermind
Click to expand...
Click to collapse
Yeah, that page #2 is a tricky one, eh?
Yeah my bad didnt realize you were that deep yet lol
Related
rootzwiki.com/_/articles/twrp-20-touchscreen-recovery-officially-released-r236
Thanks for all the hard work guys.
Sent from my Kindle Fire using Tapatalk
really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help
wtphoto said:
really want to flash this but I cant get adb to recognize the device. dont know what the issue is can anyone help
Click to expand...
Click to collapse
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.
sl0ttedpig said:
Do you have Droid Explorer installed? If so, either find a way to disable it starting, or uninstall it.
Click to expand...
Click to collapse
I have root explorer will that cause it as well?
wtphoto said:
I have root explorer will that cause it as well?
Click to expand...
Click to collapse
You mean on your device? No, that would make any difference. I'm talking about software installed on your PC.
no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason
wtphoto said:
no I dont, running mint 12 and can connect to my evo no problem but doesnt see the fire for some reason
Click to expand...
Click to collapse
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?
do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?
Did you add the edited USB vendor id?
Have someone tried to boot normally from this recovery
Sent from my Nexus One using XDA App
sl0ttedpig said:
Make sure you don't have any command windows open, then open Task Manager, and see if adb.exe is running. If it is, then you have a program that is using it's own version which is potentially overriding yours. Stop it or uninstall it.
At this point, I'm also presuming that you are rooted and so have 0x1949 in your adb_usb.ini file?
Click to expand...
Click to collapse
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
wtphoto said:
I am rooted but when I open the usb_.ini file there is nothing listed there, this is all I have in it
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Click to expand...
Click to collapse
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------
devastater said:
do i need to put the "twrp-blaze-2.0.0RC0.img" in a certain folder before flashing?
Click to expand...
Click to collapse
Put it in the same directory as fastboot.exe, which generally goes in the same directory as adb.exe.
sl0ttedpig said:
Add 0x1949 to it. Not sure how you could be rooted without having done this step at some point!
Click to expand...
Click to collapse
yeah i did that and it worked, when I rooted I was running mint 11 and then my HDD fried and I had to reinstall and when I did I switched to mint 12 but never updated the usb.ini. I feel about retarted now
thanks for the help
I decided to flash this a different way then said in their post - the way JackpotClavin has us, it sounds a bit firmer. Also, I have FIREFIREFIRE installed, in most cases installing this recovery is pointless unless your have FIREFIREFIRE, so assuming you have FIREFIREFIRE installed you can skip some steps.
This method does NOT require fastboot, so you don't have to go searching around for a bin! (then again, if you have FIREFIREFIRE installed I assume you already have a bin, >_<)
Requirements for my instructions:
FIREFIREFIRE installed
ADB up and running!
adb push *DIRECTORY OF YOUR IMG*\twrp-blaze-2.0.0RC0.img /sdcard
You may need to put the path in parentheses if you have a space anywhere in the path!
adb shell
cd /sdcard
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
reboot
Now it is installed, and it rebooted so press the power button to get into recovery! It'll install it then reboot again, just go into recovery again.
There, you successfully installed it.
Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?
adam900710 said:
Help!!!!
I flashed it according to the instruction in their homepage.
But the KF doesn't wake up,just hangs on the yellow fire picture.
I think it's in fastboot mode(because i set bootmode to 4002)
But my PC can't recognize it,so I can't use fastboot to change the bootmode.
Anyone can help me?
Click to expand...
Click to collapse
How could you make those instructions work?
Mine doesn't go further than the below ...
adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# idme bootmode 4002
idme bootmode 4002
<idme> write 4002 to offset 0x1000
# fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot: not found
#
Click to expand...
Click to collapse
andTab said:
How could you make those instructions work?
Mine doesn't go further than the below ...
Click to expand...
Click to collapse
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.
edit: fixed myself
adam900710 said:
You should reboot you KF and the KF will boot into fastboot.
Then you type fastboot command in you terminal.
It will be a screen showing that the recovery is installing and will reboot.
Click to expand...
Click to collapse
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options
loki154 said:
I'm rebooted once i set the bootmode and the kindle fire logo is showing, but when i type
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
all i get is a list of fastboot options
Click to expand...
Click to collapse
Change "twrp-blaze-2.0.0RC0.img" to the path of the img you downloaded.
Not just "twrp-blaze-2.0.0RC0.img".
I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
pistol865 said:
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
Sent from my XT1028 using Tapatalk
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
pistol865 said:
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
Click to expand...
Click to collapse
Stuck at Boot logo?
With animation or no change?
Sent from my XT1028 using Tapatalk
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
Does boot logo, fade in and out slightly?
Sent from my XT1028 using Tapatalk
No fading in and out.
pistol865 said:
No fading in and out.
Click to expand...
Click to collapse
It's in fastboot mode then, send the fastboot commands
Sent from my XT1028 using Tapatalk
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
pistol865 said:
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
Click to expand...
Click to collapse
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
sd_shadow said:
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Also whenever I try and run a command from CMD.. I also get "ADB server didn't ACK.. cannot connect to daemon".
pistol865 said:
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
sd_shadow said:
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
Click to expand...
Click to collapse
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
pistol865 said:
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
Click to expand...
Click to collapse
Create a folder in c drive named adb
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
However, once again, whenever it goes into the CMD phase, I get the phrase: "ADB server didn't ACK... Cannot connect to daemon"
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
pistol865 said:
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
Click to expand...
Click to collapse
I have not got that to work with System version 6.3.3 or 6.3.4.
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
Click to expand...
Click to collapse
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
sd_shadow said:
I have not got that to work with System version 6.3.3 or 6.3.4.
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
Click to expand...
Click to collapse
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
pistol865 said:
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
Click to expand...
Click to collapse
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
sd_shadow said:
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
Click to expand...
Click to collapse
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
pistol865 said:
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
Click to expand...
Click to collapse
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
pistol865 said:
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
Click to expand...
Click to collapse
Did you use install.drivers.bat from Kindle Fire Utility? If not do so now.
Then watch my video, follow my written steps.
On a fresh device, I used KingRoot and obtained Flashify to try to flash on the TWRP for my device with the intention of putting on Cyanogenmod. Plain and simple, the result was this: anytime I try to enter Download Mode or Recovery Mode, I get flashing red and blue lights.
I've tried rooting with KingRoot additional times, but it always seems to go away on reboot. To make it worse, I can't even get rid of KingRoot.
Anyone got ideas? And please don't link any "D855 ONLY" threads, because I've looked through those.
i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.
G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.
inasar said:
i would suggest you flash TWRP from an adb shell.
If this fails you could try and flash CM13 and then flash TWRP.
---------- Post added at 10:45 ---------- Previous post was at 10:43 ----------
Plus I don't think G3 has a fastboot / bootloader mode anyway. I haven't been able to figure it out. Maybe someone else can comment and correct me.
So, as I see it all should be worried about is getting the right recovery on your phone.
Click to expand...
Click to collapse
From what mode can I flash it? I thought you had to be in download or fastboot mode to execute ADB shell commands.
Jahanzaibawan said:
G3 has fast boot.so you can also use adb to flash the recovery.the problem might be due to mismatch of recovery and your model number.first make sure the model and then flash accordingly.
Click to expand...
Click to collapse
It's the correct recovery file for the model. I can't get to fastboot mode.
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I've got ADB set up on my Windows PC back at home already, so I may have to wait until I get home from traveling (next Friday). All I have available to me right now is my Chromebook with Linux.
Thank you for the steps, though. I'll try that as soon as I get home. Might even try to borrow someone else's computer to give it a whirl.
inasar said:
Well, can take the following route:
1. Enable USB debugging on your phone in Developer Settings
2. Setup ADB on your windows computer. There are plenty of tutorials for both Windows and Mac online and on XDA
3. Open up a terminal window and type in adb devices to check your ADB environment is correctly setup. Your phone should show up as a result of this command in the terminal
4. Type adb shell
5. This will take you to a #: prompt in the terminal
6. Now you type in adb flash recovery <path of recovery file .img>
7. Reboot to recovery
Click to expand...
Click to collapse
I get "/system/bin/sh: adb: not found" when I do this. Can't seem to figure out what that means.
Do you have adb setup on your pc?
inasar said:
Do you have adb setup on your pc?
Click to expand...
Click to collapse
Yes, and when I use the adb devices command, my phone shows up.
Ok can try the same but skip the point where you type adb shell
btothemose said:
Yes, and when I use the adb devices command, my phone shows up.
Click to expand...
Click to collapse
Did you try it again. I think it should work. If it didn't then there is a very helpful post by thecubed over here which you can follow and it will work.
The thread is here. Just go through the first post which has a tutorial and steps you need to take:
http://forum.xda-developers.com/lg-...lg-g3-twrp-d852-d852g-f400-t2900614?nocache=1