Database Info

.30 firmware bootloader overwrites TF300 JB bootloader

Move to dev if better suited there.
Thanks goes to saltxyz for this find.
For those of us on the TF300 JB bootloader you can revert back to ICS using my instructions in my other post here only be sure to grab the new .30 firmware: http://forum.xda-developers.com/showthread.php?t=1873635
Not only is ICS running smoothly again thanks to the bootloader but THE .30 BOOTLOADER ALLOWED THE JB KERNEL TO RUN!!
That's right I was able to flash my own TF300 ROM which has everything but the kernel removed from the blob and it ran JB while leaving the bootloader intact.

nice! good to hear asus has things figured out.

I'm guessing this is part of the prep for JB with the bootloader supporting both.

Mike02z said:
I'm guessing this is part of the prep for JB with the bootloader supporting both.
Click to expand...
Click to collapse
I can only assume so.

Can we just flash the .30 zip file in TWRP?
rooted/unlocked

amaury48 said:
Can we just flash the .30 zip file in TWRP?
rooted/unlocked
Click to expand...
Click to collapse
Yes, but you have to extract US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip to US_epad-user-9.4.5.30.zip and flash it.

amaury48 said:
Can we just flash the .30 zip file in TWRP?
rooted/unlocked
Click to expand...
Click to collapse
I've flashed it several times today. You will have to re-install TWRP via fastboot, and then flash SuperUser, if you care about root.

LMMT said:
I've flashed it several times today. You will have to re-install TWRP via fastboot, and then flash SuperUser, if you care about root.
Click to expand...
Click to collapse
I know it's stated that you have already done this, but I really don't want to screw something up and I don't have NVFlash to recover from a hard brick.Can you, or others, confirm that you can indeed move from the .13 JB bootloader to the .30 ICS bootloader successfully and then be able to use the NVFlash?
Edit: Oops, I guess this is for the TF700 only, or will this work on the actual TF300 as well? Anyone know?
-Nate

herschwolf said:
I know it's stated that you have already done this, but I really don't want to screw something up and I don't have NVFlash to recover from a hard brick.Can you, or others, confirm that you can indeed move from the .13 JB bootloader to the .30 ICS bootloader successfully and then be able to use the NVFlash?
Edit: Oops, I guess this is for the TF700 only, or will this work on the actual TF300 as well? Anyone know?
-Nate
Click to expand...
Click to collapse
Actually a user in the nvflash thread said he tried it for the TF300 and it worked.
Sent from my EVO using xda premium

Stuck on tf300 Firmware on TF700...No Idea how to go back HELP

As the title says. I uploaded the tf300 firmware while rooted and an unlocked bootloader. I had twrp
I've heard that flashing the 'update' removes root and relocks the bootloader.
I really have no idea how to go back to ICS but i've read that theres a way. I just can't find any clear directions.

just download the new rom from asus and flash it in recovery.
when it reboots you will be back to stock with new bootloader.

I thought the bootloader went untouched by reflashing the stock ROM? (I might be mistaken here, but isn't that the entire issue with not being able to get back to the ICS bootloader after flashing the JB bootloader?)

New ROM has a new boot loader which will flash over jb.

lafester said:
New ROM has a new boot loader which will flash over jb.
Click to expand...
Click to collapse
However. there's no way to relock the bootloader as the OP had heard, correct?

okantomi said:
However. there's no way to relock the bootloader as the OP had heard, correct?
Click to expand...
Click to collapse
No you can't relock. Not sure where the op may have heard that as I have not seen it posted anywhere.
Might be confused with losing root?

lafester said:
just download the new rom from asus and flash it in recovery.
when it reboots you will be back to stock with new bootloader.
Click to expand...
Click to collapse
It was removed from the asus site, could you provide a link?
Also....do I need to rename it to anything and place it anywhere specific? Because I have already tried and it doesnt work for me. When i go into recovery i get the android with the exclamation point in red. So....idk....

its there i just looked.
you do need to unzip it since it is double zipped for some reason.
then flash as usual.

how to get started with an OTA update maybe?

So i just got my tf700 and I am trying to catch up on what I can and can't do with it as far as OTA updates and custom roms. I have some major questions before I do too much and make an unreversible mistake.
Scenario 1:
Can i unlock the BL, make an NVflash restore point, and then flash any custom rom or perhaps the official CM10 when it is available?
Scenario 2:
Do I need to update to .30 or JB in order to unlock the BL and use any of the newer JB roms or an official CM10?
I have really been reading around,but I can't seem to get the tue answer to these questions. Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

toprunner2786 said:
So i just got my tf700 and I am trying to catch up on what I can and can't do with it as far as OTA updates and custom roms. I have some major questions before I do too much and make an unreversible mistake.
Scenario 1:
Can i unlock the BL, make an NVflash restore point, and then flash any custom rom or perhaps the official CM10 when it is available?
Scenario 2:
Do I need to update to .30 or JB in order to unlock the BL and use any of the newer JB roms or an official CM10?
I have really been reading around,but I can't seem to get the tue answer to these questions. Thanks!
Click to expand...
Click to collapse
Before you start with anything, follow the nvflash guide. Next you can unlock on any version of the OTA, doesn't matter.

so if I follow the NVflash guide, I can then revert back to day-zero at any time? I was under the impression that after I took the OTA, that I would not be able to use NV flash?
Basically, I would assume that I should be able to stay on .26, unlock the BL, and then flash anything that I would want. I have never played with a device with an unlocked BL. Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

toprunner2786 said:
so if I follow the NVflash guide, I can then revert back to day-zero at any time? I was under the impression that after I took the OTA, that I would not be able to use NV flash?
Basically, I would assume that I should be able to stay on .26, unlock the BL, and then flash anything that I would want. I have never played with a device with an unlocked BL. Thanks!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
If you have a backup of NVflash, you're god of your device. You could do practically anything and still get yourself back to factory. (flash custom rom with different bootloader like between .26 and JB, relock/unlock bootloader, recover from brick...just named a few).

buhohitr said:
If you have a backup of NVflash, you're god of your device. You could do practically anything and still get yourself back to factory. (flash custom rom with different bootloader like between .26 and JB, relock/unlock bootloader, recover from brick...just named a few).
Click to expand...
Click to collapse
How can you relock the bootloader if unlocking, which is a requirement for NVflash, permanently destroys the locked bootloader?

As far as I know you *cannot* relock the TF700 bootloader, even if you have NVFlash capabilities.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

[Q] Steps to updating the bootloader firmware?

My TF700 is currently on JB (not sure which version since Build Number isn't showing up on Settings menu anyway), rooted, and unlocked with custom ROM CROMI 3.0.4. I can see that last month there was a new update for the tablet being 10.4.4.25, and I want to update to that to see what improvements there are. The things I'm concerned about needing help with are:
1. How do I update it? As far as I know, I have two files on hand for the new update. One that's about 400+MB from the Asus site, and another being from sdbags' topic introducing his latest version of CROMI that's being about 8-ish MB. Which is the correct one to use?
2. Will I lose my root access after updating?
3. Is there any other precautions I should take before and after I update?
I'm sorry, I'm still a newb at doing this kind of stuff for Android and I've been looking through a lot of threads here on XDA to find the answers I'm looking for. Much help would be appreciated, thank you.

GigaSPX said:
1. How do I update it? As far as I know, I have two files on hand for the new update. One that's about 400+MB from the Asus site, and another being from sdbags' topic introducing his latest version of CROMI that's being about 8-ish MB. Which is the correct one to use?
Click to expand...
Click to collapse
The correct way to upgrade CROMI is to install the latest version of CROMI - it includes the firmware updates from 10.4.4.25 (but the bootloader is separate).
For the bootloader, you can check its version by holding down "volume down" (left) while powering up - the build version should be displayed in the tiny text at the top of the screen. All bootloaders from 10.4.4.18 to 10.4.4.25 are identical, so if you have any of these, you can just install the latest CROMI. Otherwise, in addition to the latest CROMI, also flash the updated bootloader from sbdags.
GigaSPX said:
2. Will I lose my root access after updating?
3. Is there any other precautions I should take before and after I update?
Click to expand...
Click to collapse
2. No, if you install CROMI and not the stock ROM.
3. Backup your data before, and then follow the instructions in the installer.

So there isn't any importance for me to really update to 10.4.4.25? I see there is a log of what it fixes, and I was just interested about updating my bootloader to it. Also, how about the two different bootloader update files?

GigaSPX said:
So there isn't any importance for me to really update to 10.4.4.25? I see there is a log of what it fixes, and I was just interested about updating my bootloader to it. Also, how about the two different bootloader update files?
Click to expand...
Click to collapse
The full firmware includes the bootloader, the stock recovery, the kernel, and the system image. Updating only the bootloader is pointless - the changes you read about were made in the kernel and the system image, not in the bootloader.
Which "two different bootloader update files" are you talking about?

http://forum.xda-developers.com/showthread.php?t=2049274
"You can install this straight over CleanROM 2.3 to 3.x or Asus Jelly Bean Stock without a full wipe. The latest JB Bootloader is necessary before flashing this and is available in Post 2."
If you look at Post 2, he provided the links to the updates for each region. I grabbed the US from his post and it's only 1.09 MB (sorry I checked again. This is the actual size.) When I grabbed the update from the Asus site, it's 456MB. That's what's confusing me atm...

GigaSPX said:
http://forum.xda-developers.com/showthread.php?t=2049274
"You can install this straight over CleanROM 2.3 to 3.x or Asus Jelly Bean Stock without a full wipe. The latest JB Bootloader is necessary before flashing this and is available in Post 2."
If you look at Post 2, he provided the links to the updates for each region. I grabbed the US from his post and it's only 1.09 MB (sorry I checked again. This is the actual size.) When I grabbed the update from the Asus site, it's 456MB. That's what's confusing me atm...
Click to expand...
Click to collapse
Did you even read my previous post? "The full firmware includes the bootloader, the stock recovery, the kernel, and the system image." That's the difference.

I've got a similar question. I'm on the .30 bootloader, which I've unlocked. I don't exactly remember why I'm on it, but if memory serves, before unlocking/rooting, I did the official upgrade to JB (which updated bootloader to 10.xx.xx) then I had to use the blob to downgrade to .30 in order to get the Asus unlocker to work. I've since flashed CWM Touch 6.0.1.9 and am running a fairly recent CM10.1.
So, am I now able to upgrade the bootloader to a newer (read official JB, or, more quantitaiively, 10.xx.xx) version? If I understand correctly, I can use a blob to flash a new "firmware", which would include the bootloader, rom, ril (we have these right?), etc. However, once I do this, I will be stuck on a stock recovery and rom, correct? If there is a way to upgrade the bootloader and keep it unlocked (/unlock it after), what are the steps involved?
I'm fine with the .30 bootloader, but it's ridiculous that the "Reboot to ..." options do not work. OK, so it's not ridiculous, it's just a bit inconvenient and has been causing me to not flash as many nightlies. My followup question would be, does the JB bootloader address this "issue"? And, correct me if I'm wrong, but the only way to get ROM Manager or GooManager to be able to do scripted flashes is to have these reboot options working, right?
TLDR: Have unlocked .30 bootloader, want JB bootloader but want it to be unlocked. Can it be done? Do I really want it?

rayman2k1 said:
TLDR: Have unlocked .30 bootloader, want JB bootloader but want it to be unlocked. Can it be done? Do I really want it?
Click to expand...
Click to collapse
In sbdags' CleanROM Inheritance dev thread, he offers bootloader-only installers - you can use these to install only the current 10.4.4.25 bootloader and keep your current recovery, kernel and ROM (no RIL on a WiFi-only device).
Warning: Make sure your recovery is compatible with a JB bootloader on the TF700 - too old recoveries (created for ICS) are known to cause hard bricks with the JB bootloader.

_that said:
In sbdags' CleanROM Inheritance dev thread, he offers bootloader-only installers - you can use these to install only the current 10.4.4.25 bootloader and keep your current recovery, kernel and ROM (no RIL on a WiFi-only device).
Warning: Make sure your recovery is compatible with a JB bootloader on the TF700 - too old recoveries (created for ICS) are known to cause hard bricks with the JB bootloader.
Click to expand...
Click to collapse
Hey, thanks for the prompt reply. Can you please confirm that this will let me keep my bootloader unlocked? Also, if this does happen to **** things up, do I have any recourse (ie. can I re-flash another, older, bootloader that will allow me to boot?). As I'm on the .30 firmware, I don't have the ability to use NVFlash. Also, will upgrading the bootloader make the "Reboot to.." options work?

rayman2k1 said:
Hey, thanks for the prompt reply. Can you please confirm that this will let me keep my bootloader unlocked? Also, if this does happen to **** things up, do I have any recourse (ie. can I re-flash another, older, bootloader that will allow me to boot?). As I'm on the .30 firmware, I don't have the ability to use NVFlash. Also, will upgrading the bootloader make the "Reboot to.." options work?
Click to expand...
Click to collapse
Once you've unlocked your bootlader, updating it to the lastest (and presumably greatest) will only updat its code, and not relock it. (If it did that, I bet a lot of the users with trouble could've gotten a free warranty reset! -- ASUS wouldn't do that, trust me.)
For completeness' sake: if you did not unlock the bootloader before, the unlock tool will remain as functional as it would have been in the first place. If you can't unlock the new bootloader, you couldn't have unlocked the old one either (issue is on ASUS' side, well referenced on the forum).
Reflashing an older bootloader: no, unless you have NvFlash and the concurrent backup files-- I didn't gather you ran that procedure before upgrading to .30...
TL;DR: your bootloader will remain unlocked if you unlocked it prior to updating, and remains unlockable if not.

MartyHulskemper said:
Once you've unlocked your bootlader, updating it to the lastest (and presumably greatest) will only updat its code, and not relock it. (If it did that, I bet a lot of the users with trouble could've gotten a free warranty reset! -- ASUS wouldn't do that, trust me.)
For completeness' sake: if you did not unlock the bootloader before, the unlock tool will remain as functional as it would have been in the first place. If you can't unlock the new bootloader, you couldn't have unlocked the old one either (issue is on ASUS' side, well referenced on the forum).
Reflashing an older bootloader: no, unless you have NvFlash and the concurrent backup files-- I didn't gather you ran that procedure before upgrading to .30...
TL;DR: your bootloader will remain unlocked if you unlocked it prior to updating, and remains unlockable if not.
Click to expand...
Click to collapse
fantastic. thanks for the detailed reply.
any idea if the reboot to recovery thing is BL-related? if so, would upgrading it solve the problem? or is the tf700 owner's club SOL with that?

rayman2k1 said:
any idea if the reboot to recovery thing is BL-related?
Click to expand...
Click to collapse
Maybe. It works for me, with the 10.4.4.25 bootloader.
In any case, before you use any "reboot to recovery" tool after flashing a new recovery, always test the new recovery by starting it at least once with the power/volume button combination.

rayman2k1 said:
fantastic. thanks for the detailed reply.
any idea if the reboot to recovery thing is BL-related? if so, would upgrading it solve the problem? or is the tf700 owner's club SOL with that?
Click to expand...
Click to collapse
My pleasure!
I had a boot-to-recovery loop once with CM10 -- that was a hairpuller. After doing some research (all the while hair-pulling, to be honest), this zip solved it. So as far as I'm concerned, that'd be a yes.
_that said:
Maybe. It works for me, with the 10.4.4.25 bootloader.
In any case, before you use any "reboot to recovery" tool after flashing a new recovery, always test the new recovery by starting it at least once with the power/volume button combination.
Click to expand...
Click to collapse
This is always sound advice -- the older recoveries indeed have caused quite a few splitting headaches.

thank you, fellas!
EDIT: I upgraded my bootloader successfully. I can now issue the "reboot recovery" command and end up in CWMR. Thanks again!

boot stuck, locked device

hi guys!
tablet has 9.4.5.30 firmware as seen in bootloader, not unlocked, not rooted.
Tablet stuck on asus logo, cirlcles in bottom of the screen rotating.
tried to install other firmware 9.4.5.26 and 10.x versions from sdcard, seems all go fine, but after restart again see 9.4.5.30 in bootloader.
any ideas, what to do?

Explain in detail how you did this. You cannot downgrade flashing stock firmware, you have to have the correct SKU and you have to rename the file properly. Did you do all that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
Explain in detail how you did this. You cannot downgrade flashing stock firmware, you have to have the correct SKU and you have to rename the file properly. Did you do all that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
One day tablet stuck on boot logo with spining wheel. This is my friends tablet. He said that he did nothing to cause error.
I load in bootloader (power + Volume-) menu and see version of firmware 9.4.5.30. I know that it is WW version.
I tried to flash the same firmware (by puting EP201_768_SDUPDATE.ZIP on sd card) 9.4.5.30, also 9.4.5.26, 10.6.1.14.10, 10.4.4.16.
Flashing 9.4.5.26 end with error - not remember error description.
Flashing 9.4.5.30, 10.6.1.14.10, 10.4.4.16 - seem all goes fine, but after reboot again stuck on boot logo and in bootloder i see 9.4.5.30 version.

There's not much more you can do with a locked bootloader. Have you tried using the wipe data option from the bootloader? Then try to flash the 10.6.1.14.10 firmware again. That's the only other option open to you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
There's not much more you can do with a locked bootloader. Have you tried using the wipe data option from the bootloader? Then try to flash the 10.6.1.14.10 firmware again. That's the only other option open to you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Yes, i tried wipe data, no help.
So, with locked bootloader i cant use fastboot and nvflash? How do u think, what is the reason - corrupted flash memory or motherboard dead?
And what is about Asus Flash Tool? Is there tf700 raw images for this tool?

bugouser said:
Yes, i tried wipe data, no help.
So, with locked bootloader i cant use fastboot and nvflash? How do u think, what is the reason - corrupted flash memory or motherboard dead?
And what is about Asus Flash Tool? Is there tf700 raw images for this tool?
Click to expand...
Click to collapse
No, with a locked bootloader you cannot anything in fastboot. Believe me - we tried.
nvflash might have been the savior but you have to generate those blobs when the tablet is still healthy. The blobs are device specific and cannot be exchanged.
Never heard about the Asus Flash tool - got a link?

berndblb said:
No, with a locked bootloader you cannot anything in fastboot. Believe me - we tried.
nvflash might have been the savior but you have to generate those blobs when the tablet is still healthy. The blobs are device specific and cannot be exchanged.
Never heard about the Asus Flash tool - got a link?
Click to expand...
Click to collapse
asus flash tool link on xda http://forum.xda-developers.com/android/general/asus-aft-flash-tool-free-solution-t3165954
but, seems it needs raw firmware image, that i cant find for tf700, may be it does not exist

berndblb said:
No, with a locked bootloader you cannot anything in fastboot. Believe me - we tried.
nvflash might have been the savior but you have to generate those blobs when the tablet is still healthy. The blobs are device specific and cannot be exchanged.
Click to expand...
Click to collapse
Are you sure that you can't flash a signed Asus image using fastboot? And for getting the nvflash blobs you need to install a hacked bootloader, which requires an unlocked bootloader to begin with...

LMK and I tried that and more on a couple of bricked TF700s in this thread: http://www.transformerforums.com/forum/showthread.php?t=48384
We tried to fastboot flash the extracted Asus stock blob to staging. That's what you meant, right?
If you have any other suggestion, I'm all ears!
Sent from my K00C using Tapatalk

berndblb said:
We tried to fastboot flash the extracted Asus stock blob to staging. That's what you meant, right?
Click to expand...
Click to collapse
Yes. If that doesn't work, I have no other ideas.