Database Info

PLEASE HELP! Very concerned have hard bricked phone!

Hi Guys,
So the story is that I was updating my Xperia Z3 (details below) from TWRP 2.8.6 to 'twrp-3.0.2-0-yuga' using the instructions androidnewsbox.com/2016/02/08/how-to-install-and-update-to-twrp-3-0-0 and after flashing the new TWRP the phone can no longer enter recovery mode and I get no other booting/loading screens.
I had 100% battery when I started the process.
It does still do the little vibrate thing when I hold down the power button but nothing happens after that.
When I plug it into the PC the LED flashes red, then green then goes off.
Reading the instructions twrp.me/devices/sonyxperiaz.html I did use the 'install' function not the 'recovery' function. Is that likely to be the mistake I made? If so is there any way to recover?
Any and all help will be greatly appreciated.
Model: D6653
Previous TWRP: 2.8.6
Android version: 5.0.2
Software version: 23.1.A.0.726

Use flashtool to reflash a new system image (ftf). You're using stock so probably your kernel doesn't support FOTA-Kernel partition flashing.

Great to hear back from someone.
Unfortunately I don't think that I can just flash a new ftf using flashtool as I cant get into fastboot mode.
I have been working through the following online tutorial
engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
I have installed the USB drivers on my PC from here
androidmtk.com/download-sony-xperia-usb-driver
And i can get the ftf file from here (mine is 1288-6090)
xpericheck.com/device/D6653
Unfortunately I am unable to put the phone into fastboot mode by holding down the power and down buttons. Nothing happens.
The tutorial above also tells me "If phone not going to Fastboot mode than connect it to PC by USB. Hold Volume Up and Power button until you get company logo or backlight."
This also does nothing and I get no backlight or company logo.
FYI if it helps about a year ago I rooted my phone using a tutorial very similar to this
oneandroid.gs/root-xperia-z3/
I will keep working on the problem and post any updates as they come up.

h3llcat said:
Great to hear back from someone.
Unfortunately I don't think that I can just flash a new ftf using flashtool as I cant get into fastboot mode.
I have been working through the following online tutorial
engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
I have installed the USB drivers on my PC from here
androidmtk.com/download-sony-xperia-usb-driver
And i can get the ftf file from here (mine is 1288-6090)
xpericheck.com/device/D6653
Unfortunately I am unable to put the phone into fastboot mode by holding down the power and down buttons. Nothing happens.
The tutorial above also tells me "If phone not going to Fastboot mode than connect it to PC by USB. Hold Volume Up and Power button until you get company logo or backlight."
This also does nothing and I get no backlight or company logo.
FYI if it helps about a year ago I rooted my phone using a tutorial very similar to this
oneandroid.gs/root-xperia-z3/
I will keep working on the problem and post any updates as they come up.
Click to expand...
Click to collapse
First hard shut down your phone by using combo, after that, download the ftf for your phone (1288-6090 is the customization, what you need is an ftf that its compatible with your phone model, download flash tools, install the drivers that come with it, and using xperifirm (Included in flashtools) you download the firmware) After you have all settled up, proceed to flash your phone, select firmware and then it'll ask you to connect your phone in flash mode not fastboot mode, you can do that by pressing vol up + power (press them and while pressing them connect the usb to the pc). Then the flashing process will start. You can find many tutorials around here in xda. Do not use external tutorials, go find stuff here. It's way more reliable as many are made just for your phone.

Hi and thanks again.
This gives me plenty to learn about and go forward with thanks heaps.
I will give this process a go later today but I have a few questions if you dont mind.
hard shut down your phone by using combo
Click to expand...
Click to collapse
I am not familiar with any combo and without visual ques from the screen or LED I cant tell if it is off. I have a button that says 'off' near the sim card is that sufficient?
connect your phone in flash mode not fastboot mode, you can do that by pressing vol up + power
Click to expand...
Click to collapse
Do I need to continue to hold down the buttons during the flashing process?
You can find many tutorials around here in xda
Click to expand...
Click to collapse
I do feel a little out of my depth here and am a bit confused about what to even search for to find a tutorial on what you are suggesting. If you can point me to an example tutorial that would be fantastic.

h3llcat said:
I am not familiar with any combo and without visual ques from the screen or LED I cant tell if it is off. I have a button that says 'off' near the sim card is that sufficient?
Click to expand...
Click to collapse
Yes that one, If you press it enough (about 5-10 secs) the phone will shutdown and It wont try to restart. This is what you need first.
h3llcat said:
Do I need to continue to hold down the buttons during the flashing process?
Click to expand...
Click to collapse
No, only when connecting the phone to start flashing the system software, you will see a green light in the notification led that will then shut off and flashing process will start.
h3llcat said:
I do feel a little out of my depth here and am a bit confused about what to even search for to find a tutorial on what you are suggesting. If you can point me to an example tutorial that would be fantastic.
Click to expand...
Click to collapse
This is a great almost-up-to-date guide http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
XperiFirm is included in flashtools now so you don't have to download it, but to get your firmware you have to do the same steps but opening xperifirm from inside flashtool.
You can download flashtool here http://www.flashtool.net/downloads.php

Seems to be a success!
Thanks heaps for all your great assistance.

Did you get the Z3 D6653 going again?
Hi H3llcat,
Jumping through some hoops with the D6653 myself... did you get it to boot up? Not sure how far you went with it, if still an issue charge it back up and let's try a couple of things; I realize it'll just be sitting there all dumb and dark like, but do it anyway. So let us know.
h3llcat said:
Hi Guys,
So the story is that I was updating my Xperia Z3 (details below) from TWRP 2.8.6 to 'twrp-3.0.2-0-yuga' using the instructions androidnewsbox.com/2016/02/08/how-to-install-and-update-to-twrp-3-0-0 and after flashing the new TWRP the phone can no longer enter recovery mode and I get no other booting/loading screens.
I had 100% battery when I started the process.
It does still do the little vibrate thing when I hold down the power button but nothing happens after that.
When I plug it into the PC the LED flashes red, then green then goes off.
Reading the instructions twrp.me/devices/sonyxperiaz.html I did use the 'install' function not the 'recovery' function. Is that likely to be the mistake I made? If so is there any way to recover?
Any and all help will be greatly appreciated.
Model: D6653
Previous TWRP: 2.8.6
Android version: 5.0.2
Software version: 23.1.A.0.726
Click to expand...
Click to collapse

Not sure if this is worth mentioning but this thread is 2 years old.
Yes I did get everything working, xkeita was a great help and the guide he sent me was useful.
Have you got issues yourself?

I think I may have just hard-bricked my G3. Is there hope?

I (stupidly) decided to repartition my Moto G3 using this guide. Now, when trying to turn my phone on, the screen stays blank and there's no indication that it's working but it reboots once every two to five seconds or so (telling you how I can tell it's rebooting would be a long story and I'm sure it's irrelevant to the issue).
Am I just hooped or is there hope?

Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)

HelpMeruth said:
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
Click to expand...
Click to collapse
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.

sensi277 said:
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
Click to expand...
Click to collapse
Try to connect it to your pc and see if adb/fastboot sees the device.

michkost858 said:
Try to connect it to your pc and see if adb/fastboot sees the device.
Click to expand...
Click to collapse
adb shell doesn't see anything.

sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...

Jewshua said:
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Click to expand...
Click to collapse
Or, since the battery is not officially removable, wait till the battery dies and then try to boot into bootloader.

Volume down broken
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?

tyty48 said:
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
Click to expand...
Click to collapse
Can you boot the ROM?
If so, you should be able to turn on usb debugging and run 'adb reboot recovery' and reflash from there
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
what about fastboot devices (with admin/root privileges) ?

I broke mit Pixel 3 !?

Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.

FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel

sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.

MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?

sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you

MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.

MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.

sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?

robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)

MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.

sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!

MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.

From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.

Samsung Galaxy Tab S6, cannot boot up after firmware update using Odin

Hi,
Really need your help, after I updated my firmware using Odin, updated BL, AP, CP, CSC, my tab cannot boot up stuck in logo. Doing the Power + volume up leads me to different screen now.
What must I do? Pleasssee help. Added the pic, after doing hard reset (power + vol up)
I cannot connect back to Odin also. Always setup connection failed.
Please help. I really messed up big time :'(
Thank you all in advance.

Well let the battery drain then boot up works or not?

LR7875 said:
Well let the battery drain then boot up works or not?
Click to expand...
Click to collapse
I haven't tried it yet, waiting also for the battery to be drain, it always boot loop but until samsung logo only..

JayR0503 said:
I haven't tried it yet, waiting also for the battery to be drain, it always boot loop but until samsung logo only..
Click to expand...
Click to collapse
Hi, can this be repaired by service center?

If warranty still here, they should repair for you, although most likely they will go ahead and replace the motherboard.

LR7875 said:
If warranty still here, they should repair for you, although most likely they will go ahead and replace the motherboard.
Click to expand...
Click to collapse
Oh my bad.. it is not under warranty anymore, this will cost me a lot right? Is there any chance of connecting back to download mode? I cannot access it anymore, it will show connect to PC only but Odin cannot setup connection though it is added successfully.
Thanks.

have you download the updated odin?

Try with latest Odin, patched Odin, or even running Heimdall(google 'Heimdall samsung') in an Linux virtualbox.

There is a procedure involving complete shut down, then holding certain buttons and somehow (with your fifth hand) connecting cable between device and PC. Probably with Odin already running on PC.
I'm sorry, I don't remember where I saw it described. I think I used it on my SM-T290, so start by checking the T290 and T295 threads.

ykkfive said:
have you download the updated odin?
Click to expand...
Click to collapse
Hi, thanks I haven't downloaded the latest version but I use the 3.14.4.. version. I will try to find the latest one. Thanks.

J.Michael said:
There is a procedure involving complete shut down, then holding certain buttons and somehow (with your fifth hand) connecting cable between device and PC. Probably with Odin already running on PC.
I'm sorry, I don't remember where I saw it described. I think I used it on my SM-T290, so start by checking the T290 and T295 threads.
Click to expand...
Click to collapse
HI, thanks for the reply, actually the tab has been added and recognized in odin, but while Odin will try to setup connection if always fail. and bootloader screen is not showing anymore only this new recovery screen which is totally different from the original and from those I have seen in the forum. attached image is the new recovery screen when I press Power + vol. up button.

JayR0503 said:
HI, thanks for the reply, actually the tab has been added and recognized in odin, but while Odin will try to setup connection if always fail. and bootloader screen is not showing anymore only this new recovery screen which is totally different from the original and from those I have seen in the forum. attached image is the new recovery screen when I press Power + vol. up button.
Click to expand...
Click to collapse
I don't know what the options on your new recovery screen are. (Do you know what "RDX" is?) I can't read the first stack of options.
The tricky procedure I am trying to remember had to do with triggering download mode, and getting Odin to connect. Try to find a more reliable description of the procedure, it will probably include an explanation of what problem it is trying to solve.

JayR0503 said:
HI, thanks for the reply, actually the tab has been added and recognized in odin, but while Odin will try to setup connection if always fail. and bootloader screen is not showing anymore only this new recovery screen which is totally different from the original and from those I have seen in the forum. attached image is the new recovery screen when I press Power + vol. up button.
Click to expand...
Click to collapse
Well not long before I saw someone enter this ss rdx mode. Maybe it is some sort of crashdump mode or something. Let the battery drain down and try to boot up again.

J.Michael said:
I don't know what the options on your new recovery screen are. (Do you know what "RDX" is?) I can't read the first stack of options.
The tricky procedure I am trying to remember had to do with triggering download mode, and getting Odin to connect. Try to find a more reliable description of the procedure, it will probably include an explanation of what problem it is trying to solve.
Click to expand...
Click to collapse
Hi i don't really have idea about RDX sorry but im searching about it also.. there are only 4 options for me to choice from the new menu, To PC connect or US, Connect to SD Card, RDX AGAIN and RDX Exit that's all.

LR7875 said:
Well not long before I saw someone enter this ss rdx mode. Maybe it is some sort of crashdump mode or something. Let the battery drain down and try to boot up again.
Click to expand...
Click to collapse
I'm trying to find some info on RDX also but I did tried to drain the battery but when it bootup same situation exit...

JayR0503 said:
Hi i don't really have idea about RDX sorry but im searching about it also.. there are only 4 options for me to choice from the new menu, To PC connect or US, Connect to SD Card, RDX AGAIN and RDX Exit that's all.
Click to expand...
Click to collapse
Have you tried:
tablet shut down, no cable
run Odin on PC
boot tablet
connect cable between tablet and PC
I'm hoping that option
Code:
[To PC] Connect a USB Cable
means "If you want to connect to a PC, now is the time to connect a USB cable."

Upload Mode means RDX Tool...
Upload Mode
There are several modes that Wave bootloader supports for certain purposes. The normal mode and low power mode just start the Nucleus kernel. I'm also pretty sure everybody knows what a DOWNLOAD MODE is (one with the red letters, but if initiated...
forum.xda-developers.com
Check this Thread...
Best Regards

2017 Fire HD 8 - GIZA -- Boot loop + Has Lineage OS on it.

Hello,
At one point this tablet was working just fine. It sat for a while and now it boot loops. Shows the amazon logo and auto restarts.
I can hold the proper volume up or down key and it says "Recovery Mode" on the bottom left but never enters into it.
Oddly enough I wasn't screwing around trying to do something I shouldn't have, but for the life of me I can't figure out what the deal is. Have anything I can try to possibly recover it? or is it straight to the bin.
Thank you in advance.
Take care,

Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.

Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
Yeah good idea I'll report back .. I mean I can't break it anymore heh. I'm going to blame gamma rays coming down from from space and flipping a single bit in my 6 year old tablet............... causing it to boot loop.

So thinking out
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?

likwidchz said:
So thinking out
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
Click to expand...
Click to collapse
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.

Shiva Kumar A said:
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Click to expand...
Click to collapse
You will have to explain how I would boot it into fastboot mode if
1 The tablet doesn't fully boot up past the amazon logo.
2 I cant even enter TWRP.
What am I missing?
Thank you and cheers!

When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key

Shiva Kumar A said:
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Click to expand...
Click to collapse
Right then what? I'm missing something here.

likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
I can't understand you what you trying to ask?

Shiva Kumar A said:
I can't understand you what you trying to ask?
Click to expand...
Click to collapse
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,

likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.

jonpjingleheimler said:
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
Click to expand...
Click to collapse
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!

likwidchz said:
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
Click to expand...
Click to collapse
From what you have described issuing any command from a computer to the device wouldn't be possible as the device is bootlooping. I could not find any info on button combination to enter fastboot only recovery. from recovery there is a reboot to bootloader or fastboot option. that is your best bet. I have messed with at least a few different kindles in my time but there is always someone out there that has done more and may have another option they can add.

likwidchz said:
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
Click to expand...
Click to collapse
Message me on telegram brother @HeyShiva

Shiva Kumar A said:
Message me on telegram brother @HeyShiva
Click to expand...
Click to collapse
Whats wrong with this forum?

likwidchz said:
Whats wrong with this forum?
Click to expand...
Click to collapse
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.

Shiva Kumar A said:
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Click to expand...
Click to collapse
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.​
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.

Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.​
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Yes I don't know about this tablet, I thought it was just like any other tablets sorry

Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.​
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.

likwidchz said:
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
Click to expand...
Click to collapse
I don't use IRC, but I do have Discord (R0rt1z2#3415).