Related
Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.
I was just wondering if someone could point me to what I need to go back to stock and get OTA updates, I live in the US and would like to know which file to download, or does it matter? Do I need the full package? and which honeycomb version should I do? and which file under the version of Honeycomb should I get? or does it matter? Sorry about being n00bish I just would like to get back to stock so I can start over with this thing and get the info down about it.
Hi,
I've been using AfterOTA to go back to stock. It's very easy. I used version 1.01 which isn't available now but 1.07 should still be able to do the same thing.
Which file you use is important as they are geared for different regions of the world. A lot of the files from the Full Package thread aren't there anymore so your choices are limited. It needs to be a full package though, it should be over 300MB. An update won't work.
Basically, you use AfterOTA to install the bootloader and recovery from it's stock tab. Have the update.zip file on the root of your SD card (some of them need to be decrypted). After the tool installs the stock recovery boot by holding down the left or top volume key. That will automatically install whatever update is on the card. Version 1.01 had separate ICS and HC bootloaders I'm not sure how 1.07 is set up. Then just let the update process happen.
I doubt that you'll find anything earlier than HC 3.2 for your (our) region. If you just want a stock ICS tab you could just use that update.zip and skip HC entirely.
Good Luck
Can you point me to the stock ICS zip we would use for our US tabets? I found a page on here http://forum.xda-developers.com/showthread.php?t=1113878 but they dont have an ICS Full Package and I don't know which HC 3.2 one to use. it says to look at my current version but I am on a flexreaper ROM. I want to remove the recovery and bootloader and go completely stock and upgrade to OTA ICS so I can then run After OTA to get a fresh new recovery and ICS bootloader. thanks for your help.
My stock 1.104.02_COM_GEN1 OTA'd to 1.033.00_PA_CUS1.
From Vache's thread the Acer_A500_7.006.01_COM_GEN2 file will update to 1.033.00_PA_CUS1. I don't think this file needs to be decrypted.
1. Download that file. Put the update.zip file on the root of your SD card.
2. In AfterOTA on the stock tab choose A50x. This should install the HC bootloader and standard recovery.
3. Disconnect the tablet. Power down the tablet. Reboot by holding the left or top volume key while pushing the power button. This should start installing the update.zip on the card. If you wind up in CWM then AfterOTA didn't work and you'll need to downgrade.
4. Try to boot after the update. It will probably get stuck at the logo. If it does you'll need to hard reset (bottom volume key + power + slide rotation locker). It takes a while for the first boot and it might crash once while setting everything up.
5. You should be in HC 3.2 from here you can OTA all the way to ICS. You'll need to install the ACER update enhancer from the market b4 it will see the ICS update.
I hope this works for you.
CWM Recovery booted, instead of flashing the update.zip, How do I do it now?
I don't know why AfterOTA isn't working for you. I really thought it would. Oh well, Gersma says it's only for OTA. There are other people who probably know better, but I think you're going to have to get a stock bootloader on there before you can use any of those files. My guess its that you'll need to follow the downgrade guide. Search on "rollback".
I hope you find a better solution, but the rollback isn't that hard.
Good luck.
what if I apply the update.zip from CWM using the "apply update from sd card"? would that just force the up date and wipe everything with the stock bootloader and ROM that is in the update.zip?
I don't think that file will work from CWM. Maybe one of the stock ICS leaks would work. If you can load one from CWM it can load the BL and it will replace the recovery when it reboots. Then you should be able to use AfterOTA to return to stock and upgrade through the OTA's.
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
A very simple question, how to install any of the JB roms? Just because i can't find any good simple guide. And i am not familiar with this device, i know how to flash with CWM and such. (I have experience with other devices) But i see that there is someting with a CPUID and a SBK or something? Please explain how to install those roms.
I did some research and is it sufficient to install the acer recovery app to get cwm on your tablet, (3.x) and then install this: http://forum.xda-developers.com/showthread.php?t=1930672 or this: http://forum.xda-developers.com/showthread.php?t=1935582
WITHOUT patching the unlocked ICS bootloader?
It's important to get your CPUID # and save it on .txt file on PC somewhere.
ALL ICS + JB Roms have Different Bootloader then older HC.
It is best to go to to Unlocked ICS Bootloader. Do lots of reading.
A great method to use is APX, then later once on you can change your Recovery to CWM, TWRP, etc
But either way you'll Need your CPUID.
http://forum.xda-developers.com/showthread.php?t=1622425
Run a SBK Generator, enter in your CPUID #, and then Get your own SBK Code.
Later when using APX, enter your info.
ktmdave7 said:
It's important to get your CPUID # and save it on .txt file on PC somewhere.
ALL ICS + JB Roms have Different Bootloader then older HC.
It is best to go to to Unlocked ICS Bootloader. Do lots of reading.
A great method to use is APX, then later once on you can change your Recovery to CWM, TWRP, etc
But either way you'll Need your CPUID.
http://forum.xda-developers.com/showthread.php?t=1622425
Run a SBK Generator, enter in your CPUID #, and then Get your own SBK Code.
Later when using APX, enter your info.
Click to expand...
Click to collapse
Oke, so i should use that blackthunder program and get my cpuid and sbk. then i can use that program to flash my tab in APX mode? And is it dangerous to flash the bootloader? i mean, if your bootloader gets stuck on a galaxy tab or something it needs to be repaired.
I'm trying to explain it the best way I know (might be slightly Politically incorrect with terms) TRY to get the Knowldege as a whole...
-"ICS Unlocked Bootloader 0.03.14-MUL" is for Acer A500 Tablet (it's custom for our tab's) I would NEVER put another Tab's "Bootloader" on our tab.
- I think you meant Flashing another BASED ROM on tab...That is OK.
*** Example Thor2002 HC 14.2 is based on ASUS's ROM, but has CODE for ACER...
*** All Acer A500 JB ROM's (will be BASED on a LEAK from another source (AOKP, ACER A700 ?), then DEV adds/changes in some Acer A500 code to make them work)
-Fact (to my knowledge) : ACER A500 has not had a JB Leak, cus they have never Made a JB ROM
-Maybe a DEV would Use a ACER A200, A501, A700, etc ROM (which sounds more close to ours) then they USE it's JB (if there is a LEAK'd ROM out)
-Dev has to take into Consideration that Bigger ACER ROMS, Might not have Tegra 2 (Dual Core 1000 Mhz stuff) (One Had Tegra 3, some have 1200 Mhz (more Mhz probably doesn't matter) A501 has 3G (so DEV would make Custom ROM with only Wi-Fi , Rip out 3G stuff or change Code lines)
Back to your Question :
1a. I already have flashed a few of the JB roms on Acer a500 and can Flash to Any other JB or ICS Roms (Without changing BOOTLOADER)
1b. I only changed to my ICS Unlocked Bootloader ONCE. Never have to change again, (Unless I want to goto a HC ROM -then I would have to change to older HC Unlocked bootloader)
2a. Some Flash different RECOVERY's (but keep same Unlocked Bootloader)
2b. Current Versions Flash Recovery (for ICS Unlocked Bootloader) : TWRP-2.3.1.0, Thor2002ro-1.7.3 , A500PubRecovery-0.2, AmonRA-Iconia-3.17
***AmonRA v3.16 is for HC, AmonRA v3.17 is for ICS
Awesome ICS ROM: Lightspeed 4.8 (Acer 1.031 based). His ROM checks to see if u have HC, or ICS bootloader, then install the correct HC, or ICS (Kernel or boot.img).
The Way I Understand It is...
1. ICS Bootlader = ICS, JB Roms, Older HC Bootloader=HC ROMS
2. If you Start with any ICS, or JB ROM (the DEV had removed bootloader.blob + Recovery) so you can keep your Bootloader, and Recovery in tack.
3. if you are 100% STOCK Acer A500 ROM ({NO ROOT SuperSU or Superuser}, Stock Bootloader (which is LOCKED), Stock Recovery (can't change, or flash ROM's)
4a. In past on HC ROM's, many would get Stuck on locked bootloaders, and have to REVERT back to HC 3.01 methed, which means install a very unstable HC 3.01 rom just long enough (like 3 minutes) to get Acer Recovery (from market), ROM manager, CWM recovery...so you could flash Superuser.zip and eventually be on HC 3.2.1 with Stable ROM (or anything)
4b.***(NOW, we have to change out bootloaders to goto to ICS (for the most part) or JB {Exception example: Lightspeed 4.8 is ICS ROM (that will accept older HC Bootloader, I'm sure few others ICS have it}
More info here on stuff : Post #5
I got the bootloader but what now?
ktmdave7 said:
I'm trying to explain it the best way I know (might be slightly Politically incorrect with terms) TRY to get the Knowldege as a whole...
-"ICS Unlocked Bootloader 0.03.14-MUL" is for Acer A500 Tablet (it's custom for our tab's) I would NEVER put another Tab's "Bootloader" on our tab.
- I think you meant Flashing another BASED ROM on tab...That is OK.
*** Example Thor2002 HC 14.2 is based on ASUS's ROM, but has CODE for ACER...
*** All Acer A500 JB ROM's (will be BASED on a LEAK from another source (AOKP, ACER A700 ?), then DEV adds/changes in some Acer A500 code to make them work)
-Fact (to my knowledge) : ACER A500 has not had a JB Leak, cus they have never Made a JB ROM
-Maybe a DEV would Use a ACER A200, A501, A700, etc ROM (which sounds more close to ours) then they USE it's JB (if there is a LEAK'd ROM out)
-Dev has to take into Consideration that Bigger ACER ROMS, Might not have Tegra 2 (Dual Core 1000 Mhz stuff) (One Had Tegra 3, some have 1200 Mhz (more Mhz probably doesn't matter) A501 has 3G (so DEV would make Custom ROM with only Wi-Fi , Rip out 3G stuff or change Code lines)
Back to your Question :
1a. I already have flashed a few of the JB roms on Acer a500 and can Flash to Any other JB or ICS Roms (Without changing BOOTLOADER)
1b. I only changed to my ICS Unlocked Bootloader ONCE. Never have to change again, (Unless I want to goto a HC ROM -then I would have to change to older HC Unlocked bootloader)
2a. Some Flash different RECOVERY's (but keep same Unlocked Bootloader)
2b. Current Versions Flash Recovery (for ICS Unlocked Bootloader) : TWRP-2.3.1.0, Thor2002ro-1.7.3 , A500PubRecovery-0.2, AmonRA-Iconia-3.17
***AmonRA v3.16 is for HC, AmonRA v3.17 is for ICS
Awesome ICS ROM: Lightspeed 4.8 (Acer 1.031 based). His ROM checks to see if u have HC, or ICS bootloader, then install the correct HC, or ICS (Kernel or boot.img).
The Way I Understand It is...
1. ICS Bootlader = ICS, JB Roms, Older HC Bootloader=HC ROMS
2. If you Start with any ICS, or JB ROM (the DEV had removed bootloader.blob + Recovery) so you can keep your Bootloader, and Recovery in tack.
3. if you are 100% STOCK Acer A500 ROM ({NO ROOT SuperSU or Superuser}, Stock Bootloader (which is LOCKED), Stock Recovery (can't change, or flash ROM's)
4a. In past on HC ROM's, many would get Stuck on locked bootloaders, and have to REVERT back to HC 3.01 methed, which means install a very unstable HC 3.01 rom just long enough (like 3 minutes) to get Acer Recovery (from market), ROM manager, CWM recovery...so you could flash Superuser.zip and eventually be on HC 3.2.1 with Stable ROM (or anything)
4b.***(NOW, we have to change out bootloaders to goto to ICS (for the most part) or JB {Exception example: Lightspeed 4.8 is ICS ROM (that will accept older HC Bootloader, I'm sure few others ICS have it}
More info here on stuff : Post #5
Click to expand...
Click to collapse
I installed the unlocked bootloader and wanted to load up the recovery, but it gives a yellow exclamation sign in an android logo. Also when i try to go into recovery mode with a500manager it loads up Honeycomb. When i check my bootloader it is the unlocked CZ bootloader V8. Also i can't enter fastboot with a500 manager. It seems that i do not have a recovery. So i downloaded the acer recovery installer but it requiers root wich i don't have. i already tried different bootloaders like the standard revcovery and the thor 1.7.3 but nothing works. When i load up the tab there is something like CZ Skrillax bootloader v8 Loading primary kernel image.
Do you know why i can't enter recovery?
P.S sorry for bad english.
XFXXFX said:
I installed the unlocked bootloader and wanted to load up the recovery, but it gives a yellow exclamation sign in an android logo. Also when i try to go into recovery mode with a500manager it loads up Honeycomb. When i check my bootloader it is the unlocked CZ bootloader V8. Also i can't enter fastboot with a500 manager. It seems that i do not have a recovery. So i downloaded the acer recovery installer but it requiers root wich i don't have. i already tried different bootloaders like the standard revcovery and the thor 1.7.3 but nothing works. When i load up the tab there is something like CZ Skrillax bootloader v8 Loading primary kernel image.
Do you know why i can't enter recovery?
P.S sorry for bad english.
Click to expand...
Click to collapse
How did you try to enter recovery? "CZ Skrillax bootloader v8 Loading primary kernel image" indicates that you push just the power button. That commands the tablet to boot to whatever OS you have installed. You should hold volume down then push power until the device vibrates. Then you release power while holding still volume -. After a second or two, the "CZ Bootloader V8" would appear along with "loading recovery" on the second line. Then release volume.
Another way, and I've been able to replicate this numerous times on mine, is while the screen is showing "loading primary kernel image" to tap power and release it quickly. MIne would go into recovery that way.
graphdarnell said:
How did you try to enter recovery? "CZ Skrillax bootloader v8 Loading primary kernel image" indicates that you push just the power button. That commands the tablet to boot to whatever OS you have installed. You should hold volume down then push power until the device vibrates. Then you release power while holding still volume -. After a second or two, the "CZ Bootloader V8" would appear along with "loading recovery" on the second line. Then release volume.
Another way, and I've been able to replicate this numerous times on mine, is while the screen is showing "loading primary kernel image" to tap power and release it quickly. MIne would go into recovery that way.
Click to expand...
Click to collapse
I already tried that but it did not help at all. It just show the android logo with exclamation sign. I update the tap with the OTA ICS update and root it and install acer recovery and reflash the bootloader and see what happens. Do you have another idea?
XFXXFX said:
I already tried that but it did not help at all. It just show the android logo with exclamation sign. I update the tap with the OTA ICS update and root it and install acer recovery and reflash the bootloader and see what happens. Do you have another idea?
Click to expand...
Click to collapse
The original question from you was how to install JB Roms. But you keep insisting on installing ICS stock (OTA). What are you really trying to do? I'd suggest that you help yourself by reading the relevant threads in here first before asking for more help. For example, are you aware that mixing unadulterated ICS stock with V8 is a no-no?
XFXXFX said:
I already tried that but it did not help at all. It just show the android logo with exclamation sign. I update the tap with the OTA ICS update and root it and install acer recovery and reflash the bootloader and see what happens. Do you have another idea?
Click to expand...
Click to collapse
u r running stock rom and its overwriting yr custom recovery.....this is all explain ed in the OP of the bootloader guide....reflash bootloader/cwm
1. if u r stock ics then root it
2. delete boot.p file
3. nvflash bootloader/cwm
4. boot to cwm flash jb rom
done...
Sent from my GT-I9300 using Tapatalk 2
Fixed
Sorry for late response.
I updated the tab with OTA ics, and used the blackthundr program to root, then i saw a option to remove the recovery protection. So i used that, and reflashed the unlocked bootloader. Everything worked! I could boot into recovery and installed JB. Everything's fine now. Thx for advice!
Thread may be closed.
XFXXFX said:
Sorry for late response.
I updated the tab with OTA ics, and used the blackthundr program to root, then i saw a option to remove the recovery protection. So i used that, and reflashed the unlocked bootloader. Everything worked! I could boot into recovery and installed JB. Everything's fine now. Thx for advice!
Thread may be closed.
Click to expand...
Click to collapse
Since your problem has been solved, you might want to edit the title of your thread and add the word "SOLVED" so other members know you don't need help anymore.
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.