So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!
I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?
in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!
ok i did all that but it removed fastboot what do i do to get it back?
Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os
Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.
_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue
Related
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
stedrocklp said:
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
Click to expand...
Click to collapse
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Thank you Thank you Thank you!
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
That was definitely the problem and I had been trying everything for the past two days. I appreciate you taking the time to reply.
asus tf300 help
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Did I brick it?
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
solution
mizifih said:
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
Click to expand...
Click to collapse
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
jijitax4 said:
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
Click to expand...
Click to collapse
What if you can only boot to APX mode? I only have the option of using that because my unlocked bootloader got erased in the process of updating to JB. Is there a way to install a bootloader using fastboot? Or will it only work with an existing bootloader?
In other words, when I issue the fastboot command
fastboot -i 0x0B05 flash system blob
I get "waiting on device" and nothing happens after that.
Thank you, this worked !!!!!!
I just got my new asus transformer tf300t-bl and wanted to root and install either twrp or cwm on it,I unlocked it and when i went to reboot it i hit the volume up on the RCK and now its stuck on RCK and it didnt boot into the usb like it says it will on the forums. Now when i reboot it,it says " key driver not found.. booting os android cardhu-user bootloader < 1.00 e> released by "us_epad-10.6.1.8-20130225" a03 starting Fastboot usb download protocol. does anyone know what i can do? i would greatly appreciate ANYONES HELP THAT KNOWS IF THEY'VE DONE THIS TO THEIRS AND IF THIS IS FIXABLE. I USE THIS FOR COLLEGE AND JUST PAID $ 400 and cant afford to buy another one. Somebody please tell me i havent screwed the pooch and that it still can be flashed into recovery and rooted. Thanks you guys. As i rooted and flashed my transform ultra perfectly because of you guys and used the megatron 6 and love it.
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
flashing recovery/ ref: help me
sevenalive said:
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
Click to expand...
Click to collapse
im a lil new to doing this so would you please give me a detailed list of exactly what to do. and what firmware do i need to download from asus. And can all of this be done using a mac? and how do i flash it all to my comp. or from it to the tablet.
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
need your help plz
Hazard17 said:
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
Click to expand...
Click to collapse
i did everything it stated to do and when i get to the last steps to root my tf300t, it says adb cannot run as root in production builds. Im at a loss as to what to do at all. IM a noob, and i follow each command on terminal perfectly and everything executes till the last or itll say permission denied. What do i do or am i doing wrong. Im following the instructions of post forum.xda-developers.com/showthread.php?t=1720980
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
re: help me
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
420Misfit said:
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
Click to expand...
Click to collapse
well, I am using a win xp machine for fastboot. so I don't have the same issues. fastboot works fine, so that I use the normal fastboot process to flash the system and the recovery kernel.
I finally got it to work again by flashing the newest TWRP instead of CWM. It seems CWM does not yet work on the latest firmware.
I followed this guide for flashing TWRP with fastboot. This version actually also just asked me, if I want to root the device, I clicked yes and it was rooted. Perfect.
http://forum.xda-developers.com/showthread.php?t=2187982
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
I am in EXACTLY the same boat as you. The only difference is that I flashed TWRP instead of CWM. I finally decided that it was time to root my tablet...got tired of the lag. IIRC I've gotten the "key driver not found.. booting OS" error message since doing the OTA update to 4.2 (I did this prior to rooting.) Everything SEEMS to be working okay, but this bugs the heck outta me, and I'm sure it can't be a good thing. Hoping somebody will chime in with a fix for this. I've searched and searched to no avail.
So looks like I deleted my android files...................... yes kill me!!!
How it stands:
Im not able to load into Android. The tablet is Unlocked and able to only boot to twrp.
2 out 10 times im able to push a file trought. The other times I get a protocol failure.
I can adb push files but at this point I dont know what files to push. What rom or what do I need to push to get it back?
I also think I lost root since I got a msg from twrp that if I wanted to install something to get root back.....
Riken said:
So looks like I deleted my android files...................... yes kill me!!!
How it stands:
Im not able to load into Android. The tablet is Unlocked and able to only boot to twrp.
2 out 10 times im able to push a file trought. The other times I get a protocol failure.
I can adb push files but at this point I dont know what files to push. What rom or what do I need to push to get it back?
I also think I lost root since I got a msg from twrp that if I wanted to install something to get root back.....
Click to expand...
Click to collapse
Use fastboot to install you stock ROM again. Dont use adb push, you can install it from your computer. Then install the correct TWRP for your bootloader and get back to your favorite custom Rom
how do I use fastboot? Is there a guide to use fastboot? Im searching lol Where can I get the stock rom?
Can I use a stock rom with twrp recovery?
Also for stock rom, its says to use the right rom with my SKU version. But I cant boot to find the sku....
Riken said:
how do I use fastboot? Is there a guide to use fastboot? Im searching lol Where can I get the stock rom?
Can I use a stock rom with twrp recovery?
Also for stock rom, its says to use the right rom with my SKU version. But I cant boot to find the sku....
Click to expand...
Click to collapse
When you restart you device and go to the recovery menu, and the top left corner where it says the device is unlocked, there will be the bootloader version. You need that to install the correct TWRP and stock ROM for your device.
When you get that stock ROM, take the stock ROM, extract the *.blob file. Copy that to your fastboot folder.
Restart your tablet and go to fastboot.
Now in CMD, type:
Code:
fastboot -i 0x0B05 flash system blob.blob
It will take about ~300 seconds if you did it right.
You can find the stock ROMs in the index thread in developer forum.
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.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!