Hi everyone, new user and post, unfortunately prompted by a problem (aren't they always!).
I have just received a slightly used Motorola Razr (Optus branded) that, unfortunately, is stuck in a bootloop and restarts every 30 seconds. Neither a hard reset nor safe mode fix the problem, although I am able to access recovery mode.
The seller is adamant that the phone was working perfectly, that they did not flash, root or otherwise mess with the firmware and only performed a hard reset, and that they have since called Motorola, who have told them its a well known issue fixed by a firmware update.
While its nice that Motorola is no nonchalant about their hard reset bricking phones, I am rather a little more annoyed and so have turned to the good community at xda developers for assistance.
I am aware that firmware can be updated using Motorola's tools, however I cannot find any Optus branded firmware or updates in the rom list. My questions are:
1) Can anyone confirm that this is a common problem fixed by a firmware update?
2) Does anyone know where to find Optus branded roms?
3) If I flash with a non Optus rom, what are the consequences for the phone, my warranty and ability to receive Optus updates?
4) What would the good people here do? Try to fix the problem? Claim under Optus/Motorola's warranty? Send it back to the seller?
Thankyou all for your time and any assistance!
i had same problem, im aussie with optus 2, unfortunately i lost mine too, but if u fastboot flash the europe/australia fastboot file in the stickied rom thread, that works, cause it worked for me.
royalbloodvi said:
i had same problem, im aussie with optus 2, unfortunately i lost mine too, but if u fastboot flash the europe/australia fastboot file in the stickied rom thread, that works, cause it worked for me.
Click to expand...
Click to collapse
I'm actually not even with Telstra, but wanted to keep the phone stock.
Have you noticed any differences between the Europe/Aus unbranded ROM and the original Optus one? Will Optus still honour your warranty?
irR4tiOn4L said:
I'm actually not even with Telstra, but wanted to keep the phone stock.
Have you noticed any differences between the Europe/Aus unbranded ROM and the original Optus one? Will Optus still honour your warranty?
Click to expand...
Click to collapse
differences should be, that there are no more optus-'installed' apps on your phone and that your phone will no more be able to receive the optus udpates (i think so). Cause updates are set on top of the previous system, for example the optus rom you already have.
to your first post:
i don't know if a software update will solve this problem, especially the phone should be running while performing it. there is no common way, to receive the update via pc... no 'legal' way and every carrier support in the world will tell you to do an update, before trying to send it back...
flashing another rom will definitly erase your warranty, unless you don't go back to stock before sending it to your carrier during next problem phase...
but i'm not shure if there's a way to go back to optus stock while having such a problem... and i don't know to, if there are optus roms available right now.
irR4tiOn4L said:
I'm actually not even with Telstra, but wanted to keep the phone stock.
Have you noticed any differences between the Europe/Aus unbranded ROM and the original Optus one? Will Optus still honour your warranty?
Click to expand...
Click to collapse
no differences in functionality, only difference was the pphone was cleaner with no optus bloatware (and you can download the optus account usage & misc apps through the market anyway)
by the way, just for the record, ive sent a razr in that was rooted for exchange, and i still got a new razr, but was stock =)
Well I've now tried two different European/Australian firmware versions and two different methods of flashing fastboot files (RSD lite initially, then the eternity project's fla**** tool). Both seemingly flashed fine, both no longer display an IMEI number, both continue to boot to android then restart after 30-60 seconds.
I'm not sure whether I have warranty any longer and really, I'm not sure I ever did as the seller got the unit as a demo/gift unit from Motorola for review (the unit also displayed build date 18 Oct 2011). Nonetheless, he's given me a receipt from his business to me (as if that satisfied Motorola's requests for a 'genuine' original receipt) and directed me to Motorola's service centre who may or may not tell me that its my fault (its not) and may or may not do it under warranty. The seller has 'kindly' told me that he's not going to leave me in the lurch and if the service centre doesnt fix the issue to send it back to him to try and get fixed. I'm not sure I trust what he tells me anymore, since this hardly seems like an issue that could just result from a simple 'hard reset'
Well at this stage I am so angry I could just throw the thing against a wall. If Motorola's service centre fails to rectify the issue, this thing is being sent back to the seller with a directive that unless he sends me a working phone he is to keep the brick and refund me my outlay.
What a nightmare. Should have just bought from Kogan for 50 bucks more.
Yea we live and learn...... Should have just sent back to seller, (if you received it that way)
Fingers crossed on motorola coming to the party.
Sent from my XT910 using XDA
65.1.40.XT910.Optus.en.AU OTA should be out there now or soon.
Android version 2.3.6
Fastboot xml will be available pretty soon.
do you have a link to the fastboot files? Need to downgrade from ICS for warranty purposes
Related
Hi
Has anyone had any experience with service centres? I ask as I might see if I can get a replacement screen for my SGS2. It has yellow on the left hand side and its really bugged me. It doesn't seem to be a software problem, I have tried lots of firmwares and tricks but nothing.
I'm not sure if I would be eligible for a repair as I have been flashing different firmwares - clockwork mod and the root kernal both brought up the ! in a triange at boottime. Its not there now as I have just flashed 2.3.6.
It was a three (UK network) phone, no branding on phone or box, but a few extra apps on the phone. I wiped that firmware and never made a backup It was carrier locked so I needed to get root and unlock it with hellroz's app.
Do you think I would need to reset it to a state it was when I first got it (re-lock it to carrier even)? If not about how much would they charge for a new screen? (someone might have paid for a similar service)
Regards
Mike
Problem:
Updated my AT&T u8652 Fusion with a Huawei OEM firmware for a u8650 Sonic phone. The firmware upgrade did not finished all the way through step 2/2 but the phone boots up with the new firmware version identified via "About Phone". I did this without rooting the phone and have not back up.
With this firmware installed: I was able to root.
The problem is that this firmware was made for India - in the folder name is specified as this:
HUAWEI_U8650_Android_2.3_V100R001C151B863SP02_India_Trench
After the upgrade seems that all functions of the phone work, but the radio seems to be incorrect, I can no longer connect 3G, only EDGE, and the cell phone sensitivity is a lot lower than before the firmware upgrade.
==========================================================
I don't mind the u8650 firmware, but would like to get the radio portion to be correct for the US.
I have and identical Fusion that has been rooted with the stock AT&T firmware. I made a Clockworkmod/Rom Manager back up of this phone and installed the back up on the phone in question.
The functionality now looks like AT&T original, but the radio part is still messed up. With boot/system/data updated, the phone now has "no service".
==========================================================
I would like to put the broken phone back to the stock setup, but do not know how to utilize the identical phone to help enable this.
Or I would just like to update the radio portion for the broken phone.
Can anyone suggest some ideas to do this?
Thanks,
Rob
rob_fed said:
Problem:
Updated my AT&T u8652 Fusion with a Huawei OEM firmware for a u8650 Sonic phone. The firmware upgrade did not finished all the way through step 2/2 but the phone boots up with the new firmware version identified via "About Phone". I did this without rooting the phone and have not back up.
With this firmware installed: I was able to root.
The problem is that this firmware was made for India - in the folder name is specified as this:
HUAWEI_U8650_Android_2.3_V100R001C151B863SP02_India_Trench
After the upgrade seems that all functions of the phone work, but the radio seems to be incorrect, I can no longer connect 3G, only EDGE, and the cell phone sensitivity is a lot lower than before the firmware upgrade.
==========================================================
I don't mind the u8650 firmware, but would like to get the radio portion to be correct for the US.
I have and identical Fusion that has been rooted with the stock AT&T firmware. I made a Clockworkmod/Rom Manager back up of this phone and installed the back up on the phone in question.
The functionality now looks like AT&T original, but the radio part is still messed up. With boot/system/data updated, the phone now has "no service".
==========================================================
I would like to put the broken phone back to the stock setup, but do not know how to utilize the identical phone to help enable this.
Or I would just like to update the radio portion for the broken phone.
Can anyone suggest some ideas to do this?
Thanks,
Rob
Click to expand...
Click to collapse
I seem to be in the same situation as you, its an ATT phone, but when I put an ATT sim inside it asks for an unlock code! Did you ever figure out how to get the original radio back?
sactownsav said:
I seem to be in the same situation as you, its an ATT phone, but when I put an ATT sim inside it asks for an unlock code! Did you ever figure out how to get the original radio back?
Click to expand...
Click to collapse
Thanks for your reply. I could never fully overwrite the India firmware where I could get the 3g working. Since I was within 15 days of purchase at Walmart, I just returned the phone. I ended finding a perfect phone on Ebay for $65 and installed the "Zac" rom. No issues ever since.
rob_fed said:
Thanks for your reply. I could never fully overwrite the India firmware where I could get the 3g working. Since I was within 15 days of purchase at Walmart, I just returned the phone. I ended finding a perfect phone on Ebay for $65 and installed the "Zac" rom. No issues ever since.
Click to expand...
Click to collapse
Im actually considering a huawei sonic radio and see if that works, at this point im almost out of options
Thanks for the reply
Hey all,
So I've ran into a snag on my XT910 over the past few days.
Randomly, the device just dropped signal one evening and it never recovered it. Having troubleshooted with my network (O2 UK) and trying other SIM cards in the device, I have narrowed it down to the "Unknown baseband" or "No IMEI" symptoms found on these forums.. The device downright refuses to read (or even acknowledge the existance of) any SIM cards at all. It doesn't prompt for one to be inserted; it just says "No Service" where my network name should be, with an antenna and red "x" where the signal bars should be. Trying a working micro SIM from my girlfriends phone yields the same result. It doesn't even know it is in there.. In "About phone" it says Unknown baseband and dialing *#06# from my device gives a blank IMEI. Adding/viewing contacts on the SIM returns an error. I went so far as to get a brand new SIM from my network - still no dice.
The device is less than a month old and still under Moto warranty. However, the company I bought it from have neglected to provide a VAT receipt and I'm having trouble getting it off them. Moto have agreed to repair/replace the phone, but on the condition I have this receipt and send a copy of it to them. I really need this phone working, as it's the lifeline to my work, so I am willing to try reflashing/rooting the device ROM or radio as need be.
After some reading I have followed QPST guides to re-input the IMEI on my device, however it still exists and is correct. I have hard reset the phone, booted into recovery and wiped cache/data but no change.. I am considering the method of re-flashing the official OTA update for ICS, as I've read many users have this issue after upgrading, here: http://forum.xda-developers.com/showthread.php?t=1849744 - that is the correct ROM for my phone, but as I am already on that ROM I do not know whether flashing it on top will break things - ultimately brick it?
The device was (and still is) on 672.180.41.XT910.Retail.en.EU. I have not flashed any custom ROMs or rooted it. I have made no software or firmware changes to the device.
Please can someone help?! I do not mind getting my hands dirty and even voiding the Moto warranty if it fixes it (I would also be prepared to root it) but I am at a loss here - all pointers go to hardware fault and if that is indeed what it is, I would prefer somebody back up my assumption so I can send it to Moto knowing there was nothing I can do, rather than being a simple ROM flash away from having my device back..
Your phone may be damaged either physically (e.g. broken contacts SIM card slot) or software-wise (e.g. damaged PDS partition).
I'd go for a reflash, though - at least when properly executed it won't worsen your phone's condition. First, get full 672.180.41.XT910.Retail.en.EU flash file. Then, flash it using RSD Lite.
Vatazhka said:
Your phone may be damaged either physically (e.g. broken contacts SIM card slot) or software-wise (e.g. damaged PDS partition).
I'd go for a reflash, though - at least when properly executed it won't worsen your phone's condition. First, get full 672.180.41.XT910.Retail.en.EU flash file. Then, flash it using RSD Lite.
Click to expand...
Click to collapse
Thank you so much for this.
If it doesn't work by reflashing, can I still send it to Motorola under warranty for a hardware fix?
FrankPlummer said:
Thank you so much for this.
If it doesn't work by reflashing, can I still send it to Motorola under warranty for a hardware fix?
Click to expand...
Click to collapse
Hey,
I've just reflashed with RSD and I still get "Unknown baseband version" and no IMEI on the device. I guess it must be a hardware fault somewhere along the line.. Thank you regardless - and if you have any further suggestions then please do let me know.
try changing baseband. who knows...
china baseband is perfect for EU
heblu said:
try changing baseband. who knows...
china baseband is perfect for EU
Click to expand...
Click to collapse
How would I go about doing that?
I'd really like to know too...
Sent from my GT-N7100 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1863106
install baseband via custom recovery. they are flasheable zip
Firstly, thank you to all who replied to or considered my plea.
Secondly, after extensive research and some testing on my part I have found this is a seemingly irresolvable hardware (or very heavily damaged software) problem. Through various threads online I have read about people getting this mostly after they upgrade their Razr to ICS. It doesn't seem to be limited to one specific baseband/regional version of the device, as customers on Verizon in the States have had the same issue I have in the UK with a SIM-free phone.
I have sent the device off to Motorola for repair/replacement. I will report back when I get the device back.
FrankPlummer said:
Firstly, thank you to all who replied to or considered my plea.
Secondly, after extensive research and some testing on my part I have found this is a seemingly irresolvable hardware (or very heavily damaged software) problem. Through various threads online I have read about people getting this mostly after they upgrade their Razr to ICS. It doesn't seem to be limited to one specific baseband/regional version of the device, as customers on Verizon in the States have had the same issue I have in the UK with a SIM-free phone.
I have sent the device off to Motorola for repair/replacement. I will report back when I get the device back.
Click to expand...
Click to collapse
si I guess it never returned from tha one trip to the repair service?
...im hvinga similar problem with the xt890 (moto RAZR i)
updated to 4.4.2 kitkat, and it lost its anthena. like forever.
since then, spent nights surfing sesrching for a clue. nothing.
even unlocked the bootloader. it ended with the never endings WARNING BOOTLOADER UNLOCKED thing. sometimes i can bypase it buy antherna is still gone.
there are no replacementes for this device i think.
i want to use it so bad
Jorge_Amaya said:
si I guess it never returned from tha one trip to the repair service?
...im hvinga similar problem with the xt890 (moto RAZR i)
updated to 4.4.2 kitkat, and it lost its anthena. like forever.
since then, spent nights surfing sesrching for a clue. nothing.
even unlocked the bootloader. it ended with the never endings WARNING BOOTLOADER UNLOCKED thing. sometimes i can bypase it buy antherna is still gone.
there are no replacementes for this device i think.
i want to use it so bad
Click to expand...
Click to collapse
I have the same problem with xt890
Hi everyone,
As i wrote before on xda (my topic), i disrupted my device's touchscreen while doing TriangleAway process. Then i tried many ways to recover but i convinced that it's not possible to fix it without changing the touchscreen parts. I left my device to warranty and they fixed in 15 mins. and it works great as before.
But now, i have another issue. While i was trying to recover my touchscreen i flashed official firmwares (downladed from sammobile) and rooted several times. And i disturpted device's imei somehow. I tried all methods which r given on xda but they didn't work unfortunately. I I have a last option, gonna leave my device to warranty again but don't know they gonna fix it under warranty or not. What do u suggest me to tell them? I mean, they gonna ask me how that happened but i don't wanna say i flashed firmware with odin cos i guess it ruins my device's warranty.
I need to learn, is that possible to lost imei while doing update with Kies or OTA? Or is it possible to happen with any legal application on an unrooted device? I need an acceptable reason to fix my device under warranty. Does anybody have any suggesion?
Thanks in advance.
I think you better not getting official firmware on other websites. You should use the "Firmware Upgrade And Initialization" in the "Tools" of Samsung KIES 2.5. It is totally original and it will download the latest firmware according to your model and serial number.
I tried using this function on my SHV-E210S and the IMEI was not lost but I don't know if there will be any problem on SHV-E210K.
At the same time, do you know how to make SIP registrations on SHV-E210S/SHV-E210K/SHV-E210L? I need that for putting the phone on LTE network and able to receive calls
evantkh said:
I think you better not getting official firmware on other websites. You should use the "Firmware Upgrade And Initialization" in the "Tools" of Samsung KIES 2.5. It is totally original and it will download the latest firmware according to your model and serial number.
I tried using this function on my SHV-E210S and the IMEI was not lost but I don't know if there will be any problem on SHV-E210K.
At the same time, do you know how to make SIP registrations on SHV-E210S/SHV-E210K/SHV-E210L? I need that for putting the phone on LTE network and able to receive calls
Click to expand...
Click to collapse
Thx Evan but that's not i'm asking.. and i don't have any information about SIP, never tried before..
egolgeli said:
Thx Evan but that's not i'm asking.. and i don't have any information about SIP, never tried before..
Click to expand...
Click to collapse
It seems that it is a must for you to lose the warranty because the IMEI cannot be lost if the phone is unrooted or coneect to the computer with USB debugging mode. However, how come you receive the warranty as I see your location is not Korea?
evantkh said:
It seems that it is a must for you to lose the warranty because the IMEI cannot be lost if the phone is unrooted or coneect to the computer with USB debugging mode. However, how come you receive the warranty as I see your location is not Korea?
Click to expand...
Click to collapse
my brother lives in Seoul, i'm not.. i sent it to him n samsung fix it.. in Turkey, they look for a slightest reason to not fix it.. my regards thru to Korea, homeland of Samsung
I bought this new i717 unlocked phone from ebay and sellers promised it is unlocked and it works with T Mobile and other GSM Networks. Got the New phone (has ATT sign on it) tried T Mobile SIM - Didn't work . ATT SIM Worked. Googled about why it does not work - read some forums like these( not blaming) and they mentioned need to root and change the ROM blah blah... so jumped on it thinking i can solve it piece of cake. BUT
I think i might of messed up by changing the unsupported boot now my phone doesn't turn ON.. tried various hard resets, soft resets.... googled but no help.. basically phone is hard bricked. No light, nothing - DEAD Phone..
So i sent the phone to Samsung they said phone bricked and some hardware failed (OMG) charged me 70 bucks since phone was out of warranty ( thanks to seller and myself for not checking before buying) and said they will compete reflash the phone and update the software
SO Lesson Learned in proper way
Guys Please be careful when you mess with ROM..
So my question is if they do reflash the phone - will it be still unlocked? ( i don't think the seller (to start with) have unlocked via att might have used some rooting methods). and can i be able to use it to ATT
if someone now what do reflashing the phone does ? and another thing i didn't get how do updating a ROM created a hardware issue. i was not able to argue with samsung guys... but if you guys know anything please shed some light
Thank you
PS: im new to XDA Dev forums
lpvasam said:
I bought this new i717 unlocked phone from ebay and sellers promised it is unlocked and it works with T Mobile and other GSM Networks. Got the New phone (has ATT sign on it) tried T Mobile SIM - Didn't work . ATT SIM Worked. Googled about why it does not work - read some forums like these( not blaming) and they mentioned need to root and change the ROM blah blah... so jumped on it thinking i can solve it piece of cake. BUT
I think i might of messed up by changing the unsupported boot now my phone doesn't turn ON.. tried various hard resets, soft resets.... googled but no help.. basically phone is hard bricked. No light, nothing - DEAD Phone..
So i sent the phone to Samsung they said phone bricked and some hardware failed (OMG) charged me 70 bucks since phone was out of warranty ( thanks to seller and myself for not checking before buying) and said they will compete reflash the phone and update the software
SO Lesson Learned in proper way
Guys Please be careful when you mess with ROM..
So my question is if they do reflash the phone - will it be still unlocked? ( i don't think the seller (to start with) have unlocked via att might have used some rooting methods). and can i be able to use it to ATT
if someone now what do reflashing the phone does ? and another thing i didn't get how do updating a ROM created a hardware issue. i was not able to argue with samsung guys... but if you guys know anything please shed some light
Thank you
PS: im new to XDA Dev forums
Click to expand...
Click to collapse
Good chance it wont be carrier unlocked after they're through with it. No big deal really as you can go here http://forum.xda-developers.com/showthread.php?t=2124544 and unlock the device yourself. Trust me it works, mines is unlocked and using a T-mobile sim and never had an issue. As for the hardware issue are you sure you flashed the right rom for the device?
dzee206 said:
Good chance it wont be carrier unlocked after they're through with it. No big deal really as you can go here http://forum.xda-developers.com/showthread.php?t=2124544 and unlock the device yourself. Trust me it works, mines is unlocked and using a T-mobile sim and never had an issue. As for the hardware issue are you sure you flashed the right rom for the device?
Click to expand...
Click to collapse
i hav att unlock code given by att ( got it this morning). once i have the phone returned from samsung i will try to unlock with att if not i will follow the unlock form you sent. thank you. i believe i flashed some kitkat supported ROM.
lpvasam said:
i believe i flashed some kitkat supported ROM.
Click to expand...
Click to collapse
Your gonna need to do better than that buddy, or your going to be sending your phone in A LOT.
Kit Kat based is not the answer. He is looking for, "did you flash the rom for your specific device?"
You need to be sure you are flashing device specific files. If you have i717, those are the files you need. Not trying to beat you up, it is pretty important you know this stuff though.
Hope it works out for ya.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app