Hi new Sony user here and I'm just curious as to why we can't use initd scripts to work around this locked boot loader? I owned a Droid 2 global and Motorola has locked boot loaders on them and the devs just used initd scripts to work around this. That is how the Droid 2 guys got cm7. Figured I'd ask and throw the idea out there. I mean it'd give us cm9 or cm10 for now til the locked boot loader issue is figured out.
Afaik initd needs kernel support and the stock kernel doesn't support initd. Therefore, you need a different kernel, and different kernel needs unlocked bootloader.
Sent from my LT30p using xda app-developers app
You could always try to use the pimp my Rom app from the play store to enable init-d. Don't know if it will work though.
You WILL need root for this.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button
Yes it does
crazymister said:
You could always try to use the pimp my Rom app from the play store to enable init-d. Don't know if it will work though.
You WILL need root for this.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button
Click to expand...
Click to collapse
When you add init.d it also has a verify button to make sure it has worked and also you can check the build.prop
Init.d works on locked bootloader
Envoyé depuis mon LT30p avec Tapatalk
There are limitations to how far you can go with Second Init. If any changes to the kernel are needed you're hosed - and Jellybean requires kernel changes for vsync at a minimum. It also means any kernel issues can't be fixed. Also, as time progresses, bootloader lockdown usually becomes stronger - and Sony's locking solution is quite strong.
It's a ****-ton of work and horrible hacks (I don't think any device using a Second Init approach has EVER received official builds since CM7) which are unnecessary on the majority of T units. Some of us (including myself) refuse to work with devices which have non-unlockable bootloaders on principle.
Sucks for the AT&T TL users, but that's why I'm leaving AT&T. I'm tired of them mangling devices.
Related
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
mp9_sit said:
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
No not at all. For 1 our device isn't supported and for 2 we have already figured out a workaround to the locked bootloader
Sent from my XT860 using xda premium
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
leerpsp said:
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Apparently it got posted and pulled and I think reposted. Android police or droid had the supported device list
Sent from my XT860 using xda premium
If you look here (https://motorola-global-portal.cust...sion/L3RpbWUvMTM0NTI1NDk1NC9zaWQvU3VDYlRZM2w=) only the Photon, Xoom, and RAZR dev can be unlocked. And the RAZR dev should be unlocked anyways... it IS the dev edition. This means nothing, and with working Kexec, I don't see why we'd even change since everything now is being written for Kexec and development for this phone ins't exactly active, we essentially have 2 people developing new things for it. There are more GNex kernels than there are D3 devs.
jesusishere said:
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
At this point what difference can it make. Either way we can load a kernel, just need the kernel to be built
Sent from my XT860 using xda premium
Kexec makes this pointless. The reason development stopped initially was because making a ducati binary work with the Gingerbread stock kernel for ICS was impossible. Also doing a kernel module custom was too. Now even though we have ducati and it won't work for the camera we can do other things like Chrome. Also, Hash was going to modify his custom kernel for a camera driver for us as his next approach. This gives us options we didn't have before. The fact that we use Kexec is better because it is flashed on top of the kernel existing at first and it is just a ROM. If it is a bad flash all you have to do is just reflash from Safestrap. We couldn't do that before.
Sent from my xt862 using xda app-developers app
So I'm ruining the jb ota and i like to run my phone with the processing power cut in half. To this point I've been using setcpu, but since the update it goes back to 1.2ghz every time i turn the screen off or open another app.
So I'm wondering if there is another app that works as well as setcpu or if someone can tell me what I'm doing wrong without changing ROMs.
Thanks ahead of time
Sent from my XT894 using that xda app
Its a problem with locked bootloader/stock kernel.... you can try system tuner pro but it might do the same thing... but I like the tuner...
Sent from my DROID4 using Xparent Cyan Tapatalk 2
You need a custom kernel that's usually included with the CM/AOKP roms that is loaded via kexec, or wait for Myfishbear to make flashable oc scripts which will allow you to underclock in Setcpu.
Never had a problem with the stock kernel or locked boot loader before, but I'll try that tuner. Thanks
Update: tried tuner, no dice. Guess this new jb kernel is to blame /:
Sent from my XT894 using that xda app
Hi guys..
I was an owner of samsung galaxy s2(i9100) and then I moved to the amazing xperia TX.
It is an amazing device as compared to galaxy s2.
However,i do miss the customization choices of the s2 as the TX does not has sufficient developer support as the s2.
Many xperia TX owners root the phone but fear unlocking the bootloader as they fear loosing drm keys,bravia engine,track id etc so they stay away from unlocking the bootloader.
So I thought to create a thread where we can discuss what to do in our devices after rooting so that we can get the most out of our devices
We can have some discussions on root apps,some mods without unlocking the bootloader,system mods etc..
Sent from my LT29i using Tapatalk 2
Want cm like themes on your Rooted TX?
This is a great mod that I came across.
All credits go to the developer of the "xtheme engine"
http://forum.xda-developers.com/showthread.php?t=2219999
Sent from my LT29i using Tapatalk 2
Superior power saving features by using apps such as Greenify and One Power Guard.
Extensive backup and restore functions using Titanium Backup.
Manual system modifications by having access to the root directory. Endless possibilities
Also I used to think that there isn't much development here compared to the previous Samsung phone I had. But to be honest, I am quite happy with the stock Rom. So I don't complain. Occasionally I shift to a CM 10.1 release but then come back to my stock rom. So there is actually not much that devs can do to improve an already full featured rom. This is my opinion.
Hi,
U r right..
When I used a samsung,i always used a sony theme on cm.
But now on sony stock rom,i never felt the need to change to any other rom
Sony's jelly bean is the best...
Sent from my LT29i using Tapatalk 2
Yeah, XthemeEngine is great, if you haven't tried already, try it.
Tapatalked from my bricked TX
After root - install TB and remove blotware.
Sent from my LT30p using xda app-developers app
Anyone here tried "pimp my rom" from play store?
Sent from my xperia TX via xda premium
Com' on guys...if you post your experiences,it will be beneficial 4 all....
Sent from my xperia TX via xda premium
i tried pimp my rom, but only used the touched velocity something.. i feel my touch ain't that responsive, not due to the kernel though , but maybe due to the screen guard.. not sure
arctic02 said:
i tried pimp my rom, but only used the touched velocity something.. i feel my touch ain't that responsive, not due to the kernel though , but maybe due to the screen guard.. not sure
Click to expand...
Click to collapse
Hi mate,
Just dont apply tweaks that u "think" would make any effects...apply the the tweaks for the feature u want on your phone..
Sent from my LT29i using Tapatalk 2
Funny thing is, the majority of mods on pimp my rom, we already have on our xperia phones anyways, so there isn't really much to do with it in the end
As for what I do after rooting, I install TB and remove all bloatware, and then leave it as it is because there's not much need for extra mods/tweaks and all that
[email protected] said:
Hi mate,
Just dont apply tweaks that u "think" would make any effects...apply the the tweaks for the feature u want on your phone..
Sent from my LT29i using Tapatalk 2
Click to expand...
Click to collapse
hello..
what do mean?
arctic02 said:
hello..
what do mean?
Click to expand...
Click to collapse
Hi,
I mean just apply the mods for the changes you "need" on your device.
For example,if we apply the mod "pimp my beats" we can get good quality audio output from our headphones.
I have bravia engine 2 and beats audio installed in my TX and they work really well..
Sent from my xperia TX via xda premium
SammiSaysHello said:
Funny thing is, the majority of mods on pimp my rom, we already have on our xperia phones anyways, so there isn't really much to do with it in the end
As for what I do after rooting, I install TB and remove all bloatware, and then leave it as it is because there's not much need for extra mods/tweaks and all that
Click to expand...
Click to collapse
Hi mate,
I agree with your point..but there are still many mods for pimping our rom
We can have build.prop tweaks,init.d support etc.
Me too have not made many tweaks in my TX with "pimp my rom" but there are still many mods which we can apply...
Cheers!!
Sent from my xperia TX via xda premium
Well like the title says I was wondering if we might be able to use kexec to boot cm on our devices. If I'm not mistaken that's what is used for the droid 3 to boot cm
Sent from my SAMSUNG-SM-N900A using Tapatalk
This has been discussed many times here and in multiple other device forums. At this point, it has not been implemented into SafeStrap. I am not sure if it is possible or not, nor do I know if hash is working on putting it in. He is aware of it though.
Sent from my SM-N900A using XDA Premium 4 mobile app
kexec uses a hijacked kernel module to direct to a different kernel placed on the SDcard. Sort of like how SS works, but a bit differently. All SS does is direct the kernel to a different image. Kexec needs a hijacked module to load an insecure kernel. While this sounds easy to implement, trust me it will most likely never happen with the note 3. The problem is that the note 3 doesn't have any modules. And don't ask about inserting them, because the kernel will not run them. They are completely disabled in this kernel. That property is set when the kernel is compiled, so with it being disabled, we cannot enable it, and we cannot hijack the modules, because they are completely disabled.
Thanks for your informative reply. Just thought id ask
Sent from my XT862 using Tapatalk
Hello,
Yesterday I picked up a T-Mobile Z1S and rooted it via TowelRoot, installed a custom recovery, and manually debloated the /system. Which is all good, however, I want to know if any of the ROMS here in this forum can be flashed to it, considering the Z1 and Z1S have the same processor. Anyone have experience doing this? Thanks.
Sent from my C6916 using Tapatalk
Just Wait On It
troby86 said:
Hello,
Yesterday I picked up a T-Mobile Z1S and rooted it via TowelRoot, installed a custom recovery, and manually debloated the /system. Which is all good, however, I want to know if any of the ROMS here in this forum can be flashed to it, considering the Z1 and Z1S have the same processor. Anyone have experience doing this? Thanks.
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
*In My Drake Voice* Just Wait On It ;P
Locked bootloader typically means it will be hard to flash custom ROMs until a way to bypass it or unlock it becomes available even with root.
I could not get towel root to work with my z1s. You just ran it and had root?
I have tried a couple yes with no luck.
troby86 said:
Hello,
Yesterday I picked up a T-Mobile Z1S and rooted it via TowelRoot, installed a custom recovery, and manually debloated the /system. Which is all good, however, I want to know if any of the ROMS here in this forum can be flashed to it, considering the Z1 and Z1S have the same processor. Anyone have experience doing this? Thanks.
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
Sent from my C6916 using Tapatalk
Actually, there are no roms yet, but you can deodex your current rom http://forum.xda-developers.com/showthread.php?t=2783626
I rooted a little different than others. First I used the jcase method, installed the dual recovery and installed SuperSU. From there, I installed TowelRoot and ran it, rebooted, then flashed the latest v2 SuperSU. Sounds a little redundant I know, however, now I have permanent root, and also read/write permissions in /system, even after reboot, without running those ADB commands all the time.
Sent from my C6916 using Tapatalk
I'll try to get a good system dump from my Z1S, and release a ROM that doesn't affect the kernel, which should be able to be flashed via recovery. Since the ROM will only be /system mods, it shouldn't matter if the boot loader is locked still. Inform me please if I'm mistaken.
Sent from my C6916 using Tapatalk
troby86 said:
I'll try to get a good system dump from my Z1S, and release a ROM that doesn't affect the kernel, which should be able to be flashed via recovery. Since the ROM will only be /system mods, it shouldn't matter if the boot loader is locked still. Inform me please if I'm mistaken.
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
I think that should be right, I thought the bootloader only prevents booting if the kernel isn't supported/allowed
troby86 said:
I'll try to get a good system dump from my Z1S, and release a ROM that doesn't affect the kernel, which should be able to be flashed via recovery. Since the ROM will only be /system mods, it shouldn't matter if the boot loader is locked still. Inform me please if I'm mistaken.
Sent from my C6916 using Tapatalk
Click to expand...
Click to collapse
No, you are correct.
As long as it runs on a stock kernel then you can have a locked bootloader. the whole of the development section is full of roms like that
The original development section is for mods/roms that need a custom kernel or a non stock boot.img
gregbradley said:
No, you are correct.
As long as it runs on a stock kernel then you can have a locked bootloader. the whole of the development section is full of roms like that
The original development section is for mods/roms that need a custom kernel or a non stock boot.img
Click to expand...
Click to collapse
does this mean i can flash a rom with stock kernel?
has any one been able to create a back up nan?
This thread caught my attention. Has anyone had luck with flashing a rom with stock kernal using dual recovery? I will be attempting this later in the evening and I will post my results
After multiple issues I was finally able to get dual recovery with root last night. After sifting through the forums looking through roms, all of them required different firmwares, will the c6916 take firmwares from other z1 devices. If so then as the above poster said, there is loads of roms in the development section that will worked with locked bootloader. The only reason I ask is the posts list different device model numbers and the c6916 is not listed on any.
I would be very careful I hope you have insurance.
Kk update will come soon.
Sent from my C6916 using xda premium
All attempts were failed attempt, next I will try to make the phone belive it's a different model and then try a refresh.
Sent from my C6916 using XDA Free mobile app
You need to learn how to port.
Did you even get to bootinmation.
No cm will boot with locked bootloader.
Sent from my C6916 using xda premium
Our devices have a 4.3 kernel that cannot be changed due to the bootloader being locked. Flashing a 4.4.X ROM will most likely not boot due to needing a 4.4 kernel as well. However, 4.3 ROMS modified to not flash the kernel, just the /system should boot fine.
When trying to boot another custom stock rom make sure you change the.
1. Libandroid-runtime-so.
2. Libandroid-servers-so.
Without not changing these it will not usually not boot up.
Sent from my C6916 using xda premium
Any update on the rom?
In my phone configuration it says
Bootloader unlock allowed: yes
Does this mean I can unlock my bootloader?
I have xperia z1s from tmo..
smxaz61 said:
In my phone configuration it says
Bootloader unlock allowed: yes
Does this mean I can unlock my bootloader?
I have xperia z1s from tmo..
Click to expand...
Click to collapse
Your signature is z2 not z1s stop it!
Sent from my C6916 using xda premium