Related
Hi everyone, I'm a new member to the forum, but have been a follower for quite some time.
Let's start by introducing my device wich is:
EEEPad Transformer TF101G with ICS running the latest WW_9.2.2.6 firmware.
The device is rooted and running ASUS stock recovery.
Everything was working fine until I decided to do a Cold Boot.
It got stuck on the cold boot menu for like 3 hours and I decided to turn it off.
After that it got stuck on the inicial Asus splash screen. I forced it to turn off a couple a times and it eventually booted up.
I knew something wasn't right, so I backed up all my files and applications.
Then decided to do a factory reset through POWER + VOL-
After that it never booted again, and after a few seconds on the splash screen I hear a click noise, like the hard drive is turning off.
When I try force it to turn off, it starts up again automatically.
I've tried to flash it through nvflash, but being a TF101G it also means it is sbkv3, wich is not supported by nvflash.
Also tried boot recovery tools, but it won't even start, because as I try to connect it to the computer through adb mode, after that "click" noise, the device becomes disconnected.
I didn't try any dangerous applications and stuff like that, just decided to do a simple cold boot, the device is a week old.
If I'm posting this in the wrong section I apologize.
And hope someone can come up with a good idea.
Thanks in advance.
Obviously somethings corrupted and in my opinion the only way to fix it would be to reflash the rom in apx mode using nvflash but that doesn't seem to be possible for your device as of yet but if everything is still stock maybe you can unroot the device (or play dumb) and get it replaced under warranty?
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Akusura said:
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Click to expand...
Click to collapse
Eek.. since it was factory resetted I think you need to send it to warranty. Not much we can do now with just a splash screen on sbkv3
I don't consider myself an advanced user.
But I really did search everywhere and I got the idea that only with APX and without a compatible NVFlash I was screwed.
But I still had some hope.
Do you think they will give me trouble because of it being rooted?
I my opinion I don't think they will ever know, because It won't boot, It won't run recovery mode (stock) and nothing else at all, the only way to fix it is to flash it, but maybe I'm just being naive.
I treated it with all the care in the world, so only by divine intervention it is a hardware problem.
But you never now...
you should be ok (should)......
i done pretty much the same thing to a customers TF and Asus fixed it no problem.
The fact is that I actually didn't do anything wrong.
Just a cold boot that didn't work, followed by a a factory reset...
How long did it take for yours to get fixed?
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Vuciz said:
Hello. I have an Acer Iconia Tab A200, and recently I tried a factory reset. However, due to my meddling with system files, it won't reset.
I've tried to do a hard reset (Power on, Volume+, Orientation lock switch) but it says the following:
Erasing Userdata...
Erasing Cache...
It then reboots, and does nothing. It hangs on the Acer logo.
When trying to go into recovery (Power On, Volume-), it says the following:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified fail ...
Now, I mentioned that I meddled with the System Files. Here is what I did:
1. Removed unwanted Vendor Apps
2. Removed the DEFAULT LAUNCHER <-- I think this plays a big part in this
3. Placed a CUSTOM LAUNCHER in the VENDOR APPS FILE
4. Did a FACTORY RESET
My brother is more techy than me, so he tried to fix it. However, he somehow re-locked the bootloader and even replaced the bootloader with a newer version.
I talked to Acer Support claiming it's system files corrupted itself, but they won't fix it unless I also pay to fix my cracked screen. I'm willing to do so, but hey, I'd like to see if I could save $120. I don't mind the cracked screen.
NOTES:
The Acer Iconia Tab A200, along with their other tablets, has a USB port. I can probably load stuff from there somehow, but not sure.
It is a 16GB model with a 32GB Class 10 MicroSD card in it.
Any ideas? All help is appreciated.
Click to expand...
Click to collapse
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Moscow Desire said:
Do you have access to any a200 Update roms? Sometimes, you can pull the update.zip from the rom, place it on your ext sd card, reboot holding Vol+ and PWR, and it might install.
MD
Click to expand...
Click to collapse
I have searched for some A200 ROMs, but can't find any that work using that method. I'm open for ANY Acer A200 official ROM, then simply updating using OTA. I tried an Acer A200 Recovery Pack I found. It is the exact stock Honeycomb image, but it didn't go. It always says recovery verified fail. I cannot unlock the BootLoader either.
Stockimage flashable while having bricked /DATA Partition
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Nickbert said:
Hi Vuciz,
do you still have the issue with your bricked A200 ?
I got the same problem with mine, the only solution was to send it to repair, it seems the storage controller chip has some bug which destroyed the /DATA partition unrecoverable.
if you need to revert your Tablet to an locked bootloader you have to download an StockRom and modify it by removing the partition check (called "assert") in the update script.
please send me an message if you need further assistance.
regards and good luck with your tab.
Click to expand...
Click to collapse
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
anything I do, fails
Vuciz said:
Yes I do. However the screen is also cracked so they want me to pay for that. Which I'm unable to do at this time.
Click to expand...
Click to collapse
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
twanhines said:
I also have this tablet. I bought it for 20 bucks because the screen was cracked. replaced the screen and then found out that the bootloader was trashed. I've done almost everything I can think of to fix it. Used APX mode to get UID from ubuntu, tried to use that UID to get sbk, got the SBK and then tried using blackthunder's tool got connection failure, tried using babsector same thing, even went in ubuntu, with tablet in manual apx mode for all three and when I attempt to reflash the bootloader, all I get is that command failure message with a nvflash connection failed nv error 0x30011 message and when that happens in windows, the tablet disappears from device manager, and in ubuntu when I run nvflash with the sbk function --sbk XXXX and so on, I get the command sent failure message, and then when i rerun lsusb, the nvidia device that represents my tablet in apx mode that showed before is no longer listed unless i reboot the tablet in apx mode again. If i boot it normally, the acer logo appears and then goes to the little animation and then the iconia tab screen and thats it. I've tried attempting to flash the bootloader from that screen which i know probably wasn't going to work anyways. If anyone has any advice on something I've missed, or anything that could help, i'll all eyes. thanks in advance.
Click to expand...
Click to collapse
Just so you know, I was never able to resolve this issue.
Hello,
I search help for my Acer Iconia Tab A200.
During a flash with TWRP, it block and I have to set my A200 off using Power.
And then, my A200 don't work, don't vibrate.
I try :
Reset + Power : nothing, no vibration
Power + Vol- : nothing, no vibration
Power + Vol+ + switch : same result
Connected to PC : adb devices : nothing
All commands adb or fastboot : waiting for device
I don't know what to do...
where can I send my Acer tablet to fixed stuck on bootloader
hello I have an acer iconia 200 stuck bootloader cant find anyone to fix it. Acer wont touch it unless its under warrenty! my 90 day store warrenty has been way past! taken to 2 local computer tech both told me I needed to send it back to acer but I cant! so what can ido i or where can I send it?? anyones time and effort would greatly appreicated!!! thanx for your time
Hi guys,
Original post was made on the AcerTabletForums, but I'd like to post it here too.
I kind of bricked my device, and I was hoping any of you might have useful input.
What did I do?
- I installed the CWN JB 4.1.1 found on this forum. Everything worked ok.
- I found the CWN JB 4.1.2 ROM on this forum, and decided to install that.
- Booted into recovery, wiped the cache partition -> ok
- Tried to wipe the data partition -> NOT ok, the system froze
- Could not boot anymore into the normal system, so rebooted again into recovery.
- Tried to install the CWN JB 4.1.2 ROM, to get back to a normal system -> NOT ok, the system froze again
And now, my A200 isn't doing anything anymore. I just get a black screen. The light on the button is on, but that's about it. All the key combinations to get it into recovery aren't working, it's simply black.
Is there a way to hack my way into the device without it booting? I guess I just have to build the file system again, but I can't manipulate the system if it's not booting ...
So far, I can only see my device popping up as "APX" in Windows. I can also see it in Linux when I probe it. That's good, right? The thing is still alive. However, I can't do any more than that ADB does not see it, so FastBoot doesn't see it either ...
Is there any way to do a low level flash of the device?
BTW: it is rooted, so I won't be able to send it to Acer. *sigh*
your device is still alive sort of... look around th thread there is some guide to revive it
calvin_ng said:
your device is still alive sort of... look around th thread there is some guide to revive it
Click to expand...
Click to collapse
You are in APX mode, which means, basically, you can only flash via NVFlash. This really is only useful for flashing bootloader files more or less. In some cases you can flash recovery image files , but probably not in your case, Unless you have the SBK (secured bootloader key), you're pretty much in a dire shape.
You can try installing an A200 stock update.zip from your ext sd. By holding vol+ and PWR. However, you may not get that far. Your recovery may be cooked as well.
I wouldn't worry too much about Acer Repair. Seeings they can't boot the tab to see what's on it, more than likely they will just change the mainboard and write it off as a bad chipset. They may try to run a service rom, which uses NVFlash, but the end result will be a clean tab anyhow.
Considering a percentage of tabs that take OTA result in APX or bootloop, I suspect there won't be an issue.
Hi there,
Sorry to hijack but I have a similar problem and I'm hoping someone can help.
I have a stock as a rock unrooted A200. I think my son let the battery drain and I haven't been able to turn it on ever since. I've kept the charger on overnight but I only get a black screen no matter what key combinations I use. The hard reset must have worked (even though I couldn't see anything) because my Win7 machine recognises the tablet and all my data is gone.
Is there a way I can revive it using the PC? I bought it cheap so it's not worth fixing but I kinda like it and it would be good for the kids to muck around on.
Thanks in advance.
Moscow Desire said:
You are in APX mode, which means, basically, you can only flash via NVFlash. This really is only useful for flashing bootloader files more or less. In some cases you can flash recovery image files , but probably not in your case, Unless you have the SBK (secured bootloader key), you're pretty much in a dire shape.
You can try installing an A200 stock update.zip from your ext sd. By holding vol+ and PWR. However, you may not get that far. Your recovery may be cooked as well.
I wouldn't worry too much about Acer Repair. Seeings they can't boot the tab to see what's on it, more than likely they will just change the mainboard and write it off as a bad chipset. They may try to run a service rom, which uses NVFlash, but the end result will be a clean tab anyhow.
Considering a percentage of tabs that take OTA result in APX or bootloop, I suspect there won't be an issue.
Click to expand...
Click to collapse
Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!
CakeWithoutEggs said:
Greetings members of XDA! I'm new to posting here, although I drop in here sometimes to look at ROMs.
Recently, after having the contacts under my screen cleaned (due to a ghost input problem which doesn't seem to be related to this, the cleaning didn't really fix the ghost inputs anyway), I factory reset my Galaxy S5 through the regular backup/reset settings. However, part of the way through the reset, my phone shut off. I don't know whether the battery lost contact for a split second, or if it just crashed, but it started booting again straight away - except this time it booted into the recovery of its own accord, without me holding down any other buttons. The recovery (TWRP) just bootloops, and the "TeamWin" screen just flashes constantly. Removing the battery is now the only way to turn the phone off, and whenever I turn it on or charge it, it boots into the recovery and the recovery just bootloops. Although the regular ROM is not accessible (it just goes to the recovery), Download Mode can be accessed normally.
I had a look at my catlog (thankfully I had USB debugging enabled before this fiasco), but it only offered me this after starting the daemon:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
I also used ADB to pull /tmp/recovery.log, here's the pastebin code: U89RQTkZ (I can't post the link itself, but this is the code for it after pastebin's URL)
The pastebin above is just one repeat of the attempt to boot inside the bootloop - the log itself is comprised of many subsequent attempts to boot, with identical results in the log. (I know the log says the date is 2014, that's probably because I had aeroplane mode on before I did the reset.)
So, can anyone help me fix this? I am inclined to try reflashing my recovery (TWRP again since my most recent nandroid backup is in that format), but I want to know if anyone here has a better idea before I start doing potentially irreversible damage to my phone.
Thanks in advance!
Click to expand...
Click to collapse
Flashing your recovery won't damage your phone in anyways. The best method I can recommend is to flash your phone's stock rom using odin. Usually flashing stock is helpful after soft breaks and bootloops. Flash stock and then you can install twrp and restore your backups. And about those ghost inputs. Sometimes with phone being charged with a non-standard cable those ghost inputs will happen. And if your phone gets wet this issue will show up. Try using another charger and cable and see if they happen again or not.
So per the Lenovo forums and this thread
https://forums.lenovo.com/t5/Androi...-x50f-dec-2016-update-fail/m-p/3530569#M14960
I flashed the firmware suggested in that thread. It was from a Russian site and I was hesitant. and I did it anyhow.
Now I have a brick.
If I can get the tablet in perfect lighting I can kind of sorta make out the boot logo. If I try to boot into recovery I can't see anything. I think the only reason I can see the boot logo in some lighting is that its light colored. I can't even tell if I can boot it into recovery.
I even tried to let it boot normally by itself. I got to a bunch of start up screens and they were all in russian. I could kind of fudge my way though touching where I could make out the outline of buttons (next, continue etc - even if I couldn't read them). Alas I bet it got to set up wifi and of course I can't see enough to set that up. I was hoping to get to setting to somehow fix the resolution.
Anyone have any suggestions? I know if I can get it into recovery I can either reset to factory, or flash again.
I've had soft bricks before. So I know if I can just get to that recovery menu I'll be okay. I just have to get there.