Related
Hi
So i have question about firmware changing.
It's possible to move from TW 9.2.2.3 firmware to WW 9.2.2.3 wf.?
Did somebody operation like that? It's save or not?
I don't have root and CWM recovery because this things isn't possible for now on latest ICS firmware, so only one possibility i flash update.zip by stock recovery.
So it's save or not and maybe some advice?
Thank you
I think it's possible with nvflash and I did it with the staging partition once, although I didn't test it extensively - maybe 5 mins to see if it worked. I didn't test if wifi worked or if it crashed every 10 mins.
The Belgium (TB) version of the 91117 rom is being switched to WW, so you might want to pull that apart and see if there is any fancy magic going on in there. There are instructions on the ASUS site.
If you only have stock recovery, it might be tough because of firmware checks to prevent you from doing exactly what you are suggesting. Again, the TB rom might offer some insight.
gee one said:
I think it's possible with nvflash and I did it with the staging partition once, although I didn't test it extensively - maybe 5 mins to see if it worked. I didn't test if wifi worked or if it crashed every 10 mins.
The Belgium (TB) version of the 91117 rom is being switched to WW, so you might want to pull that apart and see if there is any fancy magic going on in there. There are instructions on the ASUS site.
If you only have stock recovery, it might be tough because of firmware checks to prevent you from doing exactly what you are suggesting. Again, the TB rom might offer some insight.
Click to expand...
Click to collapse
Thanks!
I'm above B70, so nvflash will not work...:-\
I saw this TB version switched to WW on Asus site for 9.2.2.3 also, but I'm afraid it will not work with TW because of firmware checks...
So I need to wait for root possibility and CWM recovery?
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
jeremiah.wells said:
I have combed through these forums and haven't been able to find an answer yet, so please forgive me if I have missed something. So here goes:
If: a) I have updated to JB, and
b) I unlocked my device and
c) I successfully installed TWRP and
d) I managed to brick my device insomuch that ONLY APX mode is available to me when I connect to my PC, is there a solution unbrick my device at this time?
Currently booting my device will only display the first ASUS boot screen and never goes any further.
Many thanks to anybody who can provide some insight.
Click to expand...
Click to collapse
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
MartyHulskemper said:
What have you tried in the meantime? Did you install NvFlash before the update to JB? You cannot get to recovery? If you cannot but do have fastboot available, either use TWRP or CWM (which can be flashed via fastboot as well: http://forum.xda-developers.com/showthread.php?t=1926286 in case your recovery has been borked) and then flash a stock ROM from ASUS from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Take a look here: http://forum.xda-developers.com/showthread.php?t=1938129 as well.
Click to expand...
Click to collapse
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Can you get into recovery at all when you hold vol down and power? I had the same problem with my infinity when the .18 update came out, i had a freeze and a crash during normal use while the update was either downloading or changing something and when it restarted I couldnt do anything but go into APX. I never unlocked it (mainly because the asus tool wouldnt work) but I had to RMA to get it fixed. If you can at least get to the recovery menu you can try reinstalling the stock rom from an mSD. Otherwise you may have to do the same as me and RMA and hope that they dont tell you tough luck since its unlocked As far as I know the only way to recover the tablet when APX is your only option is with NVFlash, which I never installed because .30 was on my infinity when i bought it.
jeremiah.wells said:
I couldn't get either recovery to boot and so I attempted a data wipe
Click to expand...
Click to collapse
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
_that said:
That is the exactly step that bricked many TF700s here (search the forums). "Wipe data" with a broken recovery = bootloader won't do anything else than try to boot the broken recovery.
If you didn't create a blob for wheelie/nvflash before, your only option now is to send it to Asus for a costly "repair" (they claim they have to change the mainboard, I don't know why they don't just use nvflash).
Click to expand...
Click to collapse
Yes, with only APX available but no NvFlash backup, there's very little to no light at the end of the tunnel. I also wondered why the reports of RMA'd users mention a motherboard change, but I do remember something about unit-specific code being backed up with NvFlash. Although I'd think it strange, it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
@OP: with no fastboot available, you will not be able to follow either Scott's guide or reflash a recovery. I sincerely feel for you, especially since it was enthusiasm that got you into trouble. I know the resultant feeling, and I hate it, for it quells said enthusiasm in the future and make you overly cautious. I wish you a speedy and effective RMA!
jeremiah.wells said:
MartyHulskemper, many thanks for your prompt reply. To answer your questions:
1) I have tried (in vain, I now understand) to use nvflash (first using wheelie with a couple configurations) and to no avail
2) I did NOT install nvflash before, as I was excited about rooting and wasn't abreast of all the consequences of updating directly to JB and then unlock and then root with a new device. Unfortunately I had read a post on (another website) that nvflash wasn't working on the TF700T (which I presume was correct at the time it was written) only to now learn that it is.
A note -- fastboot is not available and the only way I can get the device visible to a computer is to put it in APX mode.
This is a classic case of me jumping the gun without fully understanding what's implied with the various updates and root solutions out there. Basically I followed a guide and used a set of files distributed on scottsroms that indeed rooted my device with the TWRP recovery. What I then attempted and (I think what ultimately did my device to its current state) was to attempt to flash CWM. After that flash I couldn't get either recovery to boot and so I attempted a data wipe and was going to reflash with CWM. After that data wipe is when I could not longer boot.
Sorry about the novel but I guess I'm vainly hoping this may trigger and idea from you or a future reader about what my options are. I will look at the link you suggested and go from there.
Again, thank-you for any assistance you may provide.
Click to expand...
Click to collapse
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
I feel for you too as this happened to me even without any type of modifications to my recovery or bootloader! As far as RMA and the motherboard change I am not sure whether they recovered my device without an actual change. When i got it back from RMA it was on the same firmware as before (not the most recent at the time) as well as retaining the same SN on my device. Since I got it back though I am unable to use the unlocker tool. I get that network error and a refusal from the asus unlock server that lots of people were having issues with a while back. I am in touch with Asus service now, but asus service is usually a long arduous process! I hope that they dont charge you for the replacement, but seeing as you unlocked its very possible if you have any sort of insurance from your credit card that may be a better route by trying to replace it as a lost or broken unit. My RMA was free (except shipping) but again, no unlock!
best of luck.
MartyHulskemper said:
it might be that even ASUS cannot revive a bricked 700 without knowing that code, necessitating the new motherboard with a known code. This is only speculation, of course, but it's the only reason I could think of.
Click to expand...
Click to collapse
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
_that said:
They must know the device key, because the unlocking process requires it. However it is plausible that service centers have no access to this information.
It's somehow depressing that not knowing 128 secret bits takes away control over our own devices.
Click to expand...
Click to collapse
In cases like this, I always hope you get a motivated technician that actually hunts down your serial from that database and helps you out. Guess I'm a bit naive in that regard.
Yeah, those 16 bytes keeping the door shut are a major bummer, as is the fact that NvFlash was not pre-installed anyway...
okantomi said:
I really feel for you...just bricked a phone last week and it's an awful feeling, like you should have known better. Good luck.
Just out of curiosity, did you use Rom Manager to flash CWM recovery? That's the kiss of death for the TF700.
Click to expand...
Click to collapse
To answer your curiosity, NO... I did not install or use Rom Manager in any way to get to this state.
Got a question. Mine is rooted but locked, i attempted to install TWRP before unlocking. I can still boot it up but i cant get into recovery. Can i unlock it without a working recovery and just reinstall TWRP? what are my options? Any help would be great.
edit: nevermind, i think i found the answer...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Hope this helps!
hobomobile said:
Okay! (bit of a noob here but I really want help T_T)
I'm on 4.2.1 by the way - build number should be latest available.
So I finally decided to get root on my tablet. I followed the instructions by a youtube user, and succeeded. I downloaded SuperUser and a root checker to make sure everything went right, and proceeded to download PacMan 4.2 Milestone, as well as CyanogenMod 10
I did a factory reset from the settings menu of the tablet, and tried to set up PacMan. It worked alright until the loading screen, where the ghost would bounce indefinitely. When it was clear I wasn't going to get in, I restarted, and factory reset again from the TWRP menu, this time making sure to erase Dalvik, cache, and system (I think that's all?).
I then tried to install CM10, which didn't work either. I found out later it was because CM 10 didn't work with the 4.2 bootloader.
So I factory reset again, erased dalvik, system, and cache, and proceeded to reboot into the recovery I made on external. I don't know if it's normal, but when it reached the step 'restoring data,' it was basically stuck. I let it continue overnight, and found that recovery overall took 1933 seconds (is this a sign of something bad?)
And now I'm back to booting! It's taking a really long time though - at least ~45 minutes on the ASUS screen with the little circle going around.
I guess my question is, (1) what do I do, (2) what is the situation I'm in/how did I get here, (3) how do I avoid it (if possible) in the future?
Click to expand...
Click to collapse
hobomobile said:
by the way, I forgot to mention that I can still access the twrp menu. I don't know if that helps though?
Click to expand...
Click to collapse
1. Assuming you know how to do this, try flashing the ASUS stock rom and kernel using TWRP. Before asking more questions, use the search tool in XDA developers first since it is most likely someone may of been in a similar situation to yours.
2. It is probably that the person who you followed on youtube might of been be using a different build of stock. That's just my hypothesis-others may differ to mine. Since you have TWRP, you will be able to recover from this situation. (Pun not intended)
3. You should always research about what you're doing with your android device before you do anything about it, especially if the guide is not moderated by the wonderful people from XDA-Developers, and even more so if you are a noob-even if you consider yourself a novice (like me)
To save you some time:
http://forum.xda-developers.com/showthread.php?t=1697227 The mother of guides, read this first.
http://forum.xda-developers.com/showthread.php?p=42407269 [TOOL]Minimal ADB and Fastboot
http://forum.xda-developers.com/showthread.php?t=2257421 Ask any question here-Noob friendly help thread.
Will update this post with more information if need be. Don't be afraid to ask if you're absolutely confused.
Hope this helped.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
Thanks a lot! I'll do my best trying to find the info - sorry if I have to bother you again though!
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Potential Solution?
Quote:
hobomobile said:
Okay, so I downloaded this: ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU (Android 4.2) - 2013.07.29 update, unzipped the file, went back into twrp, and wiped system, data, and dalvik. When I tried to install it though, it says 'failed.'
What now?
Click to expand...
Click to collapse
hobomobile said:
Okay, so I have minimal ADB (I actually used that to get root in the first place), and I downloaded the latest kernel and firmware - I'm pretty sure they're the right versions too (10.6.1.27).
Do I just open TWRP, factory reset, clear dalvik and cache, and install both of the above from an SD card? I did some looking around, but I still don't get what a kernel does, or if it's necessary in this situation.
I'm looking at this right now, by the way (http://forum.xda-developers.com/showthread.php?t=2187982), method three.
Click to expand...
Click to collapse
Define Kernel:
Google:
Define Kernel:
ker·nel
/ˈkərnl/
Noun
A softer, usually edible part of a nut, seed, or fruit stone contained within its hard shell.
The seed and hard husk of a cereal, esp. wheat.
Synonyms
core - nucleus - pith - grain - heart - seed - essence
So that was useless. :silly:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
If I was you, I would just flash a custom ROM. From here: http://forum.xda-developers.com/showthread.php?t=1697227
There are plenty of ROMs linked there. Even if you want to use one based on the Stock ROM, you can find the links there.
Flash it in TWRP the same way you flashed the "ASUS Transformer Pad TF300T Firmware: V10.6.1.27.1 Only for US SKU".
Personally, I prefer custom roms because they provide a lot of customisation options.
Is that what your looking for, or do you really want to use the stock ROM?
Remember to at least have a look at the ROMs before dismissing them.
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Hope this helped.
BTW, this did not bother me one bit. Your Welcome!
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.
If you are running "10.6.1.27" that might be the issue some roms don't boot if you can access fast boot try downgrading to 10.6.1.15.3
Sent from my HTC Desire C using xda app-developers app
1337 H4X0R said:
XDA:
Define Kernel-and ROM, and everything:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel "ROM vs Kernel"
The kernel needs to be the same type as the ROM. e.g, A stock (based) rom will need a stock (based) kernel. AKOP/ASOP ROMS need ASOP/AKOP Kernels. You get the point. See the link mentioned for more information.
Check the compatibility of the ROM with your bootloader before you flash it to not get into situations like this again. (From when you said that CM10 failed to work with your boot loader.
Click to expand...
Click to collapse
Just to add a *tiny* little tidbit right here: every rom has a kernel. It wouldn't boot without one. Yes, a dev can remove the kernel and force you to find one to flash, but that's utterly pointless. I'm just saying that you really don't have to bother yourself with that as yet.
While it's great to educate yourself, don't get overwhelmed. You have PLENTY time to learn more.
I ran into similar issues. You need to make sure your ROM/kernal matches your bootloader and matches your recovery. If not all three match, you run into this issue.
Sent from my EVO using XDA Premium 4 mobile app
so far no good :/
I gave up on this for a couple days, figuring I'd come back to it later when I wasn't as distressed.
so right now, my goal is to get back to stock, and get everything working again before downgrading to 10.6.1.15.3, and then install a custom ROM
Not sure why, but right now, I can't even install the stock kernel flashed onto the device - twrp still tells me 'failed.'
I'm sure that I got the right stock kernel/rom for my build number, so what is going on?
Hey guys,
I am back to using the TF700T after about a year's absence from it. I've done a bunch of tweaks on it some time ago and can't really remember all the things that have been done. I know that the device is rooted and unlocked but couldn't tell you the ROM or anything else ... not that it matters.
I want to get this thing back up and running as fast as possible so I am looking for some suggestions on a lightweight ROM that has speed as its focus. I don't care if I lose everything on it and would like to go back to as factory of a feel as possible ... I'm even open to the OTA ROM if people believe it's the best.
Can someone provide some suggestions on where to start?
llcooljayce said:
Hey guys,
I am back to using the TF700T after about a year's absence from it. I've done a bunch of tweaks on it some time ago and can't really remember all the things that have been done. I know that the device is rooted and unlocked but couldn't tell you the ROM or anything else ... not that it matters.
I want to get this thing back up and running as fast as possible so I am looking for some suggestions on a lightweight ROM that has speed as its focus. I don't care if I lose everything on it and would like to go back to as factory of a feel as possible ... I'm even open to the OTA ROM if people believe it's the best.
Can someone provide some suggestions on where to start?
Click to expand...
Click to collapse
This is maybe what you are looking for.... It is light version of Cromi X and very fast in my opinion...:good:
http://forum.xda-developers.com/showthread.php?t=2520828
Please let us know your opinion...Thanks...
Most popular, for a very good reason, is CROMi-X. Based on the stock rom, cleaned and optimized to the nines. It's how the stock rom should have been
http://forum.xda-developers.com/showthread.php?t=2425383
Lightweight?
Go for miniCROMi-X - stripped down to the essentials, very fast but you may miss some bells and whistles but definitely worth a try.
http://forum.xda-developers.com/showthread.php?t=2520828
Want Kitkat on the TF700? CyanogenMod 11 will get you there. Still some bugs though.
Then there's OMNI ROM, Paranoid, CMB.... they all have a thread in the Development section. Check them out.
Make sure you update your bootloader and recovery to the required version. If you didn't update in a year, both are definitely outdated!
Thank you for the suggestions but could you point me in the right direction to update my bootloader and recovery? It's been a while and I don't want to hard brick my Transformer.
I have since updated my computer so I'm sure my drivers for the Transformer aren't up to date ...
Sorry to ask but could you walk me through the process as if I'm new to it again?
Very much appreciated.
Model Number
ASUS Transformer Pad TF700T
Android Version
4.1.1
Kernel Version 3.1.10
[email protected] $51
Build Number
CleanROM 3.1 inheritance
Click to expand...
Click to collapse
What I am most afraid of is that I don't know what version of the Transformer it is ... US, World Wide ... the build number seems to have deleted all reference when I had flashed to ClearROM. Any way to figure this out with another method?
llcooljayce said:
Thank you for the suggestions but could you point me in the right direction to update my bootloader and recovery? It's been a while and I don't want to hard brick my Transformer.
I have since updated my computer so I'm sure my drivers for the Transformer aren't up to date ...
Sorry to ask but could you walk me through the process as if I'm new to it again?
Very much appreciated.
What I am most afraid of is that I don't know what version of the Transformer it is ... US, World Wide ... the build number seems to have deleted all reference when I had flashed to ClearROM. Any way to figure this out with another method?
Click to expand...
Click to collapse
Well if you are in the US, most likely it is US... And it doesn't matter that much on a custom ROM anyway.
Read the OP in the CROMI-X thread and follow the instructions for scenario 2. Download the bootloader /TWRP package provided there, flash it, reboot, do a factory wipe in TWRP and you're good to flash the rom.
berndblb said:
Well if you are in the US, most likely it is US... And it doesn't matter that much on a custom ROM anyway.
Read the OP in the CROMI-X thread and follow the instructions for scenario 2. Download the bootloader /TWRP package provided there, flash it, reboot, do a factory wipe in TWRP and you're good to flash the rom.
Click to expand...
Click to collapse
Problem is that I am in Canada and Canadians get either the WW or US version. From what I am reading, if I choose the wrong bootloader, I will brick my device. Any other way to determine the SKU version?
llcooljayce said:
Problem is that I am in Canada and Canadians get either the WW or US version. From what I am reading, if I choose the wrong bootloader, I will brick my device. Any other way to determine the SKU version?
Click to expand...
Click to collapse
The bootloader is universal. Only the firmware is regional. Look in About Tablet > Build Number. Even your old CROMi version should have a US or WW in it. But AFAIK Canada is North America, which is US - sorry, I know it's a sore point with you Canadians
berndblb said:
The bootloader is universal. Only the firmware is regional. Look in About Tablet > Build Number. Even your old CROMi version should have a US or WW in it. But AFAIK Canada is North America, which is US - sorry, I know it's a sore point with you Canadians
Click to expand...
Click to collapse
The Build Number indicates CleanROM 3.1 inheritance without anything else
Will I brick if I choose the wrong bootloader?
llcooljayce said:
The Build Number indicates CleanROM 3.1 inheritance without anything else
Will I brick if I choose the wrong bootloader?
Click to expand...
Click to collapse
Possibly if you flash the WRONG bootloader, but you won't if you flash the bootloader/TWRP package from the OP of the CROMi-X thread!
It contains the 10.6.1.14.10 bootloader (which is the latest for this tablet) and TWRP 2.6.1 which has been rock solid on this device.
During installation of the rom (if you go for CROMi-X) you will have the choice to install the WW or US version. The difference is mostly in the WiFi modules in the kernel I think, different channels are used in Europe and the US. But really, even if you flash the "wrong" version - you can just reflash the other one right on top of it.
If you go for a CM rom you don't even have that "problem". There are no regional versions for CM - and thousands of users are still very happy with it....
Read the CROMi-X OP carefully. Read it again - and then again until you're sure you understand the instructions.
Maybe a refresher would help. I wrote a beginners guide to flashing a rom on this tablet (most of it you won't need since you already have a custom recovery installed, but maybe it would be helpful to you to understand the process).
http://www.transformerforums.com/fo...ginners-guide-flashing-custom-rom-tf700t.html
For you only these steps are needed:
Flash the bootloader/TWRP package mentioned above
Reboot
Boot into recovery and do a Factory Wipe in TWRP
Flash the rom
Enjoy
llcooljayce said:
Problem is that I am in Canada and Canadians get either the WW or US version. From what I am reading, if I choose the wrong bootloader, I will brick my device. Any other way to determine the SKU version?
Click to expand...
Click to collapse
Boot into the bootloader menu (hold down Volume-left while turning on), it shows the bootloader version.
berndblb said:
The bootloader is universal. Only the firmware is regional.
Click to expand...
Click to collapse
The bootloader also has US and WW versions, but they are identical except for the displayed version string (at least I compared the 10.6.1.14.4 bootloaders back when they were released).
llcooljayce said:
Hey guys,
I am back to using the TF700T after about a year's absence from it. I've done a bunch of tweaks on it some time ago and can't really remember all the things that have been done. I know that the device is rooted and unlocked but couldn't tell you the ROM or anything else ... not that it matters.
I want to get this thing back up and running as fast as possible so I am looking for some suggestions on a lightweight ROM that has speed as its focus. I don't care if I lose everything on it and would like to go back to as factory of a feel as possible ... I'm even open to the OTA ROM if people believe it's the best.
Can someone provide some suggestions on where to start?
Click to expand...
Click to collapse
First post ever here at xda. My suggestion would be to start with flatline, to bricksafe your device. Then it is all about taste. Personally I prefer Cromi-X by sbdags.
Hello again,
I would like to install the least buggy Jelly Bean ROM onto my ASUS Transformer Pad TF300T. I have never rooted my Tablet before and I am on the latest OTA update by ASUS
Android Version 4.2.1
Build JOP40D.WW_epad-10.6.1.27.5-20130902
I very much would appreciate some hand holding on this whole process. I have signed up to the CyanogenMod website but as yet not had any replies.
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
I have never done this before and I have quite a bit of trepidation about the whole process but as it is, my official ASUS Jelly Bean operating system is laggy and the battery drain is exceptionally noticeable. The tablet can drain empty on Stand By within a couple of days. I have tried all the tricks to extend battery life, including charging Tablet and battery spereately, Cold Boots and Fresh installs but nothing helps.
Cheers
the lemming said:
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
Click to expand...
Click to collapse
If you ask 5 people about this you will get at least 10 opinions...
I choose not to vote on that part of your question.
I have never done this before and I have quite a bit of trepidation about the whole process
Click to expand...
Click to collapse
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
f69m said:
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Hello
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Are you able to post a link to a tutorial that will help me out?
Cheers
the lemming said:
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
Click to expand...
Click to collapse
You can see the version of your bootloader at the top left of the bootloader screen. It should match the last Asus stock ROM version you installed: 10.6.1.27.5 in your case. This is the latest bootloader available and should work fine with all up-to-date 4.2 ROMs. Read the first post carefully, it should mention, which bootloader versions are supported. No nee to update.
Note that flashing custom ROMs will not touch your existing bootloader.
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Click to expand...
Click to collapse
Have a look at nvflash flatline for your bootloader 4.2. It allows you to extract some files from your device. If you keep those safe, you are almost brick-safe, as you can then use nvflash to recover your tablet from most known issues.
http://forum.xda-developers.com/showthread.php?t=2545610
Are you able to post a link tersion o a tutorial that will help me out?
Click to expand...
Click to collapse
I am not aware of a guide specifically for flashing custom ROMs, but most ROMs should have good instructions in the first post. Anyhow, you can browse the stickies in the General forum. They have a lot of good information.
Sent from my TF300T using Tapatalk