Related
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
Sounds little bit like Chinese for me but hope you can get a break through and goodluck for all who trying to make it for us an even great phone
ok, i have had my jellybean semi running and oneX rom running, both not very functional, as most hardware did not work well.
the lgdrmserver kept crashing on me as well, but probably less important.
the solution i made was the early boot used the original libraries from /lib from and vendor/lib , so i simply mapped the 2 files in /lib with a symlink to the /system/drm folder and ran the wallpaper binary and it worked fine.
secondly changed a vold binary to be a little script, that
1: bind'd new libraries for drm in drm2 folder (mount -obind drm2 drm) so the new booting os would get related files.
2: start vold
and the workaround seemed to do just fine for the drm security check.
IF it fails during regular boot if you unintentionally copied over the files, do not worry. booting into safe mode (keep VOL UP pressed and press power) you can connect with a shell and bypass the check, and fix your failure and reboot.
Hi
Is DRM checking forced from kernel?
Can we live without it?
no, its called from init.d
Dexter_nlb said:
Lets see if we can get
- Locked bootloader
- Custom rom security issues
and maybe other security related problems in one development thread and how we make apps to get around this
I take the lead for now, since i started testing custom roms (JellyBean) right now.
and the DRM check at bootup is important to get around, otherwise we end up, having to restore a v10 image again and again, too often.
i suspect that it can be done using a bind folder. but lets see where this takes us.
just update with other issues seen.
Click to expand...
Click to collapse
It is allways exciting to see people like you fellow.
Curious, courageous, openminded, wise and most of all doing all without expecting anything.
Success on your way..:good:
Dexter_nlb, You're a hero :good:
When will be released some beta?
since we have root, shouldnt init.d be accessable and easily modifyable?
The Troll said:
since we have root, shouldnt init.d be accessable and easily modifyable?
Click to expand...
Click to collapse
its part of the boot.img (ramdisk), so not really, but the 2nd-init makes it possible to make a new ramdisk and start it. but its only ramdisk, not the kernel, which remains static.
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
The Troll said:
downgrade mode?
sorry, im a htc user thinking of buying this phone.. *since s3 isn't tegra, not thd games and one x kinda sucks with the lack of sd card and stuff..*
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
oh forgot to meantion, this can brick ur device.. actually downgrade mode itself is a bricking method.. so i'd be careful *assuming this method is true for gs as well*
Click to expand...
Click to collapse
nah, we haven't nothing to lose... someone should try it
The Troll said:
but htc has a dorwngrade mode.. 2 exposed connectors close to the camera.. short circuit them to access downgrade mode.. and then flashable though linux..
if im right, that should give u open access to bootloader..
evo 3d cdma used this method to get s-off.. as in bootloader unlocked and accessable with all write restrictions removed on all partitions..
Click to expand...
Click to collapse
i believe you reference a different hardware platform not Nvidia based. o4x is nvidia tegra3 and different from omap and other platforms security wise.
can you link to the tegra fuse , you reference here? (fuse is a connector which will break the firmware open and full access granted, but can also cause firmware to not load, since fuse is broken)
reas0n said:
nah, we haven't nothing to lose... someone should try it
Click to expand...
Click to collapse
flash image GUI..
someone rooted should try that first..
also, unlimited.io <--- website.. for details of the downgrade mode trick..
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1491107
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1627917
the basic idea of this is 2 connectors close to the camera.. short circuit them to switch the phone to downgrade mode *QHSUSB_DLOAD*.. bricking the device and mounting all partitions as read and writable.. then using linux to find the right partition to flash/dump the hboot *the bootloader*
at the end, if it uses fastboot/adb, i dun think this will be too different from the evo 3d..
try it.. but dont say i didnt warn you..
im not sure its a fuse, its more of a reset?
also, i dont exactly have the phone *yet* so i cant tell..
but for the 3d, its exposed.. 2 holes in the back under the cover, next to the camera..
http://unlimited.io/juopunutbear-public-beta-0-1/instructions/evo-3d-cdma-shooter/
or you can find a schematic of the phone itself..
if you dont mind me asking, whats the reason for the lack of devs?
this is an excellent phone..
is it the extreme security?
iphone got a jailbreak too :/
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Dexter_nlb said:
ok, this is a QUALCOMM solution, not for our tegra3 based platform
Click to expand...
Click to collapse
how did one x get the kernels running?
**edit.. nvm.. htcdev.. forgot..
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Dexter, the One X solution is for Tegra3 devices. The QUALCOMM-Device is called HTC One XL. So if the chipset is nearly the same, there must be a solution? If I could code anything, I would. But I cannot
Hilmy said:
Hope you guys can pass by all that anoyeingsecurity. Would like to buy that phone but without real controll over the hardware aand custom rom community i would seariously reconsider buying it...
Click to expand...
Click to collapse
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
aremcee said:
Instead of trying to bypass, people should be asking LG for an unlock mechanism. I've been talking to them about this for over half a year, and today they still feel there is no demand for it (unlock tools)
Show of hands: How many people here have actually e-mailed LG asking for an unlock procedure, for this or any other of the current locked generation?
Click to expand...
Click to collapse
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Dexter_nlb said:
do you have the mail address we can use? then we can engage a mailrobot to send them 10000s of mails regarding the unlocker, and maybe they will follow asus and motorola/google on this one.
Click to expand...
Click to collapse
I'd rather not forewarn them by asking for a contact for this
My personal opinion: a mailrobot would be a bad idea, they'd just filter it out. Actual users, with actual devices (serial numbers in the message and all that) would carry much more weight than just generic "gimme". From experience... petitions don't work, either, unless they hit visible news outlets;
My suggestion would be to hit a support contact, consistently (instead of dispersing the message to random contacts); most companies will escalate any issue given enough occurrences of it. On the other hand, I can't find contacts besides the country-specific ones at http://www.lg.com/global/supports/service-sites.jsp ...
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
Samsung GS4 locked bootloader. HELP
xAjCx said:
Since we got the new official 4.3 update, that means we got a new bootloader with the update right? If so, does anyone know if anyone has tried to get this unlocked even though we had no success with 4.2.2? I don't know if I can help get it done or not cause I don't have much background with actually unlocking it but I'm willing to help if possible. :fingers-crossed: Might run into problems with KNOX though.. idk.
Click to expand...
Click to collapse
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!
drakul123 said:
Hello,
I bought an unlocked Samsung S4 Active I537 from ATT, but I use it in Canada.
I have tried to use Goomanager, TWRP manager, safestrap, quickboot; but the phone goes back to the normal bootloader.
When I try to install a ROM from my SD card (by normal bootloader) it does not do anything at all; just stays on the same screen for a minute then reboots normally.
I am guessing the bootloader isnt unlocked.
What tips you got?
Thanks!
Click to expand...
Click to collapse
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
I learned that the hard way
Devo7v said:
The bootloader is still locked and currently there's nothing you can do about it. If you want to follow the progress read through this thread.
Click to expand...
Click to collapse
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:
drakul123 said:
In advance: sorry to sound bitter; but wasn't fun how useless can be a device with a locked bootloader.
So the google apps stopped working and the whole thing is pretty much gone to hell/
IF samsung hadnt locked it so good (in a non-compliment kind of way) I could just install a new ROM and done, even better than with their weird touch wiz. But they locked it well so the phone is pretty much an average control remote in present time.
All samsung devices are locked like this one?
or that's their only garbage version ?
If that's the way they roll... no more Samsung phones ever for me.
There is a reason I stopped buying apple stuff... I dont like buying a device that is limited not because of its hardware, but because of the useless things a brand adds to make it useless. (like locking the bootloader)
Anyways... I am considering buying another phone for now.:silly:
Click to expand...
Click to collapse
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
Devo7v said:
The device is far from useless, you can still root and flash custom ROMs, just not CM or AOSP based ROMs. I've posted all the stock ROMs and instructions on how to flash them, so if you do mess up your phone you can always start from scratch.
To answer your question about all Samsung phones, pretty much all Samsung phones from the GS3 an later that were sold by AT&T and Verizon have locked bootloaders. Nearly all the international versions as well as T-Mobile versions are sold with an unlocked bootloader, so you don't necessarily need to boycott Samsung, you just need to be more careful when purchasing a Samsung phone in the future.
Click to expand...
Click to collapse
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!
drakul123 said:
Hey there
Where did you post these ways of re installing all?
I saw many posts around here about reinstalling but I couldnt move on after they required the Samsung to do something through the bootloader.
Also there was a post to uninstall using Odin, but the post had missing files so couldnt do it.
Keep me posted!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2835481
Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.
pfhastie said:
Hi there
I will try and keep this as short as I can. I have an Xperia T which I recently recovered from a bootloop thanks to the helpful folks here at XDA. The issue arose because I tried to flash a custom ROM without unlocking the bootloader (I rooted using Doomlord's Toolkit). I have since done a lot more reading about the process, but it is nearly impossible to read every related link on the internet, so I'd really appreciate if someone could answer the following two questions before I attempt to flash a custom ROM again.
Fortunately, my bootloader is unlockable, although I am currently using the stock firmware without any changes.
The first thing I want to do is backup the TA Partition so I can reinstate Bravia etc once I am happy with the custom ROM. I thought I had backed this up using the Android Flash Tool 0.9.13.0, but I have since read that this doesn't backup the TA Partition in full. For this, I need to use Backup-TA 9.10. My question about this is, do I need to use both the Flash Tool and Backup-TA in order to fully backup and restore the TA Partition, or is Backup-TA sufficient on its own? Also, I don't see an option to restore the backup created in the Flash Tool. How is this done?
The second question I have is, can I unlock the bootloader without going through the formal Sony bootloader unlock process? I have no money to replace my phone and it is under warranty until October this year so I do not want to jeopardise this if it is not possible to unlock the phone without involving Sony. The Android Flash Tool 0.9.13.0 provides a Bootloader Unlock option, yet I have read that it is not possible to unlock the bootloader without informing Sony. If I am able to use the Flash Tool to unlock my bootloader, I have downloaded a file called "LT30_relock_bootloader.ftf" which claims to relock the bootloader should I ever need to do so for the purposes of my warranty, so I have no issue unlocking the bootloader provided I do not need to go through Sony. So, is the information I am currently armed with correct? And is using the Android Flash Tool the best method to unlock the bootloader (so I can install a custom ROM)?
I intend to backup the TA Partition, use Doomlord's Toolkit to root my device, then unlock the bootloader (if possible), then install CWM v8 to flash a custom ROM.
Any clear advice would be greatly appreciated, as ever.
Click to expand...
Click to collapse
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.
St.Jimmy90 said:
I haven't read your post completly, but you can't install ANY custom rom if your bootloader is unlockable. You can't install a custom kernel. So all your efforts are worthless....
Click to expand...
Click to collapse
why would u answer the question without understanding what he wrote ? and the fact remains that u admitted that u didnt read it all the way so its pointless to reply jus like u may be saying its pointless for me to reply to your post and not answer the question
Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.
pfhastie said:
Yes, just to confirm my bootloader can be unlocked (unlike some Xperia T variations), but is currently locked. And I am enquiring as to whether it can be unlocked without contacting Sony and how best to go about it.
I would really appreciate some help as I am disinclined to do anything on my phone until I can solve the issues and questions outlined above.
Click to expand...
Click to collapse
no know not of any other ways but sony and flashtool atm
1: Use backup-TA ONLY. You won't be reinstating it and getting back Bravia while you are using a custom ROM though You restore this backup only if you want to go back to stock and restore Bravia/send phone in for service.
2: You need the code from the Sony service. However just because you got the code, doesn't mean you used the code so won't wreck your warranty on its own. You restore the TA backup before your send away under warranty and then they don't even know you ever unlocked in the first place
Don't flash any .ftf to relock your bootloader, thats what you make the TA backup for. Any other method to relock bootloader will show relocked instead of never unlocked status you need for warranty. TA is only thing that will restore Bravia also.
pfhastie said:
Hi there
I will try and keep this as short as I can./QUOTE]
Click to expand...
Click to collapse
nlooooo said:
I think that you have a lot of problems with English, he has phone with UNLOCKABLE bootloader, which means that it CAN BE unlocked...
This is not your first post where you're blowing away people not knowing what they are writing.
Click to expand...
Click to collapse
Doh man, usually I understand everything but it seems I have to read more carefully..... And I shouldn't try to read something while talking to a friend. It won't happen again
Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?
pfhastie said:
Thanks for that, mdc1983uk, I understand about the TA partition now.
My only remaining question is, if I need the Sony code to unlock the bootloader, what happens when you use the Android Flash Tool 0.9.13.0 Bootloader Unlock option? Does it still require you to get a Sony code?
Click to expand...
Click to collapse
As far as I know you need the code. Every phone gets an unique code created from your Imei
OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!
pfhastie said:
OK, thanks for the advice.
New problem: I upgraded to 4.3, now Doomlord's Rooting Toolkit doesn't work. Is there another way to root 4.3? I can't use Backup-TA unless device is rooted.
I swear, I can understand why it sometimes seems a little tetchy round here - every step of every path seems to lead straight into a brick wall!!!
Click to expand...
Click to collapse
What if you flash Darklords pre rooted and deodexed rom?
http://forum.xda-developers.com/showthread.php?t=2647459
Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.
pfhastie said:
Thanks for that, I appreciate that would work, but I still haven't come close to being able to successfully flash a single ROM and I just don't have the time or mental strength required to work my way through every ball-breaking step. No matter how simple it seems, there will be a problem.
Unless there is a simpler solution, I shall just keep watching these forums hoping the mighty Doomlord releases a new Toolkit or another method comes to light. Surely within a few weeks there ought to be another solution given all the high IQ bods on the case.
Click to expand...
Click to collapse
don't bank on the devs coming up with a new root method for 4.3, currently there isn't a need for one since we can all root on 4.1 then unoffically upgrade with a pre-rooted firmware, this is a relitevly simple procedure and can be done within an hour
It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.
pfhastie said:
It wouldn't be an hour for me, unfortunately. It would likely be three solid days of profound agony and disturbed sleep. Even tonight, it took me hours to connect to PC Companion to run a fresh copy of the firmware and the thread related to the 4.3 pre-rooted firmware suggests there are still a few issues. The great and mighty Doomlord's Toolkit takes seconds and works perfectly. I am sure I am not alone in my concerns.
Click to expand...
Click to collapse
+1 on what @matt4321 said in the previous post. Downgrade to 4.1.2, root, and then backup your TA partition with Backup-TA, flash CWM v8, and unlock bootloader if so desired.
If you want to be on 4.3, once you're unlocked, and after flashing any Official 4.3 FTF, you can then flash a kernel that can be found in EXR leaked 4.3 thread which comes with CWM already included, and finally proceed to flash SuperSU in recovery.
The minute one of the Official 4.3 FTF's came out I flashed it and tried the kernel I just mentioned; it's been working fine, probably even better than the official stock kernel (even though it is based on a stock kernel, only with CWM, that's why you need to be unlocked), given that I don't have a single one of the bugs that people are reporting exist on the Official 4.3 Roms. Battery is at 40% and I am already at almost 35 hours on a single charge.
If you already have the FTF files, this procedure doesn't take more than 40 minutes, if you're comfortable with and know what you're doing.
I hear you and will very likely give it a shot as soon as I can find the time (if only this was my only concern). At this stage, I'd be inclined to use Doomlord's Rooted&Deodexed ROM as it doesn't require unlocking the bootloader, but it is still a long way around to get root for the 4.3 version I am already using.
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!
Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
pfhastie said:
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
Click to expand...
Click to collapse
Regarding odexing/deodexing, read this.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
Click to expand...
Click to collapse
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.
Antiga Prime said:
Well, the thing is you need to backup your TA partition, which is the only reason why you'd have to go back to 4.1.2, which lengthens the process.
Regarding odexing/deodexing, read this.
Obviously, in your case it's simple, since you have an XT and there are several custom ROMS that are currently being actively maintained for that device; you can do pretty much anything you want.
Others, like myself, have an XTX, and apparently none of the devs working on Roms actually have an XTX, so developing for it is a hit and miss. I tried CM11, and it was working flawlessly until I realized that half of the time the phone should be in deep sleep, it does not sleep due to kernel wakelocks. A battery that lasts 6 - 7 hours is no use for me. Therefore, my only option was to go back to JB 4.3.
The people who actually bought an XT have a wide variety of ROMs to choose from. On the other hand, those who have an XTX have about 3 or 4 ROMs (at the most), with the only one actually being maintained, is CM11.
Click to expand...
Click to collapse
Oh, I get you. Still, bit of a faff, isn't it? These devices will be old before they can be utilised perfectly.
Custom ROMS still have a way to go unless stock based. Although the stock 4.3 isn't flawless, its better for me than the 4.3/4.4 custom's running on a 4.1 kernel. Every i've tried comes with the proviso that you will suffer blue screens of death at random until Sony releases the 4.3 kernel open source for them to merge. Some guys are hardcore though and putting up with reboots and crashes is a normal part of the game as it's not a bug - they are waiting for Sony. There's also another huge issue (for me) of the speakerphone never working correctly at the Sony volumes. They have to turn the volume of the whole ROM down to compensate and this makes it hard to hear in a noisy environment, a frustrating bug for me which has hung around since 4.1. You can max the volume up with a file which someone did, but it breaks the speakerphone then so you can only have one or the other.
In a lot of ways I am one of those guys though, I do like to experiment and am comfortable with the processes but I always find what I flash causes me some frustration before long so I go back to stock. If I had the knowledge to help fix problems it would be a different story and i'd stick with custom but as I can't I don't really see the point until 4.3 sources come out and its all a bit more stable.
pfhastie said:
What I don't understand is, why would anyone comfortable with this whole process want to run 4.3 anyway when KitKat and supposedly better ROMs are widely available? Doesn't make sense. The truth is, the Sony interface is very well implemented already, and I'm beginning to think that better shortcuts and flashy sidebars are not worth the effort of trying to deal with flashing custom ROMs. I don't want a smartphone - or any computer - loaded with more utilities than apps that actually do stuff. That, I thought, was part of the rank old days.
I read about five web pages devoted to explaining what deodexing actually means and I still don't know, and probably never will.
I'll mull over the situation as I get drunk tonight!
Click to expand...
Click to collapse
i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)
paresh90 said:
i am deeply sorry if this is the wrong place or already been answered but i have spent almost 6 hours looking for the right solution.
so the story is i have a Z3 compact which is branded to Vodafone UK (not sure if it is relevant)
attached are images of my about page and the configuration page (where you dial *#*#7378423#*#*)
i also (on my search) have my code from the sony site where i selected my phone, sent an email, entered IMEI number and gave me a code to run using fastboot (this did not work for me)
based on theses settings what program/files/tools do i need to install custom rom, which i guess also will root it (im looking at either paranoid android or lineageOS)
Click to expand...
Click to collapse
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.
someone755 said:
You can't unlock you bootloader mate, the screenshot you put up says so. Meaning no custom kernels, which also means no ROMs that aren't based on stock. You're stuck with MIUI and various other zip-ports. No Lineage or AOSPA etc.
You can root it no problem though. Just use google or whatever, there's a couple of ways to do it.
Click to expand...
Click to collapse
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked
paresh90 said:
thank you for your response thought this would be a dead thread.
a few follow up questions if i may:
1. i asume i can find any post with MIUI in the title while should be compatible
2. i read something about down grade of firmware (is that a possible option for me)
3. in my google searching, would i need to state that my BL is locked
Click to expand...
Click to collapse
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.
someone755 said:
Just find a MIUI ROM in the dev section if you want MIUI.
You can install any firmware from Sony using Flashtool. Learn to use it, it's gonna be your friend.
That means you download any FTF file for your phone (there's a thread somewhere with a collection of FTFs), and you can flash it. KitKat, Lollipop, Marshmallow, or Concept.
I don't know how to root really, I just do it the old fashioned way since my bootloader is unlocked (and I pray that never changes). I think you'll have to downgrade to KitKat, which, again, is very easy if you know how to use Flashtool.
Np mate, I know the feeling of dead threads. Just happened by luck that I saw yours and got intrigued by the title lol.
Click to expand...
Click to collapse
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow
paresh90 said:
It's difficult trying to find a post that works for your situation.
Top of your head do you know any good miui ROMs. Light ones
And if I downgrade to kitkat or something will I be able to unlock my BL (or is it compleatly different )
I don't have the phone with me will check tomorrow
Click to expand...
Click to collapse
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.
someone755 said:
Haven't used MIUI since 2013 so you'll have to find one by yourself lol. I'm more of an AOSP guy -- if I was forced to use a locked bootloader I'd just install the concept FTF. That's about as light as you can get on this phone.
You can't unlock your bootloader, period. No software hack will help you. At least not from home. You'd need something like a riffbox and extensive knowledge of the phone's bootloader software to unlock it.
Click to expand...
Click to collapse
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.
paresh90 said:
Concept it is
Ok thank you for making it super clear (for me and anyone else reading this. )
It's annoying that the sony website gave me a code to unlock it. I'm sure they could have known from the IMEI number whqt it was and stuff.
Click to expand...
Click to collapse
I think the carriers lock the bootloaders, not Sony. As far to my knowledge, Sony ships out the devices unlocked, and the carriers decide whether to lock them, but don't report back to Sony. Their site just assumes you don't have a s'hitty carrier.
Best of luck man, and welcome to the Z3C forums!