Hello!
For some reason my board got fried so I took it to the warranty and they sent me to a place to drop off my phone. They changed it for free (great) but they also rooted my phone and left me a 4.1 ROM instead of the stock 4.2 as I had. I'm now having troubles regarding charging it (it's not detecting the cable correctly sometimes and think it's still plugged?) and it was fine before. So I'd like to see if it's a software issue before having to drop it off at the warranty for another full month.
OTA updates are not working obviously and Kies recognized my firmware as "up to date".
I don't want my phone rooted (I refused to do it right from the beginning) and I want my phone to be able to update normally.
Is there any way I can unroot my phone and leave it in the same condition I got my phone in originally? Stock ROM and all. I was happy with it.
Thanks a lot!
All needs to be Stock for unrooted phone.
Did they flash you a Stock/Custom Rom with a Stock kernel?
What does the phone info say ?
Are any root apps left in the menu? When yes, which ones?
To put in in a nutshell your aim is now to assure getting a stock Rom+Kernel and then unroot it with a Unroot App. Usually works like a charm
Oh, and if you want to switch back to 4.2 you can get the according Stock Rom either here by searching for your (exact) phone model or try novafusion.pl if its an old Samsung Galaxy.
TheDogWithoutFear said:
Hello!
For some reason my board got fried so I took it to the warranty and they sent me to a place to drop off my phone. They changed it for free (great) but they also rooted my phone and left me a 4.1 ROM instead of the stock 4.2 as I had. I'm now having troubles regarding charging it (it's not detecting the cable correctly sometimes and think it's still plugged?) and it was fine before. So I'd like to see if it's a software issue before having to drop it off at the warranty for another full month.
OTA updates are not working obviously and Kies recognized my firmware as "up to date".
I don't want my phone rooted (I refused to do it right from the beginning) and I want my phone to be able to update normally.
Is there any way I can unroot my phone and leave it in the same condition I got my phone in originally? Stock ROM and all. I was happy with it.
Thanks a lot!
Click to expand...
Click to collapse
Related
hey,
I had 4.2.2 in my 5503. Couple days ago I decided to upgrade it to 4.3 using flashtool, because there wasn't official 4.3 for my region yet . After that, I noticed my led and NFC are dead. Led isn't working (no flash when making pics, not working as a flashight). NFC unchecks just after when I click on it. Tried: downgrade, delete/rename usf (like in xperia z), many others official roms. tried fix and upgrade by SUS and SPCC. No changes. Also tried CM11 4.4, but still led is dead, NFC option can't be even marked. Now I'm on rooted 4.3. Any ideas how to bring them back? And no, backup doesn't exist
waw that's not cool.. do you erase the whole system when you flash?
Made in ZR
Yes. I thought it is better to have clean instal. Habit of installing roms on old phone. Everything else seems to work fine. I'm out of ideas.
hmm it's weird dude. well I suggest :
ensure that you bootloader is locked
do a fresh full flash with all wipes
do a reset in settings > backup & reset
then go into service menu > service tests > flash led
for the service menu, at the stock dialer, type : *#*#7378423#*#*
if it still doesn't work after this, I'm afraid this is hardware related.
Ilko said:
hmm it's weird dude. well I suggest :
ensure that you bootloader is locked
do a fresh full flash with all wipes
do a reset in settings > backup & reset
then go into service menu > service tests > flash led
for the service menu, at the stock dialer, type : *#*#7378423#*#*
if it still doesn't work after this, I'm afraid this is hardware related.
Click to expand...
Click to collapse
Did that many times. To have clear conscience I connected phone to another usb. formated, flashed .67 with wipes. After reset, in service menu led is still dead. connected to pc, updated with SUS to .569. and same story. I'm sure they were working before 1st flash and upgrade. If this is hardware problem, should NFC unchecks itself just after I click on it?
Ehh I suppose, I have to deal with it. There is no cure for my zr
ps. in /system/app/ I can see ncf.apk & nfc.odex only. That's it, right?
well I don't know mate, did you ever unlocked the BL? It may be drm related also
Made in ZR
NFC firmware needs update?
I got my ZR a few weeks ago, it came with 4.1.2 on it.
Straight away I hooked it up to PC companion and it updated to 4.2.2, during the first reboot I got a message on the screen for quite a while: "Updating NFC firmware"
I then had problems and thought it was due to 4.2.2, I downloaded & flashed a 4.1.2 ROM, once again, on the first reboot I got the "Updating NFC firmware" message.
Then I realized that the problems weren't due to 4.1.2 and flashed 4.2.2 again, once again got the "Updating NFC firmware" message.
This might not be much use to you but it seems to me that the NFC firmware needs to match the version of Android you're running.
Sorry, no idea how to update it manually, just thought it's something you might like to investigate.
Maybe start here ....
http://forum.xda-developers.com/showthread.php?t=2284166
Ilko, yes. BL was unlocked. I had thought, drm can be involved with it. If yes, I'm pretty ***. I don't see any other explanation. many official roms. repairs by sus and companion. checked in buildprop editor, and everything looks ok.
alan573819, when I bought mine it was 4.1.2 also. Couple weeks later upgrated it to 4.2.2. but I don't remember that NFC dialog. I just don't remember, so it doesn't mean I never had it it was long time ago. I know that topic. Believe me, I know them all I'm silent reader xda since se k800i. Always found answers without asking. Until now.. I had to register, because no1 have same problem. with z, there is problem only with NFC (no1 complains about led), and they can fix it by deleting usf. It doesn't work for me. anyway, on 4.2.2 I had no problems with NFC or led. everything worked perfect until I decided to upgrade it to 4.3 with flashtool.
my phone was unlocked, rooted, had .310, .67, .569 for at least 3 different regions, had CM11 4.4, was repaired and upgraded by SUS and Companion. No changes. It just has to have something with drm, because I don't believe that hardware was broken during update. drm can explain it. but.. that's weird if NFC and especially led has something to do with it.
okay, then did your ever relocked it? backed up TA? restored it?
Made in ZR
yes, I have relocked zr.
Like I said before, I didn't make any backups. Didn't expect any problems so I just wiped and flashed my phone. On the other hand- who expects them? . I can risk with my own phone. If I do something for others, I always do backups, double checks etc.
Hey.
This is my first thread so welcome all. If this issue was fixed or if there is similar thread please close it down.
I have Xperia T that was branded by Vodafone DE. I updated it once from the standard firmware (I think it was the 4.1.2 android) to 4.3 (9.2.A.0.295), everything was fine, except that on two occasions the screen just could not be forced to turn on. Everything was working, sound, calls etc. I just had to hard reset it to enable the screen. Once when I was receiving call I could not answer it, the screen was jumping, blinking and I could not do anything with it. Hard reset helped again. I thought that those were bugs from the 9.2.A.0.295 but now I'm not so sure.
I downloaded the newest version of flashtool and the UK 9.2.A.1.199 firmware from this site, not branded, not modified. I unlocked the phone using the instructions on the sony site but since i didn't wanted to root the phone I locked it again. I flashed the mentioned UK firmware without problems and then the phone started to randomly reset itself. Usually it is getting hot under the camera and it resets mainly after using facebook or basically internet. It mostly resets when my phone is in the pocked. I tried using pc companion's repair option, used the firmware from Italy, Greece and almost all 9.2.A.1.205 except the Bond release. I think it's not the firmware, I've reverted to the 9.2.A.0.295 to no success. There are from one to six resets a day at random hours. Did someone had this problem? Is it related to the firmware flashing or could be just a coincidence and my xperia is dying from motherboard\battery failure? I replaced my sim card with new one. It also happens with or without the sd card.
Hi, the most common restart's are:
a) Sim card ( you change that)
b) Software ( you change that)
c) Very rare SD card ( try to do that) get the SD out end boot the phone. Edit .. you all ready do that.
d) End must common is the Battery ( first try de c) version ,then if fail , you need to buy a new battery end try.
e) motherboard (well new phone? )
This not exactly the order, but from i have read , point d , b ,a , are the order .
So Good Luck.:good:
I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.
Nekris said:
I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.
Click to expand...
Click to collapse
I have heard that upgrading to 4.3 could actually damage the battery. So yes, it is possible.
I don't know the reason tho
Sent from my Xperia V using Tapatalk.
I have been using CM11 (14-03-2014 I believe), without major problems until yesterday. Sometimes my phone seemed to disconnect from my SIM and I had to re-enter my pin code to reconnect to my operators network. But as of yesterday my device doesn't seem to recognize the SIM card, It doesn't ask for a code at all and can't make any connection whatsoever. I didn't change a thing, this problem started out of the blue.
I wiped cache and dalvik, updated to the latest CM nightly (08-05) but that didn't make any difference. In other threads I read about the baseband that might need an update, but I can't check which version I have now because when I try to enter the hidden menu I get the no network connection error. The strange thing is that CM11 has worked with (I guess) the stock baseband.
Is my phone tripping or could it be that my SIM card is broken?
Help and thoughts will be very much appreciated
Try it on stock to be sure about it.
After some searching I found a phone that could fit a regular SIM card, a Blackberry 9900. My SIM worked perfect in this phone, so that is not the problem.
I Also did a complete wipe and installed a stable version of CM 10.1.3, but that didn't seem to help. I hoped that a downgrade would have done the trick. I might try a ICS ROM or the stock firmware, but I kind of lost hope and i'm starting to think this problem is hardware related in stead of software. I'll report back with results on stock firmware and the ICS ROM.
How can I make sure the SIM reader in my phone is working properly?
Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.
Beunhof said:
Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.
Click to expand...
Click to collapse
My good friend i know i probably come 2 late but here is the anser 4 future users!!
http://forum.xda-developers.com/showthread.php?t=2069723
its supose to freese in ther!! (not ther but ....)
I have the same problem, and exactly the same error at reflash.
Dead end. Buy a new phone .
I tried to flash it about 80 times. One guy from a gsm repair has a bit luck and make it work at the first, but then, when he wanted to repair my imei, the phone stucked again in S/W Upgrade.
Hey Guys,
So my brother recently received his Sony Xperia Z1 on a two year plan. When he received it, it was running stock firmware (android 4.2) and it was working completely fine. He then, using Sony PC companion, updated his phone to the latest official firmware (kitkat). But afterwards, his phone's microphone didn't work. He then called both Sony and his carrier asking what to do to fix the issue and they told him to restore the device, which he did, but that did nothing as his phone was still on kitkat and still glitchy.
So now the only option for him is to send it in for repairs, but that will take at least a month, and he needs the phone in the meantime. So brilliant people at xda, is there any way for him to restore his firmware to android 4.2 or another official firmware in order to fix the problem without rooting or unlocking the bootloader. If he unlocked the bootloader it would mean that he would never be able to send it in for repairs, which is vital in case it is not a software problem and a coincidence that the microphone broke at around the same time.
After the problem is fixed, I'll probably install cyanogenmod on it for him but he would not like to do that until we know we wont need to send it in for repair.
Thanks!
This is a guide to root the phone, it includes downgrading the phone... So you could just go ahead and do that step only. Good luck.
http://forum.xda-developers.com/showpost.php?p=45464115&postcount=2
Hi, I have a droid turbo that is driving me crazy, when the phone took the update to marshamallow, after a couple of weeks the wifi and signal had lost, sometimes when I restarted it or doing factory reset the networks worked, but always going to the same situation. I reflashed the stock 6.0.1 with rsd lite, it worked, but for a couple of days so I thought it was the motherboard, then I bought another one ($40 dollars) from a cracked screen turbo. That motherboard had 5.1.1 so it worked fine for a couple of days until the OTA came again and installed, it worked fine but a few days later the phone showed the same problems. I dont know what to do, I cant downgrade because the locked bootloader ( and sunshine is to expensive for me $25 dollars is to much in Mexico) and is the second motherboard !!! what is happening??? Please help me
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Einheit-101 said:
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Click to expand...
Click to collapse
but why this error is just happening to me? I dont find another users with 6.0.1 having the same issue, I repeat, I have 2 motherboards with the same problems that's to weird :/
I dont know man. Idk what you did or did not.