Related
Hi everyone,
I was hoping someone might have some advise for me to try. I did the following and now I can't seem to boot the ROM I installed and/or load the partitions to wipe them. TWRP is asking for a password (which I just cancel) and then it can't mount the partitions. Here is what I did.
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Any advise would be appreciated. Thank you. The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file. Thanks so much for your time. Someone is helping me on the side via PM, if I get anywhere with that, I'll post the resolution here.
-Tony
qzmicro said:
The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file.
Click to expand...
Click to collapse
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Any suggestions?
manhart said:
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Click to expand...
Click to collapse
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
qzmicro said:
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
Click to expand...
Click to collapse
That is a rom based on CM11 kitkat. Did you read the requirements (which the cmb creators unfortunately just touch upon in their op) before you flashed it?
The CM11 OP states that you have to be on 10.16.1.14.x bootloader and CWM 6.0.4.4 as a recovery.
It also clearly states that TWRP has problems with KitKat. Supposedly the latest TWRP version works, but to my knowledge that is not confirmed. Don't know what TWRP version you initially flashed, but then you flashed one that's totally outdated and possibly not even compatible with your bootloader.....
I hope you still have access to fastboot.... download CWM 6.0.4.4. and flash it. Then try to flash the rom again.
But check your bootloader version first!
Read this: http://forum.xda-developers.com/showthread.php?t=1957660
Now I can't seem to erase certain partitions or write to system...
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
qzmicro said:
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
Click to expand...
Click to collapse
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
It's been a single ? since I started using fastboot.
berndblb said:
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
qzmicro said:
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
Click to expand...
Click to collapse
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Drivers are installed now and stilll ? for fastboot devices.
berndblb said:
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Click to expand...
Click to collapse
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
qzmicro said:
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
Click to expand...
Click to collapse
I have never heard of this issue.....
Please post the fastboot commands you are using.
Liunx Mint 32 bit
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
I will document what I have done so far, step by step.
berndblb said:
I have never heard of this issue.....
Please post the fastboot commands you are using.
Click to expand...
Click to collapse
I'll post shortly what I have done and how it went down. Specifically the commands used in fastboot as that is the ONLY tool I've used so far besides the ASUS Unlock Tool. Standbye...
-Tony
I'll be installing linux mint 32 on a VM....
lj50036 said:
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
Click to expand...
Click to collapse
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
UPDATE: Here is all the commands I've tried on my Tablet...
Originally I did this:
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Since then I've tried this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (blob was in same directory as fastboot and I got it form the latest asus firmware zip file) <-- Failed It sends the data okay but fails to write to the disc. Error on ASUS tablet in red also confirms the command write:system failed and gives a memory address.
fastboot -i 0x0B05 reboot
Please note that some of the erase commands simply hung. I had to restart the tablet to go back into fastboot mode. When I restart it sometimes they erase successfully. Not sure why. I know I couldn't erase userdata at all, and recently tried again and it worked.
I now have a copy of Mint Linux 32-bit ready to go. What should I try?
-Tony
VM Mint
qzmicro said:
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
Click to expand...
Click to collapse
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
lj50036 said:
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
Click to expand...
Click to collapse
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
P.s. I do not believe I have NVFLASH. I had firmware that didn't alow for it, so I just did the Asus Unlock Tool. Please refer to my previous message about anything/everything I've done so far. Cheers.
qzmicro said:
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
Click to expand...
Click to collapse
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
lj50036 said:
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
Click to expand...
Click to collapse
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Great
qzmicro said:
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Click to expand...
Click to collapse
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Linux Mint still shows ?????? as my serial.
lj50036 said:
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Click to expand...
Click to collapse
So, I installed fastboot and ADB and installed all updates on the OS for kicks. Then tried the fastboot devices command and I recieved:
Code:
[email protected] ~ $ fastboot devices
no permissions fastboot
[email protected] ~ $ sudo fastboot devices
[sudo] password for amascolo:
???????????? fastboot
[email protected] ~ $
...? Still no serial number. I've seen this since I took it out of the box. Not sure what that is all about, I have found no one else with this issue. I'm going to try to flsh and I'll let you know what happens.
-Tony
UPDATE: I have tried to re-flash the damn thing and it still fails. Here is what I see...
Code:
[email protected] / $ sudo fastboot -i 0x0B05 flash staging /home/amascolo/Desktop/blob
sending 'staging' (800927 KB)...
OKAY [135.763s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 136.934s
[email protected] / $
Any ideas fellas? Seems I simply am not able to write to the system partition again.
-Tony
* SIGH *
Anyone have any ideas as to why I can't write to my device? Any ideas as to what I may try? Please advise, I'm not looking forward to throwing this thing away. Cheers.
-Tony
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 have an unlocked and rooted tf700 that I have loaded with CM11. I am currently on bootloader 10.6.1.14.8 and using CWM 6.0.4.7.
I would like to install the newly released SlimKat ROM for the device, but it requires the most up to date bootloader, 10.6.1.14.10. I can't figure out how to update my device.
I tried the guide here, but that appears to only work if you are on stock. I also tried the zip package in this post that includes the bootloader and TWRP, but I get an "assert" error from CWM when trying to install the zip.
Can anyone please point me to a guide on how to update the bootloader to 10.6.1.14.10 on this tablet with a custom ROM loaded?
gdselzer said:
I have an unlocked and rooted tf700 that I have loaded with CM11. I am currently on bootloader 10.6.1.14.8 and using CWM 6.0.4.7.
I would like to install the newly released SlimKat ROM for the device, but it requires the most up to date bootloader, 10.6.1.14.10. I can't figure out how to update my device.
I tried the guide here, but that appears to only work if you are on stock. I also tried the zip package in this post that includes the bootloader and TWRP, but I get an "assert" error from CWM when trying to install the zip.
Can anyone please point me to a guide on how to update the bootloader to 10.6.1.14.10 on this tablet with a custom ROM loaded?
Click to expand...
Click to collapse
BACKUP EVERYTHING YOU WANT TO KEEP INCLUDING YOUR PERSONAL STUFFS...
1.Go to Asus support website and download the correct SKU for you device
2. Extract it once and it should be another zip file
3. Go to CWM and install the second zip file
4. You should have the latest bootloader that you just downloaded but you need to use fastboot to install your custom recovery again, good luck...:fingers-crossed:
LetMeKnow said:
BACKUP EVERYTHING YOU WANT TO KEEP INCLUDING YOUR PERSONAL STUFFS...
1.Go to Asus support website and download the correct SKU for you device
2. Extract it once and it should be another zip file
3. Go to CWM and install the second zip file
4. You should have the latest bootloader that you just downloaded but you need to use fastboot to install your custom recovery again, good luck...:fingers-crossed:
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that as well. I get an assert failed, Status 7 error when I try installing the zip from the Asus website.
gdselzer said:
Sorry, should have mentioned that I tried that as well. I get an assert failed, Status 7 error when I try installing the zip from the Asus website.
Click to expand...
Click to collapse
Try this method and start reading page #2, good luck...
http://forum.xda-developers.com/transformer-tf700/help/firmware-manual-flash-t2858019/page2
EDIT: Did you have a correct SKU for your device? The error message is telling you that something is incompatible with your device. You may want to double check the file to be safe...
Been working on this for a few days now and I'm stuck. I've never used fastboot before.
I'm on Ubuntu 14.04, so I installed fastboot via:
Code:
sudo aptitude install android-tools-fastboot
I moved the blob to /usr/bin (directory where fastboot lives) and do
Code:
fastboot devices
Result is
015d2a5087181817 fastboot
Click to expand...
Click to collapse
Looking good, right?
Now I try
Code:
fastboot -i 0x0b05 flash system blob
< waiting for device >
Click to expand...
Click to collapse
and it just sits there. Same thing if I try
Code:
fastboot -i 0x0B05 reboot
How do I get fastboot to work?
LetMeKnow said:
Try this method and start reading page #2, good luck...
http://forum.xda-developers.com/transformer-tf700/help/firmware-manual-flash-t2858019/page2
EDIT: Did you have a correct SKU for your device? The error message is telling you that something is incompatible with your device. You may want to double check the file to be safe...
Click to expand...
Click to collapse
gdselzer said:
Been working on this for a few days now and I'm stuck. I've never used fastboot before.
I'm on Ubuntu 14.04, so I installed fastboot via:
Code:
sudo aptitude install android-tools-fastboot
I moved the blob to /usr/bin (directory where fastboot lives) and do
Code:
fastboot devices
Result is
Looking good, right?
Now I try
Code:
fastboot -i 0x0b05 flash system blob
and it just sits there. Same thing if I try
Code:
fastboot -i 0x0B05 reboot
How do I get fastboot to work?
Click to expand...
Click to collapse
Don't worry 14.8 is the same as 14.10 so you don't need to upgrade
gdselzer said:
Now I try
Code:
fastboot -i 0x0b05 flash system blob
and it just sits there. Same thing if I try
Code:
fastboot -i 0x0B05 reboot
How do I get fastboot to work?
Click to expand...
Click to collapse
You may want to go to the Asus setting and select the "developer options". Enable the "USB debugging" and try the fastboot again, good luck..:fingers-crossed:
gdselzer said:
I moved the blob to /usr/bin (directory where fastboot lives)
Click to expand...
Click to collapse
If you're root that should work, but you shouldn't do this. Putting non-programs in /usr/bin the wrong thing to do, and you should normally not work as root either. Instead you should have your udev rules set up so you can access your device with your normal user account. Your files should be somewhere in your home directory. If you don't specify a path for your blob in the fastboot command line, your blob must be in the *current* directory.
But if you do work as root (dangerous as it is), you can avoid setting udev rules. Your blob must still be in your current directory, not in the directory where fastboot is. Or you specify the path to your blob, e.g. "fastboot flash system ~/tf700/blob" (or wherever you put it).
sbdags said:
Don't worry 14.8 is the same as 14.10 so you don't need to upgrade
Click to expand...
Click to collapse
Good to know. I flashed the ROM and all seemed to work fine. That said, I still think it would be good to get fastboot working...
gdselzer said:
Good to know. I flashed the ROM and all seemed to work fine. That said, I still think it would be good to get fastboot working...
Click to expand...
Click to collapse
Oh YES!!!!
Essential, actually IMO
I've been reviewing posts similar to mine, but still not able to either grasp the solution, or get it to work. Here's what's going on...
Tab was running fine last I knew, battery was just run down. I plugged it into my computer to charge, I booted it up, and I saw the "android is upgrading" window I get whenever I start up. Ok. Running katkiss v26 I think btw. Well, the battery must have died during that process as I noticed it at a 0% as it was shutting down. I plug it into a normal plug and notice it just continues rebooting at the Asus splash screen. I can get to TWRP, but it just reboots at that splash screen too. Cold boot does not work. I have no experience with ADB, but I tried it anyway, just a simple fastboot reboot, and that was uneventful. I had to hold down the vol up button to get it to stop rebooting. It's starting to look like my next teardown project. Any thoughts?
Sent from my iPhone using Tapatalk
Also, can someone clarify how commands should be entered in ADB? I've tried doing some suggested in the tread below, but just get a big list of commands.
Sent from my iPhone using Tapatalk
Something was not quite right with your installation to begin with. You should not get the "Android is upgrading" on each boot. That probably could have been fixed with a quick wipe of cache and Dalvik. Well - water under the bridge.
Katshmallow is a pretty power hungry rom. I would not be surprised if the trickle charge your PC's USB port provides was not sufficient to keep it from crashing due to no juice.
Alright, to fix it we need to clear up your adb/fastboot confusion.
You can use adb either in recovery (if the recovery supports it and TWRP does) or in Android, that means with a booted tablet. You can do neither, so you cannot use adb commands.
If you are very lucky you may have adb access while the recovery is boot looping, try it with "adb devices", and then you could at least pull your data off the tablet with the command "adb pull /sdcard".
but I doubt that very much so probably your data is toast if you did not back it up.
What you can do is use fastboot. That's a protocol you can use when booted into the bootloader. Since you cannot even boot the recovery my advice would be to fastboot flash the Asus stock blob and start from scratch.
Read the OP here http://forum.xda-developers.com/showthread.php?t=2688891 for background info
and then follow these instructions: http://forum.xda-developers.com/showpost.php?p=68041322&postcount=292
Thanks for the response and help so far. Can you expand a bit on how to flash the blob? I have it, but am either not putting it in the right place, or pasting the command wrong, as I just get a list of options in ADB. Where should my fastboot directory be? I've made a fastboot folder at the root of my c drive, but that didn't work, and I've also put the blob where minimal adb is installed. Thanks again.
Hello.
I think you need firts to load your tablet with the power plug and after that I think it will startup the normal way.
Loading with an USB is very very slow on this tablet.
Good luck
Scenic-3
Thanks Scenic. Unfortunately, usb, power plug, or unplugged, it just boot loops.
Sent from my iPhone using Tapatalk
n8w said:
Thanks for the response and help so far. Can you expand a bit on how to flash the blob? I have it, but am either not putting it in the right place, or pasting the command wrong, as I just get a list of options in ADB. Where should my fastboot directory be? I've made a fastboot folder at the root of my c drive, but that didn't work, and I've also put the blob where minimal adb is installed. Thanks again.
Click to expand...
Click to collapse
Read the Beginner's Guide and make sure you have a fastboot connection. If you get a positive return with 'fastboot devices' you put the blob into the directory were your fastboot.exe is and run the commands as posted.
I must be missing something very basic.
I enter "fastboot devices" and get a hit, so that's good.
I have the blob from US_epad-user-10.4.4.20 in my minimal adb and fastboot folder right along with the exe's.
I then enter "fastboot - i 0x0b05 flash system blob" but only get the list of options. I've tried "fastboot - i 0x0b05 flash blob" and fastboot - i 0x0b05 flash US_epad-user-10.4.4.20.blob" and fastboot - i 0x0b05 flash blob.blob all with the same result.
I've read through the beginners guide, but didn't see anything related to the blob file. I'm sure I'm missing something basic, but this aspect is all very new to me, so I need it spelled out like a first grader.
STOP!
This is the TF700 forum, so I assumed you have that tablet! 10.4.4.20 us not TF700 firmware! What tablet do you have???
Sent from my Nexus 5X using Tapatalk
Well, the would certainly be an issue wouldn't it. I do have a tf700. Looks like I grabbed the wrong file. I thought that was iffy.
Sent from my iPhone using Tapatalk
Tf700t stuck in boot and can't get to recovery
Hi all,
I have no idea what happened but mine too was fine yesterday and now will not boot. I also can't get boot into recovery. It's also not being recognised by my win7 machine.
This us my 2d Asus tf700t and live the size and screen but I think that I must be jinxed. I've been rooting/customising since the G1 but this tablet has me stumped.
I've looked over the forums (including the beginner's guide) but just don't know enough and need help.
Also if there is a place that I could send to in the Boston, MA area that they might fix it for me.
Thanks everyone.
Ps if I can't fix it what might be a good replacement with the same or better screen.
This is screwy then.
I go to http://forum.xda-developers.com/showthread.php?t=1946456 , and scroll down to "ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update-md5: b06ff04ba888435f744f3c85ec0c6256 - size: 456MB." But you're saying that's not tf700 firmware?
I found this one below and gave it a go, but to no avail again. Pulled the blob, put it in the minimal adb directory, ran "fastboot - i 0x0b05 flash blob" and again got the list of options.
Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update - MD5 Sum: 2248ec635ea96768a5e1dfbbc996a879 - Size: 370.37 MB (388358205 bytes)
I finally thought I got smart and got this from the asus site: US_epaduser10_6_1_14_10_UpdateLauncher. Did the same routine of pulling the blob and attempting to flash it with "fastboot - i 0x0b05 flash blob", but still just getting a list of commands. Should I be entering the command differently? Have I missed a step? Arg.
n8w said:
This is screwy then.
I go to http://forum.xda-developers.com/showthread.php?t=1946456 , and scroll down to "ASUS Transformer Pad TF700T Firmware: V10.4.4.20 Only for US SKU (Android 4.1.1)-2012.11.07 update-md5: b06ff04ba888435f744f3c85ec0c6256 - size: 456MB." But you're saying that's not tf700 firmware? What am I supposed to be installing then?
What about this?
Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update - MD5 Sum: 2248ec635ea96768a5e1dfbbc996a879 - Size: 370.37 MB (388358205 bytes)
Click to expand...
Click to collapse
Ok, you're right it is TF700 firmware. But so old that I forgot about it! :laugh:
And definitely not firmare you want to flash. You can't flash any halfway recent rom on that bootloader.
You want 10.6.1.14.10, the last firmware released for this tablet: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Finally got it. Thanks for the help. The issue was that I wasn't pointing adb in the right place with my line to flash. I didn't realize that I needed to make it "fastboot -i 0x0B05 flash system c:\ADB\blob," but that did the trick.
n8w said:
Finally got it. Thanks for the help. The issue was that I wasn't pointing adb in the right place with my line to flash. I didn't realize that I needed to make it "fastboot -i 0x0B05 flash system c:\ADB\blob," but that did the trick.
Click to expand...
Click to collapse
Only if you did not open the cmd window from your fastboot directory:
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Shift + right click and select "Open command window here".
For Win XP click here
Click to expand...
Click to collapse
But I'm glad you got it sorted
I must have missed the red part
Does that do the same as starting ADB? This is my first venture into using commands.
Sent from my iPhone using Tapatalk
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?