Database Info

Pantech Burst Bricked HELP!!!

I recently picked up a Pantech Burst phone from At&t, and upgraded to ICS. I then proceeded to root the phone using the prestoroot.img method and it worked. Everything was running dandy until I got the VM Heap tool app and(stupidly) set the vm heap to 52m and attempted to reboot... It failed and all I got was a loop of boot up animations. I tried several times to reboot, and then tried to boot to recovery mode and factory reset. That worked, but it STILL didnt reboot..! I dont have a backup, and whenever i try to " Install update from external storage", it just fails over and over again. I found thestock firmware and downloaded it to my external sd card and install(still to no success). Im only 13 and cant afford a new phone! PLEASE SOMEONE HEEEELLLLPPPPPP!!!!!!!!!!!!!

Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.

I love you!!!!!!!
dvinelord said:
use p9070_download_tool_v3.3.zip and flash presto_bin_juus09032012_tp20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread pantech burst essentials.
Click to expand...
Click to collapse
it workkeed!!!!!:d

DvineLord said:
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
Click to expand...
Click to collapse
I bricked my phone few days back doing restore from CWM 6 downloeded online from ROM manager,
I wiped cache dalvik etc & rebooted, I could see the Tap the android screen then suddenly blank now it wont start
I get QHSUSB_dload in PC device manager any way out
I tried this method but I dont get the download button to click it remains greyed out.
Is there any driver for QHSUSB_dload?
Or do I have no hope at the moment or in near future?

just don`t use ROM manager for installing recovery . usually the result is bricked phone

Yah, i remember a fastboot brick i got from rom manager (LG Optimud ME)
Sent from a 2.8 inch screen

I also just bricked my Pantech Burst the same way...using ROM Manager. Is there a way to fix this or am I out of luck? I did try the method posted at the top of this thread. It just gets locked in the S/W Upgrading screen. Any help will be greatly appreciated.

I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:

coolamjadkhan said:
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.

Maybe solved!
tajlund said:
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Click to expand...
Click to collapse
Don't know if this is going to help, but I had the problem (as I described) red S/W Upgrading and couldn't do anything. Well, after about two weeks of sitting with the battery out, I decided to redownload and rerun the Pantech update app, and lo and behold, it fixed my phone. It also installed a more up to date version of Android 4.0, I went from 4.01 to 4.04.
This is after running the updater a good 30 or so times the past two weeks hoping for anything to work, now today, bam, it works fine.
I would recommend anyone in this situation give the most recent updater a try, it may solve your problem.

need help with my burst!!!!!
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?

:crying: Bricked my phone total unable start. any hardware diagnostic tool or manual reset button.
please help urgently

needhelppantech said:
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
Click to expand...
Click to collapse
would you like to sell it cheaper rate???

Bricked Pantech Burst Stuck in S/W Downloading Mode and completely wiped ...
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...

UPDATE - progress ???
dsull1981 said:
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
Click to expand...
Click to collapse
--------------------------------------------------------------------------
OK quick update, I found the pantech burst upgrade tool and the burst-hack.cmd script
I managed to successfully find my phone with the upgrade tool and it completely ran its course and I am guessing it installed Ice Cream Sandwich.
My new problem is that the phone goes to the pantech logo boot screen if I plug the phone into usb but that is all it will do. If I unplug the phone and try to get into S/W Upgrade mode again or power it on it will not do anything at all. Basically the display only comes on when plugged in at this point so I am wondering if the battery is even charged or if it will charge. I read somewhere ( in the gizmolord forum ) that a guy had the same issue as me and he ran this tool for his pantech burst and then left the battery out for 2 weeks and tried to power it back on and it worked for him.
Is it possible that I just need to power the device down completely and let it completely discharge before it will reboot or is this thing bricked ?
I am thinking that either the battery needs to charge, or the phone needs to discharge and power down completely, or the phone could be bricked. I have a feeling it is not bricked because the update tool said everything was successful and no errors or anything.
I will try leaving the battery out for awhile and letting the phone discharge on its own and see what kind of results I get. I would think that 16 - 24 hours would be sufficient. Any ideas ?
---------------------------------------------------------------------------------------------------------------------
Ok so I did a bit more digging and research and found out that the culprit is most likely the poorly designed charging circuit in the pantech phones. I found a tech blog called Mikes Techblog where he shows how to solve this on a pantech jest phone with the same issue. The problem is that the battery is 3.7v and is currently reading 2.8v on the volt meter. The phone will not even attempt to charge until 3.7v is available on the battery because of how the charge circuit is designed. I am going to try the usb cable trick and usb adapter and see if I can monitor its progress with the voltmeter and get it back up to 3.7 volts. After this it should allow me to charge it normally and should boot just fine. It is showing the pantech logo which tells me that the firmware is there and isn't buzzing or doing anything else weird so more than likely this is related to the battery and not having enough of a charge when running the official upgrade tool. This problem probably had already existed prior running the update tool and is why the S/W Upgrading screen only would come up AFTER being plugged into a power source and would disappear immediately. If the battery had any charge whatsoever and if the phone could see it then I would see a screen that tells me to plug my phone in and charge it. I am thinking this is solved but will only know after I charge the battery. From what I've been reading in comments from others the battery issue is prevalent on many different pantech phones including the burst model. Other people with the pantech burst have said in comments on Mike's blog that this made their phone boot right up and said that this was EXACTLY the issue. Perhaps the best way to use these pantech phones is to never ever let them fully discharge the battery.

[Q] Big problem: cant mount SD&cant connect to PC

Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!

PC connection
DieterW91 said:
Hello guys,
Long time reader, first time poster over here.
I'm having a serious problem and wouldn't bother you with it, but i've scrolled through hundreds of forumposts, tried serveral things but haven't find the solution yet. (because the problems in those posts are only a part of my problem :s)
So I hope, by posting and explaining it myself, you guys can help me fixing my HTC One S (wouldn't want to lose it this way -.- )
Here it goes: my phone has been rooted for more than a year now, i've used several ROMs, been through some problems but no big deal and was able to solve them myself).
A couple of months ago, I decided to try the newest Cyanogen (11) mod based on Android 4.4, needed a new recovery but got it installed and working fine.
After a while I installed a Nightly update, and after that the trouble started and went from bad to worse to nearly death
first of all the phone kept rebooting at total random moments, enormously frustrating!
so I decided to do another update, after this update, I wasn't able to turn my Wi-Fi on
No big deal i thought, but after a while it began to annoy me, so another Nightly update was incoming
After this update **** really got messy, the message "com.android.systemui has stopped" kept popping up and the only thing I could do was click OK, then it popped back up -> OK -> and so on and so on
so my phone was as good as useless at this point
At this point I've had it with this ROM, so I put another one on my internal SD card (via coupling with my PC): Beanstalk 4.4 STABLE
This new ROM actually was installed as an update of the previous one, so the damned message "com.android.systemui has stopped" was still popping up constantly.
At that point I totally had it with 4.4 and decided to put an older ROM on it with which i've had had a good experience.
And that's where **** got fcked up:
When I go into recovery (CMW 6.0.4.5) and want to access my internal storage, it says "E: can't mount /storage/sdcard0"
So I wanted to connect to my pc to flash a new ROM to my device using Fastboot, but my pc isn't recognizing my phone and neither is Fastboot.
In fastboot, when I try "fastboot device" it keeps searching and doesn't find my device.
My PC however sees my phone, cause I hear the usbconnection sound when they're coupled, but it isn't showing up as a Removable Storage Device.
So to summarize:
once my phone is booted, i can't do anything apart from clicking OK on the "com.android.systemui has stopped" alert
in recovery, i can't mount my internal storage
when 'connected' to the PC, the PC and fastboot can't detect the device.
Other info:
i've tried it on a pc running W7 and W8
phone is HTC One S S4
I hope you guys can help me out here!
Click to expand...
Click to collapse
I've had success getting a connection to Windows just be using a different USB port, the ones at the back are best. Then at least you get fastboot access...But I also still have the problem with the sdcard, still working on that, trying to figure out a way to fix it from fastboot...

any progress yet rosanna? I was also able to make the connection with my pc, by using the usb ports on the back (thanks for that!). But I haven't been able to mount my sd card yet. I tried with another recovery but that didn't do the trick.
I got into the UI of my current ROM, and then my pc said I needed to format the SD before I could use it.
But I wasn't sure this is a good idea to do in windows.
Anyone know if it is save to format your internal sd card when prompted to do so in windows?

Have a look here
Sent from my ElementalXed One S

Try using a Linux live cd (try Ubuntu). You'll need a blank DVD to burn the iso to. Reboot your computer and see if it recognizes your device (no drivers needed). If it does try a more stable build this time.

benJX said:
Have a look here
Sent from my ElementalXed One S
Click to expand...
Click to collapse
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it

DieterW91 said:
I did read through that thread and tried it.
But i'm not quite sure everything went as plannend.
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
So I started searching for one myself (I have an S4 VLE version of the phone) but I haven't downloaded one yet, although I've seen links that bring me to new links and so on and so on, I wasn't quite sure which link to trust.
If you could help me further I would really appreciate it
Click to expand...
Click to collapse
1 minute - downloadlink is on the way
Here you are: http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408
You can flash it with the toolkit selecting "Custom recovery".
When you're Storage is back alive and kickin' you can flash a custom revovery again.
My favourites are
TWRP 2.7.0.0 - http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
and
PhilZ advanced CWM - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville
In my opinion TWRP is easiest to handle and PhilZ has some more features.

DieterW91 said:
I even think it went wrong on the first step, flashing back to the stock recovery. This one isn't included in the all in one toolkit right?
Click to expand...
Click to collapse
Another direct link here, I personally flashed it manually trough fastboot, for me the easiest and fastest way to do it. Then proceed to the clear storage and flash your custom recovery (like @LS.xD I recommend TWRP but this is your choice )

THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:

DieterW91 said:
THX Guys! :victory:
Thanks to your links to the stockrecovery, my phone is back alive and kicking.
I feared for a while for my phone, but on the other hand I knew the xda community would help me fix it!
1000 times thanks :good::laugh:
Click to expand...
Click to collapse
Feel free to hit the "thanks" button

LG Optimus F3 - Hard Bricked?

Hello everyone, I do believe I have officially broken my phone, however, something tells me I shouldn't give up quite yet.
My cool-story lookin ass decided "Gee, I have done a lot with my phone, and I really want to try and use Cyanogen Mod on it because I am cool!"
Well, I am definitely not that cool. It failed, and then after sadly being turned to my stock ROM, I decided to try Clockwork Mod, it seemed that some were doing it quite easily, so I attempted this myself.
Another failed attempt there, so I figured, well, the Clockwork Mod app had some cool stuff to it, maybe I will just satisfy myself by trying to change the bootup animation to Nyan Cat to make myself feel better about it.
The original purpose of me flashing a ROM over was to allow me to install apps to my SD card without having to go though a Myriad of things. Turns out, that was probably the better option.
Allow me to tell you the current symptoms, and let you know what methods I have tried.
Stuck on LG boot screen, does not load OS
Now no longer will power on or even try to without being connected to my PC (not sure how that came about)
Recovery (Power + Vol Down) does not work, freezes when telling me to wait (gave it a good 30 minutes)
Factory Reset does not work (freezes after second confirmation gave it about 30 minutes)
Methods I am trying but have so far had no success with:
LG Support Tool - (Tells me it stopped working at the beginning of the 3rd step in Upgrade Recovery) (I am letting it sit right now and is still there after about 20 minutes or so)
Unsoft Brick (OneClick Unbrick Java tool) - Flat out fails.
The Connect.img for VMWare fails ultimately
KS360 Util ENG (So far no luck. It crashes douring the upgrade.)
LGFlash Tool - I got it to say Ready and then boom, I unplug and replug in (as per instructions) and no dice, I get no "PASS" on it.
What I can do
Get it to the Download Mode screen.
So far I have tried these methods with and without both the SD Card and SIM card.
The phone IS out of service right now and I did soft-root it at one point using Ngyuen Root method King User, so I don't believe I will get any support, even if I do take it into Sprint (Got it through Boost Mobile).
What I am thinking I may be able to do (no research on this yet)
Is be able to run Linux Distro Ubuntu, force wipe it, and then force the stock ROM back into it to make it run again..
But so far, I have mostly broken down far and needed to post a thread about it here.
If any of you have any suggestions as to what I might do in order to get my phone back up and running (loss of data is irrelevant and already happened) again, that would be fantastic.
Much appreciated everyone.
(Thread posted by myself in Android Forums as well so as to prevent any confusion)
[[ SIDE NOTE: I wasn't sure where to post this, so when I searched for a thread regarding this device, it was posted here, and I scrolled and saw other device support threads. I hope this was the way to go! Sorry if I didn't get it right. ]]

Just a quick update on the goings on:
Yesterday I was able to get it to try and boot without it being plugged in but it did only attempt so ONCE. I do know that after all of the tinkering I have been doing the battery should be at least 90% if not 100%.
This was also a great excuse to bump the thread and let you know I am still watching and hopeful

Utterly Stuck, Confused and a bit Desperate ! Trying to rescue Ampe A83 Tablet

hi,
I've been at this for a few hours with no luck and i'm out of ideas.
I've got the Ampe A83 Quad Core 3G 7.85" Android 4.4.2 Tablet PC and I was trying to upgrade the stock android 4.4.2 to something newer. I figured out that the recovery needed to be unlocked before I could properly flash anything so I used the MTK Droid Tool.
Even though the link from DX states that it's an MTK8382 chip, the droid tool identified it as MT6582 and said the MTK8382 was "fake" so I started trying to look for MT6582 Roms.
I used the tool to create and install a custom CWM recovery, which worked and I can access to do the usual data and cache wipes.
I also used the tool to make a backup before i did anything else as well - it contains the various img files - boot.img, recovery img e.t.c... and everything else.
Now i've tried at least a dozen different roms for MTK devices and NOTHING WORKS. I've had a number of errors trying to install cyanogen but i've also had roms that appear to have successfully installed but when I reboot, nothing happens - the device is stuck in a boot loop but, thankfully, i can still get back to the recovery.
That in itself is no longer the issue really, because i'm now at the point where I just want to restore the device to how it was before I started trying to update it but i'm really at a loss as to what to do now.
The part that i'm worried about is that I didn't use the IMEI/NVRAM button which, seemingly, also performs a backup.
If it helps, I did use the tool to "Prepare Backup for Flash Tool", which worked, and I've downloaded the SP Flash Tool but i'm a bit hesitant to do anything at the moment in case I go one step too far and brick the tablet, partly because all of the guides i've read about using SP Flash to restore say that Preloader, and DSP_bl have to be unchecked before you do anything and I don't actually have the DSP_bl field as an option to even uncheck.
Any help would be most welcome, thankyou. Hopefully i've provided enough information.

For whatever reason, It appears I can now no longer get into recovery. I might see if i can charge it up for a couple of hours to see if that makes any difference.
This is going to be a very expensive mistake if I can't get anything back on this tablet as i'm going to have to replace it out of my own money as well considering it isn't actually mine and i was trying to update it for someone else.

Update:
It now appears to be stuck in what I can only describe as a "charging loop". I've plugged it in to mains power and I see the Battery Charging Symbol on the screen in the centre. It stays there for 10-15 seconds and then vanishes. A few seconds later it's back and the cycle repeats - over and over and over again. I can't even work out if it's getting any charge at all.
I've tried holding down the volume minus key and power for varying lengths of time but nothing happens. Same goes with the volume plus key and power and various other combinations.
It all seems to stem from when I had it in recovery earlier today and chose to reboot the system, thinking - stupidly - I could power it off. I assume since there's no active ROM on the tablet, it's basically rebooted in to 'nothing'.

I had the tablet plugged in to the mains for over five hours last night and got up this morning to see the same screen - the battery symbol blinking in and out.
I know the cable works because I used it to charge a mobile phone not 24 hours earlier.

well, thanks for all the responses but i'm going to have to consider this tablet dead now. nothing i do or try does anything now. it won't even give me the battery symbol now and plugging it in to the mains does nothing.
Maybe the battery is just dead and maybe i need a different USB cable but I can't deal in maybes when I have to now find a way of replacing this tablet.
So yeah, thanks for the help.

Lenovo Tab 3 7 essential TB3-710I flashing experience (I bricked my phone)

Hi to anyone that has this device and reads this :highfive: I'm sorry this is not a thread on how you can unbrick your device . this is for those who have started getting issues on their device and are thinking of flashing and wanna have some guidance on what to expect first ill say its not hard and nothing to be afraid of I'm writing this on hindsight so that you can avoid the mistakes I made.(theres a bit of back story but if you don't care just jump to the bricking)
the reason I flashed my device is that about 8 months prior to my bricking I was acting as the caregiver for an elderly relative and by a set of circumstances the phone got peed took it to get cleaned and all everything was fine the back camera was shot the rest of the phone was fine the front camera was still working but was been disabled by the the device so I rooted the device and forced to get the front camera to work since I had done some test and I could get it take pictures all well till this point about 3 moths before the bricking the phone started to have issues with the contact app then a few days latter I would get stuck in a reboot cycle so I went into the developer screen and ran a root diagnose 14 files were corrupted according to the device so i decided to flash it i had already done this on a different phone so I figured nothing to worry there are many INTERNET guides and videos to this process so I won't link or describe much of this part key words are [sp flash tool(to connect your computer to your device and load the new firmware), CDC driver (an uncertificated* driver to actually use sp flashtool), firmware tab 3 7 essential TB3 710I**(to find the ROM for the device be very carefull for there are 2 diferent ROMs for the device the first ending on 0I and the second ending on 0F)].
*this driver has some issues running on windows 8 if you have this one like i do you only need to search how to run uncertificated driver most of the time it will be explained on the same page you download it but in case its not you don't have to worry.
**you can find this out on the box of your device or when you run developer screen (power + plus volume)
moving on the flash was successful and all well and to my surprise the front camera was working fine without me having to do anything then about a month after again I was at family meeting and I wanted to try to take a picture with the front camera of my meal and me as you can guess this was not easy and i already had taken pictures before this way but this time the app crashed then the device started sending messages of other apps and systems crashing and blocking me out so I figured guess its time to re flash again....
the BRICK
I went home and first thing I checked was root integrity now there were 44 files that failed First bad sign so I used the flash tool with the same ROM I was already using (Lenovo_Tab_3_TB3-710I_MT6580_S000032_160921) restarted the phone like usual it was still booting at this point but for some reason it would not load past the lenovo logo (first mistake I was feeling anxious cocky and rushed I should have given it time) I waited few moments and nothing so I figured "its the same ROM of course it will still be crashing" and the basis that the system could not tell the difference that I had just made a fresh install so I emptied the cache and flashed again did not seem to work so i download a new ROM an older version s000029 it still did not work then I tried a newer one s000035 nothing and I noticed on the developer screen the ROM that was supposed to be on my device was still the s000032 I figured something must be happening to the sp tool so I tried using the developer screen tools to upgrade the firmware as a fool I presed the first option on the OTA update option while trying to use the sdcard option it got stuck there a while i was not in a waiting mood so I forced stopped the device (second mistake don't do this ever I figured since nothing was been sent and it had not picked up anything i would just go on as intended) I tried again with the zip file on the sd card now in the right option but it would simply not load it would just insta stop and say installation aborted I new this was BAD I again ran a check on the root again and this was all it would show:
Now check begins, please wait...
Load source zip file fail
System check fail!
after that I knew I had just soft bricked the tablet and that I had just about tried all that I could to fix something like this I spent the next 8 hours reading surfing and trying to come up with a solution to this none worked and then I had a suggestion why didn't I use the lenovo smart assistant it had a rescue feature for bricked phones! (my last and worst mistake) so I downloaded the program strait from the lenovo page for the tab 3 7 essential and it indeed had the rescue feature all it required was me to be sure of the model and the right i/o which i check on the box and on the back plate of the tab and the ROM appear seeing the name it was about the same as the ROMs i had already downloaded about the same size too over 900 Mb so pressed start and it was on after downloading the steps were the same as with the sp tool turn off phone then connect wait then disconnect and done so I did and the tab now was bricked as before the lonovo assistant while i could not start android i could still run and start the dev screen but after the phone simply got stuck on a restart loop and i was locked off the dev screen now i could not check or do anything i have ran a few more sp flashes even full format and memory checks (all successful) the usb connection still works but i have not been able to unbrick the TAB so I'm moving on got my sight on a xioming for now
lessons
*don't rush when flashing if you have things to do and you don't need your phone do them then flash in peace
*if you have flashed once before successfully do a back up on the dam dev screen it only takes an 8Gb sdcard and 30 minutes tops
*the coding on the contact app is a bit faulty just download the contact app from google
*if you suspect theres hardware damage disable the parts that are damage not sure but i suspect this is what corrupted my root files
*the back plate is a bit hard to remove but you should always try to do sp before you start flashing to disconnect the battery and have very small screwdriver philipshead i also suspect this may have had a part on this
*never use the lenovo assitant i think this is why most people don't even mention it on a first dive when you search