COMPLETELY BRICKED A7+ please help

---

hi all i attempted to use the dextor hack and i messed up with the flash all data step i thought it did it but it didnt and then when i went to update and it was done i just get a black screen when i turn on the device i can not even go into recovery mode its just basically lighting up the screen and nothing i am very tech savy so i can do just about what ever i need to just somebody please help me out hours of looking and i cant find a single thing on this

Not Really Sure how much help i can give you seeing as i never seen anyone brick one of theses devices. Im pretty sure you don't a Elocity A7+, from i beleive they aren't available on the market. You should have a regular Elocity A7.

Before you check the link below be very positive you can't get into recovery, sometime it take a little long for it to come up.

Also if the tablet is new you should also think about calling or emailing Elocity to see if it can be replaced.

most of use aren't very active in the Elocity A7 forum of xda, so you may get more help at Tabletroms Forum

I don't no much about Nvflash but you should read into this it may help: http://forum.xda-developers.com/show....php?t=1022273

The A7+ has been selling and shipping for the past few weeks, i just got mine delivered today. Now I'm here learning that trying to use the A7- hack might be a bad idea.

a7+ bricked fix

---

See Destron5683 response for black screen, make sure you use the a7+ update if you bricked your new a7+ trying to upgrade it.

Any advice for following
http://forum.xda-developers.com/show...php?p=21109150

and then not being able to access the keyboard? Thats the point I am at currently.

This is an older thread, but assuming you have not tried it, see the recovery information at ElocityNow website:

http://www.elocitynow.com/prod_a7-plus_recovery.shtml

You should be able to get back up and running it the recovery posted in the post above. I got my A7+ stuck in a boot loop when I changed something that I shouldn't have in the build.prop and the PC recovery method worked just fine.