Database Info

Wifi Xoom Rooted? RSD mode 3 -- no fastboot, no adb

Hi. I was on #xoom at freenode earlier and I got some help, but unfortunately no solution. (thank you Kas, EbonyGhost, Pyrator and the others)
I flashed the recovery here:
http://forum.xda-developers.com/showthread.php?t=1074979
I flashed... THE ZIP!!
The flash went well, then the device rebooted and showed "Starting RSD mode 3"
I have only 2 screens:
- with VolUp + power = dual core techno + "Starting RSD mode 3"
- with VolUp + power then immediately VolDown = only the dual core tech logo, no text
Either way: no adb, no fastboot. Tried other usb slots. Tried reinstalling moto drivers.
The xoom never gets recognised by windows. I don't have the dongdong sound when I plug it, in either mode.
I already tried this:
http://forum.xda-developers.com/showthread.php?t=973355
but I get < waiting for device > because it's not recognised by windows...
Any other idea?
Thanks
Regards
Note: I might be away for several days. I'll try everything you say, but maybe I won't be able to post my feedback until monday night (around GMT timezone)

I have this exact problem.

So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...

if you hold the volume down button and power on the device and get no fastboot then you may as well just send it to motorola. looks like this is becoming a problem and cannot be fixed.

mbroeders said:
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
Click to expand...
Click to collapse
This. Flashing the wrong partition should *not* mean that you can't get into fastboot any more.

I know that volume down should get me to fastboot but in fact it doesn't. Windows never makes dong dong when i plug the xoom... My drivers are ok because my nexus one gets recognized instantly and adb is working fine on the phone...

Any reason you don't use RSD to flash the wifi xoom sbf file? (I'm pretty sure someone said that was released not too long ago)

I didn't try yet, I can't find the SBF for the wifi xoom.

I tried the 3G SBF file it's not even working. I know it's not the right file for my device but since it's already bricked...
I have RSD Lite 4.9, latest moto drivers, updated using the moto tool.
When I load the sbf file in rsd lite, I can't see the device, and pushing start has no effect.
I did that when the device was showing "Starting RSD mode 3"
How can I get it back?! I tried on my windows laptop and also on a macbook, without any luck.

This is happened to me , and i flipped cuz i rendered my $600 Xoom to a paper weight , i rebooted (Volup+power then voldown) , i tried ADB and it didn't work... then i left my computer to do something, i returned to my PC and i was flipping through DOS command lines (up and down arrows) and click enter in one of the commands by mistake and it worked! the command was "fastboot erase cache"
i then typed the following to return to stock (you need the stock files)
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Thanks, but I don't have fastboot. It's always < waiting for device >

Topper Harley said:
Thanks, but I don't have fastboot. It's always < waiting for device >
Click to expand...
Click to collapse
You mentioned you tried the steps in http://forum.xda-developers.com/showthread.php?t=973355, but how did this section go:
"Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img."
ed. The other suggestion I heard floating around is to flash the CDMA Xoom's SBF -- yes, it won't get you all the way there, but it might restore things up to the point where you can get into fastboot and then flash the stock images.

I did try already to fastboot flash boot boot.img (stock), then reboot pushing vol up, vol down, both, using clicking or holding them... no luck
I also tried to flash the VZW SBF file but RSD Lite doesn't even see the device. I'm trying now to get some linux running and use sbf_flash instead because I was told that it's more efficient than the linux one.
No luck yet on that part either.

I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
enter the commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.

hoopsdavis said:
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
Click to expand...
Click to collapse
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...

Topper Harley said:
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Click to expand...
Click to collapse
I'm in the same situation here... tried basically all the same steps. I'm lost too... can't connect with ADB, Fastboot or RSD... tried all kinds of key combos as well. "Starting RSD Mode 3"... its wearing me down!!

How can i change the topic title? I wanted to say "xoom bricked?" but I typed rooted by mistake

I'm in this exact situation, and I've tried everything suggested here. I spent some time in IRC talking to a few developers, and we tried pretty much everything to get fastboot to work. No luck, so I tried RSD like you said, and that didn't work, either. Eventually we gave up, and I got an RMA from Motorola via their website. I should receive the FedEx box tomorrow so I can return it to them.
If you want, I'll report back here when the whole process is over and tell you if they end up fixing it for free or not. It sounds like it'll probably be at least a week, though.

benso87: yes, tell me. I have time don't worry (away from home until may 28th)
Otherwise, I think mine is definitely a brick. I tried the last thing I didn't: boot linux and test sbf_flash: not working.
I'll try to send it to moto (the device is imported).
I'm kinda sad... not for the money, but for the bad command that completely destroys a device in seconds... and right, for the money aswell...

Small update: I got the box yesterday and sent it back, then got an email this morning saying Motorola received it. Hopefully the whole process will go this fast.
They gave me a tracking number and a site to check to see how things are going, so that's more info than I was expecting. They haven't asked any questions yet, so that's also good.

Super bricked

I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.

Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866

Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?

bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.

tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.

bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?

tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?

bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.

tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.

bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.

tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo

bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one

tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.

bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.

tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .

bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.

Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.

bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!

tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.

bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.

Need help with HTC sensation, i think he's bricked?

K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin

robin-sips said:
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
Click to expand...
Click to collapse
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..

ahsan64 said:
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
Click to expand...
Click to collapse
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S

robin-sips said:
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
Click to expand...
Click to collapse
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)

rzr86 said:
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
Click to expand...
Click to collapse
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?

robin-sips said:
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
Click to expand...
Click to collapse
since you are dealing with a hardware problem then yes
but try this
boot normally(even on safe mode)
connect it to pc and type
adb reboot bootloader
it will take you directly into fastboot mode
then type fastboot reboot
see how it goes and check volume button from there(to confirm the hardware issue)
otherwise repeat the procedure but instead of fastboot reboot run the ruu.exe again

Bootloop Google Logo (Try a lot a solutions)

Hi,
I have a problem with my Nexus 5, it bootloop on the Google Logo
I try to put a little piece of paper behind the power button and also to click on the power button a lot of times during the boot but it still stuck..
What can I do to try fix it ?
Thanks in advance

is this the kind of bootloop where it loops because of a stuck power button or is it a software based bootloop?

matgras said:
is this the kind of bootloop where it loops because of a stuck power button or is it a software based bootloop?
Click to expand...
Click to collapse
Same as this : https://www.youtube.com/watch?v=jzj73qYg5HA
I take the motherboard off, try to connect just the battery and the screen but same problem..

nathan30 said:
Same as this : https://www.youtube.com/watch?v=jzj73qYg5HA
I take the motherboard off, try to connect just the battery and the screen but same problem..
Click to expand...
Click to collapse
that happened to my old ativ s as well, it was due to a broken power button (electrically stuck, not mechanically) the only solution for me was to solder a new power button on it. But I just used it as an excuse to get a new phone.

matgras said:
that happened to my old ativ s as well, it was due to a broken power button (electrically stuck, not mechanically) the only solution for me was to solder a new power button on it. But I just used it as an excuse to get a new phone.
Click to expand...
Click to collapse
Did you try this solution or not ? To know if I can try to do it

nathan30 said:
Did you try this solution or not ? To know if I can try to do it
Click to expand...
Click to collapse
I haven't, it may be very hard depending on the phone model, I just removed it with pliers so I could boot it with a usb cable and I got all the data I needed from my phone.
Can you get your phone into recovery or fastboot mode?

matgras said:
I haven't, it may be very hard depending on the phone model, I just removed it with pliers so I could boot it with a usb cable and I got all the data I needed from my phone.
Can you get your phone into recovery or fastboot mode?
Click to expand...
Click to collapse
So I try to unsolder the power button and now the phone didn't bootloop anymore. Now I'm waiting the new power button I ordered to see.
And to answer your question, I was not able to reach fastboot or the recovery

nathan30 said:
So I try to unsolder the power button and now the phone didn't bootloop anymore. Now I'm waiting the new power button I ordered to see.
And to answer your question, I was not able to reach fastboot or the recovery
Click to expand...
Click to collapse
if you install gravitybox and xposed there should be an option to turn on the screen with the volume buttons (I'm not sure though, it might have been another module) so you could use that as a temporary solution.

matgras said:
if you install gravitybox and xposed there should be an option to turn on the screen with the volume buttons (I'm not sure though, it might have been another module) so you could use that as a temporary solution.
Click to expand...
Click to collapse
I can't have the phone booting, so I have to wait the new button ^^

nathan30 said:
I can't have the phone booting, so I have to wait the new button ^^
Click to expand...
Click to collapse
with phone turned off, (you can remove the battery and re plug it), hold the volume down button and connect it to the wall charger(do not use PC,it will trigger lg download mode), then you will be able to go to fastboot.
Once there you can:
fastboot reboot to boot to normal OS
fastboot boot twrp so you can install a rom or any other mod

opssemnik said:
with phone turned off, (you can remove the battery and re plug it), hold the volume down button and connect it to the wall charger(do not use PC,it will trigger lg download mode), then you will be able to go to fastboot.
Once there you can:
fastboot reboot to boot to normal OS
fastboot boot twrp so you can install a rom or any other mod
Click to expand...
Click to collapse
Oh I didn't know this tips. Thanks a lot I will try asap. But the lg download mode can't be a good solution to reinstall a rom with the computer?

nathan30 said:
Oh I didn't know this tips. Thanks a lot I will try asap. But the lg download mode can't be a good solution to reinstall a rom with the computer?
Click to expand...
Click to collapse
it locks the bootloader and fully wipes the userdata
here is the thread link
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

opssemnik said:
it locks the bootloader and fully wipes the userdata
here is the thread link
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
So I try to push volume down and connecting the charger. I reach the fastboot menu but I can't select "start" or something else because without power button I can't validate my choice..

nathan30 said:
So I try to push volume down and connecting the charger. I reach the fastboot menu but I can't select "start" or something else because without power button I can't validate my choice..
Click to expand...
Click to collapse
as i said, you need a computer once you reach fastboot mode, to send the commands.
fastboot reboot - to boot into normal OS
fastboot boot twrp - to boot twrp

opssemnik said:
as i said, you need a computer once you reach fastboot mode, to send the commands.
fastboot reboot - to boot into normal OS
fastboot boot twrp - to boot twrp
Click to expand...
Click to collapse
Oh i didn't understand, thanks a lot it's working
Now I'm just waiting my new power button

i had this **** sorry for swearing i thought its something with my ROM CM13 Nightly I tried the repair service they said that they changed the power button no data was deleted so its probably the button but some one had a guide how to get the phone out that **** using your PC and manual ADB commands ( No program command line only )

I need help with this issue

when this problem reached me it was a meter of replacing the power button itself (it's like stuck there) by the way my phone was still under warranty so they changed it for me
https://www.ifixit.com/Answers/View/208337/How+do+I+fix+a+Nexus+5+Power+Button+Issue
https://www.aliexpress.com/store/pr...821-NEW-Free-Shipping/629458_32289287372.html
https://www.aliexpress.com/popular/nexus-5-on-off-switch.html
If that helped you dont forget to press the thank you button

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).