any shot xrecovery working for the xperia play.since BL is locked cant do anything with this phone
No, you can't install a custom recovery unless your bootloader is unlocked. You can still gain root even with a locked bootloader though
i did root it but i have a locked bootloader and its sucks bc i cant do anything. just wondering if anything could possibly happen to chnage that
yeah, there is a method to unlock it, though it's $24. The thread is here http://forum.xda-developers.com/showthread.php?t=1232050&highlight=unlock+bootloader
Related
What would be the difference between these 2 methods of rooting for XPERIA Arc?
I know Gingerbreak is much easier to do than the other one. But, is there any limitations to what Gingerbreak can do compared with the other method ?
Since bootloader is still in locked state, that means those who did it with Gingerbreak still have their warranty valid, right? What about the installation of future custom ROM ? Would the devices rooted with Gingerbreak have no chance to install custom ROM because the bootloader is locked ?
Sorry, I'm pretty much confused atm about rooting the Arc.
My understanding is unlocking the bootloader does not give you root. Even those with unlocked bootloaders must root using either ginger break or the other method.
Having the bootloader unlocked will allow for installing custom roms though, when recovery is sorted. Those of us with locked bootloaders will have to hope for a workaround at a later date.
As for warranties...who knows on this one. SE have allowed the unlocking of bootloaders saying it "may" void warranty. Theres nothing to say rooting will void it. Personally I think the only way you will void it is if you brick it whilst fiddling with it. I think any hardware issues will be sorted regardless. (but thats my opinion, dont take it as gospel)
Rooting is rooting, it doesn't really matter what the mechanics of it are, if it's successful then the outcome is the same.
As for the two methods, yes, GingerBreak seems to be the simplest so for most people there's really no reason not to do that. If it fails and you have a handset you can unlock the bootloader on, then you can always do it the other way if need be.
When it comes to custom ROMs, there's a good chance that having an unlocked bootloader will be a requirement, to begin with at least.
It's possible that someone will find a way to offer custom ROMs for locked bootloaders but it's just more work.
if the buutloader remains unlocked your phone can ALWAYS be repaired through seus, the bootloader needs to be unlocked for the phone to be bricked . also flashing of custom roms may not require the bootloader to be unlocked - as is the case with the x10. as far as i know though the bootloader needs to be unlocked to flash new kernals but there is a workaround that for the time being with the ability to flash the various basebands. my bootloader will remain locked for the timebeing - its a sure failsafe if anything goes wrong
Thanks for the replies everyone.
I had this concept of "If you don't root your phone, you can't install custom ROM" and "If your bootloader is locked, you can't install custom ROM" before I found this Gingerbreak rooting method. (i.e. boot loader unlock -> can root -> can install custom ROM)
But just before it was conflicting because with Gingerbreak root your phone, but it seemed to me that you can't install custom ROM because the bootloader is locked. However they said "If you root your phone you can install custom ROM".
So for this time being, taking out the question whether custom ROM (which no one yet to make it for Arc) can be installed, I think it's safe to say : "Gingerbreak rooting with busybox installed gives you the same capabilities to bootloader unlocking + fastboot flashing", right?
more or less......
x10 was never unlocked bootloader，how many custom ROM out there？
cheers
Sent from my LT15i using XDA Premium App
ArcOnFire said:
"Gingerbreak rooting with busybox installed gives you the same capabilities to bootloader unlocking + fastboot flashing", right?
Click to expand...
Click to collapse
Not exactly. You can't flash custom .imgs via fastboot if you don't unlock the bootloader.
And I don't understand why people think that phone can be totally bricked if you unlock the bootloader...
sorry to say that，unlock bootloader seems waste of wait of time，if gingerbreak works
Sent from my LT15i using XDA Premium App
blagus said:
Not exactly. You can't flash custom .imgs via fastboot if you don't unlock the bootloader.
Click to expand...
Click to collapse
Well... yes, I already thrown that factor out when I asked my question.
But looking at the history, is there any case a custom ROM can be installed on a phone with bootloader still in locked state?
This is AFAIK
SE uses locked bootloaders for three reasons
1- A secure place to put DRM certificates.
2- A secure place to SIM lock the phone
3- A secure way to forbid modifying the software, as the bootloader will require a signed software in order for it to boot it ( If I'm not mistaken this is the problem with X10 unlockable bootloader as it's just hard to sign an image, correct me if I'm wrong ). the signed software thing is meant to be for not bringing bad software that may damage the phone
After SE saw that a lot of peoples want to install custom ROM's into their phones without too much hassle and a lot of them understand the risks of this so they decided to make it possible to unlock the bootloader but they want it to be the right way...
1- First the DRM certificates will be deleted as installing custom ROM's with exposed DRM certificates can bring serious legal problems to SE ( as this will mean the ability to save a digital unprotected copy of a DRM protected media )
2- SIM locked phones are excluded from this bootloader unlocking as this can make it easy to unlock the SIM lock so this will put SE in a bad position between operators..
3- As the main reason for unlocking the bootloader is installing custom ROM's and this is what the community want's SE made a bold statement here that doing so will violate the warranty as SE can't guarantee what a custom ROM may do to the phone...
but x10 has recovery
Sent from my LT15i using XDA App
The Arc isn't the X10.
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
justbenice said:
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
Click to expand...
Click to collapse
How many time passed from exit of ARC???
justbenice said:
Boring. This is a first time i use SE phone. I think this is also a last time. I will come back with HTC. There are no custom and no one with cook custom rom for SE device already
Click to expand...
Click to collapse
sorry ... I have from only 3 weeks the Arc and already have bootloader unlocked and Root ...
I think you're just a little patience
From what I gather, they can't refuse a warantee repair if it is a hardware fault, not caused by the unlocked software (as it is a problem with their manufacturing, and therefore their fault), but if you mess your phone up with something due to the unlocked bootloader they can (for example, you overheat your CPU with an overclock or something).
chriscpritchard said:
From what I gather, they can't refuse a warantee repair if it is a hardware fault, not caused by the unlocked software (as it is a problem with their manufacturing, and therefore their fault), but if you mess your phone up with something due to the unlocked bootloader they can (for example, you overheat your CPU with an overclock or something).
Click to expand...
Click to collapse
That's what I heard too. As long as you didn't mess with you phone in some way, they can't prove that the hardware fault came from the modified software and should therefore repair your phone nonetheless. I guess that's why they say that unlocking the bootloader MAY void one's warranty.
have rooted thro' gingerbreak - but am am getting frequent random reboots. while calling or recieving. can anyone help me with this.
Around last week when I first got my carrier locked Xperia PLAY, I purchased a network unlock code which I was able to unlock it with. So, then I flashed it with the UK Generic .184 FTF file with FlashTool to get rid of all the junk that my carrier included with it and rooted it using the GingerBreak APK.
Now, my question is, since I've network unlocked my PLAY, completely debranded it and rooted it, would I be able to unlock my bootloader now? From what I've read, since my device was originally locked from my carrier, that it never had Fastboot installed on it, which is needed to unlock my bootloader. But I also read that being able to unlock the bootloader on my Xperia PLAY shouldn't even matter because it's already set to S=OFF. Could someone please enlighten me on this?
You can't unlock your bootloader with the current method, it depends on two things: can your phone connect with fastboot when in bootloader mode AND is your IMEI number registered with SE to get the required unlockcode.
No you can only unlock GSM phones ie sim fee none network locked ones, unlocking the sim carrier wont count sadly
svenk919 said:
You can't unlock your bootloader with the current method, it depends on two things: can your phone connect with fastboot when in bootloader mode AND is your IMEI number registered with SE to get the required unlockcode.
Click to expand...
Click to collapse
Yes, I went to their How-To page on the SE Developer's site and was able to get an unlock code by providing my IMEI and other info. When I try to detect it with Fastboot and my PLAY in bootloader mode, Fastboot just hangs at <waiting for device>.
waz000000 said:
No you can only unlock GSM phones ie sim fee none network locked ones, unlocking the sim carrier wont count sadly
Click to expand...
Click to collapse
Cool, thanks for confirming that!
But does it even matter if I'm able to unlock my bootloader? Because I've read somewhere that the PLAY's are set to S=OFF.
From my understanding an unlocked bootloader is necessary for costum roms, if you're content with root and themes unlocking the bootloader won't be that important to you I guess.
I'm pretty content with being able to install custom themes with it only rooted. But I want to be able to overclock it, and that involves flashing a custom kernel to be able to do so, correct?
Flava0ne said:
I'm pretty content with being able to install custom themes with it only rooted. But I want to be able to overclock it, and that involves flashing a custom kernel to be able to do so, correct?
Click to expand...
Click to collapse
afraid so (as it stands atm) there probably will be a way to flash without an unlock at some point though.
Is it possible to re-lock and unlocked bootloader?
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Reason I ask is because I had it unlocked, got an OTA update from Verizon for kitkat, and soft bricked my phone. Got stuck in a boot loop with the unlocked bootloader warning message.
I just flashed back to 4.0.4 using RDS Lite 6.1.4. Id like to reset the boot loader to locked before updating to kitkat again.
It's not possible to re-lock. I've updated to KK and can confirm that the BL is, in fact, still unlocked.
I have read somewhere that when you unlock the bootloader, it actually physically blows some kind of physical fuse. or maybe I miusread it.
Someone had made a special logo.img you can flash to get rid of that message.
Although if you really want a locked BL phone, I'd be more than happy to trade you.
MxPhenom 216 said:
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Click to expand...
Click to collapse
Not that it helps, but in Australia, we do not get the nasty warning message after unlocking the bootloader. And I think that the phones are actually sold with an unlocked bootloader.
GnatGoSplat said:
Although if you really want a locked BL phone, I'd be more than happy to trade you.
Click to expand...
Click to collapse
:laugh:
For work I have to use mobileiron, which detects everything from root to the unlocked bootloader. I am not sure if it simply detects the unlocked bootloader or detects because of the warning that comes up, I would guess its the latter.
So not only can't I root, I can't unlock my bootloader in the current state. At the very least I would like to enable wifi tether, and I would do that through TWRP but then I can't unlock my bootloader. So way to relock without wiping.
So I guess the question is for people who don't know about MobileIron is will we be able to unlock the bootloader without setting off any other options? or is there way to at least edit build.prop without root or unlocked bootloader?
I guess ideally if I could root without unlocking the bootloader then unroot that would solve my problems. Thoughts anyone?
Here is a thought, although it might fail. You could unlock your bootloader, boot TWRP without flashing(fastboot boot twrp-rgvrg.img), make your changes, then boot back into the bootloader and relock it.
Still can't say for sure it would work and it will virtually guarantee your userdata be wiped.
Buy a second phone for work related purposes
I'd never spend so much on a phone just to let my company lock it down
You could always test out various configs and see what trips the software or not. You might be able to keep TWRP and root just turned off via supersu and everything work. Similar to android pay. You might not even be able to unlock the bootloader. Anything in between in possible.
Regardless it is pretty trivial to go back to stock and get everything locked back up again. So there is little risk in trying.
If it were me I'd try root and see if it worked. No? Ok, try to disable root with supersu. Will work or not. If not then make your host file edits for adaway and such and then completely remove root. See if that works.
You can also try to unlock the bootloader now as stock and see if it impacts the software. See exactly where it trips and prevents you from using it. Then work from there.
If nothing works, go back to 100% stock and lock the bootloader again. At least you gave it a go and had some fun for the evening. If I had to guess something in between will work and you can work around the limitations.
Now that it seems allot of progress is being made on rooting the s7. Does that mean that the bootloader has been unlocked.
Since having a unlocked bootloader is the only way new firmwares can be flashed, isn't this the only way this could have been done,
2 VERY different things. There MAY eventually be some ways through FlashFire but not as of yet