So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
Related
Well, here's what happened:
After flashing some different ROMs (which has been no problem in the past) my phone started acting weird...I don't really know how to describe it, it randomly crashed or didn't react, sometimes I couldn't even turn it off so I had to remove the battery and reboot it. Suddenly, the only ROM that I could flash was this one: OTA 4.04 The problem was that I got a lot of force closes so I couldn't really use it. After I spent hours on google and tried to fix the problem, I came across Odin. It seemed pretty easy and I followed a tutorial to set my Nexus back to stock Gingerbread.
Odin seemed to work perfectly and my device rebooted, but I am now stuck on the bootlogo (Google screen with the unlocked sign) and can't do anything else.
Any help, please?
Search around for "fastboot factory images" and flash one of those. Download from official google website. Note that it'll remove all apps, data, etc. Only files on the "sdcard" will be kept.
I tried to flash gingerbread and jelly bean images, following this guide. Didn't work though...it may be worth mentioning that somehow adb does not recognize my phone, fastboot however does. It says in the guide that you don't have to use adb necessarily, so I'm a bit confused that it didn't work...thanks for your reply anyways.
any more advices?
Do you actually know what you're doing? Odin socks, use Cwm recovery for flashing roms. It seems that you make flashing mistakes, dirty flashing etc. Also apps crashing is resolved with fix permissions. Read the big faq for correct flashing instructions
Sent from my Nexus S
b0ld said:
I tried to flash gingerbread and jelly bean images, following this guide. Didn't work though...it may be worth mentioning that somehow adb does not recognize my phone, fastboot however does. It says in the guide that you don't have to use adb necessarily, so I'm a bit confused that it didn't work...thanks for your reply anyways.
any more advices?
Click to expand...
Click to collapse
do this:
fastboot flash bootloader (bootloader.img)
fastboot rreboot-bootloader
fastboot flsh radio (radio.img)
fastboot reboot-bootloader
fastboot -w update (image-blabla.zip)
one more thing: ODIN ISNT NECESSARY FOR NEXUS!!
Where did you find (factory) odin images for the Nexus S, I didn't know they're available this device. In any case Odin probably aren't meant for Nexus devices.
Dont even think about using them!!! We have to stop with this! Odin was made for samsung devices but for those made by samsung not by google! Google phone use fastboot for that, odin can screw up your nexus
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
xxboarderxx said:
Hey Everyone
I've done quite a bit of reading and nothing seems to quite fit the issue I am having so I thought I'd post and seek help.
Some background info...I've unlocked the bootloader and also generated the NVFlash files when I first bought the tablet. It was running the stock ICS Rom. I had CWM Recovery and it was rooted.
I wanted to try a new ROM called BlueAndroid as I read it was really good. I followed all of the instructions and flashed from the sdcard. It appeared successful but when I went to restart the system, it kept boot looping at the ASUS Screen. Then I thought I'd just go back to what I had before by restoring it from CWM Recovery but to my surprise, it didn't work and now it isn't even looping, just stuck on the ASUS Screen.
I tried to fastboot CWM and TeamWin Recovery. Although they were both successful writes to the tablet, they won't load. I can only get to the fastboot screen where it shows the 'wipe data' and 'USB icon'. There used to be an Android Robot icon too but it is gone now.
I even tried to NVFlash. It worked but I'm still stuck on Asus Screen.
Lastly, when I select wipe data, it erases and the Team WIN logo appears for a split second and then it goes back to Asus Screen.
I keep reading something about the possibility of incorrect partitions but I have no idea what that means.
Any help would be greatly appreciated.
Thanks
A
P.S. In the meantime, is there any way to shut the tablet off? I've tried holding the power button down but it just reboots.
Solved: Used blobunpack to get bootloader files from the stock ICS ROM (blobunpack the blob file from the ROM). Then used NVFlash to download those files to tablet. Hope this helps others with same problem. I can elaborate more tomorrow...it is really late and very sleepy but relieved!
Click to expand...
Click to collapse
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
I think you could mean a kind of recovery loop: There is a file called "command" on the cache partition which causes the recovery image to boot. But if the recovery is broken then it will not empty cache. The recovery will boot but does not update screen (showing just boot splash). On the next time it will boot again ...
Please be just carefully: "wipe data" in the fastboot menu will create the "command" file.
ScottBroker said:
I had the same problem. I think it is bricked. I called ASUS, told them it was unlocked, they told me to ship it to them and they would fix it. I boxed it up, and shipped it off. Could not turn it off. Hope the box did not catch on fire.
Click to expand...
Click to collapse
Sorry...if I could have made this attempt last week, I may have been able to help you then. :sly:
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
opethfan89 said:
OP, where were you a week ago when I "bricked" my tablet?
I had the -exact- same issue, btw, although with different circumstances. I can verify with 100% confidence that using NVFlash successfully restores the ICS bootloader. How I understand our situation is that when you tried to flash a ROM or anything based on JB over an ICS-device, it confuses things and causes issues. So you basically have to restore the ICS bootloader to get any progress.
But you hit the nail on the head describing my problem, although I would have ended up typing a dissertation to get across the same information you did. So touche on that
I used the same steps, as well. I blob unpacked my ICS stock firmware (.29 version from ASUS website). I used the boot.blob from my NVFlash files, along with the files I unpacked from the stock blob and flashed them over NVflash.
After a week of a useless tablet, I'm up and running.
I'm going to write a guide about my experience for anyone else and I would welcome your input sir.
Click to expand...
Click to collapse
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
xxboarderxx said:
Well, I'm sure you learned a lot during your experience of trying to get it working again - I know I did so that's a +1. I wasn't worried that my tablet was bricked because I was told that if I had the NVFLASH files, I could recover from anything save dropping it and breaking it that way. I was also able to connect to the PC using fastboot and adb so that was another positive.
If you write a guide, that would be great as while I was trying to piecemeal information together to get my tablet running again, there seemed to be dozens of people out there with a similar problem and being unable to get it working again and having to send it off to Asus. Would probably be a great contribution.
The one thing I learned though this ordeal is that the stock bootloader needs to be the same as the custom ROM before installing. I wish ROM guides would tell you this REALLY important fact...
Cheers
A
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
I was smiling as I read the first post, but this is going to come in real handy if I nuke my bootloader. Thanks. I wish I had gotten to this first, heh, I could have told you don't flash a Jellybean ROM over an ICS bootloader, it won't boot.
Good information to have though. Thank you!
opethfan89 said:
Really? I didn't know that....that might explain why none of the ROM's I'm flashing will work.....
At this point, I'm just going to upgrade to the stock JB firmware and flash the new JB roms. I've got my NVFlash ICS files (which saved my frickin life) so I have no hesitations about doing anything, and I really understand the NVFlash process well having bricked myself so hard.
My guide is mostly done. I spent more time writing it than I did focusing on schoolwork so I will finish it up hopefully this weekend. It's rather long and quite details so I hope it will help everyone.
Click to expand...
Click to collapse
:good:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
You can do it if you have a custom recovery already flashed like TWRP or CWM. But I agree with you - after you start having a basic understanding of Android customization, there's no reason why you would want to use 'wipe data' from the volume down+power.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
elesbb said:
Just giving some advice to those who may jump in late, DO NOT use the "wipe data" method from holding volume down. This method relies on Asus' stock recovery image. And it somehow screws everything up when you do it on a non Asus' recovery.. Not sure why but dont ever use that
Click to expand...
Click to collapse
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
opethfan89 said:
That finally explains why it wouldn't work, thank you for elaborating on that!!
Is there a guide on how to get the stock recovery back, or does it automatically get flashed when you flash stock?
Click to expand...
Click to collapse
Automatically gets flashed when you flash stock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
If you are in recovery loop you cannot go into the fastboot menu. The only way to get the stock recovery back is to use nvflash.
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Foolmax said:
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Click to expand...
Click to collapse
I can only shed a tiny little light on your problem since I am not familiar with Androwook.
JB 4.2 defaults to fastboot mode if and when you boot into the bootloader. So in 4.2 you only have the icons for recovery, Android and Wipe Data.
To use ADB you have to be booted into the rom. Actually, I have read with the correct drivers yo can also use ADB in recovery, but I have never tried that myself.
Just ignore the 'key driver not found'. Every TF700 displays that message when you boot into the BL.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
AndroWook 2.2 works fine on my TF700 and technically it should on yours. It shares the same base as CROMi-X 4.x. Have you tried CROMi-X to see if it boots?
I think flumpster recommended you do a clean install for AndroWook 2.2 as well have you tried that? Also which bootloader are you on? I'm reluctant to recommend TWRP 2.6 just yet as users have reported some problems with it, so I'd also recommend you drop back down to TWRP 2.5.
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Foolmax said:
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Click to expand...
Click to collapse
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
sbdags said:
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
Click to expand...
Click to collapse
It'll be done tonight as soon as I get home, thanks for your time, I'll keep you posted ASAP.
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Foolmax said:
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Click to expand...
Click to collapse
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
sbdags said:
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
Click to expand...
Click to collapse
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Foolmax said:
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Click to expand...
Click to collapse
Cheers mate for the donation! Glad you got it all sorted!
Darren
I have been using chromi-x 5.2.4 w/ rom2sd for a while http://forum.xda-developers.com/showthread.php?t=2425383&page=178. I just realized today that my tablet's TWRP wasn't working properly and if I were to pull my sd card, I couldn't boot from my internal storage so I decided well I might as well try the new 4.4 http://forum.xda-developers.com/showthread.php?t=2686235. So I see it needs the newest bootloader (which is already on there I am using 10.6.1.27.5. but I realize I am running twrp 2.5.0.0. I go to the website and quickly update it TO THE JB VERSION....NOOO WHY DID I DO THAT! ( o well too late now).
I can get my tablet to recovery, but nothing will mount. Now i try to go into fastboot and neither of my comps that previously recognized the device are able to do anything (will not bootload from sd or from internal). Can't get my tablet to appear after dling univeral drivers. Anyone have the asus drivers that I can dl? Saw a few posts about unzipping two packages. I could only find the suite on the website and that is not recognizing my device. My comp tries to find them, but it fails by the time my tablet bootloops. I believe I can dig myself out of this and will read in the meantime, but I've already spent too much time on this tonight and the US lost in the last minute so I am not a happy camper!
If i type fastboot devices, I do see my serial (which I thought was a good sign and it would be a quick fix just flashing the new twrp). Doesn't recognize any commands in this post like I was trying to follow http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
[UPDATE] since twrp was asking for a password after flashing so many different versions (not sure where it went wrong) I decided to flash cwm recovery and all was well. Wiped everything. Got CM up and running in no time. Now onto crombi-kk to try it out.
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!