As a new member I cant yet post in the dev section but a few of you may recognize me from phandroid. Im curious is there a reason we cant use fastboot to flash an unlocked U image to unlock the phone? Im sure it signed but there is no reason to touch it, just pull and flash to an unlocked phone.... Also could anybody do me a favor and upload an unlocked u image so I could compare it to my locked image.
omgbossis21 said:
As a new member I cant yet post in the dev section but a few of you may recognize me from phandroid. Im curious is there a reason we cant use fastboot to flash an unlocked U image to unlock the phone? Im sure it signed but there is no reason to touch it, just pull and flash to an unlocked phone.... Also could anybody do me a favor and upload an unlocked u image so I could compare it to my locked image.
Click to expand...
Click to collapse
it doesn't work that way, there is an efuse on the cpu which the uboots( same for unlocked or locked phones) interprets
You use theThanks for the quick response. I am not familiar with the omap! As I am the LG msm8960 but their are similarities. The fuse must be blown to unlock the bootloader? On the 8960 the fuse is blown which presents a locked bootloader, we have tried to blow it with an higher value but it didn'twork. This phone also uses the LG wallpaper file which when activating its framework can alter (on 8960) the qfuse values.
omgbossis21 said:
You use theThanks for the quick response. I am not familiar with the omap! As I am the LG msm8960 but their are similarities. The fuse must be blown to unlock the bootloader? On the 8960 the fuse is blown which presents a locked bootloader, we have tried to blow it with an higher value but it didn'twork. This phone also uses the LG wallpaper file which when activating its framework can alter (on 8960) the qfuse values.
Click to expand...
Click to collapse
I'm not sure if dealing with efuse directly is way to go, there are plenty of devices that use omap4430 with huge developers base and mostly what they do is 2nd init or a custom uboot.
I'm unsure as to why flashing a unlocked u partition to a locked phone doesn't work. On the optimus (3d I believe? ) the LG sign tools were leaked and a custom up boot was signed and flashed to unlock. The ma8960 simply requires a unlocked abooot to be flashed. Not asking to be spoonfed perhaps it would require the u,x and maybe boot. Image. I will download the source and have a look for a qfuse generic configuration file.
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
I'm unsure as to why flashing a unlocked u partition to a locked phone doesn't work. On the optimus (3d I believe? ) the LG sign tools were leaked and a custom up boot was signed and flashed to unlock. The ma8960 simply requires a unlocked abooot to be flashed. Not asking to be spoonfed perhaps it would require the u,x and maybe boot. Image. I will download the source and have a look for a qfuse generic configuration file.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21280773&postcount=32
i'm sure these can be ported and it's possible that p76X uboot is signed with same keys as 3d.p940 but that is way beyond my knowledge
uboot https://github.com/wkpark/u-boot-omap4-optimus
xloader https://github.com/wkpark/x-loader-cosmo
the LG sign tools (who knows if keys are right) https://github.com/milaq/android_device_lge_p940/tree/cm-10.1/releasetools/ifttool
Thanks, I appreciate your time and in turn saving me some time. Looking at the unlock procedure it seems at one point data connection is a must which suggest each phone uses a generated unlock token. Following that post also suggest (as I suspected) the secure boot fuse is blown implementing a locked bl. I will do some furthur research. LG tends to have bootloaders signed by different people per device. I will look into to the wallpaper framework and the efuse values as well as looking at the LG sign tools. Thanks again.
Sent from my LG-P769 using xda app-developers app
btw current method to unlock the bootloader isn't really that difficult
Lelus said:
btw current method to unlock the bootloader isn't really that difficult
Click to expand...
Click to collapse
I'm sure its not , just a pita with the inverted screen. I'm just curious is all =-) Perhaps we can use the wallpaper framework and test a lg signed image created with the tools. Any idea on the efuse values, we could compare locked with unlocked on the W.F. These are our options :
C:\adb>adb shell
[email protected]:/ # wallpaper -framework
wallpaper -framework
------------------------------------------------------------------
Welcome Security Framework!!
01. Error Dispaly Test
02. Application Certificate Test
03. Crypto Library Test
04. TrustZone QFPROM Test
05. TrustZone SFS Test
06. TrustZone H/W Crypto Engine Test
exit -To exit this test application
------------------------------------------------------------------
omgbossis21 said:
I'm sure its not , just a pita with the inverted screen. I'm just curious is all =-) Perhaps we can use the wallpaper framework and test a lg signed image created with the tools. Any idea on the efuse values, we could compare locked with unlocked on the W.F. These are our options :
C:\adb>adb shell
[email protected]:/ # wallpaper -framework
wallpaper -framework
------------------------------------------------------------------
Welcome Security Framework!!
01. Error Dispaly Test
02. Application Certificate Test
03. Crypto Library Test
04. TrustZone QFPROM Test
05. TrustZone SFS Test
06. TrustZone H/W Crypto Engine Test
exit -To exit this test application
------------------------------------------------------------------
Click to expand...
Click to collapse
Actually 769 can be unlocked without even touching the screen so it's not a problem, you don't have to deal with inverted screen at all.
Why would you want to use something made for msm8960 on totally different cpu like omap4430 ?
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Sorry, partially my bad, anyways from what I can see it's just leftover code for qualcomm cpu.
Hello guys !! I ve several problems with unlocking procedure of my p760 bootloader , i try to unlock it with v20b and more but the phone reboost normally...I need help plese !! Is thare any way to unlock bootloader with another procedure like a system dump ??? Thanks
omgbossis21 said:
That's from our wallpaper file from our sbin. It is also the file that throws security error when removing specific apks from stock system (probably videos. Apk and about 4 or 5 others). Best to remove it from the stock startup script labeled something like xxearlyboot (after unlocking of course). I plan on unlocking my bootloader but like I said I'm just very curious about whatever device is placed in my hands
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
I believe the person I was giving these files were trying to give them to you
FILES BOOT & ETC.zip (28.1 MB)
https://mega.co.nz/#!Y4cjUYCL!FJ-0ckX-pg6YC3SdlG7sbijWR7Qr7yVukugImbGVKoE
Sorry I currently don't have to kdz for t-mobile p769 v20d but if you have the kdz. you can extract the img with this guide.
http://forum.xda-developers.com/showthread.php?t=2315727
Thanks. I've been pulling my partitions and browsing as well. My Ubuntu build is currently fresh from last time it crashed though I do wanna start a rom. Maybe I will get in the mood to setup the environment again. Haven't unlocked my bootloader yet just using the 2nd int to backup and run a few things like acid soundmod. I found the sound to be really lacking on this phone.
Sent from my LG-P769 using xda app-developers app
If i try to flash u.img located in https://mega.co.nz/#!Y4cjUYCL!FJ-0ck...yVukugImbGVKoE with omap4boot mode , I should have a unlocked bootloader ??? I try with other files but with no reasons. Thanks
Haven't tried but seems it doesn't work that way. My thinking was that the unlocked partition would unlock the phone or simply allow the unlock command but it is not confirmed what so ever.
Sent from my LG-P769 using xda app-developers app
Why do you think it does not work ? what prevents the replacement of the bootloader ?
Well I tried a unlockable u.img but the unlock command did not work. Wallpaper. Bin is applicable on our phone and is used for secure boot and called by the lge. Int. Earlyboot. RC file. After alot of hours I got the LG sign tools to sign files. Since my Ubuntu build had gone haywire I tested with cygwin using modified mkbootimg and unpackbootimg files modified for cygwin and modded the LG script to suit them but some of the LG signature files were binary and cygwin could not run them. I then proceeded to fix my Ubuntu build which took awhile. Then I remembered I installed Ubuntu 64 bit and had to install 32bit libraries lol. Is our recovery image signed? I signed a cwm touch recovery for our phone, pushed it to mine and used adb reboot recovery in which I got an android with a triangle in it. If it is signed I would have got a secure error..... I just unpacked my boot. Image made a few small changes (like removing wallpaper from starting up) and repacked it. Tomorrow I will sign it and see if it boots. O yea, can anybody link me a unlockable x block please
Sent from my LG-P769 using xda app-developers app
Sorry I didn't send it to you, I'll upload in a bit. I know it is unlocked, I never flash a new x-loader.
Sent from my LGMS769 using xda app-developers app
Related
Well, there we go. Dun wanna wait anymore, and I unfortunately are not too clever myself. So! I propose a root bounty. Whoever manages to root the device first and post a guide here will get it. If you don't have an Xperia play, I can do and upload dumps/test out new root methods for you if you contact me.
Some rules tho:
- It has to be possible for the average user without the use of additional hardware or commercial software (as in, software we have to buy)
- It doesn't have to work on devices that still have a locked bootloader, altho that would be very awesome.
- It has to work on the stock Sony Ericsson Software. Unless you can create a fully functional Cyanogenmod. Then I'll donate $100 to you instantly.
For starters, I throw $35 into the pot.
$20 by gnasher666
I'll go $20 for root
Meister_Li said:
- It has to work on the stock Sony Ericsson Software. Unless you can create a fully functional Cyanogenmod. Then I'll donate $100 to you instantly. .
Click to expand...
Click to collapse
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
johnsongrantr said:
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
Click to expand...
Click to collapse
I'm aware of that. I just mean that we should still be able to use the normal Sony Ericsson Android software, so root on the current software of the phone, even if the boot image or kernel have been replaced with other ones.
I just want to avoid loopholes, like someone saying: "I got root! But only if you replace everything and don't actually plan on using your phone because nothing else works!"
I will have my device coming this week.
please keep an eye on this thread for the arc.
http://forum.xda-developers.com/showthread.php?t=1035306&page=11
i will be updating my device before unlocking to get all the files needed. (hopefully)
I sure hope the phone can be rooted soon to much bloatware I want to get rid off
You cant get the boot.img with an unlocked one either I have got 2 one locked one open.
Sent from my R800i using XDA Premium App
waz000000 said:
You cant get the boot.img with an unlocked one either I have got 2 one locked one open.
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
why do you need the boot.img for root?
rooting the system should be sufficient
johnsongrantr said:
this will be a problem, there is most definately a sig check on the file it pushes to your phone through bundled software. A modified boot.img can be pushed and flashed to the phone with fastboot. Also the update software detects the fact you unlocked the bootloader and it basically doesn't work on those phones anymore.
not to **** in your cereal, but making a modified kernel and push through fastboot is just a matter of doing it, not a whole lot of skill will be required.
like I said in the fastboot thread, if someone who has not unlocked their bootloader can upload the recovery image package that the bundled software downloads and mirrors it, it will make things a lot quicker.
Click to expand...
Click to collapse
There is no bundled software in the box. Which one are you talking about?
also,
What is wrong with this dump
http://forum.xda-developers.com/showthread.php?t=1022224
?
Thank you for sharing with us your ideas
FrAsErTaG said:
why do you need the boot.img for root?
rooting the system should be sufficient
Click to expand...
Click to collapse
Agreed, but id like to try and install CW and get a proper recovery screen sorted.
waz000000 said:
Agreed, but id like to try and install CW and get a proper recovery screen sorted.
Click to expand...
Click to collapse
A custom recovery would be awesome. However, the Play doesnt seem to have a recovery partition.
Sent from my Nexus S using XDA App
NielDK said:
A custom recovery would be awesome. However, the Play doesnt seem to have a recovery partition.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
not stock, but you can always make one, other SE devices don't have a *proper* recovery because they didn't have full access to the bootloader.
I'm curious what mode holding the back button on while plugging in the device, it appears to be different than holding search
johnsongrantr said:
not stock, but you can always make one, other SE devices don't have a *proper* recovery because they didn't have full access to the bootloader.
I'm curious what mode holding the back button on while plugging in the device, it appears to be different than holding search
Click to expand...
Click to collapse
Yep, it seems to be another kind of flash mode, altho I wasn't able to get any response out of the device with the usual fastboot and/or adb commands.
Hopefully this might be recovery mode. And that would open for custom recovery. Allthough I didnt find recovery partition, this might be because that MTD block is hidden. Root may show
Meister_Li said:
Yep, it seems to be another kind of flash mode, altho I wasn't able to get any response out of the device with the usual fastboot and/or adb commands.
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
I thought I should jump in here and clarify a few things. Bounty threads are allowed here at XDA as long as no donations are given up front. Meaning what you are doing here is just fine, as long as no one is "collecting" the donations up front.
A bounty thread can motivate development.
So...people who want to participate should NOT DONATE now they should PLEDGE and when you feel that the goal has been met THEN donate to the developer directly.
XDA will not mediate disagreements about these matters...so you do this at your own risk.
Have fun!
Thanks for clearing that up - that's how I planned it, actually. As soon as someone accomplishes root, I'll send my donation his way and I hope that others will too!
that works as I hoped it would. I'm good for the money once root access is available.
Personally, I think root will be a lot harder than cfw as it will potentially allow access to parts of the software Sony don't want you playing with.
fingers crossed some clever person finds an exploit sooner rather than later.
I would chuck in $20 if the Neo could be included....
Just spent an hour on the phone with sony ericsson trying to get a direct link to the recovery image to no avail.
I got 20 usd for the person who gets me a copy of that recovery image.
Once you get me that, I can make a kernel with root out of it ill give it away for free with instructions on how to flash it (given unlocked bootloader)
I wish I woulda did this myself before I unlocked my bootloader. Kinda frusterrated after dealing with their tech support.
I have a locked one still cant get img files,
Right im trying a system restore on the new one (locked bootloader) im hoping the recovery image will be downloaded onto the computer and i can extract from there, lets see huh/
well it restored but cant find the image, it's pissing me off now spent to long doing sh!t.
connected to the phone to ADB pushed SU no permission chmod busybox no permission, gahhh we need that boot.img or system.img but how the hell do we get it?!?
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Shadowdancer123 said:
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Click to expand...
Click to collapse
To add to that it is for recovering from a soft brick. So it is kind of a big deal. It may also helps devs not be so gun shy.
inheme said:
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
Click to expand...
Click to collapse
If u install a costum rom, fastboot files let you back to moto stock rom
Sent from my XT910 using Tapatalk
Thanks guys!
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
cheekrox said:
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
Click to expand...
Click to collapse
Spend about 2minutes and look at developer threads, you can find them
Sent from my RAZR using Tapatalk
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
jake21 said:
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
Click to expand...
Click to collapse
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Previously no phone actually used an e-fuse (it was proven on earlier moto phones that e-fuse was not enabled). Does the razr actually use an e-fuse ?
Shadowdancer123 said:
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Click to expand...
Click to collapse
I believe this might be possible. If someone is willing to give this a try, a developer for example? Try to extract your own bootloader from you phone, re-pack it for CWM as a flashable file and upload. I don't know anything when it comes to the proceedure of how this is done, but fishing about this forum area "http://forum.xda-developers.com/forumdisplay.php?f=855" might lead to a few clues. However this is a different device from a different manufacturer, they have managed to extract the BL. Not sure how. But it proves it must be possible, no? Im desperate for a bootloader unlock. Can't believe my operator is not allowing this.
Won't work. Just won't. Adding to the list.
K900 said:
Won't work. Just won't. Adding to the list.
Click to expand...
Click to collapse
Okay, no worries. What about this, wouldn't it work if we managed to load a custom kernel AFTER the original kernel is already loaded? A bit like 2nd-init in CWM? Just suggesting as many things as I can so you can either shoot them down in flames and add them to the list, or if something pops up that we COULD possibly try, you can help forward it for development. If it fails it fails...
Booting the custom kernel still requires an unlocked bootloader right? Then you are going to have to boot an enirely new android system on top of your basic one to boot custom kernels.
Correct me if i'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Booting the custom kernel still requires an unlocked bootloader right? Then you are going to have to boot an enirely new android system on top of your basic one to boot custom kernels.
Correct me if i'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Well the thought behind my suggestion is that since the kernel is loaded officially, it means the key is already bypassed due to the official kernel going through which then means if we can load a new kernel as the Rom loads or just before it loads yet still after the original kernel has loaded then the key must still be bypassed and this new custom kernel can be loaded? People should keep giving suggestions!
Sent from my LT26i using xda premium
It might just work, but you would need 2 boot partitions right?
We could make a script that boots the second kernel before the first kernel boots the system.
Sent with my Sony Xperia S using a little bit of KA magic.
It's hardly possible to boot the kernel as late as the earliest possible injection (install-recovery) on locked BL.
No way to make a delay on that time given?
keewanchoapsss said:
No way to make a delay on that time given?
Click to expand...
Click to collapse
We can delay it, but to be able to hot boot a kernel, we need to push it back (so we can jump in earlier) not forward.
K900 said:
We can delay it, but to be able to hot boot a kernel, we need to push it back (so we can jump in earlier) not forward.
Click to expand...
Click to collapse
You can do it on post boot iirc, just overwrite /system/bin/chargemon with a custom script, mv chargemon to charger, and at the end of the script run charger.
only problem with this is you need a way of hijacking in the kernel (I have no idea how to do this).
KeiranFTW said:
You can do it on post boot iirc, just overwrite /system/bin/chargemon with a custom script, mv chargemon to charger, and at the end of the script run charger.
only problem with this is you need a way of hijacking in the kernel (I have no idea how to do this).
Click to expand...
Click to collapse
Yeah, the exact problem is we need to hot swap the kernel. It's possible (by using something similar to Uptrack, i.e. dynamically replacing code in memory), but needs to happen early enough so that nothings breaks if it goes wrong.
Can't we just do something similar to dualboot, but with the option to choose between boot system and boot the second kernel?
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Can't we just do something similar to dualboot, but with the option to choose between boot system and boot the second kernel?
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
Dualboot needs to be handled by the bootloader or the kernel itself, but we can't modify either on locked bootloader.
Dualboot different kernel it's only possible if there's a custom bootloader ( with a 2nd boot partition for the 2nd kernel , and possibility to switch kernel before booting it [ like dualboot BL of iconia a500/501 ]
Dualboot different roms it's possible by having 2 roms that uses the same kernel , so you can switch rom after kernel boot ( like siyahkernel )
For extract bootloader I think it should be possible by reverse engineering fastboot executible ( if it can put .ta key to unlock bootloader , I think fastboot can also read bootloader partition [ it's quite impossible it can write but it can't read ]) and add the command to read and save bootloader
EDIT : for extract bootloader try to extract it from loader.sin ( 7-zip give me that file is broken , but I think it has strange compression method or some protection to avoid extraction)
EDIT2 : algorithm for compress/decompress loader into loader.sin its LZMA but for some reason 7-zip cannot decompress it
If we'll found a good lzma sompressor/decompressor it will be easier to extract , edit , and repack bootloader for flash by loader.sin with flashtool
EDIT3 (too edit in this post ) : Founded romanger tool that can convert sin to img , but problem remain , tomorrow I will try to use new version of flashtool ( 0.9) to extract loader .sin.... in changelog it's wrote that thay added loder.sin extract from sony fileset ..... maybe it will work
Forzaferrarileo said:
Dualboot different kernel it's only possible if there's a custom bootloader ( with a 2nd boot partition for the 2nd kernel , and possibility to switch kernel before booting it [ like dualboot BL of iconia a500/501 ]
Dualboot different roms it's possible by having 2 roms that uses the same kernel , so you can switch rom after kernel boot ( like siyahkernel )
For extract bootloader I think it should be possible by reverse engineering fastboot executible ( if it can put .ta key to unlock bootloader , I think fastboot can also read bootloader partition [ it's quite impossible it can write but it can't read ]) and add the command to read and save bootloader
EDIT : for extract bootloader try to extract it from loader.sin ( 7-zip give me that file is broken , but I think it has strange compression method or some protection to avoid extraction)
EDIT2 : algorithm for compress/decompress loader into loader.sin its LZMA but for some reason 7-zip cannot decompress it
If we'll found a good lzma sompressor/decompressor it will be easier to extract , edit , and repack bootloader for flash by loader.sin with flashtool
EDIT3 (too edit in this post ) : Founded romanger tool that can convert sin to img , but problem remain , tomorrow I will try to use new version of flashtool ( 0.9) to extract loader .sin.... in changelog it's wrote that thay added loder.sin extract from sony fileset ..... maybe it will work
Click to expand...
Click to collapse
You are massively wrong here.
1) hotbooting a kernel is indeed possible, I can give you related links later, but for now just Google KSplice Uptrack.
2) Fastboot has nothing to do with Sony's cryptography, it is a Google tool that is open source as a part of AOSP. If you are talking about flashtool, it is also open source, so there is absolutely no magic involved on the PC. Flashtool reads and writes the loader as raw data, not trying to decipher it. If you still want to mess with loader.sin, it's unlikely to be LZMA compressed because that means an even lower level of software is required to decompress it. A 'good LZMA decompressor' you're looking for is unsurprisingly called lzma, is open source and should come preinstalled in most Linux distributions.
3) To flash anything, even the bootloader, with flashtool or any other method, you'll need to sign it with Sony's key or find a way to bypass the validation in Sony's stock bootloader. This also means that even if you manage to modify the bootloader code, you will not be able to flash it on locked devices unless one of the above happens.
But where in the loader file, or any stock file can we find the validation of sony?
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
But where in the loader file, or any stock file can we find the validation of sony?
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
In the file header. The problem is it's an asymmetric signature. So 1) you need different keys to sign and to verify signatures and 2) the signature itself depends on the file's content, so when the file is changed, it'll no longer be valid.
Are bootloader files also verified by Sony?
I don't think so, because the bootloader is the first software to start so it cant be checked by some other software right?
If all this is correct, cant we pull the bootloader file in some way, and replace it with an unlocked or unlockable version?
Correct me if I'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
JoelChrist_ said:
Are bootloader files also verified by Sony?
I don't think so, because the bootloader is the first software to start so it cant be checked by some other software right?
If all this is correct, cant we pull the bootloader file in some way, and replace it with an unlocked or unlockable version?
Correct me if I'm wrong
Sent with my Sony Xperia S using a little bit of KA magic.
Click to expand...
Click to collapse
The new bootloader is verified by the old bootloader.
K900 said:
The new bootloader is verified by the old bootloader.
Click to expand...
Click to collapse
In that case, if we remove the bootloader, and flash the other one, there is no bootloader to verify it right?
Sent with my Sony Xperia S using a little bit of KA magic.
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
this thread can be closed.
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
LG prevents rebooting in bootloader on most phones, including this one. Entering fast boot with the script and running the command fails BC its not an official fastboot its user compiled.
Sent from my LG-P769 using xda app-developers app
i've been rooting and putting CWM onto it before i bother with the bootloader, but i wonder if you have to unlock the bootloader FIRST, because CWM or rooting wipes out some thing that's needed to get the bootloader to allow fastboot??? i dunno, just taking stabs in the dark now...
I didn't have recovery or radio installed when I unlocked my bootloader
leolawliet said:
I didn't have recovery or radio installed when I unlocked my bootloader
Click to expand...
Click to collapse
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
sentientsystem said:
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
Click to expand...
Click to collapse
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
leolawliet said:
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
Click to expand...
Click to collapse
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
sentientsystem said:
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
Click to expand...
Click to collapse
*crosses fingers* good luck, if I find more suggestions I'll let you know. For now let's hope I'm right on this.
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
sentientsystem said:
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
Click to expand...
Click to collapse
Wait so you managed to unlock it??
unlocked, flashed cyanogenmod tried to fix the inverted / screwed up screen, bricked it again, trying to unlock again...
LaDY Vengeance said:
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Usually phones that don't have a key combo for fastboot you can delete main system partitions and it would start in official fastboot like my LG motion. Not on this phone though
Sent from my LG-P769 using xda app-developers app
Have you tried holding down the vol down button when the lights flash on boot?
villan.co said:
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
Click to expand...
Click to collapse
Have you tried holding down the vol down button when the lights flash on boot? Works for me to get into CWM recovery.
thanks man, but, i'm way past that point. this thread should actually be closed: http://forum.xda-developers.com/showthread.php?t=2461483
How is it possible to hard-brick a phone? Isn't the bootloader written on a read-only memory section and therefore cannot be written to? If so, how come there is a situation where you can't even get to the bootloader of the device and flash a new kernel, os, etc...
UnTraDe said:
How is it possible to hard-brick a phone? Isn't the bootloader written on a read-only memory section and therefore cannot be written to? If so, how come there is a situation where you can't even get to the bootloader of the device and flash a new kernel, os, etc...
Click to expand...
Click to collapse
It is possible by flashing the wrong firmware by using the boot loader. In my phones case, when you want to flash stock ROM you'd have to use the boot loader, but if you use a wrong firmware package containing the wrong boot loader then you are screwed. Although it isn't entirely possible to hard brick your phone by flashing ROMs though recovery because it checks the updater script which has a line that says for which phone this ROM is meant for.
Sent from my Moto G using Tapatalk
ironman38102 said:
It is possible by flashing the wrong firmware by using the boot loader. In my phones case, when you want to flash stock ROM you'd have to use the boot loader, but if you use a wrong firmware package containing the wrong boot loader then you are screwed. Although it isn't entirely possible to hard brick your phone by flashing ROMs though recovery because it checks the updater script which has a line that says for which phone this ROM is meant for.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
But why flashing a new ROM overwrites the bootloader? Should't the bootloader have it's own partition that cannot be written to?
UnTraDe said:
But why flashing a new ROM overwrites the bootloader? Should't the bootloader have it's own partition that cannot be written to?
Click to expand...
Click to collapse
Bootloader has its own partition but it can be written to. Check out the Google Nexus factory images. The first thing the flash-all script does is update the bootloader.
I've manually updated the bootloader on my current phone at least a half dozen times.
Wakamatsu said:
Bootloader has its own partition but it can be written to. Check out the Google Nexus factory images. The first thing the flash-all script does is update the bootloader.
I've manually updated the bootloader on my current phone at least a half dozen times.
Click to expand...
Click to collapse
Oh so what everybody's calling ROM (Read-Only Memory) does not actually read only?
ironman38102 said:
It is possible by flashing the wrong firmware by using the boot loader. In my phones case, when you want to flash stock ROM you'd have to use the boot loader, but if you use a wrong firmware package containing the wrong boot loader then you are screwed. Although it isn't entirely possible to hard brick your phone by flashing ROMs though recovery because it checks the updater script which has a line that says for which phone this ROM is meant for.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
nowadays..
i don't see that way works too.
seems it entirely not possible
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
UnTraDe said:
Oh so what everybody's calling ROM (Read-Only Memory) does not actually read only?
Click to expand...
Click to collapse
if u have the permission to write it..
UnTraDe said:
Oh so what everybody's calling ROM (Read-Only Memory) does not actually read only?
Click to expand...
Click to collapse
Normally that'd be the case but when you root you basically get elevated permissions and also if the package has images that are having OEMs signature key(I hope that's the right term for it) then the bootloader allows itself to be updated and the firmware as well.
Sent from my Moto G using Tapatalk