Develop Bugs

Stuck in boot screen.

As noted Here, and following on, I managed to get updated through to the OTA ICS, and attempted an upgrade to the 3.1 FlexRom.
After some attempts at fixing things, I'm at the point right now, where the issue seems to be in the boot-up sequence.
I have the following variables in play:
* I have fastboot access, but no ADB.
* The tab is now stuck in a continuous loop of the ANDROID boot loader screen.
(previously, it was the FlexRom bootloader)
* The USB at first was trying to install the A500 drivers, and now fails on "MTP USB Device" installation. It fails, but because it's unlocked, I have the first point available.
* CWM no longer loads, nor can I access any recovery functions.
(When CWM was loading, I used it to flash back to the stock OTA rom, rather than attempt another upgrade)
Attempted:
*using fastboot to update the rom via the update command. FAIL.
*using fastboot to run the OEM unlocker. The computer side says "OKAY" but nothing changed on the screen.
*fastboot WILL reboot the tab if given the command, so I know something is getting through, even with the failure of the USB cord to "work"
Have not attempted:
* Hard reset via the little hole. (I honestly don't think it will work)
* Methods I'm not aware of.
So to sum up, I'm stuck in a boot loop and can't get out.
Ideas?

Did you remove bootloader.blob and the recovery folder,from that stock OTA that you flash trough CWM?
I think you are not.That's why you're in this situation.Your bootloader is locked again, and you have the stock recovery (or may be broken recovery).
Try to do hard reset (the real hard reset) with the lock screen button+volume and power (search this forum or google it).It may help you .
Did you try other fastboot commands like: 'fastboot flash recovery recovey.img' or 'fastboot flash boot boot.img' (boot.img and recovery.img must be in the same folder with fastboot to do it this way) what they return?
If above doesn't help you still has a chance with nvflash but you must read this thread after post #48
Hope this is helpful enough!

sending 'recovery' (6144 KB)... FAILED (remote: (00000002))
(for 'fastboot flash recovery recovery.img')
Now it did reboot, and it seems I may be locked again.
This error popped up:
Fastboot: Not support the command in Lock mode
Failed to process command download: hexidecimal error code
No errors on a proper 'hard' reboot, it erased userdata and cache, and is letting me into the setup, so that's probably a good thing.

and indeed it is. I'm back into the OS, and it booted up normally.
I thought I had tried it before, but apparently, it didn't take.
Thanks!

Please Explain Red Wipe Screen

I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek

drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.

drockmd said:
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.
Click to expand...
Click to collapse
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid

drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
I know you said you aren't on 8.3, but it sounds like the bootloader issue Hash talks about in step 4.5 of his post. You could try flashing the bootloader he posts in that step to see if that fixes your issue. I had the same problem, until I flashed it.
Just an idea, I am in no way an expert just a tinkerer.

lizzord30 said:
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid
Click to expand...
Click to collapse
I too have the red screen, I tried to use the SRtool but was unsuccessful in recovering, can u provide anymore information? i'm really freaking out a little because i'm new to this stuff

I think fattire said Amazon enabled fastboot in this state. On KF2 and KFHD7, this is possible with a factory cable. I guess it's also possible that they have enabled the use of the factory cable for the KFHD8.9, but I'm only speculating.
Before the update, flashing unsigned boot and recovery partitions without the 2nd bootloader properly functioning, the device just wouldn't turn on. Now, not only will the device turn on, but some are even fixable in this state. I'm wondering if Amazon realized that wasn't cost effective to send every broken modified device to a specific secure location to get reflashed.

I don't quite remember what I did, but I was able to fix the "red wipe" screen on my Kindle 8.9.
I think I got this when I first tried installing 8.9StariROM when it was first posted on the forum. I did not know that the red screen could appear if TWRP was not installed already, and I think that's why I got the red screen error.
I didn't really know what it was all about, but somehow I was able to make my kindle go into the fastboot using this command (fastboot -i 0x1949 getvar product) and basically followed the instruction here: http://forum.xda-developers.com/showthread.php?t=2128175
I kept getting device not found error on ADB commands, so I skipped to STEP 4.5 and ran below commands in order: (of course, I downloaded all those files as well)
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
then I think I ran fastboot -i 0x1949 flash system starirom-system.img to load the system image and I was able to have a working kindle 8.9 again.
I hope this helps.

Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) Downloaded the above-mentioned KFHD SRT tool from here: https://docs.google.com/open?id=0B4lZEJI5lYeMR1YteUt2MGxZTGM) and the boot.img and recovery.img from here: https://drive.google.com/folderview?id=0B4lZEJI5lYeMNGdXMHI3T3pKM2c&usp=sharing
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.

Can we get this as a sticky in the Dev Section? it took me 2 weeks to get my system back from a red screen that the below was able to do.
GenghisKhan67 said:
Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) cant post this but look at above post.
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.
Click to expand...
Click to collapse

Need help! Bootloader / fastboot unknown issue!

Hi everyone,
I´ve been trying to install twrp recovery in my Huawei Ascend P6 via fastboot. I followed this "techglen adb and fastboot guide"
I already installed everything needed for adb conection.
So I connect my phone in MTP mode and use "adb devices" and my device appears normally, but the problem happens when I reboot into Bootloader/Fastboot mode and use "Fastboot devices" it appears a device conected but with a bunch of "?????" and a smiley face at the end like this:
C:\Fastboot>adb devices
List of devices attached
123456789 device --------> bunch of numbers appear normally
C:\Fastboot>adb reboot bootloader --------> Phone restarts into bootloader mode (shows huawei ascend logo)
C:\Fastboot>fastboot devices
????????_?_???_?<??????? fastboot ----------> WTF (this is exactly what appears)
I would like to know if there's something wrong with my phone
Should I proceed and flash the custom recovery?
I have stock android 4.4.2 (rooted with kingroot) and stock recovery.
I am a total noob at this so I need your help :crying: I dont want to do anything stupid. (If already did let me know lol)

I have the same issue. Problem is that phone is bricked, so I can only enter in recovery (official, unrooted, unlocked) and fastboot mode.
Have you managed to solve or have some hint?

I have experienced a inconsistency while using minimal adb and fastboot. While device not showing i could send command and the phone would respond. After going into bootloader and while my device wasn't shown in the list i could flash twrp without much trouble, helped me go back from being stuck on bootanimation. used the command fastboot flash recovery xxxx.img (where xxx is the name recovery name). If you can get into boot loader try fastboot reboot bootloader and if the phone responds you might be in the same situation i was.
Always remember: Messing with recoveries bootloaders and boot images might make your phone unusable so do it at your own risk

Have you actually tried to flash twrp? Did you put the img file of twrp to the minimal adb and fastboot folder? If so, try the commands 'fastboot flash recovery recovery_twrp.img(<-- use the name of twrp file here, so not the exact name wrote here) and reboot. My phone is a bunch of question marks as well and it flashed twrp just perfectly (I got it frome here: http://forum.xda-developers.com/showthread.php?t=2632542)

Boot animation only, but can boot to bootloader and TWRP

Hate to start a new thread, but I don't see what I am running into .
My Nexus 5x is unable to boot past the animation (normally it would ask for my pattern, then boot into the system). I can access the bootloader and I can access TWRP.
But when I try adb commands like adb devices I get no response.
I just use this to sideload the new OTA from google which worked just fine so I know the sdk is setup correctly on this computer (rebooted etc).
With access to the bootloader and even TRWP (3.0.2-2) any clue as to where to go from here?
If I try to use adb sideload in advanced in TWRP, I can't talk to the phone (fastboot command fail)...
Phone Bootloader is: BHZ11g
The version of Nexus should be NRD91N 7.0
Seems I have some access on my phone, but cannot send commands to it via computer.
**Update** while at the bootloader (fastboot mode) I can see response when I use
fastboot devices
00b14a7d39589285 fastboot

Okay, I was able to recover from this by sideloading again the new OTA from google. The phone then rebooted but was wiped.
Will work from there

Accessing fastboot on MTCH headunit.

Hi all, I've been following the guide from the Magisk site re: installing it on my currently unrooted headunit. I have confirmed it has a RAMdrive and I have managed to extract and patch boot.img from the payload.img file. I've coped it from my headunit back to my laptop and it's ready to be flashed back across to the boot partition. It also has separate vbmeta and vbmeta_system partitions if that matters.
However the guide (and several others I've since found) says to use the following command once in fastboot mode...
fastboot flash boot /path/to/magisk_patched.img
I've moved my patched image to the root of C: - so I have been using...
fastboot flash boot C:\boot-patched.img
However, upon entering fastboot mode, I don't appear to have ADB connection any more, either thru a regular command window or via WebADB. So when the command is executed it simply says "waiting for any device". I have tried to connect with ADB in the usual manner but get no response.
One thing I've noticed is that when in Fastboot mode, secure boot is enabled, could this possibly be blocking ADB? I'm looking into how to disable this now, unless anyone could let me know please.
Also I'm aware my HU is a MTCH model but I'm not aware of any forum specifically for these yet, apologies if there is and I've managed to miss them.
Many thanks for any assistance.
UPDATE: Sorry forgot to mention that in order to access Developer Options (as the stock ROM has hidden it) I have to enter the code ADBON into the factory settings access menu, then use a 3rd party app to show Dev Options (tapping build number does nothing), from there I have access to the usual items such as USB debugging. However, Dev Options does not seem to persist across reboots so upon reloading if I want ADB connection I have to do all that again. (Hence why I'm trying to get root!)