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

Root Any chance of seeing a hard brick fix?

I don't got recovery anymore. That's the point. I'm completely bricked, only thing it boots to is the green Android. No FTM no nothing
 
Okay so apparently I shouldn't jump to conclusions so quickly. This time I was able to repair my phone with brittnearl soft brick fix (thank you very much) last time it was just the corrupt data partition that kept me from fixing my old one. Now however, I want to sort some things out. If I'm correct, you need older recoveries to install every ROM except for CM11, because of the updater binaries, is this right? Also have any of you others had problems with flashing recoveries over one another.
 
DsyMnapTic said:
I don't got recovery anymore. That's the point. I'm completely bricked, only thing it boots to is the green Android. No FTM no nothing
Click to expand...

Do you still have that original Awe you were having problems with? I ask because I know you had all sorts of problems after messing with cm11, and I had something similar happen yesterday. I was messing with the build.prop on cm11, and accidentally hex dumped the build.prop itself into the normal build.prop lines, when I rebooted, I then lost all root functions, my internal storage partition disappeared completely, emulatedstorage0= gone!, then couldnt reboot into recovery (scrambled screen), couldnt act as root through any app to replace the build.prop, but could still boot my phone...sometimes. I dont know if this would help with the older Awe, but it might. I ran root master again, while booted into cm11, rebooted, tried to updated the binary for the new super su that got installed, watched it fail, then, to my surprise was able to power off, and manually enter recovery, I wiped EVERYTHING! Then reflashed cm11, (it fixed the internal storage that was gone), wiped EVERYTHING again, then was able to restore a back up. This might be worth a shot.
 
Hmmm, kind of the same predicament I was in, however I couldn't flash anything, nor boot anything. Also no I'm no longer on the old Awe I had. I did run into problems with this new one again, though I'm unsure of the cause this time. Seems to have been caused by trying to flash recoveries through recovery, repetitively. I don't know, but I do know the recovery got corrupted some how and had to reflash one with the Rashr app. I'm beginning to think that's the safest way to flash recoveries anyhow. The only reason why anyone would need to in the first place (I'm thinking) is to flash older ROMs based off stock.
 
DsyMnapTic said:
Hmmm, kind of the same predicament I was in, however I couldn't flash anything, nor boot anything. Also no I'm no longer on the old Awe I had. I did run into problems with this new one again, though I'm unsure of the cause this time. Seems to have been caused by trying to flash recoveries through recovery, repetitively. I don't know, but I do know the recovery got corrupted some how and had to reflash one with the Rashr app. I'm beginning to think that's the safest way to flash recoveries anyhow. The only reason why anyone would need to in the first place (I'm thinking) is to flash older ROMs based off stock.
Click to expand...

I haven't flashed the stock rom with the most recent TWRP, but I've made and restored countless backups of stock. If I remember reading in the thread correctly, TWRP can flash anything that our cwm can, the big difference is that the updater script that cm11 uses needs TWRP to execute it.
 
Right on, well I'll have to go back and see... perhaps it just because I was trying to flash versions of ROMs that weren't up to date. I was doing a lot at once and using what I already had downloaded on my card. So chances are the updater binaries are operational with TWRP and I'm just behind the times :D
 
DsyMnapTic said:
Okay so apparently I shouldn't jump to conclusions so quickly. This time I was able to repair my phone with brittnearl soft brick fix (thank you very much) last time it was just the corrupt data partition that kept me from fixing my old one. Now however, I want to sort some things out. If I'm correct, you need older recoveries to install every ROM except for CM11, because of the updater binaries, is this right? Also have any of you others had problems with flashing recoveries over one another.
Click to expand...

use TWRP :) its the most stable and will work with all current roms, glad it worked out for u!
 
Hmmm, I found a culprit to my boot loops. Before I used to be able to flash and use any kernel, now anything BUT a stock kernel within a ROM, causes my phone only to be able to boot to the green android. Once again, I used to be able to boot and run these kernels all the way up to the 1.9ghz one.
 
DsyMnapTic said:
Hmmm, I found a culprit to my boot loops. Before I used to be able to flash and use any kernel, now anything BUT a stock kernel within a ROM, causes my phone only to be able to boot to the green android. Once again, I used to be able to boot and run these kernels all the way up to the 1.9ghz one.
Click to expand...

Im a lil confused what u mean???
 
Okay...phew, I got it...I GOT IT!
TWRP has issues flashing to the boot partition. I flashed back to stock rooted B05 with Philz and then flashed a kernel again just fine, no problems whatsoever. TWRP is the culprit to the phone getting stuck in a boot loop after flashing a boot.img. It has to be.
 
DsyMnapTic said:
Okay...phew, I got it...I GOT IT!
TWRP has issues flashing to the boot partition. I flashed back to stock rooted B05 with Philz and then flashed a kernel again just fine, no problems whatsoever. TWRP is the culprit to the phone getting stuck in a boot loop after flashing a boot.img. It has to be.
Click to expand...
Kernels are specific to rom eg: stock based roms, cm roms, etc... Oc kernels are the same
 
You must log in or register to reply here.
Back
Top Bottom