Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
acelaw said:
Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
Click to expand...
Click to collapse
You flashed a PRIME rom to your tf300?
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
ppmeis said:
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
Click to expand...
Click to collapse
but fastboot need a unlocked bootloader, no?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Yes, that's right, but I suppost if he tries to flash a custom rom he has already unlocked his device. You can't flash any rom without unlock bootloader.
I cant do anything apart from get on to apx mode, from apx mode how do I use command to flash back.
My tf300 is ics, unlock.
when i connect usb to pc. i press power and volume up. thats only things i can do.
so what do i do next?
thanks.
The same problem.
I only see: "device is unlocked" or something like that. And nothing go on.
Is it totaly bicked or is there any chance to restore it?
Please advice.
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
bigworm82 said:
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
Click to expand...
Click to collapse
Try this link.
http://forum.xda-developers.com/showthread.php?t=2034866
no way to unbrick tf300t
Funny, I bricked my tf300t without doing anything. One day it just got stuck in asus screen.
tried to recover, nothing happended.
tried hard reset. Nothing.
Wipe data: result: bricked tablet.
I'm looking for information it is defintely impossible to unbrick it.
Anybody else with the same situation can tell you that.
Nobody has even been able to do it.
If you send it to Asus they provide a new tablet.
Conclusion:
TF300T is a terrible product, as any other asus product i assume. Amazing that you can brick a tablet without even trying to flash it or without even being connected to a computer.
It bricks by itself. Hundreds of other users can confirm it.
My advice: dont by asus products
If you already have one, dont use wipe data as anybody who has done it has ended up with an expensive useless brick.
Odp: [Q] How to unbrick my tf300
I don't agree witch this, only think what you not should use is t the wipe data from bootloader menu - I already flashed many times not working kernel, get really often bootloop - the problem is - much users going to made stupid things when the get a soft bootloop - If you get this first try wipe data from recovery, if this won't help, try to format data from recovery - often happends that the ext4 filessystem get broken. Recovery should allowa us to run fsck on data - I fixed my bootloops many times with it without loosing my data.
Sent from my GALAXY Cooper
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
opethfan89 said:
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
Click to expand...
Click to collapse
I have problem that my partitions won't mount at all. I have access to fastboot, CWM, and adb but no matter what i cannot access my partitions and so i cannot install zip from CWM. When i try blob within fastboot my tablet just freezes.....
Hi, what happens if I have no access to fastboot? It loops in the ASUS logo and what ever I do, can't gain access to recovery because it doesn't get into fastboot. So how to solve it via APX? Thank you.
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
unbrick tf300
ilyuha1108 said:
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
Click to expand...
Click to collapse
Hi,
I am having a similar problem to the one described. I have unvblocked my TF300T and installed CWM recovery (v. 6.0.2.3), but it can't mount any filesystem, so I can not flash anything. The boot menu is gone (RCK, wipe tablet, android) and when I switch the tablet on It just goes to CWM. If I connect the tablet to a PC, I can send commands with adb from my win 7 PC (for instance "adb reboot" will reboot the tablet), but fastboot doesn't work (it keeps "waiting for device"). Prior to this my android version was JB 4.2. I didn't make any backup, so I am fearing the worst outcome. Did I brick my tablet for good?
Thanks a lot for any reply.
TF300T blocked on boot screen
hello everybody,
my name is jonathan, and i have a very big problem.
My Asus TF300t is blocked on boot screen after try to install a new rom on JB 4.2.2.
>My clockworkMod reconvery is v6.0.1.0.
I tried to install several roms, offical or not but the problem is the same, "The device is unlocked" on the boot screen Asus...
I read the previously posts and :
- i installed on my pc the sdk
- i dowload the "blob" file and i placed it on tools directory
- but, the actually problem is whis the lign "fastboot -i OxOBO5.... (i have copied and paste it on schell command) and enter
load_file: could not allocate 820157833 bytes
error: cannot load "blob": not enough space
can you help me please ?
i want to resolve this problem with you to install the best rom for this model.
Thank you very much and sorry for my english, i am french but i understand your paragraph.
See you soon
Jonathan
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
same problem of space
Buster99 said:
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
Click to expand...
Click to collapse
Hello man,
I try your method but the problem is the same when i want to copy the blob file, "not enough space ..."
fastboot erase system OK
fastboot erase recovery OK
fastboot erase userdata OK
fastboot erase boot OK
fastboot erase misc OK
fastboot erase cache OK
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob PROBLEM
The message is the same like previously, always the problem of space.
I tries the method by copy the blob file on different directory on my computer and on a usb key too.
Always the same problem of space
I think the problem is the space on the tablet but i dont' understand. I erase system, recovery, userdata, boot, misc, cache, i think the tablet is empty.
Can you help me please ?
Thank you very much
Jonathan
which blob file did you use? Was the zip appropriate for your region? also what was the last stock rom version you ran - you said you wanted to update to 4.2.2 - what was the old version?
-Buster
Related
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
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Moved.
mathiash98 said:
To sum everything up:
1. My rom didn't work so I decided to find a new one :good:
2. I read and understand that it's much easier using fastboot
3. I was flashing the official rom when the antivirus requested a reboot
4. I forgot the flashing, and just clicked on reboot :silly: :crying:
The screen remains black when I try to boot it up :crying:
The only sign of life is when I'm charging the light is lighting and "APX" is showing in the device manager on pc with a yellow triangle, I haven't understand what "APX" stand for yet so please explain
(My bootloader was unlocked and I flashed twrp 2.5.5 just before I did this)
Do you have any tips for me? Or is the device bricked and have to be sent for service?
Please help me :fingers-crossed:
Edit: This is wrong section I know, can anyone move it to the Q&A please?
Click to expand...
Click to collapse
Apx is a method provided by the cpu manufacture for recovery. Due to the way asus has handled locking the unit apx is only available if nvflash is installed while on ICS (4.0).
Reset may be a good option for you. Power on unit. Hold volume down and insert a small paperclip to into into the reset hole. This may get you into the bootloader.
Reset: A small hole about 25mm or 1inch below the sdcard slot.
Note: If this fails you could do the same but hold volume up and hope.
Beyond this running the battery down has worked for some or remove the back cover and disconnect the battery. Leave it disconnected for thirty minutes, then reconnect.
Also see my signature for other methods to get into the bootloader. Don't bother with apx as it is useless for us.
We are looking for any change in the unit. With a change may come use of adb, fastboot, or recovery.
Try do each thing in turn and repeat this sequence twice more.
Thanks for the explanation and fir the tips! I'm going to try this
mathiash98 said:
Thanks for the explanation and fir the tips! I'm going to try this
Click to expand...
Click to collapse
Good Luck!
tobdaryl said:
Good Luck!
Click to expand...
Click to collapse
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
mathiash98 said:
It doesn't seem that any of the following work, but I haven't tried the battery pull thing, because I see that it's a sticker over the cover that says that the warrenty is void if removed. If I send it for service will the guys know that I have unlocked it, and then void the warranty?
Click to expand...
Click to collapse
I understand. If still in warranty I wouldn't remove it either.
I'm sorry that is all I have for your situation.
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
goldenval said:
Lads, let me join your conversation. I've almost same problem, probably different root cause, but same summary:
1. Originally I downloaded JB 4.2 from support.asus.com source
2. Tablet got reflashed & worked as normal, but I lost roots which I had earlier, therefore I decided to get root privs again.
3. So, I went into TWRP web-site & downloaded openrecovery-twrp-2.5.0.0-tf300tg-JB.blob blob file & via ADB was able to flash TWRP 2.5 onto my TF300T, but...
4. ...somehow TWRP doesn't let me to mount neither system, not SD-card, nothing. And currently
5. I think I'm bricked (& my TF300T too). When I press power button - tablet switches on & gets straight into TWRP, where I've only option to power it down or reboot TWRP tells me "are you sure? No OS installed".
6. When I try to switch tablet into bootload (with volume -) writing "The Device is Unlocked" shortly blinks slightly brighter, kind of trying to get into bootloader, but gets into TWRP anyway.
Any help, please! I know how Donate button works!
P.S. Because I very new writer (but really old reader) of XDA - I can't incert outside links...
Click to expand...
Click to collapse
Which tablet do you have? You show TF300T but using TF300TG twrp.
The bootloader changed again with 4.2 firmware and requires twrp especially for that version. I have been told the openrecovery-twrp-2.5.0.0-tf300t-4.2.blob does not work properly so you should have used openrecovery-twrp-2.4.4.0-tf300t-4.2.blob if you have a tf300t.
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
goldenval said:
Dear Friend! :good: That what makes difference between you - old member & me - amatuer. Yes, I loaded ...TG version of TWRP onto my ..T tablet. Bad words aren't allowed in XDA forum, otherwise I'd call myself with proper name. Anyway,
I tried to reboot from TWRP, held volume - & had no success. It loaded into TWRP again.
Then tried to reboot with command adb reboot bootloader, as you mentioned - my Windows7 PC doesn't see tablet, showing Transformer with yellow ! sign. And I tried fastboot -i 0x0B05 reboot-bootloader command, ADB is saying <waiting for device> forever & nothing happens. so I stopped here so far, waiting for your advise...
We need to break the cycle of going into twrp and only twrp.
Let's try to use twrp for that purpose. While in twrp select reboot while holding volume down.
If that fails to make a change while in twrp type adb reboot bootloader.
If that makes no change type fastboot -i 0x0B05 reboot-bootloader.
If there is still no change try the reset while holding volume down.
Reset: A small hole about 25mm or 1inch below the sdcard slot. Use a small paperclip to insert into the hole and press gently while holding volume down.
Click to expand...
Click to collapse
Ok...
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
n3tm0nk said:
So, I bricked my tf300t. I ordered a new motherboard off ebay and replaced the bricked one. It works, but it was not factory reset and still has the owners info, etc. It is password protected. I don't know the pw. When I try to boot into the recovery console, I get a dead android. Going into the menu, I have an option to wipe or boot android. How do I get around this?
Click to expand...
Click to collapse
My suggestion is use stock recovery to replace the encrypted os (probably JB 4.2) with JB 4.1 (10.4.2.20). You can download here [INDEX]25 Apr 2013 - TF300T/TG WITH ALL ASUS ORIGINAL TOOLS-Firmwares-Kernels-Guides-. Look in firmware TF300T. Use the proper sku (ww, us, etc) for your country. Please give philos64 a thanks while there he spent much time creating that post, supporting the downloads, and updating.
Unzip the downloaded file once - rename to EP201_768_SDUPDATE.zip. Place the file on your internal sdcard if possible if not place on your micro sdcard. Boot into the recovery console and make the hungry android happy. This will probably take ten plus minutes.
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
tobdaryl said:
No bad words needed. We all make mistakes. I them pointed out for future reference in case you were not aware.
First you need to get your drivers loaded for windows.
[GUIDE] How to install Universal Naked Drivers
Use that guide to get your drivers properly installed and retry the adb and fastboot commands.
Click to expand...
Click to collapse
goldenval said:
Dear tobdaryl! Thanks very much for your advice, I had to dissapear for couple of days, so couldn't answer. I followed your link & had no success. When I power on TF300T & connect it to PC, it's being read as Transformer (see my 1st picture), unlike in the guide they are working with Asus Eee pad device (my 2nd picture), so when I'm trying to install drivers from un-zipped folder it says "...couldn't install drivers for your Transformer".
Looking for more help... (
Click to expand...
Click to collapse
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
tobdaryl said:
Right click on the Transformer with the yellow symbol and point to your Universal Naked Drivers inf file. If one inf files fails to install then try the other.
Click to expand...
Click to collapse
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
goldenval said:
Tobdaryl, I couldn't find "Donate Me" button in your profile, so give me your paypal account for a little present please! :good: It worked!!! I installed correct driver from given guide, rebooted into bootloader, using ADB comand & got 3 icons: RCK, Android & Wipe Data. I tried Wipe Data, it said "can't mount something", don't remember now what. I rebooted again & clicked on Android & loaded into normal screen. Because of Asus became completely flat I put it on charge now. And after that I will have to come back to original task - to root my TF300T. While it's charging I downloaded Goo manager & tried to install TWRP, it said "No recoveries were found for your device", but in same time file for my device (that's where I made mistake, downloading TF300TG version) does exist, so what's story here? I guess this is may be because my TF300T isn't rooted yet?
Adding later. after digging this & other forums I found that in order to get root & have to have CWM/TWRP on my device & I can't get them until my TF300T is rooted. Am I confused & talking rubbish?
Adding 2 hours later. I rooted the device using XDA guide. Still trouble to reboot device. It always reboots into TWRP, then I have to connect it to PC & reboot with ADB commands. This isn't right...
Click to expand...
Click to collapse
Go manager does not have the proper twrp for our tablet.
Rooting is no longer required to flash twrp. Motochopper will root with just adb.
I suggest we try to get everything working properly with stock before changing or adding anything.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot. Verify everything works properly before making any other changes.
Thank you for the donation offer.
I don't have a method to receive donations. A simple click on thanks will be good.
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
tobdaryl said:
Unzip once and place on your tablet, flash with twrp, if that fails unzip again and place the blob file in the directory with adb and fastboot and flash with fastboot
Click to expand...
Click to collapse
goldenval said:
My problem is that because I installed wrong TWRP by mistake - it can't mount anything & I can't install anything from SD or internal memory. So, should I delete existing TWRP somehow &/or replace it by CWM recovery?
Click to expand...
Click to collapse
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
May I ask you then? My ROM number is: JOP40D.WW_epad-10.6.1.15.3-20130416 & as I can see from numbers you are offerring me to downgrade (from 4.2 to 4.1). Will this not kill the device? And why can't we re-install existing ROM through ADB? I'm not arguing, just trying to understand.
tobdaryl said:
No don't delete twrp or install cwm. We should have access to adb and or fastboot. We should be able to use either to get sorted.
Go to to this link and download the stock Asus firmware 10.4.2.20. Choose the proper sku for your location (ww, us or whatever). Don't forget to thank philos64 while there. Unzip twice and place the blob file in the directory with adb and fastboot and flash with adb. Verify everything works properly before making any other changes.
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
exit
adb reboot
Click to expand...
Click to collapse
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
robscar said:
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
Click to expand...
Click to collapse
You need a custom recovery! download twrp here: http://techerrata.com/browse/twrp2/tf300t
DOWNLOAD THE ONE THAT SAYS "openrecovery-twrp-2.5.0.0-4.2" and flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob" make sure you rename the blob to "twrp.blob"
*update your info your bootloader is "10.6.1.15.3" instead of "10.6.1.12.3"
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can also follow this guide. It explains what you need to do pretty well. But you do need a custom recovery, which i prefer TWRP http://forum.xda-developers.com/showthread.php?t=2187982
I was confused at first too. I think they need to change the wording in the tutorials. They say "If you're on JB bootloader, this twrp, if you're on 4.2 BL, that TWRP" and i was just thinking... WTF, both of them, 4.1 and 4.2 are jellybean.... it should be changed to 4.1 BL and 4.2 BL, none referred to as JB.
Sent from my TF300T using Tapatalk 2
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
robscar said:
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
Click to expand...
Click to collapse
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
I've a TF300TG but I think my question is associated to the title of this thread. Do I have to note the sku of my Pad or isn't that important when I flash a custom Rom?
In the threads of many custom Roms I've read nothing about the sku. So I'm not sure if I have to take care for this.
Sent from my HTC One X using xda app-developers app
noahvt said:
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
Click to expand...
Click to collapse
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
robscar said:
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
Click to expand...
Click to collapse
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
diesburg said:
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
Click to expand...
Click to collapse
I got these files from the SDK download for MAC.
robscar said:
I got these files from the SDK download for MAC.
Click to expand...
Click to collapse
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
robscar said:
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
Click to expand...
Click to collapse
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
diesburg said:
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
So, no matter what I do, the bootloader has to be unlocked, correct?
robscar said:
So, no matter what I do, the bootloader has to be unlocked, correct?
Click to expand...
Click to collapse
for a custom rom, as far as i know, yes
but for just root on stock rom i believe theres ways to root stock without unlocking the bootloader
Sent from my TF300T using Tapatalk 2
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
robscar said:
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
Click to expand...
Click to collapse
It's most likely drivers.
http://forum.xda-developers.com/showthread.php?t=1917237
Maybe that'll help?
Sent from my TF300T using Tapatalk 2
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
robscar said:
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
Click to expand...
Click to collapse
not sure exactly how a mac works but i believe its some sort of linux. can you by chance start the terminal with "administrator" priveleges or type "su" in the terminal to get root priveleges? Just my thoughts with a "permission denied" error, you dont have administrator/root access.
In that link i shared above about mac and fastboot, it says to use " ./ " in front of every command. So try the fastboot commands i said above to flash the recovery but do it with ./ infront like this: ./fastboot flash commands
Sent from my TF300T using Tapatalk 2
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
robscar said:
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
Click to expand...
Click to collapse
In the steps I told you above. The part where you do the fastboot commands in the terminal. "fastboot flash 0x(somenumber) recovery twrp.blob"
put a ./ in front of the fastboot command... so its "./fastboot flash 0x(thatnumber) recovery twrp.blob"
Sent from my TF300T using Tapatalk 2
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?