I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
derviansoul said:
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Click to expand...
Click to collapse
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
farsight73 said:
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
Click to expand...
Click to collapse
I left the phone overnight without the battery on, and this morning for some reason i could reboot to 2.3.3 at first the phone stayed on without rebooting for about 30mins, but soon it started doing the same constant rebooting now it doesnt even go past the moto sign.
I have wipeout now the cache also and no changes.
dlcookie said:
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
Click to expand...
Click to collapse
What do you mean for a fixed sbf? That is a new term for me. It is really hard install the bootmenu thing because the phone doesnt stay on for long in the android os!!Is there any other way to connect to adb?
I got a fixed sbf and attempted to follow all the steps stricly, but when i dowgraded from gingerbread 4.5.1-112 Orange GB 2.3.3 with MotoBlur to Uk 3.4.2 froyo stock sbf from here
http://forum.xda-developers.com/showthread.php?t=933555
my phone this time gone really weird:
All i managed to do with this sbf was to root it with superclick, before it gone off again.
yesterday Saturday 03-12
-When I put the battery in, the phone refuses to go on, or to get in bootloader/recovery, after a few minutes the boots automatically and gets stuck in the moto logo (sometimes it goes off sometimes just stays there for 5min or more).
- If i plug the phone sometimes it stays off with the white led on, but rsd doesnt detect it, neither it goes on bootloader/recovery and sometimes it boots automatically sometimes doesn't come on at all.
Today:
- Tried to get the phone on this morning, it wouldnt go on or go into bootloader/recovery, then eventually it started up on its own and got stuck on the moto logo, i took the battery off and tried again, the phone wouldnt come on again, but eventually it started on its own and went to the bootmenu, where for the first time it crashed there, and it didnt recognise usb cable. I tried again and the phone booted up on its own with the usb cable to the bootloader,it gave the ok status for the usb connection but rsd lite never recognise it. Now it wont go on at all.
Please note that i have a desk charger and all this was done with a nearly full or full battery.
Does anyone know if the phone is completly dead now or if there is anything else I can do?
Thanks for the replies.
Mine just rebooting too
Dear derviansoul (",)
Hope all is well with you.
I just have the rebooting issue, like what you said (stayed on for 2-5mins before it goes off to reboot; phone never reboots in bootloader or recovery mode).
What i did was:
- i fell in love with Cyanogen mod 7.1.0-11 & 7.2-rc1 recently (thanks to Quarx & all in CM for your hard work);
- i had 32gb microsd card & decided to spent my hard-earned $ on a 64gb microsd card for this wonderful phone (due to CM, not Motorola);
- Sandisk microsd 64gb works AFTER erasing in Settings -> Storage;
- then, using Symantec Ghost 8.2 to clone my 32gb microsd card into 64gb;
- after putting in the clone-completed 64gb microsd card, the phone starts rebooting as described above;
- i tried to put back my own original 32gb microsd card, but the rebooting still happens!?!;
- in Recovery mode, i "wiped cache" & then go to "advanced", select "wipe dalvik cache", but problem remains;
- i formatted the the 64gb from Recovery mode, and manually copied the contents of the 32gb to 64gb using my WinXP computer, but the problem still remains!;
- (my solution) in bootloader mode, i go to "Tools" -> "share sd card", then from my WinXP computer, i can see the microsd card as Mass storage device, i deleted ONLY the folder ".android_secure" which is more than 2GB large.
- now there is no rebooting, and i just need to reinstall my apps from the Play Store, & my settings and data are all still there *sweet*.
Hope this helps.
Motorola Defy (red lens) cm7.2-rc1
Related
Current Situation:
When I say bricked, I mean BRICKED in all caps. The phone is completely unresponsive. If I try to turn it on – no good. If I try to put it in bootloader mode – no response. If I hold the volume button down and depress the power – no menu displays. I get no ‘M’. I get nothing. Except…
If I fire up RSD Lite 4.9 and plug in the phone, it does recognize something. Under model it displays “S Flash OMAP3630”. If I load up an sbf file (I’ve been following Higgsy’s incomparable “How To” guide - http://forum.xda-developers.com/showthread.php?t=853674 and using the generic UK sbf file he recommends) and depress “Start” within RSD Lite, the phone will display “SW Update In progress…” in white blocky text. RSD Lite says it’s executing and, after several minutes will display a Status of “Finished” and a Result of “PASS”. On the phone, the screen goes dark but a white notification light displays. While the phone is still plugged in, I can depress the power button on and off and RSD Lite will recognize it’s there (if it’s on) or not recognize the phone is there (if the power is toggled off).
Note that the battery is fully charged.
I’ll give you a little background info:
Background:
I purchased Defy phones for my wife and me for Christmas. Her’s is working fine, is unrooted, and has only a few apps beyond stock (Angry Birds of course!). But of course I had to play with mine. All went well until I (stupidly) installed the latest T-Mobile update which removed my root access. This was not acceptable to me as I had overclocked my phone for performance purposes. I had a really hard time getting root access back until I at last found a version of SuperOneClick that did the trick.
By this time I had reset the phone back to factory settings. So I thought “Well, I might as well flash some cool ROM”, so I flashed a Gingerbread themed Froyo cooked up for the Defy. Unfortunately, it didn’t work (for whatever reason). I was stuck at the dreaded ‘M’.
Next I started following Higgsy’s guide (as mentioned above) but I guess I screwed something up because now the phone is totally unresponsive except as detailed above.
So where do I go from here? Some possibilities:
Flash T-Mobile 2.2 test sbf?
Link?
Flash Original SBF?
Link?
I’ve still got my wife’s phone which is working perfectly fine. Is there a way to copy files from her phone to my dead phone and get some life?
Do you guys have some other steps you’d recommend?
I’d really like to get my phone working again and would much appreciate the help. Many thanks in advance.
(Note that I’m a Noob so please don’t assume I know anything!)
(Yet another note: I'm in the USA.)
Which .sbf's and in which order did you install them?
The same happened to me after I'd flashed the 3.4.2 sbf, then tried to downgrade back to 2.34. it went blank and I had to reflash 3.4.2 again.
If you've flashed 2.51 or 3.42 then you can't downgrade from them. So the fix would be to flash the same rom again.
I have the same problem and this how i fix it
1.http://forum.xda-developers.com/showthread.php?t=892026&highlight=low+battery your phone will show in rsd lite
2.flash http://forum.xda-developers.com/showthread.php?t=933555 with him you get a error that can not be installed
3. disconnect phone from USB and remove the battery
4. Replace the battery in the phone and power up, and phone immediately go into the bootloader
5. Flash bootonly http://forum.xda-developers.com/showthread.php?t=899450
6. and finaly flash http://forum.xda-developers.com/showthread.php?t=922430
it works for me
sorry for bad english
Solved
I flashed http://forum.xda-developers.com/showthread.php?t=922430 per your suggestion and I'm now up and running. Thank you.
Motorola Defy bricked
hi
i have a question about my defy. The white led is still shining but there is no connection to the pc. I connected via USB-cable.
pls HELP!!!!!
I have a similar issue as the OP..
I originally rooted the phone using simpleoneclick... then I overclocked it using setvsel...
it was running fine for an hour or so, and then I ran quadrant (several times over the course of the hour) and the final time, it rebooted during the middle of a test, and then it would just keep looping the bootup moto logo and "android" screens.
at that point I could still enter the bootloader and recovery screens. I tried wiping data and resetting to factory defaults with no avail.
Finally I followed a thread on flashing a new rom to the phone with RDSLite and the uk rom. After getting it to finish flashing and it showing a 'Finished' and 'PASS' status as the OP mentioned, te phone now no longer responds. Power button does not trigger the screen to go on, regardless of if I try to press the volume buttons with it or not.
The only response I get from it is when it is connected to the computer, the white led turns on, and the computer (and rdslite) recognizes it. I can still flash it with rdslite and the screen turns on displaying the SW update In progress message...
but that's about all I can get it to do.
Any help and advice would be greatly appreciated
edit: I should also mention that after the uk 2.21 rom I've also tried the china 2.2.1 roms.... Should I also try flashing the 2.51 uk version as well?
Okay, I tried a few more roms and this one "JRDNEM_U3_3.4.2_117-00..." has everything back up and running...
however now i'm running into the issue of apps that i've 'downloaded' not actually installing...
bricked
same problem here. rsd can detect my phone but still failed flashing. i changed and renamed the /sbf but still doesnt work... please help
MB525 Defy Bricked
MB525 Defy bricked and rsd cannt detect my phone failed . ... please help
its dead. Actually i uninstalled busybox and in this process all the system files also deleted by busybox. now phone is not starting. if anyone can suggest. I was using MIUI rom. can any one make it alive again.
[email protected]
. ....please help
Same problem here, but my phone is only detected by a friend's laptop. I think I have to flash Defy+ rom
try to flash sbf use rsd
If your phone is detected by RSD Lite, then you have an easy fix in just flashing a new sbf. If it's not detected and you can't charge your battery, you're going to have to use the MacGyver method.
if sbf doesnt work u better send it to warranty
Well. On my computer the phone isn"t even recognized. Maybe because some RSD Lite files are missing and it need them to detect bricked defy (i did reinstalled RSD Lite)
If it's recognised on your friend's computer but not on yours then it means that you probably have the versions of the motorola drivers or rsd lite that have problems.
white led solution
hope for defy with only white led light turning on. This assumes that you have already have mototola drivers and RSD lite installed.
Background : I only had defy one day when I decided to flash it with miui. I bricked on the first time with bootloops. Did research and got drivers and rsd lite. managed to find three stock t mobile roms and flashed to stock Tom, then flashed miui, since then I've been switching between miui and cm7.
Problem : After a few months of use, I decided to flash stock rom to see how the battery life would be like. Bricked it the first time with bootloops. I thought I had flashed it with wrong rom because the first time I flashed back to original rom I did not delete the roms that I thought were the original roms. So after first failure I tried to flashed with the other roms I had. after the third rom it would not go into bootloader, only white led would turn on. Tried macguiver, did not work so save your usb cable, don't mess with it ain't gonna work.
Two part solution: I realized that when I plugged phone with usb I would hear the usb tone on win 7. When to device manager and saw the other device or something like that was appearing and disappearing when I would connect and disconnect phone. I clicked it and it said Motorola device or something like that, it was sensing my defy! defy drivers were wipe out due to bad flash. I had mototola drivers so I clicked on update and searched for mototola drivers on hard drive. I had rsd lite on and it recognized the defy after driver update, even though the bootloader screen was not on and just the white led was on.
decided to flash rom that have me bootloop and it flashed it but still gave me a bootloop., by the way, the update part of bootloader showed up after a while.
Second part of solution: googled problem and found out that the phone has a stock recovery. its the robot with the triangle exclamation mark. when you get to it you have to touch the extreme lower right hand corner of the screen to get to where you can wipe data and cache. when you start wiping data / cache you have to press on ok?? on lower left hand of the screen repeatedly until wipe is complete. then reboot and tada it boots up to stock tmo USA defy.
this is the stock rom I used : JORDN_U3_6.36.0
F Y I
if you ever try to flash a rom and it just bootloops, just go into stock recovery and wipe data and cache and you should be able to boot into android.
I'm Mc Gayvering my phone. Just tried a led directly connected to USB and fried it
This is my last hope
Is your phone worked?
I have the same problem. I try many ROM,But all of them dosn't work.
When I put in the battery,it shows Bootloader,When i flash a ROM use RSD，the phone always display SW Update In progress... Then the RSD's status is error verifying code group XX(XX=32/33/39/40 etc.) checksums.
What should I do?
THS.
Help :mad :
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me
wesleybinho said:
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me
Click to expand...
Click to collapse
dude this is all same **** u flashed wrong sbf.
flash the sbf service flash higher or same version which came by default wid ur phone.
flashes here http://and-developers.com/sbf:defy
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
well my dad was having problems with his defy, running a stock us 2.2.1. I looked at his phone, and after a few minutes, it would freeze up, and go into a bootloop, or still screen of the motorola logo.
First thing i tried is the stock recovery, which would freeze as soon as i started to wipe cache, and or data reset. After that, it gets stuck on the motorola logo no matter what.
I thought flashing a different .sbf would work, tried it, and finally got it to load to the "Welcome to android - please touch to continue" screen, as soon as i touched it, it froze.
flashed - JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF
went into recovery again to try to hard reset, but once again it freezes when it starts to clear cache/data factory reset.
Reflashed, now its still stuck on the motorola logo.
Any help is appreciated, thanks
DH
The phone seems absolutely messed up.. can you send it back to service?
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy
No I can't sadly, any recommendations?
Found a fix for anyone having this problem.v
Flash any sbf , and
Once its says "restart phone manually', exit the program, and unplug your phone, plug in your phone while in boot loader, them start the program,.and it should. Finish
the process, now you can clear cache and factory reset. Sorry I drank a little, the program is to install sbf's I can't think of the name
dyinghero27 said:
Found a fix for anyone having this problem.v
Flash any sbf , and
Once its says "restart phone manually', exit the program, and unplug your phone, plug in your phone while in boot loader, them start the program,.and it should. Finish
the process, now you can clear cache and factory reset. Sorry I drank a little, the program is to install sbf's I can't think of the name
Click to expand...
Click to collapse
Is the program RSDlite?
if yes the n how come when i was flashing a rom it never asks me to restart phone manually. and when i do quit the app any way and restart the phone in bootloader it does nothing.
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Charge battery with mcgyver metod or with other defy & reflash it with 231 sbf. For more info read: http://forum.xda-developers.com/showthread.php?t=966537
So, there's no other option out there?...
Deformat said:
So, there's no other option out there?...
Click to expand...
Click to collapse
Recharge battery with mcgayver metod and reflash sbf, you'll need start from scratch, because your bootmenu was corrupted and you can't restore nandroid or reinstall zip
Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...
Can't acsess anything
locn said:
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...
Click to expand...
Click to collapse
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi
Heddi72 said:
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi
Click to expand...
Click to collapse
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.
bootloader
corrinti said:
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.
Click to expand...
Click to collapse
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris
Heddi72 said:
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris
Click to expand...
Click to collapse
And your battery? Is it charged?
Yesterday I installed a custom rom
Today I flashed the verizon stock rom to see if that solves the problem (I've done before without any problem, first making a wipe data). But when the process is complete, the phone is stuck at bootscreen logo droid (not at M logo).
I rebooted the phone into recovery mode and did a wipe data.
Then the phone does nothing. I clicked on the Android but nothing happens. I´ve tried making wipe data lot of times but nothing happens. I´ve also tried to flash with 2.3.3 rom (I have 2.3.4) but nothing hapens too.
I can´t turn on debbuging usb mode because of this, so I can´t run a full wipe with ADB. Also, I don´t have any recovery mod or something like that.
Bootloader and stock recovery work both fine. So I think that this an exclusively software issue, but I don´t know how to resolve it.
There is any way to turn on the debbuging usb mode without using Android? Or there is any way to make a full wipe with ADB in this condition? Or what else could I try?
PD: Also tried to make an update of kernel and rom via SDcard, but I always get a signature error.