Related
tried to install TWRP using these instrucitons
http://forum.xda-developers.com/showthread.php?t=1399023
tried everything i could find but im stuck in the kindlefire flash screen and cant go back or anything...is there anyway i can force the tablet to reboot into the OS? It doesnt connect to adb or anything
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
smirkis said:
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i tried doing that..i looked for all of the fast boot commands and it always says fastboot not a valid command etc etc....i tried an adb shell but that didnt work either..i even tried doing a restore with a thread thats in the general forums
Have you verified that fastboot is in fact on your machine? It should reside in the same folder as adb. Also, have you you either A) added the adb/fastboot folder in your Path or B) CDed into the folder where adb/fastboot resides to run the commands?
yay i got it to work...all i did was put in this
fastboot -i 0x1949 oem idme bootmode 4000
then this
fastboot -i 0x1949 reboot
which i got from here
http://forum.xda-developers.com/showthread.php?t=1398728&page=3
looks like all i had to do was add fastboot to the directory i was using so thanks =)
now i just have to wait for a full charge and i can try the twrp again
I also try to install CM7, but it's dead in recovery, I can't exit recovery now. For I have changed boot mode to "idme bootmode 0x5001", How can I change to normal mode ? When I reboot now, it goes to recovery mode directly.
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
hillbillyhotrod said:
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
Click to expand...
Click to collapse
Sounds like you're still in Fastboot mode.
Try these ADB commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Thanks
Sorry it took me so long to respond but I had a login problem. From what I have read ADB doest go al that well using ubuntu, that and I'm not really all that good using command line and terminal. Any other ideas?
So my friend tried setting it up remotely last night but it didn't go well, anything I can't do from inside TWRP to make it work?
Sent from my SGH-T959V using XDA App
hey
hey man, in twrp, trying doing mount, then on your computer, put on a stock rom to the drive, then in twrp, run the stock rom
I'm pretty sure that is what I have been doing but I will try again
Ok, tried again and no luck, I have tried cm7 cm9 and a few others with the same result.
semms like the kf is in bootmode 5001 (recovery)
would try to use kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
but use the corrected run.sh from here:
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use option 1 - bootmode normal
an other option is firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
It's alive
Brought it to my friends house yesterday who has windows and that command worked perfectly. Now I have energy ICS installed and cant log in to gapps, lucky me.
Now should I be able to put on a different rom from Ubuntu computer without that happening again?
Sent from my SGH-T959V using XDA
to switch it accidentially to a wrong bootmode can allways happen, but it's no problem:
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Way over my head, plus im not able to do the adb from my computer I have to have my friend do it from his windows machine.
just flashed a gapps for a different rom but still not letting me sign in to google. Driving me nuts.
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
b63 said:
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
Click to expand...
Click to collapse
I will have to check that out
Gapps
Any clue how to get my gapps working?
the energy rom should have it allready built in:
http://forum.xda-developers.com/showpost.php?p=23255224&postcount=75
It does but I couldn't sign it so I tried a different one, still cant get in.
sorry - don't know the energy rom - would try to ask NRGZ28 in his thread
Thanks for the help
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".
I want to install TWRP and new roms on my X829 device. I can access the device through adb , but not fastboot
When i list adb devices the device is detected, but when i list devices in fastboot the device is not detected.
When I press adb boatloader reboot the device reboots.
Anyone experienced anything similar?
travelguy78 said:
I want to install TWRP and new roms on my X829 device. I can access the device through adb , but not fastboot
When i list adb devices the device is detected, but when i list devices in fastboot the device is not detected.
When I press adb boatloader reboot the device reboots.
Anyone experienced anything similar?
Click to expand...
Click to collapse
Its probably a driver problem on you PC install this: https://forum.xda-developers.com/showthread.php?t=2588979
Heyyo, just to double check you are using adb when in the ROM or recovery and fastboot when in bootloader?
So when in the ROM you would use... adb devices
When in bootloader you would use... fastboot devices
Or... fastboot flash recovery TWRP.img
I'd recommend following this guide for doing it all. Works good
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151