• 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

I'm pretty sure I also tried that method but will be happy to throw it in fastboot this weekend and try again. I find it so strange that in fastboot rebooting into bootloader fast OEM unlock returns a OK status on the PC and phone.
 
omgbossis21 said:
I'm pretty sure I also tried that method but will be happy to throw it in fastboot this weekend and try again. I find it so strange that in fastboot rebooting into bootloader fast OEM unlock returns a OK status on the PC and phone.
Click to expand...

It will say OK to many commands that mean nothing. The only that actually function are erase and flash :shrug:
 
mario16 said:
Both of y'll really I used some of his stuff but I been using stuff for the esteem when I left the Optimus and now I have the spirit wasn't able to get the s3 but it's ok the spirit is a kool phone too
Click to expand...

yea it seems purdy nice.

Got some breakthroughs for the esteem too, nothing too big tho. lol
 
been awhile since i had an unlocked phone but if i remember correctly
phones that are unlocked have the ability to enter a recovery type mode with a key combo at start that lets you flash update.zip on a stock phone
 
johnnyl1111 said:
been awhile since i had an unlocked phone but if i remember correctly
phones that are unlocked have the ability to enter a recovery type mode with a key combo at start that lets you flash update.zip on a stock phone
Click to expand...

Premia has this generic Android recovery.... Wonder if my phone is even locked, but i cant query the bootloader from ADB to see whether it is or not
 
Its that LG did this on purpose. The way u get into recovery is the same as others but instead of actually sending to a interactive recovery, it wipes yur data. When u receive a update im not sure what im looking at. Is that recovery or what? I can get into recovery on my locked droid inc.
 
@johnnyl1111

Is this what you were talking about?
 

Attachments

  • uploadfromtaptalk1367801839176.jpg
    uploadfromtaptalk1367801839176.jpg
    53.4 KB · Views: 166
The only way I know to get into the bootloader is through fastboot and type adb reboot bootloader it will the supposedly boot into it but issue no info upon commands. Our recovery is actually not what wipes the phone exactly. Flash a alternate recovery image and when you type adb reboot recovery you will get a error but still lose your data partially (not all settings though but any info on internal is gone). So it wipes before the recovery is even ran.
 
omgbossis21 said:
The only way I know to get into the bootloader is through fastboot and type adb reboot bootloader it will the supposedly boot into it but issue no info upon commands. Our recovery is actually not what wipes the phone exactly. Flash a alternate recovery image and when you type adb reboot recovery you will get a error but still lose your data partially (not all settings though but any info on internal is gone). So it wipes before the recovery is even ran.
Click to expand...

No...only way into motion bootloader is with wiping /boot
 
Haven't tried wiping it and booting but I would think doing that would do the same data loss and just throw a security error when trying to run.
 
So I have started working on the bootloader for the motion again. I have dissassembled bootloader, and I believe I am on the right track. Found this:
Code: 
ROM:0002CC00 a_detectD       DCB "_DETECT:%d",0xD,0xA,0
ROM:0002CC0D                 DCB    0
ROM:0002CC0E aMisc           DCB "misc",0
ROM:0002CC13                 DCB    0
ROM:0002CC14 ; ---------------------------------------------------------------------------
ROM:0002CC14                 MOVS    R0, R0
ROM:0002CC14 ; ---------------------------------------------------------------------------
ROM:0002CC16 aPartitionSDoes DCB "partition %s doesn't exist",0xD,0xA,0
ROM:0002CC33                 DCB 0x6D ; m
ROM:0002CC34 aMcReadFailureS DCB "mc read failure %s",0xD,0xA,0
ROM:0002CC49                 DCB    0
ROM:0002CC4A ; ---------------------------------------------------------------------------
ROM:0002CC4A                 MOVS    R0, R0
ROM:0002CC4A ; ---------------------------------------------------------------------------
ROM:0002CC4C aBspForever     DCB "BSP Forever",0
ROM:0002CC58 aLgeFtmMagicStr DCB "LGE FTM MAGIC string is not equal. %s",0xD,0xA,0
 
zeest said:
So I have started working on the bootloader for the motion again. I have dissassembled bootloader, and I believe I am on the right track. Found this:
Code: 
ROM:0002CC00 a_detectD       DCB "_DETECT:%d",0xD,0xA,0
ROM:0002CC0D                 DCB    0
ROM:0002CC0E aMisc           DCB "misc",0
ROM:0002CC13                 DCB    0
ROM:0002CC14 ; ---------------------------------------------------------------------------
ROM:0002CC14                 MOVS    R0, R0
ROM:0002CC14 ; ---------------------------------------------------------------------------
ROM:0002CC16 aPartitionSDoes DCB "partition %s doesn't exist",0xD,0xA,0
ROM:0002CC33                 DCB 0x6D ; m
ROM:0002CC34 aMcReadFailureS DCB "mc read failure %s",0xD,0xA,0
ROM:0002CC49                 DCB    0
ROM:0002CC4A ; ---------------------------------------------------------------------------
ROM:0002CC4A                 MOVS    R0, R0
ROM:0002CC4A ; ---------------------------------------------------------------------------
ROM:0002CC4C aBspForever     DCB "BSP Forever",0
ROM:0002CC58 aLgeFtmMagicStr DCB "LGE FTM MAGIC string is not equal. %s",0xD,0xA,0
Click to expand...

On the right track to what??? :)
 
well there's two things that can happen well three including failure, they can find the key(signature) that LG is using to sign boot.img's and recovery.img's or actually unlock the bootloader.

from the looks at it, The last string there, its stating that "LGE FTM Magic string is not equal" what ever the magic string is its causing the errors maybe.
 
zimlokks said:
well there's two things that can happen well three including failure, they can find the key(signature) that LG is using to sign boot.img's and recovery.img's or actually unlock the bootloader.

from the looks at it, The last string there, its stating that "LGE FTM Magic string is not equal" what ever the magic string is its causing the errors maybe.
Click to expand...

Ohhhhh ok. So i kno what happens if we get the bootloader unlocked but what happens if we get the keys?
 
You must log in or register to reply here.
Back
Top Bottom