【May-1】【Real Brick】【First time for all these years】

[hunteryezd]

【May-1】【Real Brick】【First time for all these years】

1. First of all this is not my phone. What I barely know about the owner just as you guys know about me, you know I am in China, and I know he is in China too!! All we did here is not just helping him, me or any body else, we are doing what we interested in, an issue broke up, we fix it~~That is why we here!!!!!!!

2. To my knowledge, krat0s123 could be right, "CWM version can't load anything lower than a gingerbread ROM or in our case CM7", so I try to use his advice, CM rom or RoyalGinger could completed, Check the pic!

3. I try to install the driver again in a ''Virgin' xp, and it did show up as before under the +android phone-Android bootloader interface (Chect the pic)

4. yet adb Fastboot devices could find SH11LT706763 Fastboot, and the other commond end up with device not found!! (Is it related to USB debugging?????)

5. I would keep trying any kind of your Suggestion, Thank you very much!











I have been Flashing Roms of every kind, and save more than 20 "Fake Brick" in China, yesterday a dude send me his device, and I try everything, but not working!!
I thought I am pretty smart, I have SDK 1.6, and ADB, Push not work(may be the Root is broken), I was wondering could any one write an application to rewrite the system like Mb525's .SBF???
Also Hboot Factory Reset not working, blocking on Android screen~~~I have my own SDcard for his device, try every step you guys suggest below!!!

State of recovery！！
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

 

[julwo]

If you are getting into recovery should not be brick (till I know)! Di you tray with other card?

 

[Amac1222]

If you are getting into recovery should not be brick (till I know)! Di you tray with other card?

+1 if you can get into recovery you do not have a bricked device.

 

[mark manning]

I have been Flashing Roms of every kind, and save more than 20 "Fake Brick" in China, yesterday a dude send me his device, and I try everything, but not working!!
I thought I am pretty smart, I have SDK 1.6, and ADB, Push not work(may be the Root is broken), I was wondering could any one write an application to rewrite the system like Mb525's .SBF???

State of recovery！！
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

Ya if you are recovery it is not bricked, assuming he has the engineering spl. First thing i would do is use the pd15img.zip, if for whatever reason it isnt working 1. make sure it isnt named .zip.zip or 2. make sure you have the part7backup file on the root of your sd card. There is no reason that wont work. I do believe if he has the eng spl there is still other options if you cant get that to work, keep searching and you will find your answers

 

[faux123]

I have been Flashing Roms of every kind, and save more than 20 "Fake Brick" in China, yesterday a dude send me his device, and I try everything, but not working!!
I thought I am pretty smart, I have SDK 1.6, and ADB, Push not work(may be the Root is broken), I was wondering could any one write an application to rewrite the system like Mb525's .SBF???

State of recovery！！
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

This cache error issues have been showing up more and more lately. So far the only solution I saw to over come this is with Eng boot loader and load recovery 2.5.1.2 via fastboot then wipe cache using 2.5.1.2 to get rid of those recovery errors. Once the errors have been cleared, proceed as normal. There might be an unusual bug with 3.x.x.x recovery.

Sent from my HTC Glacier using XDA App

 

[Hinouchi]

Does people understand what's "brick" anymore? ..

 

[camalus]

No. People assume that when they have issues flashing or don't know how to fix something their phone is "bricked".

Sent from my HTC Glacier using XDA App

 

[erickdj]

This cache error issues have been showing up more and more lately. So far the only solution I saw to over come this is with Eng boot loader and load recovery 2.5.1.2 via fastboot then wipe cache using 2.5.1.2 to get rid of those recovery errors. Once the errors have been cleared, proceed as normal. There might be an unusual bug with 3.x.x.x recovery.

Sent from my HTC Glacier using XDA App

That's exactly what I thought when it happened to me a couple weeks ago. Unfortunately, I didn't have the eng bootloader installed at the time, so it was a total "brick". My guess was it had to do precisely with the newer clockwork recovery, but so far it hasn't been "proven", even though the evidence points in that direction. So, if the person experiencing those errors has the engineering bootloader there MIGHT be a chance to recover, otherwise it IS a BRICK, doesn't matter if it boots to clockwork, so far there's not one reported case of someone fixing those issues without having the eng bootloader. There was one case reported over at the Q & A forum where someone had this error and sent the phone to HTC for a fix, the fix consisted of a new motherboard, so either HTC didn't want to bother flashing the existing board or the only solution IS to replace the board. From what I could tell, and I'm no expert, somehow the internal file system gets corrupted beyond anything that can be fixed through recovery, adb, or fastboot. Unless the phone has the eng bootloader, but even then I'm not sure if there's 100% proof that it can in fact be fixed with the eng bootloader/fastboot.

 

[faux123]

That's exactly what I thought when it happened to me a couple weeks ago. Unfortunately, I didn't have the eng bootloader installed at the time, so it was a total "brick". My guess was it had to do precisely with the newer clockwork recovery, but so far it hasn't been "proven", even though the evidence points in that direction. So, if the person experiencing those errors has the engineering bootloader there MIGHT be a chance to recover, otherwise it IS a BRICK, doesn't matter if it boots to clockwork, so far there's not one reported case of someone fixing those issues without having the eng bootloader. There was one case reported over at the Q & A forum where someone had this error and sent the phone to HTC for a fix, the fix consisted of a new motherboard, so either HTC didn't want to bother flashing the existing board or the only solution IS to replace the board. From what I could tell, and I'm no expert, somehow the internal file system gets corrupted beyond anything that can be fixed through recovery, adb, or fastboot. Unless the phone has the eng bootloader, but even then I'm not sure if there's 100% proof that it can in fact be fixed with the eng bootloader/fastboot.

Engineering boot can recover from this. It's been shown. As I stated before you need to flash 2.5.1.2 to fix the cache errors then proceed with normal flashing procedures.

Sent from my HTC Glacier using XDA App

 

[TeeJay3800]

This cache error issues have been showing up more and more lately. So far the only solution I saw to over come this is with Eng boot loader and load recovery 2.5.1.2 via fastboot then wipe cache using 2.5.1.2 to get rid of those recovery errors. Once the errors have been cleared, proceed as normal. There might be an unusual bug with 3.x.x.x recovery.

I've been suspecting that more and more every time I see one of these issues. What's the solution? Either only use CWM 2.5.x.x (not practical) or we somehow spread the word to everyone that is rooted that you must have the engineering bootloader, or else getting out of this situation is [almost] impossible. Makes me wonder when I'll be the one to get the recovery cache errors.

 

[jdkoren]

I've been suspecting that more and more every time I see one of these issues. What's the solution? Either only use CWM 2.5.x.x (not practical) or we somehow spread the word to everyone that is rooted that you must have the engineering bootloader, or else getting out of this situation is [almost] impossible. Makes me wonder when I'll be the one to get the recovery cache errors.

From what I've heard, it happens when someone with clockworkmod recovery 3.x tries to use PD15IMG.zip to revert to stock. If that's true, then obviously don't do that (in fact, if I were to ever use PD15IMG, I'd probably flash a stock recovery image using fastboot).

Since we know this sort of thing can happen and that you can save your phone using fastboot, that's reason enough in my mind to have the engineering bootloader. Better safe than sorry.

 

[erickdj]

From what I've heard, it happens when someone with clockworkmod recovery 3.x tries to use PD15IMG.zip to revert to stock. If that's true, then obviously don't do that (in fact, if I were to ever use PD15IMG, I'd probably flash a stock recovery image using fastboot).

Since we know this sort of thing can happen and that you can save your phone using fastboot, that's reason enough in my mind to have the engineering bootloader. Better safe than sorry.

That's not how it happened with my phone, I was simply flashing RoyalGinger in clockwork. Also, I have used the PD15IMG file while the newest clockwork was installed and didn't have that issue. Not saying it won't happen while using that image, but it's not guaranteed that it will simply because of that. Every time the issue comes up, the newest clockwork seems to be the common denominator.

 

[xSunny]

I had that done to me before .. I fixed it by putting in another SD card.. Going to clockwork flashing a older clockwork.. Going into clockwork rebooting then reinstalling clockwork 3.x.x.x putting back the other sd card putting the rom and reflashing..

 

[TeeJay3800]

From what I've heard, it happens when someone with clockworkmod recovery 3.x tries to use PD15IMG.zip to revert to stock. If that's true, then obviously don't do that (in fact, if I were to ever use PD15IMG, I'd probably flash a stock recovery image using fastboot).

Since we know this sort of thing can happen and that you can save your phone using fastboot, that's reason enough in my mind to have the engineering bootloader. Better safe than sorry.

Definitely have the eng SPL, but trying to revert to stock isn't the only cause. It's been happening somewhat randomly, apparently out of the blue.

 

[darinmc]

Also have only seen this issue come up with gfree root. Not saying its a cause, just a possible common denominator.

 

[mark manning]

From what I've heard, it happens when someone with clockworkmod recovery 3.x tries to use PD15IMG.zip to revert to stock. If that's true, then obviously don't do that (in fact, if I were to ever use PD15IMG, I'd probably flash a stock recovery image using fastboot).

Since we know this sort of thing can happen and that you can save your phone using fastboot, that's reason enough in my mind to have the engineering bootloader. Better safe than sorry.

From what i have read the PD15IMG has nothing to do with it whatsoever

 

[cmdmilitia13]

I had that issue once with my 1st mytouch 4g & never recovered,had the eng bootloader & all,this is how it happened(clearly my fault)-- I was running ice glacier,flashed cwr 3.0.0.5(this was before cwr 3.0.0.6 came out)booted into recovery,made a nandroid,did a full wipe,flashed cm7 rc2,flashed GAPPS,booted phone,everythin went smooth,15 min later got all force closes out of nowhere had to battery pull,went to recovery wiped both caches,fixed permissions,rebooted & got stuck in cyanagenmod skateboard animation(bootloop) battery pulled,went to recovery,tried my nandroid bckup & bam the cnt mount cache & data error & never recovered,pd15file & part7 didnt wrk,tried fastboot but any file I pushed it didnt accept i just gave up.... Sorry for the long post..

Permrooted S=off-MyTouch 4g-White
Eng-0.85.2007
Clockwork Recovery-3.0.2.4
Rom-RoyalGinger v1.4.1(Gingerbread baked just right : } )

 

[TeeJay3800]

I had that issue once with my 1st mytouch 4g & never recovered,had the eng bootloader & all,this is how it happened(clearly my fault)-- I was running ice glacier,flashed cwr 3.0.0.5(this was before cwr 3.0.0.6 came out)booted into recovery,made a nandroid,did a full wipe,flashed cm7 rc2,flashed GAPPS,booted phone,everythin went smooth,15 min later got all force closes out of nowhere had to battery pull,went to recovery wiped both caches,fixed permissions,rebooted & got stuck in cyanagenmod skateboard animation(bootloop) battery pulled,went to recovery,tried my nandroid bckup & bam the cnt mount cache & data error & never recovered,pd15file & part7 didnt wrk,tried fastboot but any file I pushed it didnt accept i just gave up.... Sorry for the long post..

What do you mean "didn't accept"? The thinking is that using fastboot to flash a new recovery is the way to fix the phone, if that didn't work, then you're totally done.

 

[thederekjay]

This same thing happend to my girfriends phone last night.. no matter what i tried wasnt working. then i placed both the backup .bin from when i rooted the phone and the PD15IMG.zip on the root of the sd-card and boot into bootloader, and now all is well again! after i flashed both those, ENG bootloader and S-OFF is still present so i dont know if this helps but it is possible to recover from this!

 

[theinitial21]

just use the PD15IMG file and restore it to stock and redo everything all over again. yay