Database Users

[Q] Can't find the SBF of my region

I have a Defy that's from Movistar Chile (Froyo 2.2.2 "3.4.2-108_JDNL-2"), I was looking to root it and install another rom, because the phone randomly reboots when entering certain specific towers, and see if my problems were solved.
Since the only way to change the radio was flashing other Full SBFs, I wanted to try other, the thing is that the SBF for my region/carrier is nowhere to be found. And I kinda need some way to go back to stock in case I need to use the warranty.
Besides, I installed 2nd init, and I'm worried that because the uninstall is partial the tech support could reject the phone. Do I have a solution or am I screwed?
Best Regards,
Lugaidster

Here You have almost all roms to Defy. If You wont find yours 2.2 try to find 2.1 and then use MSU to upgrade to Froyo. 2nd Inint will be removed after full flash sbf.

Sorry for my ignorance, but what is MSU?
Best Regards,
Lugaidster

Motorola Software Update which You can find on Motorola's site.

One last question, when you say 2.1 in your other post, do you mean 2.2.1? I'm under the impression that I can't downgrade to Ecclair or Froyo 2.2.1 if my phone came with Froyo 2.2.2 (because of the whole eFuse deal).
Best regards,
Lugaidster

Right, I forgot about unsigned kernels so if You have Defy with Froyo without any upgrade You can't downgrade it to Eclair and then upgrade to Froyo back.
I'm afraid that You wont find this rom. Only way is to find someone with it and ask for nand backup and then uninstall 2nd init. But as I remember in my region (CEE) before upgrade to Froyo people who had damaged phones with installed beta or chinese Froyo was sending their phones to Motorola on warranty and in few cases Motorola didn't asked about different software and they repaired hardware damages. If You wont find it u can flash it with some 3.4.2_107 and try to send it to Motorola if You need warranty repair.

Ok, thanks anyway. I think I'll take my chances and leave it as it is. I guess I'm stuck with a randomly-rebooting phone (Already took it to tech repair and they said that there was nothing wrong with the phone, and unless there's something wrong with it they won't change it).
Best Regards,
Lugaidster

BTW it's normal in Defy rebooting sometimes. I had Defy normal on stock Eclair and next Froyo and now I have Defy+ on stock 2.3.4 and now testing CM7 and on both phones and all firmware versions phones had 3-4 randomly reboots in week.

The thing is that more often than not, it reboots like 10 times in the span of an hour. It's incredibly annoying.

When it keeps rebooting turn on airplane mode and watch for results. If it stop rebooting it's problem with sim card. I heard that in few cases T-Mobile cards had problems in Defy and device keeps rebooting all the time and freezes. It can be problem with SetVsel if You have one, set defaults values. But if airplane mode helps just change sim card on new carrier or normal/micro sim (different that one You have now). Hope it should solve Your problem.

As you mentioned, airplane stops it from rebooting, the thing is that it doesn't matter which simcard it has, it reboots either way, I have it locked so I haven't tried with other carriers, but with the current carrier it reboots like hell. The most annoying thing is that it does so only on certain locations and I happen to live in one of those. I leave for work and it stops rebooting until I return.

Try to mix 2G/3G only and with/without data transfer and set network manually/auto.

I'll try that, but I won't keep my hopes up... I'll notify in case it fixes something, since I can't be the only one with this problem.
Best Regards

Nope You're not. Here You have similar problem. I didn't read whole thread but parts about sim card problem. Maybe it gonna help You somehow.

[q] weird problem

I used z4root to root my defy ....I don't know why i used that crap instead of using gingerbreak...But i used it.My Defy s firmware was written as Retail.2.xxxx something. I was not able to root it anyway.It used to force close.But after trying to root it,my phone suddenly started rebooting..IT showed up the moto symbol., then the screen went black and again the moto symbol..Its was going in a cycle..I was not able to boot it..!..i tried flashing it...Didn't work.!!...Any suggestions of why it happened??
My defy had a water damage ..I gave my phone to service on august 2011...I got that repaired on jan2011. I had a complete backup of cm7 with me...so was trying to restore it that night as soon as i got my defy..This thing happened.!!....So i had to again give it to the shop....But its repaired now.. Will get my defy tomorrow after 8 damn holy months of boring of without my pal!!!!!!!
I M THE ONLY ONE WHO SPENT 3000 BUCKS FOR THIS IDIOTIC WATER DAMAGE ON A WATER PROOF DEFY...!!!!...BUT I SIMPLY LOVE MY DEFY

Check here:
http://forum.xda-developers.com/showthread.php?t=1216982
Wipe data

FYI on Warranty Replacement

So, I was having some problems, my phone was only rooted, not unlocked. OK a LOT of problems after the latest update with my phone freezing and rebooting. Wiping cache and factory data resets didn't work. Did a data reset and didn't install a single app or widget and still locked up and reset after using it for a couple minutes. I used the droid utility 1.21 by mattlgroff to go back to the 9.20.1, rooted, and then took the factory OTA again and still lockup and reboot machine.
So, called Verizon, told them what I did (minus the mattlgroff utility), and they sent out a replacement to me, 1 year warranty on the phone. I bought the phone from Best Buy, they told me they couldn't do anything unless I got their goon squad warranty. Call to Verizon was fast and painless.
The replacement showed up today, and this is how it was equipped:
9.16.9.xt926
4.1.2
radio 100730.081.64.09P
Kernel 3.0.31-ge491d6d 4/5/13
build 9.8.1Q-62_VQW_MR-4
build date 4/5/13
Had a sticker on the back with the IMEI and software version and a date of 7/18/13.
Good news for me is I was unable to unlock the bootloader on this one because I was a dummy and didn't unlock the bootloader on my last one. So, now I'm back to 9.20.1, rooted, unlocked, and got CWM installed. Now it's time to pick a ROM and start flashing as soon as my new SD Card shows up seeing as I lost everything I had backed up on my SD Card because it died on me out of the blue on Sat, GRRRRRRRRRRRRRR.
If you're having issues with the updates, give Verizon a call and get yourself a replacement. Good chance you can get one that is still able to be modified!

Phone stuck at 'Checking connection' after factory reset.

My Device (Spice Dream Uno) is a year and a half old. The previous month my device started having memory shortage problems so I rooted it and removed a few bloatwares. Yesterday, I found that my phone was freezing a lot so I did a full factory reset. The reset was successful but now when I try to boot it, It comes to the activation screen and after selecting the WiFi network it starts checking connection and never stops. I tried not selecting the WiFi but it won't let me skip past it at all. Please help. My bootloader is not unlocked.

the same case I have. my phone is nexus 5

even i am facing the same problem. how did u fix that?
saptarshi5683 said:
My Device (Spice Dream Uno) is a year and a half old. The previous month my device started having memory shortage problems so I rooted it and removed a few bloatwares. Yesterday, I found that my phone was freezing a lot so I did a full factory reset. The reset was successful but now when I try to boot it, It comes to the activation screen and after selecting the WiFi network it starts checking connection and never stops. I tried not selecting the WiFi but it won't let me skip past it at all. Please help. My bootloader is not unlocked.
Click to expand...
Click to collapse
i have an android one mobile. did u fix that? if yes, how? thanks in advance.

does anyone got solution for this??
same problem with karbonn sparkle v.

Just unlock your bootloader and flash stock rom with sp flash tools.....
(Or)
Unlock bootloader and install any custom recovery after that flash any stable custom ROM
Sent from my Spice Mi-498H using XDA Free mobile app

Sigh.. Bootloop problem out of nowhere

My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****

Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.

i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.

thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.

galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI

thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.

I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app

Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.

Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.

tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired

It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app

uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.

Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha

My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.

andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...

Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.

New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.

Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.