Related
Hi,
work the method described in http://forum.xda-developers.com/showthread.php?t=1704209 also if my pad is encrypted?
Thanks
Midyr
Midyr said:
Hi,
work the method described in http://forum.xda-developers.com/showthread.php?t=1704209 also if my pad is encrypted?
Thanks
Midyr
Click to expand...
Click to collapse
I don't think so, I wouldn't try it. Just unencrypt it for a few minutes to root.
hm, what a pity!
thanks
Midyr
I would GUESS that /system isn't touched when "encrypting". Only /data et other stuff.
So my GUESS is that it would work just the same.
/dev/void said:
I would GUESS that /system isn't touched when "encrypting". Only /data et other stuff.
So my GUESS is that it would work just the same.
Click to expand...
Click to collapse
One of the first steps in miloj's root method is to push a file to /data/local, so it probably wouldn't work.
OK, then there ist really no chance
BTW: Is there any documentation about the enctryption-function?
Thanks for help
Midyr
prototype7 said:
One of the first steps in miloj's root method is to push a file to /data/local, so it probably wouldn't work.
Click to expand...
Click to collapse
Ouch. I totally forgot about that part.
Is /data/local encrypted aswell (because that seems a bit redundant)?
I guess it's both easier and safer to encrypt the whole /data partition, so I guess it may be.
Any information on this?
zeest said:
Any information on this?
Click to expand...
Click to collapse
Be more specific as to what you are trying to accomplish.
Help us help you.
bhundven said:
Be more specific as to what you are trying to accomplish.
Help us help you.
Click to expand...
Click to collapse
I am trying to find what part of a file is being read for an on/off tag, so I can modify it to bypass the bootloader. The file that is read is just a data file, full of 0's and 1's. As far as I can tell, the system reads the specific flag using an offset-length system, but the program that runs it is compiled and a few megabytes, plus I have no idea what I am doing with assembly.
zeest said:
I am trying to find what part of a file is being read for an on/off tag, so I can modify it to bypass the bootloader. The file that is read is just a data file, full of 0's and 1's. As far as I can tell, the system reads the specific flag using an offset-length system, but the program that runs it is compiled and a few megabytes, plus I have no idea what I am doing with assembly.
Click to expand...
Click to collapse
So lets take a step back and help describe the universe of this problem.
What kind of device do you have?
Which file are you talking about? Is it on a specific partition?
I have answers, well and if I don't I can at least help point you in the right direction, I just need more input.
bhundven said:
What kind of device do you have?
Click to expand...
Click to collapse
An LG Motion (ms770).
bhundven said:
Which file are you talking about? Is it on a specific partition?
Click to expand...
Click to collapse
The file is named "misc". I am not sure which partition it is on, probably the bootloader's (mmcblk0p5), since that is what uses it.
zeest said:
An LG Motion (ms770).
The file is named "misc". I am not sure which partition it is on, probably the bootloader's (mmcblk0p5), since that is what uses it.
Click to expand...
Click to collapse
I'm not a very good resource for qualcomm based devices, like the ms770.
zeest said:
I am trying to find what part of a file is being read for an on/off tag, so I can modify it to bypass the bootloader.
Click to expand...
Click to collapse
Do you have more information about how this works? Maybe a link to how it was done for another device?
zeest said:
The file that is read is just a data file, full of 0's and 1's.
Click to expand...
Click to collapse
There are ten types of people in the world; those that understand binary, and those that don't.
zeest said:
As far as I can tell, the system reads the specific flag using an offset-length system, but the program that runs it is compiled and a few megabytes, plus I have no idea what I am doing with assembly.
Click to expand...
Click to collapse
Do you have a process trace (ptrace) of this or something? I would like to know more about this.
Sorry about my slow responses... I'm not very good at multitasking
bhundven said:
Do you have more information about how this works? Maybe a link to how it was done for another device?
Click to expand...
Click to collapse
I had a link, a few months ago, that was notes from an assembly programmer to another team, for another similar device, but I don't have the link anymore, got lost when I upgraded to windows 7. From what I understand, the bootloader looks at the tag in the other file, if it is set to true, it does a signature check on the boot partition. If not, it boots with no security, aka unlocked.
bhundven said:
Do you have a process trace (ptrace) of this or something? I would like to know more about this.
Click to expand...
Click to collapse
Nope
bhundven said:
Sorry about my slow responses... I'm not very good at multitasking
Click to expand...
Click to collapse
NP, thanks for even helping.
zeest said:
I had a link, a few months ago, that was notes from an assembly programmer to another team, for another similar device, but I don't have the link anymore, got lost when I upgraded to windows 7. From what I understand, the bootloader looks at the tag in the other file, if it is set to true, it does a signature check on the boot partition. If not, it boots with no security, aka unlocked.
Nope
NP, thanks for even helping.
Click to expand...
Click to collapse
Well, update this if you get more info. You got my curiosity.
Not 100% sure how useful this is at this point, considering most of the more advanced users here may already know about this, but thanks to some Google-fu and Youtube-fu, I found 4CDMA's video on how to grab the MSL using adb logcat. I don't know if it would be proper to give the full instructions here, so I will omit them for now.
Take from this what you will, I am only a person who knows how to follow instructions and share information.
Cybird01 said:
Not 100% sure how useful this is at this point, considering most of the more advanced users here may already know about this, but thanks to some Google-fu and Youtube-fu, I found 4CDMA's video on how to grab the MSL using adb logcat. I don't know if it would be proper to give the full instructions here, so I will omit them for now.
Take from this what you will, I am only a person who knows how to follow instructions and share information.
Click to expand...
Click to collapse
How do i get msl
What's the status on reverse engineering a 2XL VZW? Surely there must be a condition where the OEM Unlockable switch can be set to on, whether by a network request or device status flag (which I would assume is out of limits for end-users to set). Or has the community already concluded this? By conclusion, I mean not a simple "no". I'm looking for a detailed insight on why us consumers are not able to OEM unlock our bootloader. I'd love to work on this if there is currently an ongoing project.
The OEM Unlock ( read: unlock ability ) flag is stored in Android's system file called build.prop.
jwoegerbauer said:
The OEM Unlock flag is stored in Android's system file called build.prop.
Click to expand...
Click to collapse
Ouch, that's definitely tough to get into without having root already
__3xcalibur said:
Ой, в это определенно сложно попасть без рута
Click to expand...
Click to collapse
How are you doing with editing build.prop?
I think through a PC you can get to the main section, but I don’t know how to do it.
zxforty said:
Как дела с редактированием build.prop?
Думаю, через ПК можно попасть в корневой раздел, но как это сделать не знаю
Click to expand...
Click to collapse
ONLY POST IN ENGLISH HERE, THIS BECAUSE THE ENGLISH LANGUAGE IS THIS FORUM'S DEFAULT LANGUAGE:
zxforty said:
How are you doing with editing build.prop?
I think through a PC you can get to the main section, but I don’t know how to do it.
Click to expand...
Click to collapse
build.prop is read only, no? You can probably *read* it from a PC and even direct on the device, but I don't think you can edit it
__3xcalibur said:
build.prop is read only, no? You can probably *read* it from a PC and even direct on the device, but I don't think you can edit it
Click to expand...
Click to collapse
You can drag a copy of build.prop from your phone to a pc, change the values, and change it via adb via recovery
zxforty said:
You can drag a copy of build.prop from your phone to a pc, change the values, and change it via adb via recovery
Click to expand...
Click to collapse
Well why hasn't this allowed us to root our P2XL's then?
__3xcalibur said:
build.prop is read only, no? You can probably *read* it from a PC and even direct on the device, but I don't think you can edit it
Click to expand...
Click to collapse
These are just my guesses sorry if this is stupid, but I am really puzzled by thoughts of unlocking recovery
__3xcalibur said:
Хорошо, почему тогда это не позволило нам рутировать наши P2XL?
Click to expand...
Click to collapse
Because our recovery does not allow installing modules, but I saw there the system mount button
zxforty said:
Вы можете перетащить копию build.prop со своего телефона на компьютер, изменить значения и изменить ее через adb через восстановление
Click to expand...
Click to collapse
I don't know why, but it seems to me that it might work, you just need to figure out how to get build.prop, change it, and send it back to your phone.
And you also need to find the lines responsible for OEM-Unlocking.
zxforty said:
I don't know why, but it seems to me that it might work, you just need to figure out how to get build.prop, change it, and send it back to your phone.
And you also need to find the lines responsible for OEM-Unlocking.
Click to expand...
Click to collapse
We're gonna need some actual sources here. I don't want this to be a thread of loose assumptions. No offense, but it litters the thread. I highly doubt Google will let Android owners modify a critical, core part of the Android system without root. @jwoegerbauer as well. If this is the case, then why hasn't this been posted anywhere?
By the way, I'm on topic for current Android versions; people who have upgraded to 10 and above or relevant versions.
__3xcalibur said:
I highly doubt Google will let Android owners modify a critical, core part of the Android system without root. @jwoegerbauer as well. If this is the case, then why hasn't this been posted anywhere?
Click to expand...
Click to collapse
All well-known manufacturers of phones in the past had to struggle with the fact that people who tried to root their phone's Android and got a soft-brick came to their service centers and demanded a free remedy.
So they pulled the emergency brake and secured Android against such tamperings. This brake is known as Android Verified Boot (AVB).
This means that all Android versions ( 8 and up ) implemented by manufacturers can no longer be modified without disabling AVB, which requires the booloader to be unlocked.
{Mod edit: Attached screenshot removed in order to protect privacy}
How can enable OEM Unlock/Lock Option?
Cannot find the OEM Unlock/Lock Option?
Tried all the steps on how to enable it.
iphonemaster72 said:
{Mod edit: Attached screenshot removed in order to protect privacy}
How can enable OEM Unlock/Lock Option?
Cannot find the OEM Unlock/Lock Option?
Tried all the steps on how to enable it.
Click to expand...
Click to collapse
@iphonemaster72 Thread closed as duplicate of
ROOTING
{Mod edit: Attached screenshot removed in order to protect privacy} I would like to Root this Android? Thank you. How can enable OEM Unlock/Lock Option? Cannot find the OEM Unlock/Lock Option? Tried all the steps on how to enable it. Is there...
forum.xda-developers.com
Same applies to this duplicate:
[CLOSED]ROOTING BY COMPUTER
{Mod edit: Attached screenshot removed in order to protect privacy} Is there anyway to root this model by computer or apk?
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis an rule no. 5 and post only ONCE! Thanks for your cooperation.
Additionally, I assumed your consent and removed the screenshot, which you atteched and that showed your telephone number and your IMEI. Both information could be used for illegal and harmful purposes if available to questionable subjects. YOU would be the one who suffers. Never make them publicly available on the internet.
Regards
Oswald Boelcke
Senior Moderator