Related
I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.
Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2
rkkaranrk said:
Stock GB with CWM > CM 9 flash twice first from red recovery and then again from blue > then JB.
Do a full wipe before and after all the flash.
I know u said u tried this way buy it did not worked for u just give it a try from scratch one more time.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
Thanks rkkaranrk. The one thing I didn't do in your instructions was a wipe before and after each flash. Instead I wiped once before I began. Could this be the problem? Is this a common problem? I've seen some mention the same issue in the Dark Knight ROM thread that said they have the same issue but wasn't sure this has to do with the ROM or the migration from GB to ICS in general.
It could be any thing which cause bootloop so its always better to wipe, I always do anand never faced any bootloops Just give it try.
Sent from my MB855 using Tapatalk 2
I'm going to give it a go today too. I've had a hard time convincing myself to leave Aeon though. It's been a rock solid / stable ROM..............
D-Trixxx said:
I was wondering if someone could detail to me a sure-fire way to make the jump from GB to ICS. I've tried twice now and both times I got stuck booting into a blue CWM without being able to load a ROM at that point. I was able to boot Aroma but after trying to recover from there I got stuck at the Galaxy S screen. Yes I followed the instructions very carefully. Is there a way to do this via Odin or Heimdall?
Any help would be tremendously appreciated.
Click to expand...
Click to collapse
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Thanks for all the replies so far.
@captemo: I followed the instructions in the Dark Knight thread exactly but maybe those instructions need to be updated because they never mentioned multiple wipes. There is no mention of getting stuck @ Galaxy S screen either but that isn't what happened at first. It kept bootlooping into blue CWM. It was only after that I tried to recover with Aroma that I got stuck, probably not the the wisest move on my part however.
I will try the Paranoid ICS build next since it sounds like you have had success with it and it looks like a good one. Just so I am clear on doing this can you list the steps you took to load this ROM? I noticed there are two variants, one with and one without the Aroma installer.
Thanks in advance!
The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.
Pony Express said:
The Aroma installer is nice but in my opinion, based on my experience and reports from others it is too problematic on the Infuse. Would really suggest not using versions with it, at least not on your first flash.
Click to expand...
Click to collapse
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
+ 10.
I had another thought, could Voodoo lagfix be the source of my issues? At the time I had the /Voodoo/disable-lagfix folder on my SDCard
D-Trixxx said:
Thanks Pony. I'll heed that advice and wait on captemo has to say regarding the steps he took to upgrade. I really don't feel like recovering a third time.
Click to expand...
Click to collapse
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.
captemo said:
WOW, somebody waiting for MY advice??? are you sure you havent been sipping on grandpa's cough syrup?
Pony i'm sure has more experience than myself and is merely expressing experiences that others and maybe he himself have had. truth is every phone is different and will react different.
i do like the Aroma myself. allows you to install some apps automatically.
i did nothing special than follow OP slowly and carefully to the T. doing this, i have never had problems flashing anything.
if i do anything special it is carefully choosing what i wish to flash. when lookin for new ROM, i go to the last page and start reading backwards. that shows me the most recent problems and issues people may be having. if its a problem i cant handle, i dont flash.
i am not taking away from developers here because they are ALL amazing and i wish i could do some of these things. as for the Dark Knight rom, i download, but never flashed. i just didnt think the development was progressing enough for me.
thats just me.
good luck hope you like Paranoid Android. i like the tablet mode, though print can be small for old eyes like mine just changed the font to something BOLD.
Click to expand...
Click to collapse
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.
D-Trixxx said:
The reason I wanted your advice was because you had successfully made the jump from GB to ICS. The Paranoid thread assumes you are starting from ICS so there are no instructions to go from GB to ICS even thought the ICS ROMs are still there.
Click to expand...
Click to collapse
anybody on ICS or JB as made that jump, obviously with sucess. since Paranoids development has jumped to JB there are a couple of small differences in install (GAPPS for ex.) the first 80 pages still deal with the ICS developments of the ROM.
even though the OP has changed to address install of JB, if you go past the first couple of pages and all the congrats of the new ROM, you will get to where any of your questions will be answered. Scott and team are very attentive and if you read read read, questions and concerns are all addressed.
if then you are happy with ROM and are dying to try JB, i think page 80 is where JB discussion begins.
The GB to ICS process should be the same for any rom. You can use cm9 or uniyumaporn to get to ics and then flash jb.
First, be aware once you are in ICS, your recovery will be filled with rainbows due to the lack of GB bootloaders (I'm assuming you don't have those).
1) wipe data, cache, dalvik (format /system is optional)
2) flash ics rom
3) reboot (Not "reboot into recovery")
4) you should hang at kernel splash (galaxy s screen).. remove battery and use 3 finger combo to boot into recovery.
5) wipe again and flash
Sent from my sweet & buttery Infuse
I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app
Goneeuro said:
I did this process two days ago. I went from factory att GB to ICS following the instructions for uniporn. Once I had uniporn fully booted and running I then rebooted back into CWM and followed the instructions in the cm10 thread.
The only thing to watch for is in the uni instructions. It still says to flash gapps. You don't have to do that now because they are included in build 40.
How did you update to GB by the way? That will tell us if you have GB or froyo boot loaders
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Hi Goneeuro,
I just saw your post but I did exactly what you did. Basically I read the instructions of a bunch of ROMS and decided to follow uniporns steps and it worked just fine including the gapps installation. Seems to be working fine still but I wonder if its a matter of time if I see issues.
I don't recall how I went to GB, its been so long ago but I don't have the rainbow CWM. Probably because I loaded them during a recovery.
Anyway all is good now. Big THANKS to all of you.
D
Dude thank you so much!
captemo said:
it does sound as if you missed a step. OP states you wll get stuck at Galaxy S screen.
you then pull battery and reflash again along wth the wipes.
i did wipes in recovery, then on second flash (in Aroma) did the full wipe version. install went exactly as described.
loving 99.9% of the Paranoid Android ICS. may want to take that for a test drive for a bit first beings they can be similar from what i know (which isnt much) from flasing one of first versions of JB
thanx for all efforts in development, biting my lip on flashing JB.
Click to expand...
Click to collapse
Really awesome I've been working on this for like 4 hours and all it took was pulling the battery instead of rebooting to get out of the bootloop. really appreciate it.
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.
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!
Hello guys,
I've been playing around with custom roms some time ago and I know some basics but since that time (that was about 1 year ago) i haven't been updating my tf300t at all.
Unfortunately my tablet started lagging a bit. I came with idea that new fresh rom might solve this problem so i came back to xda site where i found that a lot has changed since my last visit. My tablet currently works on 4.1.1 Android CleanRom Inheretiance 10.4.4.25, recovery i got installed is ClockworkMod v6.0.1.4. I belive this setup is little outdated. I'd like to install this rom
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
How ever all installation guides are created for clean Asus rom, i couldn't find any guide how to install it from the point I currently am not to mention I have no idea what actually bootloader verion I've got, I simply don't remember that. Guessing its 4.1 but how can i be sure that.
Could someone give me some tips ?
krakuus said:
Hello guys,
I've been playing around with custom roms some time ago and I know some basics but since that time (that was about 1 year ago) i haven't been updating my tf300t at all.
Unfortunately my tablet started lagging a bit. I came with idea that new fresh rom might solve this problem so i came back to xda site where i found that a lot has changed since my last visit. My tablet currently works on 4.1.1 Android CleanRom Inheretiance 10.4.4.25, recovery i got installed is ClockworkMod v6.0.1.4. I belive this setup is little outdated. I'd like to install this rom
http://forum.xda-developers.com/transformer-tf300t/development/rom-t2817919
How ever all installation guides are created for clean Asus rom, i couldn't find any guide how to install it from the point I currently am not to mention I have no idea what actually bootloader verion I've got, I simply don't remember that. Guessing its 4.1 but how can i be sure that.
Could someone give me some tips ?
Click to expand...
Click to collapse
Hi Krakus.
Since you are quite a bit behind on this I suggest you start from the beginning completely.
The first step would be to download the correct 4.2 Firmware. Unzip it once and flash it in your current recovery. Doing this will replace TWRP with the original stock recovery and you will need to start again.
I recommend my full guide for beginners located over at transformer forums http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
Most of the ones here don't have everything in one place or are outdated and one wrong move can turn into a very difficult situation.
Please give the guide a read and feel free to message me on either forum (I have the same username on both) we have quite a few very helpful XDA tf300 and tf700 members over there including some who develop and test new ROMs.
Good luck.
PS. ROMs have come soo far since back then you won't even believe it!