Database Users

DREA100 and the infamous Triangle of death?

Ok.. So a friend of mine suddenly got a triangle with the exclamation mark picture on his phone. That's all it boots up to. So, he took it to T-mobile, they told him it's FUBAR, and sold him a new phone.
The fact that the thing boots to a recovery mode tells me that there's SOME way to un-FUBAR this phone. My friend is too technologically inadiquate to attempt to do any modifying, so I'm going to assume he was at whatever firmware level would hve been blasted out to T-mobile as of last Friday 01/15/2010.
If I boot the phone normally, it gives me the TriAngle. I pop open the keyboard and hit alt-L and the I get the Android System Recovery menu. at the bottom I get "E:CAn't open /cache/recovery/command"
I've spent all day bouncing around this forum, and many like it, downloaded all sorts of G1 fimwares trying to go back to RC29, RC28, 30, 33.. gah! The latest one I'm trying to update to is "signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip" Which i rename to update.zip . I hit alt-L, select 'update from SD card' It goes through:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update package....
Installation aborted.
That's it... no more log than that.
I've done the Alt-W, and Alt-S.. wiped cache partition. I think playing around with the recent firmwares might be fun, but I'd like to get this bad boy reset back to factory defaults. I've read the forums here on how to do that.. but all of the procedures fail.
I can get Windows 7 to recognize the phone, but I cannot access the sd card while it is in the phone. I've been transfering data to it by taking the sdcard out, and putting it into a known good SD card reader. I've formatted the sdcard to FAT16, and FAT32 quick and not quick.
Seriously.. why is this so complicated? Now I need some serious digging assistance. Is there an interface that will allow me to directly talk to this phone via the USB cable? How can I force an firmware onto it? Clearly something is functional, or I would get no I/O. How can I get this silly thing back to where it was? I know this thread seems like a redundant one, but as far as I can tell, its not. The typical procedures posted here don't seem to work, but I'll be happy to run through any steps y'all suggest. I'll resign that it's been bricked if that's really whats happened.. but I'm not ready to throw this unit away yet.
Ask questions.. let me answer them. I know this team can get this phone working again.
Thanks y'all.
--Rob aka The Austin Slacker.

Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1

Roadmasta01 said:
Have you tried the RC29 DREAIMG.nbh file?
http://forum.xda-developers.com/showpost.php?p=4593084&postcount=1
Click to expand...
Click to collapse
bingo !
sounds like your friend tried to flash something he shouldn't have. or messed around with stuff he shouldn't.
as far as taking it to the store, and accepting their suggestion to "GIVE US YOUR MONEY!" that was a mistake.
the phone is likely fine, and maybe you'll buy it from him for cheap, then fix, resell/use.
good luck, should be easy.

The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him

Ok.. one more day (well ok.. couple hours) of fiddling with this thing, and i'm begining to wonder if Microsoft was involved. I'm not able to get this poor G1 to do anything new. I tried using a different SD card, hoping perhaps the one I got with it was bad... no dice. camera + power doesn't do anything useful.
I can connect it to the PC.. but i can't see the data card that way. adb devices reads no output, so its not correctly attaching to the PC (tried Windows 7 32bit, and Windows XP 64bit).. There's gotta be a good way to force a known good image onto this silly thing.
Is it probable that the internal memory has gotten corrupt somehow? I know someone out there's got the golden suggestion, please do tell if you do. I'd really like to use this phone.
--Rob

If you can get into fast boot (the tri color screen) there are ways to flash it... try getting into your tri color, then plugging in the USB cable and see if it switches from Serial 0 to USB at the bottom, if so you are golden to flash using the fast boot method.
There are guides around on how exactly to do that, as well a couple places that you can download the official RUU that will do all the hard work for you!

gah.. nothing doing. I can hit Back and Home, and end up with the tri-color screen for about 1/5th of a second, then a gray screen saying:
This operation will delete all your personal data, and reset all settings to manufacturer default. Press Send to restore manufacturer default, or press other keys to cancel.
At this point, the unit is dead. I can remove the battery, and continue on my little quest.. but hitting *any* key at all (including the Send key) will not produce any sort of output. I've tried pressing Send one time, then setting the phone down for a full hour (watched a netflix show) nothing. I can't power it off either w/o removing the battery.
I would throw in the towel.. but from all the research i've been doing, it seems as if this one is behaving in a manner in which other forum users havne't posted. Maybe by continuing to try options and post results, a positive outcome will come out, and someone else who has a G1 behaving this way will have an easier time.
... or y'all can tell me that its toast and to bugger off.. ha ha.. either way.. I continue to google. If you can think of anything, please toss it out.
OH!.. tried an RUU.. found one called. RhodiumSPLRelocker Looks promising.. but can't see the device when attached to the PC... yeah.. guess the phone has to have a functioning OS before that will happen...

You would want a Dream RUU... I looked around a bit and couldn't find one. Maybe someone has a quick link?
Double check that your SD card is formatted FAT32 and see if you can get ADB to see it when on that greay screen.

I've formatted the SD card in FAT32 multiple times.. I even questioned if my Windows 7 32bit would do it, and formatted it on a laptop running XP 64bit. adb doesn't seem to see it ever.
I don't get why I can't get it into fast boot. I've been looking on ebay for dream G1s with broken screens.. heh.. I guess i'm preparing for the worst. really sad, becasue this G1 was actually pretty well taken care of. My friend didn't do anything he shouldn't. HE woke up one morning and it was like this. He lives out in the country.. so he gets pretty spotty signal. I'm wondering if T-Mobile didn't push out an update, and it got interrupted by signal loss.
By the by... I've been doing all this work w/o a SIM card. Does that matter?

austinslacker said:
(based on cell phone standards, I'm assuming "send" is the green "call" button.
Click to expand...
Click to collapse
its not the green send button -- its the red end button
see below extracted from http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
Load the DreaIMG.nbh File
1. Download the Original DreaIMG.nbh file:
http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card, NOT in any folder. (If you did Section I the phone is off still, take out the memory card, put it in the MicroSD adapter and plug it into your computer to transfer the file over, since your G1 won’t turn on right now if you did Section I above. Otherwise if you did not need to do Section I above, then you can just put it on the SD card normally using the usb cable and the phone).
3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29

austinslacker said:
The "press camera and power to get to bootloader" procedure. I've tried holding the Camera while pressing power over and over and all I get is the triangle. However if I press power and the "back" button (swooping arrow to the left), I'll get the bars screen, and a Gray screen telling me to press send to restore.... Which is all good, but there's no progress or any thing to indicate that i've done something by pressing the send button.(based on cell phone standards, I'm assuming "send" is the green "call" button.
Is this normal?
No yeah.. he gave me the G1.. its mine. I just need to fix the little bugger.. .. well.. then laugh at him
Click to expand...
Click to collapse
You mention that you can access fastboot by pressing the back button while turning it on, isn't that how the hero gets into fastboot? maybe your friend tried flashing a rom that was meant for the hero. if you have access to fastboot you should be able to flash a new image from there, just place the image file in the root of your card and follow the fastboot instructions

Also if fastboot isn't doing it for you have you tried adb? if you don't know what that is look it up I've seen a couple guides on how to do it and they are really detailed.

Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?

Triangle of Death
I'm from Brazil, I can't take it to t-mobile to fix...
when i tried to root my G1 did the downgrade perfectly, the screen was just as it was suposed to be.
But in the recovery mode boot, appeared this triangle with an exclamation...
what do i do now???? help plz!

deftoneage12 said:
Im having the same problem, Im stuck in the recover triangle of death. Ive done the alt+w and reboot, the RC29 DREAIMG.nbh , the update.zip, camera+power, I cant get the gray screen to pop. Nothing, its brickkkkeeeddddd, FUBAR. There has got to be someway I can reload this G1. I wasnt trying to root it or anything. I was bowling and then it triangled on me. Anyone have any ideas at all on how to fix it?
Click to expand...
Click to collapse
Any one have any ideas? hell ill pay someone to fix it for me

The only idea I have is make'ing an goldcard so your sure your phone accepts the update (dreaimg)... other than that...
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk

Any chance the home button is stuck? I'm not 100%, but I think if you were to hold home, camera and power, the recovery would come out on top.

Home button is not stuck, and cant seem to figure out the CID of my SD card since my phone is unaccessable.

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

Flashed wrong ROM, u8800

Quickly, I made a mistake flashing a ROM for u8800+ while I have u8800. I did not understand that "%2B" means "+" in ASCII or somewhere. Im in bootloop, changing boot.img and recovery.img and the rest of the files do not help, tryed to format microSD card, flashing Froyo onto it, nothing works, any other suggestion, maybe with the help of linux?
Thank you for your minute reading this!

Why don't you try to flash the official 2.3 for U8800?

Hello and good morning!
I already tryed to flashed the official 2.3 (U8800 V100R001C00B522G001%28通用版%29%28Gingerbread%29".
I copyed "dload" on microSD, pushed VOL+ and VOL- and the power button, but the phone goes to pink screen instead of the built-in updater.
I will try to take it back to the store, but I doubt, they will believe my "innocence".

Hello and thank you for your time.
I flashed the STEP ONE U8800+ latest ROM in my normal U8800.... :S
Now, even if I have a "dload" with the normal UPDATE.APP, it will just go in the pink screen....Changing the files doesn't do anything..even if I alter the recovery.img and boot.img and stuff, it won't go in Recovery(or CWM) and just keep bootlooping...
Please guys, is there anything I can do to return my phone to normal?
(My problem seems to be exactly the same with R4DK0)

R4DK0 said:
Hello and good morning!
I already tryed to flashed the official 2.3 (U8800 V100R001C00B522G001%28通用版%29%28Gingerbread%29".
I copyed "dload" on microSD, pushed VOL+ and VOL- and the power button, but the phone goes to pink screen instead of the built-in updater.
I will try to take it back to the store, but I doubt, they will believe my "innocence".
Click to expand...
Click to collapse
After power off device, connect it first with usb cable and then push VOL+ and VOL- and the power buttons

For me it didn't work :/
It just keeps returning in the Pink Screen, like it did with the battery :/

I think I will solve my problem by using my warranty...For now they accepted my phone, they said I will get it back approx. in two weeks. Until then, I dont have a phone
edit:
@nasos95
I am kinda glad, I am not the only one...and yes, no matter what you do, the only thing that "works" is the pink screen and the bootloop. I have all my older files backup up and replacing it, did not help.

I am very unlucky then....I bought my phone ONLY 2 months ago, but from the shop I bought (as it is second-hand) I suppose it doesn't come with a warranty...I am left without a mobile device... TT.TT
Thank you very much Huawei for the detailed file information u give, and the "warnings" that you SHOULD have put, but are nowhere to be found....
Congratulations...

Ideos x5 brick

greetings...
I have a problem.
i flashed a rom that i dont remamber its name and my ideos x5 stoped working.
i turn the phone on, it apires logo and than it turns of.
i already tryed a lot of stock roms. 2.2.2 and 2.3.5 but when i run pink screen, it doesn't start installing... stays pink... even with out the battery.
it doesn't start recovery.
i tried to put the phone in charge but it doesn't apire the batery charging... does the logo loop.
i dont know what to do...
please help me.

Try to take off battery, and when phone is off connect the usb cable while you keep pushing the vol-/+ buttons. If doesn't start, then push(and keep pushing for a while) the power button, without to release the vol buttons.
Also make sure that you have put the update file in correct position on sd card.
You must make a folder with the name "dload" on the root directory of sd card and inside the update.app file.

i did every thing but it doesn't start installing the rom... it stays pink with and without the batery.
i toght that was the rom, but i downloaded all kind of stock roms but nun worked...
i dont know what to do more...
is there any way to access to the phone memory were are the rom files installed??

This is most probably means that your sd card doesn't detected, so loads the pink srceen mode instead of the update mode.
If you have pink screen unlocked(official froyo rom or 2.3 older version than B518 roms), then you can access some of the partitions from a linux pc. Then you can access internal storage and put the dload folder there.

im not realy familiarised with linux but i tried to atatch the phone on ubuntu with pink screen and it didnt apear nothing.

i think the rom that i used was 1 of this 2... i dont remember with one was. but i think it was the 1st.
U8800proB928GaDaNaV5_2 or 404029_4.0_BasebandCWM

Yep, that would do it. If you have a plain u8800 x5, those roms would have killed your phone good and proper. Most of those u8800 pro ICS roms flash bootloaders, amss and all kinds of things, not just system and boot.img. Unless you can get through the pinkscreen with a fresh SD card with the official B5XX update.app in a dload folder on it, you are looking at having to buy a new phone. Sorry man.
Try the official updates here: http://www.mediafire.com/#9adk7amyag95k
Start with b526 for gingerbread or b138 for froyo.

yessssss...
Thanks for every thing. specialy for the rom and specialy for the detail of the sd cards...
i tried with 3 diferent sd's and only one did the update... now the phone is funcional...
Thanks alot. i was desperating

Glad it got worked out man, nothing worse than seeing a phone stick and reboot.
Sent from my U8800 using xda premium

[Q] Defy bricked. Wont turn on, only white led on pc

I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?

Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.

htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing

Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...

Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help

Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"

Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk

thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.

htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...

Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?