Database Develop

[SOLVED] IMEI missing, Baseband unkown, Wifi doesn't turn on

THANKS GOD. FINALLY REPAIRED!!!
@DevShaft Check the attachments bro
I just would like to thanks so much Sony Repair Center in Laredo TX US for repairing my phone in just 4 days.
Usually It takes 14 business days, and for non-US takes more. ( mine is non-US version)
My phone is covered with warranty thou. Now, the phone looks like a brand new unit, and I'm so happy and satisfied with the service they provided.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The issues was:
-Unknown baseband, no IMEI, wifi doesn't turn on (radio functions wasn't working)
-The phone freezes and reboot Itself when updated to 4.2.2 or 4.3. so It was stuck on 4.1.2
In the attachments below:
-STATEMENT OF WORK
-My Xperia Z after the repair
NB:
The old mainboard was manufactured on 13W17. The new mainboard is manufactured on 13W47
of course the new mainboard's IMEI# matches the printed one on the bottom because they changed It too.
***I hope whoever have the same issues case that I had gets their device repaired***
Good luck guys, and thanks for all the suggestions and help!
Phone repair process summery:
March 13
Repair results thru live chat
March 09
Repair status check thru live chat:
-The attached thumbnails below are for my phone status before I send in for repair.

Open a case with eBay and get a refund.
If the problems were not mentioned in the description, eBay will side with you and make the seller refund.
Sent from my C6603 using Tapatalk

I have the same issue, I fix it with reflashing the rom, but everything start from the beginning.

lepi said:
I have the same issue, I fix it with reflashing the rom, but everything start from the beginning.
Click to expand...
Click to collapse
thx for the reply , but what do u mean everything start from the beginning?
can you please tell me with details, what did u do exactly ? and which firmware build did u flash in ur Z?
what's ur Z model? c6602 or c6603?
if possible provide me with screenshots
thx

kingvortex said:
Open a case with eBay and get a refund.
If the problems were not mentioned in the description, eBay will side with you and make the seller refund.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
thx for the advice... this doesn't work my friend!

@DevShaft please read my thread and give me your help!
i was in your thread about TA partition and I read so many interesting information!
if you have any idea how i can bring back IMEI, baseband, please let me know!
anything that would help me!
thanks alot

Return it. I don't understand why you're messing with it when you're entitled to a full refund.
You have already tried everything that might have fixed it.
As for the TA, editing it (or doing anything except backing up/restoring your own TA image) will result in a hard brick, so that is a dead end.
Sent from my C6603 using Tapatalk

Nidhal AKA the king said:
hello everyone,
I recently bought an Xperia Z C6602 variant (used condition) from ebay, but i didn't know that it has some problems as the onwer didn't mention that...
when i first time inserted my SIM card, it wasn't readable... i went to Settings, About, and i found that baseband is: unkown... also, *#06# shows Blank IMEI... i attached some screenshots below for the phone current state!
in all 4.1.2 builds C6602&C6603, the phone doesn't reboot or freeze.
I'm so familiar in flashing, using flashtool... so as i read in this forum that flashing and/or downgrading with a stock ROMS would fix this problem.. i have done this with many builds on 4.1.2 for C6602&C6603, in first boot i get this screen showing POWER OFF or Use phone, with a message pops up 3 time saying: FACTORY START UP SERVICE - Please wait for POWER OFF button
For versions 4.2.2 & 4.3 phone freeze & restarting itself
i tried to update using PC Companion, SUS, and even Flashtool, after first boot i got that same screen with same 3 repeated messages.. BUT, when welcome screen appears.. the phone dim, and when i click on power it's not turning on, so i restart and try to unlock lockscreen, then, phone freeze and keeps restarting....
N.B: I have never Unlocked Bootloader as you can see it's stats in the screenshots... I have never installed a Custom Rom such as CM..etc. the only thing I did is rooted the phone on a stock ROM and installed CMW.. all was done in Locked bootloader stats!
I've seen many Z users encountered the same issue, but for my case I don't know why and/or how this happened because It's a second hand bought! and the old owner did not mention anything about errors, or issues.
As you read about the phone condition, so you now know everything I went thru ever since i bought!
So, please anyone can provide me with more helpful information, links, repair tool, software...etc that would bring back the IMEI and so Baseband... would be so much appreciated
Please check the screenshots below!
Thanks to anyone in participation to help.
@pbmcmlxxi @Milad.Alef @shekharsuman @Hubriss @yahyaalbadry @mhbmutu
I took the phone to a smartphone repairshop today, when i showed him blank IMEI and unknown baseband he knew the cause of that problem!
The problem is that the original phone's baseband was lost during a sim unlock process, and a wrong baseband were installed instead. the initial (original) baseband MUST BE restored in order to have IMEI, Wifi, and the other radio frequencies back to life.. PROGRESS will take more or less two days! NOT a guarantee to get a successful restore.
in some other cases which it isn't a sim unlock related, but it's still a common problem. when you install a Custom ROM and you don't know what you are messing with, this could damage your original Baseband...and the phone will get bricked!
also, other cases of that issue occurred during update!
so we got two cases in here:
Baseband restore successful = Everything will be back intact.
Baseband restore fail = The phone will remain unrepairable.
Read&Learn:
A baseband processor (also known as baseband radio processor, BP, or BBP) is a device (a chip or part of a chip) in a network interface that manages all the radio functions (all functions that require an antenna). This may not include Wi-Fi and/or Bluetooth. A baseband processor typically uses its own RAM and firmware.
Keep in mind guys, It's still so risky to do a flash customized ROM, and/or unlocking bootloader. so, be very acknowledged of what you're going to do. I believe that rooting on a locked bootloader is the best and safest way to get the best off of your phone as It'll never damage the DRM keys (Digital Rights Management) and TA Partition.
play with everything in your phone but never do with the marked in red files.
If you ran out of warranty, this is probably the best solution to get it fixed if all kind of flashing, updating, or downgrading to stock roms didn't work like in my case.
Please if you know anyone else who has same case like us, just tag him here or send him my link, at least they can make a try. it really worth it.
Thank you all for your participation.
Good luck for us.
Click to expand...
Click to collapse
Hi Nidhal..thanks for tagging me.
I read your post & you seem to suggest that there is way to bring back these "dead" phones back to life.Can you elaborate how you are going about restoring it.I think you & I have the same problems.
What did the tech guys suggest they are going to do with your phone?Do let me know about your progress.I want to give my phone one last shot & if it doesn't work this time, then I'm actually going to go out & bury it in the nearest field. :laugh:
All the best buddy!

Hubriss said:
Hi Nidhal..thanks for tagging me.
I read your post & you seem to suggest that there is way to bring back these "dead" phones back to life.Can you elaborate how you are going about restoring it.I think you & I have the same problems.
What did the tech guys suggest they are going to do with your phone?Do let me know about your progress.I want to give my phone one last shot & if it doesn't work this time, then I'm actually going to go out & bury it in the nearest field. :laugh:
All the best buddy!
Click to expand...
Click to collapse
u welcome @Hubriss, sorry for the late respond, and also sorry to inform u that the phone failed to get repaired!
the only way to get it repaired is at Sony repair center!
if u there is a Sony repair center near your place just send it to them, even if it's out of warranty.. they charge u for a repair fee , but it's still better than to leave the phone unrepairable!
good luck!

kingvortex said:
Return it. I don't understand why you're messing with it when you're entitled to a full refund.
You have already tried everything that might have fixed it.
As for the TA, editing it (or doing anything except backing up/restoring your own TA image) will result in a hard brick, so that is a dead end.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
thanks for the advice!
will send to sony for a repair!

The cause of yours and many other users problem is that you or the previous owner flashed the wrong region baseband or RIL (radio interface layer) for your device. There are so many firmwares to download and flash, it is child's play for anyone who doesn't fully comprehend what he's doing to flash the wrong firmware and get in a lot of sh*t like this. Therefore it is crucial to always be sure you have the correct information and firmware (FTF) for your device as a backup (not to confuse with a recovery made backup that is!).
To solve this issue you need to get a hold on the correct and complete (which includes baseband!) firmware for your device, preferably the one it was running when first purchased, and flash it through Flashtool. That should solve the issue when done correctly
Yours is already at Sony Repair Center, so nothing you can do about it yourself at this point. I'm sure Sony will fix this easily. For your info, this problem you're having has nothing to do with TA.

DevShaft said:
The cause of yours and many other users problem is that you or the previous owner flashed the wrong region baseband or RIL (radio interface layer) for your device. There are so many firmwares to download and flash, it is child's play for anyone who doesn't fully comprehend what he's doing to flash the wrong firmware and get in a lot of sh*t like this. Therefore it is crucial to always be sure you have the correct information and firmware (FTF) for your device as a backup (not to confuse with a recovery made backup that is!).
@Hubriss
To solve this issue you need to get a hold on the correct and complete (which includes baseband!) firmware for your device, preferably the one it was running when first purchased, and flash it through Flashtool. That should solve the issue when done correctly
Yours is already at Sony Repair Center, so nothing you can try yourself anymore. I'm sure Sony will fix this easily.
Click to expand...
Click to collapse
thanks so much for the answer!
it's really helpful, I hope you've had answered It since long time before i send in for repair to sony. and your answer is really rich with information that i didn't get a chance to know despite the deep search i've done in the Google.
i hope for whom who ran out of warranty would try this out. at least i called Sony and they provided the country my phone was branded for!
this is so important to restore the original firmware and bring back baseband and so IMEI!
thanks again bro!

@DevShaft
So, Sony will easily fix my phone without replacing it with another one?
yeah, I thought this would damage the TA Partition or it's related to it! Thanks god it's not!

Nidhal AKA the king said:
@DevShaft
So, Sony will easily fix my phone without replacing it with another one?
yeah, I thought this would damage the TA Partition or it's related to it! Thanks god it's not!
Click to expand...
Click to collapse
I would say it is just a firmware flash for them, since they can retrieve all the info they need about your phone from the IMEI number which is located at the bottom side of the phone. Providing a refurbished one or repair the phone in question is a matter of costs analysis. So yeah, I think they will repair .

DevShaft said:
I would say it is just a firmware flash for them, since they can retrieve all the info they need about your phone from the IMEI number which is located at the bottom side of the phone. Providing a refurbished one or repair the phone in question is a matter of costs analysis. So yeah, I think they will repair .
Click to expand...
Click to collapse
well, for me i'd be happy and satisfied if they will repair the phone or either replace it with a fully working one without any issues!
thx again for the help bro :good:
i looked up the phone SI and after sony told me it's branded for Saudi Arabia, I found these SI numbers/versions below:
Saudi Arabia Generic SA 1270-8384 1270-6726 Saudi Arabia Generic SA 1270-8384 1270-6727 Saudi Arabia Generic SA 1270-8384 1270-6756 Saudi Arabia Generic SA 1270-8384 1270-6757 Saudi Arabia Generic SA 1270-8384 1273-7883 Saudi Arabia Generic SA 1270-8384 1273-7885
hopefully sony will finish the repair asap

Hmm. Now, this is very interesting information.
Every different region's FTF of a specific firmware version that I've flashed/seen all use the same baseband or I should say that the version number of the baseband is identical between regions.
Is this a case of Sony using identical version numbers on basebands that are actually different? If so, they are the only OEM that I've seen do that and it seems highly irresponsible of them or at least that it would cause issues for them internally when working with basebands.
If the above is not the case, could it be that the RIL is different in some way between regions? Someone needs to extract the RIL from different region's firmware and compare them to check that, as this is potentially vital information that should be appended to the thread when people upload FTFs.
If I have time to get to my PC later or at all this week, I'll extract some basebands and RIL from some different firmware versions I have saved and at least run a checksum on them. If I do, I'll post results here.
Sent from my C6603 using Tapatalk

@Nidhal AKA the king I stumbled on this thread more or less by accident after reading your post in the Backup TA thread.
I've got a Xperia T protoype here that is having exactly the same issues. All the screenshots you've posted could be from my phone (does the service menu crash when you try to open configuration?)
I actually only realized it was a prototype when I was about to type the IMEI in to the system of the local Sony contractor to send it in for repair.
"F...." was what I thought in that moment...no free repair for me
@kingvortex I was able to get it working with CM10, which is using the same baseband version as stock roms that don't work. Now that could fire your question about the differences in basebands using the same version numbers, at the same I have no idea what else could be wrong and whether this prototype is maybe even using different hardware components.
Also, flashing stock over CM and skipping the baseband did not help.
Link to my thread with some more information: http://forum.xda-developers.com/showthread.php?p=50901058
@DevShaft adding you just for the heck of it, maybe you've got an idea
Oh, by the way: when I got the phone, it was "running" (should say "stumbling") on branded firmware. I would guess prototypes would rather run on some other fw...

@steeserious
Thanks for the attention in participating in here, well, definitely we got the same issues, also, the service menu under bootloader unlock menu either freeze or gets opened after a while, and you get an FC msg but i click on ''waiting'' and also the sim-lock menu which it takes forever to open, if u are lucky it'll get opened with [?] each case!
except of the other screenshots i posted in the first OP, when i was trying to test the earpiece, under test menu, it freezes until i click on home or return button...
after u installed CM, do u get a beseband, wifi and cellular network working?

Yes, everything was working under CM10, and only CM10. Not 10.1 or 11. Also, Wifi was working with the oldest firmware or when flashing the ICS stock firmware module to the fw versions that didn't work with it.
I'd really like to get to the bottom of the problem though and get a stock rom running smoothly and fully working.
By the way, do they really make you send your phone all the way to the US if you're in Tunisia? Isn't there any local contractor for North Africa?

steeserious said:
Yes, everything was working under CM10, and only CM10. Not 10.1 or 11. Also, Wifi was working with the oldest firmware or when flashing the ICS stock firmware module to the fw versions that didn't work with it.
I'd really like to get to the bottom of the problem though and get a stock rom running smoothly and fully working.
By the way, do they really make you send your phone all the way to the US if you're in Tunisia? Isn't there any local contractor for North Africa?
Click to expand...
Click to collapse
yeah, i have seen custom roms with lots of bundles and options but i'm like u, i prefer the stock, the way it's polished and designed which is more sexier and faster than others...
well, first of all, we do have Sony Stores in here but they don't cover up a device or an electronic wasn't purchased from their store even if it's still under warranty.. but we do not have a sony repair service , cuz if i'd've bought it from one of their stores, they'd've send in to the nearest country with a repair service. let's say, like france.
So, what i did is , i sent an email to Sony customer services claiming my phone problem, but i didn't know the phone is still under warranty... so long story... explained to them that no repair service is available in my country, they advised to send the phone in for a repair, but they needed a valid US address. thanks god I have a friend, talked to them, and they agreed to give their home address... so yeah, provided Sony with a valid US address...etc, got some documents to print out, and RMA# in which they need to determine the phone's case and follow up thru the whole process... so eventually, sent to US TX with an express delivery took almost 5days, then the friend sent it in to Sony repair center in Laredo TX, been contacting sony for checking the phone's status repair, they don't disclose and/or have any detailed info, all they got me is : phone is still under repair, and yesterday i did call, and the ''chat agent'' said, ur phone was shipped, and yeah , my friend will pick it up tomorrow from UPS without knowing if they did repair or NOT, replace it or NOT... no clue bro...
told they , u should've at least send an email to the customer about the phone 's status repair, updates..etc. the agent was like, u will find a paper which contain all the info about the process was done to ur phone. so it's a kinda of a report.
omg so long story.. hope u enjoyed reading it :laugh:

Return MJ5 to Stock after Kingo Root

I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://forum.xda-developers.com/showthread.php?t=2559715
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.

its on here too
http://forum.xda-developers.com/showthread.php?t=2559715

Return to stock
steveh_131 said:
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
Click to expand...
Click to collapse
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.

asilva54 said:
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Thank you, didn't see that when I searched last time.
ZOMBIExM4STER said:
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
Click to expand...
Click to collapse
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.

steveh_131 said:
Thank you, didn't see that when I searched last time.
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
Click to expand...
Click to collapse
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?

ZOMBIExM4STER said:
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
Click to expand...
Click to collapse
I will try, but I am not an expert by any means. I tinker, but hopefully these other more experienced guys will chime in if I say something incorrect.
1. Download odin from here: http://www.firmware-files.com/download.php?id=1&token=QDXtLX5r3hLhxpTt604CYR6zP9twKSmr
2. Extract odin to a folder on your computer
3. Download these four files:
http://www.firmware-files.com/download.php?id=8&token=1QMc777QYjZgceInVMKs1HlcxAWv2wrU
http://www.firmware-files.com/download.php?id=7&token=6AfQkrv4S1mjr2oClQdwHp62lZpT8BK5
http://www.firmware-files.com/download.php?id=6&token=rXopUUlOTAGrBAQfksBLl1lKu52xIjl0
http://www.firmware-files.com/download.php?id=15&token=5CYaBqGOCoJSQMM6K7WECGlLDK4NYWTT
4. These four files will be zipped. You need to extract the zip files somewhere onto your computer. Each file should have a .tar.md5 extension once you extract them.
5. Power off your phone. Put it into download mode. To do this:
Power off your phone completely'
Hold down the home button, volume down button and power button all at the same time
When the screen comes on, let go of the buttons
It will give you a warning. Press the volume up button to proceed to download (odin) mode.
6. Run the Odin3 v3.09.exe application (that you extracted in step 2)
7. Now that odin is running and hopefully connected, you need to specify the four files that you extracted to be downloaded. You should end up with a screen that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Click start and let it run until it is finished. Once it is finished, hold down the power button to power off your phone then do the same to turn it back on. The custom icon should be gone.

First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.

Rukbat said:
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Click to expand...
Click to collapse
Doesn't factory reset delete the Xposed framework?
With AT&T you can't do a walk-in exchange after 14 days - pretty scary to mail it in for exchange and risk a $650 charge when they discover you rooted it.
I had the icon turned off with Wanam, but it came back.

steveh_131 said:
Doesn't factory reset delete the Xposed framework?
Click to expand...
Click to collapse
I could probably write an accounting program for an agency as large as the US government (or have fixed the health insurance site - doing something for half a century does pound some knowledge into even rock hard heads like mine), but when it comes to Android, I'm one of the learners, not one of the teachers. You know the answer to this question better than I do. I'd assume it does. I've made a lot of stupid assertions over the years, so ...
I downloaded a course that I may start reading one of these days, so I might yet learn enough to write a "Hello, World" app for Android. (Programmers know what I'm talking about - the difference between being able to develop a program and being able to code something to run in a particular environment - and the only internal environment I know in Android is where the battery and cards go.)
With AT&T you can't do a walk-in exchange after 14 days
Click to expand...
Click to collapse
SSSSSSHHHHHHHH!!!!!!! You weren't supposed to tell them that. I hope they didn't read this thread, and I hope the very nice lady who gave me the phone I'm using now doesn't get into trouble. (I'm not talking about walking in and saying "I don't like this phone, may I have a different one, please?" I'm talking about walking in during the warranty period and saying "could you please make my phone work?" and being told that they'll have to give you another phone. The only thing I'd trade my N3s for is N3s with unlocked bootloaders. I just want to see something other than comets revolving around Samsung's name.)
I had the icon turned off with Wanam, but it came back.
Click to expand...
Click to collapse
Mine stayed off - for the 3 or 4 days that the hardware didn't die on me. Then ... well, maybe Samsung has a way to read melted silicon, or whatever it did to make itself electrically invisible, but I'm not going to worry about it.

Wanam will keep the icon hidden but once you factory reset the phone I believe it deletes the xposed framework and the icon comes back.
I could be wrong about that, but that is my understanding.
I don't think you'd ever fool the warranty department that way, unfortunately, which is why I used this method.
Sent from my SAMSUNG-SM-N900A using Tapatalk 2

after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)

ryant100 said:
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
Click to expand...
Click to collapse
No custom and no lock. I didn't run a root check, not even sure how.
The files are small because you're not flashing an entire ROM. My ROM was still stock.

[Q] Unlock bootloader wipes all data ?

Hello.
Im abit new to the forum but here goes.
Ive read tons of posts everywhere and there aint any exact answers anywhere to find.
In the past ive never known about the TA and DRM so happy as i am i just unlocked the bootloader on all the phones and still happy. The latest phone is the Xperia Z1. It has been abit buggy to say the least but im hoping software updates will cure this.
Anyway, i rooted my phone and unlocked the bootloader on the .681 firmware and now i am on .757 firmware. Using Doomlords kernel. I thought id check if i could backup my TA partition after unlocking the bootloader. And from what ive read its suppose to be wiped when you unlock the bootloader.
Well it was no problem backing up the TA partion. All files were there and it came out with no errors. So the question, how is this possible ?
I posted this same thing in General, sorry for that but i posted it here now so if a moderator finds this post in general then please delete it.
/Jonas740

If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.

eclyptos said:
If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.
Click to expand...
Click to collapse
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app

well.
HellRoot said:
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce

Jonas740 said:
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce
Click to expand...
Click to collapse
closed for being a duplicate.
use this link for other thread.
http://forum.xda-developers.com/showthread.php?t=2730169

Camera focus working ONLY after a factory reset/firmware repair!

Hi guys,
First of all, sorry for my really bad use of the English language;
Second: I recently switched from a Nexus 6P to an E6553 (because...reasons), and I'm really feeling home with my new smartphone.
The only thing is driving me crazy is...the camera focus.
What's the problem? Simple: it doesn't work, I'm sure it's a software problem and I'll let you know why I think this.
Just after the Setup Wizard, the camera works, and works really really well (it shots awesome pics!). Focuses even little objects such as insects, without the littlest issue. An example is the first attachment: I shot that pic just after a factory reset.
But the problem comes when I restore my apps, my photos and then reboot the phone. Then, the focus literally DIES. No way to get it working, it just stucks. End.
The only way to get it working is...formatting the phone another time and then never reboot it again!
I tried a factory reset from setting, a software repair via Xperia Companion, I even tried to refash the stock ROM through Flashtool (which...simply stucks at "Writing data", and the only thing I can do is repairing the software with XC).
Nothing to do: the camera works flawlessly after a reset/repair/flash, but after a reboot it becomes unusable.
And focus isn't the only problem (as it was a little one ????) : opening the Video Mode in camera makes the device freeze, meanwhile using third party apps for the camera makes me see an huge amount of glitches. The strange thing is that everything works without issues until a reboot, so it's certainly a software bug, but I don't know related to what. And no, it's not an app or something I installed: focus doesn't works even when booting in Safe Mode or creating a new user from settings.
And no again, bootloader is not unlocked, it isn't even unlockable, so no DRM Keys fault.
What you suggest me to do? I really love that phone, but using it with this camera is just impossible.
Uh, last details: I'm on the latest firmware, 32.1.A.1.185, Customised IT (Italy). I tried to flash another firmware (CE1) but as I said before, it stucks on "Writing data".
Thanks in advance.

Today I'm going to send it in warranty for replace the camera. It will be back in a couple days, I'll let you know if the bug is solved.

I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.

Oveana said:
I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.
Click to expand...
Click to collapse
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!

ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Thanks for your Solution. KEEP US UPDATED

ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Sorry, I did not understand what you did. Could you say that again with different words?

Oveana said:
Sorry, I did not understand what you did. Could you say that again with different words?
Click to expand...
Click to collapse
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.

ale29-09 said:
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.
Click to expand...
Click to collapse
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.

Oveana said:
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.
Click to expand...
Click to collapse
Why you unlocked bootloader Man?

arokososoo said:
Why you unlocked bootloader Man?
Click to expand...
Click to collapse
For rooting

Oveana said:
For rooting
Click to expand...
Click to collapse
If you again lock bootloader+ Ta restore, then camera problem gonna stay as it is now I.e no focus?

Anything we can do with this github code for huawei bootloaders?

https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?

borgqueenx said:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?
Click to expand...
Click to collapse
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.

JazonX said:
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.
Click to expand...
Click to collapse
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.

borgqueenx said:
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.
Click to expand...
Click to collapse
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader

xchatter said:
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?

I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?

JazonX said:
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?
Click to expand...
Click to collapse
Hi there,
I don't have any Huawei device right now. Only one P20 Pro for my wife but I unlocked it with a code back then.
I had a Mate 30 Pro but sold. Waiting for some stable google services solutions and I will buy again.

borgqueenx said:
I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?
Click to expand...
Click to collapse
Yes no problem at all.
ADB reboot bootloader works just fine, the usual white bootloader screen. No FRP lock though, which explains the "missing" switch in Developer Options.
Fastboot reboot, then reboots the phone as normal.
Didn't try any other commands.

Just waiting to get my pro plus to try this. Anyone else?

Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.

GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Unfortunately not. Although if all data is erased, it should have successfully completed its task and then you have a unlocked bootloader.
If no unlocked bootloader, your data should be kept on the device.

GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Make a backup with HiSuite on PC : Which you can restore later if the operation is successful.
Your data will only be erased if the Bootloader gets unlocked. At the attempt / trying stage It won't trigger a data wipe.
If the bootloader does get unlocked, It will be a massive win which is totally worth doing the google installations again.
Maybe next time onwards you can use Titanium Backup to backup apps and data., Push the Google Apps from the system dump of P30 Pro EMUI 10 to the Mate 30 / P40 Pro devices to have Playstore certified GMS, Host level adblocking and many more life-saving solutions.

Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any other ideas?

That is unfortunate. I dont think we can do more then. Will request a lock for this topic if no one else gives ideas this week.
Thanks for trying!

GabiTM said:
Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
Any other ideas?
Click to expand...
Click to collapse
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?

colthekid said:
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?
Click to expand...
Click to collapse
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.

borgqueenx said:
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.
Click to expand...
Click to collapse
Can we start a gofundme or something similar, money is a good incentive.

GabiTM said:
Can we start a gofundme or something similar, money is a good incentive.
Click to expand...
Click to collapse
Nope, because this is a very well paid job.
It could start to be attractive if you also count the media attention at minimum 50k dollar.

If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit

Gatos7 said:
If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit
Click to expand...
Click to collapse
Just like I thought...
The ban will cost them sure a lot sales off smartphones... And also aocked bootloader ?