• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Flashed a recovery for a different device - Am I bricked?

S

saxophown3d

Lurker
So... I just made a pretty stupid error.

I recently tried to flash a newer version of TWRP recovery onto my Awe which was currently running an older version of CWM. I was in CWM recovery and then chose the TWRP file to flash and the flash completely successfully...

... or so I thought. A word of advice: Don't use the same SD card to install recovery for two different devices. I ended up installing a TF101(Transformer Tablet) recovery TWRP onto my phone instead of the correct recovery. Now, whenever I try to boot the phone, I can't get anywhere. If I take out the battery and put it back in, I'm greeted with a red light in the corner, but it doesn't advance further than this. When I plug it into my desktop, it doesn't recognize it. From the way I see it, my phone is bricked.

However, I was hoping someone could convince me otherwise. I would really, really like to be convinced. Does anyone have an idea of how to get into a proper recovery? I have a backup on the sd card along with the correct recovery zip, if that makes a difference. Any help at all will be appreciated!
 
Welcome to the forum - and sorry it has to be in these circumstances!

I should say that I don't know this device at all, so am only going to make a couple of generic suggestions. Obviously you can't flash a working recovery from recovery now, because you don't have a working recovery to do the flashing from. So the question is can you reflash the device from a computer over USB?

The key question is whether you can get the phone into the bootloader, which usually involves pressing some key or keys while booting (varies between phones). If you can then there's a chance. This guide to unrooting may help. In fact if you can get a compatible recovery image (e.g. extract the img from the recovery zip file) and can get the phone responding to fastboot you could try:

fastboot flash recovery recovery.img

where "recovery.img" should be replaced by the name of your recovery image file. If we're really lucky and nothing else was corrupted when you flashed the wrong recovery that might be enough to fix it (replace the bad recovery with a good one). Otherwise flashing completely back to stock as described there should, if it works, give you your phone back.

If anyone who actually knows this phone responds please listen to their advice, because I have never even touched an Awe so cannot claim any expertise with it. But if not that would be what I'd try.
 
if I rember there is an unbrick kit that put on SD card some were here do some diving should find it .try holding volume up botton then hold power bottom should get whit box if so then there might b chance just look through these therds there people herd that can help u good luck
 
I've seen this happen before, and the prognosis for this sort of thing isn't usually very good. It all depends on what partition that recovery flashed to. Try holding volume up+power while your phone is off, if it works and you get to FTM mode, try this http://androidforums.com/awe-all-things-root/850926-fix-soft-brick-one-click-fix.html

Edit: Linking us to the specific recovery you accidentally flashed would provide worlds of info. We can check the scripts, and see what it overwrote. :D
 
Hey everyone, thanks for the responses!

To answer Hadron, when I connect the device to the computer, it cannot detect my device, so I don't think I will be able to get it to respond to fastboot.

Unfortunately, when I try to boot holding volume up and the power button, nothing happens; my phone stays dark. The only response I get is the notification LED lighting up red for about half a second, and this only happens after I take out the battery.

Also, the recovery that I flashed is TF101 TWRP 2.7.1.1. This is the page for 2.7.1.3, but I'm sure the difference is minimal.
 
It looks like it overwrote /dev/block/mmcblk0p4 which the partition is named "rpm". I'm not exactly sure what it is but it must of been important if you can't even turn on the phone after overwriting it.
 
Is there a way that I can connect to the phone and factory reset? I have a custom recovery image that I can work with, but considering that the phone won't boot into recovery, fastboot, or connect the computer, is there any possible way I can use this recovery image?
 
saxophown3d said:
Is there a way that I can connect to the phone and factory reset? I have a custom recovery image that I can work with, but considering that the phone won't boot into recovery, fastboot, or connect the computer, is there any possible way I can use this recovery image?
Click to expand...
Try the to access ftm mode while attached to a pc just bcuz its not recognized normally doesnt mean it wont b in ftm mode... If it is recognized try my soft brick fix posted a few posts up... If not im afraid u may have a dead device until a hard brick fix is available
 
Unfortunately, it does not boot to anything :( when I try to boot the phone after taking out the battery, the notification LED flashed red for about half a second and then goes dark. The screen, however, doesn't turn on, whether it be normal boot, recovery, or ftm boot.
 
mine did the same thing one flashed wrong recovery I pulled bat and charger cord unpluged then while bat removed pushed power button several times then let it boot and it did ten I used a flash tool from play store flashed cwm then then rebooted in cwm then flashed twrp worked fore me worth a shot can't hurt
 
saxophown3d said:
Unfortunately, it does not boot to anything :( when I try to boot the phone after taking out the battery, the notification LED flashed red for about half a second and then goes dark. The screen, however, doesn't turn on, whether it be normal boot, recovery, or ftm boot.
Click to expand...

Alright, so no green android or backlit black screen or nothing?
 
I would suggest pulling the battery, and trying to boot ftm, then connect your phone to the PC and see if it recognizes it anyways. You might not see anything on the screen but it could still be booting into ftm. I found a file that probably corresponds to /dev/block/mmcblk0p4, but there doesn't appear to be any info on it. Its called, rpm.mbn. Its in, /system/etc/firmware/ and also, etc/firmware. Looks inconsequential to me.
 
saxophown3d said:
So... I just made a pretty stupid error.

I recently tried to flash a newer version of TWRP recovery onto my Awe which was currently running an older version of CWM. I was in CWM recovery and then chose the TWRP file to flash and the flash completely successfully...

... or so I thought. A word of advice: Don't use the same SD card to install recovery for two different devices. I ended up installing a TF101(Transformer Tablet) recovery TWRP onto my phone instead of the correct recovery. Now, whenever I try to boot the phone, I can't get anywhere. If I take out the battery and put it back in, I'm greeted with a red light in the corner, but it doesn't advance further than this. When I plug it into my desktop, it doesn't recognize it. From the way I see it, my phone is bricked.

However, I was hoping someone could convince me otherwise. I would really, really like to be convinced. Does anyone have an idea of how to get into a proper recovery? I have a backup on the sd card along with the correct recovery zip, if that makes a difference. Any help at all will be appreciated!
Click to expand...

Perfect, ok I know your situation. Ur hard bricked. Me and a few devs came up with a hard brick fix a while ago. When your device turns on its actually in Download mode. You will need linux to fix this....
 
You must log in or register to reply here.
Back
Top Bottom