Hello everyone.
So I successfully rooted the A10-70L ZA010062ZA using the simple tool: KingoRoot.
It was truly easy; just downloading and installing KingoRoot onto my laptop (I did not trust installing it on the tablet itself) and it turned out to be a big success with just one click of a button ("Root") after plugging the tablet into my laptop using USB (with USB debugging turned on ofcouse).
So here I went and downloaded Linux Deploy onto the tablet and spent a day TRYING to install Kali onto it. Honestly, there were so many issues and errors, I just got frustrated.
I honestly did not figure out how to do this yet; because why? The tablet thought to itself "What madness it this?!" and he shut down instantly, BOOM!
I was confused at first, holding my head with my hands in my hair when i then realised - Wow, okay.. It does NOTHING when i try to turn it on! I freaked when I realised that I have hard-bricked it.
After trying ONE LAST TIME to turn it on, holding the power button for almost a minute before losing hope, IT TURNED ON! But.. It got stuck in a boot loop, showing only the boot screen. I WAS RELIEVED!! I only soft-bricked it.
Now I am currently downloading the stock ROM, which I believe should work. I will post an update on this thread to keep you up to date on what I did and if it was successful.
Question: Is there maybe ANY custom ROM that is compatible with the A10-70L ZA010062ZA?
The stock ROM is cool and everything, but why not make the device a brutally epic device if the possibility exists?!
Xx
EgyptianCobra
Related
Hello all! Today I have been having a tough day with technology SMH! But anyways I have been looking at every single post on this website and looked on Google about my problem and I can not fix it AT ALL! I'm really new to this hacking rooting stuff. I just bought a kindle fire just last week and I decided to put android 4.0 just last week and I had no problem with doing that what so ever. It was very simple and easy. But for some really I went back to the stock OS and deleted the android 4.0 files off my Fire. But today, I wanted to do it again but this time from a different website. The file was called MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D FYI. I thought these files all do the same thing and stuff. Like I said, I am new to this. Never used an android device a day in my life. (Team IOS lol) Back to my problem. So I did the regular on TWRP. I Backed up my data, cleared the Factory Setting,then I went to flash the Zip file I had. After it was done installing or whatever, this is when everything happened. I rebooted my kindle like always, But this time the yellow triangle was on the screen for about 10 min. So I held the power button for 20 and maybe thought it just needed to reboot again. Well, I sat and waited for about 5 min once again and nothing happened at all. I tried to connect my Kindle to my Laptop but it makes the donkdonk noise once like it connected. But then it makes the same noise again but it disconnects. Also, with the KFU (Kindle Fire Utility) it says device is not connected or whatever it says.So, I have been reading online that I need to go into Device manager and do some stuff. But when I go into Device Manager. I see my Kindle for 5 secs when I first plug it into my pc but then it disconnects. I can not believe that I did this. So can anyone please help me out before I do something else stupid to it,it would mean a lot to me! I will take ANY advise right about now! Thank you!
I did the same thing
The file you downloaded was bad i downloaded the same file , I fixed it by running KF utility and reinstalling TWRP , when it tells you to plug in or device not found turn off device plug in usb and push power until turns orange or green forget which one after that it will recognize the device , this worked for me i hope i helped you
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
I have the Lenovo ideapad K1 and have flashed it twice. My third attempt stopped part way through due to a bad image file. Turned the device on and off and haven't been able to access it since. Now I have not animation when powering the device. When I turn on the device the lights come on (2 near the "navigation" button on the front) but that is all. It no longer registers in windows as an APX device either and it says "unknown usb device". The device registered before and I've changed nothing.
So, is it bricked are just playing dead?
UPDATE!! I plugged my pad into the wall charger and then turned it off and on repeatedly. I put it into APX mode while plugged in and saw a flash on the screen instead of the usual soft lighting so I thought, maybe somethings changed. Plugged the pad into the usb port and still now APX. Moved the usb plug to a different location and now I'm in APX . Am able to run NVFlash.bat but getting errors. Will keep trying while looking up info on NVFlash. Still think I'm bricked but will throw everything at it to get it working. Will keep updating this post.
It's working again
I moved the cable to a different usb port, tried installing the stock HC rom first and it partitioned the tab but got stuck sending the recover.img file. So I turned it off again, moved it to a different usb port and tried installing the JB CM9 rom which was the last working rom I had (besides ICS). It worked! When the tablet came back on it had 11% battery left!
I've never appreciated my tablet as much besides the first days I got it. I couldn't really afford a new one right now since I'm recently unemployed so I"m grateful this worked.
My only suggestion with a "bricked" tablet - try try again, try everything, keep you head, walk away and come back, don't give up
Time to go setup my tablet again!
i need help
gendou2 said:
I moved the cable to a different usb port, tried installing the stock HC rom first and it partitioned the tab but got stuck sending the recover.img file. So I turned it off again, moved it to a different usb port and tried installing the JB CM9 rom which was the last working rom I had (besides ICS). It worked! When the tablet came back on it had 11% battery left!
I've never appreciated my tablet as much besides the first days I got it. I couldn't really afford a new one right now since I'm recently unemployed so I"m grateful this worked.
My only suggestion with a "bricked" tablet - try try again, try everything, keep you head, walk away and come back, don't give up
Time to go setup my tablet again!
Click to expand...
Click to collapse
can u send me the HC image, my tablet is showing unrecoverable bootloader error 0x00000000008
any suggestions?
Hope this will work on my K1 issues:fingers-crossed::fingers-crossed:
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help