Database Info

What to do if you DONT have s-off, and recovery takes a dump on you (and cant boot)

This may have been posted before but this just SERIOUSLY saved my ass this morning.
Only use this method if you phone will not:
Boot into your:
Recovery
ROM
Anything else besides HBOOT (hold vol. down and turn on phone)
Get an RUU from somewhere and pull the rom.zip file
Rename it to HERCIMG.zip
Put on ROOT of sdcard
Reboot to hboot as per instructions above
If you renamed it right it will say:
SD Checking...
Loading.....[HERCDiag.zip]
No image!
etc.etc.etc
then
Loading...[HERCIMG.zip]
You will see a progress bar on the upper right of the screen.
It will ask you if you want to upgrade. Press Action (trackball btn) for yes.
***YOU WILL LOSE EVERYTHING! Root/files/etc. just like if you flashed it with the RUU setup file***
After it finishes you now have a working hero again

Very helpful post. Saved me once.
Also, a tad off topic, but if you are S-OFF, you can flash the recovery only (clockworkmod tested). This might save some time vs a total reflash.
google clockwork recovery, find the 2.5.0.1 img file for the heroc. Get an android-info.txt from an exisiting HERCIMG.zip (either find one on xda in this forum, or follow OP instructions and get it from ROM.zip) and zip it along with the clockwork recovery .img file. Rename it to HERCIMG.zip and flash from hboot.
You can also create custom RUU with a clockwork recovery by replacing the stock recovery img in an HERCIMG.zip with the clockwork recovery .img, and then flashing. You will get sprint stock but with clockwork recovery instead of the stock recovery.
Just a few tips I've learned. Remember mine requires S-OFF, which is opposite of what the OP is working with.

Well this is very helpful.
BUT! Here is the issue I am now having...
My phone wont boot into android... OR recovery (stock).
I know the recovery is stock since I just flashed the RUU from the carrier.. So I am thinking maybe a corrupt partition?
Major worry I am having is I did flash the engineering spl however it is still in s-on mode (dunno why) so I cant even boot into a custom recovery to flash back the old spl. Is it possible to flash the spl with the method you mentioned? If so I will do that and then if it still doesn't boot (I know it wont btw) I will take it in store.

hexskrew said:
Well this is very helpful.
BUT! Here is the issue I am now having...
My phone wont boot into android... OR recovery (stock).
I know the recovery is stock since I just flashed the RUU from the carrier.. So I am thinking maybe a corrupt partition?
Major worry I am having is I did flash the engineering spl however it is still in s-on mode (dunno why) so I cant even boot into a custom recovery to flash back the old spl. Is it possible to flash the spl with the method you mentioned? If so I will do that and then if it still doesn't boot (I know it wont btw) I will take it in store.
Click to expand...
Click to collapse
I tried the eng-spl also to get fastboot working but that didn't seem to work either. Not sure why. I used the other S-OFF method flashed via clockwork.
This wouldn't be an issue if we could use fastboot on our phones (I always get access denied). I think the eng-spl was supposed to enable the use of fastboot.
If you think the eng-spl worked, try using fastboot to wipe your partitions. I think there was talk about this in the firerat mod thread. I don't recall the exact commands, but it's run like adb is from the command line. I think fastboot system -w erase but I could be wrong... probably best to check the firerat mod thread.
btw about your question, I am not sure if you can flash anything else via hboot other than what I tried. At least I think this is what you were asking.

Porkrinds said:
I tried the eng-spl also to get fastboot working but that didn't seem to work either. Not sure why. I used the other S-OFF method flashed via clockwork.
This wouldn't be an issue if we could use fastboot on our phones (I always get access denied). I think the eng-spl was supposed to enable the use of fastboot.
If you think the eng-spl worked, try using fastboot to wipe your partitions. I think there was talk about this in the firerat mod thread. I don't recall the exact commands, but it's run like adb is from the command line. I think fastboot system -w erase but I could be wrong... probably best to check the firerat mod thread.
btw about your question, I am not sure if you can flash anything else via hboot other than what I tried. At least I think this is what you were asking.
Click to expand...
Click to collapse
What I was wondering is if I could flash either an original HBOOT, or to put it back to S-On by the method you described.
OR....
Does the original hboot have the option for fastboot? If so then I will just bring the phone in for service

hexskrew said:
What I was wondering is if I could flash either an original HBOOT, or to put it back to S-On by the method you described.
OR....
Does the original hboot have the option for fastboot? If so then I will just bring the phone in for service
Click to expand...
Click to collapse
Well, if you are S-ON right now, you can't flash anything that isn't signed with HTC's private key I believe.
You should be able to get to fastboot via hboot menu... just boot into hboot (power off, vol dwn + power on) and see if there is an option to get to fastboot (I think it's home key? I forget). Thing is... we can't do anything using fastboot (as end users) because it's turned off. The eng-spl was/is supposed to turn that on as well as S-OFF if I understand correctly.
Since you tried the eng-spl, have you tried hooking up to USB, booting into HBOOT and then jumping to fastboot and seeing if you can do any fastboot commands?
Sadly, the only two ways I know to flash something is either via a recovery like clockwork, or via S-OFF via HBOOT. Fastboot is possible, but like I said before it seems to have been turned off..

fastboot works after you flash the eng-spl. you'll have to look for the commands to use it though. ive used it once after flashing the eng-spl just to verify it worked.

Well, I did flash the ENG-SPL like I said and I did try to use fastboot from HBOOT, however nothing ever worked except for the fact that I could see that fastboot detected it when using "fastboot devices".. fastboot reboot wouldn't even work though. It would say that it worked but it actually did not.
No biggie though, as like I said I flashed the RUU to wipe it. It still wouldnt boot but that's ok cause I got a replacement today

Awesome post, thanks. I'm tagging this should the unfortunate event happen.

hunterd13 said:
fastboot works after you flash the eng-spl. you'll have to look for the commands to use it though. ive used it once after flashing the eng-spl just to verify it worked.
Click to expand...
Click to collapse
Good info thanks. I think I might have been S-OFF via unrevoked already so maybe that is why the eng-spl didn't work for me (as far as being able to use fastboot, I still got access denied errors).
OP: glad you got it fixed the easy way

Possible Brick

Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"

Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app

whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!

Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app

whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!

Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville

usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!

You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville

Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!

Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.

Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?

Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?

Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.

Need help rooting and/or flashing twrp

Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.

Shad0w32 said:
Hello everyone!
I need some help rooting my tf300t, because what I've read here and there was somewhat useless, since everyone sais different stuff. For first I'd like to ask for your help in clarifying which one is first. I have read guides in which rooting was first than pushing the recovery, and I have read ones in which fasbooting recovery was the first thing to do, and than flashing su. I have tried both methods, with no luck. When I try to fastboot twrp onto my device, it sais 'waiting for device'. I read that this means fastboot is not properly configured, but I am an administrator on my PC and I have the proper drivers, since adb reboot-bootloader works. So thats for flashing twrp first. Then rooting first. I tried with motochopper, but that does no work on 10.6.1.27.5. So I tried pushing root files manually, but when adb shell /data/local/temp, it sais failure. So if you could help me, of what did I do wrong, I'd greatly appreciate it.
Click to expand...
Click to collapse
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.

cmendonc2 said:
First make sure that you have unlocked your bootloader (text in the upper right corner of boot screen). What I did first was flash TWRP from ADB. In your case, you would flash the stock ROM, and then flash SU.
Click to expand...
Click to collapse
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance

Shad0w32 said:
I know I'm unlocked sorry for not mentioning that, though even that was strange, because the unlock device app should have wiped the memory, but it didn't, and still unlocked. But I don't exactly understand what you mean by flashing the stock ROM, then SU. And if you mean that do that with twrp, I can't because fastboot flash recovery twrp.blob just waits for device. Is there another method which I can flash it with? Thanks in advance
Click to expand...
Click to collapse
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.

graphdarnell said:
If it says "waiting for device," your PC is not communicating with the tab. What Windows version do you use? Does "fastboot device" command from fastboot mode on tab return any serial number? It should show a serial number before you can flash TWRP onto the tab. And where did you read that unlocking the device would wipe the memory?
Get fastboot to work first, then you can flash whatever. Otherwise, if you're on stock recovery, try loading the rom zip file onto your sd card and flash it using RCK option. If you have no idea what I'm talking about, read first, so you don't brick your tab just because you have no idea what the heck you're doing.
Click to expand...
Click to collapse
For first, I downgraded my device, so I could root it with motochopper. Then I flashed recovery with the way explained here:http://forum.xda-developers.com/showthread.php?t=1845377
Now twrp seems to be working, i can start it, but it cant mount anything, so i cant flash anything from the device. Both 2.5 and 2.4.4 does this. Goo manager cant find a recovery for this device, so i cant use that either. Fastboot still cant see my tab. Im on windows 7, with proper drivers

Nevermind my stupidity, I installed the wrong recovery, not the one for the 4.2 bootloader. By now I'm a proud owner of a tf300t with cyanogenmod on it Thank you both though, for trying to help

[Q] Fastboot Brick (CM11 v.12)

Hi, I rooted my Froyo 2.2 Optimus One (LG-P500) with z4root (http://forum.xda-developers.com/showthread.php?t=833953) then I installed CWM with ROM manager.
I installed CM11 v.12 (http://forum.xda-developers.com/showthread.php?t=2589303) following AROMA installer steps; I rebooted my phone and I saw this:
http://3.bp.blogspot.com/-nl2aGm8NgoI/T4qw9y80_cI/AAAAAAAADvQ/w5IbpEFH-Yk/s1600/IMG_3388.JPG
I read this guide to unbrick the phone (http://forum.xda-developers.com/showthread.php?t=1088046&page=9) but it seems for people that have bricked their recovery while I can correctly run it. Have I to follow this guide anyway? Then? Where I'm wrong?
Thank you all!

steve281188 said:
Hi, I rooted my Froyo 2.2 Optimus One (LG-P500) with z4root (http://forum.xda-developers.com/showthread.php?t=833953) then I installed CWM with ROM manager.
I installed CM11 v.12 (http://forum.xda-developers.com/showthread.php?t=2589303) following AROMA installer steps; I rebooted my phone and I saw this:
http://3.bp.blogspot.com/-nl2aGm8NgoI/T4qw9y80_cI/AAAAAAAADvQ/w5IbpEFH-Yk/s1600/IMG_3388.JPG
I read this guide to unbrick the phone (http://forum.xda-developers.com/showthread.php?t=1088046&page=9) but it seems for people that have bricked their recovery while I can correctly run it. Have I to follow this guide anyway? Then? Where I'm wrong?
Thank you all!
Click to expand...
Click to collapse
Still can run recovery? Did you do a backup before attempting any of this? If so, restore it. If not, well, live and learn

Recovery is ok
Dovidhalevi said:
Still can run recovery? Did you do a backup before attempting any of this? If so, restore it. If not, well, live and learn
Click to expand...
Click to collapse
As I wrote, recovery is working fine; unfortunately, I have no backup.
EDIT: I tried flashing CM11-v.11, no way. Is the problem what I flash? Or it's nothing to do about it? (I'm thinking about flashing stock rom)

steve281188 said:
As I wrote, recovery is working fine; unfortunately, I have no backup.
Click to expand...
Click to collapse
Know for the next time
Here is a backkup of a older ROM http://forum.xda-developers.com/showthread.php?t=2711770
This runs new baseband. If you still have old baseband, find the old baseband fix and flash afterwards or adb push the three files to /system/lib/. No need to even reboot in this case.

CM10
Dovidhalevi said:
Know for the next time
Here is a backkup of a older ROM http://forum.xda-developers.com/showthread.php?t=2711770
This runs new baseband. If you still have old baseband, find the old baseband fix and flash afterwards or adb push the three files to /system/lib/. No need to even reboot in this case.
Click to expand...
Click to collapse
Thanks!
What if I just flash this? (http://forum.xda-developers.com/showthread.php?t=1811325)

steve281188 said:
Thanks!
What if I just flash this? (http://forum.xda-developers.com/showthread.php?t=1811325)
Click to expand...
Click to collapse
Can certainly try it. Newer ROMs do work better than this, however. If you were on Froyo, you will need the old baseband fix for any of these ROMs. It's OK, I use it myself.
Note that for KitKat, you need the newer recovery Clockwork 6.0.4.8. For others, the older 6.0.2.7, etc.
Maybe get your phone working again with that backkup before trying any other ROMs.

CWM
Dovidhalevi said:
Can certainly try it. Newer ROMs do work better than this, however. If you were on Froyo, you will need the old baseband fix for any of these ROMs. It's OK, I use it myself.
Note that for KitKat, you need the newer recovery Clockwork 6.0.4.8. For others, the older 6.0.2.7, etc.
Maybe get your phone working again with that backkup before trying any other ROMs.
Click to expand...
Click to collapse
OK thanks! I notice now that ROM manager installed me a 5.0.2.0 CWM recovery! Is this the problem?
How can I upgrade it?
Regards

steve281188 said:
OK thanks! I notice now that ROM manager installed me a 5.0.2.0 CWM recovery! Is this the problem?
How can I upgrade it?
Regards
Click to expand...
Click to collapse
Use this to flash ROMs up to Kitkat.
For Kitkat, need the 6.0.4.8 version which can be flashed using recovery. ROM manager does not download newer versions.

brick
I flashed CWMod-6.0.4.8-June04 "img" file (taken here "http://forum.xda-developers.com/showthread.php?t=2564767") through the command "fastboot flash recovery recovery.img" in fastboot mode, and now it's a total brick (black screen).
I'm not really lucky
EDIT = i can't enter fastboot mode neither. I'm not sure if it's because the back button is faulty (that is true but I succeded the first time) or even fastboot mode is broken (is it possible?)
Looking for a new phone, thanks all

steve281188 said:
I flashed CWMod-6.0.4.8-June04 "img" file (taken here "http://forum.xda-developers.com/showthread.php?t=2564767") through the command "fastboot flash recovery recovery.img" in fastboot mode, and now it's a total brick (black screen).
I'm not really lucky
EDIT = i can't enter fastboot mode neither. I'm not sure if it's because the back button is faulty (that is true but I succeded the first time) or even fastboot mode is broken (is it possible?)
Looking for a new phone, thanks all
Click to expand...
Click to collapse
You can get these phones dirt cheep in some places now.
Last try.
Take out battery, press home/volume-down/power, replacing battery. Or variations of this scheme. Since I have never succeded in running fastboot, this is how I got my phone back after similar mishaps. Try several times. (Make sure you have charge on that battery because that will to it as well!)
I flashed that image from adb shell: flash_image recover /sdcard/....img. There is also a normal zipped version that can be flashed from whatever recovery you have up, but not recommended. Using the adb method, if it fails, one can IMMEDIATELY flash an img that is known to work and not be bricked!

Dovidhalevi said:
Last try.
Take out battery, press home/volume-down/power, replacing battery. Or variations of this scheme.
Click to expand...
Click to collapse
is this the recovery combination? I tried but I'll try again.
Dovidhalevi said:
I flashed that image from adb shell: flash_image recover /sdcard/....img.
Click to expand...
Click to collapse
where I was wrong?
Dovidhalevi said:
There is also a normal zipped version that can be flashed from whatever recovery you have up, but not recommended.
Click to expand...
Click to collapse
are you talking about flashing a recovery with a recovery? why it's not recommended?
Dovidhalevi said:
Using the adb method, if it fails, one can IMMEDIATELY flash an img that is known to work and not be bricked!
Click to expand...
Click to collapse
sorry, I don't understand this part.

steve281188 said:
is this the recovery combination? I tried but I'll try again.
Click to expand...
Click to collapse
Yes, but more physical action. Sometimes manipulating the battery can get back into recovery. Cost nothing to try.
are you talking about flashing a recovery with a recovery? why it's not recommended? ...
sorry, I don't understand this part.
Click to expand...
Click to collapse
If the flash that recovery zip (overwriting the current one) and this fails. Brick.
If I am alive in adb and I flash_image the recovery .img and it fails, I now have no valid recovery but am still alive, and can then flash_image another that is known to succeed..
Problem is that our phones are restricted to a 5 meg recovery section. The dev worked hard to get the new CWM small enough (taking out some functionality such as partioning sdcards to do so), but it is right on the line. On some phones, unluckily maybe yours, it doesn't quite fit on. There is also a new TWRP recovery around, same restriction but maybe would be OK.

Dovidhalevi said:
Yes, but more physical action. Sometimes manipulating the battery can get back into recovery. Cost nothing to try.
If the flash that recovery zip (overwriting the current one) and this fails. Brick.
If I am alive in adb and I flash_image the recovery .img and it fails, I now have no valid recovery but am still alive, and can then flash_image another that is known to succeed..
Problem is that our phones are restricted to a 5 meg recovery section. The dev worked hard to get the new CWM small enough (taking out some functionality such as partioning sdcards to do so), but it is right on the line. On some phones, unluckily maybe yours, it doesn't quite fit on. There is also a new TWRP recovery around, same restriction but maybe would be OK.
Click to expand...
Click to collapse
I flashed the recovery that bricked the phone exactly through fastboot shell with the command above. So where I was wrong?
Is it possible I've "bricked" fastboot mode too? Or I can't enter fastboot anymore just because my back button is faulty?
thanks!!!

steve281188 said:
I flashed the recovery that bricked the phone exactly through fastboot shell with the command above. So where I was wrong?
Is it possible I've "bricked" fastboot mode too? Or I can't enter fastboot anymore just because my back button is faulty?
thanks!!!
Click to expand...
Click to collapse
I have never succeded in getting fastboot from my PC. Did it in an adb shell session (which means android or recovery was alive and kicking).
What messages did you see on the flash_image? Any error? Did it fit?
From the adb shell, if the flash_image fails, I can flash another img which I know is OK (must have that around on the sdcard). Then, no harm done. Otherwise, it is possible that the flash over-wrote the existing recovery, but failed. Thar's the problem.

recovery
When I flashed recovery from fastboot shell, everything was ok and no errors showed up.
From that moment, screen is always black.

Unable to root after OTA update

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