yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] david_rowe:
someone correct me if im wrong, but if youre on official 2.2, then in order for the update.zip file to work you have to odin back to 2.1 [the files are in the posted link]

http://xdaforums.com/showthread.php?t=734475

lemme know if it works out for ya :)
[Vibrant Q&A, Help & Troubleshooting] alexef2000:
That was obvious I put the file on the internal sd (root) but still nothing.

When I reinstall the packages the phone boot up and ... when I going back into recovery mode it is still the same screen with blue letters and not green like in CWM.
[Vibrant Q&A, Help & Troubleshooting] alexef2000:
I am in the stock rom 2.1 . Not 2.2. Odin was a big help.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
EDIT, meant to edit this post but o well, see my next post... re-read what you stated and it sounds like you rooted fine, you just did not flash CWR
[Vibrant Q&A, Help & Troubleshooting] s15274n:
WAIT, so you DID root then... you just haven't flashed CWR

Go download rom manager and select to flash cwr, then reboot into recovery, reinstall packages twice.
[Vibrant Q&A, Help & Troubleshooting] alexef2000:
THANK YOU !!! It Worked perfectly !!
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Nice, now go rom manager (or cwr) and make a backup! Always nice to have a fresh stock jfd rooted to go back to.

What rom were you going to flash? Check out heathens stock and trigger, the latter has voodoo enabled fyi.
[Defy General] wrexe:
Hello all,

I am new here, My name is Lewis, and you all seem like a very clever bunch of people. So i was wondering if you could give me some help with my Defy.

So here we go:

I bought my Defy last week after my Nokia died, it is second hand, and was locked and branded to T-Mobile (UK). I got it unlocked a few days ago, and it unlocked straight the way with the 1st code. So i assumed all was well. After trying to send a message, i realized that it was stuck in 'Emergency Call Only'. After a bit of searching around the interweb, i found that i had to check my APN Settings. The sim card i have is with Tesco Mobile, so i found out the APN settings and all seemed fine. I have tried hard reseting the phone, but still no luck.

It is all standard, so do i have to do any flashing to get it to have signal? Thank you for your help in Advance.

Motorola Defy

Locked to T-mobile

Unlocked to work with Tesco Mobile sim (O2 masts)

4GB memory card

All default.

Edit: When I 1st put the Sim Card in, it has signal for a few seconds before reverting to emergency calls only.

wrexe
[myTouch 4G Android Development] 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
[myTouch 4G Android Development] julwo:
If you are getting into recovery should not be brick (till I know)! Di you tray with other card?
[myTouch 4G Android Development] Amac1222:
+1 if you can get into recovery you do not have a bricked device.
[myTouch 4G Android Development] mark manning:
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
[myTouch 4G Android Development] faux123:
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.
[myTouch 4G Android Development] Hinouchi:
Does people understand what's "brick" anymore? .. :confused:
[myTouch 4G Android Development] camalus:
No. People assume that when they have issues flashing or don't know how to fix something their phone is "bricked".
[myTouch 4G Android Development] erickdj:
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.
[myTouch 4G Android Development] faux123:
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.
[myTouch 4G Android Development] TeeJay3800:
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. :(
[myTouch 4G Android Development] jdkoren:
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.
[myTouch 4G Android Development] erickdj:
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.
[myTouch 4G Android Development] 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..
[myTouch 4G Android Development] TeeJay3800:
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.
[myTouch 4G Android Development] darinmc:
Also have only seen this issue come up with gfree root. Not saying its a cause, just a possible common denominator.
[myTouch 4G Android Development] mark manning:
From what i have read the PD15IMG has nothing to do with it whatsoever
[myTouch 4G Android Development] 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 : } )
[myTouch 4G Android Development] TeeJay3800:
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.
[myTouch 4G Android Development] 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:D so i dont know if this helps but it is possible to recover from this!
[myTouch 4G Android Development] theinitial21:
just use the PD15IMG file and restore it to stock and redo everything all over again. yay
[myTouch 4G Android Development] jdkoren:
Well, ruling out one possible cause is at least a step in the right direction.
[myTouch 4G Android Development] cmdmilitia13:
I tried pushin the recovery image,got an error,anythin I tried with fastboot I just kept gettin errors,im good now got another mytouch 4g....

Permrooted S=off-MyTouch 4g-White

Root Method-gfree

Eng-0.85.2007

CWR-3.0.2.4

Rom-RoyalGinger v1.4.1(Gingerbread baked just right : } )

Afraid of the evil cnt mount cache & data error!
[myTouch 4G Android Development] hunteryezd:
No Way can go back to 2.5.1.2, Caz' Adb not work, Hboot flash PD15IMG.zip not

work, it seems that the system become Unreadable and Unwritable????
[myTouch 4G Android Development] mark manning:
Make sure the part7backup file is on the root of the SD before you give up on the pd15img. If that and fastboot are not working then the phone is actually bricked. All though I do feel you are missing something

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] hunteryezd:
Where could I find "part7backup file"

Could I find the file from mine, the Brick one is from a dude?????
[myTouch 4G Android Development] hunteryezd:
I had Changed from my own SDcard, not working

I tried to use my own sdcard, and tried older Clockwork, also try Restore not working ~~
[myTouch 4G Android Development] hunteryezd:
This did help, Tks

This info is very important, tks
[myTouch 4G Android Development] hunteryezd:
Tks, I would try my phone's SDcard again!!
[myTouch 4G Android Development] mark manning:
Pm me your email and ill send u mine. I'm not at home so can't upload it to here

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] mark manning:
Actually found a way to upload it here you go

https://rapidshare.com/files/459865351/part7backup-1297066910.bin

Put this on the root of your SD and try again

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] Nicgraner:
Hmmm....not really first time to the OP but I have a different situation here. The phone just died right so I figured oops charger came unplugged right? Nope. Left it in for another 4 hours tried to turn on got splash screen for bout 5 seconds then black screen :eek: so I thought time for pd151img.zip. flashed it through hboot and then tried booting. Splash screen wouldn't stay up for more than half a sec so tried flashing new rom through recovery (3.0.2.4) and phone randomly powers off. At this point I said screw it ill try pd151img one last time. So I did. No dice. Started it flashing again and pulled battery to corrupt hboot,recovery,and radio. Sent to T-Mobile and got new one within 2 days :) I know my method for hiding root was rather crude but it worked. Not sure what caused the brick as this was completely random. Wish I could've pulled a logcat :(
[myTouch 4G Android Development] hunteryezd:
Thank you very much for your support, I would try right now and report~~

Report: odds, Fail-up again!!

Tks all the same!!
[myTouch 4G Android Development] kimbernator:
Hey, what exactly IS the engineering bootloader and why would I want it?
[myTouch 4G Android Development] mark manning:
Ewww i think its done.

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] mark manning:
It gives a you access to code from the bootloader, it is sometimes your last defense to fixing a phone. So YES FLASH IT!!! Just be exact in doing it. Messing up bricks the phone. Don't let that scare you tho just be careful

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] mark manning:
Just saw the picture, the phone does not have the engineering spl. So the phone is officially bricked!!!

Case closed.

Sent from my Royal Glacier powered XDA app
[myTouch 4G Android Development] hunteryezd:
Brilliant conclusion~！！Tks dude~
[myTouch 4G Android Development] tilt4life2:
I rooted my phone using this method: http://wiki.cyanogenmod.com/index.ph...l_Update_Guide

I did everything except flashing a radio. I am currently using 3.0.0.6.

I want to do a nandroid backup of a previous RoyalGlacier 1.3 through Recovery. Should I be worried that something like this could happen? I remember seeing an E: error on the phone when I installed CM 7 Final to test, but it loaded up okay.

Any chance my nandroid and do this to my phone if it is a potential problem with the new Recovery?

Also, how do I check to see which bootloader I have? Through Recovery?
[myTouch 4G Android Development] hunteryezd:
1. 3.0.0.6 is OK, and could be reversed back to 2.5.1.2, but it is not necessary

2. RoyalGlacier 1.3 is ok, and even CM 7 or RoyalGinger is fine, your E: error is also common, not the one I am posting on this thread, what you should keep in mind is don't Reversed back by Hboot using PD15IMG.zip

When you could not get in the system!!

3. Press The Power bu. + Volume down, then you would see Whether you are ENG or not!!!
[myTouch 4G Android Development] mark manning:
1027654321
[myTouch 4G Android Development] cmdmilitia13:
Ur eng bootloader should read 0.85.2007 if it doesnt then u dnt have it...

Permrooted S=off-MyTouch 4g-White

Root Method-gfree

Eng-0.85.2007

CWR-3.0.2.4

Rom-RoyalGinger v1.4.1(Gingerbread baked just right : } )

Afraid of the evil cnt mount cache & data error!
[myTouch 4G Android Development] krat0s123:
Wow! Too many unnecessary talks/discussions on this thread. Did the OP ever got helped or did he revive his MT4G? Anyway, the adb issue is only a matter of installing the right driver. The phone isn't bricked. Just go to device manager on your computer (right click my computer, properties), look for android or ADB, right click and update driver, select browse my computer for driver software, click Let me pick from a list and then you should be presented with one choice (Android or ADB or android ADB.. I forgot sorry), click whatevr of the three it is, let it install then go to your command prompt and type adb devices. You should then see your device and able to send adb commands to your phone. And those who said that the phone is bricked, come on! If it can go to recovery, it ain't bricked! Also, you can only load a cm7 based rom on your device, because of the recovery version on your mt4g. Hope that helps!
[myTouch 4G Android Development] xdviper:
So if he has access to ADB, Can't just boot into recovery or fastboot and flash a new or stock recovery?
[myTouch 4G Android Development] faux123:
The problem is lack of Engineering Boot Loader (EBL)...

He can Boot into recovery, but he CAN'T use it because Recovery ITSELF is broken... You need EBL to have ADB enabled in HBoot so he can fix his recovery, without EBL, you don't have ADB access in HBoot which means he has NO WAY of fixing his broken recovery... :(
[myTouch 4G Android Development] krat0s123:
Do you mean he can?? Anyway, if he has access to ADB, yes he can just flash a new recovery (stay away from stock recovery for now, to avoid bricking the phone). This has been an issue in the past and I just can't believe how no one here has brought up the answer! ADB gets broken on windows and it's been a known fact. And like I said, if the phone can go to CWM recovery, it's not and will never brick! The OP's issue is just the ADB driver installed on his computer.. All he has to do is follow the instructions I typed.. It may not be as accurate, as I have a few ADB drivers on my computer (XOOM, LG, HTC etc).. I know the XOOM ADB driver interface is called differently for example.. But he should get the idea of what I was saying.. If he has done ADB on other phones in the past, like he said on his OP, it means he has the right driver for it on his computer.. All he has to do is point the right device driver on the device manager.. The key point would be to right click on anything that says "Android or ADB" on the device manager, left click Update Driver, Browse My Computer for Driver Software and then "Let me pick from a list of device driver on my computer", he should then be presented with Android ADB or something with ADB interface, select that and all should be well..
[myTouch 4G Android Development] dcwiker05:
It's not that easy, as far as I know I am one of the very few to recover from this issue (http://xdaforums.com/showthread.php?t=1043459 my thread and my solution faux mentioned) and adb was basically useless, and 110% useless if I didn't have 0.85 bootloader. 0.86 is a waste, you can not do anything adb via that bootloader, all your adb has to be done with the phone booted, and with this error the phone most likely will not boot. Basically this error is a warning to all FLASH EBL!!!! I guessed my a$$ off when I fixed this and the only thing that lead me to my fix was a random unrelated issue that was fixed by CWM 2.X.

Also this issue is 100% random crap shoot issue, nothing "causes" this. The way it happened with my phone was just strange. Phone was working great, I was texting and bluetoothing music. Replied to a text went about what I was doing, and when I went to read my reply text my screen wouldn't light. Hard keys did but not the screen. Figured a battery pull would solve the issue but once I did that phone bootlooped, that was when I went to recovery to flash a Nandroid and got that error. Flashed my nandroid and it booted but acted like a fresh ROM install but EVERYTHING FC'd then restarting the phone lead to bootloops.

So moral, I did NOTHING out of the ordinary and CWM's ghost still bit my ass.
[myTouch 4G Android Development] darinmc:
No windows driver can fix the fact that he has the .86 bootloader.
[myTouch 4G Android Development] krat0s123:
Yes, the issue with his phone is the fact that his CWM version can't load anything lower than a gingerbread ROM or in our case CM7. But to simply assume that ADB is shot? I don't know. I know for a fact that windows 7 is just hard to work with when it comes to adb, and a lot of people had the same problem, of which the solution was just to pick the right adb device driver like on the instructions I posted. That's why I was advising the op to try and install the right adb driver first before assuming that his phone is bricked, like what a lot of the useless posts on this thread. I mean no offense to those posts, but saying something like that especially on a phone where CWM is booting is just simply stupid! As it doesn't help the op at all, even give him false info. Lastly, I've worked with a lot of android phones, and never have I encountered such a thing where a phone boots to recovery and not able to run adb at all. Every single time that I'm having a problem sending adb commands to the phone, I simply just install the adb driver or I use a "virgin" windows XP machine. When I say virgin, I meant that a windows XP machine that doesn't have any android USB drivers installed. Then what I do is I just download the USB driver from HTC website, download android sdk or just the adb ecxecutable files and it's dependencies to the XP machine fire up the cmd prompt and send adb commands from there. Anyway, to the OP, if all those I said fails, just restore a backed up CM7 based ROM from CWM and then install the new CWM recoveries from ROM manager and he should be good. I know, I may sound stubborn, but I just can't give up and agree that his adb was shot or that he's SOL when I know that the phone is booting to recovery especially CWM. If the OP was only local, I'd try to help him out.
[myTouch 4G Android Development] darinmc:
You can get adb to recognize the device, the problem seems to be in the restrictions of the .86 bootloader. Keep trying to help the guy, by all means, people are saying the things they are saying because there are other threads that give detailed accounts of the same situation where every action produced errors of one kind or another, adb included.