Related
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!
dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.
Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem
reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576
kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?
HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.
I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.
Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??
buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.
MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards
ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.
I found multiple development threads that are close to this, but here's the deal...
I took Asus 4.2.1 OTA update and used that for a while.
The device was already unlocked and I decided to try TWRP 2.4.4.0 for recovery before trying any custom ROMs
I followed the big bold red instructions that said:
If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA.
I downloaded the -JB version (at that time, -ICS was the only other choice), and installed it via fastboot.
Upon rebooting, it will only boot into recovery and TWRP can't see any partitions. More importantly, I've spent almost a month now reading the threads that are related to this trying various suggestions in trying to break out of this, and during this time, I've realized that I can't flash anything. ADB works, but the devices says "123456789ABCDEF recovery". I can run "adb reboot bootloader" and I will get my 3-icon 4.2.1 bootloader screen with a blinking green square on RCK. Fastboot devices shows my S/N, and it acts like it is flashing (tried flashing the -4.2 version of TWRP 2.4.4.0 and a new copy of the JB 4.2.1 OTA ROM), but all the tablet does is lock-up. The green square stops blinking and, even though fastboot says it's working, the tablet is no longer responding and requires a reset to reboot, upon which it boots right back into TWRP.
I'm just asking if there is a way out of this yet that doesn't involve replacing the main logic board.
I suppose what bothers me more, is that Teamwin's website for TWRP still has the same instructions in big bold red letters, without acknowledging that there are TWO official Asus Jellybean OTA releases. One will work just fine with the -JB version they specify to download, the other will do what mine did. Anyone current with Asus releases is gonna follow these instructions and brick their pads unless they already know about the -4.2 version of TWRP.
Yo!
Have you tried flashing asus stock 4.2.1 system blob using adb?
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This is the link to the instructions i followed. http://forum.xda-developers.com/showthread.php?t=2187982
Here is the main point.
- Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash system blob
, hit enter and wait until it completes
Write this to reboot your tablet:
Code:
fastboot reboot
or hold the power button for 10 seconds if the code doesn't work
You are now updated to Android 4.2
There are 3 things keeping this from working:
1) fastboot -i 0x0B05 flash system blob
This locks the tablet up. Fastboot thinks it's still working, but the blinking RCK has stopped blinking and...
2) fastboot reboot
... doesn't work because the tablet has locked up from the flash attempt. You have to...
3) hold the power button for 10 seconds if the code doesn't work
Which does reboot the tablet, but it goes right back into TWRP, and you have NOT been updated to anything.
Now, in my particular case, I can get it to "adb reboot bootloader" and tell it to cold boot Linux to get into my OS, but that never happens either. It's likely been wiped from one of my multiple attempts at trying others' suggestions for getting out of this.
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I did the same thing as the OP. I'm not new at this, I've rooted and run custom ROMs for years on dozens of devices. I always do lots of research before starting the process. What the OP and I are saying is that the Team Win site doesn't state anything about the 421 patch and if you look at the file list, the patch only exists in the 2.4.4.0 version. With those two things in mind, a reasonable person would conclude that 2.5.5.0 is patched for both...as long as you use the -JB version. Obviously wrong as I now know, but certainly not clearly wrong before bricking the device.
I would never assume to blame the Dev's, but I (we) are asking that they be a bit more blatant with the fact JB v4.2 MUST USE TWRP version 2.4.4.0-4.2 and not anything else.
Now, for good or bad, so many people have now bricked their TF300's that there are many threads like this one. Any research at this point will reveal this issue. Still, Team Win should post the warning.
joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I wish it was as simple as reading the wrong post... When I downloaded TWRP 2.4.4.0, there were only -ICS and -JB files listed (much like TWRP 2.5.0.0 is now)... Wouldn't you have picked -JB?
Even now, Teamwin's directions tell you that, if you took the Asus JB OTA, that you need the -JB version. They don't differentiate WHICH JB OTA, and they don't mention that a -4.2 version specifically for the 4.2.1 OTA exists. Never mind mentioning that using the -JB version on the latest Asus JB OTA update will BRICK THE TABLET.
There are 192 people that have downloaded the 2.5.0.0-JB blob file as of now. How many of these folks do you suppose have taken the Asus 4.2.1 OTA update and are about to permabrick their tablets?
It sickens me to know of the 192, likely most are on 4.2.1. I only hope they catch it before pushing the ROM.
When you flash recovery its flash ix505blah recovery recovery.blob is it flash ix5o5blah system system.blob? If that makes sense? Or no.?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
The two things here centers around the fact that TWRP is the only thing that will boot, other than the bootloader (but you have to boot TWRP first).
1) If you are in TWRP, there are no partitions mounted. In fact, there are no mmcblk devices at all, which is why there are no partitions mounted. As a result, there is nothing to flash to from here (even if fastboot worked). Adb works from here, but the device serial says "123456789ABCDEF recovery". Fastboot detects no devices at all from here.
2) If you reboot bootloader from adb, you can get access to fastboot. However, any flashing from here locks up the tablet, even though the command looks like it's running and completing the first time. Adb does NOT work from here, sees no devices. Fastboot looks like it sees the right device until you try to flash something with it. Once you try to flash anything, no fastboot command completes, furthering the notion that the tablet is frozen. A reset reboots the tablet back into TWRP, and nothing has changed. Repeat the cycle ad nauseum.
Basically, you can't do squat from TWRP, and fastboot flash from the bootloader locks up the tablet so you can't flash anything. I'm pretty sure it will take a logic board replacement to fix it at this point unless someone comes up with something better.
I'm having the exact same issue as you... I had flashed the TWRP JB blob and it couldn't recognize anything so I tried to flash CWM. Now...My fastboot doesn't do a thing since the blue progress bar doesn't show up and just freezes when trying to flash the stock firmware. I don't think I can send it to Asus for warranty either since my device is unlocked.
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
You can't flash a recovery? And what about the stock Rom?
Sent from my WT19i using xda app-developers app
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
Lol did that too...I don't know if there is anything left to try. Did you try putting stock rom on an external SD card and running RCK?
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
I did the same thing and got the same result. This i very interesting because the
Code:
fastboot -i 0x0b05 flash <partition> <filename>
command which tries to write/edit something on the partition fails (maybe is due to some encryption introduced in 421) but the
Code:
fastboot -i 0x0b05 erase <partition>
which also does the write/edit, succeeds. What I'm trying to say is that either both should fail or succeed because both are trying to do some editing to the storage.
steveb05 said:
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
Click to expand...
Click to collapse
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
splashg said:
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
Click to expand...
Click to collapse
Just got my TF300 back for Asus service center. They said that they had to replace the motherboard @ a cost of $186.00 total, parts and labor. Told them to just send it back. I'll buy a Nexus 7 instead for the same price almost.
Got my broken TF300 ebay win today. Digitizer and LCD were toast. But, the main board went right in to my bricked TF300. I'm unlocked, rooted, and running 4.1.1 and life is good!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...
dedalus2k said:
I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...
Click to expand...
Click to collapse
Make sure you have flashed the correct version of TWRP. as there are three different versions on their website. If you are confident you have flashed correct TWRP version then you may need to downgrade to the previous version of TWRP. I had a similar issue I downgraded to 2.4.4.0 JB build. Hope this helps
"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.
dedalus2k said:
"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.
Click to expand...
Click to collapse
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.
anaschillin said:
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.
Click to expand...
Click to collapse
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.
im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live
Update: Bought a card reader at local Discount Electronics. Plugged it into my PC and it promptly froze my computer and destroyed my $80 64G sd card. Can't catch a break here. So I need to get another card and reader before I can attempt to install rom from external card.
The card reader is by a company called Zeikos. http://www.amazon.com/electronics/dp/B001T9N0R6 You have been warned.
Sheena0220 said:
im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live
Click to expand...
Click to collapse
Can you flash a recovery...
if you manage to flash a recovery run the command: fastboot reboot recovery.
dedalus2k said:
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.
Click to expand...
Click to collapse
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
I'll give the first one a shot. I can't get into fastboot mode and the su command comes up an error even though I am rooted or was. I really can't figure out where it all went haywire.
YES! I'm in!
tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!
dedalus2k said:
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!
Click to expand...
Click to collapse
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Grazie Mille! Gonna give it a go right now.
Should I bother with TWRP? I tried to update it before and that's the point it went to hell last time.
tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.
dedalus2k said:
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.
Click to expand...
Click to collapse
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.
tobdaryl said:
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.
Click to expand...
Click to collapse
Done and no luck
dedalus2k said:
Done and no luck
Click to expand...
Click to collapse
No recovery either?
What happens in both cases - please explain.
tobdaryl said:
No recovery either?
What happens in both cases - please explain.
Click to expand...
Click to collapse
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.
dedalus2k said:
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.
Click to expand...
Click to collapse
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?
tobdaryl said:
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?
Click to expand...
Click to collapse
Excuse my noobishness.
I can get into bootloader with the adb reboot bootloader command you gave me
When I go to recovery, RCK right?, it freezes up.
From cold boot it goes directly into TWRP, which asks for a password which it hasn't ever before this mishap.
If I go to android from bootloader and it goes to TWRP as well
Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...
Slarty Bartfast said:
Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...
Click to expand...
Click to collapse
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!
FordPrefect said:
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!
Click to expand...
Click to collapse
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
ok, thanks for the clarification. However, that is exactly what I would have done ... you have checked the download file and fastboot seems to transfer it. From then on you should be able to boot into recovery.
Forgive me please for a dumb question ..but have you tried to boot the "classic" way? Like switching the device off and then power on with the Volume minus key pressed? Other than this, I am sorry but I don't have any further suggestion
Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...
LetMeKnow said:
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...
Click to expand...
Click to collapse
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?
sbdags said:
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?
Click to expand...
Click to collapse
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.
Slarty Bartfast said:
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.
Click to expand...
Click to collapse
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot...
Click to expand...
Click to collapse
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?
berndblb said:
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thats the wierd thing, I did not encrypt the tablet, just discovered it with the green android telling me it needed to do a full data wipe because the tablet was encrypted, I've never encrypted any of my android devices. After this process it worked fine again. Then last time I powered it off it came back up in a boot loop.
I've put the stock firmware on an sd card and the it spins for a few minutes 3 or so then reboots into boot loop.
Slarty Bartfast said:
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?
Click to expand...
Click to collapse
Well, I can kind of confirm this. Without having done scientific research, but recently I fought my fastboot connection as well. It turned functional only after I checked the USB debugging thing.
_that said:
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.
Click to expand...
Click to collapse
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...
LetMeKnow said:
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Click to expand...
Click to collapse
Would be interesting.
LetMeKnow said:
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...
Click to expand...
Click to collapse
The real experts in this area are those who brought you wheelie and flatline... for me it looks very confusing. The twrp.blob md5sum matches mine, and I don't understand why it finishes so fast, says "OKAY" but doesn't work. If there was a problem with the fastboot protocol or with writing to flash memory, I'd expect some error message. Anyway, maybe try a different/newer fastboot binary or another USB port or another PC? I assume it's Linux on the native machine and not a VM?
I've seen a bootloader which would not flash anything in the case where someone cross-flashed a TF300 bootloader on the TF700, but I assume the OP has never tried such a crazy thing. Check the bootloader version, it should be 10.6.1.14.x.
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.
Slarty Bartfast said:
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.
Click to expand...
Click to collapse
Wow nice response to people trying to help you.......
sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
I agree. Figured some people prefer failing over learning.
Enjoy your new cutting board. Should work great on peppers too. Probably will last you longer screen down - just some friendly advice....
sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
Indeed. Seemed like a good idea at the time. Fed up with this rubbish now, gpl'd but still managing trying to foist essentially drm on it. I think what annoys me most is the insidious and slow corruption of the ideal. Must say its partly my own fault, i have stood by and done nothing.
Apologies anyway.
Think I'll buy a Rasberry Pi.