Database Info

[Q] easiest way to boot into bootloader/recovery

okay guys looking for the easiest way to boot into recovery / bootloader
would prefer both physical on the phone and adb commands
if you would be so kind

Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader

Pirateghost said:
Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
thanks, i never had to use adb with my captivate or infuse so i figured i would ask .
also for some reason sometimes volume down +power wont work to get me into the bootloader.

I use Quickboot...it has many reboot options, including reboot into Bootloader and Reboot into Recovery.

Another simple way is to pick restart from the power menu then just hold volume down as the phone restarts.
Sent from my HTC One X using Tapatalk 2

The_Zodiac said:
thanks, i never had to use adb with my captivate or infuse so i figured i would ask .
also for some reason sometimes volume down +power wont work to get me into the bootloader.
Click to expand...
Click to collapse
You have to hold volume down the entire time until it gets to the bootloader. On the Captivate you could release it as soon as the splash screen came up but on this HOX you have to continue holding.

The_Zodiac said:
also for some reason sometimes volume down +power wont work to get me into the bootloader.
Click to expand...
Click to collapse
If the phone is powered off when you want to go into bootloader, you have to make sure "Fast boot" in Settings>Power is unchecked.
Going into bootloader using power+vol down requries the phone to be fully powered off or a reboot. Fast boot is actually just a deep sleep mode and not a full power down.
---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------
BBock9 said:
Another simple way is to pick restart from the power menu then just hold volume down as the phone restarts.
Click to expand...
Click to collapse
That method never seems to work for me. Holding the vol down immediately after selecting restart, or even holding the vol down while picking restart, it just boots normally.
I have to power down (with fast boot unselected in Settings>Power) then hold vol down while pressing power button, in order to get to bootloader.

Pirateghost said:
Volume down+power = BOOTLOADER
adb commands are the same across nearly every device
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
I am trying to boot my samsung captivate into the boot loader. I've tried the physical key combos mentioned in this thread and there not working.
I tried using ./adb reboot bootloader but the phone does a regular reboot.
I am able to get a splash screen with that says "Download" and has a picture of the Android shoveling, by pressing both volumes and plugin in the power.
But if i do this, the device is not visible when I used ./adb devices
The question is how can i get this to reboot into the bootloader preferably from the terminal so that I can unlock it and install CWM.
Any advice would be much appreciated!

Good job finding the wrong phones forum and digging up an old thread to post on
Sent from my HTC One XL

leptone said:
I am trying to boot my samsung captivate into the boot loader.
Click to expand...
Click to collapse
This forum is specific to the HTC One X/XL. You need to go to the forum specific to the Samsung Captivate. The key sequence is likely different, and getting advice from people with a different device can quite possibly lead get you the incorrect info.
Also, as mentioned above, try not to dig up old threads from 7 months ago.

derp.
wrong thread

Quick question: I'm trying to reboot my android STB in bootloader mode to check its lock/unlock status... Obviously I can't use the Vol Down + Power button in a STB...
So I tried "adb reboot bootloader", which didin't seem to work. I mean, it powered down, then powered up in a screen with the brand's logo, but nothing else happened, and the command "fastboot devices" didn't find any device either (while before that, "adb devices" showed the device normally). Also, I didn't get any unrecognized devices under Device manager which would denote that a new "device" got connected into the system...
I then tried "adb reboot recovery" which works fine...
So what does this situation mean for my STB?

Can't access bootloader menu

Howdy XDA, lurking for a few weeks now, first time posting.
I have a Vodafone Smart 2, which runs pretty much the same hardware as the Alcatel V860. I previously rooted it myself, removed crapware, blah blah. This worked fine until I updated the firmware through the Firmware Upgrade Manager, which restored all the crapware on my phone and somehow removed my root privileges.
Now, when I try to root using the same method I used to root the phone previously, I run into an error. Normally, I would root from a zip file on the SD card through the bootloader/recovery menu. Now, when I try to access this menu, I'm greeted with a message stating: 'All data will be lost, continue?' in various languages.
This obviously doesn't allow me to root my phone through the familiar method, which was, as far as I know, the only method to root this particular type of phone. I have tried using the sdk manager but this came up as a dead end.
I would be extremely grateful if anybody can give me any information or ideas as to how to root this phone again?
Cheers.

Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.

Scorpius666 said:
Maybe you're pressing the wrong buttons? I remember that if I pressed volume down + power button instead of volume up a different thing happened.
Click to expand...
Click to collapse
Hi there, thanks for replying.
Normally I would hold the power & the volume + buttons, which would bring me to the bootloader menu. Doing so now just brings up the 'All data will be lost, continue?' message.
Interestingly enough, holding the power & the volume - buttons causes the phone to freeze on the android startup logo, which leaves me with no other option than the pull the battery and try again.

Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10

MemoryController said:
Can't you use adb reboot recovery or sth like that?
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.

seanmaxwell99 said:
Hi there, using the command 'adb reboot-recovery' simply refreshes the list that first comes up when you execute adb.exe within Command Prompt.
I am able to reboot using the 'adb reboot' command though, so the drivers must be in working order.
Click to expand...
Click to collapse
Hi there
do what you did using "adb reboot" dos command, but type in " adb reboot recovery " instead while the phone is on, phone goes off and on into boot menu , where you can do your rooting(update.zip) from sdcard.
hope that helps you,

xt1032 BootLoop (Android starting..) can't enter recovery or bootloader.

Hi everyone im stuck on the resurection of my device (moto g 2013 8GB updated to 5.1 with [5.1 GPE 1 click] from This forum.
I've tried everything or almost for now, cant get it out of that loop.
*Battery pulling.
*hard buttons combinations.
*fastboot and ADB. (not in fastboot mode so.. And as i did flash de 1click before the loop USB Dbgn isn't enabled)
*i think i've tried every toolkit on this forum.
*Raped google search for over a week trying every posible method-
*Only thing left is to take it to church for a blessing. but im not a believer D:
ADD: i've rooted with a "boot.img" from this forum i think it was a 2015 file.
before this i had not 1 issue with the phone. just unlockd the bootloader a few days ago and updated to 5.1 from 5.0.2 becouse of a wifi issue (unknow mac adress) i had to reboot it like 10 times until it appeared again (original mac adress from device, still wrote it down i have it somewhere.)
I think this would be my first post on this forum and it took me over a week to do it becouse this (asking you-comunity) is my last resource.
PS: i had it going betwen 5.0.2 and 5.1 like 4 times to try solving the wifi issue.. only thing it got me was the "line" on the screen like if it where a problem with vertical sync. (i think you are all very familiar with that issue after downgrading the kernel i think.)
the phone just turns it self on everytime. (everytime)
i was able to boot into recovery before the last flash touching the place were the hardware volume button goes (with a neddle) untill it didnt workd anymore and i send it to a store to repair the volume rockers. still no recovery or bootloader boot.
my pc (laptop with 7-32bit recognices it as xt1032. and the one with xp as MTP.)
I've installed every posible thing that i found to bring it back to life even the android sdk full every pkg from 5.0.2 to 5.1 and extras, Motorola drivers and ADB. tried online searching automated from windows and listing it from a folder with the google one. tried adding the hardware manualy and have every ADB thing that i found on device mng but everyone is wit a yellow triangle. (No USB Debuging enabled so why bother anymore.)
I think that's about it.

You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img​
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata​
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

i m sorry for my english, isnt my native lang. And for making it over complicated.
i cant enter fastboot mode or give any order to the phone trough fastboot on a console.
I have installed a TWRP touch, just cant acces it. dont know if it is the hardware button (Vol -) or what.
so it dosnt show up on fastboot devices nor adb devices.
am i not understanding something ?
Thanks for replying and taking the time to help!

Enter fastboot mode by turning on phone while holding Volume Down.

lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.

dieguitwow1 said:
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
Click to expand...
Click to collapse
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.

If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
Click to expand...
Click to collapse
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?

dieguitwow1 said:
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
Click to expand...
Click to collapse
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.

lost101 said:
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img​
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata​
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
lost101 said:
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
Click to expand...
Click to collapse
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?

dieguitwow1 said:
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
Click to expand...
Click to collapse
If you power phone off completely, then no commands are remembered. The button is broken.

lost101 said:
If you power phone off completely, then no commands are remembered. The button is broken.
Click to expand...
Click to collapse
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a niddle until it stoped working is there a fix for it? :fingers-crossed:

dieguitwow1 said:
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a needle until it stopped working is there a fix for it? :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I can't help you with that. If you know someone good with a soldering iron, maybe they can fix it - otherwise, try another repair shop.

its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..

dieguitwow1 said:
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
Click to expand...
Click to collapse
adb reboot bootloader​

lost101 said:
adb reboot bootloader​
Click to expand...
Click to collapse
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]

dieguitwow1 said:
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
Click to expand...
Click to collapse
Yes, USB Debugging would need to be enabled.

lost101 said:
Yes, USB Debugging would need to be enabled.
Click to expand...
Click to collapse
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:

dieguitwow1 said:
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
Click to expand...
Click to collapse
I am not aware of any other options.

i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.

dieguitwow1 said:
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
Click to expand...
Click to collapse
What has changed? Did you get the vol button fixed?

Adb/fastboot on ruizu.

Hi, I got stuck on my own lock screen in my riuzo, but wanna knkw how to go to fastboot/recovery mode to remove it.

Removing lockscreen can't be done via Fastboot or Recovery.

xXx yYy said:
Removing lockscreen can't be done via Fastboot or Recovery.
Click to expand...
Click to collapse
So how I'm supposed to fix this?

Recovery and wipe data will certainly fix it, at the cost of losing all your data, apps and settings.

Renate said:
Recovery and wipe data will certainly fix it, at the cost of losing all your data, apps and settings.
Click to expand...
Click to collapse
The problem is how I wipe it. I mean, I I tried all keys but can't go in screen to wipe it.

Doing a long (10+ seconds) press on the power button while holding some combination of volume buttons should get you somewhere.

Renate said:
Doing a long (10+ seconds) press on the power button while holding some combination of volume buttons should get you somewhere.
Click to expand...
Click to collapse
Already tried that.

Is this a Qualcomm, a MediaTek, some kind of processor?
You may need to go to ROM bootloader.

Renate said:
Is this a Qualcomm, a MediaTek, some kind of processor?
You may need to go to ROM bootloader.
Click to expand...
Click to collapse
I really doesn't know but I.g is a mtk.

You're quite sure that when the lock screen is showing that there is no ADB running?
Does the device make any reaction when plugged into a desktop?
A slim chance, but you might try rebooting it and after it starts rebooting, but before it gets to the lock screen, reset it.
If you do this a bunch of times (>8) it might think that it can't boot and will go to recovery.
If nothing works, you're going to have to open it and find test points or disable the flash so that it goes to the ROM bootloader.
Step one, is using lsusb -v or UsbView.exe to know what you've got.

Renate said:
You're quite sure that when the lock screen is showing that there is no ADB running?
Does the device make any reaction when plugged into a desktop?
A slim chance, but you might try rebooting it and after it starts rebooting, but before it gets to the lock screen, reset it.
If you do this a bunch of times (>8) it might think that it can't boot and will go to recovery.
If nothing works, you're going to have to open it and find test points or disable the flash so that it goes to the ROM bootloader.
Step one, is using lsusb -v or UsbView.exe to know what you've got.
Click to expand...
Click to collapse
Yes, no adb running. When connected it only charges. I will test everything you said when I go to pc since I need sleep soon, but I will reply again as soon as I test everything. Thanks for helping me btw.

Assumed ADB is successfully installed on desktop computer there is a chance to enable ADB on mobile device when having booted device in recovery mode.
1. Unplug USB-cable from device
2. Boot device into recovery mode
3. Connect desktop computer and mobile device via USB-cable
4. On desktop computer sequentialy enter the coomands
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=adb,mtp" >>/system/build.prop"
reboot

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