from what I seen scanning the first page none of thats is for msm8960. I would double check b4 attempting anything and find the info for msm8960 instead of going by specs for msm8660.
I think you scanned entirely too fast
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [WIP][DEV] Custom Recovery/Bootloader unlocking Work In Progress Thread
- Thread starter plasticarmyman
- Start date
-
- Tags
- lg motion 4g
I think you scanned entirely too fast
andriodadmirer
Android Enthusiast
What about editing the cab files to be pre rooted and modifing the bootloader take a look at what i found could this be the right track or is this way off?
http://forum.xda-developers.com/showthread.php?t=1891573
http://forum.xda-developers.com/showthread.php?t=1891573
andriodadmirer
Android Enthusiast
Ok what about the 2nd bootloader project maybe this could work to get around our locked bootloader
Bootloader Project - OMAPpedia
Bootloader Project - OMAPpedia
adanmex
Android Enthusiast
I bet we can do this. this is basically the Asgard trick for the moto cliq. we went around system and booted directly from sdcard. SD Card Boot
If MMC is included in the booting device list, the ROM looks for an SD Card on the first MMC controller. If a card is found, the ROM then looks for the first FAT32 partition within the partition table. Once the partition is found, the root directory is scanned for a special signed file called "MLO" (which is the x-loader binary with a header containing the memory location to load the file to and the size of the file). Assuming all is well with the file, it is transfered into the internal SRAM and control is passed to it. Both MMC1 and MMC2 can be used for booting.kudos
If MMC is included in the booting device list, the ROM looks for an SD Card on the first MMC controller. If a card is found, the ROM then looks for the first FAT32 partition within the partition table. Once the partition is found, the root directory is scanned for a special signed file called "MLO" (which is the x-loader binary with a header containing the memory location to load the file to and the size of the file). Assuming all is well with the file, it is transfered into the internal SRAM and control is passed to it. Both MMC1 and MMC2 can be used for booting.kudos
omgbossis21
Android Enthusiast
What exactly happened when you used the tool to blow the qfuse and how are you sure its still locked?
plasticarmyman
Android Expert
never mind i wasn't reading the whole thread
* embarrassed emoticon*
* embarrassed emoticon*
Not at home right now, so can't tell you exactly, but it said something not found, I decompiled it and some address didn't match up. I know I am still locked because I booted to fastboot and flashed to the recovery partition, but got a security error.
sammyz
LG Whiz Kid
But our phones don't have an OMAP processor....
sammyz
LG Whiz Kid
Even if it were pre-rooted, would not help unlock processor.
It would speed things up when we need to unbrick.
sammyz
LG Whiz Kid
sammyz
LG Whiz Kid
LG or all brands??
And most of the LG bootloaders were unlocked by fastboot OEM unlock.
Older LGs that were unlocked that got locked by an ICS update took, well idk, 3 months?? But they already had a way to unlock the bootloader by flashing the gingerbread bootloader. We don't have a gingerbread boot loader and LG phones that use msm8960 with gingerbread use a boot loader that's 3MBs. Our bootloader is 512kbs...
omgbossis21
Android Enthusiast
This week I will try to look at that unlock tool and explore a few area of this phone.
PlayfulGod
Extreme Android User
Well most were prolly like the spectrum, not truely unlocked, but rather the older unlocked bl from GB was used.
I dont know of any LG bootloader that was locked and unintended to be unlocked being cracked.
sexylion23
Member
Is it possible to flash a gb bootloader and a different kernel that doesn't run security checks at the same time???
rhino889a
Android Expert
Just from reading the post you quoted,i would doubt it
Gingerbread bootloader partition 3 meg
Our bootloader partion half meg
You would have to stand on it and jump up and down to smash it into that itty bitty little spot
PlayfulGod
Extreme Android User
Its not likely you're going to find GB on a msm8960 device.
So... do we have a way to trace security errors, to find what caused them? I believe I have blown the qfuse, using wallpaper, that contains our bootloader "lock", but... still security errors. Should there be any visual key that the qfuse actually blew? Ex: phone restart.
Yes, and I also read this http://forum.xda-developers.com/showthread.php?p=34772926#post34772926 and used info from both. While looking around after this didn't work, I discovered that the security message I am getting does not appear to be in aboot, the kernel, wallpaper, morningcall, sbl1-3, or the tz partition. This makes me wonder: what is checking the signatures? I have opened all these partitions in a hex editor and searched them, finding nothing.