First things first. The device in question is an Acer Iconia Tab A200.
Alright, so here's what's going on. Recently, something happened and the tablet asked to do a hard factory reset. It stopped at a screen that terminated in red text "Verified Failed". It is a stock device. The only thing different is that it was running Nova Launcher. No rooting, nothing else. Nearly all of the posts I have found assume that some level of rooting has occurred, and the rest are unresolved. I have nothing, not even any tools, because almost all of the links to tool downloads terminate in dead dropbox links or uncomfortably sketchy download sites. Thank you in advance for any and all help.
Hydroskull said:
First things first. The device in question is an Acer Iconia Tab A200.
Alright, so here's what's going on. Recently, something happened and the tablet asked to do a hard factory reset. It stopped at a screen that terminated in red text "Verified Failed". It is a stock device. The only thing different is that it was running Nova Launcher. No rooting, nothing else. Nearly all of the posts I have found assume that some level of rooting has occurred, and the rest are unresolved. I have nothing, not even any tools, because almost all of the links to tool downloads terminate in dead dropbox links or uncomfortably sketchy download sites. Thank you in advance for any and all help.
Click to expand...
Click to collapse
how about to enter recovery mode and wipe all?
droidinterest said:
how about to enter recovery mode and wipe all?
Click to expand...
Click to collapse
Not sure entirely what you mean, but through the Pwr, Vol+, and screen lock combos, it does a couple "booting recovery kernel" loops with the android and a spinning wire ball, but then it terminates in "Verified Failed"
Hydroskull said:
Not sure entirely what you mean, but through the Pwr, Vol+, and screen lock combos, it does a couple "booting recovery kernel" loops with the android and a spinning wire ball, but then it terminates in "Verified Failed"
Click to expand...
Click to collapse
maybe this is will help you http://forum.xda-developers.com/wiki/Acer_Iconia_A200
droidinterest said:
maybe this is will help you http://forum.xda-developers.com/wiki/Acer_Iconia_A200
Click to expand...
Click to collapse
I have seen that page, but am not entirely sure how to flash anything to the device. I tried flashboot commands, but I am apparently missing a myriad of .dll's. Just as a point of inquiry, was the A200 not widely sold? I have seen a lot of A100 and A500, but not much from A200, A300, or A400. I apologize for my helplessness, but I have absolutely no experience with the inner-workings of android devices, and I do not know anyone who has any experience. Thank you for your help.
Hydroskull said:
I have seen that page, but am not entirely sure how to flash anything to the device. I tried flashboot commands, but I am apparently missing a myriad of .dll's. Just as a point of inquiry, was the A200 not widely sold? I have seen a lot of A100 and A500, but not much from A200, A300, or A400. I apologize for my helplessness, but I have absolutely no experience with the inner-workings of android devices, and I do not know anyone who has any experience. Thank you for your help.
Click to expand...
Click to collapse
I think your recovery got messed up. if you can go to recovery mode do a factory reset from there. if XDA has forum for your device, ask there you will get a better response and solution
PradeepMurugan said:
I think your recovery got messed up. if you can go to recovery mode do a factory reset from there. if XDA has forum for your device, ask there you will get a better response and solution
Click to expand...
Click to collapse
Yes, that is exactly my problem. Unfortunately, XDA does not have an Iconia A200 forum. It has A100, and A500, but no A200. I checked. Also, I already did a factory reset, which was the spark that led to the current problem. I have sense tried multiple factory resets with the exact same error.
UPDATE:
A friend of mine, who apparently has de-softbricked a tablet took a look at it. He returned it with the sad news that he/we could not do anything with it due to it failing to register when connected to the computer. Thank you all for your assistance, but I now have to decide between attempting to contact Acer and just buying a new tablet.
Related
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
I have exactly the same problem please someone help us :angel:
virus4o said:
I have exactly the same problem please someone help us :angel:
Click to expand...
Click to collapse
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Same problem while flashing CM
Aduniel said:
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Click to expand...
Click to collapse
My tf is in the same state. Got there when trying to install CM's nightly build.
Bricked TF201 - Stuck in bootscreen
I have the exact same problem. :crying:
Please, I know that there are many brilliant minds in this forum, help us n00bs get out of this mess and lead us into the light. Oh, and bump this thread
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
spudthedestroyer said:
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
Click to expand...
Click to collapse
This sucks, I did the same exact thing last night factory resetting it to give it to my brother. I still don't understand what exactly I did wrong as I've factory reset this thing before. I had CM on it before but have been using the stock rooted ROM & recovery for the past 6+ months.
bricked?
I've been scouring that internet and haven't been able to find a case exactly like mine, but most are similar. From what I can remember (it's been months since I initially 'bricked' it), I was upgrading a cm nightly and did the data/cache/dalvik wipe like the instructions said and I became stuck in a bootloop after leaving recovery. When I tried volume-down and power, I was left with the original 3 options and after some reboots and shutdowns I ended up doing a factory data wipe. From there, when I rebooted the phone I was left with just 'Wipe Data' and 'Fastboot.' Wipe data does nothing more and when I choose fastboot I am left a message 'Starting fastboot usb download protocol' which never changes.
I have tried to push TWRP onto the device but I can't get into recovery (unless I'm doing something wrong of course). Sorry if I missed a duplicate of my post somewhere on here, but if so can someone at least point me in the right direction? Thanks!
i.imgur.com/LEHNREw.jpg
try another ROM
This has worked for me everytime, possibly due to dud bootloader install or some other thing: so long as I was able to recover to CWM with pwr+vol down, I installed virtuous prime rom. This rom was on sdcard already, not sure if you can get from adb if machine in this state. Anyhow, this virtuous prime rom replaced the booting sequence, restored OS and machine worked again.
Asus TF201 stuck on Asus Logo
My Asus Tablet was slow while browsing, and it had JB 4.1.1 with stock rom, so i tried to unlock the device, which was successful and was planning to push the CM11 Kit Kat. I booted in to recovery mode as i could see the 4 icons and then tried to do wipe data/factory reset and then it rebooted and got stuck on the asus logo and at the right bottow with the message powered by NVIDIA Tegra. I tried all the options to get into recovery and also downloaded drivers on my laptop for APX, but no luck at all. What are my options or if any one was successful to get it fixed. Appreciate any help here from smart guys out there. Thanks
spudthedestroyer said:
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
Click to expand...
Click to collapse
I had messrd up my tf101 with cm nightly to. I did manage to get it working again with adb tool of sorts. When im home i will tr y to find it on my comp. Th
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
After reading http://forum.xda-developers.com/showthread.php?t=2433323 I am starting to think a lot of these topics go unanswered and point to a flaw in the flasher, my region.prop is also missing and can only presume the tablet requires this for an update and the factory reset removes the root so cannot push another .prop over. So for all intents and purposes the tablet be fooked. I really do hope I am wrong but if i am right then why is this flashing tool still available after so many screw ups.
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job. I've flashed many things over the years and never screwed one up so this is bit of a shock to the system, My first reaction to your reply was to reply don't be smart then my second was to go check tool again, then third was ah f*#k. 26 letters in the alphabet and sony had to call the next model an S too. I cant say i keep up with tablet technology so thought they same thing pre flash,I didnt expect my tablet to be replaced in market so quickly after i bought one. Oh well lesson learnt now the question is wtf can be done if anything. If i send in for repair do they spot this instantly and try hammering me for a heavy bill to fix. Its under guarantee but they do say software issue they wont touch it.
I did read a lot about these problems but only reference i can find was today on page 36 of the flasher tool post. I blame mondays and my obvious lack of cognitive skills on them.
dex9mm said:
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
Can it be fixed?
nkxtc said:
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job.
Click to expand...
Click to collapse
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
soilchemist said:
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
Click to expand...
Click to collapse
Now thats why i thought it was ok i read that site first too rather than here. Too much reading after the event not before. So who are these idiots at androidadvices.com? The advice below is from that site and is what got me to reset tablet. Now i'm even more annoyed at this.
Note: Just in a rare case if the device doesn’t boot up or show the home screen then long press the power button to turn off and then re follow the instructions.
nkxtc said:
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
Click to expand...
Click to collapse
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
stifilz said:
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Click to expand...
Click to collapse
nkxtc said:
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
Click to expand...
Click to collapse
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Here comes a rant
stifilz said:
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Click to expand...
Click to collapse
I did notice but i eternal optimist and sorta hoped they different files even though filesize gave it away plus I already had that file from your links in sig but wouldnt be first time a company names files the same but different regions. Factory reset did numerous times now.
Didnt realise could get adb from logo screen so got hopes up again when lo and behold there in device manager was MTP device. After couple hours messing with it and getting lots of errors saying no driver etc I figured out putting hardware id in different adb usb driver inf files (USB\VID_054C&PID_05B3&REV_0100) would give me a working driver or so I thought. The PC decided after few minutes to give yellow exclamation and driver no longer works. Persevered with it until got driver stable but from command prompt adb says no devices in list.
Now all this happened early hours since 3am so not having greatest amount of patience (4hours not bad) i took a huff turned everything off and said [email protected]#k it ive had enough. This aint ever gonna work im resigned to this fact.
Now i may have not read one tiny part of the AIO tool which turned out to be biggest mistake i made in all this however for anyone else unfortunate to have a blonde moment would it not be possible to put some sort of checker in the tool to determine what is actually attached to be flashed based on hardware ID or something before any system changes occur. Having flashed many many devices from phones to consoles each and every one has a check of some sort before hand.
However putting that aside I think its disgraceful how Sony have treated this tablet and how locked down it actually is. This pains me but the £300 wouldve been better on a damn ipad.
@stifilz appreciate help you tried to give mate
Ok so I've tried looking through these forums for several months in an attempt to find something that will get my kindle fire HD 7" out of it's boot loop that I put it in while trying to root. Turns out I skipped a step.. Anyways, so far I cant even get it to show up as a drive on my computer. It will show up in the device manager and I bought the factory fastboot cable so it will go to fastboot. However, I've tried using system restore programs such as kindle fire first aide and the SR tool. KFFA has been the most productive in the sense it will attempt to restore my kindle back to factory but fails to download the required files from drop box. It moves past all that saying no error and tells me to reboot my kindle, which then returns to looping at the Kindle icon. I'm seriously stumped here as no help program I've seen has been able to do anything so far. Amazon said the warranty ended a year ago and to buy a new one. Any help would be much appreciated and if you don't mind reply like I'm computer illiterate because this was my first attempt at rooting anything.
Thanks!
nakedamerica said:
Ok so I've tried looking through these forums for several months in an attempt to find something that will get my kindle fire HD 7" out of it's boot loop that I put it in while trying to root. Turns out I skipped a step.. Anyways, so far I cant even get it to show up as a drive on my computer. It will show up in the device manager and I bought the factory fastboot cable so it will go to fastboot. However, I've tried using system restore programs such as kindle fire first aide and the SR tool. KFFA has been the most productive in the sense it will attempt to restore my kindle back to factory but fails to download the required files from drop box. It moves past all that saying no error and tells me to reboot my kindle, which then returns to looping at the Kindle icon. I'm seriously stumped here as no help program I've seen has been able to do anything so far. Amazon said the warranty ended a year ago and to buy a new one. Any help would be much appreciated and if you don't mind reply like I'm computer illiterate because this was my first attempt at rooting anything.
Thanks!
Click to expand...
Click to collapse
Edit: Ok so I continued messing with KFFA and somehow got it to restore my kindle doing all the same things I had already tried. I guess you all can ignore this post lol...
lol
nakedamerica said:
Edit: Ok so I continued messing with KFFA and somehow got it to restore my kindle doing all the same things I had already tried. I guess you all can ignore this post lol...
Click to expand...
Click to collapse
We were anyway you are in the wrong forum .
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Asus Eee Pad Transformer Prime
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Eee Pad Transformer Prime Q&A, Help & Troubleshooting
Good luck!
Bump, could really use some help...
GiordyWarner said:
Bump, could really use some help...
Click to expand...
Click to collapse
There is only hope, if you can manage to get into bootloader screen by pressing power + vol down.
APX mode would only help you, if you had pulled your nvflash files.
GiordyWarner said:
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Click to expand...
Click to collapse
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
gsanglan said:
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
Click to expand...
Click to collapse
This has nothing to do with what he is asking.
flumpster said:
This has nothing to do with what he is asking.
Click to expand...
Click to collapse
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Jimboy00 said:
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Click to expand...
Click to collapse
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
flumpster said:
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
Click to expand...
Click to collapse
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Jimboy00 said:
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Click to expand...
Click to collapse
Unfortunately unless you have nvflash backups then you will have to get the board replaced. Forget contacting Asus as they would charge you more than the tablet is worth. Try and find one with a smashed screen on ebay etc cheap that still works that you can swap the board out from.
lemicp said:
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Click to expand...
Click to collapse
Thanks for your feedback,
So I don't have these files :crying:
I found also another thread with same story, and it seems that I can search for a new MoBo....
http://forum.xda-developers.com/showthread.php?t=2143942
...or buy a new tablet, maybe the better solution...
I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick
69Rixter said:
I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick
Click to expand...
Click to collapse
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.
ninjasinabag said:
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.
Click to expand...
Click to collapse
Re: ninjainabag
Thank You for responding and my apologies for not getting back to you sooner!. I'll answer in the order of your questions.
#1. Charging the phone via the comp/USB port. #2. Yes, and have been there. However the "recovery" menu on this phone only goes as far as "wiping cache", "wipe data/factory reset", "update from SD card" and "reboot now". Wiping cache and factory reset (3x) accomplished nothing! #3. Agreed, but never installed one (secondary stock recovery). 2 questions now... could I possibly D/l and install an O.S. from the SD card?, and/or use a "recovery" program from the computer through the phone?
Appreciate your response"
Rick
You're fine homey.
Your phones not, but you are. The Coolpad avail is the budget device for people who can't afford a budget device. So there's not much in the way of documentation for the 3300a.
In my personal opinion on the subject, you'd seriously just be better off picking up a new one.
-no recovery.
-no stock firmware available
-no support on the web (xda, AF, 4PD)
What service provider are you using? If you're looking to replace the phone. I can give a couple of suggestions that would help you make sure this doesn't happen again.