Related
Hi guys,
I decided to root my Nexus S with Nexus root toolkit, and then I tried to install CyanogendMod 10.
Then, it rebooted, and now when booting it stuck at a moving circle with the CyanogendMod text in it. after 30 minutes I had to remove the battery to shut it down.
Now I can access to the Fastboot mode (bootloader version I9020XXLC2)
it says Lock State : unlocked. But a recovery shows a robot on it's back with an exclamation mark on top of it during some minutes and then it try to but normally again and get stuck at the circle.
Update :
thanks to http://forum.xda-developers.com/showthread.php?t=1069032
I can now access to download mode, and I'll try to do something with ODIN, I'm on my way to tutorials.
And it's still recognize in windows as : Android ADB Interface in the computer management window (but no USB hard drive in the computer menu).
Any suggestion to help me out ?
ps : as you can guess, I'm quite a beginner, and may not get the meaning of all technical word in flashing phones.
Thanks for reading.
DO NOT use Odin for things like that. Think of Odin as a last resort thing rather than a tool you can use daily.
The Nexus line of phones is super easy to deal with.
Flash your recovery using fastboot.exe while in bootloader mode.
http://wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img
Download for recovery (rightmost column):
http://www.clockworkmod.com/rommanager
Once that is done, boot to recovery, and wipe data + flash your prefered ROM.
Edit: Apple pie is awesome.
polobunny said:
DO NOT use Odin for things like that.
Edit: Apple pie is awesome.
Click to expand...
Click to collapse
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Tartopom said:
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Click to expand...
Click to collapse
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
polobunny said:
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
Click to expand...
Click to collapse
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Tartopom said:
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Click to expand...
Click to collapse
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
polobunny said:
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
Click to expand...
Click to collapse
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Tartopom said:
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Click to expand...
Click to collapse
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
polobunny said:
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
Click to expand...
Click to collapse
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Tartopom said:
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Click to expand...
Click to collapse
Bravo, you're getting there. You'll be an adb master in no time.
At least you are now a user that knows how to use fastboot and fix issues that arise from flashing ROMs and relying on automated stuff.
Besides actual hardware issues most issues people have on their device are by some automated form of something. Tool kits/ROM manager and so on. All of which can be fixed up right away with fastboot and a basic understanding of what you're doing.
So now you're better off. All nexus devices work the same way as well.
Hello
I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.
Now bootloader is unlocked and starts straight into TWRP.
At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.
I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way
Does anyone else have a procedure that can be repaired?
And that since the corect connection mode that allows me to write on tablet via fastboot ?
I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.
BR
Mihnea
I wait with many interes your sugestions.
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Sorry to say but you should have read a little more about what you were doing. It CLEARLY says over and over and in this forum NOT to use THAT wipe option.
You've just wiped all the files from your device. There are now no files to boot from.
If you can get into fastboot or ADB you may have a chance of saving your tablet. There's a very good chance that you've just bricked it though. Best of luck.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
mihnea_gsm said:
I dont understand ... WHY is happend that ? TWRP is sucks because I thing that soft dont have safety belt... ??? Because before to upgrate I do wipe and all was very ok .... or other is cause? I think that Asus dont put this obtion ... that people damage our tablets...
I think that good answer must be come from twrp team ???
Click to expand...
Click to collapse
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
wetbiker7 said:
Dude, you really didn't even get into TWRP recovery. If you would have tapped the RCK tab you would have went into TWRP. Don't go blaming it on TWRP because you failed to do your homework. I know there are probably 10 threads where people have done the same thing and tapped the wrong WIPE tab. If I can find and read them then so can you. You just failed to do so.
It really sux that you've messed your tablet up but when you've got a device that costs that much, you are supposed to do your research before trying something you know nothing about. I read through this forum for over a week before I bought and rooted mine because I wanted to make sure I knew what i was doing and didn't end up with a $300 paperweight. If I didn't know or couldn't find the answer I asked questions. :good:
Click to expand...
Click to collapse
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
mihnea_gsm said:
Man no longer take ptr defense that I think you're wrong ...
Look .. when I got the asus app to unlock bootloader it says clearly: If using application note is lost ... guarantee ...
But here in this case I have taken away from the site fisirele .. and nothing in there that you do not press WIPE button
* That's what ... ok there is a software bug and it's understandable ... waiting to see how to solve ...
And another thing ... I have a GSM service ... so I pass many phones and tablets by hand and install a lot and CWM and TWRP and it is the first time that happens ... so do not need me to tell me that I have not done my homework.
Then I recommend the Samsung Galaxy Tab that anything is much simpler and solutions are at hand ... including bootloder destroyed ... then we rewrite bootloder JTAG on the tablet and tablet repair in 1 hour .. simple as that.
Today I gave mail to all those who produce JTAG interfaces (riff jtag, meduse jtag, vulcanobox, easy jtag) to see if anyone has any solutions for NVIDIA Tegra3 jtag, although I do not think ... but if I stick to appear instant boot tablet and restore bootloader, but many people don't have this interfeces...
BR
Mihnea
Click to expand...
Click to collapse
Man, if you would have read , you would have known not to use the wipe tab. As I said before, there are threads all over the place in here stating NOT TO USE THAT WIPE OPTION. You may have done SOME research but you didn't do enough on THIS tablet. The research on all the other devices you know about doesn't count. LOL It's TF300 series we're talking about.
Oh, and you said for me not to take offense because I think you're wrong. Bro, I don't take offense because you disagree with me. I'm just trying to get you to man up and admit that you made the mistake and didn't do enough reading. LOL
quidrick said:
I've also read those warnings, but if bootloader's wipe is safe with stock recovery and bricks tablet with TWRP flashed, then there is clearly something wrong with TWRP.
Click to expand...
Click to collapse
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Moe5508 said:
I had also wiped my device and would have been stuck had I not had nvflash...please guys take all possible precautions before you start messing around with your devices and ensure you can go back and flash a stock ROM...now all I do is get into APX mode, fire up wheelie.exe and I unbrick my device. Did you nvflash your device before? If you can get into fastboot mode there may be some hope yet...
This is a good place to start: http://forum.xda-developers.com/forumdisplay.php?f=1579
If all else fails, please PM me...
Click to expand...
Click to collapse
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Well, let me ask you a question. Why would you want to wipe the tablet anyways when it's not in recovery? You MUST press RCK to enter the recovery. The wipe option you guys are talking about is not even a part of TWRP recovery.
Click to expand...
Click to collapse
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
Man you are right 100% wipe buton from asus MUST BE - wipe data from recovery (twrp) but I thing that twrp team is not agree with us...
Most important for me in this moment like other people I want to make table tablet alive....
BR
Mihnea
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
You guys aren't getting my point at all. I'm not saying that the wipe data option screwing people's tablets up is right. All I'm saying is that the info is here in this forum saying not to do it. Lol If the time is taken to read the info in these threads we wouldn't even have this thread. :thumbup:
If myself and all the other people have been able to find this information and avoid tapping the wrong wipe data option then so should other people. THAT IS MY POINT.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
At this point it really does not matter who is and who is not, right ... matter to be able to start and run ok tablets ...
So I expect all of which can give you an idea
BR
Mihnea
This is a question for developers more familiar with our partition layout. My working knowledge of android is limited, but I do have background in linux. If he can see his device under ADB, shouldnt it be possible for someone to do an adb pull of their system, data, bootloader, and recovery partitions for him to push to his?
The only reason I could think of that not working is if the wipe option deletes the entire partition table and they need to be repartitioned from scratch. Its either that or the Bootloader partition is getting wiped instead of the Data partition. Just bouncing ideas in my head here. It was on a kyocera zio and on gingerbread, but this was one way I was able to help restore a device.
NVflash seems capable of repartitioning the drive........ Does adb have commands to set up partitions as well?
One would also think odin should be able to help with repartitioning. There has to be a way.
-Edit-
Ok so if you DO have fastboot, you might be able to recover. Read this post !
http://forum.xda-developers.com/showthread.php?t=2236885
Something new...
We all know that in the above case is bricked tablet that starts directly in TWRP ... even if we start trying to po fastboot (volume down + power) it will start directly in TWRP
Now to answer adb shell like this:
c: \ Adb> adb devices
List of devices attached
0123456789ABCDEF recovery
But if I try to send something to it (like a touchscreen driver) see the answer and receives information
c: \ Adb> adb push 02-3011-4820.ekt / data / local / tmp /
* Daemon not running. starting it now on port 5037 *
* Successfully started daemon *
1027 KB / s (32868 bytes in 0.031s)
In other words we can send information in tablets briked .. I think now matter what name send.
I have here 2 tablets bricked (tf300tg and TF300T) and 3 functional TF300T tablet (but with broken touchscreen). The point is that I do not know what commands to send, and how to pull information from functional and tablets to the tablets who have problem
Now comes my question logic ... We can not copy anything from a 100% functional tablet and send this information to a tablet briked?? Can only boot, or recovery?
mihnea_gsm said:
in this moment I am in this point:
in this point adb recognized my tablet
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF recovery
but after I want to flash blob
C:\adb>fastboot -i 0x0B05 flash system blob
< waiting for device >
BR
Mihnea
Click to expand...
Click to collapse
Have the same problem...
fastboot stock at < waiting for device >
my device boot/reboot or power on without any touch....always boot into recovery twrp ( but can´t mount and do nothing)
Any help?
Boot your tablets up into the selection screen where you can select to wipe data, fastboot, recovery or load OS. If you have updated your bootloader and firmware to 4.2 then the fastboot option disappears and now you are already in fastboot mode when when you load the selection screen. All you will need to do is plug the USB cable into your tablet and your computer will recognize this and load the ADB interface. Btw if your having problems with TWRP 2.5, simply flash back to 2.4.4.0.. which is exactly what I did.
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
anaschillin said:
I updated my bootloader and firmware to 4.2 ASUS stock and then flashed TWRP 2.5... I was having issues such as split screen, coudn't mount anything and when I loaded into recovery I was asked for password. I simply flashed back 2.4.4.0 JB TWRP.
I was back to normal.
Click to expand...
Click to collapse
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
bwiberg said:
No - I think this part is wrong. Do not use JB version of TWRP with bootloader version 4.2. You must use TWRP version ending in -4.2.
Click to expand...
Click to collapse
OK .. to start over ... I had Asus tf 300TG firmware version 4.1.1 and I did the OTA update to 4.2.1. After that I put some revovery TWRP 2.5.0.0 (most probably was not what I had) and broke the tablet.
Now my tablet is in this variant:
C: \ adb> adb devices
adb server is out of date. killing ...
* Successfully started daemon *
List of devices attached
0123456789ABCDEF recovery
But after I want to flash blob
C: \ adb> fastboot flash system's 0x0B05 blob
<Waiting for device>
You say that I should write: openrecovery-TWRP-2.5.0.0-TF300T tablet-4.2.blob as did the OTA update to 4.2.1 right?
* But in this moment I realize WHY I broke the tablet ... because I wrote this file: openrecovery-TWRP-2.5.0.0-tf300tg-JB.blob ...
Why I wrote this? because if you look here: http://techerrata.com/browse/twrp2/tf300t he write: If you have the 4.2 official update, choose one of the files that ends with -4.2. If you choose the wrong file you may brick your tablet.
* THIS FILE NOT EXSIT: openrecovery no-TWRP-2.5.0.0-tf300tg-4.2.blob .....exist only for tf300t not for tf 300tg
I write a post at twrp blog : http://www.teamw.in/project/twrp2/97
* Now see another file: openrecovery-TWRP-2.5.0.0-TF300T-JB.img .... what to do with this file?
OK and now...
What should I do? which file should I write?
And how (mode - fastboot, apx ???) should be the tablet to write the file?
And who would command if the tablet would be in that mode (fastboot, apx)
BR
MIHNEA
quidrick said:
a) Because it's official method to do factory reset, recommended by ASUS when you have problems with your tablet. It is working perfectly fine on stock recovery and some users are used to do this that way.
b) Because it's quite easy to do this by mistake, when you are trying to enter recovery. Please, give me fast and honest answer without checking - which button changes option, and which enters selected option?
My tablet is perfectly fine, running TWRP and custom ROM, but someone has to defend users who used wipe data.
Unless we hear sensible explanation from one of TWRP developers why this option is working fine on stock recovery and is bricking tablets on TWRP, and why it can't work correctly (or at least safe) on custom recovery, then it should be treated as a custom recovery bug.
Click to expand...
Click to collapse
I have nothing to do with twrp and certainly am no dev.
What I do know is the partition for recovery is a limited space and there is not enough room to emulate stock recovery and still have enough space to provide for the way we use twrp.
The "factory reset" recommended by Asus is located in settings. This is "wipe data" located in the bootloader. I have not heard or read of Asus suggesting use of wipe data but I have seen factory reset.
Now I don't believe in flaming anyone!
Explaining a mistake is positive, it helps the user know what not to do in the future but only if presented properly.
I'm sure the reply came from frustration of wanting to help but understanding that recoveries from wipe data are few.
No one wants to see a brick!
Sorry for taking space without providing any help for the OP!
If anyone has any suggestions for the OP please present them.
I was so slow posting I see help has arrived.
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?
I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.
lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.
First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.
Nobody has any more expertise to proffer?
monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!
Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.
New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.
Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience
berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?
No, you cannot relocate the bootloader. Flash away
berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.
Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.
I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks