Related
Hi everyone,
I was hoping someone might have some advise for me to try. I did the following and now I can't seem to boot the ROM I installed and/or load the partitions to wipe them. TWRP is asking for a password (which I just cancel) and then it can't mount the partitions. Here is what I did.
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Any advise would be appreciated. Thank you. The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file. Thanks so much for your time. Someone is helping me on the side via PM, if I get anywhere with that, I'll post the resolution here.
-Tony
qzmicro said:
The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file.
Click to expand...
Click to collapse
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Any suggestions?
manhart said:
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Click to expand...
Click to collapse
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
qzmicro said:
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
Click to expand...
Click to collapse
That is a rom based on CM11 kitkat. Did you read the requirements (which the cmb creators unfortunately just touch upon in their op) before you flashed it?
The CM11 OP states that you have to be on 10.16.1.14.x bootloader and CWM 6.0.4.4 as a recovery.
It also clearly states that TWRP has problems with KitKat. Supposedly the latest TWRP version works, but to my knowledge that is not confirmed. Don't know what TWRP version you initially flashed, but then you flashed one that's totally outdated and possibly not even compatible with your bootloader.....
I hope you still have access to fastboot.... download CWM 6.0.4.4. and flash it. Then try to flash the rom again.
But check your bootloader version first!
Read this: http://forum.xda-developers.com/showthread.php?t=1957660
Now I can't seem to erase certain partitions or write to system...
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
qzmicro said:
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
Click to expand...
Click to collapse
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
It's been a single ? since I started using fastboot.
berndblb said:
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
qzmicro said:
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
Click to expand...
Click to collapse
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Drivers are installed now and stilll ? for fastboot devices.
berndblb said:
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Click to expand...
Click to collapse
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
qzmicro said:
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
Click to expand...
Click to collapse
I have never heard of this issue.....
Please post the fastboot commands you are using.
Liunx Mint 32 bit
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
I will document what I have done so far, step by step.
berndblb said:
I have never heard of this issue.....
Please post the fastboot commands you are using.
Click to expand...
Click to collapse
I'll post shortly what I have done and how it went down. Specifically the commands used in fastboot as that is the ONLY tool I've used so far besides the ASUS Unlock Tool. Standbye...
-Tony
I'll be installing linux mint 32 on a VM....
lj50036 said:
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
Click to expand...
Click to collapse
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
UPDATE: Here is all the commands I've tried on my Tablet...
Originally I did this:
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Since then I've tried this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (blob was in same directory as fastboot and I got it form the latest asus firmware zip file) <-- Failed It sends the data okay but fails to write to the disc. Error on ASUS tablet in red also confirms the command write:system failed and gives a memory address.
fastboot -i 0x0B05 reboot
Please note that some of the erase commands simply hung. I had to restart the tablet to go back into fastboot mode. When I restart it sometimes they erase successfully. Not sure why. I know I couldn't erase userdata at all, and recently tried again and it worked.
I now have a copy of Mint Linux 32-bit ready to go. What should I try?
-Tony
VM Mint
qzmicro said:
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
Click to expand...
Click to collapse
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
lj50036 said:
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
Click to expand...
Click to collapse
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
P.s. I do not believe I have NVFLASH. I had firmware that didn't alow for it, so I just did the Asus Unlock Tool. Please refer to my previous message about anything/everything I've done so far. Cheers.
qzmicro said:
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
Click to expand...
Click to collapse
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
lj50036 said:
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
Click to expand...
Click to collapse
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Great
qzmicro said:
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Click to expand...
Click to collapse
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Linux Mint still shows ?????? as my serial.
lj50036 said:
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Click to expand...
Click to collapse
So, I installed fastboot and ADB and installed all updates on the OS for kicks. Then tried the fastboot devices command and I recieved:
Code:
[email protected] ~ $ fastboot devices
no permissions fastboot
[email protected] ~ $ sudo fastboot devices
[sudo] password for amascolo:
???????????? fastboot
[email protected] ~ $
...? Still no serial number. I've seen this since I took it out of the box. Not sure what that is all about, I have found no one else with this issue. I'm going to try to flsh and I'll let you know what happens.
-Tony
UPDATE: I have tried to re-flash the damn thing and it still fails. Here is what I see...
Code:
[email protected] / $ sudo fastboot -i 0x0B05 flash staging /home/amascolo/Desktop/blob
sending 'staging' (800927 KB)...
OKAY [135.763s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 136.934s
[email protected] / $
Any ideas fellas? Seems I simply am not able to write to the system partition again.
-Tony
* SIGH *
Anyone have any ideas as to why I can't write to my device? Any ideas as to what I may try? Please advise, I'm not looking forward to throwing this thing away. Cheers.
-Tony
Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7". So,I decided to create this tool. May I present to you,
Flasher
By SafinWasi
This is a batch file which can flash the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 7.2.3 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP/CWM Touch/CWM Stock (thanks r3pwn)
Downgrading the Bootloader to 7.2.3
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[01/02/2014]Initial Release
[19/02/2014]Fixed a bug in the backup script
[17/03/2014]Added restore backup option
[24/06/2014]Added support for CWM Touch Advanced Edition and Stock CWM;updated TWRP to 2.7.0.0
Click to expand...
Click to collapse
Download link:
Link 1:flasher-v2-20140624-tate.rar - 31.23 MB
Link 2:flasher-v2-20140624-tate.rar
MD5 Checksum:84313f4b18008f63346853a8666523d5
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 7.4.6. So,using it on any other software might get you into a bootloop,but the recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green,r3pwn and anyone else whose work helped me.
Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
XDA:DevDB Information
Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-06-24
Created 2014-03-18
Last Updated 2014-07-01
Reserved
bump
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
GMattZ said:
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
Click to expand...
Click to collapse
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Anonymous.123 said:
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Click to expand...
Click to collapse
I do have all the Fastboot and ADB drivers installed.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
You might want to use this Bin4ry's Root Toolkit to root your Kindle. I've attached the link for you to download.
Root_with_Restore_by_Bin4ry_v33
As for fastboot, adb reboot-bootloader will not work. You'll need to issue this command:
adb shell
su
reboot bootloader
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
Well,you could use the Root with Restore by Bin4ry to root the device. But since you have OS version 7.4.8,you should keep the ROM and GApps zips on the sdcard since using my tool on any OS other than 7.4.6 might get into a bootloop.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
FillTheVoid said:
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
Click to expand...
Click to collapse
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
FillTheVoid said:
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
Click to expand...
Click to collapse
No problem bro.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Bump
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should because it looks like it flashes the same files you would flash were you to do it manually complete with bootloader downgrade. You still want to rot first. Root Many Android v31 for that http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Most probably it will work,but you can never be too careful. Be sure to make a backup by option 2.
Bump
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My tool will boot you into Fastboot. And the preferred (and probably only) root method for 7.4.8 is the Root with restore by Bin4ry v31. LinearEquation answered this question a while ago.
Ty,sorry guess i didnt read back far enough
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?
lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!
lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?
berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Wow what a difference DATA2SD and ROM2SD make!
lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW
lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?
lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
tom_clegg said:
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
Click to expand...
Click to collapse
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Fstop said:
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Click to expand...
Click to collapse
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
GXGOW said:
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
where do i find the files for mac with fast boot adb etc.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
Hmmm no recovery? When u hold down volume + power ?
Did u find the fastboot & adb tools for Mac?
What happens when u hold volume key up + power button at same time after turning device off?
What happens if u $fastboot devices -
Can u issue cmd "$fastboot oem unlock"
Know its frustrating but have to keep trying till u get in. Just have the rom files unzipped on your Mac ready to flash 1+1 when u get in. Its how I did it. When I wasn't able to but into recovery. Get on fastboot go thru OEM unlock, then flash 1+1. Follow the install script manually. Open script w plain text reader & just issue cmds following script. I don't trust scripts I + automation to get things unstuck.
tom_clegg said:
where do i find the files for mac with fast boot adb etc.
Click to expand...
Click to collapse
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Heisenberg said:
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Click to expand...
Click to collapse
would u be able to do a short one for mac that would help a lot with the commands
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Heisenberg said:
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Click to expand...
Click to collapse
is it just ./ then the command?
can i message you somehow maybe so it is quicker
tom_clegg said:
is it just ./ then the command?
can i message you somehow maybe so it is quicker
Click to expand...
Click to collapse
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Heisenberg said:
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Click to expand...
Click to collapse
fine then
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
tom_clegg said:
fine then
Click to expand...
Click to collapse
Don't get an attitude because I'm trying to help you help yourself.
tom_clegg said:
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
Click to expand...
Click to collapse
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Heisenberg said:
Don't get an attitude because I'm trying to help you help yourself.
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Click to expand...
Click to collapse
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
tom_clegg said:
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
Click to expand...
Click to collapse
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Heisenberg said:
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Click to expand...
Click to collapse
it says device tampered true
unlocked false
charge screen enabled false
tom_clegg said:
it says device tampered true
unlocked false
charge screen enabled false
Click to expand...
Click to collapse
Ok, try the unlock command again. What recovery did you previously have installed?
Heisenberg said:
Ok, try the unlock command again. What recovery did you previously have installed?
Click to expand...
Click to collapse
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
tom_clegg said:
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
Click to expand...
Click to collapse
You definitely can't boot into recovery? Most times not being able to get into recovery it's a case of user error. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Hello,
i did this here
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
(unbrick device, install color os)
the fastboot of my device worked, after it, I did this here because i dont wanted the chinese color os, i wanted stock
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
(this dude tell how to get stock back, this here work only with adb...
...but by 'adb devices' my device dont got listened, so i followed this dude:
https://www.youtube.com/watch?v=kpUiIfAUNVU&feature=youtu.be
(how to install adb drivers)
I cant boot in my phone, i have only fastboot, before this yt video in device manager my phone in fastboot got listened under 'other', 'android', after this yt video my device is listened in device manager under 'android device', 'android adb interface'
why my device dont get listened under adb devices?
please help me guys i dont know anymore what to do...
#edit tested on my linux laptop(kubuntu(kde), 15.10), the self stuff... detected as 'android', dont get listened under adb devices...
#tested on windows 8.1 from my sister, the self...
Try booting into fastboot and flash stock CM again
@dabanhfreak ??? I already use fastboot, but my pc dont list it under adb devices
PlayersHeaders said:
@dabanhfreak ??? I already use fastboot, but my pc dont list it under adb devices
Click to expand...
Click to collapse
the command is
fastboot and not adb
dabanhfreak said:
Try booting into fastboot and flash stock CM again
Click to expand...
Click to collapse
DerRomtester said:
the command is
fastboot and not adb
Click to expand...
Click to collapse
thanks guy!!!
fastboot flash recovery twrp.img
worked!!!
thread can get closed
PlayersHeaders said:
thanks guy!!!
fastboot flash recovery twrp.img
worked!!!
thread can get closed
Click to expand...
Click to collapse
Why don't you just edit your first post and add [solved] or [resolved] to the title.