Develop Bugs

[Q] Unlocking bootloader Xperia Play question

I bought a few weeks ago an Xperia Play locked on the 3 Network of UK. I removed the sim locked through one of the many sites that offer this service (htccode to be exact) and debranded it through wotanserver.com.
The problem I have is that I tried unlocking the bootlader of the device to no avail since I just can't enter fastboot mode no matter how many times I try (the blue light just doesn't light up). I've read quite a few other posts on this forum and a few other sites but I just can't find a clear answer as to why this is happening. I mean I unlocked the sim lock, I changed the firmware with a "clean one" and still it refuses to enter fastboot mode.
I tried rooting my phone through Gingerbreak or Superoneclick but they didn't work either. Is there any method (preferably an easy one) to root my phone? It's on Android 2.3.3.

Just a quick update to inform you that after a little more tinkering I managed to root my phone, and I might as well share with you how I did it.
Basically again using the wotanclient I returned my FW to 2.3.2 and tried Gingerbreak again. This time it worked like a charm! I also discovered that in 2.3.2 the 3g that didn't work on 2.3.3 now works like a charm so I might stuck with this FW for a while longer (maybe I will try 2.3.4 at some point as well).

Your bootloader is locked by your provider and it won't help unlocking the sim nor debrand it with flashing another FW. That's why it didn't help doing the stuff you did.
Look at this thread for unlocking the bootloader and accessing fastboot (it'll cost some money though, not much afaik):
http://forum.xda-developers.com/showthread.php?t=1232050
Further more gingerbreak/superoneclick etc. only works on gingerbread 2.3.2 as the loophole got patched in the higher builds. So if you want to retain root when updating do it by OTA or if you get fastboot going you can do it via CWM (clockworkmod) with a flashable .zip.
Regardcs Dousan.

Dousan said:
Further more gingerbreak/superoneclick etc. only works on gingerbread 2.3.2 as the loophole got patched in the higher builds. So if you want to retain root when updating do it by OTA or if you get fastboot going you can do it via CWM (clockworkmod) with a flashable .zip.
Regardcs Dousan.
Click to expand...
Click to collapse
or you can flash doomkernel (which has many advantages, but again, need to enable fastboot mode on your phone, to then unlock bootloader before you can flash the kernel)
i highly recomend using alejandrissimo's service. i did, and i've never looked back

Is there a way to downgrade my phone's fw if im on 2.3.3?

cj360 said:
Is there a way to downgrade my phone's fw if im on 2.3.3?
Click to expand...
Click to collapse
Yes there is mate. I take you have a R800i.
Go to the dev section and find a FTF file of FW build 2.3.2. Then grab flashtool 0.2.9.1 beta. Flash the FTF file and there you go. Downgraded and ready to root.
There's an easier way to root now, i take that's why you want to downgrade, just use the zergRush to do it. That works on any FW build. Check out the dev section for a thread about 'rooting with zergRush'.
Regards Dousan...

I forgot about the zergRush post cuz I bookmarked it but didn't read it that well. Are their bugs for doing it on the higher fw tho?

[Q] Xperia Pro MK16a / MK16i firmware

Does anyone have a copy of the stock firmware from the Xperia Pro MK16a or MK16i.
I messed up the phone and want to re-flash the stock firmware back into my phone.
I dont know what else to do and I am desperate....
If you have it in ftf it would be great. Please put it up on mediafire to share.
THANKS!!!

First, it should be usefull to know what you did to brick your phone.
Thinking quickly, here are your options:
1. If you damaged the system partition(mtd0), you may restore it with fastboot having a stock one. Also, it may be possible to restore it with from ClockWorkMod recovery(started via fastboot), with an update created from the stock firmware.
2. If you accidentally damaged the kernel, that would be a bit more difficult. Currently, there's no custom kernle for MK16, so you would have to wait until there's one, or recompile the stock kernel from source(SE makes sources available).
If it's the first, I may be able to help you providing my system partition. It's not the stock one, because the first thing I did when I got to root my phone was start Titanium Backup and begin to delete some system applications I considered useless. But I think you could find my system partition useful. Just explain a little more what you did.

Thanks for trying to help.
Basically I flashed another firmware for it and it didnt go as expected.
I cant restore it because now my phone is recognize as another phone so i cant download the stock firmware for my phone via PC Companion.
Mine is a MK16a with all the bloatware from fido.
I dont really care about rooting it or not.
I just wanted to get raid of some of the stock apps so it doesnt take up so much internal memory.
I think what I really need is the stock MK16i firmware and flash it to my phone or if someone got the stock MK16a firmware I can flash it again to get it running again.
If you anyone have any other suggestions please let me know.
Thanks

i also need a mk16i firmware packed as ftf, can someone help?

TeamXperia has MK16's now, so a stock firmware should be coming pretty fast from them.

I think ftf is for kernel & loader, not for system partition....
ichidakira, I managed to make a dump of my system partition, I think that will fix your phone. Note that it's not the original system partition, as I've deleted some of the default apps and changed the bootanimation.
To restore it in your device, follow this steps:
WARNING: This will clear all your data, including (but not only limited to) contacts, sms, applications, configurations, etc.
1. Download & extract this file: http://soporte.opensysperu.com/downloads/system.zip & the Xperia Pro recovery image from FreeXperia Project: http://www.megaupload.com/?d=8L3DC0UQ .
2. Copy the system.img to your sdcard(using any method).
2. With the phone turned off, hold the menu button and connect the USB cable. If windows asks you to install the driver, do it as specified in the thread about rooting Xperia Pro.
3. Open a command prompt on the folder where you have downloaded recovery.img .
4. Run "fastboot boot recovery.img"
5. The phone will turn on and get detected as a ADB device. Also, the CWM menu will appear on the screen, but you will not need it for now.
6. Run "adb shell". Then, run the following commands: (It may take a few minutes)
cat /sdcard/system.img > /dev/mtd/mtd0
exit
7. On the CWM menu, use thew Vol Down key to highlight "Wipe data/factory reset", and then press the power button. Confirm the action if needed.
8. When finished, type "adb reboot" on your command prompt.
Then, your phone should boot normally.

rcummings100 said:
TeamXperia has MK16's now, so a stock firmware should be coming pretty fast from them.
Click to expand...
Click to collapse
Thanks for the info.
Please let me know when they release it.

For anyone looking for mk16i ftf...
http://forum.xda-developers.com/showthread.php?t=1323730
Thanks to Jozinek

MK16i system partition
Guys, could anyone provide me stock or at least his semi-stock system partition, as alvaroag did above? I have rooted xperia pro MK16i (via xperia recovery) and I'm experiencing weird problems after hard reseting my phone. Everything works virtually fine now, but:
- home button works, but doesn't act as home should
- after USB connecting to PC the PC says that my SD card is not inserted (however I can see its content while in the phone)
- PC Companion software can't find the phone
If anyone would have any advice how to solve this, it would be much appreciated also.
Edit: I had rooted this phone month ago and until yesterday there were zero problems. But then suddenly I lost some of my synced contacts from MS Exchange, so I decided to hard reset it and reinstall apps to fix this little issus. And then everything started...

Try with the latest SE firmware:
{PRO}[DEVELOPMENT] - CM7.2.0 - FXP047 FreeXperia Project
At the bottom of the post are the links for the MK16i SEMC 4.0.2.A.0.42 & MK16a SEMC 4.0.2.A.0.42. Select the one according to your device. Flash them with FlashTool. No this will permanently erase all of your user data.
Then, if you want to root it, try with the zergRush exploit: [16/Nov][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v3.0](zergRush Exploit)
If the phone still presents problems, reflash the stock firmware & take it to your service provider for warranty.

Thanks, alvaroag. I was fixing further and further on and ended up with reflashing Jozinek's stock firmware which solved everything. But then, even with virtually out-of-the-box phone, SEUS still denied to update firmware, saying that the phone has altered software. Not sure if anybody really tried to wipe out EVERYTHING from the phone and pretend, that it hasn't ever been rooted or hasn't been did anything else, but I doubt SE repair service can be fooled that much - even stupid updater still sees some difference between my phone (which obviously lost all changes I made to keyboard, root access, everything after successfull revert to stock firmware provided by Jozinek) and regular not altered phone. So to make the story short - now everything works fine, I have virtually brand new phone, rooted via [16/Nov][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v3.0](zergRush Exploit). But on the other hand I really doubt that these changes can be reverted to the state, that SE repair center would not be able to detect them and thus maybe cancel my warranty. Which is a bit sad and I did not expect it.
BTW: What is the procedure now to update my firmware, once SE will release it? SEUS refuses to do it... And for sure I would prefer to keep my data, if possible...

If you have unlocked your bootloader, then you will not be able to use SEUS. Try using PC Companion. Even with the bootloader unlocked, PC Companion will work, as long as you use stock firmware.

alvaroag said:
If you have unlocked your bootloader, then you will not be able to use SEUS. Try using PC Companion. Even with the bootloader unlocked, PC Companion will work, as long as you use stock firmware.
Click to expand...
Click to collapse
Not true that unlocking bootloader automatically stops SEUS from working. I had Alejandrissimo unlock my bootloader remotely via the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1254416
And even with an unlocked bootloader SEUS worked just fine (that is until i flashed to the latest firmware posted on XDA in the Xperia Pro CM thread). But that's only true if you use his exact method. It seems that all other methods do prevent SEUS from working.
But yes, as soon as you've unlocked the bootloader, regardless of the method, your phone's warranty is void. That includes unlocking it the official way via the sony ericsson website! PITA
And technically, if you even root your phone, you've lost your warranty as well.

rcummings100 said:
But yes, as soon as you've unlocked the bootloader, regardless of the method, your phone's warranty is void. That includes unlocking it the official way via the sony ericsson website! PITA
And technically, if you even root your phone, you've lost your warranty as well.
Click to expand...
Click to collapse
Yes sure, but my point was not that this act voids warranty, which is clear and obvious. My point was about the fact that many people in forums are understanding rooting and other hardcore activities in the way, that "if something would go wrong with my phone, I still can revert all changes, reflash it to out-of-the-box condition and send it to repair service, while they will not be able to detect the phone used to be rooted or altered in similar way", but in fact there must be some detection mechanism which in certain circumstates (as is my reflashed phone) will recognize that phone has been rooted in the past. And my phone is now not upgradable by both SEUS and PC Companion.

Not exactly. If you root your phone without unlocking the bootloader(zergRush exploit), then you can reflash it using SEUS or PC Companion & any track of the rooting will disappear. But if you unlock the bootloader, that's permanent. Even if you relock the bootloader, you will not be able to lave it as it was before unlocking, as the DRM keys are deleted when unlocking.

If there's still interest, I have a stock SEMC/MK16a:2.3.4/4.0.2.A.0.58/xf_v3w:user/release-keys phone and I'm yet to start fiddling with it.
If there's anything worth extracting from it just let me know and I'd try.

mk16a stock firmware - wanna unlock phone
hi. i'm totally new to android platform and rooting stuff! i have a xperia pro mk16a which is locked to fido canada. i want to unlock and debrand it. what i have learnt till now is that i can debrand it by flashing it to stock firmware. please help!
about phone:
see attachment

ichidakira said:
Does anyone have a copy of the stock firmware from the Xperia Pro MK16a or MK16i.
I messed up the phone and want to re-flash the stock firmware back into my phone.
I dont know what else to do and I am desperate....
If you have it in ftf it would be great. Please put it up on mediafire to share.
THANKS!!!
Click to expand...
Click to collapse
Did you tried to do it with phone repair menu in pc suite?
-DON'T PLUG THE PHONE!
-go to SUPPURT ZONE
-and in the software update check phone repair
-check mk16 on the phone list and follow the instructions!

Firmware ftf
I have some links to generic firmware but i can not publish links.
If anyone wants me for the requested by pm

Which of these two possibilities is better for installing updates on a rooted phone?

Hello. I'm coming from a old windows mobile phone and just got my first Android device "Samsung Galaxy S4 mini GT-i9195" and obviously i'm loving it.
Still being a newbie to Android i already did a bit of advanced stuff (at least for a novice android user) like installing CWM Recovery and rooting the phone in order to be able to install apps on and external SD card.
But a new question arose: What about new Android updates, can i still install them without loosing root or even worse, damaging the phone?
After searching a bit on google i came up with two possible and contraditory possibilities which are:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
-No, it will likely mess the phone and i should wait 1 or 2 weeks for a updated rooted rom and "install" that instead.
So, i'm a bit confused here, what would be more advisable?

I suggest to make a nandroid backup, then try a custom rom from the dev forum.
There are 4.4.4 kikat roms for our beloved S4 mini, and i dont think samsung will go further.
Envoyé de mon GT-I9190

rick6 said:
-Yes, and afterwards i would only need to restart the phone in CWM mode and reapply the zip root file i used previously;
Click to expand...
Click to collapse
...... if, as has been said, you ever get an update. An update certainly will not damage the phone.
You certainly won't have to wait for anything. I agree with zlaz, flash a new ROM such as Carbon - you get regular updates and great support here on XDA (whichever ROM you try).

Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.

LanderN said:
Custom ROMs like CarbonRom (see the development section) is the way to go for this phone I would say. But if you wanna stay on stock and if we would get an update, Samsung probably wont let you install it via the usual OTA or Kies method, because your device is flagged as "Modified" after flashing a custom recovery (you can see this in the about this device section in the settings). You would still be able to flash the update manually with Odin, but you will then probably have to reroot it.
Click to expand...
Click to collapse
That's 100% true, I don't remember now exactly when your phone say, that it is modified and you can't update - moment you search for update in it or moment you try to download update that it has find.
Samsung oryginal software is not that greate anyways

Thank you all for the replies.
I think i got what i wanted with your awnsers, i just need to dig a bit more about the avaiable roms what what i can get from them. At the moment i'll keep my s4 mini as it is for a while longer i guess.
As for warranty i get something while booting up saying "Set warranty Bit: Kernel", but that seems to be what you normaly get when root a stock rom.

Possible Brick HTC M8

Hello All,
I think I may have possibly bricked my m8.
I was using cyanogen 11, when I decided to try and flash the GPE rom that is available.
However I did not flash the latest firmware. I am not able to get into fast boot. When I press Power + Volume Down, it takes me too bootloader but no options are available other then press power to reboot.
When it reboots I do get into the rom however, wifi, and service are unavailable for obvious reasons. My Stupidity may have costed me this phone :/ I wasn't able to get s-off with my t mobile variant. It is unlocked, and had TWRP installed.
Any help would be greatly appreciated!

Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.

BerndM14 said:
Bricked? But you can get into ROM? Do you even know what a "brick" means?
Just restore your device to Stock and do an OTA to get latest firmware in order to have a working custom ROM on latest firmware. You are T-Mobile, US? Do an RUU, or head over to the Collection thread in General section and download a nandroid backup for your device and restore it from within TWRP(Instructions is also available in the first 2 posts of the Collection Thread).
If you can get it into bootloader/fastboot it ain't "bricked", it's recoverable.
Click to expand...
Click to collapse
Okay maybe not bricked but I messed it up quite badly, Im not able to get it into the recovery or have it be detected via fastboot. I did try and do a ruu to have it be put back to stock but Im not sure how to go about doing that since ruu cannot see it since it isnt in fastboot... :/

Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop

subarudroid said:
Did you Make sure you update you SDK. Only the latest fastboot and adb will work with lollipop
Click to expand...
Click to collapse
I did get the latest one from the official site, I was able to use it perfectly fine last night. Now however when I try adb shows the device offline, even if I kill and start the server, and disable and renable the debugging, try different ports etc. I can get it to show the device name, but it says offline next to it, I get no prompt on the device. I was reading the gpe doesnt use fastboot, ( I may be wrong) But that would explain why I dont see anything at the bootloader screen, other then press power to reboot the device.

Good news everyone! I was able to fix it in the most impractical way ever.
So why nothing else worked, I did still have access to the rom which of course had no wifi or service. So what I did was install the terminal emulator via browsers onto my phone, from there I was able to type reboot recovery and restore my backup that I had! and wala, whatya know, now it works, and I dont have a useless phone anymore

[Q] BL locked on Xperia ZL. 4.4.4 - 0.292 - What are my options?

Hello,
I have a Xperia ZL C6506 with a locked bootloader. I would like to unlock it, or at least root the phone.
Bootloader unlock allowed: No
Android 4.4.4
Kernel version: 3.4.0-perfg1bb39c2
Build Number: 10.5.1A.0.292
Country: Canada
Flashtool will not root the phone, even trying Towelroot V3.
Seems like every answer I find on XDA says something about my phone is always stopping me. Either 4.4.4 is a problem, or BL locked, or 0.292, I can't root... What am I missing?
Do I have to flash a new kernel or rom? Is it even safe to flash anything, even if it is stock, on a phone with a locked bootloader? I do not want to brick.
Thanks in advance for your help!

I found this forum: http://forum.xda-developers.com/xperia-zl/help/rooting-xperia-zl-t2994781
But,
I read this: http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092 it says: "Newroot work with all kitkat firmwares but doesn't work with latest kitkat *after 108) .133, .157... firmware or with old JB firmwares!!!"
This is the only thing that I have found that I have not tried, but I am hesitant to try and flash an old kernel on a phone with a locked bootloader. Is it safe to flash anything on a locked bootloader?

Himura357 said:
I am hesitant to try and flash an old kernel on a phone with a locked bootloader. Is it safe to flash anything on a locked bootloader?
Click to expand...
Click to collapse
Yes, it is safe, as long as you know what you are doing. Put it this way: flashing the downgraded kernel will not screw you up, but doing things the wrong way might.
1. Download this. It's NOT a flashable zip! Just unzip it, and use FTF files to flash the appropriate kernels.
2. Read my post that you linked. It gives you all the steps of the process. Installing recovery is optional, but highly recommended (very useful). Use the kernels you downloaded from my link above.
That's it! A couple of notes...
- I am assuming you know how to use the FlashTool. Not the original one from Sony, but the the one by Androxide. Make sure you are familiar with it before flashing!
- Newroot DOES work with .230 kernel. I have done it many times while playing with different ROM versions, works perfectly. Make sure you enable USB debugging, and watch your phone for prompts to grant access. Your phone should reboot after successful rooting. If for some reason it doesn't work, just try again.
- When you flash .230 kernel, you may have some weird issues with your phone. You will lose WiFi. Your phone may start vibrating for no reason (mine did). Maybe something else, I dunno... Don't worry, it's only temporary. Everything will get back to normal once you flash .292 kernel after rooting. Again, tried and proven fully working many times.
- If you decide to upgrade to LP afterwards, this will also be your procedure to recover, if you screw something up in the process (been there, done that). Just flash your .292 stock ROM, then repeat the rooting process, then start with LP over again.
Happy rooting!

Thanks so much. It is crystal clear now. Always good to get some advice from someone who has done it before on the same phone.

Trying to flash and I got this error (attached pic)
I am running the newest flashtool. I didn't have any problem with the older flashtool in the past when I used to flash my older phones. Also, the older one installed completely in one folder, this one installs in 2 folders, one in C: and the other in C:/users/Me for some reason.
I installed the V1.5 driver package. Not sure what else is wrong. I unzipped the zip file, put the kernel.only.ftf into the firmwares folder, I clicked flash, selected the .ftf file and connected the phone in flashmode. No dice.

Ok, tried it again, this time it didn't get a red error, I got a different one, and my build number is still 10.5.1.A.0292...
Installed recoveries.
Pic is attached.

Okay!
So, after the first flash, the build number didn't change, but the kernel was applied. I just tried using newroot and it worked, superuser is there. Just like you said, the wifi stopped working with the new kernel. I flashed the 0.292 kernel and the wifi came back, and the phone is still rooted.
Thanks for you help kt-Froggy!

Himura357 said:
Okay!
So, after the first flash, the build number didn't change, but the kernel was applied. I just tried using newroot and it worked, superuser is there. Just like you said, the wifi stopped working with the new kernel. I flashed the 0.292 kernel and the wifi came back, and the phone is still rooted.
Thanks for you help kt-Froggy!
Click to expand...
Click to collapse
Good to know! Cheers!