Related
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
Updated 05/08/11
ATTENTION - IF YOU ARE ON STOCK 4349+ or any MOD BASED OFF 4349+ USING THE NEW RECALLED BOOTLOADER! READ PLEASE!
Starting with the most recent but recalled update to Tap N Tap Viewsonic has introduced a new Bootloader being called the 1.2 bootloader. This bootloader is not compatible with mods or Roms based off of the Viewsonic Current Bootloader being called the 1.1 bootloader! This bootloader provides absolutely no known advantage other than being able to boot any new STOCK kernels. If you would like to use any of our stable ROM's (i.e. Vegan 5.1.1, Vegan GingerEdition and currently CM7) using Viewsonics currently supported and shipping bootloader (1.1) you must Downgrade your bootloader and TNT Version before you flash a new kernel or a new ROM.
Please download the following downgrade update.zip and place it on your sdcard renaming it to "update.zip".
http://www.gtabdevs.com/releases/4349_Downgrade.zip
Then power down your device. And power back up while holding the power button and vol + till your display says "recovery key detected" in the top left corner.
Using the volume keys to navigate up/down in the menu highlight "Apply Internal update.zip" if you copied the update.zip to the internal memory or "Apply External SDCard update.zip" if you happened to place it on an external SDCard and then inserted it before booting to recovery. Now select the menu choice using the menu key.
This process will take a few minutes. You will see a Box with an arrow and a progress bar while it applies the update.... when it is finished it will reboot to make the changes. Once the changes are complete your tablet will boot into Tap N Tap version 3588.
You are now free to follow all the tutorials about installing CWM and/or Kernels/Roms.
Thank you and good luck.
Be aware. I am not connected with Viewsonic in any way. I make no assertions as to the validity nor the safety of anything in this post. Do anything above at your risk.
That is a handy utility to have. Thanks!
How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!
Strange. One step forward and two steps back for Viewsonic. But, maybe, this means there is still some interest from Viewsonic for our tablet and chance for further development (maybe even Honeycomb).
roebeet said:
How do we check if the bootloader is locked? I'm curious if the bootloader.bin in 3991 (which is based off the same branch) has this same issue.
Thanks!
Click to expand...
Click to collapse
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source. EDIT: Already tweeted them. I see "1.1" in the source that's there, and we know that this is "1.2", so maybe there's new source code to be requested? Not sure.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!
gojimi said:
If it too will not boot any other kernel besides a stock kernel built specifically for their new bootloader. That bootloader.bin also appears to be locked.
Click to expand...
Click to collapse
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?
roebeet said:
Does that mean it's locked, or does that mean that we just don't have the new source code to build custom kernels? I just want to distiguish because, if it's the latter, we can just ask them to release that like they did the 1.1-based source.
I know that we can check for a locked bootloader with something like fastboot, but I don't think that works here. That's why I was asking.
Thanks again!
Click to expand...
Click to collapse
By all means ask for their new source... though I do not believe at this point they are required to give... maybe they are. So for the purposes of everyone else's understanding this is a LOCKED bootloader in the sense that we are LOCKED to their kernel...... nothing ever stays locked forever.... this is not however LOCKED in the terms that a select few who already know what's going on with this bootloader typically use the term LOCKED. Take it as you will.
snapz54 said:
what could the thinking possibly be to locking the bootloader on a product like ours?
I'm seriously asking, besides being dicks, what would the reasoning be?
Click to expand...
Click to collapse
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.
Does nv flash still works to downgrade everything?
gojimi said:
To be honest they are probably tired of all the people calling viewsonic support with issues that are not on OFFICIAL viewsonic software... most companies try to do something to deter this activity in some regards.
Click to expand...
Click to collapse
I understand this for "most companies" but Viewsonic is the company that openly linked on their product page that XDA is the place to be if you need support or any real use from your gtab.
We had to fight them to finally stop doing that. It doesn't really add up.
The only thing this does if it works is effectively pull the plug on the life support that was pumping any further life into the tablet.
We still have great "legacy" roms and infrastructure that make the tablet great. but moving forward all this does is concentrate our efforts towards them. releasing a workable open solution keeps us busy tinkering with it for months. Locking things down only sends us back to twitter and the like but now we have more members thanks to the new OD, TD, and amazon users.
I thought VS said they were going to work with the devs. Didnt they contact you guys? I thought they would of asked or told you guys what the best way for them to go would be. Did this never happen?
Pazzu510 said:
Does nv flash still works to downgrade everything?
Click to expand...
Click to collapse
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt
jasco13 said:
Yes, maybe. I had to NVflash mine because I accidentally flashed CWM over 4349 while i was playing in the 4349 recovery screen. The NVflash process worked, but for some reason my touch screen was borked (no touches were registered). Couldn't do anything. In the past a couple restarts with calibration.ini on the external SD would clear that for me, but didn't this time. I ended up doing NVflash with CWM as part9.img and then repartitioned with CMW and NVflashed again with stock recovery part9.img. Screen was still borked but cleared up with a couple restarts with calibration.ini on an external SD. So the answer is yes you can, but it may not be as smooth as you are used to. Of course it may work fine for you.
Matt
Click to expand...
Click to collapse
I've nvflashed back to 1105 at least a dozen times since last night (was doing upgrade / downgrade scenarios). So far, so good.
The bootloader is provided by viewsonic I think, it may be the key for some chipset feature, some other brand of tablet like the adam already has the same exact one
it's probably not locked but only doing something different like you said!
if I had to guess, they didn't lock it to be pricks...odds are it is locked to prevent people from flashing our current kernels to this to avoid messing things up...
so here's prolly how we'll be structuring our ROMs/Kernels now...1.1-based Froyo ROM; 1.2-based Froyo ROM; 1.1-based Froyo Kernel; 1.2-based Froyo Kernel and so on for GB if we're lucky HC in the future.
It's going to be a pain in the butt in the short-term, but long-term it'll only benefit current and future gTab owners as a whole if we stick to the 1.2 path alongside the vendor. This will keep confusion to a minimum, features to a maximum, and upgradability easy.
Thanks to all devs for their future support even through some of the PITA times
i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.
Edited...You can't fix stupid
iamnottypingthis said:
i have no options to choose between, aka no menu when i do all that, it just goes to a box picture and then reboots and loads normally.
Click to expand...
Click to collapse
There is no menu. It takes you back to 3588 and the ability to flash all current roms.
So this "rollback" is jsut a stock 3588 image, or is it something different?
Okay guys. I've searched and searched and found nothing, almost found something but wasn't definitive enough, and wasn't going to risk bricking my device.
Acer Iconia A500 Wifi Version
Current OS Version: HC 3.0.1
FLEX Version: 04_COM_GEN1
Kernel Version: 2.6.36.3
Build Number: ACER_A500_1.145.04_COM_GEN1
Now, notice I only bought this end of December-ish 2011 but this device has been out for quite some time. I don't know what is going on with Acer right now but this thing will not update through the system update no matter how many times I click on it. (tap on it you know what I mean)
Now, I wanted to do it manually, since I was able to do so on my Nexus S with ICS. But there are so many version out there and most of those forums say that if you don't use the correct region you'll brick your device.
Also, I searched my build number and only 1 person on 1 forum here on XDA Devs had the same build number and even then was only saying it to share. I cannot find anything regarding this build number, or what build to use to upgrade to 3.2.1, or all the way up to even if it takes multiple updates.
I know that Acer A500s are supposed to be getting ICS 4.0 sometime this month in Jan, but I'd like to be able to be updated to 3.2 at least while I'm here.
NOTE: I DO NOT WANT TO ROOT ANYTHING (That is not what she said)
Can someone take a look at my build number and current versions and what not, and please point me in a direction to get this thing upgrade to 3.2?
Thanks. A lot. In advanced. And stuff.
-B00mer
I'm actually facing the same problem too. Same build number, and no updates found. I checked Acer's website and say a document for updating to 3.2. The document mentions certain build numbers from different countries that are eligible for an update, and ours is not in the list. I wonder what Acer is up to?
Does it download the update?
mrtoken said:
Does it download the update?
Click to expand...
Click to collapse
It won't even see any of the updates. It just keeps saying "No Update: Your device is up to date."
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
mrtoken said:
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
Click to expand...
Click to collapse
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
b00mtastik said:
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
Click to expand...
Click to collapse
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
mrtoken said:
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
Click to expand...
Click to collapse
Would the update mean much to me since I am still on 3.0.1? I cant even get any of the other ones to even get to the latest update.
If I get a date for ICS, ill be sure to post it.
Just root it, then update. After that you can install a none rooted updated 3.2.1 stock rom
Hi b00mtastik,
I had the same problem with an iconia a couple of days ago. I tried different things and managed to fix it.
I'll try to give you step by step how to fix it (not sure if it will work for you).
I thought that the people from the shop i got the tablet played with it and put some custom rom and so i tried to get it to stock.
I used stuff from this thread.
1. You have to root your tablet - Click here
2. You have to install Clockwork Recovery.
- install from market "Acer Recovery"
- run it and give it root permission
- choose ClockworkMod Recovery rev1.3.4 by thor2002ro
- click Install Recovery Image
3. Download this. It is a backup made with clockworkmod. It will give you an android with version 1.139.02. In the zip is also a update.zip which will update your 1.139.02 to 1.139.05.
4. unzip it and put it on your external sd card (if you do not have one, find one, you need ~ 500 mb free)
5. put the files directly on sd card (e.g. update.zip goes to root, clockworkmod folder goes to root)
6. After that you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you get to the menu.
7. Navigate using volume keys and enter a menu using the power button.
8. Navigate to backup/restore and then full backup and full restore (might be a little different). You choose full restore and navigate to restore a backup made on 25.06.
9. Wait until it is done.
10. Reboot and wait for the tablet to boot.
11. Open Acer Recovery and choose to install Stock USA recovery image. install.
12. Again you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you see the update installing (An android robot).
13. After the update installs and the tablet boots check for updates.
This has worked for me. I did try other stuff but with no success.
I hope it was helpful for you and you can fix your device.
What you are most likely running into is ACER has not released an OTA for your region. What people are telling you might not be what you want. For example, if someone in the USA is telling you to flash or update, they are often referring to experiences that relate to the USA. NZ might have a different configuration, digital rights, contracts, language, etc etc that ACER just hasn't upgraded yet. Or might not ever upgrade.
If you are totally stock and have never rooted, then CALL ACER TECH SUPPORT and get the correct answer for you make and model for your country. If not, then following directions here might void your warranty. So, just give them a call and see what they tell you first. Then let us know what your find out.
TD
Of course you should first make sure there IS a higher version in your region. And rooting will void warranty.
Although as I spoke with Acer Support about the tablet mentioned in my post, they told me that 3.0.1 is the newest version, which is not true since I have two other a500 tablets both up to 3.2.
Just shared what did it for me.
Hope you can fix your problem the easy way.
Current for NZ is
3.2.1
Kernel version 2.6.36.3+
Build Acer_A500_7.014.15_Com_gen1
Is your current firmware stable? Is everything working OK?
New Zealand and Australia are typically the first countries to get the updates. But they are rolled out by google due to some number to do with your tablet. I'm in the south island and have had 3.2 for quite a while. When I brought my father an A500, it took about a week before the update was available for it. basically if you have any problems just go to the acer ANZ facebook fanpage, one of their acer people are always very good there with question. firmware is stable, and android 4 is meant to be released to NZ/Aussie shortly.
i forgot to mention before you get the big android updates there is a smaller update, i can't remember the size of it, but your tablet has to take that update before it will take the 3.1 or 3.2 update, cannot remember if you need 3.1 before 3.2
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
b00mtastik said:
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
Click to expand...
Click to collapse
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
timmyDean said:
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
Click to expand...
Click to collapse
The last thing I want to do is give it back to them and wait for about 2 weeks for the retail store to get their asses into gear and send it off, then wait another week for Acer to do fix things, which should just not have happened in the first place.
I've tried the idea you gave me mate. I took out the SD Card, and used an old phone that allowed me to access it as a Mass Storage Device because I didn't have a card reader, and formatted it both to FAT first then FAT32 and still no go. The tablet just cannot seem to be recognizing that it even has an External SD Card in it.
Its looking more and more like I'm going to HAVE to go in and get it sorted somehow. Thanks everyone for your input and help. I've also contacted Acer Support. Lets see what they have to say, which I will post here. I'll also fiercely be practicing my Google-Fu to see what else I can find.
-b00mer
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
mrtoken said:
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
Click to expand...
Click to collapse
Its kind of the only choice I have while I'm unable to do anything else.
Thanks mate, that'll be good to know. And yeah, I was thinking they removed it from their servers to get it ready, but I'm hoping they don't cut it out and stop it either like they did with Nexus S. I had to manually update that as well, but that worked seemlessly, while I was JUST getting drunk, during a party. You know something is good when you can do that.
I'm dreading letting it go away, but if they can load it up, I technically should be able to getting it loaded somehow as well?
-b00mer
Hello...
I've spent about a good week and a half trying to root and install ICS on the A500 at where I work. My goal is to get ICS or higher on this device so that it can be used for testing purposes. I was able to root and install CWM but have not been able to flash ICS or JB. Am hoping you guys can point me in the right direction.
I have tried to flash cm-10-20121027-UNOFFICIAL-a500.zip and cm-9-20121221-NIGHTLY-a500.zip but what I get in both cases is my device hanging on the Acer logo. My last attempt I left the device like that over the weekend and this morning it was still displaying the logo.
The CM9 nightly wouldn't install at first until I came across a post that said to remove the first line of the install script, which I did, and the install seemed to happen but as I mentioned the device hung up at the Acer logo.
No idea how to move forward here... there are hundreds of posts and updates on the topic but quite frankly there are terms that I've never heard of, all sorts of caveats, specific recoveries that need to be used, dead links, etc... am making no progress.
I do have a backup up of HC, so am able to revert easily via CWM.
Current Android is 3.2.1, build is Acer_A500_7.014.02_COM_GEN2
@eyepoker..... I honestly don't see where your problem is provided you are prepared to load a custom ICS rom from any of the Developers in thread #3. Without picking out a favorite I would suggest any of "Civatos" FLEXxxxx ..... SHELLshock..... roms will give you a highly customized ICS Rom.
Be aware that you will have to load first an ICS Bootloader..... you cannot run these custom roms on a HC Bootloader, but in "Civatos" posts there are links to tutorials on how to do this.
The issue is that i can't flash a rom, it doesn't work. The device hangs with the Acer logo displayed and advances no farther after a flash and reboot.
Should my take away be that the latest CM nightly and the unofficial don't work? Should i not bother with CM? Is ClockworkMod old now - is there something else I should be looking for?
I'll look at the bootloader stuff you mentioned.
@eyepoker..... With respect you know your tab better than I, however unless you have bricked it (you don't say it is nor does anything you say about it suggest that is the case) then there is no earthly reason why you cannot load a ICS rom onto it. Now I am not going to say that there is a problem with the NIGHTLY updates of CM roms but is it possible that an app that you have previously installed is causing a problem with CM?
To prove to yourself that your tab can run ICS why don't you try the following.....
1) Follow the instructions in Civato's thread to load an unlocked ICS Bootloader..... I would recommend "v.8"
2) Download one of his ShellShock or Flex roms and put the zip file onto your External SD card - DON'T unzip the file leave it in it's zipped state.
3) Boot into CWM Recovery - do the necessary "wipes"
4) From within CWM install the zip from your SD Card
I am quite certain that the rom will install.
If the above doesn't work then I think there is far more wrong with your tab than it being unable to flash a rom.
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Have you ever used Odin?
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Bicknasty said:
Have you ever used Odin?
Click to expand...
Click to collapse
Yessir Mr. Nasty,
I followed a guide on this part of the forum that had me use Odin. After using Odin successfully I was able to get TWRP up before normal boot!
vIgGeN7 said:
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Click to expand...
Click to collapse
Just to clarify, you're saying that if I boot into TWRP again and clear the cache/wipe, I'll go back to factory settings and get the OTA?
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Bicknasty said:
-snip-
Click to expand...
Click to collapse
Thank you for being so specific and clear, and for helping me out. I am new to this, used to working on computers that I can tear apart more easily and change things inside of.
I will keep this in mind and consider switching. I have a lot of free time with a 1GB/1GB
Futtermax said:
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Click to expand...
Click to collapse
I dont know what everyone is thinking, but OTA will not work with rooted device. It will failed and in most case you will nee to flash full stock rom to fix it, then your bootloader will locked again. The best bet is to wait until Samsung released the rom and Dev here will modified it the right way so you can flash with TWRP.
Sent from my SM-N920V using Tapatalk
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
JOSHSKORN said:
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
Click to expand...
Click to collapse
I think CM13 is worth giving a chance.
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Sent from my SM-N910V using Tapatalk
Bicknasty said:
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Click to expand...
Click to collapse
I might add to that storing a copy of that backup on another device... your desktop computer, perhaps, so that if something really goes bad and wipes your sd card, you still have a backup.
Do not, no matter how much your phone nags you to, take an OTA now that you're rooted. The odds are good that they've closed the exploit used to get root.
If you're looking for stability, Jasmine ROM is the best that I've tried. It's not being supported anymore, but it really doesn't need it. Everything works. I froze, then deleted every single Samsung and Google app that I don't use and it is just smooth.
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
joshw0000 said:
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Click to expand...
Click to collapse
Dual boot patcher has worked pretty reliably for me. Just be sure to thoroughly read the directions to make doubly sure that nothing goes wrong.
douger1957 said:
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
Click to expand...
Click to collapse
Bluetooth is flawless. I can't see why anyone would set their sd card as internal (defeats the point of being able to move info between other phones and/or computers). Camera works very well (for CM). I've had very few issues with taking pictures. Recording video doesn't work for me. I've modded every phone I've used (I've owned many that I wouldn't carry due to no root) since the Eris and this is IMO the best CM port ever.
Sent from my SM-N910V using Tapatalk
I am using PaulPizz 5.1.1 ROM and it's working almost flawlessly. I'm happier than ever with this phone. I want to wait for the OTA 6.0.1 to hit and the teardown of that to begin before I switch.
I'll look into dual boot.