Related
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
shadowboxx said:
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
Click to expand...
Click to collapse
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
brickdummy said:
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
Click to expand...
Click to collapse
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
when i flashboot the recovery.img file it goes to the red triangle.
brickdummy said:
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
Click to expand...
Click to collapse
Hi the program is actually called 4EXT Recovery Touch. I finally was able to open it through fastboot....Now all thats left is to find the right zip file to put my phone back to stock.
shadowboxx said:
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
Click to expand...
Click to collapse
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
shadowboxx said:
(on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Click to expand...
Click to collapse
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
brickdummy said:
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
Click to expand...
Click to collapse
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
As for your post in your other thread, read my signature.
bananagranola said:
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
Click to expand...
Click to collapse
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
brickdummy said:
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
Click to expand...
Click to collapse
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
bananagranola said:
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
Click to expand...
Click to collapse
Ok, one more thing. I have S-ON. does that matter?
----
It did not, lol anyway it worked. Thank you everyone for you help. I really appreciate it.
-----
For those wondering I found the stock rooted rom here http://http://forum.xda-developers.com/showthread.php?t=996368
http://forum.xda-developers.com/showthread.php?p=26617631
Instructions to flash the rom
http://http://forum.xda-developers.com/showthread.php?t=2168500
brickdummy said:
Ok, one more thing. I have S-ON. does that matter?
Click to expand...
Click to collapse
Yes. You need to read the part in my signature about being stuck in the splash screen.
bananagranola said:
Yes. You need to read the part in my signature about being stuck in the splash screen.
Click to expand...
Click to collapse
ok, got it. Thank you again
Dear friends,
I have this problem: I got a brand new TCL S720 and the Google Play did not work, being a known rom issue. So, before doing anything, I've managed to make a backup of it's original rom with MTK Droid tools whichI supose it did it well. Then I've tried to install a CWM recovery to try a custom rom for it. The CWM recovery seemed to install succesfully but I didn't manage to install the new rom. If I remember well, it stucked on boot logo. Then tried to revert at it's original stock recovery, managed to have the phone back as it was in initial state, but doing more tries, It remained stucked on boot logo. The problem is that my computer doesn't recognise it anymore, when I connect it to USB it tries to install MTP usb driver but even before the driver was installed well, now it refuse to install, like the driver is not good or the proper driver doesn't exist. So the only thing I can do is to boot on stock recovery but even I tried to copy the original rom update.zip on external SD and to flash the phone using install update from sd card in recovery mode, It doesn't find the external sd card. So I'm stuck here, the computer doesn't detect the phone to try flashing it with SP flash tool or MTK Droid tool, and I also can't flash it from sd card. Have you any idea how to make it work again?
Thanks in advance.
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.
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.
fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7
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!