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

Root Soft brick! ...getting harder

surphace

Lurker
Dec 3, 2011
5
0
Hey I've Bricked the incredible 2 in 2 days!! Rooted a couple days ago using the sticky here. Loaded a few roms, working great. then i tried to load a couple bliss sense 3.5 rom's supposedly for inc2 neither worked one bootlooped the load screen from a previous rom. recovered ok and loaded MIUI from rom manager. played with it for about ten minuts right as im getting really excited (very nice rom, something i could live with) about three force closes pop up in a row including i belive the rom. reboot stuck on splash screen. in cwm recovery E: can't mount /cache/recovery etc... definite noob have been trying various things (undoubtedly making things worse). Seems like internal memory partitions are faulty but cant get adb to read the phone. tried ruu but says battery is below 30% (green light on when phone is off and unplugged) no recoverys work no installation zips work. i cant find any information on odin (what it does how to use it where to find the appropriate files. if anyone has any ideas id really appreciate it. i will be tirelessly researching and slowly making my phone worse untill something different happens. preciate it
 
Ouch.:eek:

Sounds like you know more than I do about getting things up and running. I was stuck on a splash screen after a bad flash once. Battery pull after battery pull. Just kept trying to load into HBOOT and failing. Finally got into HBOOT and kept failing to execute anything in it. Battery pull after battery pull, then finally was able to do a factory reset from there, finally able to reboot into recovery and wiped again before reflashing a good zip.
Whew, that was the closest I ever had to the point of paperweight.

Have you looked over at the IRC yet? XDA?

Best of luck to you!
 
  • Like
Reactions: surphace
Upvote 0
ok so now ive put an ruu zip on the reformatted sd card loads asks if i want to up date push yes says in progress do not power off device and seems stuck been about a half hour maybe i need to find a different zip this is the most ive gotten it to do in a while. This phone is making me sad.
 
Upvote 0
Just to update im dumb and flashed a rom for an incredible. Im not sure if i can rebuild the internal memory partitions or if that would even work to flash the ruu. I'm pretty much stuck and maybe stuck with a brick. If anyone has any ideas id appreciate them.

Yea bro that's really bad:( sorry to hear that, you gotta be very careful about what you flash, ESP a ROM..
If you can boot into bootloader/recovery.. then you are not bricked and it's VERY easy to get back to where you need to be.
turn off the phone and see if you can boot into recovery or bootloader.. if you can you are fine and just load up a new ROM, or run the RUU as a PG32IMG.zip in bootloader.
 
Upvote 0
Yeah i had recovery but The flash memory partition blocks were all gone. The recover files had no location to flash to recovery failed new rom installation failed ruu couldent ghet past the bootloader same with fastboot oem reboot couldent reformat partitions that didnt exist. The only thing i could see to do would be reformat the entire flash memory of the phone and reformatt all blocks. But thats a little out of my scope. I got a new phone for 35 bucks. Im happy and hopefully this thread will caution others to double check. Although in my extensive searching of all these forums it seems im the only dummy. Or at least the only one to tell everyone about it. Anyways thatnks everyone id still like to hear if anyone has ideas on how the problem would be fixed.
 
Upvote 0
I feel you same boat. I try pushing through adb fastboot, adb shell, in recovery and nothing..how did you " reformat the entire flash memory of the phone and reformatt all blocks" can you explain it to me please Thank YOU and I'm still looking if I have a answer I will comeback and post it with the solution.

S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0622
eMMC-boot
Apr 1 2011.18:34:39

E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
 
Upvote 0
you could have a failed emmc. if you have adb/fastboot working,you can check the emmc with this:


-flash a custom recovery if stock
-power on to hboot
-boot to recovery (select recovery from hboot menu)
-open cmd window,plug in phone
-check for conectivity:
adb devices (should return serial mumber)

-run the following:
adb shell (should change prompt to a #)

dmesg | grep mmc0

it should spit out some stuff.

if emmc is ok,you should see something like:
Code:
c:\miniadb_inc2>[COLOR="Red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx    recovery


c:\miniadb_inc2>[COLOR="red"]adb shell[/COLOR]
/ # [COLOR="red"]dmesg | grep mmc0[/COLOR]
dmesg | grep mmc0
[    8.258270] mmc0: No card detect facilities available
[    8.258941] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 8
[    8.259094] mmc0: Platform slot type: MMC
[    8.259307] mmc0: 4 bit data mode disabled
[    8.259460] mmc0: 8 bit data mode enabled
[    8.259582] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
[    8.259826] mmc0: Slot eject status = 0
[    8.259948] mmc0: Power save feature enable = 1
[    8.260192] mmc0: DM non-cached buffer at ff011000, dma_addr 0x18feb000
[    8.260345] mmc0: DM cmd busaddr 0x18feb000, cmdptr busaddr 0x18feb300
[    8.421417] mmc0: new high speed MMC card at address 0001
[    8.422576] mmcblk0: mmc0:0001 SEM04G 2.17 GiB
/ #

if your emmc is bad,youll see something like:

Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed


there is maybe hopes to fix bad blocks(im not sure how),but a failed emmc means its not repairable without new hardware. :(
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones