Database Users

Help! My Acer Iconia A500 keep doing Endless Booting after i change the vmheap

I Experimental change the vmheap of my iconia from 256m into 36m that available in droid overclock application, and then it says it will be functioning after rebooting, and then it's just keep on booting and booting, the bootanimation keep restarting and restarting, i try to install the new cwm, and try to flash rom that i think can make my tablet works normal, but the problem is, after i press power + volume(-) button, it's just writed installing update.zip and rebooting, after that it's just rebooting again and again like nothing happens, pleasee, help me with this one, i beg you.

have you tried to hard reset it?

yeah reflash a your ROM and never do that agian, unsure of you were trying todo; though reads like you were trying to shrink your VM heap, may I ask why

BrianDigital said:
yeah reflash a your ROM and never do that agian, unsure of you were trying todo; though reads like you were trying to shrink your VM heap, may I ask why
Click to expand...
Click to collapse
what can i do to reflash my ROM?
hard reset : not working, just reset my boot animation to default but still endless booting
power + volume down : trying to install update.zip (thor cwm) but nothing happens, still endless booting and not come to recovery mode
i just thought to increase my performance without aware of this thing.

schythe said:
what can i do to reflash my ROM?
hard reset : not working, just reset my boot animation to default but still endless booting
power + volume down : trying to install update.zip (thor cwm) but nothing happens, still endless booting and not come to recovery mode
i just thought to increase my performance without aware of this thing.
Click to expand...
Click to collapse
can't be doing those phone things to tablets.
if you can get into APX mode, you can nvflash your bootloader and cwm recovery. You may also be able to run an EUU if you remembered to keep your UID number. This will be needed in both cases.
But a good way to start.

i've got into APX Mode, and now how to install Nvflash? Or how to use EUU?
I got in some thread that they say, it's the SBK that make us can't use the nvflash, can u help me, with the link to install nvflash at iconia tab a500?

Up, Please help, i've got into APX Mode and don't know what to do next, really, i search in entire google and don't know what to do

I've proven myself an expert at bricking a Kindle Fire

installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.

Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.

Let it charge, then just flash a new rom.

left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!

Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP

The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.

vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.

shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.

There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode

He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.

Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.

Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.

FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)

vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.

darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.

Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app

freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.

Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.

Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.

This entire thread is ridiculous.

A500 suddenly died

Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.

Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD

Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?

And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...

Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.

Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....

Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.

Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD

Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...

It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....

tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD

First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....

Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...

I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week

ACER A500 Iconia Tablet -- Stuck at Acer Logo...

Was using tablet and just playing a game -- tablet reset, robot with ! showed up.
After that, reboots bring me only to the Acer screen.
I can do the VOLUME UP + POWER -- vibrates, powers up, toggle the switch, let go of power button and it does:
ERASING USERDATA...
ERASING CACHE...
Then it reboots back to the ACER logo, and just sits there. I have downloaded one of the ROMs and done the VOLUME with POWER BUTTON start up and it doesn't do anything. Just stays at ACER logo.
I've looked at quite a few things here on the forums and it hasn't done me any good -- nothing seems to want to work with the tablet unless it's in debug mode (which means it has to be a working tab). When connected to a PC it does detect as an MTP USB DEVICE and says "THIS DEVICE IS WORKING PROPERLY." But I can't get much of anything. The only thing I've used that remotely works is USBDEVIEW which gives me the device info including a serial #, which I understand is NOT the cpuid. I do have the box, so I guess that would have the CPUID? Any help appreciate. More than willing to just blast this thing with a one touch factory reset from the PC, if it will just connect.

If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD

Moscow Desire said:
If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD
Click to expand...
Click to collapse
It went to the Dead Android guy when it rebooted after a crash. I haven't seen it since. Just got to the Acer logo screen and stops.
Your linked post is going to what it actually shows instead of the real link.

Fastboot
Sent from my Kindle Fire using xda app-developers app

Vintage144 said:
Fastboot
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Don't think he has V8 bootloader Mate.

Moscow Desire said:
If you had it at the dead android guy, it means you probably didn't have the decrypted "update.zip" on your Ext SD card. If you had stock ICS running before, you can try downloading those 4 update.zips I posted a few threads ago. Will have to try each one, and hopefully one of them works.
Here's the post...
http://forum.xda-developers.com/show...54&postcount=2
This would be the first thing I try.
MD
Click to expand...
Click to collapse
I'm also stuck at the ACER logo. I d/l'd all four of the zips from your link. All four appear to install correctly but when the flash finishes and the tablet reboots, it's still stuck at the logo.
Also, when I just tried the link again, it is no longer working.

where were you coming from when you tried this ? what BL? gb?JB? what recovery , theres a alot of reading to be done with this device Acer didnt make it easy , but if you read and take it slow there are/were some great devs that left the door open for us all to use these ? Explain where your started from and how you got to where you are now? (Moscow is a sharp dude he can help)!

Vintage144 said:
where were you coming from when you tried this ? what BL? gb?JB? what recovery , theres a alot of reading to be done with this device Acer didnt make it easy , but if you read and take it slow there are/were some great devs that left the door open for us all to use these ? Explain where your started from and how you got to where you are now? (Moscow is a sharp dude he can help)!
Click to expand...
Click to collapse
I bought the tablet used and it would loop on the green "ANDROID" screen. So I don't know what version it was on. I tried the volume +, rotation left and power on to clear the cache and user data. After that it hangs at the ACER screen. I'm assuming it had HC because it has standard recovery. IOW, if I hold the volume - when powering on, it goes to the green Android logo and if an "update.zip" file is present, it will flash it. I've tried just about every "full" ROM I can find and most of them flash but none of them get past "ACER".
I've tried pushing the reset button while powering on while connected to both a Linux box running Mint 15 and a Win7 box. The Win7 box see the tab but won't load the driver. Even though I d/l'd the USB driver from the Acer site. Mint 15 sees the tab but comes up with the error box saying it can't be mounted.

[Q] Cannot get CyanogenMod v0.9 to install - can't get CWM to reboot into recovery

ThinkPad Tablet A400
Android v. 4.0.3
Have an app that needs to run on Android 4.1 and quickly found out this 2 year old device was pretty much left unsupported since about 3 months after I bought it in May of 2012. So, I located the links to xda-developers and dove into the install process.
Got the device to Root following install directions etc.
Cannot get the device to reboot into recovery mode from ROM Manager nor via ROM Installer.
Tried installing the CyanogenMod v0.9 anyway from inside either aforementioned utility (from the .zip file), just reboots back to the normal state.
I'd pay to download & install Android 4.1 on this device, seriously...just lost 6 hours of time attempting to do this ROM upgrade.
any suggestions?

First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.

pwstein said:
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
Click to expand...
Click to collapse
I've tried various combinations of that Vol button....still stubbornly refuses to go to CWM.
Now, I am running Android 4.0.3..perhaps that is the issue, ie. perhaps the CWM image file was intended to be used on TPTs running Android 3.x.
It'd be nice to go to a site and buy a $50 OS load....

Well....wonders never cease. I happened across a post talking about the TECHNIQUE to reboot the TPT into CWM...so, sure enough...I got the puppy into CWM.
HERE 'tis for the rest of us nuves out there:
Entering/Booting CWM Recovery on the Thinkpad Tablet
Shut down your Thinkpad Tablet
Press the power button until the Tablet vibrates
Keep pressing and releasing the volume up button until you see Booting Recovery Kernel Image in the upper left corner. It's all about timing of when the volume up button is pressed. That's why it's a good idea to just keep on pressing and releasing the button until the message appears.

Well i continued on with the Jelly Bean load from the xda-developers...and after reboot to ver 0.92 the tpt seemed to freeze on the os boot screen.
So, i fell back to the 4.0.3 os and will read-up on what can freeze the reboot into 4.1 android.
CWM is a cool program..gotta say it.

Can't get it to install CWM
Tried numerous times but now I have lost my original recovery and it just loops,
Changed permissions but won't go and when I am in the recovery boot after pushing the volume button it just reboots as there is nothing there suggestions?

Honestly, the best thing you could do is get something newer/better supported. I hate saying that, because I bought the 64gb version right around the same time you did. The tablet had so much potential with the pen, USB, sd slot, and even pci-e, but it suffered from non-existant Lenovo support, and very little dev support. Koshu's work on it was amazing, but without trim I feel like I have to constantly wipe and start fresh to do anything with it. Clearing dalvik from time to time helps, but not as much.