Related
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
NavyLCDR said:
Hi!
Is it normal to lose the ability to get into fastboot via software commands after installing CM10.1? I've tried SU and reboot bootloader - just reboots and stops at the blue KindleFire logo of TWRP. I've tried the fastboot command with the Kindle Fire turned off and disconnected and then plugging it in, and I think that still hangs at the TWRP logo (if I remember correctly). I've tried setting bootmode to 4009 using IDME, that doesn't seem to do anything.
I won't be back from military deployment for a few days, so I don't have my new factory cable to try yet. Just wondering if this is normal, and if not what can I do to fix it?
Thank you in advance,
John
Click to expand...
Click to collapse
Can it boot into TWRP?
If it can
Code:
adb reboot bootloader
This should get you into fastboot
EDIT:
I so misread the question...so you are stuck at the blue KindFire boot screen and not the TWRP boot screen right?
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
NavyLCDR said:
Thank you for your reply! Now that I have my Kindle in front of me this time:
1st: I have CM 10.2-20131015.UNOFFICIAL-otter2 loaded. Kernel is 3.0.72+. Everything works normal, and I love it, except can't get into fastboot.
Using Terminal Emulator I type in su and get the "[email protected]:/ #" prompt, so I know I have root.
I type reboot bootloader and something appears quickly in response in the terminal window that I can't read because the Kindle reboots immediately. I captured the text to a txt file and what appears is:
Reading idme data ...
Setting bootmode to 7
Writing new vars to temp area
It shows the white and orange KindleFire logo for a brief moment and then black screen. The Kindle appears to turn itself off after the brief appearance of the KindleFire white and orange logo.
The same thing happens if I do reboot bootloader using adb shell.
I can get into TWRP the normal way by pressing the power button at boot time.
I won't have access to my factory cable for a few more days, so so don't know if that works or not.
Click to expand...
Click to collapse
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
LinearEquation said:
Make sure to turn ADB on and enable developer options by tapping "build" six times. Now plug your kF2 into a USB port and open a command prompt and type "adb reboot bootloader" with no quotes. You should enter fastboot mode. You should be able to just open a command prompt and type "fastboot" (no tablet plugged in) and see some lines of data which lets you know the path is set right.
Click to expand...
Click to collapse
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
NavyLCDR said:
adb reboot bootloader and adb reboot recovery both do the same thing - the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns itself off. Press the power button and all is normal. I can get into TWRP by pressing the power key when the blue and white Kindle Fire logo is up.
Click to expand...
Click to collapse
No, they are not the same thing. One reboots into the bootloader and the other reboots into recovery. My comment had nothing to do with testing a reboot and everything to see if you can enter fastboot mode.
Since you have now stated you can enter TWRP, use this tutorial to push a ROM onto TWRP and then just flash it from there. http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation,
I know that adb reboot bootloader and adb reboot recovery are not the same commands and I know that they are not SUPPOSED to do the same thing. HOWEVER, on MY Kindle both commands ARE doing the same thing. And that is why I know something is wrong. Both commands on MY Kindle ARE having the same result: the Kindle reboots, I get the white and orange KindleFire logo for a second and it turns off.
Why would I want to reinstall a ROM from TWRP when I have a ROM installed? Once I press the power button, if I let it go it boots into CM 10.2 just fine or I can boot into TWRP by pressing the power button at the right time. I cannot reboot in TWRP or fastboot using software commands, and I don't even know if it is supposed to be that way, or if it is a problem.
I did not (and still don't) know if it is normal for the only way to get into fastboot is with a cable after CM 10.2 is installed (and I don't know if I can get into fastboot that way for a few more days), or if I need to reflash a bootloader file or which bootloader file I need to reflash.
I hope that clarified what my problem is.
08 Feb 2016
It seems Kingroot (NewKingrootV4.80_C135_B242_office_release_2016_02_ 03_105203.apk)
is working, but you may need to run it a few times before it will root
XDA Thread: KINGROOT: The One-Click Root Tool for Almost All Devices
Direct link: NewKingrootV4.80_C135_B242_office_release_2016_02_03_105203.apk
You may see This Warning
It is not unusual for Anti-malware to give warnings about root programs, because they often use exploits/Trojans in order to gain root access. just click on details, then visit this unsafe site.
Edit: 07 Nov 2015
Looks like the HD 8/10 Does not have a nice Fastboot screen, like the Fire 7 in
Seems it's just a black screen.
There should be a few different ways to get to Fastboot mode
From Power off: Hold Volume Down and power on.
From Power Off: Hold Volume UP and power on, it should boot to Recovery
From Recovery: select Boot Bootloader, bootloader has Fastboot mode enabled
From Rom; Use ADB command
adb reboot-bootloader
or
adb reboot recovery
I don't think the modified boot.img is going to work as it is now
Creating a bootable custom recovery may be the best option for the HD 8/10
like ggow did here http://forum.xda-developers.com/ama...ecovery-cyanogen-recovery-2015-11-04-t3240726
Original Post:
Looking for Testers for a Possible Root method
Using the same method of creating a Boot.img that makes the /system rw for the 2015 7 in Fire.
@csolanol and @diegocr have created a batch file, with a modified boot.img for the HD 8/10.
There is some risk that this method will not work, Amazon may have done something different in the 8 and 10 models.
If the boot.img does not work, the tester may have to re install the firmware via adb sideload, or this could brick the device, although that is unlikely.
just post in this thread, if you are willing to test, the batch file is already uploaded to dropbox.
I want to test it.
xdadev_user11 said:
I want to test it.
Click to expand...
Click to collapse
pm sent
Sent from my KFFOWI using Tapatalk
I'm willing to test.
gt7599a said:
I'm willing to test.
Click to expand...
Click to collapse
pm sent
Sent from my KFFOWI using Tapatalk
I'm having trouble installing. I get this message. What do I do?
xdadev_user11 said:
I'm having trouble installing. I get this message. What do I do?
Click to expand...
Click to collapse
Not sure, could just be a typo in the script.
or the boot.img is not right
maybe @csolanol or @diegocr have some ideas
Did you reboot the device?
script looks good, just a quick glance at it.
you checked device manager, when fire was in fastboot mode?
xdadev_user11 said:
I'm having trouble installing. I get this message. What do I do?
Click to expand...
Click to collapse
With "fastboot boot boot.img" boots ?
If boots can edit .bat file, execute commands and know where gives the error.
gt7599a said:
Tom, thanks for sending this.
Since you're sending this via PM, I'm assuming you'd prefer me to ask questions via PM, rather than the forum. If you'd prefer this on the forum, I'm happy to move the conversation there.
Running Win 10 64bit, New Kindle Fire HD 8" 5th Edition, connected directly via USB (not USB hub).
I'm running into the following.
When it should go into Fastbook mode, the device just shows a black screen even though the Device Manager appears to show the Fire in ABD device mode.
Booting device...
downloading 'boot.img'...
OKAY [ 0.219s]
booting...
FAILED (Status read failed (Too many links))
finished. total time: 0.502s
//It didn't reboot so I manually report it
//lots of errors similar to the following
mkdir failed for /system/app/SuperSU, Read-only file system/app/SuperSUunable to open /system/app/SuperSU: No such file or directory
chcon: could not label / ...
//looks like the files weren't written
//I'm addred drivers and tried to make sure they lined up with what you'd written for both Composite & fastboot mode.
Click to expand...
Click to collapse
Replying back in the thread, just didn't want to make the boot.img available if it causes issues,
but easier for csolanol , diegocr and others to reply in the thread.
The script may not work with the HD 8"
If it tried flashing the boot.img anywhere other than fastboot mode, the rest will also fail.
May need to do the step manually, till we figure out somethings.
From power off, hold volume Up, and power on, does it boot to fastboot mode?
Are you familiar with using adb/fasboot commands?
Here is a video by Tomsgt rooting the Fire (7")
To give you an idea what the process should be like.
https://www.youtube.com/watch?v=ux-2b3X3BlI&feature=youtu.be
Fastboot mode only shows black screen
Environment: Kindle Fire 8 HD (5th Ed), Surface Pro 3, Win 10 Pro 64bit, connected directly (not through USB hub)
When I run the batch file fastboot appears to reboot the Fire into bootloader (I think). At that point the Fire's screen appears black. Nothing on the screen.
Windows Device manager shows a change in the device from "Android Composite ADB interface to (something ABD)
I press a key & get the following Error. Multiple attempts each produce the same error message (only the times vary)
Booting device...
downloading 'boot.img'...
OKAY [ 0.219s]
booting...
FAILED (Status read failed (Too many links))
finished. total time: 0.502s
The bat command doesn't reboot the kindle and I have to do it manually. At the login I press another key and get the following
mkdir failed for /system/app/SuperSU, Read-only file system/app/SuperSU unable to open /system/app/SuperSU: No such file or directory
chcon: could not label / ...
I've managed sporadically (power & volume down ) to get into recovery
wiping cache hung with some error messages
factory reset proceeded but was followed with cache related error messages
Now its not finishing booting.
gt7599a said:
Environment: Kindle Fire 8 HD (5th Ed), Surface Pro 3, Win 10 Pro 64bit, connected directly (not through USB hub)
When I run the batch file fastboot appears to reboot the Fire into bootloader (I think). At that point the Fire's screen appears black. Nothing on the screen.
Windows Device manager shows a change in the device from "Android Composite ADB interface to (something ABD)
I press a key & get the following Error. Multiple attempts each produce the same error message (only the times vary)
Booting device...
downloading 'boot.img'...
OKAY [ 0.219s]
booting...
FAILED (Status read failed (Too many links))
finished. total time: 0.502s
The bat command doesn't reboot the kindle and I have to do it manually. At the login I press another key and get the following
mkdir failed for /system/app/SuperSU, Read-only file system/app/SuperSU unable to open /system/app/SuperSU: No such file or directory
chcon: could not label / ...
I've managed sporadically (power & volume down ) to get into recovery
wiping cache hung with some error messages
factory reset proceeded but was followed with cache related error messages
Now its not finishing booting.
Click to expand...
Click to collapse
From power off, hold volume Up, and power on, does it boot to fastboot mode?
Are you familiar with using adb/fasboot commands?
Based on the video there should be something on the screen when the Fire goes into fastboot and that never happened on my device.
Re: abd commands. I've only used them occasionally.
Ed
---------- Post added at 10:47 AM ---------- Previous post was at 10:29 AM ----------
An no, Vol Up & Power doesn't boot into fastboot.
Currently it shows "fire" with a color swipe and just sits there and doesn't appear to finish booting.
Ed
gt7599a said:
Based on the video there should be something on the screen when the Fire goes into fastboot and that never happened on my device.
Re: abd commands. I've only used them occasionally.
Ed
---------- Post added at 10:47 AM ---------- Previous post was at 10:29 AM ----------
An no, Vol Up & Power doesn't boot into fastboot.
Currently it shows "fire" with a color swipe and just sits there and doesn't appear to finish booting.
Ed
Click to expand...
Click to collapse
it has been like that since running the batch file?
Sent from my KFFOWI using Tapatalk
No, that's more recent.
I ran the batch, got the error message I posted. Rebooted the Fire. Re-ran the batch. Same error message. Rebooted the Fire. ran the batch, same error. Manually make sure the drivers are right. Try continuing and get the write error messages, reboot the Fire. Stumble on Recovery, try to wipe cache. It hung. (I think this is was really messed me up) reboot. And a few more attempts with the batch. Tried wiping the cache again. Rebooted got to recovery, factory reset. Saw error messages related to cache folder.
gt7599a said:
No, that's more recent.
I ran the batch, got the error message I posted. Rebooted the Fire. Re-ran the batch. Same error message. Rebooted the Fire. ran the batch, same error. Manually make sure the drivers are right. Try continuing and get the write error messages, reboot the Fire. Stumble on Recovery, try to wipe cache. It hung. (I think this is was really messed me up) reboot. And a few more attempts with the batch. Tried wiping the cache again. Rebooted got to recovery, factory reset. Saw error messages related to cache folder.
Click to expand...
Click to collapse
error wiping cache is not good,
Do you have adb.exe and fastboot.exe files?
yes
I have the SDK installed but had been using the adb & fastboot you sent
sd_shadow said:
error wiping cache is not good,
Do you have adb.exe and fastboot.exe files?
Click to expand...
Click to collapse
if not download [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
run the adb-setup-1.4.3.exe
follow the on screen prompts. you can allow install drivers, and adb global
it should end by opening a command prompt like
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
connect tablet to pc
type/paste in command prompt window
Code:
fastboot -i 0x1949 getvar product
should get something like this back
Code:
Memphis
Thank you for the detailed help.
adb installed
ran command fastboot -i 0x1949 getvar product
result
< waiting for device >
Kindle still stuck trying to boot but the device manager switched from showing Fire as under Other Device to Android Composite ADB Interface and its showing up under Portable Devices as Fire but with a yellow ! icon.
Ed
Stock watch, never turned on debugging. Have tried to do the steps in Skin1980 post (return to stock... load boot, recovery and system (got the error on System). Tried the ADB steps (but noob on ADB with no luck). Am I toast? Attached are screen shot showing fastboot recognizes devices. Also here is device screenshot. Any help would be appreciated... Love this watch but for now it's a paperweight.
Also when I try and write .img files (boot, recovery, system) I get the FAILED (remote: device locked).. I am in fast boot screen on watch.
Can u see the device if it is connected n u enter 'adb devices' in the command prompt?
If not then have to confirm does your driver install correctly.
The device must be connected to PC before you can do anything to it. My understanding.
In fastboot screen on your watch doesnt mean it is connected to PC.
You have to unlock bootloader to be able to use fastboot flash.
While in bootloader, use "fastboot oem unlock" command.
Note, that this automatically wipes all user data on the watch.
What is the error you are getting on System?
A lot of people are reporting errors but in reality they are not.
Can you screenshot the error like you did the fastboot command?
Any progress so far???
It has been a while; have you succeeded to recover the Huawei watch pass the Google animation?
I have read no thread who has solved the problem. Any feedback is appriciated.
Update: After so many days I managed to flash... My watch is working again; still no news from Huawei!!!
For newbies like I am, you have to know is you don't need to enable anything before you are stuck to google logos.
I just downloaded "adb-setup-1.4.3" and "Minimal ADB and Fastboot". Whenever the windows didn't recognize the watch I ran adb-setup which at the end asks for installing drivers and when I disconnect and connect the device, it worked.
After getting connected check if the watch is getting fastboot command by c:\fastboot devices. If you can see any letters and fastboot at the right you're ok to go.
You need to c:\Fastboot Oem Unlock which unlocks the watch and you're out of warranty. Just accept it.
Then follow the steps of skin1980 (thanks it was really great)) http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596
If you need "twrp" not written; just "swipe right" and follow the instructions of skin1980.
Boot Stuck Problem is over.
The watch is getting the updates right now but I guess I'll learn more and get to stock by the experts' help...
Thanks to you all...
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
This worked great for me thanks. BUUTTTT, I now have this issue:
error: cannot load 'bootloader-sturgeon-mec23l.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
W/ (58966): Unable to open 'image-sturgeon-mec23l.zip': No such file or directory
error: failed to open zip file 'image-sturgeon-mec23l.zip': I/O Error
STEPHENs-Mac-Pro:~ HomePC$ fastboot devices
FFS7N15B06002296 fastboot
All 3 files are in the PATH sdk/platform-tools folder: bootloader img, flash shell, and image zip.
Can anyone please help me..
I got my Huawei watch today.. And u was doing the flash system and it didn't work so I did a reboot recovery from the watch.. Then it's not working.. After boot loading the Android logo appears for 2 sec then it's blank then the logo.. Etc.
It isn't recognized by my PS so I can't use any command prompt.. What can I do?
Please help
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev
Hello all
My Pixel is stuck at "Pixel is starting..." screen for a while now. I did not install any new apps recently. I did fiddle with System Tuner UI to turn off displaying clock (I think) some time back - but, did not reboot since then. This was the first reboot after that change.
It looks like I have exactly the same turn of events as this post - https://forum.xda-developers.com/t/stuck-at-pixel-is-starting-after-boot.4038847/ - except that, the OP on that post was rooted and I am not. All I am trying to do is recover some data from the phone (pics, chat backups for Signal etc). Once that is done, I can wipe and do a factory reset.
Since I have a security unlock enabled (fingerprint & pattern) - I am guessing it is not letting me in. Any options I can try out and exhaust before assuming the worst (loss of data?)? Thanks.
My device Info :
Code:
Device Name : Taimen
BootLoader Version : TMZ30m
Secure Boot : yes
Device State : locked
I have adb & fastboot set up, the device is recognized once I boot into recovery and get into 'Apply update from ADB'.
Code:
C:\>adb devices
List of devices attached
<alpha-id> sideload
C:\>adb root
adb: unable to connect for root: closed
C:\>adb shell
error: closed
Any other adb commands return errors.
I did try rebooting multiple times including safe mode, hard reset etc, Everything gets stuck at 'Pixel is starting' screen.
I also tried side loading OTA using adb sideload. The side load worked fine - but, same issue. stuck at the same screen. Not able to pull any data from the device yet.
Any help or pointers is much appreciated.