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.

bootloop, battery low, can't use fastboot or rsdlite

I have a Photon Q with CarbonROM and TeamWin recovery I think. Someone else set things up for me so I don't know precise versions of things. It was working great for several weeks but suddenly seems to be in a boot loop. The device constantly cycles through green led on, boot logo, then black screen maybe and repeat.
I can get into bootloader screen with volup+voldown. None of the options does anything different except fastboot which I can get to also with voldown.
In fastboot I see "Battery Low" which seems to prevent me from doing any flashing either with fastboot or with RSD Lite.
I edited an xml file or use fastboot and can do operations like
"erase cache"
"reboot-bootloader" - but this sends me back into my loop
I feel as if I must charge the battery somehow. I noticed BP Tools in the bootloader options but that just goes back into the boot loop.
I have seen folks charge the battery by directly hooking up a charger to the battery, not quite ready for that.
Any ideas?
Thanks!
What info I have:
- Photon Q w/ cornholio SIM mod.
- CarbonROM
- Fastboot details:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-51ba9a3, 2013-03-22 20:10:25)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code: 3
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Key pressed
usb connected
- Bootloader
Boot Mode Selection Menu (10.9B)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools

You need to charge the device. Plug it into the wall and try to get some juice into it.
You should be able to charge from TWRP if you can make it to recovery.

arrrghhh said:
You need to charge the device. Plug it into the wall and try to get some juice into it.
You should be able to charge from TWRP if you can make it to recovery.
Click to expand...
Click to collapse
Thanks! I have tried that. Left it plugged into the wall for about 24 hours or so. No luck. Still Low Battery and boot loop. Recovery fails in a similar way.
I'll try charging the battery either in another device or by hooking up power directly to the battery for 10-15 minutes.

in the first post you wrote u can boot to recovery.
so put a rom on your sd card and boot into recovery.
while your phone is hanging on the wall charger.
so you can flash the rom via recovery. it worked for me when my battery was low.

huhu1312 said:
in the first post you wrote u can boot to recovery.
so put a rom on your sd card and boot into recovery.
while your phone is hanging on the wall charger.
so you can flash the rom via recovery. it worked for me when my battery was low.
Click to expand...
Click to collapse
Ah, no. I can't get into recovery. It gets there but does a bootloop just like the logo screen does. Never get anywhere that I can do "anything".
I am now charging a battery from a Droid 4 that I think is the same, EB41 minus maybe a heat sensor? Hoping I can swap batteries and get into fastboot.

I have resolved this!
- used the EB41 battery from my Motorola Droid 4
- charged it to 50
- grabbed a stock image from the interwebs (hard to find actually as http://sbf.droid-developers.org/ is gone apparently) asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml
- booted up to fastboot with power+volume down
- says Battery OK
- grabbed the motorola version of fastboot. It has "Multi-Flash" which is required for the system.img.
- used the xml file inside the stock image as a guide on which fastboot commands to run on Linux
- skipped erase "userdata" because I wanted to try and save it
- see my "me-too" comment here about Multi-Flash: http://forum.xda-developers.com/showpost.php?p=63571551&postcount=7
Thanks all.

I had a similar problem. I could not even boot into recovery, only fastboot. I don't remember exactly how I solved it, but I seem to remember that the phone would not charge when off but charged only when left in fastboot. I managed to get enough charge to get into recovery and flash a new image.

Mate 8 bricked. Button combo's do nothing :(

I've foolishly tried coming back down from NXT-L29C636B585 ending up on NXT-L29C636B330 after using the roll back update mid-way. I then tried the roll back update again to then flash to NXT-L29C636B211 and now my phone does nothing but show the boot logo and get hot - which in this weather I could live without!
Power+up does nothing, power+down does nothing, and power+up+down also does nothing. I don't have TWRP on, and adb/fastboot commands do nothing as it can't get to recovery. I can't even turn it off!
Is it now a paperweight? The only way to turn it off is to let the battery run down I think as holding power down just makes it restart.

Confirmed - it only turns off if the battery runs out. On giving it charge it then pops up with the logo screen again, and again none of the buttons combinations do anything other than restart it. I think my only option now is to send it off to Huawei. Does anyone have any ideas other than having to send it off?

Did you connect it to a PC before trying power + volume down? Was the reason it didn't work for me before.

Yeah, hold Power + Volume down after connecting it to your computer via USB and you should see go into fastboot mode.

arvin2212 said:
Yeah, hold Power + Volume down after connecting it to your computer via USB and you should see go into fastboot mode.
Click to expand...
Click to collapse
I'll give it a go when I get home! god I hope this works..

YES! FASTBOOT! Only issue now is i'm FRP unlocked, but PHONE locked.. I can use the tool to unlock the phone as I have my password from Huawei, but what then? use the tool to flash one of the recoveries?
Thanks for the advice so far - I was very nearly physically sick when i realised nothing worked..

Try unlocking the bootloader and flashing twrp

bootloader unlocked and I used the SRK tool to flash stock 4.1 so now getting messages about my phone not being secure. Next step I figure is build enough charge in it to try flashing B330 again assuming power + vol up/down is working

bootloader unlocked. twrp 3.0.3 flashed ok:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (23498 KB)...
OKAY [ 0.500s]
writing 'recovery'...
OKAY [ 0.330s]
finished. total time: 0.834s
However TWRP is nowhere to be found.. I just get the 'Your device has been unlocked' waffle and can't get to recovery still. Left the phone to fully discharge, and on inserting a mains lead to charge it for a while it then auto starts up and goes to the same screen - I try power&up and it just goes to the red charging 'lightning bolt' screen - then back to 'Your device' etc. I have no way of getting into TWRP!
I've been flashing Samsung phones for years and I can't remember ever getting this infuriated on a flash procedure..
I think I may have to do everything through fastboot as that's the only screen I can get to - but the only thing I can alter which seems to make a visible change is locking or unlocking the bootloader.
Should I re-lock with TWRP supposedly on? I have tried, and all I get is the 'not enough charge' screen - regardless of how long it is left untouched on power. It's as if all the charge I am putting in is just going to heating up the back and showing me the flipping message - then it runs low enough on charge to blank the screen, reboot and then end up with the unlock screen.
All I want to do is hold down all the buttons and have it install B211 - B330 - B'anything' from the dload folder on the sdcard I have in there. If anyone could tell me what to do to get to that point i'd be super happy. Failing that is there a way to fastboot flash a rom file?

Make sure to unplug the usb cable in order to get to TWRP.

malekowsky said:
Make sure to unplug the usb cable in order to get to TWRP.
Click to expand...
Click to collapse
At the moment i'm just struggling to get back to stock let alone a custom rom! If I ever get back to working phone in any way i'll be happy..
I've extracted out the boot, recovery and system from B330 and flashed them all through fastboot then re-locked the bootloader. It is still starting up with the Huawei logo as if booting up, and stays at that screen - It eventually then goes blank, pops up with the red circle with red charge pic in it, then after a while the Huawei logo reappears. I am essentially no further forward.
The more I flash things the more it pays no attention to me and sits on my work desk doing nothing.
I'm wondering if - in my epic screw-up - I managed to somehow destroy some part of the OS that governs charging, as it refuses to hold a charge while plugged in to the pc, powerbank or mains lead. At least thats what it is showing me.. It stayed powered long enough for me to fastboot flash the system.img, but that is when on the pc usb connection.
When I lock/unlock the bootloader through the SRK tool it finishes with the 'choose lock or unlock then press power' option which then promises a system reset.. and then it turns off with the red power screen. I can flash TWRP but because it is seeming not to hold a charge, I cannot then get into it without cables attached as it just boots back to the red charge screen.
Is there another file from the update.app I need to flash? should I just flash every single image and hope for the best? I really felt I was getting somewhere this afternoon..

Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529

Don Kronos said:
Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529
Click to expand...
Click to collapse
I plan to in the morning at work!

SOLVED: Phew - problem solved! see https://forum.xda-developers.com/mate-8/general/best-c636-rom-battery-life-t3623313#post72775720

Don Kronos said:
Have you tried what I posted to you on?
https://forum.xda-developers.com/showthread.php?p=72758529#post72758529
Click to expand...
Click to collapse
Hey,
I unbricked my phone using the same method - thanks for mentioning it! But sadly I'm stuck again. Maybe you have a hint for me?

Patneu said:
Hey,
I unbricked my phone using the same method - thanks for mentioning it! But sadly I'm stuck again. Maybe you have a hint for me?
Click to expand...
Click to collapse
Replied on that post! Probly not that useful though..

Pixel bricked qusb_bulk

Hello XDA
After 2 years of usage my pixel died, last time alive it was android 10, turned off in my pocket and never returned, just turned out black screen and connecting as qusb_bulk with PC
Holding power button with/or volume buttons doesn't make any difference, no reaction
Any ideas how to fix this?

It looks like your phone is in some kind of download mode. qusb_bulk, qusb definitely means Qualcomm USB but the bulk thing doesn't mean anything to me. Maybe stuck in fastboot on EDL mode.

Dumbass370 said:
Hello XDA
After 2 years of usage my pixel died, last time alive it was android 10, turned off in my pocket and never returned, just turned out black screen and connecting as qusb_bulk with PC
Holding power button with/or volume buttons doesn't make any difference, no reaction
Any ideas how to fix this?
Click to expand...
Click to collapse
You are probably screwed while the system ran out of battery when auto installing a system update. You are now in edl mode.
You can try disconnect and reconnect battery and see if other state acheived.

You can try to flash the boot, recovery and system.img through adb using EDL like "adb edl flash system C:\path\to\your\system.img" Same for the recovery and boot except replace system in the aforementioned command and put recovery or boot along with the path to them

Also, forgot to mention that after flashing the system, boot and recovery.imgs run "adb edl reboot recovery" If that doesn't get you in recovery try getting in it using key combos. After getting into recovery flash an OTA image from Google and you're good to go.

↑good that is What I want to say

jjgvv said:
disconnect and reconnect battery
Click to expand...
Click to collapse
Tried it, with and without battery plugged in, pc sees phone as qusb_bulk still

muhammad42620 said:
through adb
Click to expand...
Click to collapse
I'd already do it, but adb can't recognize the phone, adb drivers not installing

Dumbass370 said:
I'd already do it, but adb can't recognize the phone, adb drivers not installing
Click to expand...
Click to collapse
Did you find out the reason of the issue ?

Andri_ju said:
Did you find out the reason of the issue ?
Click to expand...
Click to collapse
Nope.

Hello all, my google pixel1 32gb bricked after a SW update and it is going into EDL (emergency download mode) , can someone help me with .mbn file that I can flash with QPST tool? adb or fastboot is not recognizing the device, its always goes to EDL mode.
Thanks

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