So I got this Tablet a few days ago and wanted to get root. It came with the 3.2 update already installed so I read around and saw I needed to downgrade the os, root, flash recovery, then flash a rom via recovery.
I plan to install this rom:
http://forum.xda-developers.com/showthread.php?t=1290318
It is basically stock acer 3.2 with root. Which is all I really want.
I followed method 2 here:
http://forum.xda-developers.com/showthread.php?t=1276227
After booting and installing the unstable version to be able to get root, then I did the adb push for cwm and itsmagic. Wasn't sure what to do after this so I rebooted. (I tried downloading the acer recovery installer but my market would not let me type anything in with all the force closes)
So after reboot I am unable to get adb to show it as a listed device and everytime I try to copy the rom over I need I get an error "Cannot copy *filename* The device has either stopped responding or has been disconnected"
In frustration I figured I didn't get cwm installed properly so I downloaded the apk from the web and installed it via dropbox. It let me apply it and actually boot into recovery.
I powered off and tried getting back in but my pc still fails to see the device listed in adb or save files to it via the basic windows file explorer.
I'm currently letting the update install itself (I flashed back the original recovery via acer recovery installer) don't know if this will fix it.
If anyone can help, it would be much appreciated.
Update:
It upgraded me to 3.1 but I still can't save anything to my tab (atleast the fc's are gone). It doesn't list anything on my tab just shows 0 files. Not sure how to get this fixed.
Update:
I did a factory reset. Now it detects it and I'm able to save the rom to it. I did the root, and flashed cwm thru acer recovery installer. (avoiding adb entirely). However when I'm in there now it says "E:Can’t mount /sdcard". Read some folks are throwing it on a usb drive and flashing it that way.(BTW I put the rom zip on the root file directory, not on the external SD). Will update if it works or not.
*RESOLVED*
Got it working. It installed off the USB thumb drive just fine. Was able to install the 3.2 root Rom mentioned earlier. Everything is working as it should. Able to read and write to and from the device now. Showing superuser in my apps. Now to start removing the crap Acer put on there
This is just in case anyone runs into the same problem. Took a few hrs but its working nice
Basically I suggest this if you wish to just install the the 3.2 stock rom via cwm
1.) Since the unstable flash doesn't clear your data, download and install everything you will need first. ex: Acer Recovery Installer, Iconia Root. Put the rom on the root drive and/or a thumb drive.
2) Flash the downgrade.
3) Run the Iconia Root tool.
4) Run the Acer recovery installer (since you'll have root now) and reboot to recovery
5) Flash the rom. If it doesn't detect it try it on a usb thumb drive. Done
I always put my ROMS on an external microSD. That is the only thing I use my SD card for, and as far as I can tell is always the recommended place to store your ROMS for updating. In the root of the microSD card.
Glad to hear you got it working though.
I'm not allowed to post in the Development forum, so I will ask my question here:
I updated to ICS successfully by changing the update-script in the update.zip.
I removed the lines which delete the recovery or reinstall it; I deleted the whole recovery folder as well.
But now I can't get back into CWM, it just doesn't start, it stops during "booting into recovery kernel" ( it was not overwritten).
So, is the ICS update changing so much in the system that CWM stops working? (through google I found something about different kernels, but didn't understand it)
I think I'll try to install the original recovery, better than nothing.
(this may also be a warning to people who think that they can roll back to honeycomb with CMW - apparently, once the update was succesfull that's it with honycomb)
daniel
I think it might have to do with the updated bootloader that comes with the ICS OTA.
I just had a look at the "blob"-file in the update.zip and was able to unpack it with the BlobTools for the Asus Transformer (https://github.com/AndroidRoot/BlobTools). Inside it was an EBT-file, which, according to my research, should be an image for the bootloader.
Looking through the strings in the blob, it seems to be one indeed: "Bootloader Start at:%d ms".
So I guess the new bootloader loads the recovery system from a different address or partition than the HC bootloader, which is why CWM won't start.
So adding the lines for flashing the OTA recovery-from-boot.p to the updater-script and re-running the update over HC should theoretically solve the issue. Or, if that doesn't work, flash the recovery image manually and flash the blob via nvflash (I'm not sure, though, if that is possible without the keys).
Maybe then someone with enough reverse-engineering skills could determine what has changed in the update and patch CWM accordingly...
Similar Issue..
In CWM, from [ROM][JB] CM10 for Ideapad K1 [Updated 8/29] (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Any thoughts?
It will work again. Just find the file "k1recovery" from the system/bin folder of a rom that has it. Push it in the device, fix permissions and execute it using ADB. The combination Power Btn & VOL+ doesn't work on some devices.
Hello,
I have an A500 with 8GB, bought in USA nov 2011.
it is currently running Thor/TegraOwners ICS ROM v164 (with CWM recovery)
my back-facing camera stopped working and I would like to go back to stock to send the tablet in for repairs.
I got the full stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1113878 (Acer_A500_0.000.00_4.010.10_COM_GEN2_1310535068614_9b84abb1)
unfortunately, I'm not having much luck flashing this :| ... I decrypted the zip and extract the update.zip and put it on the sdcard.
-tried applying update.zip through CWM ... no luck (it extracts but nothing happens)
-tried installing stock recovery using 'acer recovery installer' ... no luck (i get the android with exclamation mark when i try to go into recovery)
acer recovery installer shows bootloader version 3.01
any ideas ?
thanks
Fadius said:
Hello,
I have an A500 with 8GB, bought in USA nov 2011.
it is currently running Thor/TegraOwners ICS ROM v164 (with CWM recovery)
my back-facing camera stopped working and I would like to go back to stock to send the tablet in for repairs.
I got the full stock firmware from here: http://forum.xda-developers.com/showthread.php?t=1113878 (Acer_A500_0.000.00_4.010.10_COM_GEN2_1310535068614_9b84abb1)
unfortunately, I'm not having much luck flashing this :| ... I decrypted the zip and extract the update.zip and put it on the sdcard.
-tried applying update.zip through CWM ... no luck (it extracts but nothing happens)
-tried installing stock recovery using 'acer recovery installer' ... no luck (i get the android with exclamation mark when i try to go into recovery)
acer recovery installer shows bootloader version 3.01
any ideas ?
thanks
Click to expand...
Click to collapse
First off, get your UID number just in case you need it. You can get it in the Dev forum (sticky). Always have your UID written down somewhere.
Then go to the "all files" Sticky thread in the Dev forum. Where they have all the Acer roms and updates.
Download 2 or 3 of the a500 ICS Update files. These are full update files.
Decrypt them if needed, then pull the update.zip out. Copy to EXT SD Card, and boot holding Vol+ and PWR till you see the text about installing, then release.
Might have to try more than one, but eventually one should install. These are full update roms, not patches.
Should give you a stock ICS. Hey, check your camera, might start working again
MD
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
onyxkhan said:
My Tegra Note 7 came with Android 4.2. I unlocked, rooted, and installed CWM via the instructional videos over at rootjunky.com. Then through CWM I installed De-Odexed Stock Rooted 4.3plus from this thread: http://forum.xda-developers.com/showthread.php?t=2627671
Once the install finished and I rebooted the device (the reboot took maybe 30-45 seconds) I came to the setup "Welcome" screen. It is here that the Tegra Note froze. I thought it may be because it takes upwards of ten minutes for the first boot to complete/install but 30 minutes later the screen is still frozen.
When I do a hard reboot a few times I'm able to make it through the welcome and setup screens and the device appears to work just fine. I'll be able to install apps, run the stylus software, etc but then every 5 or 6 minutes (maybe shorter, maybe longer) the device freezes again and I must do another hard reboot. This happens repeatedly. And I still can't use the device for more than a few minutes.
Any ideas/suggestions?
Click to expand...
Click to collapse
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Fixed
RimanX said:
I am having the same issue my Tegra Note keeps freezing after flashing either update, I only did this because the ota update was not hitting but now the tablet is unusable
Click to expand...
Click to collapse
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
RimanX said:
I was able to finally fix mine and stop the freezing and locking up. What I had to eventually do was reflash the stock 4.2.2 image, reflash the stock recovery and then update as usual OTA and now I have an updated EVGA TN7 fully functional. Thankfully this forum helped a lot by having the resources needed to fix the issue.
Click to expand...
Click to collapse
How did you flash the 4.2.2 image and the stock recovery?
Freeje said:
How did you flash the 4.2.2 image and the stock recovery?
Click to expand...
Click to collapse
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
RimanX said:
Have to get into the bootloader which for some reason mine is still just a blank black screen even though it says it's unlocked. I used a program called Quick Boot which is mentioned in one of the tut videos, it took a while because of the freezing but once I had it installed I used it to boot back into recovery and bootloader. I did this because the method of holding down power and vol up was not working.
I also noticed that as long as you are moving the screen around with your finger on any screen it would not lock up. I used this to transfer the stock image and recovery over from my computer using the usb.
Once in bootloader you use fastboot to flash. ex. fastboot flash recovery stock_recovery.img from the windows cmd prompt.
I had CWM recovery flashed when this first started so I used Quick Boot to go into recovery to flash the stock 4.2.2 image first to even see if it would help the freezing and once it did I went back and did the above to flash stock recovery so I could let the tablet update using OTA updates.
Click to expand...
Click to collapse
From where did you get the 4.2.2 image that you can flash from stock recovery? I have a problem of getting the 4.3+ installed since I flashed the CWM recovery. I tried flashing a stock recovery but failed every time. My question is, would flashing an earlier ROM such 4.2.2 enable me to get the 4.3+ update or do I still have to flash a stock recovery?
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
4.3/4.4 crash. I fixed mine finally! 4.4 working great, no crashing!
astuermer said:
Got the same error after flashing 4.3 or 4.4.2 manually (since OTA halts with an error).
How to get rid of it?
Thanks!
Click to expand...
Click to collapse
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
4.4.2 Freezing- FIXED!
TerryRed said:
I had the exact same problem as you... I finally got it working, up to date with 4.4 CWM recovery, rooted and sd card fix. All working great... but here's some history...
I had the same bootloader that never worked from Power on/Vol Up, but would work after an adb reboot into fastboot. (blank screen only)
I was on stock 4.2.2, then unlocked bootloader, then updated to 4.4 using Supertool 2.2, Root, Sd card fix, but stock recovery still. All installed fine, but I had the crashing problem. Factory reset, and reinstall.. didn't solve the problem.
So I went back to 4.2.2 using the "temp" cwm recovery (using the root option to get in the cwm recovery, but I flashed the 4.2.2 file from root junky web page instead of rooting)
So here I was at 4.2.2 stock (from rootjunky web site), and stock recovery. Still not bootloader screen from Power.Vol up.
4.3 OTA would not work (dead droid with red triangle,error),
So I used supertool 1.5, installed CWM recovery, then I installed 4.3. It worked and rooted automatically, but I still got the crashing, and no bootloader by Power/VolUP. 4.4 OTA wouldn't work even when I put stock recovery back.
Here's where I got it to work from 4.3 stock (with crashing still happening, blank bootloader):
So now I used Supertool 2.2 to flash its version of CWM recovery (I had to keep touching the screen to keep it from crashing until CWM was installed and rebooted).
I did NOT use Supertool 2.2 to flash 4.4 as it contains the OTA 2.1 with it!!! (We don't want that yet! You'll se why below) I copied the 4.4 file at rootjunky: "Stock-4.4.2-TegraNote7.zip, February 22nd 2014 460 MB" onto the internal sd card (NOT the external sd card)
I used adb commands to reboot tablet into cwm recovery (had to keep touching screen until it rebooted into recovery so it wouldn't crash). Then I flashed the above 4.4 file. Install went fine. Of course I I still had crashing with 4.4 stock again. However, I noticed that the OTA 2.1 update appeared! I tried to update, but of course it wouldn't with CWM installed. So I reflashed recovery back to stock using supertool 2.2
Guess what happened next? The OTA 2.1 downloaded, flashed and worked! This was the first time I was ever able to get ANY OTA update to work! The key was to flash a stock 4.4 that didn't contain the OTA 2.1, and have stock recovery (from supertool 2.2) first in order to allow the OTA 2.1 to install!
Guess what works now? 4.4 works with NO CRASHING! and my bootloader finally works by holding Vol Up and Power ON and fully function menus,etc..!!! The tablet runs beautiful! The 4.4 had no root, or sd card fix applied, and stock recovery, but it DID lock the bootloader!
So now I used supertool 2.2 to unlock the bootloader (which I could now do because my bootloader had working menus, and could be accessed by Power/Vol Up). Keep in mind that this does a factory reset and wipes user data. (I had not wiped ANY user data right from 4.3 up until now!)
After the bootloader unlock/factory reset, I then used supertool 2.2 to: install CWM recovery, install root, install sd card fix.
Now I have an EVGA Tegra Note 7 with a fully functional bootloader, 4.4 Kit Kat, CWM recovery, root, sd card fix. All running great with NO crashing!
This is what worked for me... proceed with caution and know what your are doing first. Good luck!
Click to expand...
Click to collapse
@TerryRed:
You saved my bacon! I was having a similar issue with a totally borked root attempt... I was frustrated with repeated attempts to recover from the freezing issue. I followed your instructions and recovered the Tegra. Like you, I discovered that if I continually the device active by tapping and moving the screen, I could use the device. My idle limit was about 5 seconds, though.
In a nut shell, and while pretending to be a poor excuse for DJ 'scratching' (or do they call them 'controllerists' now?) I:
* Made sure ADB Debugging was enabled
* Copied the 'Stock-4.4.2-TegraNote7.zip' archive to the device's internal storage
* Ran SuperTool 2.2 and ONLY flashed the stock recovery
* Rebooted
[Resume silly DJ motions, while frantically setting up WIFI]
* Checked for, and downloaded the OTA update manually [OTA FOUND!!!]
* Waited the agonizing 10 second countdown for the device to initialize the installation
* Let Android do it's thing
!! SUCCESS !!
Thank you, and all of the guys here at XDA who donate their time, talent, and valuable info that help us mere muggles free our devices and take them to new heights.
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Bricked as well
OrangeCalculator said:
I bricked my while trying to get back to 4.3 and I really hope that this will still help me after all I've already done. Wish me luck(
Click to expand...
Click to collapse
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
NVflash unbricked
jardam.cz said:
So yours bricked as well???
I had the same problems:
- Bootloader not working as expected (only black screen).
- After CWM and flashed 4.3 constantly freezing.
- OTA not working (it said something like "This is not Tegra Note, it is Tegra Tab")
So being desperate I flashed a deodex 4.3 from RootJunky's web.
Since then tablet in boot-loop and still no way to get into Recovery.
I can only access APX mode, but I am not sure, how to use it.
Any help appreciated.
Jaro
Click to expand...
Click to collapse
So, to fix the boot loop it is as simple as it can be. I can't believe I didn't find that earlier. (BTW I didn't find a clear answer in the forum until today, thanks to hacktrix2006)
Just download the NVflash and the image mentioned in post #2 in following thread. Follow the instructions to switch tablet into APX mode, install the driver and start the flashing. Flawlessly done. No problem. Got rid of the Chinese OS (not supporting Google).
Really cool!
Just in case anyone still has these issues I'm going to post how I found a way to resolve them. I had all the problems mentioned in the previous posts and more besides. The inability to apply OTA updates, the device would freeze after 5 seconds of inactivity, endless boot loops, failed recovery partitions etc etc etc.
I tried a butt load of different solutions but none worked for me. What did work is described below. Others have already mentioned that Advent has a stock rom recovery utility, however, even after flashing that my problems still remained. So I downloaded the Advent stock recovery util and documentation and modified it slightly to the latest Android release for the Tegra Note 7.
Do as follows:
1 - Go here and download both the Advent Vega Tegra Note Factory Image (4.3) util and the documentation.
2 - Extract the Advent Factory Image zip file (as described in the documentation) somewhere on your pc.
3 - Inside the extracted folder you'll see a bunch of files. The three files we're interested in are the "recovery.img", "system.img" and "boot.img". Select all three and delete them.
4 - Now download the Tegra Super Tool utility here. At the time of this post the latest version is 2.5.
5 - Extract the downloaded Supertool to a new folder on your pc.
6 - Inside the extracted folder there are another bunch of files. Again, we're only interested in three of them. You're going to rename three of the files and use them to replace the three files you deleted earlier. At present their names are "4.4.2-2.5recovery.img", "4.4.2-2.5boot.img" and "4.4.2-2.5system.img.ext4". The filenames will obviously change as time goes by, but a little common sense goes a long way at this stage. So "4.4.2-2.5recovery.img" is renamed to "recovery.img", " 4.4.2-2.5boot.img" is renamed to "boot.img" and "4.4.2-2.5system.img.ext4" is renamed to "system.img". Once you've renamed them, copy them into the folder for the Advent Vega Tegra Note Factory Image which you extracted in step 2.
7 - Now go and read the documentation for the Advent Vega Tegra Note Factory Image util. Just take your time and follow it to the letter. It'll tell you how to put your Tegra Note 7 into it's APX mode, install windows drivers for it and begin the recovery of your device. It's mostly an automated procedure and fairly simple to follow as long as you follow the documentation.
This method brought my Tegra Note 7 back when it had several of the problems mentioned earlier in this thread, all at the same time.
Hope it helps someone.