Related
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
I just got from a friend an Acer Iconia a500 he says that is bricked.
I tried this method: http://forum.xda-developers.com/showthread.php?t=1572622
But I can't continue because I don't have ADB access, what should I do?.
Thanks for all and God bless you.
EDIT:
I got everything to using the secret APX mode, but now is still everything the same the Android System is still there and not charging and not touchscreen...
Go to the bottom to see how I solved this lol...
Click to expand...
Click to collapse
If your tablet Iconia 500 (ONLY ACER ICONIA A500) went crazy, and present the next symptoms (Yes it has flu...):
-flu
-Android System icon
-Doesn't want to charge (20% / 15% 12%).
-TouchScreen is not responsive.
-Always when you turn it on says Shutting down and never shuts down.
-In case you're using ICS shuts down immediately without even make you see.
The solution is the next!:
1. Download this file: http://www.4shared.com/archive/zyP91E0C/root-321-V4.html (This is the file to put recovery in case that you don't have it).
2. Extract all the files in any folder, it doesn't matter where you put it.
3. Go to Image Folder and rename the recovery to: anyname.img.
4. Download any of the lastest recoveries for Acer Iconia a500 (it will work believe me lol).
5. Put the recovery in the Image folder (Ex. Iconia/root-3.2.1/Image/) and rename it to recovery.img
6. Now open with Administrator Rights DotNetDetecter.exe
7. Continue, continue and continue.
8. If you have ADB Active just put it and it will install it. (If you don't have it just go to 8.1)
8.1 Shut down the tablet completly, connect your USB Cable *micro* (Tablet-Computer), take a paper clip and put it on reset without release it then press the power button and count until 4 or u4ntil you hear the sound when you plug something into Windows
8.2 Now your tablet is in APX Mode and the Acer Utility should now work.
9. Put your UID with a 0 in front of all the numbers (if you don't have it go to secret step).
10. Now let everything work. After everything is done you should have recovery now.
11. Press down volume and the tablet will take you to the recovery.
12. Download some ROM 3.2 or ICS 4.0.3, install it via recovery.
13. Download this file: http://www.mediafire.com/?9svnvdk982sxrw4
14. Install the version you have choosen via Recovery.
15. Voila! Your tablet is revived right now
Press thanks button if this helped you =D
SECRET STEP TO GET UID (IS NOT SECRET THOUGH... lol)
Just go to USB tools and use USBdeview, and is done... (Remember to stay in APX Mode)
CREDITS:
-Fguy on www.4pda.ru (EC_FLASH FILES)
-timmyDean on XDA (Root-3.2.1-V4 FILES)
-Moscow Desire (XDA Member, if it wasn't for him it couldn't get to see the light)
thanks for the great guide but could you point me in the right direction for the lastest recoveries for Acer Iconia a500 as the links i find dont work
thanks in advance
matthew
mjfaderway said:
thanks for the great guide but could you point me in the right direction for the lastest recoveries for Acer Iconia a500 as the links i find dont work
thanks in advance
matthew
Click to expand...
Click to collapse
Acer Recovery from the Market should have the most recent RA Recovery, and the original GPL compliant CWM recovery.
Or if you already have the original CWM, you can get the most recent RA Recovery here. Just check the threads for the flash files.
http://forum.xda-developers.com/showthread.php?t=1459821
For CWM you will need to go to tegraowners.
Dear Sir
I have same problem with my tablet too for 4 months and I explained that HERE or HERE
and i followed all instruction in these 2 threads
http://forum.xda-developers.com/showthread.php?t=1572622
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
and I used from ECrom files created by Mr. Fguy ver 4.03-22 and 3.2.1 but my problem is Lasting yet
can you help me?
you had same problem and you know how bad is a bricked tablet in your hands
thank you and GOD bless all of you
[email protected]
[email protected]
darvis said:
Dear Sir
I have same problem with my tablet too for 4 months and I explained that HERE or HERE
and i followed all instruction in these 2 threads
http://forum.xda-developers.com/showthread.php?t=1572622
http://forum.xda-developers.com/showthread.php?p=24531880#post24531880
and I used from ECrom files created by Mr. Fguy ver 4.03-22 and 3.2.1 but my problem is Lasting yet
can you help me?
you had same problem and you know how bad is a bricked tablet in your hands
thank you and GOD bless all of you
[email protected]
[email protected]
Click to expand...
Click to collapse
I don't have the tablet anymore, it was a friend one, I can help you with your big problem because really it was easier than I thought, you can PM me with all the details, and yes the flu is a big problem... =P
Problems with opening up settings to turn on usb debugging
Hi Travisantonio,
I have a question:
Did you have any problems opening up the settings when you were on the black "android system" screen?
My touch screen is completely unresponsive at the moment.
Maybe I didnt read or understand everything but with my tab USB view didnt give me my ID or it wouldnt work. Got into ADX mode but couldnt get things working. Tried ADB to list devices and would never list anything. I heard my computer beep when I would hook it up but couldnt really do or complete anything. I couldnt get the DOTNETDETECTOR (PBJUPRADE_ to work. Tried A500 APX flash utitlity. Tired nvflash and falied. Guess I should list more information but at this point I tried so many things to recover dont remember the order I did things. I originally tried to upgrade to a Rom but all things failed and actually not sure what ever got completed. Only thing I could tell my tab did besides black screen was the power button either was white(some type of one) or orange.
This helped me to recover my bricked Acer 500 tablet after a failed ICS upgrade. The Acer update seemed to go okay, but on reboot it froze at the Acer logo and had an error in the corner. Every reboot or button/reset resulted in this. It would not recover or do anything else. I was able to get the USB device ID /serial number using the USB deview 64 program in the usb folder. There were several entries for the tablet but only one had a usable number (bottom right line at the end). Then the tool wiped the tablet and reloaded 3.2.1 and booted to factory new. Thanks for the instructions and to all the other XDA-ers for the tools. I am now on ICS properly.
Trying to recover a bricked acer a500, I just have a black screen on boot with no boot logo, vibration or letters or words on the screen
trying to enter recovery/update mode doesnt work
Im up to the step where is says put in your UID into the program
Just go to USB tools and use USBdeview, and is done...
Click to expand...
Click to collapse
I did this and found the device but where exactly is the UID located?
looking at other threads, the serial number is the UID however the serial number entry is blank for this device
Joey22688 said:
Trying to recover a bricked acer a500, I just have a black screen on boot with no boot logo, vibration or letters or words on the screen
trying to enter recovery/update mode doesnt work
Im up to the step where is says put in your UID into the program
I did this and found the device but where exactly is the UID located?
looking at other threads, the serial number is the UID however the serial number entry is blank for this device
Click to expand...
Click to collapse
this method is total overkill for your situation....
how did u get yr tab like this???
if u have total black screen - is the power button lite on?????
what bootloader version are u on
have you had a custom recovery on there
to get your cpuid follow the first link to a guide in my signature - you need to follow steps in the guide if you have any probs then post in the guide thread
the previous owner said he tried to install a custom rom and I think it crashed and this is the result
the power light turns on (white)
if I just power it on, the backlight turns on however its just a black screen, nothing else happens
apx mode seems to be the only thing working right now, I thought this method would be my only chance to get the recovery mode working again
I dont know anything else about the tablet, bootloader ect...
Joey22688 said:
the previous owner said he tried to install a custom rom and I think it crashed and this is the result
the power light turns on (white)
if I just power it on, the backlight turns on however its just a black screen, nothing else happens
apx mode seems to be the only thing working right now, I thought this method would be my only chance to get the recovery mode working again
I dont know anything else about the tablet, bootloader ect...
Click to expand...
Click to collapse
ok thats cool, apx mode works!!!
well try this first - using hard reset:
1) Turn off your tablet,
2) Rotation lock on your left;
3) Press Vol Up closest to rotation lock and power on simultaneously
4) As soon as the tablet vibrates you can release the power button and you should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol Up is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
otherwise plan B!!!
do u know whether tab was running HC or ICS?
u need some package files and a flash tool either apxflash or nvflash
if u start the tools and then connect your tab via usb cable to your pc
there are links to guides in my sig
my cpuid guide shows u what u need and where to get it, info about your cpuid too and drivers - altho you wont need to worry too much seeing as youre in apx
civatos guide has all the links to the packages and all the info you need to patch the bootloader, then you can flash one of the ics roms and youre all good!!!
the process is simple enough - but if you get it wrong it can be frustrating as heck!!!!
tried that method, get no vibration, devices just turns on to the black screen like normal
the only problem right now, I cant retrieve the uid
adb
when I type adb devices, nothing shows up
A500 manager
tried to the use the uid retriever tool however it just stays blank, same for the bootloader
it says it detects the A500 in apx mode
usbdevice view
shows no serial number for this device
I see there is a A500 motherboard on ebay (cant link to outside links...)
"Acer Iconia A500 Tablet Replacement Parts - MainBoard - 32GB MB, H6000 001 PBJ20"
"Complete with Android 4.x installed, 32GB memory and ready to install and boot."
could I get that and just replace the whole mobo and it will work fine?
Joey22688 said:
tried that method, get no vibration, devices just turns on to the black screen like normal
the only problem right now, I cant retrieve the uid
Click to expand...
Click to collapse
OK just clarify - black screen, that is, nothing at all displayed AND Power Light ON??
IF u r in apx mode then
U have a couple of options
EUU flash back to HC 3.2.1 or
apxFlash to ICS
Everything you need for doing this is in my cpuid guide link in my sig.
open apxflash tool do not connect your tab Yet
Go as far as the enter apx mode
Now connect your tab to yr pc
Windows should install apx drivers
Once installed. try clicking blue arrow first
If u don't see the do u want to flash window then
You'll need to click on the "enter apx mode " button instead then
Click blue arrow
Hopefully the PC and tab are feeling pretty friendly and decide to take each other on
The tab should flash the bl and install recovery.....u should be good to go from there!!!
EDIT you can try cmd prompt on nvflash folder
Run a500.bat or.bat file that should kick you to bootloader mode
its really important that your screen display something in white letters!!
Entering Acer download mode OR
Entering apx mode
The flash will fail if u don't see something like this. This holds true for all methods
I see there is a A500 motherboard on ebay (cant link to outside links...)
"Acer Iconia A500 Tablet Replacement Parts - MainBoard - 32GB MB, H6000 001 PBJ20"
"Complete with Android 4.x installed, 32GB memory and ready to install and boot."
could I get that and just replace the whole mobo and it will work fine?
Click to expand...
Click to collapse
Wayyyy outta my league m8. Sum1 else will know....
yes, its just a black screen, no vibration, no boot logo, no letters or words on the screen, backlighting for the screen is on, and the power light is on
when I press the blue arrow in a500 apx flash tool it asks me for my SBK, going to that generator site it then asks for my UID which I cant retrieve
Joey22688 said:
yes, its just a black screen, no vibration, no boot logo, no letters or words on the screen, backlighting for the screen is on, and the power light is on
when I press the blue arrow in a500 apx flash tool it asks me for my SBK, going to that generator site it then asks for my UID which I cant retrieve
Click to expand...
Click to collapse
if you do not have your cpu id and
if you do not have access to adb and
you're stuck in apx mode
then things are looking grim.....
the only way to get into your tab without yr cpuid is fastboot
but you need adb working for that
someone else was stuck in apx mode a day or two ago, try a search...maybe...
I'm sorry guys I was a little off of this thread .
I will be glad to help you guys to get your UID or any problem that you have even though I don't have the Tablet anymore.
Thanks for all and God bless you all.
dibb_nz said:
if you do not have your cpu id and
if you do not have access to adb and
you're stuck in apx mode
then things are looking grim.....
the only way to get into your tab without yr cpuid is fastboot
but you need adb working for that
someone else was stuck in apx mode a day or two ago, try a search...maybe...
Click to expand...
Click to collapse
There is no way to fastboot the tablet in that mode, the only way is to get the UID and then decode it and NVFlash the Bootloader after it is done then put ICS or HC and the EC_ROM files and the tablet will be working again.
I'm gonna throw in the towel and just buy a new mobo for cheap, it seems im screwed without the UID and cant retrieve it either
I wish the previous owner would have gotten the UID beforehand
thanx for the all the help though
Joey22688 said:
I'm gonna throw in the towel and just buy a new mobo for cheap, it seems im screwed without the UID and cant retrieve it either
I wish the previous owner would have gotten the UID beforehand
thanx for the all the help though
Click to expand...
Click to collapse
Sent from my A500 using xda premium
Just come across this check here: /sys/firmware/fuse/acer_cpuid
dibb_nz said:
Just come across this check here: /sys/firmware/fuse/acer_cpuid
Click to expand...
Click to collapse
What do I exactly do?
I dont have any access to the devices files and do not have a dump
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
I had heard it was coming. Good deal. Now I can give up root to get repaired without fear.
Could someone host the two needed files somewhere? Its a pain in my ass to load these from these Chinese hosters...
coming soon! uploading to hotfile..
hope helps
https://hotfile.com/dl/169617659/de8c673/CWM.rar.html
https://hotfile.com/dl/169617791/ac3fa3c/root.rar.html
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Any steps to follow on how to root my TPT ROW on a mac?
Does not work at all for me. nvflash shows me the typical 0x4 error when it tries to injct the bootloader bin file...
This will work only on unlocked devices, because it uses nvflash and i can't find any sbk in the bat files (cwm.zip). The root.zip only contains the known exploit for devices below ICS.
nsxt99 said:
Yes! i have mine 16GB ROW rooted!
The link is in Chinese, i am for sure will have some kind soul will translate it to English.
http://cnzhx.net/blog/apx-root-thinkpad-tablet/
download link of 2 files is at hotfile. please find the link at 5th post.
enjoy rooting.
& i will say, finally i got life back on my TPT!
Click to expand...
Click to collapse
Yes, I heard this and tried it on my US 32Gb version, but i failed.
Got an write/read error/warning, then the program stopped.
As I know, this rooting method ONLY works on ROW versions, but not US version.:crying:
It did fail, but did not bring any bad effects to my TPT. I just updated to the stock OTA3.5 smoothly.
Anyway, thanks for sharing.
Hey guys, i just wanted to tell you that it worked for my OTA3 TPT ROW.
Tip: try extracting the recovery image from your rom (eg. US) and put it instead of the one provided in there rars, it might work for you.
Cheers!
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
EDIT: Does anyone have a stock rom? I'm looking to do what the last commenter suggested and switch out the image.
goodboynyc said:
Google did it's best to translate the think but I'm a little weary to try it as the steps are still a bit garbled.
Click to expand...
Click to collapse
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Does this mean we have the key for nvflash?
Sent from my ThinkPadTablet using Tapatalk 2
My question in regards to this is can we build a flashable rom of this? And would this work with the US TPT?
Sent from my ThinkPad Tablet using XDA Premium HD app
crabnebula said:
I followed the translated instructions and am now running CM10 on my 16GB ROW. It's fantastic -- like having a new device.
The instructions are pretty simple to follow. I had one problem though.
To use nvflash, you need to start the tablet by holding down the rotation lock button and then install the provided driver in Windows. This works well. However, after performing a flash, Windows would no longer recognize it if you power it on while holding the rotation lock button. To gain access to the special recovery mode again, I had to uninstall the device and driver in Windows Device Manager, and the reinstall again when prompted.
Because the whole procedure requires multiple flashes with nvflash, I had to perform this uninstall-reinstall process several times.
Other than that, it worked perfectly well.
Hope this helps if anyone encounters the same issue.
Click to expand...
Click to collapse
I need to try this. But from what I understand this only works for ROW versions and not US versions(given the attached files from the OP). If someone could post an image of a US version I'd cross my fingers and give it a go.
I can't even get past CWM.bat.
I get an NvError 0x30011.
goodboynyc said:
I can't even get past CWM.bat.
I get an NvError 0x30011.
Click to expand...
Click to collapse
Same here and before is a hidden 0x4 hidden by a CLS command inside the script.
I'd be great if we could get some developers input. I program in C++ and Visual Basic but have no experience with Android/Linux to be able to look deeper into this :S
Moved To General
If somebody wants to write a guide and supply a proper dev section thread, fine. But this thread is not development.
Hi, I have succesfully rooted my ROW 16GB Wifi-only ICS 4.0.3 tablet following chinese guide. Excuse my english, Im not native speaker . I'll try to explain what I did:
1. make sure you can see your TPT with "adb devices" command.
2. turn off your device, make sure you have USB cable connected, hold rotation lock button + power on device to get to APX mode. Screen will not turn on, but windows will find new APX hardware unknown.
3. update software driver for APX, set CWM folder manualy. You should now have NVIDIA USB Boot-recovery drover for Mobile devices installed.
4. in APX mode run "cwm.bat", after its done, reboot device to APX mode and press any key, dont press it before you restart your device. You can see CWM_recovery.img installing to your tablet. Follow instruction...
5. After step 4 is done, reboot your device to Recovery, when you see small lenovo logo spam volume up button until you see "booting to recovery kernel mode".
6. Navigate to mount and store using vol +/- button, power button to confirm. Select mount /system
7. make sure you can still ses your device using "adb devices" command, and run root.bat, follow instruction. When all is done, select power off in recovery menu.
8. Now you have root, but you cant boot to system. You need to get to APX mode again and run "403 recovery.bat", follow same steps as with "cwm.bat".
9. reboot and you should now have rooted TPT.
Hope this help, Im not so good at giving instructions .
So, i have been tasked with fixing an acer tablet. I have been searching these forums for a few days to try and figure out how to fix this tablet.
The issue is, it sits at the ACER logo screen (this would be an easy fix on my GNEX). Sifting through the threads i decided to post here to help me move this along faster.
I can get the device into the bootloader. I am presented with the following -- Bootloader v0.03.12-ICS: Starting Fastboot USB download protocol. I can not use fastboot as the bootloader is locked and i can not unlock it (from searching i found i need to installed a patched version, and that is where i am running into issues).
I can not figure out his CPUID. Since the system will not boot, i can not use a terminal to get it. this tablet was completely stock so no CWM on it. I thought i had it showing in ADB once, but i have never been able to get it back into that mode. (any tricks, i thought it should work if i am in the bootloader, i installed the driver from acer, but i does not list any devices, tried another usb port).
I have also tried putting an update.zip file on the sd card and booting into stock recovery, but that ends up with an android with the red ! mark above its belly.
so, i ask you guys for some help. Is there any way i can fix this tablet?
EDIT:
when i do a fastboot devices, i just get a ? fastboot. and nothing for ADB
The tablet also responds to fastboot commands, mainly reboot, anything major and it tells me denined (that it is locked)
EDIT2:
I have blackthund3r A500 manager running, i got the tablet into APX mode, at the bottom it says A500 detected in APX mode. When i click Dump dmesg to desktop, it created a file but nothing is filled in it. When i clicked view dmesg, it says - error: device not found.
Also, under device manager i am seeing a device called Acer USB boot-recovery driver. When i get it into bootloader it shows up as a ADB driver.
Thanks
-CGfreak102
I'm going to assume you have an A500 and NOT an A501.
It appears your stock recovery is probably also working, as if it weren't, you'd probably go to APX mode. As it is, you get the Acer screen.
Regardless, here's a list of A500 ICS full update files on my Dev Host server. I've already decrypted, and named each one a little different so you won't get confused. Put one of them (the zip file, DO NOT EXTRACT) on your external SD card. Then power on your tablet holding either PWR & Vol+ , or, PWR & Vol-. Can't remember which for stock recovery. See if the update will install. You'll see some text in the upper left corner, then you can release the buttons.
http://d-h.st/Zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/KXl
Now, you may have to try more than one of these updates. Some work, some don't. But try each one and see if it completes install. This is about the easiest way to begin with.
If it don't work, then probably have to get a linux ubuntu install to get the UID number.
MD
Moscow Desire said:
I'm going to assume you have an A500 and NOT an A501.
It appears your stock recovery is probably also working, as if it weren't, you'd probably go to APX mode. As it is, you get the Acer screen.
Regardless, here's a list of A500 ICS full update files on my Dev Host server. I've already decrypted, and named each one a little different so you won't get confused. Put one of them (the zip file, DO NOT EXTRACT) on your external SD card. Then power on your tablet holding PWR & Vol+. See if the update will install. You'll see some text in the upper left corner, then you can release the buttons.
Now, you may have to try more than one of these updates. Some work, some don't. But try each one and see if it completes install. This is about the easiest way to begin with.
If it don't work, then probably have to get a linux ubuntu install to get the UID number.
MD
Click to expand...
Click to collapse
The updates did not work for me (was I not supposed to change the names of the archives to update.zip?), and I have the exact same issue as the author of this thread (minus the part where he's doing it for someone else, It's my tablet). Is there a way to get the CPU ID on XP? I do not have access to a Ubuntu installed computer, although I have Virtual Box installed on my XP and when I set up Ubuntu on it, it did not work.
thank you
thank you, it worked for me.
i formatted my SD card, and i renamed the file i downloaded with ------> update
i copied it to SD card.
i pressed Power button + Volume button (-)
it took me less than 2 minutes to update.
CGfreak102 said:
So, i have been tasked with fixing an acer tablet. I have been searching these forums for a few days to try and figure out how to fix this tablet.
The issue is, it sits at the ACER logo screen (this would be an easy fix on my GNEX). Sifting through the threads i decided to post here to help me move this along faster.
I can get the device into the bootloader. I am presented with the following -- Bootloader v0.03.12-ICS: Starting Fastboot USB download protocol. I can not use fastboot as the bootloader is locked and i can not unlock it (from searching i found i need to installed a patched version, and that is where i am running into issues).
I can not figure out his CPUID. Since the system will not boot, i can not use a terminal to get it. this tablet was completely stock so no CWM on it. I thought i had it showing in ADB once, but i have never been able to get it back into that mode. (any tricks, i thought it should work if i am in the bootloader, i installed the driver from acer, but i does not list any devices, tried another usb port).
I have also tried putting an update.zip file on the sd card and booting into stock recovery, but that ends up with an android with the red ! mark above its belly.
so, i ask you guys for some help. Is there any way i can fix this tablet?
EDIT:
when i do a fastboot devices, i just get a ? fastboot. and nothing for ADB
The tablet also responds to fastboot commands, mainly reboot, anything major and it tells me denined (that it is locked)
EDIT2:
I have blackthund3r A500 manager running, i got the tablet into APX mode, at the bottom it says A500 detected in APX mode. When i click Dump dmesg to desktop, it created a file but nothing is filled in it. When i clicked view dmesg, it says - error: device not found.
Also, under device manager i am seeing a device called Acer USB boot-recovery driver. When i get it into bootloader it shows up as a ADB driver.
Thanks
-CGfreak102
Click to expand...
Click to collapse
I found a partial solution to the problem. you need to download a file archive called babsector.rar. It has two batch files in it that will basically do the same thing as blackthunder's tool, the only problem being is that the tool won't work for me. The other part of the bad side is that now I need help to flash a kernel onto mine without the tool.
moscow desire said:
i'm going to assume you have an a500 and not an a501.
It appears your stock recovery is probably also working, as if it weren't, you'd probably go to apx mode. As it is, you get the acer screen.
Regardless, here's a list of a500 ics full update files on my dev host server. I've already decrypted, and named each one a little different so you won't get confused. Put one of them (the zip file, do not extract) on your external sd card. Then power on your tablet holding either pwr & vol+ , or, pwr & vol-. Can't remember which for stock recovery. See if the update will install. You'll see some text in the upper left corner, then you can release the buttons.
http://d-h.st/zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/kxl
now, you may have to try more than one of these updates. Some work, some don't. But try each one and see if it completes install. This is about the easiest way to begin with.
If it don't work, then probably have to get a linux ubuntu install to get the uid number.
Md
Click to expand...
Click to collapse
this being a very old thread, any luck on getting new links 4 years later? My acer a500 stuck on the boot screen. Thanks
GizoMot said:
this being a very old thread, any luck on getting new links 4 years later? My acer a500 stuck on the boot screen. Thanks
Click to expand...
Click to collapse
I might have one or two of the files lying around on my computer let me see if I can find them and upload them.
Hello,
I have been asked to troubleshoot an ACER iconia stuck at boot logo. I am not sure if what I read here is applicable to the model I got. Here is what I can read on the label at the back of the tablet :
ACER iconia One 10 B3-A20 Model A5008
FCC ID:HLZA5008 IC: 1754F-A5008
So is "A500" topics relevant for that tablet ? I don't see any topic about "iconia one 10" or "A5008" ...
Thank you for your answers.
Stock firmware reinstalled
Replying to myself !
Found stock firmware from that Acer link, entering model etc.... (change language FR to what you need).
Then copy downloaded file to SD-CARD, and restore firmware from the recovey menu (pressing "Vol Down + Power" to enter.
Then Restart ... Cool.
pled said:
Hello,
I have been asked to troubleshoot an ACER iconia stuck at boot logo. I am not sure if what I read here is applicable to the model I got. Here is what I can read on the label at the back of the tablet :
ACER iconia One 10 B3-A20 Model A5008
FCC ID:HLZA5008 IC: 1754F-A5008
So is "A500" topics relevant for that tablet ? I don't see any topic about "iconia one 10" or "A5008" ...
Thank you for your answers.
Click to expand...
Click to collapse
I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!
Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it
CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.
no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
will this root onn 8 inch tablet running android 9
soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.
installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes
when you mean patch boot img do mean to unzip file on onn 8