Related
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...
I want to know. if you can start the phone in QCOM ? as default.
I refer to the option in the bootloader.
It is the only option for me, to have signal and data. :crying:
jezuss said:
I want to know. if you can start the phone in QCOM ? as default.
I refer to the option in the bootloader.
It is the only option for me, to have signal and data. :crying:
Click to expand...
Click to collapse
qcom? it does nothing, try.
simms22 said:
qcom? it does nothing, try.
Click to expand...
Click to collapse
Actually my phone has signal only when I enter QCOM mode
jezuss said:
Actually my phone has signal only when I enter QCOM mode
Click to expand...
Click to collapse
odd. whos your provider? as im in tmo, and whenever i enter qcom, i boot up normally.
simms22 said:
odd. whos your provider? as im in tmo, and whenever i enter qcom, i boot up normally.
Click to expand...
Click to collapse
My company is Movistar in Mexico , when I start my phone in normal mode , I have no signal.
i try everything and nothing.
but when i start my phone in QCOM everything works great
jezuss said:
My company is Movistar in Mexico , when I start my phone in normal mode , I have no signal.
i try everything and nothing.
but when i start my phone in QCOM everything works great
Click to expand...
Click to collapse
you have tried different apns i assume? maybe its something in your settings? have you tried a factory reset?
simms22 said:
you have tried different apns i assume? maybe its something in your settings? have you tried a factory reset?
Click to expand...
Click to collapse
I've tried everything , only in QCOM my phone works normally.
It will be possible to change the boot order from my phone?
jezuss said:
I've tried everything , only in QCOM my phone works normally.
It will be possible to change the boot order from my phone?
Click to expand...
Click to collapse
no
I got error while disabling secure boot on windows phone for arm.
Error code is C0000135
Unable to trace :/
djamol said:
I got error while disabling secure boot on windows phone for arm.
Error code is C0000135
Unable to trace :/
Click to expand...
Click to collapse
Interesting...What is it that you need exactly?
feherneoh said:
@djamol: a SecureBoot exploit just got released that supports any of the Windows UEFI devices (x86/x64/arm)
Click to expand...
Click to collapse
Yeah I know that since long days ago.
feherneoh said:
I knew about it since it was found, just couldn't get my hands on it
but question stays: how did you try to disable it?
Click to expand...
Click to collapse
I just was reversing
"EnableUEFISB.exe /disable"
feherneoh said:
I would have laughed quite lot if that actually worked
Click to expand...
Click to collapse
Lol, its should be work fine but the whole part of the code is missing.
Need to write your own one.
Hey guys,
I'm trying to unlock the bootloader for this phone but it gives me this weird error:
Code:
Unknow Error (1004)
. These are the logs:
Code:
DEBUG <08:20:08.374,T:12524> : to sign token with key for device:angelica
DEBUG <08:20:08.379,T:12524> : Begin login unlockApi
ERROR <08:20:18.900,T:12524> : Fail to login unlockApi
DEBUG <08:20:18.900,T:12524> : unlock return:1004 msg:
Any ideas on how to solve this?
protoloc said:
Hey guys,
I'm trying to unlock the bootloader for this phone but it gives me this weird error:
Code:
Unknow Error (1004)
. These are the logs:
Code:
DEBUG <08:20:08.374,T:12524> : to sign token with key for device:angelica
DEBUG <08:20:08.379,T:12524> : Begin login unlockApi
ERROR <08:20:18.900,T:12524> : Fail to login unlockApi
DEBUG <08:20:18.900,T:12524> : unlock return:1004 msg:
Any ideas on how to solve this?
Click to expand...
Click to collapse
I am not sure what you are doing here but the unlocking prcoes in my opinion is different. One of the things is: you ave to wait for a full week to complete is. Do a search for in Google "unlock bootloader redmi 9c" and you will find a complete instruction.
I got this error too.
It was because of the VPN running in the background connected to some other country on my PC.
Disconnecting it and trying again fixed it.
I have found the problem. It is the account. Although the account supports unlocking, it will show 1004 to change the account.
我已找到問題 是帳號的問題 帳號雖然支持解鎖可是會顯示1004換個帳號就可以了
I'm getting the same error. My issue is that I already unlocked the bootloader and accidentally locked it up again.
Now my xiaomi account does not allow me to unlock it again.
Tepepa said:
I'm getting the same error. My issue is that I already unlocked the bootloader and accidentally locked it up again.
Now my xiaomi account does not allow me to unlock it again.
Click to expand...
Click to collapse
I have the same problem, did you solve it?
Crystallinee said:
I have the same problem, did you solve it?
Click to expand...
Click to collapse
I had to pay to let someone with the EDL access rights reflash the ROM. My bootloader is still locked tho.
Probably once the bootloader is re-locked, you have to start the unlocking procedure from 0 and wait for the unlocking period. But in order to do that, you must have a working system partition.
Guys, I found the solution and have returned in faith that you might still be needing it.
scroll the comments posted 15th or 16th June 2022.
https://www.reddit.com/r/PocoPhones/comments/thhxgq
GUYS! Use mtkclient and unlock your bootloader without crappy MiUnlock!
Can anyone help me, to solve this problem?
sudipta08sarkar said:
Can anyone help me, to solve this problem?
Click to expand...
Click to collapse
sudipta08sarkar said:
Can anyone help me, to solve this problem?
Click to expand...
Click to collapse
I got through the error by using the sign in method i used the first time on miunlock, i was failing it using email sign in, then switched to phone number sign in and it just passed
Hey guys,
I Fixed this problem for my device after trying many types of solution.
1. First check my region on my pc, I set my own region on pc then I restart my pc.
2. I Check my sim card(that number I am using on mi account) is correct insect on my device, I insect my sim again on my device.
3. And must log in into Mi unlock tool using sim number, Not E-mail or Facebook. Because E-mail of Facebook log in...is not working for me.
I don’t know exactly which solution help me.. But I did this 3 work. And after doing all things Mi unlock tool gives me 44 hours to unlock my device. It is taking so long but I am happy because at last my work will be done.
sudipta08sarkar said:
Can anyone help me, to solve this problem?
sudipta08sarkar said:
Can anyone help me, to solve this problem
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sudipta08sarkar said:
Can anyone help me, to solve this problem?
Click to expand...
Click to collapse
Read my post. You may able to solve the problem
protoloc said:
Hey guys,
I'm trying to unlock the bootloader for this phone but it gives me this weird error:
Code:
Unknow Error (1004)
. These are the logs:
Code:
DEBUG <08:20:08.374,T:12524> : to sign token with key for device:angelica
DEBUG <08:20:08.379,T:12524> : Begin login unlockApi
ERROR <08:20:18.900,T:12524> : Fail to login unlockApi
DEBUG <08:20:18.900,T:12524> : unlock return:1004 msg:
Any ideas on how to solve this?
Click to expand...
Click to collapse
Hey, I found the solution, until now I tried to log in with my Facebook account to mi unlock tool and I got the same error (1004)
After trying to log in with the email and password of the account and not using another way AKA Google/Facebook, I was able to solve this problem and unlock the bootloader
a27229790 said:
لقد وجدت المشكلة. إنه الحساب. على الرغم من أن الحساب يدعم إلغاء القفل ، إلا أنه سيظهر 1004 لتغيير الحساب.
我 已 找到 問題 是 帳號 的 問題 帳號 雖然 支持 解鎖 可是 會 顯示 1004 換個 帳號 就 可以 了
Click to expand...
Click to collapse
First of all, I'm sorry for my bad English. After imei repair, the network and 5g work fine on this phone. But when I make a call, the screen freezes and does not make calls. When I install the Chinese software, I can make calls, but the wifi does not work properly. Please help. Thanks.
Reflash the correct firmware package
Fastboot Method
https://c.mi.com/thread-1857937-1-0.html
Chinese Wire Brush Tutorial（中文线刷教程）
小米社区
web.vip.miui.com
Personal advice, for reference only
个人建议，仅作参考，线刷miui12固件包啊，若还有问题，可能返厂维修。
jianjianus said:
Doğru üretici yazılımı paketini yeniden yükleyin
Hızlı Başlatma Yöntemi
https://c.mi.com/thread-1857937-1-0.html
Çince Tel Fırça Eğitimi（中文线刷教程）
小米社区
web.vip.miui.com
Kişisel tavsiye, sadece referans içindir
个人建议，仅作参考，线刷miui12固件包啊，若还有问题，可能返厂维修。
Click to expand...
Click to collapse
Bunu zaten yaptım. Toplamda 12 adet yazılım denedim. Her birinde farklı çalışıyor ancak görüşme sırasında mikrofon ve hoparlör hiçbirinde çalışmıyor.
civandemir4 said:
Bunu zaten yaptım. Toplamda 12 adet yazılım denedim. Her birinde farklı çalışıyor ancak görüşme sırasında mikrofon ve hoparlör hiçbirinde çalışmıyor.
Click to expand...
Click to collapse
Xiaomi Redmi Note 10 5g (Camellia-China)
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
miui12.5
小米社区
web.vip.miui.com
jianjianus said:
miui12.5
小米社区
web.vip.miui.com
Click to expand...
Click to collapse
Now I will download the software you suggested and try it. I tried two different software for the same region before but the result was the same for me. I will try it now.
civandemir4 said:
Now I will download the software you suggested and try it. I tried two different software for the same region before but the result was the same for me. I will try it now.
Click to expand...
Click to collapse
Do you remember the old miui version?
You can try its original line brush firmware,Fastboot Method
jianjianus said:
Xiaomi Redmi Not 10 5g (Kamelya-Çin)
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Failed (Error reading sparse file), this software got stuck in the middle of the software. I tried a different software and I get the same error. Now the device restarts constantly. And my priority is to fix this error for now.
civandemir4 said:
Failed (Error reading sparse file), this software got stuck in the middle of the software. I tried a different software and I get the same error. Now the device restarts constantly. And my priority is to fix this error for now.
Click to expand...
Click to collapse
Lütfen ayrıntılı işlem adımlarını açıklayın
jianjianus said:
Lütfen ayrıntılı işlem adımlarını açıklayın
Click to expand...
Click to collapse
this is the original firmware code (RKSCNXM).I installed this software in fastboot mode and after getting the error, the device reboots constantly.I tried two different firmware but it gave the same error (Error reading sparse file) . I will be using a different setup tool soon. I will post the result.
MiFlash2020-3-14-0
https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
I installed the software on the phone and turned it on. I did imei repair. It still stays on the search screen. I can surf the internet with mobile data. now i will add a picture and try to find out if my problem is related there.
jianjianus said:
MiFlash2020-3-14-0
https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
Click to expand...
Click to collapse
Could the problem in the topic title be related to the place in the picture? Can anyone with knowledge please help?
civandemir4 said:
I installed the software on the phone and turned it on. I did imei repair. It still stays on the search screen. I can surf the internet with mobile data. now i will add a picture and try to find out if my problem is related there.
Click to expand...
Click to collapse
imei Fix? Why do you need this? Normally, fastboot flashes do not lose imei
civandemir4 said:
Could the problem in the topic title be related to the place in the picture? Can anyone with knowledge please help?
Click to expand...
Click to collapse
There is no relationship, the figure shows that is to modify the sim card password?
İşletim sistemi dili Türkçe olarak ayarlanmıştır, böylece en azından anlayabilirsiniz.
civandemir4 said:
I installed the software on the phone and turned it on. I did imei repair. It still stays on the search screen. I can surf the internet with mobile data. now i will add a picture and try to find out if my problem is related there.
Click to expand...
Click to collapse
if you backed up the QCN,good,just flash it back.but if not.......connect the customer center and send it back to the factory to fix it.
柠檬Lyme said:
if you backed up the QCN,good,just flash it back.but if not.......connect the customer center and send it back to the factory to fix it.
Click to expand...
Click to collapse
There is no qcn file because it is a Mediatek processor. There is an nvram file. overseas registered devices do not have factory support.
civandemir4 said:
There is no qcn file because it is a Mediatek processor. There is an nvram file. overseas registered devices do not have factory support.
Click to expand...
Click to collapse
nvram not work with out flash rom with a box paid
shinobusensui said:
nvram not work with out flash rom with a box paid
Click to expand...
Click to collapse
it works with some paid programs but needs original nvdata backup