Database Develop

HELP: device in reset loop

Hello,
I was trying to root my device, and I thought it was going well. once I rebooted it, the "Kindle fire system recovery" showed up. with two options. to reboot or to reset to factory defaults. booth options cause the device to reboot ans show the same message again.
I desperately need your help.
Thank you

Thank you for the reply,
I hope I could get it to adb but I can only boot it and when its booting the message shows up. I don't know if it has fastboot or if I could access it.
any other suggestions?

Thanks for the comprehensive response,
I tried what you suggested and the only output I get is ERROR: could not get pipe properties
I guess I need to look into factory cables hopefully it will get me to run fastboot mode.
If you have any other suggestions please share them

If your (stock) device only boots into recovery, you cannot change bootmodes without a factory cable, unless it's rooted. If your device IS rooted, changing bootmodes will be slightly different because you have to do so using the shell.
Code:
adb shell su -c idme bootmode 4000
adb reboot
If changing the bootmode doesn't work to bring your device back, you're probably looking at much bigger problems.

Thank you for the reply
the commands you listed are to be entered using a factory cable? am I correct?
because the device is rooted but I could not connect to it via adb nor fastboot.

samio2 said:
Thank you for the reply
the commands you listed are to be entered using a factory cable? am I correct?
because the device is rooted but I could not connect to it via adb nor fastboot.
Click to expand...
Click to collapse
No. If the device won't connect via adb, it's likely a problem with your computer and/or drivers.
One thing I have to ask is...are you using the Kindle Fire HD or the original Kindle Fire? With the Kindle Fire HD, you should not be trying to use fastboot unless you absolutely know what you're doing. Any alteration to the bootloader or recovery partitions WILL lock your device down, and it's highly unlikely you'll get it running again.

I am using the fire HD 7" ..
and I want to make sure because the only screen I am available to access right now is the "Kindle fire system recovery" menu. and during it being displayed and I'm not sure if the system fully booted to access it with adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and I think my problem is caused by messed up permissions of the /system/app folder

Josepho1997 said:
I'm not sure if fastboot will work. You could try running fastboot in cmd. If its the same as the original kindle fire, you should first completely shut it down. Then, with fastboot type
Code:
fastboot getvar store
Then, turn on your kindle fire. If it says something in cmd, then it worked and your in fastboot. As of right now, fastboot wont help anything. But, when the kf hd gets a custom bootloader and a custom recovery, you could enter something like
Code:
fastboot 0x1949 flash bootloader nameofbootloader.img(or some file extension)
fastboot 0x1949 flash recovery nameofrecovery.img
Again, 0x1949 was for the original kindle fire. I don't know if it will work for the kf hd.
After you would flash the recovery and bootloader, you could flash a ROM or you could get somebody to make a backup of a kindle fire hd that just had a factory reset, and then you could restore it in recovery.
And if you want to get out of fastboot mode, you could
Code:
fastboot 0x1949 bootmode 4000
fastboot 0x1949 reboot
Android>iOS... Android FTW!
Click to expand...
Click to collapse
it's wrong.
KF HD no 4000 bootmode
KF 1 can boot on mode 4000
but KF HD can't
please confirm

bournezhang said:
it's wrong.
KF HD no 4000 bootmode
KF 1 can boot on mode 4000
but KF HD can't
please confirm
Click to expand...
Click to collapse
You're going to have to provide more detail than that. Where are you getting this information?
OP, if the KFHD is anything like the KFOG (I'm betting it is), you should be able to send adb commands while in recovery (stock or otherwise). What errors are you getting, if any, when trying to send adb commands?

At the prompt shown in the screenshot, there is no connectivity between the device and pc. I checked the device manager and also tried it on the mac "adb devices" shows nothing ... that why I thought fastboot is the only way out. if there is anything you want me to try I'll be glad to.

??
Got an answer about the problem now?

No. still waiting for some senior member revelation, or buying the factory cable

I ordered a factory cable ... I will need assistance with flashing the stock ROM back with fastboot

I have same bootloop issue.
I have entered Kindle Fire HD 7" fastboot mode
but it entered shorting some cables, not completed makes factory cable.
my KFHD is fastboot mode but my computer has not detect any devices.
It's normal micro 5pin data cable now.
anyone have idea to convert this to facory cable?
front of cable has REV.3 and RED, BLK words
back of cable has GRN, WHT words
i have no electric tester

you are one step ahead of me .. so I can't help you ... hope a more experienced member could lend a hand with this.

parintan said:
I have same bootloop issue.
I have entered Kindle Fire HD 7" fastboot mode
but it entered shorting some cables, not completed makes factory cable.
my KFHD is fastboot mode but my computer has not detect any devices.
It's normal micro 5pin data cable now.
anyone have idea to convert this to facory cable?
View attachment 1370293
View attachment 1370294
front of cable has REV.3 and RED, BLK words
View attachment 1370295
back of cable has GRN, WHT words
i have no electric tester
Click to expand...
Click to collapse
Did you read this: http://forum.xda-developers.com/showthread.php?t=1392693 ?

Found these instructions on ebay, don't know if they are useful.
Boot up your computer to Windows
Turn off the Kindle Fire
Plug cable into Kindle Fire
Plug into USB Port of the computer
The Kindle Fire unit if not on already will have turned on again.
Press and Hold the Power button for 20 seconds (past the do you want to turn off prompt). The device will go dark.
Press the power button once and let go.
The device will turn on and it will stop at the Kindle Fire Triangle ( This is in the Fastboot Mode)
If you check your devices, it should say under Android Phone
Android ADB Interface

OMG Stop.
Stop, stop, stop ,stop, stop, before you lock your device down for good.
You need to do some research before trying random things, not knowing what they are for.
The factory cable PUTS THE DEVICE IN FASTBOOT. It does not take it out of fastboot. Research fastboot commands to determine the best course of action for you. Just be sure you know what you are doing and the potential consequences of doing so.

@parintan
any luck with your kindle?

Any updates on the KFHD front?

[Q] Nexus 7 Nakasi factory .img wont flash

Hi guys im new to the nexus 7, i have previously owned a samsung galaxy s wifi 4.0(piece of crap), i had unlocked and rooted my nexus using the nexus root toolkit v1.6.3. Then i flashed francos latest release kernel through the francos kernel app, Next i downloaded the beats+xlouder mod, i attempted to flash it through cwm by installing zip, it seemed to work, booted then said, something about configuring apps and it got stuck on that. I tried rebooting many times but it didnt work. So then i tried to flash a nandroid backup i had made through the toolkit, this failed. Now i have been trying to flash the nakasi factory image through the toolkit, here is the message i get;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any ideas as to whats going on? and how i might get the nexus working again?

Don't use toolkits.
Apparently, your bootloader won't flash correctly. What version is your bootloader now? If you want to flash android 4.2.2, then it should be 4.18.
Check your USB-cable. If possible, use the one that came with the nexus 7. Check your bootloader img-file. Is the md5-sum correct? If uncertain, then redownload the firmware here: https://developers.google.com/android/nexus/images#nakasi
Extract the contents of the firmware file in your folder with adb and fastboot.
Put your nexus 7 in fastboot/bootloader mode (you can do this by pushing all three buttons on the sides simultaniously).
Type (this will erase everything from your device):
: fastboot erase boot
: fastboot erase cache
: fastboot erase recovery
: fastboot erase system
: fastboot erase userdata
If you need to update your bootloader, then type:
: fastboot flash bootloader bootloader-grouper-4.18.img
If you get an error like signature failed, then recheck your USB cable. This should work. If not, then download the android 4.1.2 firmware and skip flashing the bootloader. You can do an OTA update later.
: fastboot reboot-bootloader
Then type:
: fastboot -w update image-nakasi-jdq39.zip

I had a few troubles on my first attempts too... My suggestion is to get Nexus7 Toolbox from the Sticky in the Development section and flash the image you have, that always worked without a hitch for me!
Good luck!

Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium

random hero said:
Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium
Click to expand...
Click to collapse
Probably not, but I have seen forum posts where people reported different experience with different cables used to flash firmware. I only experience it when charging. My nexus charges faster with the original cable and charger. Also the original cable's small end is slightly longer than the small end on the cable I got with my samsung smartphone. If it makes any difference when flashing? I am not sure, but to rule out bad USB-cables as a reason for firmware not flashing I always use the original cable.

My bootloader versin is 4.18, how exactly do i check md5 sums,?
i have no experience with fast boot and adb, are they pc programs? If so cqn you give me a link to them?
Sorry im sure you guys get sick of idiots like me asking questions all day but i really appreciate the help

If your bootloader version is 4.18, then there is no need to reflash it and you can skip this step. Don't worry about feeling idiotic for asking questions. Up until I first rooted my nexus, I had no idea how everything worked either. I learned everything by myself, but it's not that easy for everyone.
You can find adb and fastboot in the folder platform tools in the official google android SDK. Instead of downloading the entire SDK, you can also just download the latest platform tools online from many file share websites: https://mega.co.nz/#!1c1XjIIC!dTyG200R4V3BPIfrac4xayEttP02f9tYlPkqAlqvTko .
Extract that folder. Go to that folder. Hold shift and click with your right mouse button and select open terminal prompt.
Now you can use fastboot to flash images, recoveries, bootloaders, erase your devices, restore, etc.....

yeah ok, ill try it and fingers crossed that it works

i tried to flash it but it says
error: failed to load 'image-nakasi-jdq39.zip
the file i have is a .tar, would that be the problem?

Yes! We found the problem.
You need to unzip the tar file as well. 7-zip can do this for example.

thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:

TheFro74 said:
thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:
Click to expand...
Click to collapse
http://www.modaco.com/forum/657-google-asus-nexus-7-nexus7modacocom ... but I would say that wouldn't I, given it's my own ROM of choice.
Leaving aside my own personal preferences, check out these two threads for ideas and recommendations...
http://forum.xda-developers.com/showthread.php?t=2151963
http://forum.xda-developers.com/showthread.php?t=1807811
The question you have to ask yourself is... do you want full-on functionality, with shed-loads of bells and whistles... or a lean, mean, and minimalistic ROM... or, perhaps something inbetween.
The choice, as they say, is yours....
Rgrds,
Ged.

One of the fun things about the nexus 7 is to experience different roms yourself. See what they differ, what they have in common, what you like about them, etc. I liked paranoid android a lot. I found it very creative, but it didn't ran fluent for me. I even tried ubuntu, but that's just not ready for daily use yet. Now I settled for CM 10.1 M3. It's very stable, smooth and provides a better experience than stock, which I was looking for. But it might be too basic for you. Try it out! And make NANDROID BACKUPS before you do!

Thanks guys , my current setup is a cm10.1 snapshot with Franco's kernel.
Sent from my Nexus 7 using xda app-developers app

Provisioning Fail

Hey guys. I successfully rooted and installed twrp last night. This morning, I tried to install a custom rom but after installing and then rebooting I received an error message on the screen stating "Provisioning Fail". I tried a couple of other roms and have even tried the original stock Amazon rom but none of them will work. I followed a thread that I saw here and attempted a system recovery using fastboot and original img files,
This resulted in the loss of twrp on my kindle and now every time I boot, I get the normal kindle fire logo and then straight the the "Provisional Fail" screen. Please help. Cheers.

Any ideas???

tmosxda said:
Any ideas???
Click to expand...
Click to collapse
That usually comes up with a firmware update failure. Even people with stock units got that message before but it's been a while. You need to restore it via system restore tool again and use option 3.
Sent From Kindle Fire HD 7 running CM 11 4.4.2

LinearEquation said:
That usually comes up with a firmware update failure. Even people with stock units got that message before but it's been a while. You need to restore it via system restore tool again and use option 3.
Sent From Kindle Fire HD 7 running CM 11 4.4.2
Click to expand...
Click to collapse
I have tried to restore it with a couple of tools that I found on the forum but I get an error message saying device not found. When I connect the Kindle, it doesn't even show up in the device manager on my laptop.

tmosxda said:
I have tried to restore it with a couple of tools that I found on the forum but I get an error message saying device not found. When I connect the Kindle, it doesn't even show up in the device manager on my laptop.
Click to expand...
Click to collapse
You need a fastboot cable to restore it.

stunts513 said:
You need a fastboot cable to restore it.
Click to expand...
Click to collapse
I was hoping that wouldn't be the case! Is it possible to make a cable myself without needing a soldering iron?

Eh yea but Its not fun and you still will need a cable that has a contact point for the pin that's normally soldered. Not all USB cables have them(and I believe the cable that came with the kindle didn't have the contact point either) You could use a paperclip and try to hold it in place but I don't recommend this, you might accidentally slip the paperclip and short something. The black hat adapters are nice. I recommend them, they go between a normal cable and the kindle.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Eh yea but Its not fun and you still will need a cable that has a contact point for the pin that's normally soldered. Not all USB cables have them(and I believe the cable that came with the kindle didn't have the contact point either) You could use a paperclip and try to hold it in place but I don't recommend this, you might accidentally slip the paperclip and short something. The black hat adapters are nice. I recommend them, they go between a normal cable and the kindle.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I am going to order one of those adapters and hopefully it will do the trick. Thanks for your help.

Simlar situtation
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.

IrishMLK said:
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.
Click to expand...
Click to collapse
Do you have a fastboot cord? Use the most recent SRT and choose option 3. http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
Do you have a fastboot cord? Use the most recent SRT and choose option 3. http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I do have the fastboot adapter and option 3 still brings up the provisioning fail error. I have tried all permutations of the SRT and KFFA. I get nothing but provisioning fail unless I go back to the 2nd bootloader boot/recovery/system files. Then I get the orange kindle fire boot loop.
Thanks, MLK

I had this problem, I had gotten it due to trying to put different kernel on stock system. My way of getting out of this loop was using KFFA and doing the option that installs all partitions off a working kindle. It installs a total of 7 partitions,if I'm correct, and viola your fixed! That was the thing though.....I used another extra kindle I had in hand, I extracted the partition files from it and injected them to faulty kindle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

IrishMLK said:
Were you able to get past this?
I had successfully loaded the 2nd bootloader and put CM 10 on my Kindle. When I tried to go to CM11, something got borked. All I could get was a boot loop with the normal kindle boot screen - I no longer saw the blue graphic.
I get provisioning fail only when I use the recovery tool - any version. Honestly I have tried so many things I don't know how to get back to stock.
Click to expand...
Click to collapse
Sorry for the late reply.
I contacted amazon and they sent me a replacement kindle. I sent them back the broken kindle.

south956 said:
I had this problem, I had gotten it due to trying to put different kernel on stock system. My way of getting out of this loop was using KFFA and doing the option that installs all partitions off a working kindle. It installs a total of 7 partitions,if I'm correct, and viola your fixed! That was the thing though.....I used another extra kindle I had in hand, I extracted the partition files from it and injected them to faulty kindle.
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
Hi! I'm having the same problem with "Provisioning Fail" I bought a fastboot cable and used KFHD System restore tool. My Kindle Fire HD (2012) is unrooted and kept freezing until one day i opened it again and saw the Provisioning Fail on the screen. So chose option 3, going back to stock but when I opened the device, the Kindle Fire logo back but after a few seconds went back to Provisioning fail.
Can you tell me you used the KFFA? And what partitions did you mention about? Sorry I'm a total noob about all these stuff. Hope you can help me.

Device not found....

I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.

nibblemynutz said:
I've already read the forums in search of a solution, I've uninstalled all htc drivers and reinstalling a single htc one driver. adb push wont work cause it can't find the device... What had happen was, I installed viper one "successfully" and it kept rebooting after starting up, so I went into recovery and wiped everything so it kept bringing me back to bootloader, Now i can't install a rom cause of this "device not found" issue. I hate this so much, it happen before and somehow it randomly worked, but this time it seems like luck isn't on my side... halp.
Click to expand...
Click to collapse
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.

nibblemynutz said:
Tried that, that's what i meant when i said i uninstalled the driver. and when I plugged it in without a driver it didn't say "one" anything, just unknown device.
As you can see the device is correctly installed. but still can't be found, and it isn't displaying under my computer.
Click to expand...
Click to collapse
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.

Cancel pc security and firewall...
Sent from my HTC One using xda premium

alray said:
looks like your phone is booted in bootloader, you must be booted in custom recovery to use adb commands. My phone is listed as ''My HTC'' when booted in OS or in bootloader and under ''Android adb interface'' when booted in recovery.
Click to expand...
Click to collapse
Tried it in fastboot/bootloader/ recovery twrp/
device still could not be found.
horst81, I disabled firewall and tried. no good.
Someone should just release an aio for this issue, it seems so easy to solve but then again nothing i've tried seems to be working.

Solved!!! I uninstalled the drivers and rebooted then tried everything again. this time I went into recovery mode and it actually worked.
Thanks alray.

Bricked ME375CL Please Help

I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!

The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127

johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.

If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.

johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.

Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.

I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.