Related
fastboot on kf2? cwm?
you can get into fastboot with a factory usb cable
Reflexdarky said:
you can get into fastboot with a factory usb cable
Click to expand...
Click to collapse
what about idme bootmode? also is there a recovery?
fmkilo said:
fastboot on kf2? cwm?
Click to expand...
Click to collapse
if you have root access, you can try this code in adb mode
Code:
adb shell
su
reboot bootloader
padest.com said:
if you have root access, you can try this code in adb mode
Code:
adb shell
su
reboot bootloader
Click to expand...
Click to collapse
yes, I know how to use adb and reboot. Typing that does not work. It just reboots normally. Some people have reported the ability to type reboot recovery and get to fastboot. But the recovery on this device is the screen that says that your kindle cannot boot.
I recommend investing in a factory/fastboot cable if you are planning to do any type of modifcations to your device.
They only cost like 6 dollars and mine has saved my ass way more than I'd like to admit.
reverendkjr said:
I recommend investing in a factory/fastboot cable if you are planning to do any type of modifcations to your device.
They only cost like 6 dollars and mine has saved my ass way more than I'd like to admit.
Click to expand...
Click to collapse
I have been thinking about making one. I have a great cable for it, I just have to sit down and do it.
Is there any way besides the factory cable to get to fastboot on kf2?
Read this before you buy anything
Before you go for the fastboot cable - read this:
http://forum.xda-developers.com/showpost.php?p=33807375&postcount=34
Apperently the size of the restore image is to big for fastboot.
irve said:
Before you go for the fastboot cable - read this:
http://forum.xda-developers.com/showpost.php?p=33807375&postcount=34
Apperently the size of the restore image is to big for fastboot.
Click to expand...
Click to collapse
Sparse image. Strip apps that can be restored.
All I want fastboot for is a bootloader and recovery. Not a restored system image.
I did actually get to fastboot. I modified a samsung micro b cable. I didn't solder anything, and as soon as it showed up as fastboot, I switched the cable to a good cable I knew would work.
apparently, it is the only way to get to fastboot on this device, and I'm glad I know how to recognize it on this device now.
how did you modify it ?
Hondologe said:
how did you modify it ?
Click to expand...
Click to collapse
if you are asking about my fastboot cable, I spliced a wire into the red line in the usb cord then wrapped that tightly around pin 4 and replaced all covers so that it lined up correctly with the pins of the device.
fmkilo said:
fastboot on kf2? cwm?
Click to expand...
Click to collapse
adb shell su -c 'idme bootmode 4'
fmkilo said:
adb shell su -c 'idme bootmode 4'
Click to expand...
Click to collapse
I personally just used
Adb shell
Su
Reboot boot loader
Then verified with fastboot -i 0x1949 devices
Worked great. Fmkilo thanks for convincing Hashcode to work on this, you need any testers or anything pm me
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
avathor said:
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
Click to expand...
Click to collapse
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
avathor said:
I bought a Factory Cable
As soon as I plug in the cable, and my Kindle startint and i see fastboot screen,
My pc find a new Device and cant install driver " Otter2-Prod-04". (Win7 x64)
what do you do then?
How can I get the drivers?
how can I install twrp.
Click to expand...
Click to collapse
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
fmkilo said:
Your main problem is windows. Kfu has the drivers, but if you already rooted of, you can try to use the method here you do not need a factory cable.
Click to expand...
Click to collapse
There is a special version of KFU for Kindle Fire 2 ?
I know the other method where I do not need Factory cable.
What if it goes wrong?
what do I do?
My other PC find also not a driver for it.
avathor said:
There is a special version of KFU for Kindle Fire 2 ?
I know the other method where I do not need Factory cable.
What if it goes wrong?
what do I do?
My other PC find also not a driver for it.
Click to expand...
Click to collapse
No, there is not. Get the KFU for the original Fire and that will get you the drivers. That's all you're getting from it. Don't bother with anything else in the tool.
If it goes wrong, you're screwed most likely.
You get a fastboot/factory cable.
Skorpn sells some nice ones, you can look him up on XDA.
Odds are things shouldn't go wrong, but IF they do, you will need a fastboot cable to fix things.
It's up to you how you want to go about that.
Does anyone have any idea why the Fasbootdriver does not work with me?
Have just used the normal usb cable, via ADB Shell "reboot recovery"
booted into fastboot,
then used "fasboot devices" and my Tableed was visible.
"fastboot reboot" works too.
But when I bring my tablet with the fastboot cable into recovery mode,
shows me "fasboot devices" nothing.
To root my kindle I have also long search for the right driver, not a driver of all guides worked for me.
Only the Amazon driver from SDK manager works. I have here 3 PC´s and 1 Notebook (alls PC´s Win7 and Notebook Win8)
I tested it on alls PC´s, but it still dnot work.
My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?
Persianity said:
My current situation: Rooted phone with unlocked bootloader and CWM. No rom loaded on the phone. No roms on SD card. Is there anyway to flash a rom on my device in my current predicament?
Click to expand...
Click to collapse
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.
bananagranola said:
I know you can do it from your computer through fastboot. Or you could mount your phone on your computer, move a ROM from the computer to the phone, and flash it from recovery.
Click to expand...
Click to collapse
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?
Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
adb push location_of_downloaded_rom /sdcard/
Click to expand...
Click to collapse
Another alternative is sideloading it if you have TWRP
Persianity said:
I tried connecting it via ADB but since there is no ROM loaded on my phone, USB Debugging is inactive. Is there a way for me to connect it without enabling USB Debugging?
Click to expand...
Click to collapse
ADB debugging option in settings only pertains to a booted Operating System
iLeopard said:
Boot into fastboot. ADB works there. Push your rom to /sdcard and flash it via recovery
Another alternative is sideloading it if you have TWRP
Click to expand...
Click to collapse
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery
Pirateghost said:
ADB debugging option in settings only pertains to a booted Operating System
fastboot and recovery are different things
adb does not work in fastboot
fastboot does not work in recovery
adb push will work in recovery
Click to expand...
Click to collapse
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.
iLeopard said:
Right, once again getting terms confused. I was in the same situation last week and went in circles between fastboot and recovery and you are correct, adb push does work in recovery.
Click to expand...
Click to collapse
Thank you both for your help. I did not want to go through Odin and wipe my SD card. Love!!!!
I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
RedJack117 said:
I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
Click to expand...
Click to collapse
Use ADB while in a custom recovery.
cupfulloflol said:
Use ADB while in a custom recovery.
Click to expand...
Click to collapse
How do I use that?
RedJack117 said:
How do I use that?
Click to expand...
Click to collapse
There are quite a few guides on how to setup and use adb. There is an FAQ stickied on this very subforum that likely has the information you seek. adb push is the command you want to look at.
RedJack117 said:
I completely formatted my phone and now I am stuck because I forgot that I didnt have an sd card to back up the new rom I want to flash to so how can I move it to my phone? I connected it to a pc but it didnt recognize it
Click to expand...
Click to collapse
..or if you want to give a clean you can also use toolkit
hotto. said:
..or if you want to give a clean you can also use toolkit
Click to expand...
Click to collapse
Thing is it won't even recognize my phone at all... I believe drivers are installed or maybe it has to do with the fact that I can't enable us debugging cause my phone doesn't have a rom
Sent from my SGH-T999 using Tapatalk 4 Beta
If the issue is getting the new ROM on the SD card, buy/borrow a small USB adapter so you can access the SD card on the PC without using the phone.
Sent from my Galaxy Nexus using Tapatalk 2
You don't need USB debugging enabled for adb to recognize your device in recovery. USB debugging is needed for adb to work while Android is booted, but not in recovery. The drivers on the other hand, you will need to figure out why those aren't working. Once those work, your custom recovery will allow adb to function. You then can adb push the file(s) to your sdcard.
UncleMike said:
If the issue is getting the new ROM on the SD card, buy/borrow a small USB adapter so you can access the SD card on the PC without using the phone.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What adapter would be helpful in this situation? If you are talking about removing the sdcard, you realize this device doesn't have non-removable memory right?
cupfulloflol said:
You don't need USB debugging enabled for adb to recognize your device in recovery. USB debugging is needed for adb to work while Android is booted, but not in recovery. The drivers on the other hand, you will need to figure out why those aren't working. Once those work, your custom recovery will allow adb to function. You then can adb push the file(s) to your sdcard.
What adapter would be helpful in this situation? If you are talking about removing the sdcard, you realize this device doesn't have non-removable memory right?
Click to expand...
Click to collapse
Yeah im guessing its an issue with my drivers then im not not sure why
RedJack117 said:
I cant enable usb debugging because i dont have a rom to enable it...when i hit adb sideload in recovery it doesnt come up on my computer
Click to expand...
Click to collapse
You don't need USB Debugging to be on to get adb to work in your recovery. As I said previously, USB debugging only matters when you boot into the OS. You don't have an OS to boot into, and even if you did it wouldn't matter in the recovery. I have USB debugging off right now, and use adb in recovery quite often. The state of USB debugging, either on or off, isn't your issue.
ADB doesn't recognize your device because you are having driver issues. Maybe they aren't installed, aren't installed properly, or something else. Figure out what is going on with those, and adb will recognize your device in recovery. You then can use it to push the file(s) you want to flash, or use sideload.
cupfulloflol said:
You don't need USB Debugging to be on to get adb to work in your recovery. As I said previously, USB debugging only matters when you boot into the OS. You don't have an OS to boot into, and even if you did it wouldn't matter in the recovery. I have USB debugging off right now, and use adb in recovery quite often. The state of USB debugging, either on or off, isn't your issue.
ADB doesn't recognize your device because you are having driver issues. Maybe they aren't installed, aren't installed properly, or something else. Figure out what is going on with those, and adb will recognize your device in recovery. You then can use it to push the file(s) you want to flash, or use sideload.
Click to expand...
Click to collapse
Ok I got it to work thank you
RedJack117 said:
Ok I got it to work thank you
Click to expand...
Click to collapse
Why don't you flash Google's stock images ? As you did to update to 4.2.2 .
Sent from my Galaxy Nexus using xda app-developers app
because he doesnt need to.. and he doesn't know how to search... http://forum.xda-developers.com/showthread.php?t=2343269
beekay201 said:
because he doesnt need to.. and he doesn't know how to search... http://forum.xda-developers.com/showthread.php?t=2343269
Click to expand...
Click to collapse
Isn't easiest/fastest way is :-
Code:
fastboot flash system <The system image >.img
????
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Isn't easiest/fastest way is :-
Code:
fastboot flash system <The system image >.img
????
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That would definitely be needed, if he was trying to flash Google factory images. He's trying to push a flashable ROM zip to /sdcard/, and those, as you know, are not packaged for fastboot.
a manta wrote this.
How can I try to use my internal SDCard in CWM, or would I be able to use my laptop to install SuperSU? I am not able to get a new microSD card until christmas and would like to root
TheGamingBarrel said:
How can I try to use my internal SDCard in CWM, or would I be able to use my laptop to install SuperSU? I am not able to get a new microSD card until christmas and would like to root
Click to expand...
Click to collapse
Try adb sideload. It installs packages in cwm via the usb connection so you won't need to put them on the external sd first.
4m8 said:
Try adb sideload. It installs packages in cwm via the usb connection so you won't need to put them on the external sd first.
Click to expand...
Click to collapse
When I am trying to send the file I get this message "* cannot read 'UPDATE-SuperSU-v1.34' *"
EDIT: I am an idiot, I forgot to put .zip but now it says that it cant find the device
TheGamingBarrel said:
When I am trying to send the file I get this message "* cannot read 'UPDATE-SuperSU-v1.34' *"
EDIT: I am an idiot, I forgot to put .zip but now it says that it cant find the device
Click to expand...
Click to collapse
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.
4m8 said:
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.
Click to expand...
Click to collapse
I changed to TWRP and it worked, but thanks for your help!
4m8 said:
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.
Click to expand...
Click to collapse
Ok, I plugged it in, went to sideload in TWRP and windows asked me to format the disk in drive E:/ Could this fix it?
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Phaisto said:
Good day community,
My Stick Gen 2 tried to do an update and somehow got bricked. The stick boots up to "installing new updates" then goes into a bootloop.
I tried the unbrick/root solution but the stick does not boot into fastboot, but instead tries to install updates again.
Is there a way to cancel this update step and just flash a stock rom?
Your help is much appreciated!
Regards
Phaisto
Click to expand...
Click to collapse
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Sus_i said:
If you have done the unlock/root thing, you can boot to twrp recovery with the boot-recovery script... take a look in the unlock thread.
In TWRP you can flash the latest prerooted rom for your 'tank' device (or a stock update.bin renamed to zip, if you have one), wipe cache and dalvic cache.
Before you reboot, you could delete the ota update file, it's on sdcard... you can google the path. Then reboot.
Click to expand...
Click to collapse
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Phaisto said:
Hi, thanks for your quick reply!
Unfortunately the unlock doesn't run through, it does not boot into the fastboot mode, so I can not run fastboot-step, and therefore I do not have twrp...
Is there an other option to send a "kill-order" to stop the installing? Maybe during bootrom step?
Adb is not available....
Click to expand...
Click to collapse
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Sus_i said:
Is the ota really looping?
You see the update screen?
You may test the first script again. Start it, then plug the stick in without any short...
Then report back, please
Click to expand...
Click to collapse
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Phaisto said:
Yes, I see the update screen, the bootrom-step goes through until the script says "reboot to fastboot". When I put sudo bash fastboot- step.sh, it's just waiting for device and the update loops again...
https://photos.app.goo.gl/cnz3JEwhQL1G4Gbp7
https://photos.app.goo.gl/SNK9c7Ly43a3NuVx6
If I plug the stick in without short, the bootrom-step is waiting for device...
Click to expand...
Click to collapse
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Sus_i said:
ok, don't know, maybe @k4y0z can tell you what to do...
Edit: I suppose you have disabled modemmanager and installed the required packages, i.e python3 python3-serial adb-tools-adb adb-tools-fastboot ??
Click to expand...
Click to collapse
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Phaisto said:
Yes, all the packages are installed as in the unlock threat, I copy/pasted the inputs. Modemmanager was removed as well.
Click to expand...
Click to collapse
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
Code:
rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin
or twrp file manager, if you have an otg cable and a mouse.
Sus_i said:
Ok, I've seen that behavior somewhere months ago, but I can't remember what causes that.
Unfortunately you can't delete the update package without adb... and you need twrp to flash a new system.
Your best bet is to do the unlock, flash a prerooted rom, flash magisk.zip, wipe cache and dalvic, and then delete that update package with adb shell:
or twrp file manager, if you have an otg cable and a mouse.
Click to expand...
Click to collapse
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Phaisto said:
That was exactly my plan for unlocking the stick in the hope of deleting that pesky update file. But I can not manage to get the twrp installed. As far I can understand it is installed with the fastboot-step script. But to execute this script I need the stick to enter fastboot, somehow the update is blocking that. Is there a way to modify the bootrom-step script to delete it, or wipe something?
Click to expand...
Click to collapse
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Sus_i said:
No. You can't improve the scripts
Usually that whole unlock thing is done in 5 minutes, including booting linux and disassemble the stick
Something must be wrong on your side.
Click to expand...
Click to collapse
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Phaisto said:
I meant, if there is a possibility to add a function to the script to delete the update.
And yes, I know that the scripts are very good, and I also realize that the issue is with my stick not the script....
Click to expand...
Click to collapse
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Sus_i said:
Why you run the scripts with bash instead of dash?
Have you downloaded and extracted the amonet.zip with windows?
You may test this out...
Plug your stick into a hdmi port. Run the boot-fastboot script with:
sudo ./boot-fastboot.sh
then power the stick with your laptop.
If you see on your TV down in the left corner a hacked fastboot message together with the amz. logo, it worked.
You can then try a fastboot devices...
Click to expand...
Click to collapse
I have downloaded the zip- files with Ubuntu and extracted as well. I used bash, as I saw it in the posts as a possible fix to problems, but my Linux knowledge is limited so I just used it without thinking about it....
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
https://photos.app.goo.gl/BAL9V2sQhjowTq498
https://photos.app.goo.gl/iL5D3meE6LgNjdDW8
Any ideas?
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Phaisto said:
I just tried your suggestions, but no luck. The stick stays on the Amazon logo and doesn't go into the update cycle ( maybe small victory?).
Click to expand...
Click to collapse
probably it goes into fastboot, but maybe not the unlocked hacked one
Phaisto said:
I tried to redo the bootrom step, after it finished, took the USB off, run boot-fastboot followed by fastboot-step, but as you can see, still stuck in waiting for device....
Any ideas?
Click to expand...
Click to collapse
have you tried to run: fastboot devices
behind the boot-fastboot script?
Phaisto said:
Update: the device shows up on adb now, but unfortunately it is unauthorized.... Any chance to fix this?
Click to expand...
Click to collapse
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Sus_i said:
probably it goes into fastboot, but maybe not the unlocked hacked one
have you tried to run: fastboot devices
behind the boot-fastboot script?
With TWRP shell you can authorize ADB access, like you can see in this link.
But without TWRP this won't work.
Click to expand...
Click to collapse
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Phaisto said:
No luck with fastboot devices:
https://photos.app.goo.gl/bd4Qrjr6si9b9gZm9
How come the script doesn't let the stick boot into hacked fastboot mode?
Anyone an idea?
Click to expand...
Click to collapse
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Sus_i said:
I had trouble running the boot-fastboot script with ubuntu, debian worked as expected.
I would try also an other usb port/cable/hub.
Since amz. can't patch the exploit, there isn't a reason why it should not work.
Click to expand...
Click to collapse
Debian did not work either, same result....
Changing cable, same result....
I suspect, the bootrom-step script can't write the hacked fastboot...
Does anyone have an other idea how to fix this stick?
Amazon took the lazy way out and just offered 15% discount.... On a device their update broke....