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
Related
The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!
What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD
Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.
It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?
Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89
Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.
opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...
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.
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!
Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag
You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington
When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.
shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.
Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag