Hello...
I used the basebandswitcher V4 on my rooted XT720 w/ Froyo 2.2.1, and change the baseband from "unknown" (cellphone bought in South Korea) to Americas baseband (Im located in Mexico which uses 850/1900). When I lost signal I supposed that picked some baseband which my cellphone didn't support, then, I changed it again to Americas Argentina (850/1900)... now It's keeping rebooting with the Motorola logo all the time...
so, after many boot attempts, I used RSDlite to load the original version STSKT_N_79.33.50R, but the cellphone keeps rebooting on M logo...
did I bricked my phone? there's anyway to change the modem settings without boot the phone?
thank you for all
pull your sd card and then reboot. If that doesn't work, try reflashing with sd card out of phone.
Hello reverendkjr, thanks for your reply, as you said, I flashed the phone without the sdcard on it, same result...
do you think that the bootloader is the problem? since I change the modem band values, when the bootstrap is being performed then an error occurs while it tries to turn on the modem or something like that...
my current bootloader is 80.89, do you know any way to change it?...
Thanks again...
I suppose that you cannot enter recovery mode, too?
pajo985 said:
I suppose that you cannot enter recovery mode, too?
Click to expand...
Click to collapse
Hello!, yes I can, but wipe data/factory reset and wipe cache partition, even though are successfully committed it keeps restarting while booting... I can even flash it with any sbf file, I've tried korean, and two from US with same result...
Does anyone changed the modem settings using RSDlite?, there are some parameters that may help in one ini file...
Thanks!
casmol said:
Does anyone changed the modem settings using RSDlite?, there are some parameters that may help in one ini file...
Thanks!
Click to expand...
Click to collapse
Have you tried one of the Milestone XT720 2.1 STR_* sbf's (say the Cincinnati Bell STR_U2_04.1E.1) instead of the Korean Motoroi XT720 2.2 to see if it can restore your phone? I think the sbf include the baseband code. (I use sbf_flash on linux instead of RSD Lite so I can't answer that last part)
Mioze7Ae said:
Have you tried one of the Milestone XT720 2.1 STR_* sbf's (say the Cincinnati Bell STR_U2_04.1E.1) instead of the Korean Motoroi XT720 2.2 to see if it can restore your phone? I think the sbf include the baseband code. (I use sbf_flash on linux instead of RSD Lite so I can't answer that last part)
Click to expand...
Click to collapse
Hello, yes, I've tried that, same result... I think that with the program "switchbandV4" I wrote some registers in the modem flash or something like that, then, when is booting, an error appears and force the reboot until battery drains out.
I think there is a way to reset the modem via RSDlite, in the files pst.ini and pst_flash.ini are several keys like [MODEM_PARAMS], [MOTOMODEM] and TDMA and CDMA related configurations, but I have no single clue of how to do it jeje...
Well... thanks
casmol said:
when is booting, an error appears and force the reboot until battery drains out.
Click to expand...
Click to collapse
What does the error say?
Mioze7Ae said:
What does the error say?
Click to expand...
Click to collapse
No error message, just Motorola logo for few seconds, then reboot and start again with M logo...
have you ever fixed this problem... i did the same thing and have the same problem
not yet...
lNOFXl said:
have you ever fixed this problem... i did the same thing and have the same problem
Click to expand...
Click to collapse
Not yet... I havent go that deep in the ini files, my next try will be to change the boot commands...
pls advice if you find any solution.
good luck
casmol said:
Hello...
I used the basebandswitcher V4 on my rooted XT720 w/ Froyo 2.2.1, and change the baseband from "unknown" (cellphone bought in South Korea) to Americas baseband (Im located in Mexico which uses 850/1900). When I lost signal I supposed that picked some baseband which my cellphone didn't support, then, I changed it again to Americas Argentina (850/1900)... now It's keeping rebooting with the Motorola logo all the time...
so, after many boot attempts, I used RSDlite to load the original version STSKT_N_79.33.50R, but the cellphone keeps rebooting on M logo...
did I bricked my phone? there's anyway to change the modem settings without boot the phone?
thank you for all
Click to expand...
Click to collapse
I read this earlier, but it didn't occur to me that you probably need to factory reset. For some unknown reason, after I flash STSKT_N_79.33.50R, I always have to factory reset. Try this:
Power off phone (i.e. remove the battery)
Press and hold camera and gallery (both) while powering on
When you see the triangle screen let go of the keys
Press hand hold volume up
While holding volume up tap the camera key
Select "wipe data/factory reset" (volume + gallery key to select)
Select "reboot system now"
If the first boot after factory reset hangs on the M, Pull the battery and it should boot through the second time. This always happens to me when using STSKT_N_79.33.50R on Milestone XT720.
STSKT_N_79.33.50R is for the Motoroi XT720 (Korea only) which is actually different from the Milestone XT720. STSKT_N_79.33.50R will boot on the Milestone version, but sensors don't work and there are some other problems.
Sorry, I just realized you've tried that already and you probably do have Motoroi.
yah but im going to try it again just for good measure hahaha thanks
Edit: no different, same boot screen loop
Mioze7Ae said:
Sorry, I just realized you've tried that already and you probably do have Motoroi.
Click to expand...
Click to collapse
jeje thanks for trying to help, I am almost sure that I need to change the modem parameters but I just dont know how...
I'm having the same issue, baseband switch, and now brick. rsd lite flash stock sbf not working.
ideas?
hakkafusion said:
I'm having the same issue, baseband switch, and now brick. rsd lite flash stock spb not working.
ideas?
Click to expand...
Click to collapse
How are you guys changing the baseband?
well its not the way we are supposed to do it obviously its a program for another phone... i only noticed after i did it since i was so excited that i thought i was going to be able to have 3G haha... o well, now we just need a way to get into the kernel to change the radio and change it back to the original files but the problem i think is that we all don't know how to do that
oh and the program is called basebandswitcher V4 .... but like i said.. don't use it(you can only use it from the phone and once you do a restart you cant use the program again since the phone doesn't start back up
lNOFXl said:
well its not the way we are supposed to do it obviously its a program for another phone... i only noticed after i did it since i was so excited that i thought i was going to be able to have 3G haha... o well, now we just need a way to get into the kernel to change the radio and change it back to the original files but the problem i think is that we all don't know how to do that
oh and the program is called basebandswitcher V4 .... but like i said.. don't use it(you can only use it from the phone and once you do a restart you cant use the program again since the phone doesn't start back up
Click to expand...
Click to collapse
exactly what I did.
tried flashing BrightPoint,Cincinnati Bell,South-east Asia,SK Telecom, no work.
I would suggest xt720 users to stay clear of this program.
Related
Imagine you have to send your Milestone to the customer service, would be better if it was "clean" or you want to downgrade it ? Here is how to :
- 0 : What you need : A Windows (sorry ^^), RSDLite and the drivers 32bits or 64bits
- 1 : Choose the right .sbf from here
- 2 : Plug the USB and shut your Milestone down
- 3 : Boot it in bootloader mode (press the D-PAD UP key while pressing the power button)
- 4 : Launch RSD Lite, your device should be in the list
- 5 : Select your .sbf file and click on start ans let it do, your phone will reboot at the end
Here we are, you have your clean Milestone !
This completely un-roots it and everything, right?
chambo622 said:
This completely un-roots it and everything, right?
Click to expand...
Click to collapse
Yes, this wipes everything you have in your phone, including root and/or vulnerable recoveries etc...obviously it doesn't format your MicroSD
how do i know which SBF file to use if my country isn't listed there? (I'm from South Africa) Thanks
dingeth said:
how do i know which SBF file to use if my country isn't listed there? (I'm from South Africa) Thanks
Click to expand...
Click to collapse
Hi dingeth:
1) Are you rooted yet?
2) Where'd you buy the phone from?
3) Are you on the original ROM you bought it with?
4) What do you see under settings > about phone > Firmware configuration version?
There's a chance your phone is actually running the same firmware as another country's. For example if you bought it from Expansys it's probably a UK milestone. In any case, if I read Wikipedia right, UMTS 2100 is the only frequency used in all of Africa. So your phone might be like the Euro/most-of-Asia 900/2100 version, but it could also be like the CDN/Thai/LatAm 850/1900/2100 version. You won't lose 3G from flashing the wrong one because they all have 2100, but you'd be best to stick to the closest one you can.
Now - if your phone is still in total stock condition, unrooted, then you have the opportunity to make a nandroid backup of the original state. Go to the root instructions using OpenRecovery. When you get to the stage where you're in the OpenRecovery menu, before you go and root the phone, make a full backup. Make two in fact - one with data, one without. And copy it somewhere safe.
Does this also reset a custom rom??
lg
Masterchief14 said:
Does this also reset a custom rom??
lg
Click to expand...
Click to collapse
Name your favourite custom ROM for the Milestone and we can answer your question.
(tumbleweed)
Oh right, there are no custom ROMs... only highly customized images that are still piled on top of the stock ROM.
cmstlist said:
Hi dingeth:
1) Are you rooted yet?
2) Where'd you buy the phone from?
3) Are you on the original ROM you bought it with?
4) What do you see under settings > about phone > Firmware configuration version?
There's a chance your phone is actually running the same firmware as another country's. For example if you bought it from Expansys it's probably a UK milestone. In any case, if I read Wikipedia right, UMTS 2100 is the only frequency used in all of Africa. So your phone might be like the Euro/most-of-Asia 900/2100 version, but it could also be like the CDN/Thai/LatAm 850/1900/2100 version. You won't lose 3G from flashing the wrong one because they all have 2100, but you'd be best to stick to the closest one you can.
Now - if your phone is still in total stock condition, unrooted, then you have the opportunity to make a nandroid backup of the original state. Go to the root instructions using OpenRecovery. When you get to the stage where you're in the OpenRecovery menu, before you go and root the phone, make a full backup. Make two in fact - one with data, one without. And copy it somewhere safe.
Click to expand...
Click to collapse
Hi cmstlist
yes I am rooted. I used the rooting procedure desribed using aumkar's method with the vulnerable recovery and RSD Lite.
I received the phone on contract (MTN) and the firmware configuration version says:
GAS_EMEA_USASHLS00RTINT_P012 and Build SHOLS_U2_02.31.0
I was thinking of trying the U.K SBF for 2.1 coz it also has the same build number?
too late for the nandroid backup since it's already rooted. everything works fine though, rooted it to overclock which works 100%!!! Nut i'm wondering if i'll run into any problems when i eventually try to upgrade to Froyo. thanks again
dingeth said:
Hi cmstlist
yes I am rooted. I used the rooting procedure desribed using aumkar's method with the vulnerable recovery and RSD Lite.
I received the phone on contract (MTN) and the firmware configuration version says:
GAS_EMEA_USASHLS00RTINT_P012 and Build SHOLS_U2_02.31.0
I was thinking of trying the U.K SBF for 2.1 coz it also has the same build number?
too late for the nandroid backup since it's already rooted. everything works fine though, rooted it to overclock which works 100%!!! Nut i'm wondering if i'll run into any problems when i eventually try to upgrade to Froyo. thanks again
Click to expand...
Click to collapse
Interesting! MTN must have released it so recently that nobody has located the SBF. EMEA means Europe, Middle East, Asia... so it's probably UMTS 900/2100. Don't forget to take a nandroid backup now before trying anything - because you may have no way to get back to your original carrier's firmware.
Also if anyone else on your carrier buys a Milestone and is looking to root, suggest that they make the backup before rooting. Then there will be a master copy.
EDIT: That string is mentioned in this post:
http://androidforums.com/all-things-root-milestone/75460-milestone-2-1-update-root-guide.html
and the following file name is posted to match:
SHOLS_U2_02.31.0_UCASHLSMR2EMEAB1B805C.0R_PDS003_USASHLS00RTINT_P012_A011_HWp2a_Service1FF.sbf.gz
The SBF in question is not listed yet on and-developers but it's on Motorola's site:
https://rsddownload.motorola.com/do...SHLS00RTINT_P012_A011_HWp2a_Service1FF.sbf.gz
And the non-service version (full wipe when you flash it) is here:
https://rsddownload.motorola.com/do...003_USASHLS00RTINT_P012_A011_HWp2a_1FF.sbf.gz
Good luck!
ok so i made the nandroid backup
last question: should i use the service or the non-service .sbf?
what are the differences, and which one do you recommend?
thanks
dingeth said:
ok so i made the nandroid backup
last question: should i use the service or the non-service .sbf?
what are the differences, and which one do you recommend?
thanks
Click to expand...
Click to collapse
As far as I know, the only difference is that the service SPF doesn't do a wipe.
Yep, the only difference is a non-service doesn't do a wipe
Ok awesome, thanks for the help
Well if you want everything to be wipe out than a non-service sbf should do the job but a wipe/data reset via recovery console is also recommended for ultimate clean state.
So I guess a non-service sbf is a total wipeout but service sbf leave something intact which I have no idea. I have been using non-service sbf to root and unroot my milestone hence I have no idea what the service version do.
to delete, i type post in wrong topic, sorry.
This may be useful if we have supposedly brick'd Milestones.
Coburn64 said:
This may be useful if we have supposedly brick'd Milestones.
Click to expand...
Click to collapse
need optus dump still
does it clean the SD too?
If not, how to do this ?
No, it doesn't. To do it, on you Androphone, you've have to go into Setting, SD Card and Memory, Desactivate the SD and then format it (maybe not the right label, mine are in French, but should be close).
I am from israel and I so celcome's sbf, but it says the alarm isnt working, does it contains celcomes hebrew?
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
after remove all files in /pds, rm -r /pds/*
my defy keep to reboot loop.
power on, the screen show the motorola (M) logo, after few second, then reboot.
i can go to bootlooder mode (power + sound up),
or go to wipe data/cache (power + sound down).
and i can flash sbf with rsdlite.
after tried all still keep boot loop
(full power changed 100%)
i tried reflash few different sbf rom
3.4.2-155, 3.4.2-133, 3.4.3-11
i'm sure all sbf rom work fine before.
i did flashed those sbf rom a few times, and all is work.
anyone know why keep reboot loop?
and how to solve it?
what is /pds/* files for?
please help, and thank you.
This was not a good idea. I think someone here on XDA (Tenfar) already tried to remove /pds and his Defy is dead now. Present sbf files probably do not include /pds.
peetr_ said:
This was not a good idea. I think someone here on XDA (Tenfar) already tried to remove /pds and his Defy is dead now. Present sbf files probably do not include /pds.
Click to expand...
Click to collapse
OMG, my defy is dead?
How can it be... you did wipe before sbf flash?
Why did you deleted these files?
Sent from Barebones-Defy using tapatalk.
johnw.xda said:
OMG, my defy is dead?
Click to expand...
Click to collapse
yep is dead , pds is Phone Descriptor Security and you delete IMEI number
http://forum.xda-developers.com/showthread.php?t=988115
Try to flash the bootloader the sbf files you can find in the forum then it should work if it does not flash with the latest sbf file then it had to work otherwise. My defy had many bootlops and do not start but i got it to work Sorry for my englisch my defy is alive ;-)
Send from my brain using Tapatalk
here the bootloader i used http://uploaded.to/file/ofcxbyhj
dumrul said:
Try to flash the bootloader the sbf files you can find in the forum then it should work if it does not flash with the latest sbf file then it had to work otherwise. My defy had many bootlops and do not start but i got it to work Sorry for my englisch my defy is alive ;-)
Send from my brain using Tapatalk
here the bootloader i used http://uploaded.to/file/ofcxbyhj
Click to expand...
Click to collapse
i did it, but still not work.
thank you.
wipe you phone
turn device off
vol down and power
you should see an android with a ! mark
press on the bottom left or right (im not sure)corner until you see an option to wipe
reboot
hope it helps
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
have you tried re-flashing with a full sbf instead of a fixed sbf? also, try to make sure your RSD lite is the latest version
sunoldman said:
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
Click to expand...
Click to collapse
i can not use those tools to repack it with CG38.smg
MotoAndroidDepacker.exe
MotoAndroidDepackerMono.exe
SBF-Recalc 1.2.9.1.exe
did you tried it? (repack sbf with CG38.smg)
thank you.
anyone can share /pds/* files to me?
maybe use bootloader recovery/update.zip, can copy those files to /pds
thank you.
Sorry for that, I can't do that either. Maybe it really needs to be back to factory.
I send back to factory on Saturday , and get back today.
they say need to replace another mainboard.
free of charge, good service.
thank all, thank moto.
I live in Hong Kong.
sunoldman said:
Try to use SBF depacker to incert CG38.smg to sbf file and reflash it,
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
USE AT YOUR OWN RISK
Click to expand...
Click to collapse
This idea maybe work.
Thank god, you are lucky.
So I just received a replacement phone via warranty from T-Mobile.
I have upgraded to Gingerbread 2.3.6 and am rooted.
I just realized now that the IMEI number in Android is 00000000.
I'm not sure if it was like this before I started tinkering with it or if it happen as a result of the root/upgrade.
Anyways, I have the sticker that gives me the IMEI number under the battery, I just need to know if/how I can get this back into my phone. I've read something involving a HEX editor? But I don't know what or how.
Any advice and links would be greatly appreciated.
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
CoBfan1987 said:
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
Click to expand...
Click to collapse
Did you make any backups before upgrading to Gingerbread 2.3.6?
ADD: Here is a quote off another thread with this problem:
I got my IMEI back. I had my nv_data.bin.md5 and nv_data.bin backed up when I unlocked my phone after I got the new one from Samsung. I just coppied them the the efs folder and my IMEI is back."
Hope it helps! And hope you have a back up... maybe even from your other phone?? Or before you upgraded the phone you have.
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
CoBfan1987 said:
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yes.
10char
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
CoBfan1987 said:
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
Click to expand...
Click to collapse
First - Is your phone working?
Second - Have you tried a factory reset if your phone is working?
Third - Try a factory reset and reflash a stock rom.
Fourth - If you phone is not working give it a shot and let us know
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
CoBfan1987 said:
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
Click to expand...
Click to collapse
What I have read is a factory reset or reflashing a ROM (or both if all else fails) should restore your IMEI. I have also read flashing the original ROM that came on the phone has worked. You may try that if the factory reset does not restore it.
Since your phone is working don't copy the files over from your other phone
Do let us know your progress.
How do I obtain the original rom, is it posted here in the forum?
CoBfan1987 said:
How do I obtain the original rom, is it posted here in the forum?
Click to expand...
Click to collapse
Did you do the factory reset yet?
resetting as we speak. Report back in a sec
okay reset is done and IMEI is still 0000000000
CoBfan1987 said:
okay reset is done and IMEI is still 0000000000
Click to expand...
Click to collapse
Try doing the factory reset again and flashing back to froyo
http://forum.xda-developers.com/showthread.php?t=1106822
assuming the was what came with the phone?
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
CoBfan1987 said:
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
Click to expand...
Click to collapse
What color is your recovery?
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
CoBfan1987 said:
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
Click to expand...
Click to collapse
You need a custom kernal to flash from CWM. That is why you are getting that error. Let me look for an odin flash back to froyo stock for you.
On a side note - I have read taking your battery out for 10 mins has worked for some. Since your phone is working you may try that while we continue to look for a fix.
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
CoBfan1987 said:
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
Click to expand...
Click to collapse
I say before going back to froyo try raver's ROM-ODIN-2.3.6-Gingerbread Offical Maybe a stock reflash will work. I have read a thousand ways that have work for different people now. You have done a few. Try this as it is easier than going back to froyo for now. Let your battery charge first.
Maybe kies just f-ed up your imei. And where are the big dog's when you need them? bhundven/FBis251?
Did you just root? Or did you use an app to unlock your phone as well?
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
First of all your phone is fine, since it is booting. You can continue to choose normal power up and be fine.
To fix you need to flash the fxz and replace the files to allow you to do it after being on 2.3.6. see here http://forum.xda-developers.com/showthread.php?t=1396650
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
biupil said:
unfortunately i cant flash the fxz it says failed all the time, its like its locked, i tried.
Click to expand...
Click to collapse
did you replace the files
Sent from my MB865 using xda premium
yes my friend and this is what it says
biupil said:
yes my friend and this is what it says
Click to expand...
Click to collapse
hmm. Is your phone the AT&T version or one of the international ones? Make sure you are using the correct fxz file for your device, that is most likely the problem with the step it is failing on find a list here: http://sbf.droid-developers.org/edison/list.php
Go to settings- about phone and look at system version. That should tell you what version you are. it will be 55.13.25.MB865.VERSION.... or something like that, you should be able to tell which you are
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
biupil said:
it is At&t
system version 55.11.16.MB865.ATT.en.US i have downloaded the
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.Zip that is for At&t is that correct?
Click to expand...
Click to collapse
yep that is the correct one. have you ever tried to flash a different one? that may have messed something up.
Try this, it may work. It is just a script that runs the fastboot comands. Extract it and run the stock restore file in it:
https://docs.google.com/open?id=0B_F787JD56X9SjZSUlljQ2ZYdFk
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
biupil said:
yes i have tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc as i said before. I will try the one that you told me and i will inform you...
Click to expand...
Click to collapse
that is probably the problem. there are some files you will have to skip flashing in order to make it work I think. PM jimbridgman (i think thats how you spell it and ask him for help)
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
biupil said:
nope still the same lets hope that jimbridgman can help
lkrasner thank you for your time.
Click to expand...
Click to collapse
he should be able to just link him to this thread and be nice.
I also just replied to your PM, but I wanted to put this here as well, so others can also see it.....
This just a theory, since no one has done this yet, so we might have to try a few things to get it right
my first guess is to do this:
Take the following files from the update that you flashed and replace their counterparts in the 2.3.5 fxz, and update the md5 sums in the xml file, you can google for a windows md5sum executable for windows.
Here is a link to a good place to find the m5sums for windows7:
http://www.walkernews.net/2009/12/26/how-to-check-md5-checksum-in-windows-7/
files you will need from the leak:
cdt.bin
device_tree.bin
lbl
now once you have them in the same folder as the rest of the 2.3.5 fxz, use that exe I told you grab to get their md5 sums, and replace those numbers in the xml file in the 2.3.5 fxz, this should get you back to 2.3.5, in theory.
Jim
wtf my brain hurts already lol. I will try to do it in the morning i will inform you for the results.
i realy understand nothing at all of this. unfortunatly my phone will stay as it is.
biupil said:
I have a problem with the power button i push it and this is what i get
AP Fastboot Flash Mode (S) (Flash Failure)
0A.68
Battery OK
OK to Program
Connect USB
Data Cable
But with vol-&+&pwr button i choose normal mode and it works just fine.
The problem is tha i cant fix it with rsd lite + InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.
So if i want to get an update it will try to reboot and will not start up to setup the update
I have even tried the Blur_Version.55.28.37.MB865.MERetail.en.06.andcrc but still nothing.
Atrix 2 At&t sorry for my english
Click to expand...
Click to collapse
download the fxz and replace files from noob thread. extract and replace files, after replacing erase third line
i.e <step operation="flash" partition="mbmloader" filename="mbmloader.bin"MD5="9D1958ED3F5E971FF079B195E338BA86" />
from InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.xml and flash it using rsd lite it will definetely work as i had the same problem
thanks man i just love u my phone works perfectly