[How to] Solution for Random Rebooting of Defy - Defy Android Development

Hello Everyone,
I had this random reboot problem and posted it in various forums on the web but had not found the root cause of the problem.
But now I seemed to have completely solved it. Here is how for those experiencing similar issues.
1. If you are having it from just few days, then it is surely got to do with the phone trying to fetch data when the signal strength is very low. I found out that -113dbm is the least signal possible and the phone displays a '+' mark in the signal status notification bar. Hence when the signal goes to somewhere near -112dbm and -102dbm the phone goes into a reboot.
So if this is your problem, then you need to download "Shutupbatterymanager" from the market and set the phone to turn off data connections when the signal is below a certain threshold. It is also attached in this post below. For example you can slide the signal bar in the app and set it to -102dbm cutoff after which it will disable the data connections. This is one way of solving the issue if you have had reboot problems occur very recently.
2. The best way to solve this issue is to compromise on your 'downgradability'. For me the above option did not work well after a few test runs and then I accidentally found out that flashing this file (thanks to Higgsy for making this) is the best way. Maybe motorola found out the issue after numerous posts in their support forum and has solved it with a change in the kernel. So just download the file and flash the froyo 2.2 GB UK sbf file with your RSDlite.
It would be helpful if someone can post their kernel version. The flashed one after using this file that seems to solve the problem is [email protected] #1
Hope it solves all your reboot issues. Google you can please index this for some much needed help for desperate Defy owners.
Thanks to: Higgsy and Sorensiim
PS: Important point i forgot to mention is that the change in the kernel is reflected when you get into recovery by holding Vol down + power button. Here if you are on newer and changed version, touching the corner of screen does not work. Instead pressing the volume rocker simultaneously up+down will enter recovery functions.

Substantially is the UK 3.4.2-117 sbf that have you flashed?

alezzandro said:
Substantially is the UK 3.4.2-117 sbf that have you flashed?
Click to expand...
Click to collapse
Yes, but it is not the complete sbf. Some segments have been knocked off and it has been repacked by Higgsy so that there is no locked bootloader and downgradability problem.

Which means the complete SBF already has this fix built-in?

Yes it should.
Sent from my MB525 using XDA App

okidoki - thanks good to know

I would verify the change by going into stock recovery.
Sent from my MB525 using XDA App

How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?

OK before I get confused with the build numbers do this. Power off phone and boot with power button and volume down. Once recovery appears tell me if you are able to enter recovery using the corner of the screen or is it through pressing the volume rocker up and down simultaneously.

It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.

mrt3k said:
It works by pressing the volume rocker up and down simultaneously and NOT by a tab in a corner.
Click to expand...
Click to collapse
OK then you are already on the newest froyo kernels and not on the eclair ones which had the problem.
Now tell me, is your rebooting problem still there?. When do you face it? What is your observation?.

i think if you are using pays rom, then you must've flashed the whole sbf already. you don't need to flash this partial old sbf, since the new sbf should include the old fix (of course some assumption here, hehe) you probably can't downgrade using official sbf either...
mrt3k said:
How about if I do still have the problem with Pay'S Rom (3.0/3.1) that is based on: 3.4.2_145-003 Motorola SBF.
I cant flash the sbf file that you named because its older I think. Right?
Is there a chance of getting a cleaned and fixed version of the 3.4.2_145-003 Motorola SBF?
Click to expand...
Click to collapse

Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.

mrt3k said:
Yes I flashed the most recent kernel, as I mentioned before.
Well, the reboot happens just spontaneously some times a day and also often when a calls or an SMS comes in. But not always, usually only when the phone has not just been rebooted but is still switched on for some time.
But for now: I changed the sim card (from T-Mobile Germany to Base/Eplus/Germany - jus for testing) and afterwards there was no reboot for 12 hours. So maybe the reason is the sim-card, thats my idea at least. But with the Sim-card I want to use on a regular bases, the T-Mobile one, I did have the reboot problem even with the newest kernel.
Click to expand...
Click to collapse
OK then. Continue your observation on the sim card and come back again to report if this occurs again. All the best.

Ok I will do so. Thanks for your help!
But apart from the hint on the sim-card (which is not yet proven) - Any idea? Do we know that the brand new kernel does not have the error anymore? Or could it still be part of the release if Moto did not realize and fix it?
So, do you see any other thing that could cause all the reboots?

Every rom out there has ways by which you can still maintain downgradability. I did the same. I loaded chinese sbf and then tried various roms by restoring it by nandroid backups. Also people like jboogie and higgsy give boot only and safe sbfs which can be tried. For me flashing the above attached sbf from higgsy and restoring the rom posted by Iaoa PL deblur solved the problem totally.
Sent from my MB525 using XDA App

Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!

mrt3k said:
Strange thing, without any further changed to the system, no update or so..... suddenly there are no reboots anymore. The problem seems to have been solved - at least no reboot for nearly a day so far.
What i just did: Removed the SIM, put another in, later changed again. Also: Put out SD-card, formated it again (standard sector size - was 32byte before) and put all files back on the card and inserted it again.
I also uninstalled JuiceDefender.
Well, either its total random or one f the above mentiond changes whatsoever solves the problem. I hope it'll stay like this now - I'm happy than!
Click to expand...
Click to collapse
Yeaaah, thats some good news. Enjoy your Defy

After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?

mrt3k said:
After 100h of perfect work of my DEFY, I rebooted it - and what happened? After this, the reboot problem! Same thing than before!
Spontanious reboot and reboots when a call comes in!
What I also observed: after some reboots, the Defy does not find any services, "only emergency calls possible". Could that be a hint?
Click to expand...
Click to collapse
This is exactly the same problem I had. Why dont you do this. Flash the new poland leaked sbf and then restore nandroid backup from Iaoa. He has a rom for the same poland version.
This solved my problem. Hope it works for you too.
And please remember that you can get back to 2.51 roms and nothing below that if you flash this sbf.

Related

Help, can't flash 'fixed' sbf files except for one. Telstra Au MB525.

I just tried to flash the Telstra (Australia) SBF. No info comes up in file properties and it gives an instant 'failed flash' message.
I am a bit stuck- i can only flash the China Froyo and the GB Froyo, the only 'Fixed' SBF I can ever flash is the 2.2GB_NoCG_31_39.sbf -(Higgsy fix). The China rom is the first and only Froyo rom I flashed with the above fix.
1a. :I want to know why I cannot flash 'fixed SBF's' that come with JBoogie, ADXLmod, barebones etc roms.
1b :Why do I still have to use the 'Higgsy fix' 2.2GB_NoCG_31_39.sbf? It appears that I am somehow locked to it.
1c :Is it because of the Telstra rom I am on- with all rom flashing instructions, it is mentioned eg 'if you are on 2,21 or 2.34 fw etc- no reference is ever made to the 2.26 fw.
2: I want to know how flashing a rom without the corresponding SBF actually affects the operating of the rom- eg: I get random reboots, black screens, freezups=- is this likely an issue with the rom or because I cannot flash the fixed SBF.
3. Will restoring a Telstra nanodroid on top of the China Froyo SBF that I am running, then applying the fixed Telstra SBF that racca graciously provided make my Defy exactly like stock- or will there still be remnants of the China Froyo etc rattling around under the hood and potentially affecting stability and continuing to affect my ability to flash fixed SBF's as per Q 1 & 2.
4. Does anyone have a FullTelstra SBF that works unlike the one already posted on XDA.
I have tried renamimg and moving sbf to root folder as per a suggestion for 64 bit windows, though i am only on 32bit, it didn't work for me- 'start' is still greyed out in RSDLite..
I have also tried different rsdlite versions.
I welcome any other suggestions or questions.. At least I would like to know what is going on and how it affects my phone as I have spent hours and hours searching these and other forums and am none the wiser..
Cheers
Gavin
Accidental 2nd post-ignore.
what exactly are you trying to do?
i can't make much out of your long and pointless statements.
be specific about what you need, then maybe we can help.
all i can understand is that you might want the fixed sbf, so here it is.
http://mir.cr/6MJBVDCN
Thanks for that, pointless is a bit harsh though, long maybe- i was trying to give some background to prevent 'have you tried that, just do this- when it is clearly not applicable to my situation.
I will try to put it in point form.
I hope that is a bit clearer, but it is a complicated situation- there are alot of threads dancing around similar themes, but I cannot find specific answers to these questions- i can't see how I could provide less information without having 5 pages of people directing me to posts that I have already looked at but aren't applicable, so yes it is a bit long, but by doing this much misdirected effort is saved by myself and those helping.
Thanks again
Looking at my original post again, it was hard to see what I was asking, thanks racca.
I just restored the Telstra factory reset nanodroid- the start button was greyed out with the Telstra SBF , so i can't use it. Had to use the 'Higgsy fix' to get it to boot. Weird, i just don't understand it.
To be honest, with all the eventual issues with any rom i use, i would prefer to go back to stock (i will have to put up with the grey status bar, short battery life and no flash). I am tired of getting crashes at the most inopportune times.
Can't wait until the bootloader is fully cracked- I have put Gingervillain (CM7 base) on her Desire, which is much more stable than any rom when i was using it.
Update- it just won't boot now, have to reflash the China Froyo SBF, looks like I am stuck with daily @ 3x daily reboots, bluetooth that works 60% of the time, dropped calls etc....
Change SBF file name
Hey there,
I kinda have the same issues as you do, I think...
The RDS lite gave me an instant ROM-flash error when trying various SBF's. I simply renamed the file name to an SBF file name that was working, yes it got a little confusing... first I renamed the original working SBF to *.old.
Suddenly the flash process was working, I've renamed SBF-files on 4 different occasions in order to get it to work.
I'm not quite sure whether you have this issue or you have something different going on, but feel free to try it.
//Dave
Sounds like a plan, I will give it a go. Thanks.
Thanks Dave69 and Racca, i just renamed the TElstra fixed sbf to the higgsy fix; restored the stock nanodroid and flashed it and it worked. It at least gives me the confidence to flash others now, but will sit on this for a bit- don't have time for more tinkering this weekend.
Titanium wouldn't work with the Telstra rom- said it had restored apps, but wouldn't restore evn one.
Thankfully I got Barebones running, SBF and all. Looks great. Thanks guys.
I would still like to know what's going on though, I haven't tried the TElstra full SBF with the rename yet- it had a different issue than others- just failed. May try again later.
Sounds like you have the same problem as me, was on the telstra on. Not being careful enough I flashed a non downgradable 3.4.2_155-002 sbf. So now I can't downgrade back to the stock Telstra one. I have tried both nandroid backups and flashing the stock telstra sbf and neither work. so am stuck on this rom running JBoogie GingerBlur
Not compaining, for a blur rom it is quite fast, only thing is I can't downgrade back to telstra if the phone needs to be returned for anything.
Hope this helps.
Cheers.
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
superfastmonkey said:
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
Click to expand...
Click to collapse
ok, now where do i begin. i'll just say what i can think of instead of answering every single question.
sbf's contains various code groups as you may noticed while flashing it slipts into smaller pieces.
out of those, cg31&39 are non-downgradable and the pair of them must match. all other partitions on the phone are either not flashed by the sbf (e.g. bootloader/mbmloader, pds), useless (cdrom) or downgradable (kernel, recovery, lbl, devtree).
there are no hardware incompatibilities except the chinese ones, but if you don't update cg31(cdt) to match your /system(cg39) you might have some minor issues (i singles these out because they are not downgradable, of course you'll have issues if you don't match all other things).
you might have a chance fooling tel$tra by flashing the sbf i provided (stock 2.26.0) and restore the nandroid. it should be almost identical except you'll get busted when they try to do flash their service sbf.
the bottom line is,
1. if you flashed any sbf larger than 50MB it must have cg39 in it, and you can't downgrade.
2. you must use matching kernel/devtree with the system: the chinese ones will not be compatible with any other roms, you can't mix match froyo with eclair.
Thanks racca, it makes things a bit clearer. I didn't think I had flashed the GB rom, but I must have-it was 3 or 4 mths ago- it explains why I used the Higgsy fix...i think the China one came out very shortly after..
I should probably try flashing a 2.1 rom b4 restoring the telstra nano if I want stock-( with Telstra, we will have to wait until 3 mths + after the rest of the world gets Froyo for them to fill it to the brim with bloat ware..)..
It looks like the Higgsy fix didn't work for our devices anyway-i suspect my phone believes it is a 3.42 fw now.
In any case, I am relieved to have a way to flash the fixed sbf's now.. Barebones is very impressive, no hint of an issue, but need to run it for a week to really see.
Thanks.
I have a Telstra phone too and after a week of owning it back in January, I had already installed a 2.2 De-blurred ROM. I did have radio issues at first and also remember a non-stop reboot issue. I think it was the USB debugging somehow but I could be wrong.
Now I install new ROMs with ease when the need strikes me.
Are you able to flash the fixed sbfs for roms you install?
I've just put the CM7 rom on mine, best rom I've used. Also flashed a fixed rom with it.
Next thing i tried was restoring a nandroid backup of the default telstra rom, then flashed a fixed stock telstra sbf, this worked and was able to at least make the phone look like it was stock. Whether or not that would be enough if i had to send the phone in for repairs. Can only try if it needs to go in.
CM7 is by far the fastest rom I've tried. Only used for a day so far and no problems yet. Highly recommend this one.
Cheers
Sent from my MB525 using XDA App
I flashed the fixed sbf by renaming after restoring the telstra nano and it worked, but didn't run properly, I did it a couple of months ago with just the nano after having jboogies blurless ginger and it passed for warranty. Haven't tried renaming the full telstra sbf yet. I might over the long weekend.
Sent from my MB525 using XDA Premium App
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
samorgs said:
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
You'll be fine.
On a side note, it's ridiculous that Optus have official froyo already, Telstra due in July.
Sent from my MB525 using XDA Premium App

[Q] Logcat for developers: Switch on 3G network = reboot loop

Every time I turn on 3G network, I get a reboot loop. Here my logcat:
http://content.wuala.com/contents/jgmoreno75/Motorola Defy/Logcat turn on 3G network.txt
I do not know if it's hardware problem or software. I changed my Rom (eclair, froyo and ginger), always with the same result. I always wipes
I need help, please
Thanks.
I am not a developer but have been dealing with reboots from quite sometime. I have created many posts but ultimately had to solve it myself due to lack of interest from developers to even analyse this problem.
Now I use CM7 and there is no way to deal with this problem. I can confidently tell you that it happens only when 3G is ON and the signal strength measured in dBm is very low. So when you move into low signal area the 3G tries to get data and suddenly jumps into reboot.
This is my observation.
jgmoreno75 said:
Every time I turn on 3G network, I get a reboot loop. Here my logcat:
http://content.wuala.com/contents/jgmoreno75/Motorola Defy/Logcat turn on 3G network.txt
I do not know if it's hardware problem or software. I changed my Rom (eclair, froyo and ginger), always with the same result. I always wipes
I need help, please
Thanks.
Click to expand...
Click to collapse
chaihg said:
I am not a developer but have been dealing with reboots from quite sometime. I have created many posts but ultimately had to solve it myself due to lack of interest from developers to even analyse this problem.
Now I use CM7 and there is no way to deal with this problem. I can confidently tell you that it happens only when 3G is ON and the signal strength measured in dBm is very low. So when you move into low signal area the 3G tries to get data and suddenly jumps into reboot.
This is my observation.
Click to expand...
Click to collapse
do you use original baseband?
if not - try to revert to original (or the closest) baseband.. then report if it helps
I am sure that you only don't get help because your problem is rare. And if a problem is not reproducable it is hard to get solution for it.(like mine was with the adata SDcard) I suggest you to flash back your original firmware but as i see you are on leaked GB. And the only thing i see that it is kernel panic. Can you send a dmesg? (but i am almost sure it is hardware related)
Sorry, I was out of my house. I tell you how it all started:
I had installed CM7 (some nightly) with baseband by default (T-Mobile I think). I was in a place with poor coverage and I decided to first use the apk Baseband Switcher v4 (not backup my baseband before). I chose Central Europe RT 2.34.0 and I got top coverage, but from that moment began continuous reboots when selecting 3G network.
I did a nandroid restore to another nightly, but still the same thing happening.
Then I flashed almost everything (eclair, froyo, ginger, mods,...) and I still have the problem.
I have also tried other SIM from other operators (my Defy is unlocked by IMEI)
Here I upload my. /adb shell dmesg:
http://content.wuala.com/contents/jgmoreno75/Motorola Defy/dmesg.txt
Thanks for your answers.
P.S.: I also suspect the hardware.
P.S.: Sorry for my bad English.
sorry seems like i am not enough for this i cannot figure out the exact cuse of the restart but seems like baseband related. Can you restore the original basband the phone came with? or set the us baseband? or try a couple setting in service menu *#*#4636#*#*?
vick33 said:
sorry seems like i am not enough for this i cannot figure out the exact cuse of the restart but seems like baseband related. Can you restore the original basband the phone came with? or set the us baseband? or try a couple setting in service menu *#*#4636#*#*?
Click to expand...
Click to collapse
I have not the original baseband. With U.S. baseband problem persists. What settings do I change the menu * # * # 4636 #*#*? I've tried GSM Only and GSM auto prl too.
Enviado desde mi MB526 usando Tapatalk.
www.wuala.com/jgmoreno75
then you have tried everything. The only thing i can think of is to go back to spanish stock froyo factory reset no root no apps.
if it still no good install baseband swicher and try every baseband.
If still not good unroot and return to shop.(if i have the wrong baseband my phone does not freeze or reboot just eats the battery and no coverage at some places)
Ok, I'm going to do it now!
Thanks.
Enviado desde mi MB526 usando Tapatalk.
www.wuala.com/jgmoreno75
and remove the sd card too while trying so if it will rebot then it can be nothing else but the phone and in the shop they can reproduce the problem immidiately
Ok, I did it before and also format the SD Card, but I'm going to do the same again.
Enviado desde mi MB526 usando Tapatalk.
www.wuala.com/jgmoreno75
... looking for original banseband ... without success for now. I tried with a nandroid (only system) of the Spanish Froyo but the problem persists.
At the end I'll choose to leave it as GPS for the mountain bike and buy another more reliable brand (Samsung, HTC,...)
This was my attempt at solving the issue.
http://forum.xda-developers.com/showthread.php?t=956659
If I remember right then roms from Ioao were actually found to be good and I did not find reboots.
Changing baseband did no help. My logcat clearly showed decrease in signal strength and then reboot. I can reproduce it in elevators and low signal areas.
Even Motorola service did not know why and how it happened. I got a new phone but then the problem persists. Now I have been able to reduce it somehow but still manage to get 2 reboots per week.
chaihg said:
This was my attempt at solving the issue.
http://forum.xda-developers.com/showthread.php?t=956659
If I remember right then roms from Ioao were actually found to be good and I did not find reboots.
Changing baseband did no help. My logcat clearly showed decrease in signal strength and then reboot. I can reproduce it in elevators and low signal areas.
Even Motorola service did not know why and how it happened. I got a new phone but then the problem persists. Now I have been able to reduce it somehow but still manage to get 2 reboots per week.
Click to expand...
Click to collapse
I'd seen this post. thanks, but if I flash the SBF my Defy will not start. I need a nandroid backup and then build my own fix-firmware (this is easy)
I also tried the apk, but without satisfactory result.
I have the same rebooting problems, curious to know the root cause of the problem.
Sent from my MB525 using XDA Premium App
ATXiceman512 said:
I have the same rebooting problems, curious to know the root cause of the problem.
Sent from my MB525 using XDA Premium App
Click to expand...
Click to collapse
I have this problem from the time I installed the Rom (2.1, 2.2, 2.3.4). Without installing any application.
jgmoreno75 said:
I have this problem from the time I installed the Rom (2.1, 2.2, 2.3.4). Without installing any application.
Click to expand...
Click to collapse
Then now i almost sure it is a hardware problem take back the phone i am sure they will replace it.
I'm afraid so. It does not matter, to the bike hehe!. No warranty.
Thanks for your help.
Enviado desde SGS i9000 usando Tapatalk.
www.wuala.com/jgmoreno75
Is it possible to change the voltage of the processor without any application? A partner of the forum HTCMANIA is using setvsel.apk in the Rom 2.3.4 134 (my current), but when I start the application restarts my Defy. I suspect that when I was with CM7 Nightly, the processor is kept low voltage. Is that possible?
Enviado desde SGS i9000 usando Tapatalk.
www.wuala.com/jgmoreno75
yes you can do that in bootmenu.

Think My Baseband is DONE FOR!!!

Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
can you install a stock rom back onto it? There is a baseband selection mode that you may have to do.
http://forum.xda-developers.com/showthread.php?t=1116884
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
Ive had to run this a few times depending on radio and rom.
after many trials I am sticking with rooted stock.
Wow that is defiantly a menu I have never seen before.
It doesn't let me select any of the preferred carrier option. When I tap on GSM auto (PRL) it just closes and defaults back Unknown.
It's ded?
Sent from my HTC Phone
thepyro6 said:
It's ded?
Sent from my HTC Phone
Click to expand...
Click to collapse
Ya, I think it is. RIP Nexus S. HTC Sensation here I come.
after you select gsm auto you hit the menu button on your phone then select the carrier. I know its not labeled what it is on the walkthrough but its similar. not phone frequency but like signal or something. then yuo jsut select usa.
reboot and it should find whatever your service is on its own.
have you tried going back to stock rom? I used this version to go back when i thought i bricked out my phone and its been great. I think my friend used it too but he wont admit he used somethign i gave him.
http://forum.xda-developers.com/showthread.php?t=1060192
http://forum.xda-developers.com/showthread.php?t=1038007
Same issue also involved the trinity kernel. Dev may need to be notified.
kmmxracer said:
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
Click to expand...
Click to collapse
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
No im absolutely sure i flashed the right ROM. Peter Alfanzo was a ROM i flashed after this issue happened. It was the CM7 nightly + Trinity kernel that did me in...
Sent from my Nexus S using XDA Premium App
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Canehdianman said:
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Click to expand...
Click to collapse
have you tried reformatting all your phones partitions?
simms22 said:
have you tried reformatting all your phones partitions?
Click to expand...
Click to collapse
I've wiped user data/factory reset a few times now. Is there a higher-level format option that I should be using?
I thought for sure that going back to stock (based on these instructions - theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/) would work, but no such luck.
I find it perplexing that the baseband shows in fastboot, but nowhere else. *#*#4636#*#* shows radio off and network type unknown, settings/about phone/ shows baseband version unknown.
I tried different methods that I've found online over the weekend, but nothing has brought my radio back.
I am certainly open to suggestions!
I'm going to provide as much additional information as possible.
I have a Nexus S I9020A, running on Fido (Canada).
My initial problem stems from when I updated to cyanogenmod 7.1 from 7.0. My first (and likely biggest) mistake was not making a backup. Oops.
I think I accidentally chose "Nexus S 4G" instead of "Nexus S". As soon as I did that, I stopped getting any cellular voice or data connection (wifi continues to work fine). Under Phone Information, it said it was a Nexus S 4G.
The phone locks itself into airplane mode now. When I try to turn airplane mode off through the settings menu, it hangs. When I hold down power and choose "turn airplane mode off" it seems to work, but then I still get no signal.
I have pushed it back down to stock. It now remembers that it is a Nexus S (not 4G), but it didn't help the baseband problem.
I have tried to reflash the baseband. no effect.
I called Fido and got them to "repush" the SIM card. No effect.
I am humbly appreciative of any and all help that anyone can provide!
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Thanks! This is similar to some other threads I saw on the android forum (and elsewhere on XDA).
I'll try this when I get home (and get to a reliable wifi signal).
Wow! I haven't looked at my post in a wile. Hopefully you all are getting some resolution to these issues. I ended up calling Samsung and they agreed to fix my Nexus under warranty. They replaced some parts that I can't remember off the top of my head, but it should arive at my door tomorrow!!!
Sent from my HTC Sensation 4G using xda premium
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Hmmm bad news... my efs folder appears to be empty. Now what?
A very frustrating day... Thought i would have it fixed pretty quick, alas....
My efs folder is empty. I guess that explains the lack of radio, but it appears that i might need to send the phone to Samsung to get the efs reflashed. Is there a way to write it back myself? Ill look tomorrow i guess.
Here is some more info:
I just tried to update to 2.3.6
Clockwork mod is giving me an error message:
Assert failed: getprop("ro.product.device") == "crespo" || get prop("rp.build.product") == "crespo"
E:error in [filename]
(Status 7)
Installation aborted
Not sure if that helps but it's another piece of thepuzzle hopefully.
*sigh*
So it appears that I need a backup of my /efs folder in order to fix this myself (which I do not have).
I know what my IMEI should be, however I have no idea if it is even possible to take someone else's backup and alter it the proper IMEI.
I fear my next option will be to submit it for repair at a Samsung repair shop (and be without a phone even longer )

[Q] No WiFi

I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Is this issue solved?
Is this issue solved?
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Click to expand...
Click to collapse
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
broadways said:
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
Click to expand...
Click to collapse
The files the OP pulled are for his phone based on the baseband shown. It looks like it may be related to the OTA update that came through recently.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files [edit] [and] my WiFi is not working
Baseband: I847UCLH4
Does anyone have any idea what could be the problem?
Click to expand...
Click to collapse
Did you install the OTA update that AT&T pushed recently before flashing the ODIN images?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kemonine96 said:
Did you successfully apply the ota update that came through for the rugby?
Click to expand...
Click to collapse
VoiceArtistUSA said:
Yes, before any root or flash of course.
Click to expand...
Click to collapse
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
YEEEEE HAAAAWWWWW
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Can't imagine why not a "Full fix".
Thank You !!!!
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Also I'm getting ...
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
kemonine96 said:
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
Click to expand...
Click to collapse
VoiceArtistUSA said:
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Click to expand...
Click to collapse
I'm glad to hear it's working again for you.
VoiceArtistUSA said:
Can't imagine why not a "Full fix".
Click to expand...
Click to collapse
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
VoiceArtistUSA said:
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Click to expand...
Click to collapse
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
VoiceArtistUSA said:
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
Click to expand...
Click to collapse
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
VoiceArtistUSA said:
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Click to expand...
Click to collapse
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
VoiceArtistUSA said:
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
Click to expand...
Click to collapse
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
VoiceArtistUSA said:
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
Click to expand...
Click to collapse
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
kemonine96 said:
I'm glad to hear it's working again for you.
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
Click to expand...
Click to collapse
The lag is a noted issue, along with the WiFi shutting off randomly and intermittently. I'm researching these issues as much as I can to find a fix, but I can only do so much so fast .
I was going to start a new thread but then I found this. I too had the issue with I the wifi turning off and the screen lag. After reflashing the no bloat Odin image and the 1.1 kernel my wifi turns on, but does not find any networks. It just searches then shuts off? Any ideas? I wonder if the stock kernel being worked on would fix this or if there is something else wrong. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I847 using xda premium
I sent the rugby smart to SAM to have it completely reloaded. when it comes back, i will try to make a back up much like i make an image of a hard drive...if that's possible.
For my PC, I have an image of this existing hard drive. If i pull it out and put in a BLANK hard drive, I can write the image to the new disk with all my apps installed...I use that feature often with my pc's and others...for mine, I frequently make a new updated image and delete the oldest one.
Once I change the bootloader, is it possible to get it back if I backed up with with Kies?
You guys are in luck. Kernel1.2 should be out shortly with the lag and wifi fixed . I'm waiting to hear back from another tester, but so far ut's proven stable. I've only had one error pop up, and that was after running pretty hard.
Motorhead1991, Is this for the Samsung Rugby Smart?
How much of, if any, overclocking??
Can you also tweak a non-overclocked version without "City ID" app, "Carrier IQ" app and possibly no AT&T bloatware??
You rock for everything thus far
No overclocking just yet, but I'm giving it hell. On the bright side, Kemonine and myself are currently treading in uncharted territory for this device (see if anyone gets my reference)
And to answer your question, yes it'll be for the Rugby.
iam not sure
thats a good question
Motorhead1991 said:
And to answer your question, yes it'll be for
the Rugby.
Click to expand...
Click to collapse
After a day of use, it seems very stable and even more efficient.
That is great news! Can't wait to test
Sent from my SAMSUNG-SGH-I847 using xda premium
alan2424m said:
thats a good question
Click to expand...
Click to collapse
Yeah, it actually did hurt to ask that one.
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
ESPFreak said:
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
Click to expand...
Click to collapse
When you flashed via ODIN did it show it was flashing the boot area? In the status window it should tell you which images are being flashed to the device. Can you re-try the stock boot/kernel ODIN image and confirm it did flash the boot image?
That is the only thing that booted. As soon as I selected the image I got a "MD5 checksum failed" prompt. The "start" button changed to the same message but it let me click it and it loads the boot.img. Does that help at all?
Sent from my SAMSUNG-SGH-I847 using xda premium

Motorola XOOM Z604 32GB IHDT56MT1

Motorola XOOM Z604 32GB IHDT56MT1
Sorry if there was another thread about this, but i looked and didn't find any
Anyway friend of mine flashed some kinda rom he says official 4.1.1 JRO03H, but i'm not sure
anyway as he said after OTA tab is freezing randomly and gives android keyboard error
so i assumed i can unlock/root and flash some custom rom that will resolve the problem
after using AIO tool and unlocking/rooting/flashing various roms problems persists
sometimes tab is crashing during start up (android loading) sometimes just randomly by touching/using absolutely random
using tiamat recovery 3.2.2 and TWRP, it's rock stable in recovery
so i assume it's hardware related
any ideas, cause i'm out of any
p.s. it does have a sim card slot, but judging by FCC code it's wifi only
p.s. i tried to flash stock rom and lock it, still freezing and crashing randomly, first at wifi menu then at internet browser, guess something is really hardware related, possibly memory got corrupted or something like that
p.p.s now i'm not even sure which xoom this one is, is it a wifi only or 3g and maybe it needs some different stock rom? most confusing tab i've seen so far, there is just so many variation of this
thnx in advance
Mortibus said:
Motorola XOOM Z604 32GB IHDT56MT1
Sorry if there was another thread about this, but i looked and didn't find any
Anyway friend of mine flashed some kinda rom he says official 4.1.1 JRO03H, but i'm not sure
anyway as he said after OTA tab is freezing randomly and gives android keyboard error
so i assumed i can unlock/root and flash some custom rom that will resolve the problem
after using AIO tool and unlocking/rooting/flashing various roms problems persists
sometimes tab is crashing during start up (android loading) sometimes just randomly by touching/using absolutely random
using tiamat recovery 3.2.2 and TWRP, it's rock stable in recovery
so i assume it's hardware related
any ideas, cause i'm out of any
p.s. it does have a sim card slot, but judging by FCC code it's wifi only
p.s. i tried to flash stock rom and lock it, still freezing and crashing randomly, first at wifi menu then at internet browser, guess something is really hardware related, possibly memory got corrupted or something like that
p.p.s now i'm not even sure which xoom this one is, is it a wifi only or 3g and maybe it needs some different stock rom? most confusing tab i've seen so far, there is just so many variation of this
thnx in advance
Click to expand...
Click to collapse
The wifi xoom also has a sim card slot but it does not work( missing the radios).
Can you get into recovery and which one is it (custom CWR or stock)? With the xoom off press power until the moto dual core logo appears then press volume down after 3 seconds. You will see android recovery written on top press volume up. If you still have a custom recovery you can then install 4.1.1 JRO03H again but do a factory wipe (very important to get rid of any possible corruption) before and a cache dalvik cache wipe before.
If you are still having issues you can fastboot the stock honeycomb wifi images and allow the updates to happen automatically but this will wipe all of your data. I can walk you through this.
i did mentioned recovery in my post, otherwise how the hek would i be able to flash it in the first place duhh
i did all that, i even tried stock image 3.01 let it update it all the way up to the 4.1.1 which kept giving me weird android keyboard stopped working error and same random freezes
most stable was honeycomb though, i could stay in the system sometimes longer before touching anything, i even let it on lock screen for an hour or two and wouldn't freeze, in ics and jb it froze on lock screen, sometimes wouldn't even let me pass welcome/choose language
i just don't understand how can it install without any problems and stock/custom recoveries being stable while in OS it's just freezing for no apparent reason, my theory is something wrong with video part of the chipset, then again i simply dunno anymore
i tried several times factory defaults and wiping cache before and after flashing didn't helped
Good luck

Categories

Resources