I recently bought a Sony Xperia Z C6603(used).It came with JB 4.1.2 on 10.3.A.0.423 firmware.It had an unlockable bootloader(but not unlocked).I did the following to it:
1.Rooted with DooMLoRD's method
http://forum.xda-developers.com/showthread.php?t=2186368
2.NFC stopped working after root, so applied this technique
http://www.youtube.com/watch?v=ts8rbhZpQOQ
3.Soon after, an update came up on Sony PC companion for JB 4.2 with firmware 10.3.A.0.423 so I got my device updated to the new firmware.
[But after this update,I lost my root previleges.So I had to root it again.]
4.Rooted again with DooMLoRD Easy Rooting Toolkit (v17) {perf_event exploit}
5.Installed CWM Recovery using this method
[After this root, however,I lost the Bravia Engine functionality in Album(it still worked with videos though)]
6.Made a TA partition backup using Backup-TA v9.6
After all this,the phone worked like a charm.I had rooted a locked BL & installed a working CWM Recovery.It was all I needed.
Then something strange happened.One day,I tried to turn on the Wi-fi and suddenly the phone rebooted and the SONY logo popped up.
I thought it was strange but then I thought it could have happened due to some software error or an app malfunction.
After the phone had booted I saw something weird on my Lockscreen.The Lockscreen clock was missing & in its place it read
"Loading..."
Then I pressed the Home Key & all i got was a black background.But I could still see the notification bar with time,network & battery status.
But the screen wasn't responding anymore.After a few minutes like that,it rebooted again.And so it kept on and on.Until I finally decided to Hard Reset[Power + Vol up]
At this point there was a new firmware upgrade on PC Companion(not OTA) & I had been thinking of updating my device, when all of this happened unexpectedly.
Nonetheless I decided to see if the PC companion still recognized my phone and if it did,I would try and flash the new upgrade.And it did & I flashed the new firmware 10.3.1.A.0.244.
The upgrade was successful(as in,there were no errors during the whole process).I powered up the device & was hoping to see a fully working phone.
But to my dismay, I was greeted with the same Lockscreen with Clock missing & "Loading...." written in its place.
I was utterly heartbroken & kept contemplating what might have gone wrong.I read up a lot of articles on XDA regarding Xperia Z devices & could't find anything that I could relate to.
The ones that seemed similar where left unanswered.
So finally I decided to downgrade back to its original firmware & see what I could do from there.
I tried searching for a C6603 10.3.A.0.423 firmware from my region but couldn't find one.Then I found the same firmware for C6602 for my region & flashed it on my device using Flashtool.
After the flash,however,I saw something strange.On the screen after the first boot,I saw something like this
POWER OFF
Please wait for Power Off Button.
USE PHONE
I selected the USE PHONE option & I was taken to the Homescreen where everything seemed normal.
However,the network was missing & the wifi did not respond.
Thinking it had to do with the C6602 firmware,I decided to flash a C6603 10.3.A.0.423 firmware from another region.
[Please note that while using Flashtool,I have always performed a clean wipe]
Doing so didn't help me either.The mobile network was still missing n wifi still unresponsive.
After this I tried EMMA but without much luck.
Right now I have a phone which boots up to the Homescreen & then restarts after a few minutes.
I cannot however access the app drawer or the Settings Menu anymore.
And most icons are unresponsive except Bluetooth,GPS & Display Brightness.
I have even restored the backup of the TA partition(which I had taken before it started malfunctioning) but to no avail.
If there is anyone amongst you who can help me restore it back to normal ,I would thank you from the bottom of my heart.
Regards,
An Xperia Z owner in despair.
Edit:Changed Title from "Xperia Z:Close to Bricked" to "Xperia Z:Bricked after turning Wi-Fi On".
Try flashing the same firmwares kernel and baseband in flashtool, not sure if it will help but worth a try. Use C6603 if thats your phones model to avoid any bugs if it causes any.
Phone off or continue using phone always appears when i flash a new firmware so i just power down and reboot.
Mackay53 said:
Try flashing the same firmwares kernel and baseband in flashtool, not sure if it will help but worth a try. Use C6603 if thats your phones model to avoid any bugs if it causes any.
Phone off or continue using phone always appears when i flash a new firmware so i just power down and reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I got a two C6603 stock ROMs with me right now: C6603_Unbranded_10.1.A.1.434 SG & C6603_10.3.1.A.0.244_Generic IN
I have tried flashing both using the latest Flashtool (while wiping Data,Cache & Appslog)
Both these ROMs include kernel & baseband.Will flashing them again separately help?
When I press POWER OFF on the screen,nothing happens.The screen just stays there.But after a while it reboots which happens even if I don't press the POWER OFF.
Thanks.
Ok, here I am again, nice post!
the "POWER OFF / Please wait for Power Off Button / USE PHONE" menu appears every time you flash a FW. It is some kind of in-factory test.
And maybe it would be a good idea to rename your thread into something more descriptive. "Bricked by turning on WiFi, only homescreen works" or something, so one can know what the thread is about just from the title. there are a lot of " I bricked! Help please" threads here already,
To me, it seems the first step now should be a logcat to find out why your phone reboots, and maybe in a next step also why you cannot access the App-Drawer/Apps/other stuff. But just try reflashing kernel&baseband as @Mackay53 suggested. If it won't help, it will certainly not hurt.
As for people who might be able to help: Anyone with a thread in the developers sections seems a good choice, but I don't know any people here yet as I'm also fairly new to this phone. I thought about mentioning some of the wellknown devs, but doing so before having a logcat wil only make them mad or laughing...
Attached Logcat
Ok..I'm back.Sorry for the delay between posts.
First off, thank you @Coirpre for trying to help me out!:good:
So I flashed only the Kernel & Baseband from firmware C6603_Unbranded_10.1.A.1.434 SG.
Same issue.
Then I decided to flash the complete firmware.
This time the phone booted properly & I could even access the app drawer n everything except again No Network & No Wifi.
In fact, the Wifi On/Off toggle was greyed out,meaning I couldn't change the On/Off status.
Apart from that the Phone itself stayed on for about 7 to 10 minutes(it still varies from one reboot to another).
This allowed me enough time to root it & install Catlog_v1.4 app.
Even this time around I tried restoring the TA-Backup in the hope that it might fix the Baseband=Unknown issue(I read somewhere about it)
But as of now Baseband & IMEI are still showing up as unknown/missing.
After a reboot,I got the logcat app running and recorded till the phone went into a reboot.
I'm attaching the same here.
I couldn't make any sense of it(as expected) but I do hope the brilliant minds here at XDA might throw some light into the info contained in the log.
Thanks in advance to anyone who can decipher it. :fingers-crossed:
*BUMP*
Anyone????No one??
Hubriss said:
Ok..I'm back.Sorry for the delay between posts.
[...]
Apart from that the Phone itself stayed on for about 7 to 10 minutes(it still varies from one reboot to another).
This allowed me enough time to root it & install Catlog_v1.4 app.
[...]
I couldn't make any sense of it(as expected) but I do hope the brilliant minds here at XDA might throw some light into the info contained in the log.
Thanks in advance to anyone who can decipher it. :fingers-crossed:
Click to expand...
Click to collapse
never mind the answer times, can't answer instantly either... I had a look at your logcat, and a few things seem odd.
First, there are heaps of these, which is somehow expected, as your IMEI and baseband is missing. No clue what it's supposed to say or do though.
Code:
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:261 IMEI reserved0 = 494d4549
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:262 IMEI reserved1 = 35653505
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:263 IMEI reserved2 = 30126670
Then, the modem crashes:
Code:
04-13 21:17:57.588 D/Diag_Lib( 343): Sending modem crash broadcast intent com.sonyericsson.modemcatcher.MODEMDUMP with data MODEMCATCHER_DATA:
04-13 21:17:57.588 D/Diag_Lib( 343): Event: Crash
04-13 21:17:57.588 D/Diag_Lib( 343): Time: 8889476
04-13 21:17:57.588 D/Diag_Lib( 343): Subsystem: modem
04-13 21:17:57.588 D/Diag_Lib( 343): Crashinfo:
04-13 21:17:57.588 D/Diag_Lib( 343): MDM-A5:hsu_al_ecm.c:1394:Assertion (uint32)"Allocating SPS pipe failed" == 0 f
04-13 21:17:57.598 D/Diag_Lib( 343): Intent child successfully forked
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorServiceBroadcastReceiver: Forwarding intent: com.sonyericsson.modemcatcher.MODEMDUMP
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorService: Service started...
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorService: onHandleIntent action: com.sonyericsson.modemcatcher.MODEMDUMP
the modem is subsequently shut down, there's things happening with netlink, IP-adresses and ports which I don't understand. Then, the modem crashes a few more times, always followed by netlink stuff and kickstart/SAHARA errors.
What I can not find is the moment when the definitive crash/reboot is. Can Catlog also get "dmesg" logs? That is the kernel log (logcat is the system log if I'm not mistaken), which could maybe help finding the cause for the reboots. when that is sorted out, it will maybe be easier to fix the IMEI/baseband issue...
Coirpre said:
never mind the answer times, can't answer instantly either... I had a look at your logcat, and a few things seem odd.
First, there are heaps of these, which is somehow expected, as your IMEI and baseband is missing. No clue what it's supposed to say or do though.
Code:
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:261 IMEI reserved0 = 494d4549
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:262 IMEI reserved1 = 35653505
E/kickstart( 2972): ERROR: function: start_sahara_based_transfer:263 IMEI reserved2 = 30126670
Then, the modem crashes:
Code:
04-13 21:17:57.588 D/Diag_Lib( 343): Sending modem crash broadcast intent com.sonyericsson.modemcatcher.MODEMDUMP with data MODEMCATCHER_DATA:
04-13 21:17:57.588 D/Diag_Lib( 343): Event: Crash
04-13 21:17:57.588 D/Diag_Lib( 343): Time: 8889476
04-13 21:17:57.588 D/Diag_Lib( 343): Subsystem: modem
04-13 21:17:57.588 D/Diag_Lib( 343): Crashinfo:
04-13 21:17:57.588 D/Diag_Lib( 343): MDM-A5:hsu_al_ecm.c:1394:Assertion (uint32)"Allocating SPS pipe failed" == 0 f
04-13 21:17:57.598 D/Diag_Lib( 343): Intent child successfully forked
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorServiceBroadcastReceiver: Forwarding intent: com.sonyericsson.modemcatcher.MODEMDUMP
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorService: Service started...
04-13 21:17:57.918 I/CrashMonitor( 1761): CrashMonitorService: onHandleIntent action: com.sonyericsson.modemcatcher.MODEMDUMP
the modem is subsequently shut down, there's things happening with netlink, IP-adresses and ports which I don't understand. Then, the modem crashes a few more times, always followed by netlink stuff and kickstart/SAHARA errors.
What I can not find is the moment when the definitive crash/reboot is. Can Catlog also get "dmesg" logs? That is the kernel log (logcat is the system log if I'm not mistaken), which could maybe help finding the cause for the reboots. when that is sorted out, it will maybe be easier to fix the IMEI/baseband issue...
Click to expand...
Click to collapse
Hello @Coirpre,
Nice to see u again.This is the first time I'm seeing logcats in my life.So I cannot make heads or tails of it.
Although I did notice that more than 70% of the lines have the "ERROR" attribute to it,which can;t be good.
Also,if it helps,I recorded this logcat just after a reboot & I guess it must have recorded it till the point where the next reboot happens.I had to wait for the phone to be booted up again to collect this log.
I don't know about "dmesg" logs but if you guide me in the right direction I could probably try to get that too(in the meantime I will try and find out more about it on my own).
If there's anything else you would have me do, just let me know.
Thanks again man!
Hubriss said:
Hello @Coirpre,
Nice to see u again.This is the first time I'm seeing logcats in my life.So I cannot make heads or tails of it.
Although I did notice that more than 70% of the lines have the "ERROR" attribute to it,which can;t be good.
Also,if it helps,I recorded this logcat just after a reboot & I guess it must have recorded it till the point where the next reboot happens.I had to wait for the phone to be booted up again to collect this log.
I don't know about "dmesg" logs but if you guide me in the right direction I could probably try to get that too(in the meantime I will try and find out more about it on my own).
If there's anything else you would have me do, just let me know.
Thanks again man!
Click to expand...
Click to collapse
I am using Logcat Extreme from the Play store. It's made by an XDA member and also does dmesg. install it, open it, and tap the three dots at the top right corner. you then get a dmesg option at the bottom[EDIT] I just tried and I can not find a way to save the log. BetterBateryStats has a "save dmesg" feature which I also did not get to work. The only way I got something was with terminal emulator, which you can also find on the play store. type:
Code:
su (accept the superuser prompt)
dmesg >/mnt/sdcard/dmesg.txt
you should then have a dmesg.txt file on your SDcard. I also hope it logs until the phone crashes, else it's quite useless.
finding out more on your own is the best way to learn! most of the things I am writing here is just educated guesses and things i found on google... I hope we can sort this out eventually...
Coirpre said:
I am using Logcat Extreme from the Play store. It's made by an XDA member and also does dmesg. install it, open it, and tap the three dots at the top right corner. you then get a dmesg option at the bottom[EDIT] I just tried and I can not find a way to save the log. BetterBateryStats has a "save dmesg" feature which I also did not get to work. The only way I got something was with terminal emulator, which you can also find on the play store. type:
Code:
su (accept the superuser prompt)
dmesg >/mnt/sdcard/dmesg.txt
you should then have a dmesg.txt file on your SDcard. I also hope it logs until the phone crashes, else it's quite useless.
finding out more on your own is the best way to learn! most of the things I am writing here is just educated guesses and things i found on google... I hope we can sort this out eventually...
Click to expand...
Click to collapse
I'm going to try & get the dmesg using GetLogs_v1.1 from here [APP] GetLogs - Get dmesg, logcat, radio, etc with one click!
I hope this gets the job done.
DMESG
Hubriss said:
I'm going to try & get the dmesg using GetLogs_v1.1 from here [APP] GetLogs - Get dmesg, logcat, radio, etc with one click!
I hope this gets the job done.
Click to expand...
Click to collapse
Ok.I couldn't get GetLogs to work.So I used the emulator method.I was able to run the command just for a minute before it rebooted.Attaching the log here.
Edit:Not saying that I know what it means but from the log,this part sticks out like a sore thumb
mdm_errfatal: Reseting the mdm due to an errfatal
Is this suggesting a hardware modem failure?Just curious
Hubriss said:
Ok.I couldn't get GetLogs to work.So I used the emulator method.I was able to run the command just for a minute before it rebooted.Attaching the log here.
Edit:Not saying that I know what it means but from the log,this part sticks out like a sore thumb
mdm_errfatal: Reseting the mdm due to an errfatal
Is this suggesting a hardware modem failure?Just curious
Click to expand...
Click to collapse
ah, good find! it seems it boots OK
Code:
<6>[ 15.075019] mdm_modem_ioctl: normal boot done
<6>[ 15.110178] mdm_pblrdy_change: pbl ready:0
<6>[ 17.551320] mdm_status_change: status = 1: mdm is now ready
but then encounters the errfatal which you found. I think it's too early to speak of a hardware failure, but to me the modem seems to be the culprit. this is as far as I can help you, no clue what to do now... sorry It might be an option to ask someone who is more experienced for help, but I'm not sure about the best way to do that....
Coirpre said:
ah, good find! it seems it boots OK
Code:
<6>[ 15.075019] mdm_modem_ioctl: normal boot done
<6>[ 15.110178] mdm_pblrdy_change: pbl ready:0
<6>[ 17.551320] mdm_status_change: status = 1: mdm is now ready
but then encounters the errfatal which you found. I think it's too early to speak of a hardware failure, but to me the modem seems to be the culprit. this is as far as I can help you, no clue what to do now... sorry It might be an option to ask someone who is more experienced for help, but I'm not sure about the best way to do that....
Click to expand...
Click to collapse
So,if indeed it is a hardware failure,I don't have a choice but to go to a Sony service center?or is it possible to replace hardware units on one's own?
Thank you @Coirpre for helping me out all these days.It's more than what I can expect from anyone.So thanks again.:good::good:
I hope other experienced members can come forward & share their knowledge on this.
Hubriss said:
So,if indeed it is a hardware failure,I don't have a choice but to go to a Sony service center?or is it possible to replace hardware units on one's own?
Thank you @Coirpre for helping me out all these days.It's more than what I can expect from anyone.So thanks again.:good::good:
I hope other experienced members can come forward & share their knowledge on this.
Click to expand...
Click to collapse
if no one else comes forward with a solution. i would talk to the guys at mobiletechvideos.com and see if they can fix it. their price should be a lot cheaper to fix it and a lot faster getting the phone back to you
skinsfanbdh said:
if no one else comes forward with a solution. i would talk to the guys at mobiletechvideos.com and see if they can fix it. their price should be a lot cheaper to fix it and a lot faster getting the phone back to you
Click to expand...
Click to collapse
Thanks for the suggestion.But it seems like they don't do Sony products.And being non-US resident,the shipping+insurance+repair charges would probably cost a lot.
Cmon guys.Some help needed here.Help me bring this "sleeping beauty" back to life.
Have you read this if I remember you got baseband unknown http://forum.xda-developers.com/showthread.php?t=2350795
Sent from my C6603 using XDA Premium 4 mobile app
indycar said:
Have you read this if I remember you got baseband unknown http://forum.xda-developers.com/showthread.php?t=2350795
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi indycar,
I did try that method in the thread u mentioned before.
I downgraded to stock .434,rooted,then restored TA partition.
But it did not work for me.
I'm not sure if it is really required to go down to .307 firmware to restore the TA.
If that's the case I haven't tried it yet.
Thanks for your suggestion.
It seems that my journey to revive my phone has almost come to a dead end.
After flashing various stock ROMs,basebands,kernels etc the phone just refuses to work.
Restoring the TA partition has not helped in restoring it back to normal either.
Somehow I get a feeling that all this has something to do with the IMEI & baseband gone missing.
Even after doing an extensive research on this forum on how to reinstall IMEI & baseband,there seems to be no perfect answer to it.
The few who managed to get IMEI & Baseband after they went missing are ones who either had a complete backup done before losing IMEI & baseband or ones who were lucky enough to get it work with a TA partition restore.
For whom TA partition restore did not work(I have seen a few on this forum) & for those who did not have a TA backup & IMEI and Baseband gone missing after firmware update,there seems to be no workaround.
It would also seem that since the device is fairly new,even the devs & Xperia Z enthusiasts have still to come up with a way of restoring them.
Until then, the case of missing IMEI & Baseband is a lost cause & there is no hope for revival for those folks whose device suffer from it.
Regards
An Xperia Z owner who has (almost) given up.
Hubriss said:
It seems that my journey to revive my phone has almost come to a dead end.
After flashing various stock ROMs,basebands,kernels etc the phone just refuses to work.
Restoring the TA partition has not helped in restoring it back to normal either.
Somehow I get a feeling that all this has something to do with the IMEI & baseband gone missing.
Even after doing an extensive research on this forum on how to reinstall IMEI & baseband,there seems to be no perfect answer to it.
The few who managed to get IMEI & Baseband after they went missing are ones who either had a complete backup done before losing IMEI & baseband or ones who were lucky enough to get it work with a TA partition restore.
For whom TA partition restore did not work(I have seen a few on this forum) & for those who did not have a TA backup & IMEI and Baseband gone missing after firmware update,there seems to be no workaround.
It would also seem that since the device is fairly new,even the devs & Xperia Z enthusiasts have still to come up with a way of restoring them.
Until then, the case of missing IMEI & Baseband is a lost cause & there is no hope for revival for those folks whose device suffer from it.
Regards
An Xperia Z owner who has (almost) given up.
Click to expand...
Click to collapse
what is condition of your phone right now ?
my xperia z has happened the same thing and I revive it successfully without a hitch so can u tell me following things ??
1. Can your phone detected by flashtool ?
2. can you copy anything in your phone sdcard ?
3. can you unlock your bootloader ?
If your device is able to detect by the flashtool, than flash only baseband of the firmware u flashed before. Remember flash only baseband which will give your baseband number and imei number
Let me know how it goes...
Related
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
it really work....thx a lot..my phone have the signal back again...
U mean that it supposed to have a weak signall,or no signal at all?
Sent from my Xperia X8 using XDA Premium App
you may try it too. but most of the time after unlocking have no signal at all because of the sim-Lock.
@mhieyato : if unlocking using msm7227_setool2 i put to debugging mode or NOT, if not to put debugging mode that tools can't running or stuck in " getting ROOT rights"...
Please explain step by step master...
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
Hey, what if my phone still have no signal ? Could you show me the whole tutorial? I use the ms7227_semc but when its nearly done , the ms7227_semc suddenly shut down. Could you please help me? I want my x8 back :'(
why it doesn't work for me? when running msm phone reboots, and this:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
3487 KB/s (585731 bytes in 0.164s)
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
430 KB/s (3087 bytes in 0.007s)
success
Waiting ...
Getting ROOT rights.
Failed to set prot mask (Inappropriate ioctl for device)
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
874 KB/s (8064 bytes in 0.009s)
insmod: can't insert '/data/local/tmp/mapper_2.6.29.ko': invalid module format
Second, we need to write semcboot
3643 KB/s (596916 bytes in 0.160s)
can't find userdate partition
Press any key to continue . . .
jjumphard said:
why it doesn't work for me? when running msm phone reboots, and this:
[...]
Failed to set prot mask (Inappropriate ioctl for device)
[...]
insmod: can't insert '/data/local/tmp/mapper_2.6.29.ko': invalid module format
[...]
Click to expand...
Click to collapse
As a wild guess I'd say you're not on Stock Kernel/ROM but some custom kernel/ROM.
Restore back to Stock Kernel/ROM.
EDIT: Oh wait, you're from the Unlocking Guide ... *should ID nicknames first*
Well, this can now be interesting to see if you can manage to unlock the boot loader again with nAa's Kernel flashed - as there's also no way to go back to Stock Kernel (through Flashtool, PCC, SEUS) while the boot loader is locked. :s
it works!
thanks a lot!
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
hi, i have a question about this fix, i unlocked a Xperia X8 (E15a) with octopus suite and then ''no service'' this post work for me? thanks for your help.
yey it worked for me.. after 1 year of giving up on my xperia, i found this post then i thoght why not give it a shot.. then boom it worked.. thanks for the post ^_^
Wow!! Thanks you have saved my phone from "no service" this thingy
yeah it really works!
I was about to put my phone in my garbage, thanks
Hiya guys,
I'm new to the Sony side of things, I'm usually a HTC user but my mother has just got herself an X8 E15i and I am having a few problems with it and was hoping people could help?
firstly, I rooted, UNLOCKED BOOTLOADER, flashed a custom kernel (X8_v08a-cm7_Alfs_djnilse) & GingerZaraki-v05.
Then I had no signal at all, so I thought "ok, flash a newer baseband to attempt fix"
but alas, no joy.
I have then accidently relocked the bootloader :faceplant:
This has now caused her to have no signal... oops... arn't us teenagers great
and then I have read HERE that it is fixable, and I have followed the steps listed but I still can not get signal.
every time I run either script msm7227_semc.cmd OR msm7227_setool2.cmd they both get root, reboot, but still can not get signal.
EDIT: copy of cmd results...
"process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
adb server is out of date. killing...
* daemon started successfully *
415 KB/s (585731 bytes in 1.378s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
52 KB/s (3087 bytes in 0.057s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
18 KB/s (8064 bytes in 0.422s)
Second, we need to write semcboot
919 KB/s (596916 bytes in 0.634s)
successfully wrote 0003ff00
Press any key to continue . . ."
its obviously gettting root, but what does 'protocol fault: no status' mean?
and I know that the bootloader is locked because I have used "x8toolbox.final" which I found on here - I would give the maker of it the credit but can not remember who it was.
So at present my mother has a x8 e15i, running 2.1.1 but can't have signal at all??
EDIT1: please help or I think I am in trouble here...
EDIT2: Doesn't matter now guys, after soft-bricking and Hard-bricking (attempted bootloader unlock fail) the X8, I have resurrected it!
and I have successfully rooted (4th time tonight) and now I have flashed GingerDX, which is running great with the GingerDX O/C Kernel
GlennBrownie said:
EDIT2: Doesn't matter now guys, after soft-bricking and Hard-bricking (attempted bootloader unlock fail) the X8, I have resurrected it!
and I have successfully rooted (4th time tonight) and now I have flashed GingerDX, which is running great with the GingerDX O/C Kernel
Click to expand...
Click to collapse
And What you did to resurrect it? I am in the same situation and i can not Find any solution. I used omnius to unlock my simlock...
Sent from my iPhone using Tapatalk
well I have the same problem. after omnius unlock i unlocked the bootloader and no signal. HHHEEEEELLLLLPPPPPPPPPPPPP.
nice guide bro, it really works =D
hello everyone,
i have xperia x8 E15i
I unlocked my phone and after that the signal of the network is weak or inactive.
i think the problem is in a step while unlocking the phone.
i have an idea and i wish you can help fix it.
i didn't personnaly unlock the phone and i don't know the code unlock
tell me is this the same problem as you??
and thanks for sharing your technical experiences
Well for Omnius sim unlock problem you have the answer here: http://forum.xda-developers.com/showthread.php?t=1911915
Did not unlock bootloader but have 3 phones with same issues
In response to what you said, I have 3 Xperia X8's with the same issue but all were unrooted using superoneclick and then loaded gingerdx on them. They worked fine for about 2 months then on all 3 phones (friends) one by one they ended up accidentally putting their sim unlock pin code into the network unlock code thing that pops up on the gingerdx rom and all ended up with no signal at all.. I dont have seTool 2 pro only lite and i cant find any way to get the phone fixed. i live in southern Africa so limited resources etc.. PLEASE HELP
mhieyato said:
i know some of you have this problem and worries that something wrong happend during the process of unlocking your phone. well that's the same thing i was thinking about 3 days now and trying to figure it out how to fix this. i just a noobie here and new for all this android thingy but i guess im just lucky fixing it.
by reading again the thread of how to unlock. it mention there that your phone might have a sim lock. this might be the problem so i search some thread related to this and guess what a found the answer!
now here's how to fix it.
1. after unlocking your phone using msm7227_setool2. check if you have network signal so you won't do the step 2 of this thread.
2. now if there's no signal, open again your msm7227 folder (which is the unlock bootloader tool) and you will see there's another tool which is ms7227_semc.
3. put to debugging mode then connect your usb to your PC.
4. run the ms7227_semc and wait till it done.
5. reboot your phone and you already have network signal again.
i hope that this help you specially for those who are new to this kind of stuff..
Click to expand...
Click to collapse
IF THIS HAS BEEN SOLVED SOMEWHERE PLEASE TELL ME ASAP
sorry this is first post. Cheers
Hello XDA!
man ive nervous to post..
BUT i have come a null/null IMEI reading after a CM10.1 bootloop issue and trying to flash a new CM.
I have been a XDA follower for about 9 months but I have never needed to post for anything, as you have carried all of the lords answers. :angel:
I have done, stock firmware reset, Param bin, wiped all done it again. etc etc.
Many a conclusion has led me to probably a service repair centre.
I believe one option will still work for my IMEI restore but my phone comes up with a command that makes no sense.
Any help would be appreciated.
I am currently using QPST Configuration to write my IMEI back to my phone.
I have got these programs http://forum.xda-developers.com/showthread.php?t=1804117
Aswell as another handy IMEI converter to make sure my IMEI HEX conversion correct. (sorry cannot link. cannot find)
I have been using QPST and can follow all steps, except my phone WILL not show on on active phones.
I have reinstalled drivers and followed all necessary steps.
I have tried it in recovery mode also in QPST and no active phone still.
I believe i can get this to work, just need it to recognize my phone, and ill write the IMEI and hopefully..
Voila.. i can call the GF and tell her to chill. :good:
IS RNDIS different to RNMET? (how big of an impact will this play on the process)
In qualcomm settings i get "RNDIS + DM + MODEM" but i do not get "RNMET + "
SOLVED:FLASH PERSEUS KERNEL AND CALL GIRLFRIEND
samsung i9305
Unitized said:
IF THIS HAS BEEN SOLVED SOMEWHERE PLEASE TELL ME ASAP
sorry this is first post. Cheers
Hello XDA!
man ive nervous to post..
BUT i have come a null/null IMEI reading after a CM10.1 bootloop issue and trying to flash a new CM.
I have been a XDA follower for about 9 months but I have never needed to post for anything, as you have carried all of the lords answers. :angel:
I have done, stock firmware reset, Param bin, wiped all done it again. etc etc.
Many a conclusion has led me to probably a service repair centre.
I believe one option will still work for my IMEI restore but my phone comes up with a command that makes no sense.
Any help would be appreciated.
I am currently using QPST Configuration to write my IMEI back to my phone.
I have got these programs http://forum.xda-developers.com/showthread.php?t=1804117
Aswell as another handy IMEI converter to make sure my IMEI HEX conversion correct. (sorry cannot link. cannot find)
I have been using QPST and can follow all steps, except my phone WILL not show on on active phones.
I have reinstalled drivers and followed all necessary steps.
I have tried it in recovery mode also in QPST and no active phone still.
I believe i can get this to work, just need it to recognize my phone, and ill write the IMEI and hopefully..
Voila.. i can call the GF and tell her to chill. :good:
IS RNDIS different to RNMET? (how big of an impact will this play on the process)
In qualcomm settings i get "RNDIS + DM + MODEM" but i do not get "RNMET + "
SOLVED:FLASH PERSEUS KERNEL AND CALL GIRLFRIEND
Click to expand...
Click to collapse
which rom u flash i having i have been googling for and tried all th steps and solution can u help me it would kindful
I hate my first thread in a new forum to be a "please help im a noob and f**ked up" but here i go anyway :laugh:
I've had the xperia Z c6603 for a few months everything's fine, Then it randomly got stuck in a boot loop, no way out including a hard restart didn't stop it.
* Used sony update to reinstall the latest firmware this led to "process system not responding" on start up.
* Used Flashtool to install C6603_10.1.A.1.434_UK unbranded the phone now works but with "please insert sim" and restarts with the sim in only to ask me to reinsert the sim again.
* I have tried C6603_10.3.1.A.2.67_CE this also leaves we with "process system not responding" and i have retried sony update with the same error again.
My uneducated guess is either a hardware problem, which is unlikely as the phone was 100% before the bootlooping and hadn't been dropped or under any added stress ect or something to do with the baseband/imei as these words have popped up a couple times whilst searching the forums lol , if it helps looking in "about phone" tells me "baseband version unknown"
This is all new to me but i like to think im a little smarter then your average noob , Any help or ideas on where to go next would be hugly appreciated, Chears peeps
Ok after more exploration and learning what the baseband not showing up means and also finding the same for my imei, I'm thinking i need to restore the TA.img but ive hit another sticking point.
Following rickwyatt's method found here ive rooted my xperia, no dramas there but when i run Backup-TA i get this,
/dev/block/mmcblkop1: cannot open for read: permission denied
This is the md5 for phones TA md5sum: 'can't open '/dev/block/mmcblk0p1': Permission denied
Remote object 'sdcard/TA/img' does not xist (sic)
This is the md5 for the TA backup cannot open input file c:\Backup-TA\tools\backup\TA.img
The phone is still under warranty so can be sent off if i have to but as it's xmas thats going to be a pain ...and besides i don't want to be defeated after 2 days of reading everything i can find about my phone lol
o0c0mrade0o said:
Ok after more exploration and learning what the baseband not showing up means and also finding the same for my imei, I'm thinking i need to restore the TA.img but ive hit another sticking point.
Following rickwyatt's method found here ive rooted my xperia, no dramas there but when i run Backup-TA i get this,
/dev/block/mmcblkop1: cannot open for read: permission denied
This is the md5 for phones TA md5sum: 'can't open '/dev/block/mmcblk0p1': Permission denied
Remote object 'sdcard/TA/img' does not xist (sic)
This is the md5 for the TA backup cannot open input file c:\Backup-TA\tools\backup\TA.img
The phone is still under warranty so can be sent off if i have to but as it's xmas thats going to be a pain ...and besides i don't want to be defeated after 2 days of reading everything i can find about my phone lol
Click to expand...
Click to collapse
Use this backup after rooting your phone, but before you unlock your bootloader
http://forum.xda-developers.com/showthread.php?t=2292598
CiscoX said:
Use this backup after rooting your phone, but before you unlock your bootloader
http://forum.xda-developers.com/showthread.php?t=2292598
Click to expand...
Click to collapse
Thanks for the reply, I figured where i was going wrong when using Backup-TA. i was trying to run "adbd insecure" on my computer instead of the phone, massive face palm moment but i now have my TA back up safe and sound, although restoring it hasn't helped so im going to flash the phone and start afresh then restore my TA back up and see if that cures it ....
Restoring the Ta hasn't made a difference, I've also tried C6603_110.1.1.A.1.253 as its the oldest firmware i could find for the Z on here as I'm sure i read somewhere sometimes the old firmware will help bring back the imei, maybe the launch firmware could help? Other then that I'm out of ideas now, and any search's for "lost imei and baseband" ect bring up threads that all point to the phone being a lost cause.
Okay everybody,
I decided to write a new thread for my problem because I think my prob is a very special thing.
I'm from germany, so please don't wonder about my english. I think it is a understandable.
The story begins with a software update for my GT-I9305. After the update, the IMEI was just "null", after some work with google I found out that the efs partition was broken. With my bad knowledge for this case, I destroyed the whole EFS folder. I installed perseus kernel. And, there it was! The whole and correct IMEI. The solution was the perseus kernel (stock doesn't work, neither reflash). But then, after a while the phone doesn't boot anymore. I flashed Android 4.4.4 and my phone was revived but the IMEI was again "null". I have no backup or anything else!
So I spent approximately 20 hours or more to understand the efs thing. I found much solutions but nothing worked for me. So, here I am.
What I've tried before
-reflash KitKat
-reflash Perseus (not compatible anymore)
-formatting efs partition for a blank and new EFS for editing
-tried to edit nv_data.bin with HEX
-tried to backup efs with a 3rd party app and edit this with hex (the app doesn't support my GT-I9305)
and then, there it was:
-tried to use a working EFS partition from another GT-I9305
-editing with Qualcomm NV Tools! (I think THIS is the solution!)
I tried NV-items_reader_writer (1.0) and EFS Professional (2.1.73), but in both can't find my phone:
What I've done in NV-items_reader_writer
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened NV-items_reader_writer
-checked the both boxes near the SPC box
-selected the right port (last: COM4)
-clicked on "connect"
-clicked on "read"
-> here it search the phone, but it can't find it and says "Failed.. Phone does not answer"
What I've done in EFS Professional
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened EFS Pro
-clicked on "Qualcomm NV Tools"
-refreshed the Available COM Ports
-selected "SAMSUNG Mobile USB Serial Port" (last COM4)
-clicked on "Connect"
-> Here it takes few seconds and he stops and says: "Phone connection has been lost!" and "Unable to send SPC to the Phone!"
What I've tried to solve this problem
-tried QUALCOMM USB Settings: "DM + MODEM + ADB"
-reinstall all Samsung drivers
-tried to install Samsung Modem with Qualcomm drivers (failed due to wrong platform; I've Win7 X64)
-reinstall Samsung Kies (for actual drivers)
-tried to dial *#9090# (in my case, this menu is totaly blank)
-tried in factory mode
It could be that I forgot some....
Now, my question to you all is, do you know what I've done wrong? I mean, this is working for the most users, but why not for me? What do you think? Did you think I really forgot something?
Some informations:
Phone: GT-I9305
Android: 4.4.4 KitKat
Kernel: Stock (3.0.31-2760029 ; [email protected] #1 ; Fri Sep 12 13:08:24 KST 2014)
Buildnumber: KTU84P.I9305XXUFNI3
Windows: Windows 7 X64
Do you need more informations? Post it!
Please help me, I want to bring this phone back to life!
And yes I know, to change the IMEI to a number which is not your own is ILLEGAL and to prevent this, it is not well seen to talk about, but this is MY PHONE and I want to change the "null" IMEI and IMSI to MY ORIGINAL IMEI. If this is a problem, I can send a PM to an mod with my phone (where you can see the IMEI), my username on a sheet of paper and the original box with the IMEI printed on. All on one picture!
Simply... I need a hero! Be MY HERO!
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
vnholden said:
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
Click to expand...
Click to collapse
Thank you for your reply!
I tried this, already. But I can't downgrade from 4.4.4. I don't read very much about this. I just know that this is a new security option from samsung (or Android)... I will tell you when I know more
qasim799 said:
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
Click to expand...
Click to collapse
Thank you for your reply!
The warranty is already expired...
This will be the last step I will do. Before this, I will try my very best to do this at home... But thank you for this tip
Edit:
What do you all think about this idea:
-I try to find somebody with a working EFS on GT-I9305 Android 4.4.4
-I get a backup from him
-I restore this backup to my phone
-I edit the duplicated IMEI with NV Tool to my IMEI
This requires that the NV Tool will with work with an existing IMEI and the the phone will be THE WHOLE TIME IN PLANE MODE to prevent IMEI ban...
What do you think? Will this work? Do I need somebody from germany (DBT) or is this not needed?
Take it to a phone repair shop they might have a way to fix it. And if they don't they might know someone who can and it would likely be cheaper than Samsung service center
Sent from my GT-I9305 using XDA Free mobile app
Identical case (Solved)
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
WesleyPs said:
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
Click to expand...
Click to collapse
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
viktorak said:
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Hello,
someone could give me an EFS file because I deleted mine but my camera would not boot and remains on bootloop
thank you in advance
SurrendeR1993 said:
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Click to expand...
Click to collapse
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
---------- Post added at 05:00 AM ---------- Previous post was at 04:46 AM ----------
banjomike said:
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
Click to expand...
Click to collapse
Sorry dude just found out only samsung can restore Imei give phone shop a try but I don't think they could sorry
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
SurrendeR1993 said:
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
viktorak said:
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
Click to expand...
Click to collapse
Hm okay. I applied a "old bootloader" before here from xda. I don't know what it was exactly. There was a boot.so or so in it.
I will try my best. I mean, if I can beat this, this is a really great success for me. My next step is to restore a full NAND backup from a friends of mine (from a GT-I9305).
I wondered about that, after I restored a working EFS, there were no NV data.
My journey to restore a corrupted GT-I9305 without pay some money
Sent from my GT-I9300 using XDA Free mobile app
how did you success ?
how did you success ?
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed
hope this helkps anyone, took me some 20 hours of tinkering
Oakhand said:
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed(
Click to expand...
Click to collapse
Can you post the links you used?
EwOkie said:
Can you post the links you used?
Click to expand...
Click to collapse
aside from the dropbox link in my post above I did not use much else. I downloaded a stock kitkat rom, but don't know from where.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)