Has anyone been able to change their splash screen on cm6 using the command listed: fastboot flash splash1 <name>.rgb565
If not, how can we swap the splash screen in cm6?
Hi,
I tried to install the original ROM by TWRP but the process stopped and the kindle fire rebooted.
Now it is stucked on orange boot logo.
When I try to invoke ANY command on KFU, on the screen appears the message <waiting for device>
When I try to invoke ANY "fastboot" command manually, on the screen appears the message <waiting for device>
If I delete the windows drivers and plug the device, I can see the memory but I can't read the content and I can't write any file.
If I install the drivers from the KFU folder (install_drivers.bat), the devices is recognized correctly by the system, but I can't see the memory on pc resources(only on system)
Anyone has some ideas or suggestions in order to install TWRP or the original ROM On my kindle?
Could I solve my problem by a factory cable?
Thanks in advance
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
http://forum.xda-developers.com/showthread.php?t=1668159
If by "memory" you mean the storage area in the /sdcard partition and it can be mounted on the desktop, you are not going to be in fastboot mode. If it's trying to boot into the system software but it doesn't quite get there, you need to see if you can use an appropriate "adb shell" command to change the bootmode to fastboot. If you can't do that, your next best option is probably to get a factory cable and see if your bootloader can be put into fastboot mode. If what I just said in this paragraph doesn't make any sense to you, take a good look at the guide mentioned in the beginning of the post above.
Click to expand...
Click to collapse
Thanks a lot for your answer...
The "memory" are the storage area of my Kindle, and it can be mounted on the desktop but is not accessible.
I have tried to boot the system in all fastboot mode (4000, 4002, 5001) but the system shows the <waiting for device> message. I have tried to activate the fastboot also using "adb" command, but I have the same result.
I could reinstall TWRP or the original ROM with the factory cable? When I plug my kindle by the factory cable my pc can communicate with it?
Thanks for your help
kinfauns said:
It's going to be important for you to figure out where your device is in the booting process when it gets stuck...
Click to expand...
Click to collapse
You look like you could use some help figuring this out.
kinfauns said:
Recognizing fastboot mode
The Display - As the bootloader loads up on the device, one of the previously mentioned bootlogos will appear on the display. With fastboot mode enabled, that bootlogo will be persistent and remain bright on the display. If the display blacks out and redisplays the bootlogo with the backlight slightly dimmed, the bootloader has bypassed fastboot mode and moved on in the boot process.
Click to expand...
Click to collapse
Now, are you in fastboot or not?
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
Anyone?
alchemist said:
The orange logo is persistent on the screen, but if i press for 20 sec the power button on reboot the display shows the orange logo, then the display blacks out and redisplays the bootlogo with the backlight slightly dimmed.
I think thant the kindle not is in fasboot mode...is correct?
Click to expand...
Click to collapse
No, it's not in fastboot mode. Use the Fastboot guide I referred to earlier and try to get the system to set the bootmode to fastboot. This is your next best option to getting the device fixed. I'm pretty sure you have an unrooted stock device, so you'll have to use pokey9000's fbmode. If you can't get it to fastboot mode this way, you need a factory cable. If you don't have a factory cable and you can't make or buy one, then the only option you have left is to open up the case and use Firekit. All of this is detailed in the Fastboot guide. I highly recommend you try using the factory cable.
Once you get the device into fastboot mode, you'll need to follow this guide to flash TWRP and FFF again...
http://forum.xda-developers.com/showthread.php?t=1638452
Once you've done that, the same guide contains instructions on how to revert back to the stock software. Follow those instructions carefully and it will walk you through the process.
Kindle fire stuck on boot logo...the device is corrupted? [SOLVED]
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
alchemist said:
Problem solved by factory cable. In fastboot mode I have installed TWRP and I have launched the restore of a old backup (boot and data).
My Kindle is alive!
Thanks a lot for help.
Click to expand...
Click to collapse
I have an other problem. In Kindle Fire Utility the kindle is always offline, and the boot status is unknow (and I can't install FFF and EX Launcher...)
I tried to reboot in normal mode or fastboot mode with KFU and "fastboot" command, but my pc show <waiting device> message.
What kind of command I need to use?
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
soupmagnet said:
The KFU problem is due to driver issues with Windows.
If you are booted normally, you can use the command line or Pokey9000's bootmode binaries from a terminal emulator to change your bootmode.
Click to expand...
Click to collapse
I tried this and it stopped the boot looping but stuck on the Boot Logo. I used the unbrick method and it went back to boot looping. I have restored my KF several times in the past but this one has really stumped me. I have never had this problem. Are there any other solutions out there?
Kindle Fire Stuck at Logo and Screen Flashing
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
truckaveli said:
hi i have a kindle fire that is stuck at the boot logo the screen is flashing every 3 seconds or so and the light is flashing as well it has stock everything but the soupkit is just stuck here at waiting for device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
#31
thanks
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
#31
Click to expand...
Click to collapse
thanks i will try this and see what happens i also have another kindle fire that is operational but the screen flashes randomly and the touch screen in the game sometimes jumps all over the place like i would be touching one area and a selection for another area comes up
Not working
i charged the kindle entire day still no change it wont even read in the system i am in ubuntu 12.04 nothing in soupkit is helping as it is just hanging <waiting for devices>
Did you follow the instructions? What steps did you take to charge it? Is it still on a 3 second bootloop?
Hi
given this is my first thread here, please redirect me, if my search-fu did not lead me to the correct post.
I'm trying to install a custom ROM on my 5T but after successful flashing it is simply displaying the boot animation of Lineage and nothing else happens and no connection with ADB is possible at that time. Steps I did (following this guide):
updated to stock OxygenOS (A5010_43_180223), reboot, ...
enable dev options
enable USB debugging, advanced reboot, OEM unlock
reboot into bootloader
fastboot oem unlock
enable dev options, USB debugging, advanced reboot, OEM unlock again
reboot into bootloader
fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.73-op5_op5t.img (also tried twrp-3.2.1-0-universal-codeworkx-dumpling.img and twrp-3.2.1-2-dumpling.img)
boot into recovery
swipe to allow system changes (no change detected when not doing this)
adb push lineage-15.1-20180402-microG-dumpling.zip /sdcard/ (also tried older images or standard lineage build)
install this via TWRP
when done, wipe cache/dalvik
reboot system
boot animation for a very, very long time (longest waiting time > 45 minutes)
Initially, I had magisk v16 also thrown into the mix, but to reduce complexity I don't at the moment.
Interestingly, once I'm at this stage and the boot fails (also not on second or third try after force-reboot), I cannot get stock (OnePlus5TOxygen_43_OTA_030_all_1802230142_ebdb8bfbc359405a.zip ) to boot anymore, it also is stuck in boot animation. The only way to get back to working stock ROM found so far is flashing original recovery and firmware (sideloading) and locking of boot loader again.
Does this sound familiar to anyone, as I'm running out of ideas what I did wrong and where.
Thanks a lot in advance for any pointers!
I really need some help.
I recently set a PIN number on my phone before clean flashing another rom. I forgot to flash twrp after the room (no big deal).
However, after trying to access the developer options to enable ADB to fastboot TWRP, it asks for a PIN number, and nothing works!
I tried to reboot into recovery mode, but it says "No Command". Basically, I can't get to fastboot.
Weird thing is that it says my screen lock is set to swipe, but it still asks for a pin.
Any ideas?
marbertshere said:
I really need some help.
I recently set a PIN number on my phone before clean flashing another rom. I forgot to flash twrp after the room (no big deal).
However, after trying to access the developer options to enable ADB to fastboot TWRP, it asks for a PIN number, and nothing works!
I tried to reboot into recovery mode, but it says "No Command". Basically, I can't get to fastboot.
Weird thing is that it says my screen lock is set to swipe, but it still asks for a pin.
Any ideas?
Click to expand...
Click to collapse
You need to set a pattern and a fingerprint and then it'll properly decrypt. If you can boot back into system do that. If you can't boot back in the system you might Flash the factory image again
Also that no command is the stock recovery press power button and volume up button once it'll give you the options. So you're going to probably have to fastboot TW RP image
mac796 said:
You need to set a pattern and a fingerprint and then it'll properly decrypt. If you can boot back into system do that. If you can't boot back in the system you might Flash the factory image again
Also that no command is the stock recovery press power button and volume up button once it'll give you the options. So you're going to probably have to fastboot TW RP image
Click to expand...
Click to collapse
Well when I try to change the security option it asks for the pin, which doesn't work. I can't get ADB enabled so I can't boot into the bootloader like I normally do.
I'll try that method that you mentioned when I get a chance tomorrow. Thank you for replying
marbertshere said:
Well when I try to change the security option it asks for the pin, which doesn't work. I can't get ADB enabled so I can't boot into the bootloader like I normally do.
I'll try that method that you mentioned when I get a chance tomorrow. Thank you for replying
Click to expand...
Click to collapse
so you're already booted into system and you go to try to change it to developer mode and ask for a pin? Or is this all in fastboot mode?
I figured it would save me some hassle in the long run if I just wiped and went back to stock, so I did. I didn't realize I could still access the bootloader by holding down the buttons on that screen, thanks for that!