Related
Okay, I know there is many post about this, but none seem to answer my question or help me. I have a Vibrant and I've been searching this site along with google to help fix my phone.
I brought it off a friend so warranty won't happen since T-Mobile is being asses. My phone is suck on the black screen after it passes the big S logo. It stays black, and I get 4 lights bright on the buttons. I've reflashed my phone with Odin and it has not worked. I think it correctly as well. Com3 was on, ran the stock Vibrant with Pitt and Tar with PDA one. That had only got my phone off the complete brick that my phone had gone through, when It wouldn't even turn on.
I got the brick off and now I'm stuck with this program. I did have a one click root fix and I was trying to mess around with clock work. To help answer some questions. No, I can not boot into recovery mode. Yes I have cleaned and wipe out cache. Yes I can go into Download mode, but its pointless since odin doesn't do much for me. No I can not go into the phone since the black screen is there and no I can not flash a update file for some reason.
Saying that, I would be grateful for some help and before hand I thank anyone who comes across this even if they don't help, just for taking time to read this and maybe referring someone else to help me or even pointing me in the right direction. Thanks and once again PLZZZZZZZ HELPPPPPPPPPPPPPPPP.
No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?
zephiK said:
No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?
Click to expand...
Click to collapse
Okay. One thing I notice when I try to put my phone into the Android system recovery it says this "
-- Movi_check start .. !!
checksum confirmation need _checksum [1301305579]
MBR _Chksum in header :4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MBR Checksum Error
Movinand Checksun Confirmaton Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti - CSC ...
Installing Muti - CSC "
Another thing, I hit reinstall packages and It says "
-- install from sdcard...
finding update package ...
opening update package ...
E: cant open /sdcard/update.zip
(no such file or directory)
installation aborted.
the drivers I use are the samsung Vibrant drivers for windows 7 64. I know it works because the phone before didn't come up when I didn't use the driver. It always failed and when I install it, than it read my phone. When I connect the phone to the computer, the phone does read it and on odin, it says com 3 in yellow. I than Install pitt and install tar.
The tread you sent me too, I actually went through there before. Both of those drivers didn't work but I found one for windows 7 and it started working for my computer. I could tell it works because the computer actually reads the phone and so does odin. Like I use odin right because it goes through the phone and than says pass at the end. so like WTF lol. I'm pretty sure I'm doing it right tho
Another thing. I used odin a few seconds ago, got the phone to run and it went through the green bar and a blue screen now saying reset came up. My phone than went into androids recovery mode but it started to wipe out data. When doing so, the data said wipe fail. It booted up and now back to the start. Black screen, 4 panels on the bottom lit up and nothing to do.
I'm starting to think it has to do with clockwork I did a partition in it and every since than my phone has been doing this blackscreen with 4 lights.
ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work
same thing here, know idea, odin says everything passed but still the black screen and four buttons. i also noticed that the sound and tmo splash screen are not in sync. no idea ???? help would be great!!!!!!!!!!! same errors though. also from the partion feature in clockworkmod.
i assume your on windows i don't keep up if there is a working version for mac. Anyway, make sure your update.zip is just named update DO NOT add .zip yourself or the phone for what ever reason sees .zip.zip. I would also go ahead re download your odiin files just to make sure non of them are corrupted for what ever reason.
files all check out good, i can't gain access to the phones sd, i have flashed this thing with every checked build i could find, all with the same result. the master boot record is not adding up.? still have know idea.
have you tried using this.. http://forum.xda-developers.com/showthread.php?t=740558
this work for me and was able to flash to stock..
somebody please help I'm experiencing the same problem as the OP? can somebody point me in the right direction I've been looking for hours
Instead of making us read the entire thread perhaps you could summarize your specific problem.
My initial impression goes like this.
1. Get into download
2. ODIN back to STOCK 2.1
Run odin in admin mode
Use rage against the cage
After getting back to stock Recovery 2e go ahead reroot and flash away
Sent from my SGH-T959 using XDA App
Don't know if this is still an issue, but here's how I fixed it.
http://forum.androidspin.com/showth...yo-That-does-not-Brick!-Downgrading-Is-Fine-)
Downloaded this file knowing it wouldn't work, Had ODIN flash it and got into this weird recovery screen. Just pulled the battery and then flashed back to stock using ODIN.
Helped me out.
Use 512 .pit and True Stock 2.1 from this post
http://forum.xda-developers.com/showthread.php?t=747335
And quit messing with your phone! lol
This is how i fixed mine too, my phone would go through a seemingly normal start up, but the UI would never load and it would stay on a blank screen.
Flash Eugenes373s froyo that doesnt brick. once it brings you to the recovery screen, pull the battery and once again use odin to flash back to stock. the phone should boot up now.
mnm0071980 said:
ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work
Click to expand...
Click to collapse
Hey i just encountered the same exact problem four days ago except i flash with odin it says pass but im still stuck on a black screen after the s logo my problemwas encountered by tryig flash a kernal. Please tell me that u found a solution
Just downloaded Football's stock rom, thank you btw. I followed all the directions I could find regarding flashing.
Downloaded
Renamed to PD15IMG.zip
Copied to root of SD card
Booted into Hboot... now here is where the problem starts.
Hboot comes up normally at first with the regular options on the screen
after a few seconds a screen comes up that looks like it is looking for the update.
then it gives a messages about
PD15DIAG.zip no image
PD15DIAG.nbh (or some such) no image or wrong image
PD15IMG.zip loading... ...
a blue bar comes up on the upper right of the screen that seems to indicate loading. after about a min or so the bar finishes and it just goes back to the main screen.
It doesn't seem like it has done anything at this point and rebooting just takes it back to the normal version of the phone.
Am I missing a step? I never see an option on screen that says press something to upgrade.
Thanks in advance for any help.
Possibly a corrupted download. Did you check the version? Is it possible you're already on 2.3.4?
Thanks for the reply,
As of now my Software information is as follows:
Android Version - 2.2.1
Baseband Version - 12.28b.60.140eU_26.03.02.26_M
Kernel Version - 2.6.32.21 - g899d047 [email protected] #1
Tue Oct 26 16:10:01 CST 2010
Build Number - 1.17.531.2 CL277036 release-keys
Software Number - 1.17.531.2
Browser Version - WebKit 3.1
I'll give re downloading a try and see if that helps. Just out of curiosity are the messages about PD15DIAG.zip ect not found normal?
I'll post my results again after work today.
ok, just tried to re download the file from the link Football provided and it seems to be broken. I keep getting a file not found error after waiting the 60 seconds.
Would anyone happen to have a mirror link?
The link in this thread works...
http://forum.xda-developers.com/showthread.php?t=1174344&page=1
Thanks to the both of you. It was indeed a corrupted download. The link provided did work this time, even though it was the same as I used before.
Maybe the site was doing a maintenance or some such.
In any case, copied the files over again and it prompted for the upgrade and it seems to be working well.
Thanks again
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
cute_kayani said:
My Motorola Defy goes dead after flashing.
-No Recovery
-No bootlaoder
But when i connect it with RSD, white led turns on and RSD connect it.
I try 3 different ROMs for Flashing but nothing has been changed.
When pressing vol down and power not going into recovery.
When Pressing Vol Up and power not showing black screen with white Text for bootloader.
-After flashing 3 Roms, RSD shows status PASSED and phone Reboots but not turn ON.
-Battery charged with Universal Charger
I installed these roms:
>JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_ USAJORDANRTGB_P026_A007_HWp3_Service1FF.sbf
>JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB 1B8TMGB030.0R_USAJORDANTMGB_P039_A015_M003_HWp3_Se rvice1FF.sbf
>JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTINT_P030_A020_HWp3_Service1FF.sbf
Every time i got staus passed message and cellphone reboots.
but now it is not going in recovery/bootloader or power on.
Completely Dead
When i go this phone it has eclair and than updated to froyo and than i moved to miui.
It comes from T Mobile. when i got, it has T Mobile startup logo and T mobile Apps in it.
Click to expand...
Click to collapse
I think I got the answer for you......
Use below mentioned steps and share the outcome:
1. Download the compressed SBF and extract using any software like 7zip or something - http://www.mediafire.com/?s3uc8cb782w1oue
[Note: Do not use any download manager while downloading.]
2. Use RSD Lite to flash the phone with the SBF file;
3. After flashing let the phone boot up and hopefully it will resolve the issue.
However if the phone is still in boot loops then try entering Stock recovery and wipe data/format and wipe cache also.
Please use the above steps and share the outcome.
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
pranks1989 said:
I recommend DON'T flash that SBF! Why? : Its a chinese and has the potential to fry your LED! And since it is not downgradable and rootable you may get stuck!(See this. From what I have seen in few threads there is a big chance your battery is dead and not charged!!
Click to expand...
Click to collapse
I understand your concern and I appreciate your comment however, I would like to point this out that this firmware is for "India, Indonesia, Malaysia, Philippines, Thailand, Vietnam" and its safe to flash I have flashed it multiple times and its Rootable and even my flash is healthy.
You may visit this link and Control+F "JRDNEM_U3_3.4.3-33-1":
http://and-developers.com/sbf:defy
The chinese firmware which is suspicious of burning flash is "China - JDGC_U6_0.26.0" [Correct me if I'm wrong.]
cute_kayani said:
ok i will download it and try it, but what i think is that, T Mobile is creating problem and i read some where there is only one SBF which work for T Mobile. Dont know for USA or UK. Mine cell is from UK.
Hopefully the link which you send helps me..
But the link you send for sbf is not down gradable. Can it create more problem for me if i install it and same black screen problem appears. And not rootable i think so how would i root it and move to custom rom,
Click to expand...
Click to collapse
cute_kayani said:
okay, if battery is dead why RSD connect it and every time status passed message appears.
PLz tell me what to do
Click to expand...
Click to collapse
You may use this firmware or any different firmware from this link : http://and-developers.com/sbf:defy
The ROM which I have given you link is Rootable however not down-gradable.
You may refer this extract from All-in-one-Guide-for-Defy
SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.6, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
ATTENTION: This CG 7 Version is NOT rooteable. You wont be able to flash a lower version ROM nor Root to use CWM.
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
Official SBFs
Here is a list of all the OFFICIAL SBFs, meaning they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
Ref == http://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
The only thing which is important here will be to use a Froyo or newer version SBF.
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani said:
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
Click to expand...
Click to collapse
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Thanks Rajneeshgadge17
JRDNEM_U3_3.4.3-33-1 is working...
thanks you for your precious time.....
Defy is seems okay now and will tell you if i found any bug in this JRDNEM_U3_3.4.3-33-1.
I think i flashed every time with eclair and that was the main problem. First time flashed with froyo and black screen gone.
Thanks again and plz tell to root this rom is as easy like what i did with orignal froyo.
I did it with Super one click and than use 2ndint and moved to custom rom.
plz tell should i follow all those steps for rooting and for custom rom, or there is something new to be done for this flashed Rom.
Thanksssssss ,, i am so happy now
cute_kayani I think you double posted mistakenly....
Have already answered your query above
I'm glad to know that it’s finally working for you!!
Yeah to root this follows the same procedure as you have used with the Éclair...
Simply Turn on USB debugging and use Super One click to Root.... >>>> then use 2nd init apk to flash with the Custom recovery
All Izz Well!!
Click to expand...
Click to collapse
---------- Post added at 09:26 PM ---------- Previous post was at 09:12 PM ----------
One important thing for your information is the reason behind those black screens was that you must have flashed Froyo SBF before; which was not down-gradable and now at this point you were trying Éclair which resulted in this issue.
So, the Downgradibility of your previous flashed SBF was causing this issue.
Now, as you have flashed this Froyo SBF; so, now onward in case you need to flash you phone you need to use SBF which should be Froyo or newer and must have “3.4.3” or later Build Numbers.
Hope this helps someone who needs this information.
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
cute_kayani said:
okay
one bug found, market is still not updated to play store, and when i try to download it says download paused . i cleared both data and cache of market but still not downloading and stuck at paused.
Click to expand...
Click to collapse
LOL its official Froyo it might have more bugs
haha okay i am moving to miui.... but from past 7 days my defy remains dead due to Miui weekly rom update
hopefully this time miui wont make any problem
LOL
All the very best this time ..
You know what last week I also updated to MIUI 2.3.23 and my wifi was not working with that ROM however, it was working fine with my CM9 as I had dual boot.
Please update me if you also face this issue with the MIUI 2.3.30
currently am on 2.3.23 every thing is okay, and wifi also working now am updating it to 2.3.30. will tell you if there any wifi bug.
Will wait for your review!!
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
cute_kayani said:
More force close, and now message comes for low storage. DON'T know why.. some apps moved to SD.
Click to expand...
Click to collapse
Lol 2GB internal memory occupied
Yesterday night I flashed with MotoGinger III for a change... so far so good. However, AutoWifi fix is resetting my wifi pwd every 15 mins or so ..
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
Occupied :/ now how to free that, miui occupied or rom flash occupied it. Internal storage is now just 15 mb left. How to use this defy now
But I used miui before flash, at that time I haven't experienced any low storage problem.
NOTE: I typo'd the thread title, it's supposed to say MF3 not MK3.
I have been unable to get a rom working on SafeStrap (AT&T SGH-I337, MF3). I have SafeStrap loaded and working just fine.
This is the process im using to load a rom, please let me know if im doing something wrong or if you got any further advice:
I create the rom-slot, default values.
Then I goto Wipe, and use the "Slide to reset to factory"
Then i goto Install, select the ROM zip file (ive tried several, all have been verified to work on my setup such as darkstalker, gpe, or graviton)
After that's complete i will do install again but select my mk3 components to fix wifi etc. Ive tried with and without this step.
After all this is done and i reboot, it goes to the Safestrap enabled screen and after the 10 second wait the screen goes black and a few seconds later the options and back button on the phone turn off. after a while it'll reboot and loop the same.
And that's as far as i get, everytime =$ I can jump back to stock-rom just fine
Any info you got, advice, etc?
Today I tried flashing my backed up stock rom (from stock-slot) to rom1 slot. This did the same thing. Black screen after "Safestrap Enabled" and several seconds later, the lights of the menu and back button on the phone go out. A minute or two later, I get two vibrations and it loops back to the start from there. >.<
thegtproject said:
I have been unable to get a rom working on SafeStrap (AT&T SGH-I337, MK3). I have SafeStrap loaded and working just fine.
This is the process im using to load a rom, please let me know if im doing something wrong or if you got any further advice:
I create the rom-slot, default values.
Then I goto Wipe, and use the "Slide to reset to factory"
Then i goto Install, select the ROM zip file (ive tried several, all have been verified to work on my setup such as darkstalker, gpe, or graviton)
After that's complete i will do install again but select my mk3 components to fix wifi etc. Ive tried with and without this step.
After all this is done and i reboot, it goes to the Safestrap enabled screen and after the 10 second wait the screen goes black and a few seconds later the options and back button on the phone turn off. after a while it'll reboot and loop the same.
And that's as far as i get, everytime =$ I can jump back to stock-rom just fine
Any info you got, advice, etc?
Click to expand...
Click to collapse
I'm not sure that u are on MF3 or MK2.......Both using different Safestrap version......MF3 use SS-v3.65 and MK2 use SS-v3.71 but your is MK3.....i dunno if there is new MK3 firmware just update lately.......Deadly venom SS edition just released couples hours ago for MK2+SS-v 3.71 users....... everything worked.....for link and guide check Post #4 DVSS_EDITION_ML6. ...
Swyped from MK2 Deadly Venom SS
I apologize about that, it is MF3. I did in fact have SafeStrap 3.71. So I odin flashed back to stock. Re-rooted and re-installed SafeStrap 3.65. Slightly different results, when I try to install a ROM after it gets to the SafeStrap Enabled screen, it goes black and then starts this strange 2 vibrations, pause several seconds, 1 vibration, and it repeats that 2-1-2-1-2-1 vibration pattern until i reboot it.
So still no luck, can't get a ROM installed. Any idea?
P.S. im going to try and correct the thread title to reflect the right MF3
thegtproject said:
I apologize about that, it is MF3. I did in fact have SafeStrap 3.71. So I odin flashed back to stock. Re-rooted and re-installed SafeStrap 3.65. Slightly different results, when I try to install a ROM after it gets to the SafeStrap Enabled screen, it goes black and then starts this strange 2 vibrations, pause several seconds, 1 vibration, and it repeats that 2-1-2-1-2-1 vibration pattern until i reboot it.
So still no luck, can't get a ROM installed. Any idea?
P.S. im going to try and correct the thread title to reflect the right MF3
Click to expand...
Click to collapse
Did u READ this thread http://forum.xda-developers.com/showthread.php?t=2428254.....there is very good information......including what rom that compatible with SS-V3.65. ....from first post (OP)......good luck. ....Hit thanks if people helped u........matter affect this rom worked perfecty for me.....im using it right now as my DD phone not to mention MK2 firmware phone with the link I posted earlier.....
Swyped from MF3 Deadly Venom SS
ted77usa said:
Did u READ this thread http://forum.xda-developers.com/showthread.php?t=2428254.....there is very good information......including what rom that compatible with SS-V3.65. ....from first post (OP)......good luck. ....Hit thanks if people helped u........matter affect this rom worked perfecty for me.....im using it right now as my DD phone not to mention MK2 firmware phone with the link I posted earlier.....
Swyped from MF3 Deadly Venom SS
Click to expand...
Click to collapse
Yes i did read that. As a matter of fact that is the rom i tried very first. Same results.
Im in the exact same boat as OP
MF3
Everything went according to plan, tried a few different roms.
Flash says it goes through, reboots, get the safestrap enabled screen, wait ten seconds... phone just reboots over and over.
Hello to all.
I have a cell DEFY MB525 and he was flashing a ROM with brick and was wrong. With white led. I looked at various threads here in this forum, I discovered how to revive using a ROM BL7 the DEFY MB526.
However coming back to the original ROM MB525, or any other rom, the phone brick. Appearing white led.
I can not use the ROM BL7 Defy MB526, because I can not customize with a modified rom (cyanogemod for example) and worse and that many features of the device are in trouble, such as wifi, bluetooth connections.
One of the most common problems in using the MB526 is a ROM that the device is restarting all the time.
To advance, I'll tell you what I did:
I tried all the ROMS BL7 site (4.5.1-134)
I tried to put a ROM BL7 then a Chinese ROM:
JDGC_U6_2.12.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANGCCORE_P013_A033_HWp3_Service1FF
Another Chinese Rom:
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF
And in both tests the phone brick.
I also tried several of the rooms MB525 (not all, but I'll still try ...)
I also tried to install a custom rom MB526:
cm10.Quarx24.09.Defy + red.fixed.sbf
In addition to some custom roms the MB525:
FroyoCEE_cm7.2_2.3.7
Froyo-MIUIandroid.2.4.20-fixed
Froyo-cm9.epsylon-27.06.12.bl4-fixed
froyo.cm10.JB.Quarx.24.09Defy.red.green.bl4.fixed
However .. all attempts brick the phone.
There is finally a way back for any rom MB525, preferably one ROOT to customize with Android 4.0 and use multiple languages?
Once you flash a higher BL version, there's no turning back! You are now stuck with BL7 SBF's only.You should have read the "All-in-one Defy Beginers' gide" by Zephyrot beforehand.
Try This :
http://forum.xda-developers.com/showthread.php?t=2318453
jalal-jap said:
Try This :
http://forum.xda-developers.com/showthread.php?t=2318453
Click to expand...
Click to collapse
So ...
Excuse my ignorance. I believe that some procedures should have a minimum of knowledge. Thanks Aurius!
I've plotted a plan to recover and am following with a mix of topics from the forum.
I managed to do the following:
http://forum.xda-developers.com/showthread.php?t=1595013
And with this I could install Boot to install custom roms
Also unable to access the custom boot and install:
cm-7-20130301-NIGHTLY-Jordan or CM10-20120924-NIGHTLY-mb525
The problem is that if I install "cm-7-jordan" the phone never leaves the logo "M" .. and if I install CM10-Nightly-mb525 the phone is stuck in "cyanogen logo"
I've tried making various wipes .. the normal boot ... by custom boot without success ..
Not to mention that I'm still with the problem of direct restart the phone.
alex.p.mahmud said:
So ...
Excuse my ignorance. I believe that some procedures should have a minimum of knowledge. Thanks Aurius!
I've plotted a plan to recover and am following with a mix of topics from the forum.
I managed to do the following:
http://forum.xda-developers.com/showthread.php?t=1595013
And with this I could install Boot to install custom roms
Also unable to access the custom boot and install:
cm-7-20130301-NIGHTLY-Jordan or CM10-20120924-NIGHTLY-mb525
The problem is that if I install "cm-7-jordan" the phone never leaves the logo "M" .. and if I install CM10-Nightly-mb525 the phone is stuck in "cyanogen logo"
I've tried making various wipes .. the normal boot ... by custom boot without success ..
Not to mention that I'm still with the problem of direct restart the phone.
Click to expand...
Click to collapse
staff
Trying to solve the problem I reported, I tried this:
http://forum.xda-developers.com/showthread.php?t=1923855
However whenever I update the kernel, it gives a black screen coming in direct firmware upgrade with "Err, A5 ...":crying::crying:
So with que, I need to go back to step 2 Which is to defy the firmware upgrade file (rooted room. Returning, I fall into the same problem I reported .. Eternal Logo Motorola, or Multiple reboots.
Talking about multiple reboots, tried unsuccessfully this tutorial:
http://forum.xda-developers.com/showthread.php?t=1923855
alex.p.mahmud said:
staff
Trying to solve the problem I reported, I tried this:
http://forum.xda-developers.com/showthread.php?t=1923855
However whenever I update the kernel, it gives a black screen coming in direct firmware upgrade with "Err, A5 ...":crying::crying:
So with que, I need to go back to step 2 Which is to defy the firmware upgrade file (rooted room. Returning, I fall into the same problem I reported .. Eternal Logo Motorola, or Multiple reboots.
Talking about multiple reboots, tried unsuccessfully this tutorial:
http://forum.xda-developers.com/showthread.php?t=1923855
Click to expand...
Click to collapse
I installed a customized version:
CM9-NIGHTLY-Defy-121116
And this happened:
* The first time was more than 5 minutes at Cyanogen logo and not charged;
* I removed the battery, waited a bit and then called .. al entered the Android .. I was very happy when I first saw one andoid 4.0 and also on entering settings and see that the name of the phone is MB525 .. however when it restarted tinker a bit ..
* After reboot, it got stuck again in the Cyanogen logo. I removed the battery .. I waited a bit and then charged;
* After loading test the camera was OK, tested the WIFI and it does not work!;
I believe this is the way .. install a custom rom and fix all possible problems that will have as Camera, GPS, Bluetooth.
What is the rom the MB525 which is more stable?
jalal-jap said:
Try This :
http://forum.xda-developers.com/showthread.php?t=2318453
Click to expand...
Click to collapse
I tried this procedure but unfortunately not defy the advances in bootloader. Another night without success ...:crying::crying::crying::crying:
flash BL7 SBF.
http://forum.xda-developers.com/showthread.php?t=966537
---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------
flash any custom kernel Rom ( My --> Slim kat 4.4.2 ).
Before Reboot connect your phone to PC OR Charger
Here your defy Wont reboot.
then install rootexplorer apk.
go to system folder--> find battery state .bin
Set permission and chek all square.
battery always show 100%.
But Your phone wont restart any more.
jalal-jap said:
flash BL7 SBF.
http://forum.xda-developers.com/showthread.php?t=966537
---------- Post added at 12:36 PM ---------- Previous post was at 12:28 PM ----------
flash any custom kernel Rom ( My --> Slim kat 4.4.2 ).
Before Reboot connect your phone to PC OR Charger
Here your defy Wont reboot.
then install rootexplorer apk.
go to system folder--> find battery state .bin
Set permission and chek all square.
battery always show 100%.
But Your phone wont restart any more.
Click to expand...
Click to collapse
I can BL7 flashing the firmware and the phone connects normally .. the problem is that it does not work wifi, it makes connections and has many problems.
I'm trying to install one of the custom room MB525, to see if the problem actually .. so I'm currently experiencing various custom roons CM7 CM9 and CM10 ... .. Today I managed to run a CM10 .. But to advance the initial setup it gives error.
alex.p.mahmud said:
I can BL7 flashing the firmware and the phone connects normally .. the problem is that it does not work wifi, it makes connections and has many problems.
I'm trying to install one of the custom room MB525, to see if the problem actually .. so I'm currently experiencing various custom roons CM7 CM9 and CM10 ... .. Today I managed to run a CM10 .. But to advance the initial setup it gives error.
Click to expand...
Click to collapse
Hello to all .
In particular the user avi_tandel conversation I managed to evolve a bit more and now have a phone with Android 4 ( CM10 ) .
So with that, I will explain here for those who are going through what I went through, how to get out of this problem
Step 1 - Install Rom BL7
I installed the rom ( 1 - DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF) that is in the link:
http://sbf.droid-developers.org/phone.php?device=27
Step 2 - Install a Rom Rooted
I installed this one , the post below :
http://forum.xda-developers.com/showthread.php?t=1595013
Step 3 - Wipe Data / Cache
Step 4 - Turn off your phone and see if it is charging the phone if yes .. leave the phone with 100 % load
Step 5 - Load Firmware Booted , skip the initial setup and habilte the USB Debugging option.
Step 6 - Via computer, install the 2nd Int
Step 7 - Restart the phone and when the blue LED appears, press Volume ( - )
Step 8 - Ext3 format ;
Step 9 - Wipe Data / Cache / Cache Davil
Step 10 - Install a custom Rom CM10 - 20120924 - NIGHTLY - mb525.zip
Step 11 - Install the GAPPS GAPPS gapps_update_2.3.5 - signed.zip
Step 12 - Reboot the machine and wait a long boot will be done (somewhere around 5-10 minutes). Important .. if the player does not leave the logo "M", turn off your phone, connect to the universal charger and wait to get up to 100% again. Then repeat the steps 7,8,9,10 and 11.
Step 13 - Your phone will load the Android 4.0, test all the features to make sure it's right.
Me I tested successfully:
* Camera photo and video;
* Sound recording;
* Wifi;
* GPS;
However I am facing some problems, I would like to see if it went through and how it resolved:
* Lots of slow to start and to use the telephone;
* Problems finding the band/net (can not make calls and send sms);
* Reset the device, the device restarts During the bootloader or after open Android;
* Catching some google apps;
Does anyone have any solution to some of my problems?
Thanks in advance:fingers-crossed::fingers-crossed::fingers-crossed:
Why are you installing an antique rom? Get the latest from the thread(quarx2k.ru, 30th October). Also format to ext4. Use baseband switcher in defy parts in settings for network. I did not understand "catching some Google apps"
Sent from my MB526 using Tapatalk
maybe u should wipe system in twrp recovery.(dont reboot after wipe)
then Flash rom
thekguy said:
Why are you installing an antique rom? Get the latest from the thread(quarx2k.ru, 30th October). Also format to ext4. Use baseband switcher in defy parts in settings for network. I did not understand "catching some Google apps"
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
You say to install this rom?
http://quarx2k.ru/cm10-2ndboot-nightly-defy (+) / cm-NIGHTLY 10-20131030-mb526.zip
She is not only DEFY (+) MB526? For this I installed another rom ...
About baseband, I think I know what it is .. roted as the firmware that is installed Chinese it comes configured with the wrong baseband. I just still can not test because the phone is restarting all the time.
About "Catching some google apps", some googles apps like maps, search, are giving error.
jalal-jap said:
maybe u should wipe system in twrp recovery.(dont reboot after wipe)
then Flash rom
Click to expand...
Click to collapse
How do I do this?
alex.p.mahmud said:
You say to install this rom?
http://quarx2k.ru/cm10-2ndboot-nightly-defy (+) / cm-NIGHTLY 10-20131030-mb526.zip
She is not only DEFY (+) MB526? For this I installed another rom ...
About baseband, I think I know what it is .. roted as the firmware that is installed Chinese it comes configured with the wrong baseband. I just still can not test because the phone is restarting all the time.
About "Catching some google apps", some googles apps like maps, search, are giving error.
Click to expand...
Click to collapse
Model is irrelevant for recent roms. First, format to ext4(no reboot). Wipe system, data and cache before flashing rom and gapps.
Sent from my MB526 using Tapatalk
thekguy said:
Model is irrelevant for recent roms. First, format to ext4(no reboot). Wipe system, data and cache before flashing rom and gapps.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Oh my god ... there is no miracle to make this my phone work. :crying::crying::crying::crying::crying::crying:
I tried exactly what happened and said several things:
* Bootloader caught in the logo "M";
* Boot Loop, always to shine brighter the logo cyanogem;
* Charged the system, but it did not work Wifi and a message appeared saying that the phone was faulty and needed to be rebooting. After this, I restarted the phone and the same message appeared. After skipping the initial settings of android, the phone keeps resetting ..
I'm desperate .. already spent several thoughts about this phone, how to break it, burn it, stepping on top, throw on the wall, among others .. but I managed to keep me calm and believed that one day I will fix this unit. :angel::angel::angel:
Help me please .. I know that the options are not exhausted!
Data wipe from stock recovery, use minimal gapps( banks core gapps(the smallest size) and the correct one for your android version). If data reset occurs on ext4 after a clean install(no boot loop) then it must be a hardware problem
Sent from my MB526 using Tapatalk
thekguy said:
Data wipe from stock recovery, use minimal gapps( banks core gapps(the smallest size) and the correct one for your android version). If data reset occurs on ext4 after a clean install(no boot loop) then it must be a hardware problem
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Hey .
I did exactly what you said and now unable to run the system .
I am however a problem with the system displays the following message :
Telephony problem
A problem was detected in the phone 's telephony later . a reboot of the phone is required to repair the phone state . What do you want to do?
Perhaps for this reason , can not make calls and use 3g .
With regard to the problem of links tried updating the baseband using the file ( bbsV4.0mlV0.7.zip )
I selected multiple carriers ( Brazil ) and did not work .
I read on some forums that the " telephony problem" was enough to wipe cache and cache davil ... did not work .. but ..
The great news is that for now the phone is not restarting ..
And unfortunately , just broken my LCD , I'll have to buy another .. I left the device with the Motorola logo about 2 hours to see if it started .. and this has made the lcd generate a patch of dead pixels .
If anyone has any tips to solve the problem of this message help me !
Try a different rom, like cm 7. Start from sbf, and use the gapps from the cm7 thread. Try the freezer method to get rid of dead pixels
Sent from my MB525 using Tapatalk
thekguy said:
Try a different rom, like cm 7. Start from sbf, and use the gapps from the cm7 thread. Try the freezer method to get rid of dead pixels
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Hello to all .
Took me to post something because I wanted to test the most of the options that were given to me here in this forum .
I did the freezer method is unable to get a little touch of the damage . But still some stains .. unfortunately I will have to buy another . (No problem ) .
I tried to install CM7 as was instructed and managed for once to configure and test a few things that worked as WIFI , CAMERA , CAMCORDER ..
But .. as well as other customs roms , the problem of eliminating the logo " M" or keep restarting remains .
To be honest , I can only do something about this phone as follows :
* The night he let Loading and off for 10 hours or more;
* When you wake up and turn on my phone for about 2 .. 5 minutes I can do something .. eg rootting or start a custom rom that crashed in Cyanongen soon .
I made some videos to show rather than going to .. and as a result , once you've installed custom one room again , I'll make another video .
https://drive.google.com/file/d/0Bz5W5nUB8BfUR1hMWi1fY0hfV2s/edit?usp=sharing (53 MB)
First video shows the installation of the Chinese ROM :
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF
Realize that the process does not occur naturally , disconnect the phone and rsd lite never completes the process :
https://drive.google.com/file/d/0Bz5W5nUB8BfUZmlhSGhsX0hoR2s/edit?usp=sharing (58 MB)
In the second video , I show the installation of the rooted rom :
firmware.sbf
The result is similar to the first video .
https://drive.google.com/file/d/0Bz5W5nUB8BfUcHFEZlhVYUZ5Zms/edit?usp=sharing (22 MB - Play Online)
In the third video , I show a major problem, just stop in M. Notice that I can not do easily wipe .. wait only a few hours after the phone is 100 % charged .:crying::crying::crying:
https://drive.google.com/file/d/0Bz5W5nUB8BfUU2cyaURnSjZGYkE/edit?usp=sharing (28 MB)
In the fourth video, after waiting a bit, I managed to get into the stock recovery. Do wipes and restart the phone .. and as always .. does not work..Will only work if you leave the phone still loaded .. all night ..
I'm beginning to think that this phone is something physical, maybe a problem on the motherboard.