Related
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!
dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.
Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem
reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576
kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?
HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.
I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.
Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??
buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..
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
Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
You are amazing. I will give it a try tonight and report back!
cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.
I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.
Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13
There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.
If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished
All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks
Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...
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?