Develop Bugs

Stuck on KindleFire orange logo.. can go to fastboot mode

Hi, I am reading whole day forum, but cannot find the solution, please help me guys.
My story:
I was made succesfull root, than i putted TWRP recovery, made a backup, and full wipe, than i realize, that i forgot to load CM11 rom... So i restarted device, enter TWRP, and make a restore of backup...
After that, there was no KindleFire blue logo...
After reboot, the device just show static orange kindlefire logo...and that is all.
Only thing I can do - is to enter * using CMD line * to the fastboot mode.
Now i am trying to restore kindle using KFFirstaide - but i get errors because of that there is no files to download from dropbox...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also tried SRT ( I am confused, which is the best/last version of this software ?) , and it looks like it works, something was loaded, but after that, still have static logo, nothing more..
Is there any hope ?
HELP

ok, finally
i manage to push system, recovery and reboot via KFHD System.img Recovery Tool
I run the device with 8.4.1, and i manage to check , that device is still rooted ( via rootchecker ).
After that, i try to again push the twrp into the kindle, doing as it was last time, by the fire flash, but after that - i had no TWRP, and again - I stuck on the kindle fire logo...
What is wrong ?

I'm guessing you forgot to check something off in fireflash like apply stack override.
Sent from my Amazon Tate using Tapatalk

id fallen into like this case, and i did restore using KFFA type 1 on my kindle,
but it output like that error,.. and stuck on boot logo,...what can i do?
and i dont have original boot.bin, recovery.img and system.img, where can i get it?
PLEASE HELP ME!

Bricked OP3 - MD5 Checksum System: Failed

Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!

flash stock system.img

I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.

did you find a solution

Try method 2 unbrick tool as per what they said, again. No other choice.

Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.

unable to install or launch TWRP

Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma

Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.

Facing the same issue. Tried everything but no success.

Did I Brick my 2XL?

After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this state:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.

Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.

The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.

Question Rooted Pixel 6 Pro - no longer receiving updates

Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.

Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.

Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?

zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk

So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.

Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!

zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse