Related
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.
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.
hi everyone
i'm explaining the problem that's getting me crazy!
I've got an a500 tab. it was HoneyComb 3.1 at first, I downloaded ICS 4.0.3 Stock Rom and installed it via SD Card, Power + Vol- button.
i've been using it a few monthes now i want to use a custom rom like tegraowners JB.
my current version of rom (ICS 4.03) can't be rooted with ICS Root for a500 because it's version is'nt supported.
so i decided to install a 3.1 HC Stock rom, root it and use custom roms.
i downloaded 3.1 stock rom, named it update.zip and copied it on a sd card.
inserted SD card in tab and turned it on with Power + Vol-. here is the problem!
first i see recovery mode loading then an android logo with a (!) sign on it.
cdn.gooyait.com/uploads/android-recovery-mode-600x276.jpg
and tab get's restarted...
any idea?
I don't know maybe i've downloaded the wrong rom.
if yes please link to the correct rom for thei version:
Kernel Version:
2.6.39.4+
Image Version:
Acer_AV041_A500_RV21RB01_WW_GEN1
Build Number:
Acer_AV041_A500_0.014.00_WW_GEN1
PLEASE!
AHashemi said:
hi everyone
i'm explaining the problem that's getting me crazy!
I've got an a500 tab. it was HoneyComb 3.1 at first, I downloaded ICS 4.0.3 Stock Rom and installed it via SD Card, Power + Vol- button.
i've been using it a few monthes now i want to use a custom rom like tegraowners JB.
my current version of rom (ICS 4.03) can't be rooted with ICS Root for a500 because it's version is'nt supported.
so i decided to install a 3.1 HC Stock rom, root it and use custom roms.
i downloaded 3.1 stock rom, named it update.zip and copied it on a sd card.
inserted SD card in tab and turned it on with Power + Vol-. here is the problem!
first i see recovery mode loading then an android logo with a (!) sign on it.
cdn.gooyait.com/uploads/android-recovery-mode-600x276.jpg
and tab get's restarted...
any idea?
Click to expand...
Click to collapse
Stock recovery probably isn't designed to flash anything other than ICS. (Or it can't go backwards?). As for rooting, the blackthud3r ICS root tool oughta get ya done. (There are 2 methods, search and find one. For your case I recommend number 2)
[Anyway, don't worry about rooting the stock ROM, on an A500 this doesn't help you get jellybean.]<- MAY BE WRONG. In order to install a custom ROM, you must install a custom bootloader and recovery. Here is a guidehttp://forum.xda-developers.com/showthread.php?t=1622425 Once you've gotten through that(and assuming you haven't died of heart attack), you can install a custom ROM. Just follow the instructions on said ROM's thread. My favorite(albeit, a bit buggy) one is here :http://forum.xda-developers.com/showthread.php?t=2239476&highlight=jellybean+rom&nocache=1. Good luck!:good:
EDIT:
You need a CPUID to flash your bootloader. I don't know if you need root to get that.
Install a custom bootloader
You shold read about custom bootloader, it isnt that difficult, you get root of your iconia, download a flex software it automaticly downloads the latest recovery I recommend TWRP, and from ther you could touch the option install and select you zip file
Hi, I'm trying to unroot my iconia.
I've tried blackthunder unroot tool, seems to work but doesn't (as stated elsewhere).
So I'm trying to flash a stock firmware.
I downloaded the same firmware I have on the tablet:
Acer_A500_1.031.00_WW_GEN1
renamed as update.zip, put it onto sd card, rebooted the tablet with vol down + power, the android appears, then falls down with a red triangle in.
So I've tried acer update decrypt, even if in the diagram was not contemplated, but I get an out of memory message.
Then I've tried to install a custom recovery, downloaded Acer Recovery Installer from the market, chose cwm, then when booting into recovery i get a red error message, recovery verified failed.
luckily the tablet still works, but I really need to unroot it, any help would be appreciated.
Thanks, cheers
edit: I followed this:
http://forum.xda-developers.com/showpost.php?p=25891744&postcount=44
and, with some issues, I think I was able to unlock the bootloader, in fact I could flash the stock rom.
many many thanks
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.