Database Info

B70 bricked - is there no way out?

Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?

Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev

After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.

Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.

Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?

The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?

df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?

My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.

Not getting anywhere with ADB, device is offline

hmm.. can you cold boot? just hold vol-down and wait?

df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.

Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.

I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.

Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.

Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.

Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day

Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.

[Q] Help with Recovery/Reboot Problem

Hi Guys,
I have the TF101 tablet and anytime I try to reboot it just stays at the first boot screen with the "Eee...." screen. Forever. If I hold down power and vol-down then hit vol up, it just stays there saying its booting recovery image but never changes. If I hold down volume long enough it comes to the factory reset/cold boot screen, if I choose cold boot it will boot.
I have rooted the tablet and had no problems previously, was able to flash roms and whatever else I wanted to do. Also, when I plug the tablet into my Windows XP machine, it does not detect the tablet in any way.
Tablet info:
Android Version: 4.0.3
with 2.6.39.4 kernel
I don't remember what rom its running exactly but I know its a version of ICS

Did you use ROM manager to update your CWM version? This sounds exactly like that, you can try running the bootloop-fix in my PERI tool (link in my signature) to fix, or manually run roach2010's fix found in his latest recovery thread. You definitely need ADB working, otherwise you'll need to Nvflash. (Nvflash Wheelie link is in my signature as well)

You are probably right i very well could have done so in rom manager. Im on vacation and dont have access to a pc right now but am going to try ur tool when i get back. Thx for the info
Sent from my Transformer TF101 using xda premium

Wait. I just realized. My pc doesnt even respond when i plug my tab in. How do i run PERI?
Sent from my Transformer TF101 using xda premium

Cold boot and install the drivers.

Ok Thing o Doom, you've been great pointing me in the correct direction, however I need some more guidance.
I have installed ADB, and when I cold boot the device and run adb devices I get nothing.
HOWEVER, if I just reboot the tablet, when it's stuck on the EEE screen, I do adb devices and it shows 123456789ABCDEFG.....
My computer doesn't see the tablet when it's plugged in otherwise, nor does any other windows PC in the house. Do you have any guidance as to what I can do? Please help, I need to get this thing running right.

You just need to get to a state where adb is recognized, and 'adb shell' command works.
From that point PERI should work.
Reboot when it prompts you to if it doesn't automatically (Probably won't being stuck on logo)

I can't seem to get anywhere else. My pc recognizes the tablet at the first boot screen but adb shows it as inactive. When I cold-boot the tablet it boots and loads fine but ADB nor any PC recognizes that it's plugged in. I'm lost.

Is "Enable USB Debugging" Checked in Developer Options?

[Q] tf101 CWM Bootloop - similar to most but SU is denying access

I used ROM manager to add Cyanagenmod 9.1 to my tf101 - I had scoured the forums on how to but somehow missed the warning to not use ROM manager. Cold Booting to OS works but I have no wifi access and turning it on only results in an endless "turning on wifi" message.
Anyway like others I am getting the CWM bootloop but when I try to use the shell commands:
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I'm getting an access denied error from superuser...so no access there from terminal emulator
I've tried easyflasher, viperMOD, oneclick, naked drivers, ASUS, etc...nothing works. I can Cold boot to OS and view the tablet as a storage device and load .zip files to the internal memory but the current CWM does not see the SDcard.
One issue which someone said might be complicating things is that I don't have an OEM cord so that may be hampering my laptop (Win7 64b) seeing it in APK mode...
assistance por favor!

I bought a 5$ chinese cable and it works fine, but that doesn't mean yours doesn't.
What are the symptoms when you try to enter APX?
Can you access ADB through a computer?
Are you sure you su'ed to root in your terminal emulator?

Lethe6 said:
I bought a 5$ chinese cable and it works fine, but that doesn't mean yours doesn't.
What are the symptoms when you try to enter APX?
Can you access ADB through a computer?
Are you sure you su'ed to root in your terminal emulator?
Click to expand...
Click to collapse
I have a new cable coming. No recognition on the computer trying ADB.
Yes I tried su command on terminal emulator dozens of times and definitely got the "superuser has denied access to terminal emulator" message every time.
I'm hoping the brain trust here will clue me in on what I'm missing.
Sent from my SGH-I897 using xda app-developers app

The CWM version on my tf101 is 5.8.3.4
My tablet is a B70
Anything else that might help? I'm really bummed about this since cold booting to OS is rather useless since wifi is not working, superuser is denying access to any and all apps.
I think I have read nearly all the threads on this CWM bootloop and so far nothing seems to be working to flash and new recovery, stock ROM, new ROM etc...
Updated SDK and Java dev to try and run ADB but SDK only flashes a command screen for nanoseconds and closes. I've run in the past for other devices and it's worked fine but not this time.

gt_bike said:
The CWM version on my tf101 is 5.8.3.4
My tablet is a B70
Anything else that might help? I'm really bummed about this since cold booting to OS is rather useless since wifi is not working, superuser is denying access to any and all apps.
I think I have read nearly all the threads on this CWM bootloop and so far nothing seems to be working to flash and new recovery, stock ROM, new ROM etc...
Updated SDK and Java dev to try and run ADB but SDK only flashes a command screen for nanoseconds and closes. I've run in the past for other devices and it's worked fine but not this time.
Click to expand...
Click to collapse
Try to enter APX mode on another PC and plug it in check device manager for anything with yellow next to it and let me know.

Tablet boot into "Purple screen" only (no fastboot possible)

Hi guys,
I hope, you help me.. I had twrp (don't know exactly what version), and I "migrate" to clockwork. I had problem with battery life, so I want to test another ROM. I installed some nightly build of CM, but after that, my tablet only boot into some purple screen, with rotating diamond (or what is it) and with green android robot in the centre. I never see this screen before, so I can upload photo somewhere.
And this is the end. It's not possible to go into recovery or bootloader, I can only reset device - if I press power button for couple of seconds (I tried much combinations in past 10 hours..). When I'm in that screen, I can connect with terminal, I can adb shell, but I can't send fastboot commands. If I list devices, I see only this:
C:\Temp\adb devices
List of devices attached
025e2a84285201a17 recovery
I can run into APX too, I tried to backup, but with no luck (maybe, I don't know how to do it, I tried only "Brks_rootkit_v8.exe"). I don't know which drivers I should need, I'm running on Windows 7 x64 - have apx drivers with this name: "NVIDIA USB Boot-recovery driver for Mobile devices"
So, do you mean, that my device is bricked completely? Or somebody can help..?
Thanks a lot..

If you can connect via adb shell, then most likely your tablet is not bricked. I have never seen a "purple screen" on my TF700 - could this be your recovery? Did you use any "reboot directly to recovery" or "factory reset" commands from your Android system?

Thanks for reply. I let device switched on and charging over the night, and at this morning it is booted to android! So now I don't know what to do. I have CyanFox 2.0.2 with KitKat 4.4.2.. but I'm afraid to do anything with this device, I don't know ho to get into recovery for example.
But, if somebody will have this screen too, let device working for a long time..
EDIT: I found what is that purple screen.. it is recovery: philz_tf700t_recovery_v6.12.8

TWRP Bootloop [SOLVED]

Hi all
I've had my Tf700 for a long time now. I've had it unlocked and rooted and had CROMBi before trying OMNIRom and then finally moved to KatKiss7.1 last year. All was well until today when, having enabled screen rotation, the background went a strange looking pink colour and would flicker back and forth to black. Then the WiFi started to misbehave so I rebooted it. But instead of rebooting, it just went into a bootloop.
I used power + VolumeDown to access the recovery mode and tried to get to TWRP (2.8.7.4) via the RCK option but without any luck. At that stage, all it was doing was resuming the loop. I tried booting into Android but got the same result. I tried for TWRP a few times and it always failed.
My next move was the Wipe Data option. Turned out to be a bad one. I hadn't done anything with the device in so long that I forgot about the "don't use the Wipe Data" instruction and I didn't read up before doing anything else. The device rebooted itself and then appeared to be going into TWRP - I could see the logo coming up - but my hope was short-lived as the device then proceeded to go into a bootloop where it displays the TWRP splash screen, but then reboots.
About the only thing I seem to be able to do is access APX, but I didn't know about APX or NVFlash until today when I started trying to read everything to do with anything that might help.
I run Linux on my PCs and have installed ADB so that I can try to use fastboot or adb. Neither seem to work in that nothing shows up when issuing either "fastboot devices" or "adb devices". But on a more basic level, nothing shows up in lsusb. The mouse is listed, as is my card-reader, but the TF700 isn't. The thing is, I haven't connected the device to a PC in a long time and the last time, it was windows, so I can't say for sure that the PC is definitely seeing it or not.
And so to my questions:
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup?
(I've seen instructions for the TF201, but can't see anything for the TF700)
Any help would be really appreciated.
With thanks,
Scouser27

I don't like the sound of this. This "background went a strange looking pink colour and would flicker back and forth to black" business makes me suspect a hardware failure. Maybe something got fried on the board - don't know.
1) Should the TF700 show up in Linux using the lsusb command when connected via the cable. (maybe I need a new cable? maybe I need Windows )
Click to expand...
Click to collapse
Yes, it should, something like this:
Code:
...
Bus 003 Device 009: ID 0bda:57af Realtek Semiconductor Corp.
Bus 003 Device 016: ID 0b05:4d01 ASUSTek Computer, Inc. Transformer Prime TF201 (debug mode)
Windows is not going to help you. If it doesn't connect in Linux it definitely won't in Windows....
2) If I got a new cable, is it likely that I'd be able to push a recovery image back to the device to allow me to start to rebuild?
Click to expand...
Click to collapse
Not unless you get a connection in either fastboot or adb
3) When APX is available, is it possible to transplant someone elses NVFlash backups, or whatever is just enough to get it running again so that I can re-install recovery and maybe reload an earlier TWRP backup? (I've seen instructions for the TF201, but can't see anything for the TF700)
Click to expand...
Click to collapse
No, nvflash files are device specific
If you cannot get it to boot into fastboot or get an adb connection - however briefly - it is a brick.
Install Hardinfo in Linux - it is very similar to Windows Device Manager - and open the USB page. Then reboot into TWRP. If you are lucky you may get a few seconds before TWRP loops where the PC has an adb connection and sees the tablet. If that works, follow this: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Still a tiny chance but better than nothing.
If bootit.ko kicks it into the bootloader and you get fastboot you can reflash the recovery, format data in fastboot and all that good stuff.
But my guess is: No dice
Try it anyway - good practice.
I still have a couple of TF700 lying around, one with a so so screen. If you want it, you can have it for the cost of shipping. You can either swap the screens or m-boards...
PM me if you want to go that route.
Good luck

Update
Thought I'd post something in case it's useful to anyone having similar trouble to what I described. This applies to my instance of TWRP booting in a loop and never exiting until the battery was flat.
Ensure your cable is working correctly.
If it's not, you won't see anything on your pc. (I use linux and nothing was showing up in lsusb or dmesg)
If this is the case, borrow a cable if you can or invest in one. I did - best 5 Euro ever.
Get the bootit.ko file that's mentioned in a few places such as here.
While you're getting that file, read the instructions there a few times and also have a look at the details over at this page (same one @berndblb links above)
Connect your tablet and boot it. As soon as you see the TWRP logo, it's time to try to run commands.
If you use linux, you can issue all commands at once like this:
Code:
sudo adb devices; sudo adb push bootit.ko / ; sudo adb shell insmod bootit.ko
Note the "/" after "push bootit.ko" - that's not a typo. If you leave it out, it won't work.
I don't know if sudo was strictly needed, but I wanted it to work and it didn't cause any trouble.
I haven't used Windows in a long time so I don't remember if you can do the same, but you could put the various adb commands into a batch file and run that. Don't forget to drop the sudo.
If it has worked, the tablet will reboot. You should now be able to get back to the bootloader.
Follow the fastboot erase instructions at this thread.
I found it useful to write the commands as
Code:
fastboot -i 0x0b05 erase boot
The last version of TWRP that I was using was KANG TWRP
I downloaded that, extracted the blob file and flashed it:
Code:
fastboot -i 0x0b05 flash recovery boot.blob
I used that because I wanted to install TimDuru's KatKiss 7, but you could presumably install whatever Recovery you wanted and proceed as normal.
And that's it. I flashed KatKiss7 and SU and all was well again:laugh:
Big thanks go to @berndblb for his help on this - If, like me, you didn't read his posts before, you really need to read them now. And maybe, just maybe, you'll be able to recover.
Thanks to all other contributors whose post's I've linked or whose work contributes to this solution - you've all just saved me having to buy a new tablet. Nice one!:victory: