Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK
If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.
CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app
As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.
Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.
KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!
xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around
Related
I tried many times and many versions of flashtool but my phone just won't flash any firmware. Unknown source and debugging mode were selected, but I always get Erro Flashing Aborted and it is really starting to annoy me.
Anyone could help????
let me help u out. u should check and do the following steps:
1. Turn on debugging mode + unknown resource in application setting
2. Make sure, drivers for xperia arc fastboot are installed correctly (no yellow hardware warning in "device manager" windows when you use flash mode
3. install sonyerricson software update and update services from sony website (this will correct ur xperia arc driver)
4. Try to update ur firmware from "update services", it will guide u through flash mode. in my case, that will not let me updated bcoz i already unlocked bootloader. The reason i did update via update services is just want it install correct usbdrivers for my arc
5. Go back to flashtool, now i'm pretty sure u can run flashing as smoothly as silk
How do I install those Fastboot drivers?
ratatouille said:
How do I install those Fastboot drivers?
Click to expand...
Click to collapse
So, i can assume that u haven't unlocked ur bootloaders
Here, following those steps thoroughly to get it done:
This one tell u how to install fastboot driver:
http://dvpda.com/299/how-to-unlock-bootloaders-on-your-xperia-arc-for-neo-play-pro.html
Click to expand...
Click to collapse
this one tell u how to get ur phone rooted:
http://www.addictivetips.com/mobile/how-to-root-sony-ericsson-xperia-arc-and-xperia-neo/
Click to expand...
Click to collapse
babygau said:
So, i can assume that u haven't unlocked ur bootloaders
Here, following those steps thoroughly to get it done:
This one tell u how to install fastboot driver:
this one tell u how to get ur phone rooted:
Click to expand...
Click to collapse
Problem is that my bootloader can't be unlocked... No blue light while holding menu button+connecting cable.
I even tried this http://forum.xda-developers.com/showthread.php?t=1115542 but it failed on Installing User Data.sin (at only one milimeter from succes). I am going crazy over it.... Had to use SEUS seven times so far to have the phone work again.
did u buy sim-locked phone?
babygau said:
did u buy sim-locked phone?
Click to expand...
Click to collapse
Yes but it is now unlocked
I think that's bcoz ur using locked phone, so hope this will solve ur problem
punkmonkey1984 said:
So as you may already be aware phones like mine, (orange uk) have the fastboot locked down, and so we cant unlock the bootloader.
I for one believe it can be accessed but needs a little bit of time and research on getting it done.
This thread is aimed for brain-storming for ideas and collecting them for us to try out,
You can de-brand your phone by flashing the software from this thread
http://forum.xda-developers.com/showthread.php?t=1033193
thanks to scott4 for the first upload mirror on page 3
Any ideas on getting the bootloader up and going on locked devices please put them in here
UPDATES
We now have root access thanks to Chainfire's gingerbreak apk which is here
http://forum.xda-developers.com/showthread.php?t=1044765
If your getting "could not extract assets" from gingerbreak
try doing
if that Fails try replacing it with rm -r /data/local/tmp
Update 2
Blagus has kindly opened up this thread here
http://forum.xda-developers.com/showthread.php?t=1063394
We need people with a SIM-FREE phone with a LOCKED bootloader to help us all out, so if thats YOU !!!
Help us poor sods with branded handsets please.
Click to expand...
Click to collapse
Sorry, I know this is the arc forum, but as there is no mk16 forum, I saw that usually people post pro development's in arc's forums.
I bought an used mk16 with the 4.0.1.a.0.283 firm, and the bootloader unlockable as explained in this link the SE website.
I installed Android SDK, JDK, PC companion, etc. I was unable to install the fastboot drivers until I found someones in SE website and now it seems to be OK (blue light if I connect the phone (turned off) to the computer while holding menu key)
After that, I configured my phone to enable USB debugging. Then I installed flashtool, and I tried to root the phone with it. It worked! (I didn't expect it to work, because I saw a few post with scripts, etc. to root the phone...)
So...
- Now I am with that firmware, rooted. Wich rootable firmware do you recommend me to flash to my phone? I always loved cyanogenmod, but I don't know if there is problems with the freexperia releases (like bad quality in camera picture, low volume, etc.)
- What is the baseband? I have one ending in 49.
- What are the requirements to install clockworkmod recovery? I love this recovery to do my nand backups, etc. Do i need to unlock bootloader to this? Is there any chance to lock again the bootloader? You know, for warranty things.
- Do you have ny list of what apks are secure to erase from /system/app? For example, I don need the moxier pro, let's golf, etc.
I suppose that those questions have been answered before, but without the mk16 forum, searching that info is quite impossible...
Thanks in advance.
Search keywords: mk16 mk16i bootloader flashtool wotan
khodos said:
Sorry, I know this is the arc forum, but as there is no mk16 forum, I saw that usually people post pro development's in arc's forums.
I bought an used mk16 with the 4.0.1.a.0.283 firm, and the bootloader unlockable as explained in this link the SE website.
I installed Android SDK, JDK, PC companion, etc. I was unable to install the fastboot drivers until I found someones in SE website and now it seems to be OK (blue light if I connect the phone (turned off) to the computer while holding menu key)
After that, I configured my phone to enable USB debugging. Then I installed flashtool, and I tried to root the phone with it. It worked! (I didn't expect it to work, because I saw a few post with scripts, etc. to root the phone...)
So...
- Now I am with that firmware, rooted. Wich rootable firmware do you recommend me to flash to my phone? I always loved cyanogenmod, but I don't know if there is problems with the freexperia releases (like bad quality in camera picture, low volume, etc.)
- What is the baseband? I have one ending in 49.
- What are the requirements to install clockworkmod recovery? I love this recovery to do my nand backups, etc. Do i need to unlock bootloader to this? Is there any chance to lock again the bootloader? You know, for warranty things.
- Do you have ny list of what apks are secure to erase from /system/app? For example, I don need the moxier pro, let's golf, etc.
I suppose that those questions have been answered before, but without the mk16 forum, searching that info is quite impossible...
Thanks in advance.
Click to expand...
Click to collapse
Xperia Pro has a very few roms for now.The famous CM7 & CM9 are available for Xperia Pro.I guess,MIUI is also available(not sure).But,You must unlock your bootloader in order to install these roms.Rooted phone is not enough to install these roms.Atleast not yet. And rest assured,there is not drawback regarding camera and volume.Different users have different taste,many like it and many dont.But the fact is they are closely equal.
Basebands are well explained by a XDA member in the following post,please do take a look at it
http://forum.xda-developers.com/showthread.php?t=1462360
For CWM, you only need a rooted phone.And the easiest way to install CWM on locked-bootloader Xperia 2011 device is by using this beautiful app from the following link.Go check it out
http://forum.xda-developers.com/showthread.php?t=1437840
For relocking bootloader,i haven't come across any thread which claims to relock Xperia Pro's bootloader.But yes,relocking Xperia Arc's bootloader is poosible.You can give it a try but I'm not sure if it would work on Xperia Pro or not.Here is the link:
http://forum.xda-developers.com/showthread.php?t=1134335&highlight=relock
Here again,we have a the list of system apks with their descriptions for Xperia Arc's firmware.I assume that the Xperia Pro Has Almost the same System Apks with it so the list for Xperia Arc would also imply for Xperia Pro as well.Here is the link:
http://forum.xda-developers.com/showthread.php?t=1089470
PS: Welcome To XDA
Thank you very much for all that information and the wellcome.
I can execute commands like "fastboot.exe -i 0x0fce getvar version" or "fastboot.exe devices" while in fastboot mode, so I assume that's OK.
But in the SE website they are very insistent about voiding warranty depending of blablabla. My phone is an unlocked (SIM free) from fabric one. I understand it will void the warranty if the phone would be form Vodafone (for example), but not mine... Do you know anything about this?
Do you recommend me any official rom? maybe the .42 one?
Now I have clear everything about the baseband, thanks.
That CWM apps you linked say to me (downloades form market) that MK16i is not supported by the app
I will take a look at that APK list, but first I want to be able do a NAND backup before starting to remove apks
Thanks again.
khodos said:
Thank you very much for all that information and the wellcome.
I can execute commands like "fastboot.exe -i 0x0fce getvar version" or "fastboot.exe devices" while in fastboot mode, so I assume that's OK.
But in the SE website they are very insistent about voiding warranty depending of blablabla. My phone is an unlocked (SIM free) from fabric one. I understand it will void the warranty if the phone would be form Vodafone (for example), but not mine... Do you know anything about this?
Do you recommend me any official rom? maybe the .42 one?
Now I have clear everything about the baseband, thanks.
That CWM apps you linked say to me (downloades form market) that MK16i is not supported by the app
I will take a look at that APK list, but first I want to be able do a NAND backup before starting to remove apks
Thanks again.
Click to expand...
Click to collapse
See, Unlocked phone means the phone is SIM free,i.e you can use any carrier SIM in your phone.But, Unlocked-Bootloader is a different thing.When you unlock bootloader,then you are free to flash any ROM which is compatible with your phone.Unlocking Bootloader voids warranty and that is what the SE website is trying to say.
I would recommend you to update your phone to the official .42 fimware version because it has many new features when compared to .283 ROM.Use SE update service or PC Companion for updating your phone.
And about cwm..try this...
http://forum.xda-developers.com/showthread.php?t=1302037&highlight=cwm
Thx again
I know the diff between sim locked and bootloader looked. It's just that I don't understand why they let you unlock the bootloader, but don't keep the warranty...
I have unlocked the bootloader right now. Didn't know that it wipes all your configuration, apps, etc! At least, it's still rooted.
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Maybe is an image to boot just one time?
And about the ROM you recommend, PC Companion offers me the .62, not the .42. SE Update Service tells me that I have modified software (because of the rooting, I suppose) so it can't update my phone. Any idea?
Thanks again
khodos said:
Thx again
I know the diff between sim locked and bootloader looked. It's just that I don't understand why they let you unlock the bootloader, but don't keep the warranty...
I have unlocked the bootloader right now. Didn't know that it wipes all your configuration, apps, etc! At least, it's still rooted.
And about the ROM you recommend, PC Companion offers me the .62, not the .42. SE Update Service tells me that I have modified software (because of the rooting, I suppose) so it can't update my phone. Any idea?
Thanks again
Click to expand...
Click to collapse
Now that you have unlocked-bootloader, then you must not use SE update service,niether PC Companion Update nor SE OTA updates !! If you do,then it will brick your phone.
The other option you have is to flash a firmware.For more details follow this link http://www.wotanserver.com/en/sony-ericsson/se/xperia-pro-mk16/unlock-tool/debranding-flash
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
khodos said:
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
Click to expand...
Click to collapse
Search in this forum and you can find the changelog
Have fun.
Sent from my LT18i using XDA
QUESTION
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
PANCHOMATASANO said:
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
Click to expand...
Click to collapse
Yea sure..
---------- Post added at 01:06 PM ---------- Previous post was at 12:58 PM ----------
khodos said:
Thx!
I edited my previous post with this:
I have installed that CWM, and booted to it, but now I don't know what combination do I have to press to boot again into CWM XD Taking a look at the commands executed in the bat, maybe is an image to boot just one time?
Thanks about the wotan link. Really easy to flash. Now I'm in .42. Do you know where can I find the firmware changelogs?
I'll take a second look to flashtool, because I'm going to need it to flash the CM 7.2 and the baseband...
Thanks again.
Click to expand...
Click to collapse
Well if u wan a permantent CWM based recovery and u r using any stock or stock based ROM use this kernel.. flash it using fastboot..
http://www.mediafire.com/?m4f43973m3vxybs
PANCHOMATASANO said:
AFTER OPENING THE BOOTLOADER
I CAN FLASH THE ROM AN OFFICIAL FTF?
Click to expand...
Click to collapse
If you just need to flash an official firmware, then there is no need to unlock the bootloader. I was advised not to unlock it when not necessary (for example to flash the phone with some custom ROM like CM). Because with locked bootloader you should not be able to brick the phone and you could be always able to save the situation using Sony PC Companion.
So if you need to flash an official firmware, you can do it without any unlocking via Wotanserver. The firmware flashing is free, just register there. The flashing is very easy - there is a graphic wizard which tells you what to do.
EDIT: Ooops, flashing FW using Wotanserver is no longer free - costs 2 EUR now. Few weeks ago I flashed my phone there for free...
Version 3 released! Check for even more simplicity and a new UI! NO more copying!
Click to expand...
Click to collapse
If you're experiencing errors, please report them either in the thread or PM me.
Please report ANY errors or typos you come across, I made this in 4 hours without a single break, so there's bound to be an error somewhere
What's new:
-Completely rewritten (ACTUALLY written, not VB)
-Even simpler! NO MORE COPYING!
-Even smaller in disk size!
-No tutorial needed! Yes, it's that easy -- just read carefully and don't panic
There's still no way to:
-relock the bootloader
-flash FTF files
_____________________________________________________________________________________________
Note: Inside the Fastboot.rar, there are fastboot drivers for 2012 Xperias. Install them if you dont have them yet. Those are the only useful files you need from that folder, everything else (both adb and fastboot) are already contained in the new BU.zip!
TESTING:
Reported working Windows versions:
Windows 7 x86
Windows 7 x64
Windows Vista x86
WANT TO HELP?
Then test it and report your phone model and windows version (x64/x86, service pack etc.) -- send me a PM
Please do... You can always flash a kernel or recovery.
Thanks for helping me and all those noobs out
About the attachments:
-Fastboot; contains adb and fastboot, plus Xperia 2012 Windows drivers
-BootloaderUnlock; contains the old PMFT - version 2 (kind of useless unless you understand everything it says in there)
-nexus; the NEW PMFT - version 3 -- if you already have the drivers, this is all you need
someone755 said:
I've been getting some questions on PM lately, about 'how to unlock my bootloader'...
So, fed up with those infinite PMs, I quickly put this together (30 minutes, not much).
It's not much, and I've only tested it for one minute, but it should help the average noob user get their bootloader unlocked.
(I've only tested this on a x86 Win7 PC, so please help me find out where this works on.)
So, the basic idea is, that the noob user extracts the attached adb and fastboot .zip file and extracts it to disk C: (I'll make options for other drives later on, I just need to know whether or not this works). The user then opens up the program inside BootloaderUnlock (and installs it), and, after many warnings, gets to a screen where he is told to input his Bootloader unlock code (obtained from Sony's website).
The program then warns the user a little more, just to make sure he understands, and then, two lines of text show up.
The user enters those lines of text into the console window (the fastboot.exe he extracted at the beginning) and Viola!
If all steps have been done correctly, he now has an unlocked bootloader
It's a simple, yet fool-proof concept, tested on a complete phone moron (after reading some instructions on Sony's unlock site).
Please help me test this, as this may be really helpful to those that don't understand FlashTool and don't have an idea how to do it via the official method.
Also, if you don't understand, there are some instructions within the program (written in VB, so you may need NET framework... MAY need it...)
Thanks for helping me and all those noobs out
Note: extract the fastboot.rar to C:, so you will have the fastboot.exe in C:\Fastboot\fastboot.exe
Note: Inside the Fastboot.rar, there are fastboot drivers for Xperias. Install then if you dont have them yet.
Note: The BootloaderUnlock.rar is a visual basic program. Please help me test it on different Windows systems (XP, Vista, 7, 8, 2000; all both x86 and x64)
Click to expand...
Click to collapse
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
derrickdroid said:
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
No it wouldn't. It'll either work or not
Sent from my Jellybean Xperia S
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
someone755 said:
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
Click to expand...
Click to collapse
i think he was referring to:
IF you are so beginner that you aren't able to even unlock your bootloader
THEN you could be so newbie to brick it
That's possible, if you're pointing to the fact they could brick their phone after unlocking the bootloader.
But before the unlock, no, it wouldn't be possible...
But hey, some people might have trouble with windows and are new to it. (I know many linux users that are forced to use windows for their phones that could use tools like this for their phones (not Sony, but others...)...)
So can this way unlock any bootloader even if it says bootloader locked? Thanks
Sent from my LT28i using xda app-developers app
Nope.
Did you not read the first post?
It's the same as the official method, but simplified...
Nothing's changed, basically, so it can't do more and it can't do less!
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Its not the phone, it's the carrier...
mcmanone said:
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
It's because companies like AT&T give locked down phones away for free with a service contract. That way they can lock some services to make you pay more. For example AT&T makes you pay an additional monthly fee for the use of tethering (only when you use the att stock Rom, it's free on generic version )
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread
So I guess it's great in my country;
you don't get a 'free' phone, you pay at least 1€ (depending on the plan you chose; I chose the one where I get to pay 370€ for a nozomi)
You can always trade your phone on Swappa (you have loads of ads on CM's sites and forums) and get an unlockable one...
what is the difference between this tool and this one?
http://forum.xda-developers.com/showthread.php?t=1794800
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
someone755 said:
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
Click to expand...
Click to collapse
okay thanks....
DOWNLOADING
Let the Noob try it !!
Hey Guys,
I am a Noob and have been trying to unlock my bootloader for about a week now, I have tried a few methods without any joy.
I will give this a go and will report back if it works or not. :laugh:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
someone755 said:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
Click to expand...
Click to collapse
Hi,
Thanks for the reply, the problem i have is with the drivers. I have tried different solutions as posted here and on the web.
But still could not get the drivers to work??
I will try this method as it states the drivers are included. If it all works awesome, if not then I fail and will forever be stuck with stock rom's.
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
someone755 said:
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
Click to expand...
Click to collapse
I'm running windows 7 on a 64 bit laptop.
Tried the flashtool drivers also but still no joy, I check in device management for S1 and each time there is a problem installing the drivers.
I still have a PC running vista so might give that a try if all else fails.
Thanks for your help so far, will keep you updated with how I get on
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand
Wow, Thanks for the surprise! U make my days!
sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161
sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?
hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse
sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago
hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!