Related
Hi,
I know this is not the place for n00b questions but I didn't find answers for these. I own a Moto XT300/Spice and since it is only available in Canada and Brazil the mod support is pretty weak. I'd like to try a few things, like adding the adreno200 3d module to the kernel/load dynamically or even try to update to froyo.
First, what are each partitions on the android device?
boot - where kernel/ramdisk/kernel arguments are kept
system - system data, not modifiable by user, only /data is ?
recovery - kernel/ramdisk/other files booted when pressing power+x on power?
userdata - ?
cache - ?
kpanic - ?
In system there should be a recovery.img that is flashed to the recovery partition at each restart? My moto spice does not have it. Why?
Motorola normally has a locked bootloader. What does this mean? That I can't change the bootloader? That I can't change the boot.img ?
When pressing Power+X and the Alt+L the recovery menu appears. This is the result of booting the recovery partition?
When hard-reseting the phone, boot.img and /system are not restored, just certain folders are wiped? For example, if busybox and su was installed, when hardresetting the phone they would still be there ?
/sdcard/update.zip can be used to restore the state of the phone(with the right update-script, of course). It should be included the boot.img and system/ as well as the META-INF and must be signed. Is sensitive information of the phone included in either boot.img or system that should not be given to others, like the IMEI?
Using the default.prop and build.prob from system could I compile the kernel from source and modify it?
Thanks for any help regarding these topics. I've searched around and most similar threads were not answered.
If you con do it please let me know, i'm a former WM user and know nothing of android or linux (so far)...
snakerdlk said:
Hi,
I know this is not the place for n00b questions but I didn't find answers for these. I own a Moto XT300/Spice and since it is only available in Canada and Brazil the mod support is pretty weak. I'd like to try a few things, like adding the adreno200 3d module to the kernel/load dynamically or even try to update to froyo.
First, what are each partitions on the android device?
boot - where kernel/ramdisk/kernel arguments are kept
system - system data, not modifiable by user, only /data is ?
Click to expand...
Click to collapse
Still no idea...
recovery - kernel/ramdisk/other files booted when pressing power+x on power?
Click to expand...
Click to collapse
YES
userdata - ?
cache - ?
kpanic - ?
In system there should be a recovery.img that is flashed to the recovery partition at each restart? My moto spice does not have it. Why?
Motorola normally has a locked bootloader. What does this mean? That I can't change the bootloader? That I can't change the boot.img ?
Click to expand...
Click to collapse
No idea
When pressing Power+X and the Alt+L the recovery menu appears. This is the result of booting the recovery partition?
Click to expand...
Click to collapse
YES
When hard-reseting the phone, boot.img and /system are not restored, just certain folders are wiped? For example, if busybox and su was installed, when hardresetting the phone they would still be there ?
Click to expand...
Click to collapse
probably..
/sdcard/update.zip can be used to restore the state of the phone(with the right update-script, of course). It should be included the boot.img and system/ as well as the META-INF and must be signed. Is sensitive information of the phone included in either boot.img or system that should not be given to others, like the IMEI?
Click to expand...
Click to collapse
I heard that after signing in to the google account on your phone, system partition may have it... who knows...
Heard of a guy who managed to erase his IMEI. Is this possible ?
Using the default.prop and build.prob from system could I compile the kernel from source and modify it?
Click to expand...
Click to collapse
Don't know, but Clockwork Mod uses the info from the boot.img to setup the build environment...
Thanks for any help regarding these topics. I've searched around and most similar threads were not answered.
Click to expand...
Click to collapse
Yeah, had a feeling such post would not be answered in these forums...
The dump will be online soon, special thanks to the members who helped me get the dump! Without the help of them I wouldn't have do this.
I wanna thank these guys and to all who have posted here..
biktor_gj
Jaxbot
E:V:A
Cotulla
and especially rob243 who will host the dump for the developers to download.
I hope Windows Phone users will benefit to this!
Please check back here in a few days for the dump.
Meanwhile, the engineering HTC 8X loaner device will have to go back to the company soon, too. I would appreciate a little donation from the generous ones out there. Buy me a pizza? Buy me my own 8X? Just hit the donate to me button on the left under my username, or here.
Thanks all!
neilgoco said:
I got one with tons of apps that seems to be for testing. Maybe somehow this will help in the future development of the device? I am not sure how though.
Click to expand...
Click to collapse
Lucky you, check the hspl/spl to see if it's locked or unlocked. If unlocked, contact the user, I mean The Living Legend called COTULLA and tell him about your phone. Actually, just contact him, he will tell you to do a few things and if someone can help in here, it's him. We owe him the HSPL for HTC WP7 1st and 2nd generation phones and the 1st Titan custom rom (DFT) among other things.
Thanks for sharing!
f.
forelli said:
Lucky you, check the hspl/spl to see if it's locked or unlocked. If unlocked, contact the user, I mean The Living Legend called COTULLA and tell him about your phone. Actually, just contact him, he will tell you to do a few things and if someone can help in here, it's him. We owe him the HSPL for HTC WP7 1st and 2nd generation phones and the 1st Titan custom rom (DFT) among other things.
Thanks for sharing!
f.
Click to expand...
Click to collapse
Okay, how do I check that? Here are the apps installed, aside from the normal ones.
AudioPathSwitch
AutoCountCharge
AutoCountHeadset
CameraAutoFocus
CameraTestTool
DebugFlagEdit
eMMCTool
GCFSettings
HTCLogUploadStatus
NFCTool
PPT7Extension
StorageFullTool
TestSuite
USBModeSwitch
User Trial Feedback
WiFiTool
WirelessTool
WPRControl
zAccCalibrationApp
zAdventureWorks
zAllThingShell
zAppPurchaseHistory
zBattInfo
zBingSuggestsTestApp
zCafeApp
zCasey's Coffee
zDebugMenu
zEpdDiscoverySettings
zFiddlerClient
zGestureBester
zIE Optimization
zLocation Diagnostic App
zManaged Maps
zMarbleMaze
zProximityTestApp
zSensorView
zSystemInfo
zTicTapToe
zUpdate
zUsbFnBusMenu
zWiFiCSSettings
zWPPerf
zWPRedApp
what is the ROM version installed on the device?
Cotulla said:
what is the ROM version installed on the device?
Click to expand...
Click to collapse
Check these screenshots, especially the 3rd one.
okay, from the app titles and about phone screenshots- this is most definitely an engineering/test unit. bootloader entry built into the OS? wp bld lab? how did you come across this gem?
nothingsfactory said:
okay, from the app titles and about phone screenshots- this is most definitely an engineering/test unit. bootloader entry built into the OS? wp bld lab? how did you come across this gem?
Click to expand...
Click to collapse
[REDACTED FOR PRIVACY REASONS]
By the way, I am not sure if it's right to tap the Enter Bootloader button, I'm scared! LMAO
You do realize that this can help developers reverse engineer windows phone 8 right?
mcosmin222 said:
You do realize that this can help developers reverse engineer windows phone 8 right?
Click to expand...
Click to collapse
I do, that's why I created this thread so I can help somehow, even by a bit.
EDIT: I found a setting that lets me developer lock/unlock the device (even without registration). If you want me to test or run apps that will help you guys let me know.
EDIT 2: I tried tapping the Enter Bootloader option but it does nothing. Maybe I am doing it wrong?
neilgoco said:
I do, that's why I created this thread so I can help somehow, even by a bit.
EDIT: I found a setting that lets me developer lock/unlock the device (even without registration). If you want me to test or run apps that will help you guys let me know.
EDIT 2: I tried tapping the Enter Bootloader option but it does nothing. Maybe I am doing it wrong?
Click to expand...
Click to collapse
You can try holding down Vol Up, camera, and power, or Vol Down, camera, and power to get to the bootloader.
Is there a way to access the file system?
Jaxbot said:
You can try holding down Vol Up, camera, and power, or Vol Down, camera, and power to get to the bootloader.
Is there a way to access the file system?
Click to expand...
Click to collapse
I tried doing the volume down, camera, and power combination and it displayed something like a BIOS screen very quickly, around 1-2 seconds and then continues to boot up. I only managed to read the 1st line which says 'Security Unlocked' or something. I'll try take a photo.
EDIT 2: Regarding the file system access, I found these on the phone. Will any of these help?
[REDACTED FOR PRIVACY REASONS]
neilgoco said:
I tried doing the volume down, camera, and power combination and it displayed something like a BIOS screen very quickly, around 1-2 seconds and then continues to boot up. I only managed to read the 1st line which says 'Security Unlocked' or something. I'll try take a photo.
EDIT: Here's a rather blurry shot. :S
EDIT 2: Regarding the file system access, I found these on the phone. Will any of these help?
Click to expand...
Click to collapse
Security Unlocked probably means UEFI is off, or otherwise the bootloader is unlocked. Could be very wrong on that, though. Either way, doesn't matter since we don't have a 8X ROM to cook and modify.
Jaxbot said:
Security Unlocked probably means UEFI is off, or otherwise the bootloader is unlocked. Could be very wrong on that, though. Either way, doesn't matter since we don't have a 8X ROM to cook and modify.
Click to expand...
Click to collapse
JK. http://www.xda-developers.com/windows_phone/say-hello-to-wp8-htc-8x-ruu-leaked/
This is so very serious and huge news...if it has the UEFI unlocked like an ES is supposed to be. Can you access the file system/mount device in bootloader mode?
Also, could you try and install a WP7.* xap file ( just download an app/game xap from xda or this one from here, not a sys messing one) on it? Just copy it inside phone's int meme and click on it, the installer ''should" handle the xap...
BTW,if tha XAP installs and runs I could say that phone is worth its weight in gold...cough...cough...for us and MS.
htc9420 said:
This is so very serious and huge news...if it has the UEFI unlocked like an ES is supposed to be. Can you access the file system/mount device in bootloader mode?
Also, could you try and install a WP7.* xap file ( just download an app/game xap from xda or this one from here, not a sys messing one) on it? Just copy it inside phone's int meme and click on it, the installer ''should" handle the xap...
BTW,if tha XAP installs and runs I could say that phone is worth its weight in gold...cough...cough...for us and MS.
Click to expand...
Click to collapse
Can you access the file system/mount device in bootloader mode?
I cannot enter the bootloader mode, when I press volume down, camera, and power button it just shows the (I'll call it the...) BIOS screen very quickly, and then continues to boot up. Are there any other ways to access the file system?
Also, could you try and install a WP7.* xap file on it?
I'll try later. And what do you mean by "Just copy it inside phone's int meme and click on it, the installer ''should" handle the xap..."
neilgoco said:
Can you access the file system/mount device in bootloader mode?
I cannot enter the bootloader mode, when I press volume down, camera, and power button it just shows the (I'll call it the...) BIOS screen very quickly, and then continues to boot up. Are there any other ways to access the file system?
Click to expand...
Click to collapse
Maybe it's a combination of only two buttons....or maybe there's an app for that
neilgoco said:
Also, could you try and install a WP7.* xap file on it?
I'll try later. And what do you mean by "Just copy it inside phone's int meme and click on it, the installer ''should" handle the xap..."
Click to expand...
Click to collapse
Email it to you as an attachment and try to open it on the phone.
Also, depending on your time and availability, you could contact E:V:A by PM or posting in this thread http://forum.xda-developers.com/showthread.php?t=1934388 so you could dump whatever is on that phone.
Wow, this is real HW porn! I posted partition dump instructions in that thread, but I now see that this could be even more useful in the future, for allowing us to have unlocked bootloaders with all engineering features intact. So if you could somehow get us, either a full "disk image" or preferably all of the individual partitions, that would be awesome!
All the tools needed can be found in the links of my footer. It could be that you need to install some additional USB drivers as well.. But we'll see.
E:V:A said:
Wow, this is real HW porn! I posted partition dump instructions in that thread, but I now see that this could be even more useful in the future, for allowing us to have unlocked bootloaders with all engineering features intact. So if you could somehow get us, either a full "disk image" or preferably all of the individual partitions, that would be awesome!
All the tools needed can be found in the links of my footer. It could be that you need to install some additional USB drivers as well.. But we'll see.
Click to expand...
Click to collapse
My brains! Is it possible to do that via TeamViewer or something like that? So you would control my PC?
EDIT: I got into the 'bootloader mode' (not sure if it is). I plugged it into my notebook and it installed Windows Mobile Device Center (forgot the exact name lol) and the 'Serial' mode changed into 'USB'. ?
[REDACTED FOR PRIVACY REASONS]
neilgoco said:
My brains! Is it possible to do that via TeamViewer or something like that? So you would control my PC?
Click to expand...
Click to collapse
It's not that hard and it can't be done via remote support unless you have two machines ( you need one running linux and the other one with a IM that has video also). Your best shot is to find a friend that knows Linux and has a Linux distro installed and "beg" him to do it for you.
Also, it would be wise to keep secret the rest of the info about the device. It's been known that MS roams XDA and this thread isn't good news for them, just let me put this in another way : it's like you've got a WIN8 key generator in your hands ( though this is not a solution to activate W8). Stick to PM the devs.
Gracias
More finds. I pressed camera, volume UP, and power. Got this on Windows.
CHECK FIRST PAGE. =)
Hello,
My carrier (SFR France) doesn't recognize the One SV, because it's not in their database.
How can i make the carrier believe the phone is another phone, like a Desire 601?
Thanks,
Did you try to edit build.prop?
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Well I never try to use adb without root, but I think without root you can't edit system files. Fastboot will not work. You need root or costume recovery.
Ivory_75 said:
Thanks for the answer. i didn't think it was that easy. However i'm not ready to root my phone. (Warranty, risks etc...)
I've manage to open, read, copy to SD card and modify with text editor, but how can i push it back (and not loose modifications after reboot)
(adb, something else? )
anyway. I've check the build.prop and found i need to change the ro.product.model= xxx
Now i just need to push it back. Could ADB or Fastboot do it ?
Any idea on how device identification works when it's not an android phone ?
Regards,
Click to expand...
Click to collapse
Unless you unlock your bootloader and root then there is really nothing you can do to the build.prop file. Restrictions won't allow you to make changes.
Sent from my K2_CL using Tapatalk
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows.bat and follow instructions. Takes 30 seconds - 1 minute all in all.
Thanks, but...
gee2012 said:
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows,bat and follow instructions. Takes 30 seconds - 1 munute all in all.
Click to expand...
Click to collapse
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?
Casteel said:
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?
Click to expand...
Click to collapse
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.
gee2012 said:
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.
Click to expand...
Click to collapse
What do you mean by "injects SuperSU" ?
It sounds very simple from the way you say it. Why can't I do this myself?
I believe it doesn't just mean copy it to the right place.
Does it also include putting the su binary in the right system path with the right permissions?
How does the root privilage is gained?
Does only unlocking the BL let me write to the system partition?
I would really appreciate some technical details to understand this rooting process and what this image file contains.
Thanks again!
Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.
gee2012 said:
Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.
Click to expand...
Click to collapse
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.
Casteel said:
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.
Click to expand...
Click to collapse
Look here https://www.google.com/search?q=how+root+works&ie=utf-8&oe=utf-8&aq=t and other sites how root works http://stackoverflow.com/questions/...hat-are-the-pre-requisites-for-it-to-work-wha.
With Google you can find anything
Actually, I read this also...
It only talks about gaining root privilage using some system exploit.
So, you're telling that CF-Auto-Root is running some script in its bootable image file that is using some kind of exploit to gain root access?
Shouldn't it be less "hacky" thing in nexus devices?
And how can it be that the image file is related to specific devices and not to specific stock versions?
What prevents from other apps to use this so called "exploit"?
This is probably what you are looking for...
Embedded in the boot image a folder cfroot with the SuperSU apk file, the su binary and the necessary init scripts and there is a binary under sbin does the remaining steps of copying the files to the respective places. It is not an exploit, it merely uses the boot image and the boot process to "install" SuperSU. You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
In more detail:
1. Embedded in the ramdisk is a folder "cfroot" with "99SuperSUDaemon, install-recovery.sh, su and Superuser.apk".
2. In the sbin folder in the ramdisk is a binary "cfautoroot" which does stuff like copy the above files to the correct locations and set the appropriate permissions, etc.
3. This file is called through the "recovery" script/binary in the sbin folder
4. The "recovery" script/binary is executed as a startup server via the init system in "init.rc" within the ramdisk
The result:
When you boot up, the superuser files are copied to the respective locations with the right permission, thereby rooting the system
OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
craigacgomez said:
there is a binary under sbin does the remaining steps of copying the files to the respective places.
You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
Click to expand...
Click to collapse
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:
Casteel said:
OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:
Click to expand...
Click to collapse
"cfautoroot" is a binary created by Chainfire which is embedded in the sbin folder in the kernel ramdisk. It's in the CF Auto Root boot image. Android kernels are essentially Linux kernels and have an init process which is basically a bootstrap/startup process. init.rc is part of this process. It is run when the kernel boots up. Anything within the init process is low-level and essentially run as "root". It kick-starts various other processes like zygote which is the Android process management system. This will help you understand the init process a bit better (http://www.mekya.com/blog/2012/03/android-initialization-from-init-rc-to-third-party-code/). In the init.rc file is a line which "executes" the file /sbin/recovery (which is embedded in the ramdisk along with cfautoroot). This in turn "executes" cfautoroot which takes care of copying the superuser files to the correct locations and setting the correct permission. All this is done within the init process and has elevated (root) permission.
Unlocking the bootloader does not root your phone. It simply allows you to flash "unsigned" (custom) boot images.
Any phone with the ability to flash a custom boot image can make use of this process.
Exploits make use of holes or workarounds to either flash a custom boot image or inject files into the system partition without unlocking the bootloader and are only needed if you cannot unlock the phone bootloader.
Hope this helps!
Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Thank you for asking the question and being polite yet persistent about getting your answer. I have been trying to get to this answer myself for some time now.
Sent from my Nexus 5 using Tapatalk
Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...
Casteel said:
Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...
Click to expand...
Click to collapse
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk
craigacgomez said:
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk
Click to expand...
Click to collapse
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!
Casteel said:
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!
Click to expand...
Click to collapse
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.
craigacgomez said:
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.
Click to expand...
Click to collapse
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!
Casteel said:
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!
Click to expand...
Click to collapse
Glad I could help you... It's what communities are all about... Sharing knowledge and experiences.
Sent from my Nexus 5
Excellent thread. Thanks to OP and members who responded.
Thats the problem...Android Device Manager is useless cuz there is already a pattern...I tried almost 100 times and there is no "forgot your password?" option...I need at least do a copy of my pictures.
Is there any solution to this? I feel like a real idiot...I was trying a different pattern and I forgot It...I cant believe it...
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Jerber said:
How I do that? my phone is not rooted, the bootloader is locked and debugging mode is off :S
Click to expand...
Click to collapse
That could be a problem. I think that it might be done using adb but not sure if it can be done without root/bootloader secured
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
Testing it would be really easy. just set a pattern and then delete that file.
Lets us know is it is that easy to hack it or not.
Since obviously you know better, share your findings with us.
dahawthorne said:
If cracking an Android device were as easy as deleting a file then I doubt that there's much value in any security on a device at all, no?
Surely this has to be a reinstall of the ROM...? Maybe with no-wipe to preserve the data?
Genuine question - I don't know for sure.
Click to expand...
Click to collapse
The phone has to have an unlocked bootloader and twrp installed, so you already compromised its security yourself. You could relock the bootloader, flash a stock recovery and encrypt the phone, that would solve the issue.
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
dahawthorne said:
"Since obviously you know better, share your findings with us."
Look, guy, just because you're a senior member there's no need to be offensively sarcastic.
Maybe you didn't get as far as my last comment: "Genuine question - I don't know for sure."
Click to expand...
Click to collapse
Not being Sarcastic at all. Making a point. If you got offended, sorry about that.
I posted what I have , after testing it myself. Had the same issue on Lollipop.
Further more, I will share another piece of Info in here.
When You are able to access any Solaris/Linux server using a console , and boot it from DVD, you can simply edit the /etc/shadow file and reset even the root password. Does that mean Unix/Linux aren't secure OS's ?
When you have access to OS level files you can practically hack every OS.
Same goes here. When you have unlock bootloader and modified recovery you can access system files that otherwise would be inaccessible. if he can have access to that file and remove it, he will gain access to his system.
Well, I tried everything that I could because my phone is no rooted, and the bootloader is locked, plus, the debugging mode is off too... so I was close to give up, BUT finally I remembered that my phone was connected to Airdroid!; if Airdroid is connected to the phone It can bypass the lockscreen and you can access to the internal memory anyways with the Airdroid website!, so I did a full backup of all my pictures and then I did a factory reset!, the copy was a kinda slow but I didn't care of course!. What a relief!!!
So, I really recommend use Airdroid (and have the app connected of course), it saved my life!, I was really frustrated about this, I cant believe Google doesnt provide the old way the restore the pattern like in Kitkat and Jelly Bean.
wizardwiz said:
I think there's a file not sure if it is directly under /data/system or one of it's sub directories, but basically what I did was to boot to TWRP , use the built it file manager and delete that file. I could then access my phone. I will search maybe I kept the file name somewhere.
EDIT:
Just remove this file /data/system/gesture.key
and reboot.
Click to expand...
Click to collapse
It worked like a charm!
I have a fingerprint enabled phone. forgot my pattern, followed your suggestion and presented in my phone are data/system/gesture.password.key and gesture.pattern.key so I deleted the pattern.key (guided by forgotten pattern) I rebooted and my apps were optimized and voila the phone is unlocked.
However, I tried accessing the fingerprint menu on my phone but refused access. I then used root explorer, browse to aforementioned location, copied and renamed gesture.password.key to gesture.pattern.key as it was before deletion.
went back to the security setting of my phone, setup pin option (scared of forgetting the pattern again) and phone screen locked. I try using my fingerprint to unlock (which I am accustomed to) and voila! it says pin required for additional security. entered Pin and the fingerprint menu became functional again and all previously stored fingerprints remained unaltered....QED