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!
Related
After my thread for the TF101, here are my first repackaged OTA updates for the TF700:
First of all let me make this clear:
If you have root and want to keep it, use OTA Rootkeeper.
The original recovery is removed from the blob, so you won't lose your current recovery.
If after flashing one of these zips you still have the OTA update notification, do this:
Go to Settings -> Apps -> All and clear data from DMClient.
Current OTA 9.4.5.26:
US version:
us-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: 2C6C763D0A7618E4AB4CB530D714F833
WW version:
ww-9.4.5.22-to-9.4.5.26-TF700-CWM-v1.0.zip MD5: E9597AD7C18483445A1F006D91A44C1B
IMPORTANT! If you deleted/changed some files, these updates will NOT work. These updates are meant for people on a stock rooted rom.
Sweet I know a few people were looking for a flashable OTA update.
...for CWM that hasn't been ported yet
tweeklulz said:
...for CWM that hasn't been ported yet
Click to expand...
Click to collapse
AFAIK cwm zips are compatible with TWRP.
It's a generic name which is supported by most recoveries.
(TWRP or CWM) As far as we are able to unlock our TF700... That not my case...
But it's a good news for those who can
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
eyeballer said:
Lizard, a better title would be "[ROM][FLASHABLE]" or something. People tend to get very confused when you say "CWM" because they think no other recovery can flash it .
Click to expand...
Click to collapse
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Lizard said:
I've changed the title to flashable, since I don't consider the update zips to be roms. I hope this will take away some of the confusion.
Click to expand...
Click to collapse
Thanks! Will reduce our support requests for TWRP
Bad Link To zip File
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
TECHNOLLIC said:
Oops! This page appears broken. DNS Error - Server cannot be found.
This is the message I get when I click the link to download your OTA update, need that update, can you help. Please.
Click to expand...
Click to collapse
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
_that said:
Look at the date of the OP - 9.4.5.26 is very old. Why do you need this old update?
Click to expand...
Click to collapse
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
TECHNOLLIC said:
To install NvFlash. I have 9.4.5.30, NvFlash will not install with this Rom version, it has to be before that.
Click to expand...
Click to collapse
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
_that said:
You cannot downgrade from 9.4.5.30 to 9.4.5.26; the 9.4.5.30 bootloader and above accepts only signed bootloaders and the older ones are not signed.
Click to expand...
Click to collapse
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
TECHNOLLIC said:
So how will I be able to install the NvFlash Tool? I want to flash custom roms but I want to protect my tablet from getting bricked.
Click to expand...
Click to collapse
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
buhohitr said:
You can no longer able to install nvflash once you already flashed above .26 version, like .30 and up. You're out of luck.
Click to expand...
Click to collapse
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet. Thank you very much for your help.
If you've flashed roms on other phones or tablets in the past then you should be fine. Just don't do anything crazy and you shouldn't brick it. I don't have NV Flash capabilities on mine, though I had the chance to but updated my bootloader anyway. Doesn't bother me as I'm not a dev and won't be doing anything crazy on mine. I've done plenty of flashing on many phones and the Asus Prime in the past, so I'm not worried about it
Sent from my Evo LTE using XDA Premium
TECHNOLLIC said:
That sucks, I didn't flash .30, it came with it already installed. I'm used to flashing my phones, so it should be no problem flashing my tablet.
Click to expand...
Click to collapse
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
_that said:
Just be careful to never choose "wipe data" in the bootloader menu without a working (compatible to bootloader) recovery, that is the #1 reason for hard bricks:
http://forum.xda-developers.com/showthread.php?t=1917304
Click to expand...
Click to collapse
Thanks again for your help and support.
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
rocketjr said:
I just received my TF700T for Christmas and it has JB. Can I flash this to go back and get root without unlocking?
Click to expand...
Click to collapse
Yes. see http://forum.xda-developers.com/showthread.php?t=1925230
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
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.
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
devlop said:
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
Click to expand...
Click to collapse
You do have unlocked boot loader right?
http://forum.xda-developers.com/showthread.php?t=1803343
Yep, unlocked bootloader. The link you provided is what I've been trying to do. Just like the other person at the end of the thread, I get a signature error during boot and my recovery remains custom with TWRP. I'm not sure what the problem is, this is why I am considering nvflash.
devlop said:
Yep, unlocked bootloader. The link you provided is what I've been trying to do. Just like the other person at the end of the thread, I get a signature error during boot and my recovery remains custom with TWRP. I'm not sure what the problem is, this is why I am considering nvflash.
Click to expand...
Click to collapse
If it's not working for you, you could try to downgrade to .22. Basically, download full .22 version, extract, renamed and copy to your SDcard then use twrp to flash.
How to downgrade.
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
EDIT: On a second note, why you want to restore back to "stock recovery"??
devlop said:
I've installed Nvflash and have grabbed the files intended for restore per the instructions. Now I'd like to restore my tablet. I'm on .26 with TRWP installed and am having issues restoring stock recovery. I want to upgrade to .30, then jb. My only known alternative is to use Nvflash. So, can someone point me in the direction of instructions for this process?
Click to expand...
Click to collapse
you don't have to use nvflash for this,just download JB from Asus site and install with TWRP,done.Why you need o complicate your life?
Hmmm, I thought the process for getting to jb was to first upgrade to .30. From what I've searched through, I've only found instructions to upgrade to .30 by means of stock recovery. Is it possible to jump straight to jb from .26?
devlop said:
Hmmm, I thought the process for getting to jb was to first upgrade to .30. From what I've searched through, I've only found instructions to upgrade to .30 by means of stock recovery. Is it possible to jump straight to jb from .26?
Click to expand...
Click to collapse
haha, I doubt that anyone here have tried to go directly from .26 to JB, You probably the first if you try. Why don't you twrp to .30 and let the OTA to JB? based on my knowledge, OTA upgrade one version at a time.
Perhaps I have some info wrong. I can install the factory updates with TWRP? I don't need stock recovery?
devlop said:
Perhaps I have some info wrong. I can install the factory updates with TWRP? I don't need stock recovery?
Click to expand...
Click to collapse
OK let start over. This is how i would do this:
1. Downloaded .26 from Asus site.
2. Unzip and moved the zipfile inside to root of internal sd card.( /mnt/sdcard)
3. Rebooted, your device should found the update and prompt you to update, flashed the update. You should be back on .26 with stock recovery and unrooted.
4. Reroot and download OTA root keeper to save root. Run root keeper to save root
5. OTA to .30. (if OTA is not working, let me know).
buhohitr said:
OK let start over. This is how i would do this:
1. Downloaded .26 from Asus site.
2. Unzip and moved the zipfile inside to root of internal sd card.( /mnt/sdcard)
3. Rebooted, your device should found the update and prompt you to update, flashed the update. You should be back on .26 with stock recovery and unrooted.
4. Reroot and download OTA root keeper to save root. Run root keeper to save root
5. OTA to .30. (if OTA is not working, let me know).
Click to expand...
Click to collapse
I'm already on .26. Should I be downloading .30? Also, even though I have TWRP installed, the tablet should still pick up the fact that there is an update on the memory? Just a side note, I'm unlocked, so ota's will not work for me.
devlop said:
I'm already on .26. Should I be downloading .30? Also, even though I have TWRP installed, the tablet should still pick up the fact that there is an update on the memory? Just a side note, I'm unlocked, so ota's will not work for me.
Click to expand...
Click to collapse
Sure if you want to, download .30. Tablet should pick it up, make sure you unzip it first. Yes, you're correct you have to upgrade using manual process. Every methods here on XDA are not 100% work for everyone (you already knew that). But it should work for most ppl.
Great. I appreciate your help. I'm at work, tablet's at home. I'll give this a go tonight and report back.
buhohitr said:
haha, I doubt that anyone here have tried to go directly from .26 to JB, You probably the first if you try. Why don't you twrp to .30 and let the OTA to JB? based on my knowledge, OTA upgrade one version at a time.
Click to expand...
Click to collapse
Mate do you actually know what you are saying? The JB firmware from Asus site it's a full rom not just an OTA (incremental) update, this means you can update from any version (do you see any word from Asus saying you must be on. 30 before installing?) because everything will be updated (BL, Kernel, etc) so installing this with TWRP will get you Full Stock JB (yes, you will loose twrp too).
Pretoriano80 said:
Mate do you actually know what you are saying? The JB firmware from Asus site it's a full rom not just an OTA (incremental) update, this means you can update from any version (do you see any word from Asus saying you must be on. 30 before installing?) because everything will be updated (BL, Kernel, etc) so installing this with TWRP will get you Full Stock JB (yes, you will loose twrp too).
Click to expand...
Click to collapse
I'm not disagree with you! just saying no one here have tried to go straight before. The only question here is the bootloader between .26 and JB is different and why Asus pre upgrade to .30 before JB? IDK, maybe there is a reason, maybe not. Some how I think they need to prep the bootloader on .30 to be ready for JB? again I don't know.
buhohitr said:
I'm not disagree with you! just saying no one here have tried to go straight before. The only question here is the bootloader between .26 and JB is different and why Asus pre upgrade to .30 before JB? IDK, maybe there is a reason, maybe not. Some how I think they need to prep the bootloader on .30 to be ready for JB? again I don't know.
Click to expand...
Click to collapse
My personal opinion on that is that Asus did this because they made a mess by letting people install TF300T Jelly Bean on TF700T (that should never be possible with locked bootloader and official firmware) so they updated the bootloader on .30 update so ppl could downgrade from that tf300t Jelly Bean rom.Maybe i'm wrong,but it does make sense and if i'm not wrong TF700T is the only transformer device that can downgrade from JB to ICS so easily.
Good news, I was able to flash .30 and now jb. I had no idea it was that simple. I thought I had to be back on stock recovery. Thanks for the help guys.
devlop said:
Good news, I was able to flash .30 and now jb. I had no idea it was that simple. I thought I had to be back on stock recovery. Thanks for the help guys.
Click to expand...
Click to collapse
Guys you can just install the JB firmware from asus. Unzip, flash that file in twrp and boom straight from .26 to JB with no issues. It even keeps all your data.
Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.
I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!
madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:
LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...
berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.
Hi there,
I am running an unlocked TF700 on 10.6.1.14.10.
I am currently trying to get downgrade to firmware 10.6.1.14.08 in order to get root and to install custom firmware (stock Asus firmware is just too damn slow).
I've put the unzipped (it was a zip inside a zip) "WW_epad-user-10.6.1.14.8.zip" into the root director of TF700. When I reboot and the system offers me to downgrade, everything seems to be going okay.
But once the downgrade process begin, I get an error message (just a red "error" and a broken android mascot) and i have to turn the TF700 off and reboot back into the 10.6.1.14.10 firmware.
I tried downgrading my going directly into the boot / recovery menu and I get the same result.
How can I find out what's going on?
Thanks,
Levi
You probably have some system apps or bloatware frozen or uninstalled. The upgrade/downgrade checks for system integrity. If it doesn't find certain apps it will not install.
But why downgrade? Root doesn't help you getting a custom recovery onto your tablet.
Unless GooManager works again for flashing recoveries. Have read conflicting reports on that. If you go that route and it works, please let me know.
It is just as easy to flash the recovery in fastboot though. No need for downgrading either...
Sent from my XT894 using Tapatalk
How do I find what I s causing this? I tried Clean Master but that didn't change anything. How can I get more info on this problem?
I following the instructions for the latest cromi ROM. they need unlock and root.
levictus said:
How do I find what I s causing this? I tried Clean Master but that didn't change anything. How can I get more info on this problem?
I following the instructions for the latest cromi ROM. they need unlock and root.
Click to expand...
Click to collapse
Go to settings, apps, and scroll over to the right, do you have anything disabled?
If so enable it.
It's probably easier if you block and follow the fastboot instructions to flash twrp and then CROMi-X.
levictus said:
How do I find what I s causing this? I tried Clean Master but that didn't change anything. How can I get more info on this problem?
I following the instructions for the latest cromi ROM. they need unlock and root.
Click to expand...
Click to collapse
You do need to unlock your tablet to run a custom rom. You do not necessarily need root.
If you are looking at a CROMi thread, you probably look at outdated information. CROMi was JB 4.1 based.
The same dev - the guy up there^^^^, sbdags - developed CROMi-X from the JB 4.2.1 base. That's the latest and greatest rom in the CleanROM lineage. His thread his here:
http://forum.xda-developers.com/showthread.php?t=2425383
Check out the OP for information how to proceed.
I recently wrote a little tutorial with current information on another forum geared towards users new to flashing custom roms. Maybe it helps:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
berndblb said:
You do need to unlock your tablet to run a custom rom. You do not necessarily need root.
If you are looking at a CROMi thread, you probably look at outdated information. CROMi was JB 4.1 based.
The same dev - the guy up there^^^^, sbdags - developed CROMi-X from the JB 4.2.1 base. That's the latest and greatest rom in the CleanROM lineage. His thread his here:
http://forum.xda-developers.com/showthread.php?t=2425383
Check out the OP for information how to proceed.
I recently wrote a little tutorial with current information on another forum geared towards users new to flashing custom roms. Maybe it helps:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
Thanks, that last link is exactly what I was looking for. I will try fastboot once I am back home and report back.
P.S. the instructions for the current version of cromi don't reference the fastboot method.
cheers,
levi
Hummm, might be wrong here but if you want to downgrade the version unzip the file one time while it's on the PC rename the unzipped file to EP201_768_SDUPDATE.ZIP plug your sd card into the PC and copy that to the root of the sd card. Then try it.
Got CROMi running using the fastboot method. So far everything is working greater. The UI is much more responsive than with stock 4.2.1. The tablet is actually usable now.
I will provide more feedback in the CROMi thread once I get a chance to use it properly.
Thanks berndblb!
Levi
levictus said:
Got CROMi running using the fastboot method. So far everything is working greater. The UI is much more responsive than with stock 4.2.1. The tablet is actually usable now.
I will provide more feedback in the CROMi thread once I get a chance to use it properly.
Thanks berndblb!
Levi
Click to expand...
Click to collapse
:Good: Glad if I could help