Database Info

[Q] How bad did I brick my Kyros 7005??

Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe

can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.

I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.

do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.

Solution: Gtablet can not power on or reboot after nvflash

I hope my post will help somewhat those buddies who had the same problem or who will probably have this problem in future.
I had the problem that my gtablet couldn't power on after I did Nvflash. I'd been frustrated in the past week for searching the internet to find the way out.
The similar problem that tcrews had. (http://forum.xda-developers.com/showthread.php?t=903684)
Also some posts I browsed:
http://forum.xda-developers.com/showthread.php?t=999287
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
http://forum.xda-developers.com/showthread.php?t=927006
http://forum.xda-developers.com/showthread.php?t=971608
http://forum.xda-developers.com/showthread.php?t=938706
I am grateful to tcrews and a lot of other buddies for their inputs which saved me lots of time, though i didn't find a right solution from their posts. Acidburn89's solution in tcrews's post (page 9) didn't work out for me either.I don't know whether tcrews solved his problem in acidburn89's method.
I tried all the methods I could find and nothing worked out for me. The only way I can turn the tablet on is to follow tcrews's post on rebooting the tablet by using nvflash (nvflash --bl bootloader.bin --download 9 recovery.img --go)
Some background of bricking my gtablet:
1.my gtab had CWM0.8.and was running rom "zpad clean 3.0" (before that it was TNTL, not any problem)
2.one week ago, I was trying to flash a rom from a chinese website, which was modified from the official malata zpad rom. This was the problem started from. After flashing (nvflash method),the tab was rebooting and stuck at "Tegra II" logo and couldn't never start with the new rom. At this moment, i could still power on and off the tab.
3.next I flashed my tab by following this link (http://forum.xda-developers.com/showthread.php?t=861950) After flashing it, the tab couldn't not reboot, and could not power on. Every time I pressed the power button, it just went to the APX mode authomatically
(with black screen).Only using the above-mentioned method (from tcrews) I could start the tab.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
2.Copy recovery-stock.img into the nvflash folder.
3.Start the tab by nvflash (tcrews' method)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
I tried this method with and without CWM. Both worked. So don't worry whether you tab has CWM or original recovery. My advice: flash your favorite rom using sdcard method instead of nvflash. If you want to nvflash it, save all the files we have used for possilbe repeation of our above job to get your tab back to life!!
I've received a lot of information and help from xda-development before, and hope my first post could contribute to our community a little bit.

Just noticed that idocinthebox has the same idea of correcting recovery.img in this post:
http://forum.xda-developers.com/showthread.php?t=994046

Master
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)

Well done! If this helps anybody mash the thanks button ;-) ^^^^^^^^^^^

Exact same issue
Can you provide your stock update.zip file? I have not been able to find a file that works for me. So far I have repeated this process many times with many update.zip fules but its still wont start on its own.

I can fin a update.zip.... can you posted here?
Thanks.

I follow this thread but still my gtab is power on APX (only). I was using the stock 3588 and went to the new 4349... start to having issues decided to go back to 3588 using the nvflash. it worked at the first time (until I had the tablet on) As you turned of and turned on, just a black screen (apx) and the only way to get it back is running the nvflash again but if I turned off have to do it again.
Please help!!!!
I can't figure it out on my own.

The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/show...54&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
*** could you posted your original (stock rom) update.zip? The one above mention is not in zip format. I did a zip format but still not working.
2.Copy recovery-stock.img into the nvflash folder. (i did that)
3.Start the tab by nvflash (I did that)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
*** the only way I could put the update.zip in the internal sdcard on the tablet was after nvflash the tablet power up, then I plug a usb drive (with update.zip in it) and copy to the internal sdcard... i did not plug the tablet to the computer.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
*** I did that the same way above mention from a usb drive.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
6,7,8,9,10,11 **** I did all but at the end still my tablet only work with nvflash unless I never turned off!!!

that download is corrupt...
Err it's the img ranamed... by bad..

Naysses and jettajon:
I uploaded the original update.zip I extracted from my G-tab. Try it to see whether it can help u.
w w w.mediafire.com/?fywhca6fi514toq
(remove space between "w"s)

I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly

Citi said:
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Click to expand...
Click to collapse
I ran across this post http://forum.xda-developers.com/showthread.php?t=1010659 which says that the BCT part of the nvflash isn't the same for all the GTablets and that's my experience.
I couldn't get nvflash_gtablet_2010110500.zip (from the dropbox repository of nvflash files) to work, but nvflash_gtablet_46_2010112600.zip worked fine.
The problem was that I couldn't get CM7 installed on my GTablet, but then I hacked the gtablet.cfg file to swap partitions 7 and 8 by merely cutting and pasting the partition 8 (name=OGO stuff) and putting it before the partition 7 (name=BLO stuff) to match the order of the gtablet.cfg in nvflash_gtablet_2010110500.zip.
Now CM7 has installed and seems to be working fine for me.
BTW- I didn't nvflash the CWM recovery since I was trying to minimize the number of things I was messing with. I assume it'll work, but I already had CWM installed on the internal emmc (SDCARD2) so really didn't even need to nvflash it.

Nope, I have tried both files and neither worked for me

kaluna00 said:
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Click to expand...
Click to collapse
guobug you are a hero
same thing happened to me
and because of you it works!!!
( followed the steps and used your updat.zip)
BUT I have another problem
when I tried to install CW
it says "Can't open sdcard/recovery.log"
now I dont know what to do
because I want to install another rom
I think there is something corrupted in the device after apx boot loop

You are a life saver. Worked like a charm. Have been reading through 50 million threads the last 3 days, and happened to find this one. Absolutely amazing. Thanks.

In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!

guobug said:
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
Click to expand...
Click to collapse
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.

BrandonJay21 said:
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
Click to expand...
Click to collapse
That error means the command 'nvflash' is not in the path for the windows command line.

Where do you type the DOS command at? Thanks.

when I hold the volume up and hit enter on the keyboard I get a bad command prompt. What am I doing wrong?

[Q] Bootloop, Rom Manager, no restore possible

Can be closed!
Oh man, I read the warning too late.
I had a few issues installing Rayman's 4.2 on my TF101 with clockworkrecovery v5.x (Error was not able to open /cache/recovery/** or so. Shouldn' t matter anymore).
Call it stupidness, I thought using the actual cwm version would solve my problem.
As you can see, it did not.
I flashed v.8, the addons and the gapps. No errormessage (did not get any with the older version either).
But it is stuck in a bootloop.
Not too stupid, I did a backup before - sad but true I can't use it. (E:unknown volume for path[/sdcard/]\\E:Can`t mount /sdcard)
Of course I am not able to flash any other rom from internal sdcard. (not even think about external sd!)
I can push a rom to sdcard via adb push, but can`t use it (>choose zip from sdcard \\ E:unknown volume for path[/sdcard/]\\E: Can`t mount /sdcard/) and after reboot the rom dissapears.
Pushing to /data/media is not possible, as media does not exist.
Fastboot seems not to be a possibility, as I can`t boot in bootloader mode... (but tell me, if I am wrong!)
So if anybody knows a solution - I would be so happy!
Update 1:
I followed these instructions:
www tabletroms.com /forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
I installed Nvflash on my linux pc.
APX mode works, I just had to do what people told me to. (Press Vol UP(!) and Power Button)
Connect via USB.
Then run sudo ./download.sh
Everything looks fine, but then again: An error occurs:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Update 2:
I tried another version. For some reason, my TF is not WW, as I thought than US...
Everything is fine, I am happy again. Maybe it helps anybody? And if not - I had my xda rubberduck.

[Q] Won't go into Recovery

I'm trying to root my Photon Q 4g lte from Sprint. I've gone through the motorola unlock procedure and had success. And I have the USB drivers on my computer and have connected the USB to the phone in order to flash the CWM image to the phone. Also the superuser is copied onto the built in SD card. I seem to be stuck at the #7 on this page <http://www.android.gs/how-to-root-motorola-photon-q-4g-lte-xt897-cwm-recovery-installation-guide-included/> which is where I hold vol up & down & the power button. When I come into the bootmode page that has several options include AP Fastboot, Recovery, and Normal startup, sometimes I can scroll down to AP Fastboot but there's no way to "select" it like the instructions say to do. And before I can really do anything more than scroll to it, the Motorola warning message pops up saying the phone is unlocked and might be endangered, etc.... Then the phone does a normal reboot.
I have been able to get into recovery by an alternate method of powering down phone, and holding the volume up and power button at the same time. The first thing that pops up is the Motorola warning message after which the screen goes to the android figure laying down with a red triangle over him. At this point I push power and volume up & down at same time and recovery opens. The top lines says I'm in Android System Recovery <3e>. This page is black with blue lettering. The next line says Android System Recovery Utility. Under that I have options to Reboot, or Apply update from external storage, or wipe data/factory reset, or wipe cache partition, or apply update from cache. When I select 'apply update", the list showing folders and files on my SD are shown. At the top is SuperSU-v0.94+.zip. So I select that and it beins to open the update package and verify update package. Then the thing "E: failed to verify whole-file signature and E: signature verification failed" and so the installation of SuperSU won't flash.
I figure I'm doing something wrong: misreading something. Can someone help? Thanks. p.s. my phone has the latest software update from motorola.

In boot mode, pressing volume up button is the select button
Sent from my XT897 using xda app-developers app

Aaargh! said:
In boot mode, pressing volume up button is the select button
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I tried that and selected ap fastboot, and it went to what I described above. After trying to flash SuperSU, installation aborts.

Step # 6 in the instruction you pointed out can be done in the following way:
"Boot it into Bootloader mode by pressing Volume Down and Power buttons"
If you do this way you will be booted in fastboot mode and need to skip step #7 and proceed with step #8.
Please note that SuperSU-v0.94+.zip can be flashed only with CWM recovery and not with stock Motorola recovery (i.e. Android System Recovery <3e>).
So you need to be success with CWM recovery flashing before try to install SuperSU-v0.94+.zip.

Thanks A1936, I'll give that a try. I do not understand why CWM image didn't flash. I'll restart the process and try again. Some of the instructions are confusing for example it will say that the CWM image needs to be in the 'fastboot' folder. I don't even recall making a 'fastboot' folder though I do have the 'fastboot' app in a sub folder under sdk/tools or platform-tools. So that was confusing. I just moved the cwm into the platform tools folder. It's trial and error, I suppose. Thank you! I really appreciate your guidance here.

CWM Boot
OK
I have been through this at least 50 times. I think part of the problem is after it boots the phone it over writes cwm. My phone does exactly the same thing sometimes. I will try and delete the recovery.sh file and see if I get different results
It can be kind of frustrating.

MrSing said:
OK
I have been through this at least 50 times. I think part of the problem is after it boots the phone it over writes cwm. My phone does exactly the same thing sometimes. I will try and delete the recovery.sh file and see if I get different results
It can be kind of frustrating.
Click to expand...
Click to collapse
Please let me know if it works and what you did. Thanks

I'm unlocked but can't get root. The CWM image doesn't seem to have taken. By the random process of pressing keys above, I can get into Android Recovery which allows me to wipe data and cache. But I can't run the SuperSU because I don't have the CWM.
Now I seem to be stuck where pushing vol up/vol down + power just gives me the warning screen saying the device is unlocked and bad things could happen.
By doing the power up + power I get first the warning, and then I get the dead android (red triangle). From here I can press power + vol up/volume at same time and I get the Android recovery. From here I am able to "wipe data/factory reset" and I can wipe cache partition. I can also reboot. If I try flashing the SuperSU from the external storage, I get a message that installation failed.
I'm at a loss. Can you help?

motofailt2go
Has anyone tried this? It looked promising but it's failed to get me root. Here's the message I get: At one point it says the exploit failed and the that it's complete. But I get no root. Any ideas what's going on?
Success
[*] Preparing for exploit...
1559 KB/s (22364 bytes in 0.014s)
3960 KB/s (843503 bytes in 0.208s)
4135 KB/s (1867568 bytes in 0.441s)
4478 KB/s (64208 bytes in 0.014s)
[*] Please trigger a bugreport on your phone by pressing
[*] Volume Up + Power simultaneously. If successful, your device
[*] will vibrate. Make sure this vibration is distinct from the
[*] vibration that occurs when you turn the volume all the way
[*] down. Press enter once you have successfully triggered a
[*] bugreport.
Press any key to continue . . .
[*] Getting root...
[*] This may take a minute or two.
[-] Exploit failed.
[*] Cleaning up...
Success
[*] Exploit complete!
[*] Press any key to reboot and exit.
Press any key to continue . . .

I got into CWM recovery!!!
OK, I screwed up earlier because I'm a tech wannabe. I was confused about the various folders and file names. Under the SDK folder there was a platform-tools folder and a tools folder. And in those folders was a fastboot app. The directions are sometimes confusing or misleading. For example, see this <http://www.android.gs/how-to-root-motorola-photon-q-4g-lte-xt897-cwm-recovery-installation-guide-included/>
#2 says to download CWM and place it in the 'fastboot' folder. Well when I downloaded fastboot, it had it's own folder on C drive and it had a subfolder called fastboot. So I put the CWM image there. But then....
#9,10 says to go to the SDK/platform tools folder and open a command prompt from there. Then in the command prompt, type, "fastboot devices". This works because there's a 'fastboot' app in that folder. So far, so good because it reads the devices serial number and I'm cooking.... But then...
#11 says to now type 'fastboot flash recovery cwmrecovery.img'. But it doesn't work, it fails. Why? Because earlier it told me to put the CWM image in the 'fastboot' folder - which isn't the platform-tools folder.
The answer was now that I had the device unlocked and fastboot was recognizing the device, I opened a new command prompt in my 'fastboot' folder and then typed: 'fastboot flash recovery cwmrecovery.img'
Bammo! CWM recovery opened. I flashed SuperSU from the phone's external card and then rebooted. Root Checker app confirmed that now I have root. Thanks everyone for helping.

Failtogo
discipler said:
Has anyone tried this? It looked promising but it's failed to get me root. Here's the message I get: At one point it says the exploit failed and the that it's complete. But I get no root. Any ideas what's going on?
Success
[*] Preparing for exploit...
1559 KB/s (22364 bytes in 0.014s)
3960 KB/s (843503 bytes in 0.208s)
4135 KB/s (1867568 bytes in 0.441s)
4478 KB/s (64208 bytes in 0.014s)
[*] Please trigger a bugreport on your phone by pressing
[*] Volume Up + Power simultaneously. If successful, your device
[*] will vibrate. Make sure this vibration is distinct from the
[*] vibration that occurs when you turn the volume all the way
[*] down. Press enter once you have successfully triggered a
[*] bugreport.
Press any key to continue . . .
[*] Getting root...
[*] This may take a minute or two.
[-] Exploit failed.
[*] Cleaning up...
Success
[*] Exploit complete!
[*] Press any key to reboot and exit.
Press any key to continue . . .
Click to expand...
Click to collapse
This has not worked since the Sprint US 7.7.1Q-6_SPR-125_ASA update.

MrSing said:
This has not worked since the Sprint US 7.7.1Q-6_SPR-125_ASA update.
Click to expand...
Click to collapse
As far as I know, I have the latest Sprint update on my PHoton Q. See my previous post that I did get root. I explain how the directions concerning where to put the CWM, a folder called 'fastboot' or under SDK/tools or under SDK/platform tools. Turns out that I thought I had flashed the CWM image to the phone, but I was unsucessful and the instead of having Clockwork recovery, I was still trying to flash the SuperSU to the phone using the stock Android Recovery. It would fail. So I went back through the process, this time found the 'fastboot' folder I had created when I downloaded that and instead of copying cwm to the SDK/platform tools, like some instructions said to do, I copied the CWM image to the 'fastboot' folder. Success. See my previous post.

Tried it all, still no CWM recovery
discipler said:
As far as I know, I have the latest Sprint update on my PHoton Q. See my previous post that I did get root. I explain how the directions concerning where to put the CWM, a folder called 'fastboot' or under SDK/tools or under SDK/platform tools. Turns out that I thought I had flashed the CWM image to the phone, but I was unsucessful and the instead of having Clockwork recovery, I was still trying to flash the SuperSU to the phone using the stock Android Recovery. It would fail. So I went back through the process, this time found the 'fastboot' folder I had created when I downloaded that and instead of copying cwm to the SDK/platform tools, like some instructions said to do, I copied the CWM image to the 'fastboot' folder. Success. See my previous post.
Click to expand...
Click to collapse
So I've tried everything the same as you describe it, just like the updated procedure states, and still no Clockwork. I have cwmrecovery.img in my Fastboot folder, and SDK says that it was a success, but still boots into Android Recovery. What am I missing? I had no problem rooting it as well as my Razr M prior to the last OTA, but it went fubar after that. Any help would be awesome (or maybe just a good slap to the back of the head!)

[Q] broke asus tf101 eee pad transformer

Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?

Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.

Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?

DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z

*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926

DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash

DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server

DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help

DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?

DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429

*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?

DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip

*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it

DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way

*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!

DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine