[Q] [solved] Won't boot - No ADB, no CWM/, no "wipe data", no nvflash (c20 serial)
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
After lots of searching and reading, I found a few help threads that offered suggestions for those unable to boot, but they all require adb. My understanding based on the adb tutorial is that it requries configuration within the Android OS, and for the device to be running, which mine does not. And from what I've read, the c20 serial number isn't compatible with nvflash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
edit: to clarify, I never setup ADB, which makes me think that solutions like this won't work: http://forum.xda-developers.com/showthread.php?p=25636698#post25636698
Hello cfbauer,
Did you try this driver pack? after 1st remove all you transformer drivers?
http://forum.xda-developers.com/showthread.php?t=1514942
If you install this, then you can check with adb if there is communication possible with your transformer. if you connect it, is there any life on your pc when you start your TF?
or volume + and power to put tablet in apx mode and see if then the apx driver installs. If it does then try the brks rootkit v7.1 to see if you can install cwm with this tool....maybe your refurbished TF is an old B40 to 70).
unless this is what you already did......
dont forget to disable spashtop and asys sync on your pc.......
Well I managed to get ADB setup, I think. I'm new to this, but when I attempt to boot into recovery, and do "adb devices" I get "0123456789ABCDEF offline".
I'm a little hesitant to try nlheiz's suggestion of brks rootkit v7.1 as it says it's for a serial number that's older than my device is. nlheiz, can you confirm this is safe? Or can someone else suggest an alternate method of getting my 2 week old Transformer to a useful state? I definitely appreciate the help.
-Chris
edit: I just read this
The only thing that differs between SBK1 tablets and SBK2 tablets is the use of NVFlash. SBK2 cannot use NVFlash, so if you end up botching both your recovery and your ROM, and cannot boot into either, then you are SCREWED, so I would suggest reading everything before attempting to mod your device if you are an SBK2 owner.
Click to expand...
Click to collapse
There is no emoticon to convey how sad I am right now
edit2: I'm looking at trying this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html since it appears to be able to fix the issue I'm having.
edit3:attempting the guide posted in edit2 is giving me a "error:device offline" on step 6 when I try the adb push command
edit4: I can't seem to download brk Universal Rootkit 7.1 as neither download link is working
Does anyone have a suggestion? I'd appreciate it. Or is my device totally dead and I'm just screwed?
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Thanks for your response. I get "0123456789ABCDEF offline" when I type adb devices when I boot into recovery mode, which isn't actually recovery mode since the system it hangs when I try to boot into recovery mode.
cfbauer said:
Thanks for reading.
I recently bought a refurbished Transformer with a serial starting with c20. I rooted with vipermod, installed recoveryinstaller and AOKP. After being unable to install CWM (I now know why) my device became unable to boot into recovery. Recoveryinstaller would not install either. When I attempted to normal boot, the device would just hang. My only option was to cold boot into linux, which worked.
I then attempted to "full wipe" in order to re-install recoveryinstaller for access to recovery. After doing so, my Transformer no longer boots. It sits at the "Android" splash screen, which I believe is AOKP still attempting to load. Recovery doesn't boot, full wipe only beings me back to the "Android" splash, and cold booting into linux also returns me to the "Android" splash.
Can someone point me in the right direction? I feel like I'm at a dead end here. Thanks a bunch.
-Chris
Click to expand...
Click to collapse
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
baseballfanz said:
How did you get AOKP ROM on the TF if you couldn't get CM to install?
Are you still on stock recovery? I know yo usay recoery doesn't boot but what does it do when trying to boot into recovery?
Doe sit hang or you get any message?
FOR ADB offline message, have you try a different USB port?
Click to expand...
Click to collapse
OMG it worked! I'm back baby! So exited. Thanks for your help! I suppose this means my Transformer is an SBK1. Nice.
To answer your questions if you're curious, I used RecoveryInstaller. It was CWM, but an older version, my mistake. I ran into the random reboots issue, but the version of CWM recoveryInstaller used wasn't compatible with Aroma, which was required to install a custom kernel.
I don't remember the exact text on screen when I try to load into recovery, but I believe it was something like "booting into recovery mode."
And yes, I did try a different usb port for adb, it didn't work. Thanks for the suggestion though!
Thing O Doom said:
Try NvFlash anyway, It can't hurt. Does ADB work at all?
Click to expand...
Click to collapse
Worked! Thanks for the heads up!
By the way, you don't need Aroma to install a custom kernel with AOKP. Since I utterly refuse to flash touch recovery (no ext-sd support) I can't use aroma. The classic way is to go grab the .zip of the kernel (I recommend Testymehics or Guevor's test kernels) out of development. Clear cache, then flash as if you were flashing a rom, no aroma required.
Related
Hi everyone, I've got a BIG problem with my sbk2 TF101.
I don't know why but I cannot access the Recovery. I don't know if it is actually installed or not, but I cannot access it nor I can flash it with CWM Manager or Recovery Installer
-When I restart, it simply stucks at the EEE logo.
-I cannot boot in recovery with any of the apps made for this;
-Every time I want to start the tablet, I need to start it using cold-boot (first, vol- and power, and then vol+), because it seems to be always starting in recovery.
-Without recovery I cannot flash a new recovery or a new rom, and I'm stucked with an AOKP cooked in the firsts days of may (I don't remember the name)
-I've got random and frequent reboots, freezes, and can't do something for more than 5 min because the tablet freezes.
-Standard voltages.
-My tablet is not recognized when I plug it in Windows or Mac OSX, didn't try with Ubuntu.
Please help me!
Thank you very much in advance for your great help.
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Thing O Doom said:
Don't do any wipes, as that may be unrecoverable. I don't see why recovery installer isn't working, you should have root. Sounds like some stuff is seriously messed up. You can try using flash_image to manually flash a recovery.img with ADB or with a virtual terminal, that's about all I can think of now. Find the boot.img, and flash_image files and put them on root of SD and run appropriate commands, more info should be in recovery dev sections.
Click to expand...
Click to collapse
First of all, thanks a lot for trying helping me.
The problem is that I don't know how to use ADB or wich commands should I use or where I could find the boot.img. Using a virtual terminal means running a trminal on the tablet? Can I use the internal memory instead of an SD card? I can confirm I've still got root, by the way.
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
wanzer said:
Please, could someone help me? I think I need to overwrite the recovery image manually, but I don't know how to.
Click to expand...
Click to collapse
Use PERI/my easyflasher tool to reflash recovery from nvflash.
Read more here:
http://forum.xda-developers.com/showthread.php?t=1688012
Hello guys, I have a problem with my tf101! is brick, and only goes with apx.provo easyflasher wheelie but returns error when it finishes loading bootloader towards the closed dell'applicazione!
sorry for the English, are Italian
I figured out that the OP had the ROM manager bootloop :/
Romyfra - is it a Tf101 Wifi-only or a Tf101G, if it's a Tf101 then you can use NvFlash to reflash it
I brick my wifi tf101 with serial bcoka ..., ICS v24ww 1.6e 4.0.3 I can not even come out with a wheelie! This is what I done, done correctly with the root easyflasher 0.4, after I stupidly installed netformer 1.6 (that idiot) and restart it disappeared with the cmw.ho riflashato easyflasher and end of proceedings, the tab will not light! is only apx, so no recovery! the problem is that when I start wheelie crash and does not pass to nvflash! is possible that the flash is corrupt?? as a last resort if you think I'll send you notice of changes in the RMA? ICS had no stock and cmw più.possono dump and see what happened or there is no trace?? thanks
Just picked up a TF101 and it had the Cryo (whatever it is called) OS with ClockworkMod Recovery v5.8.3.4. The OS didn't pick up wifi on the apps but it is on and logged into the router so I did a reset. Once I reset the TF101, i am stuck at CWM. It won't boot into any OS or anything else. I tried almost everything I found googling (this site and others) but nothing works. I did, however, got the TF drivers for my laptop so I can connect to it but I can't get the USB debug option on (of course).
So what are my options? how do I "unbrick" this thing? is this what some people call it soft-brick as it does boot but there just isn't any OS in there? I tried to put the OS zip file from Asus on a MicroSD but when I went to install zip from sdcard, it i can't get to the microSD to install it. it doesn't find it at all.
what can I do? what are the steps in unbricking this thing? I got this for my dad for father's day (chinese father's day which is TODAY...) and would like to get it to him.
Thanks in advance!
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
baseballfanz said:
Is it in a CWM boot loop? Meaning when you reboot the tablet it keep going back to CWM?
Try this to see if you can boot OS.
Turn off tablet
Push and hold Vol down plus Power button
Wait till you see a screen that give you two options
Wipe data or Cold boot Linux
Choose Cold boot to boot into OS.
Click to expand...
Click to collapse
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
chivas228 said:
still stuck in CWM. I held it down and no options came up except to push vol +. tried both and regardless of what i do, it just goes right back into the CWM menu. it seems there's no OS to this tablet anymore?
Is there something I can do via USB cable to flash a ROM in there?
Click to expand...
Click to collapse
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
baseballfanz said:
If you have ADB working, you can push a ROM file to internal memory and flash it.
Alternatively you can NVFlash a compatible ROM.
Click to expand...
Click to collapse
Sorry to sound ignorant but what's ad and what command (extra code after the .exe) do I add afterwards?
I'd try to flash a ROM via NVFLASH.
You may download it from here, but you must know if your TF101 is WW version, US version or any other. You must also know if your device is SBK1 or SBK2. That depends on the serial number. For example, mine starts by B50 and it's SBK1. If yours is SBK2 then you'll have to take a look at wheelie. If not, take a look here.
http://forum.xda-developers.com/showthread.php?t=1620758
However, I'm not responsible for any damage your device might suffer.
Take a look at that and tell me
here's the endall- easyflash version 0.8.3b whitekidneys just updated it and saved my brick. it'll save yours too. just install it on your computer, along with naked drivers 0.7, put the tf in apx, and flash. literally that easy.
Follow the link to easy flash / nvflash and follow the steps...
http://forum.xda-developers.com/showthread.php?p=26893961
Sent from my Transformer TF101 using xda app-developers app
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
thefunkygibbon said:
i'm getting the CWM bootloop too, but i can do what was mentioned and get into the OS although it still boots into CWM on the next reboot. what can i do to fix the bootloop? not really fancying reinstalling yet again. but if i have to...
Click to expand...
Click to collapse
Try Install different recovery... download and flash the new recovery through CWM..
Sent from my Transformer TF101 using xda app-developers app
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
You cant't wipe data from bootloader menu, If you do that, you will get unrecoverable brick.
Sorry I believe I mislead you -> I wiped data from within CWM.
Anyway, I used this thread:
http://forum.xda-developers.com/showthread.php?t=1757077
I went back to stock and I think i'll stay there for a little while longer, this process made me nervous (I've rooted my thunderbolt, droid DNA, galaxy tab 2 7" and my friends phones) so anyway I believe I installed the wrong CWM and that caused errors trying to install a JB rom on a ICS CWM... If you have any insight let me know...
undergfx said:
Hi guys,
So this is my first post but I've been on XDA for a long time. I've been looking for an answer to this problem, and I haven't been successful in finding a post that regards to my situation...
Ok so I just got my tablet today. I upgraded to JB and then I unlocked it using the asus unlocker. I attempted to install TWRP, but when I use .blob files and attempt to load into recovery it didn't work. Anyway, I looked around and I installed CWM recovery instead.
I installed v5.5.0.4 following this guide:
http://theunlockr.com/2012/05/25/how-to-install-clockworkmod-recovery-on-asus-transformer-tf300t/
Now, I notice it's written back in may of 2012 aka before jelly bean... anyway so I installed this using fast boot, and booted into recovery and it worked. I believe I installed the ICS version of CWM. I tried to install Clean Rom v3.3 and I just get bootloops. I can still boot into fastboot and clockwork mod fine.
I tried to install v6.0.1.4 via this thread http://forum.xda-developers.com/showthread.php?t=1846554
But once again if I boot into recovery it just does nothing and reboots after a few seconds.
I re-installed v5.5.0.4 and I can wipe data/install everything just as I normally would, and I still have access to Fastboot. Can I get some help on how I can 1 install the correct CWM and 2 install a working rom? I don't think I bricked my device just yet since I can still flash in fastboot etc.
Thanks guys!
Click to expand...
Click to collapse
My suggestion is to flash the latest stock JB blob.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Once you get it sorted then flash the latest twrp for jb.
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Edit:
Ah didn't see your post. I did what you recommended, and actually, while my device said it was on 4.1.1 JB, when I hold pwr/vol down I see a completely different menu now than last time, so I wonder if perhaps my OTA didn't correctly load everything from the firmware update hmm...
undergfx said:
Now, when I try flashing blobs and I go to boot into RCK (I believe that's the term...) it just reboots the tablet instead of booting into recovery.
Android software is out of my element, if this was some C (somewhat similar to C) or Matlab I would better understand (I'm a senior Mechanical Engineer in college)
Click to expand...
Click to collapse
The same way you flashed cwm.
Windows? Start - in search type cmd - press enter
In the cmd window cd to the directory with fastboot.
Hook cable between tablet and usb port on computer.
On tablet hold power and volume down till you see the bootloader menu.
Down volume till you are at the usb symbol - then volume up.
This should put you into fastboot mode - use the commands above.
Wait till the first command completes before you give the second command.
[INDEX][04 Feb 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc. You will find the stock firmware here as well as most other needs.
You will have to unzip to get the blob which you should place in the directory with fastboot.
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
undergfx said:
Thank you very much.
So after flashing the most resent blob, I successfully installed CWM recovery and successfully flashed a rom. I'm not sure what the issue was before. Thank you for the help! much appreciated.
Click to expand...
Click to collapse
You're welcome.
Good Luck!
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??
lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?
nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays
So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Hope this worked
s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?