Related
I'm no expert when it comes to the topics of rooting and getting access to the emmc and all of that good stuff. I more specialize in ROMs and themes and stuff, the less complexed stuff lol
Someone has posted an idea in the general forums in relation to permanent root, I'm not sure if he posted it here or not. So here's what he wrote....and is it possible? Or does it have to be done manually first before this idea can happen?
Originally Posted by deliberate187
In order to unlock the phone, we have to figure out what the protected sectors are first and all related flags. If an Android app could be made to have direct read access to the eMMC filesystems (including write protect flags) and save a log to the SD card detailing these items, this would be ideal.
Then all that would remain is a program to undo the write protection (and re-do it if necessary to unvoid warranty)
If anyone is willing to create these programs, I would be more than happy to test them out on my own G2.
However, I think the keys to the mystery may lie in the recovery image, and/or in the bootloader itself. Has anyone disassembled these yet?
Click to expand...
Click to collapse
Sorry to have to tell you but this is all old information stuff we already know just are unable to do anything about it. Its harder then just coming up with an idea of something. Now if we knew a person that programed the g2 in htc factory then all would be good but as of now we just dont have the information we need to do anything
thanks
Thanks for the idea. Some people will be mad you didn't post in the root thread though.
File under "I'm no expert but..."
Here is one observation I have noted in my exploration. The root filesystem and system partition are mounted with the flags "-o ro,relatime" but in addition the /system partition has ",errors=continue" leading me to believe that this change is in fact written to the release configuration rather than to the eMMC itself. Can anyone try to get a permanent write to the fstab and see if this can net us permanent root? Possibly take a temp root session and remount the system and / filesystems read/write to see if writes stick... just an idea.
The errors=continue flag allows the ext3 filesystem to continue working even if there was a read/write error.
I've been able to get the system to change to r/w a couple times while wandering through root explorer. I have made subtle changes to certain folders such as moving txt files but nothing has ever been permanent. I can't really tell you how I did it either seeing as I can't replicate it on demand...I'm assuming it still gets written to cache despite being in the /system
Sent from my T-Mobile G2 using XDA App
heyy, I'm not punchie, I've got what the doctor calls a relaxed brain
I am thinking there should be a set of adb commands to unlock the nand. I am definitely thinking a nand dump and full disassembly of the bootloader and recovery image could be absolutely crucial in discovering what needs to be done. Just a thought, has anyone done a nandroid backup of the G2 yet? I'm pretty sure TMob doesn't have HTC encrypt its bootloaders...
deliberate187 said:
I am thinking there should be a set of adb commands to unlock the nand. I am definitely thinking a nand dump and full disassembly of the bootloader and recovery image could be absolutely crucial in discovering what needs to be done. Just a thought, has anyone done a nandroid backup of the G2 yet? I'm pretty sure TMob doesn't have HTC encrypt its bootloaders...
Click to expand...
Click to collapse
if you can figure it out, go for it and i wish you luck
deliberate187 said:
Here is one observation I have noted in my exploration. The root filesystem and system partition are mounted with the flags "-o ro,relatime" but in addition the /system partition has ",errors=continue" leading me to believe that this change is in fact written to the release configuration rather than to the eMMC itself. Can anyone try to get a permanent write to the fstab and see if this can net us permanent root? Possibly take a temp root session and remount the system and / filesystems read/write to see if writes stick... just an idea.
The errors=continue flag allows the ext3 filesystem to continue working even if there was a read/write error.
Click to expand...
Click to collapse
If it were only this easy.
Re-mounting /system as r/w is part of the rooting process. This does not result in changes written to eMMC. In fact, the controller "lies" to Linux that the change has been synced. From then on, Linux holds the changes in its cache which, when dropped or rebooted, reverts changed files to their original state (because they were never written in the first place.)
The ext3 continue on errors thing is merely a way to skip fsck in the event that the read-only system has issues in the journal (very unlikely to happen, since nothing can write to it.) Presumably, this only covers an oversight in OTA updates (where the journal of the image provided by the OEM is dirty for some odd reason.) Again, since nothing can write to /system, it's all but an impossible scenario (nothing can write to the journal either...)
As for marking "sectors" as write-protected or not, that's also easier said than done. Entire partitions are locked, and half of the space is mysteriously "missing." It's difficult to see what's really going on from userland, as the device is deceptive as to what is and is not being written, or what is even stored on the eMMC in the first place.
The real solution is to exploit either the boot-loader or eMMC (re)/initialization somehow to allow a) unsigned firmware to be loaded and/or b) allow booting without write protection, allowing us to c) flash rooted rom to the phone and/or d) disable said protection. The unlock procedure will likely be similar to Unrevoked, as that is essentially the same situation (aside from the controller issue.)
All of this is covered in the wiki and various threads - check those out, if you find a way around it everyone would be glad to hear it.
HamNCheese said:
If it were only this easy.
Re-mounting /system as r/w is part of the rooting process. This does not result in changes written to eMMC. In fact, the controller "lies" to Linux that the change has been synced. From then on, Linux holds the changes in its cache which, when dropped or rebooted, reverts changed files to their original state (because they were never written in the first place.)
The ext3 continue on errors thing is merely a way to skip fsck in the event that the read-only system has issues in the journal (very unlikely to happen, since nothing can write to it.) Presumably, this only covers an oversight in OTA updates (where the journal of the image provided by the OEM is dirty for some odd reason.) Again, since nothing can write to /system, it's all but an impossible scenario (nothing can write to the journal either...)
As for marking "sectors" as write-protected or not, that's also easier said than done. Entire partitions are locked, and half of the space is mysteriously "missing." It's difficult to see what's really going on from userland, as the device is deceptive as to what is and is not being written, or what is even stored on the eMMC in the first place.
The real solution is to exploit either the boot-loader or eMMC (re)/initialization somehow to allow a) unsigned firmware to be loaded and/or b) allow booting without write protection, allowing us to c) flash rooted rom to the phone and/or d) disable said protection. The unlock procedure will likely be similar to Unrevoked, as that is essentially the same situation (aside from the controller issue.)
All of this is covered in the wiki and various threads - check those out, if you find a way around it everyone would be glad to hear it.
Click to expand...
Click to collapse
Listen to this dude. Absolutely correct.
I need some help XDA. I don't know if you'll help or not, but I'm law enforcement and I need to access a locked Droid X. None of the forensic solutions available support bypassing the lock code and I don't have access to the Gmail password for this phone.
What I was looking for is a way to flash the phone with a rooted recovery image that would not overwrite the user data on the phone, so that I could recover the contents of the phone. I've looked at several different options including adb/custom recovery images but it looks like I need to access the USB debugging mode to root the phone.
Can this be done and if so how. Is someone out there willing to help me with building a custom recovery image that doesn't overwrite or dump the user data?
maybe im oversimplifying this but have you tried just plugging it in to the computer? my x will automatically connect as a usb drive and allow me to access the files on the sd card, obviously this wont help if you are wanting call logs or txt messages unless they backed them up to the sd card, just a suggestion before custom recovery
xsurferx, I have tried that and the only thing I get is the phone will charge. In device manager the phone is recognized as a Motorola MB810 USB device.
There is no way to access the device available through Windows Explorer.
My bet is that the person who took the time to ensure that privacy is more important than convience ( deny data connect from usb, wipe sdcard, and strong enough password/encryption) has looked further into other routes aswell. But I don't know of any kind of flashable that would both preserve data and reset the lock screen. The phone is probably one of the best suited to not devulging its information. It would probably be easier to get a court order for the cell records. But I wish you luck.
Dispatched at the Speed of Light from my XOOM
If you're trying to access the SD card, take it out and use a SD card reader on a computer and should be able to fix permissions that way? Maybe....
Sent from my DROIDX using XDA App
Thanks chbennet, I've already retrieved the cell phone records from the provider (via Search Warrant) and examined the victim's phone in this case. But as always I'd also like to have all of the evidence including the suspect's phone contents. I already have the SD card contents.
There has to be a way similar to the iPhone to restore the system data to default while keeping the user data (call logs, SMS, Images, video, browser history, etc.) in tact.
The iPhone does this by creating a system partition and a user partition. Is this the same in Android phones? Or is it one partition and directories?
I'd still like to see if there is someone that could build a ROM flash that would disable the passcode.
If it is rooted, there was probably a nandroid backup on the card. If there was, this might help.
http://androidforums.com/evo-4g-all-things-root/319602-read-copy-contents-nandroid-backups.html
Dispatched at the Speed of Light from my XOOM
In short, i deleted my photos by accident, and deeply desire to recover them.
Data Recovery programs wont work on my Google Nexus 4, for a combination of reasons. Namely, because it is not a usb mass storage device, it is internal memory, and because the phone has not ever been rooted. If it is possible to recover the photos without rooting the phone, this would be favorable. But i doubt this is possible.
Is there a way to root my phone without causing a "factory wipe/reset"? Perhaps by avoiding unlocking the bootloader?I am not even 100% sure if this can be achieved on 4.4.2. as of now. I am continuing to investigate, but if anyone has the know-how, please let me know.
this forum here, suggests something that might work, but at the end of the forum, it suggests that 4.4.2 is still impossible to root without wiping.
-There are methods of scanning the phone after it has been rooted, but i can't find the right kind of rooting i need.
-There are methods of copying the phone's hard drive -bit-by-bit- to my PC in .RAW format, and then converting this into something that can be mounted like a real drive, which could be scanned and from which photos could be recovered., but this method requires a rooted phone as well
-there is a possibility of trying to mount the phone on a linux OS, and then scan it possibly. but i don't know if this is impossible.
i am reading the basics in the meantime.
LG Google Nexus 4, 4.4.2
Build:KOT49H
kernel:
3.4.0-perf-g2cae413
[email protected] #1
wed Nov20 14:54:28 PST 2013
Desktop PC: Windows 7 Professional 64bit, service pack 1.
Laptop: mac...
you can read more about things i have tried and my other concerns, in greater detail below.
LOTS OF METHODS, LITTLE CLARITY
I just came back from visiting some dear friends in china and purchased an upgraded version of dropbox. Before I uploaded my photos, I accidentally deleted my entire album.
What is the safest and surest attempt for recovery?
1. i need to avoid installing anything on my phone as much as possible - (lest it overwrite the empty areas where the "deleted" photos reside.)
2. i need to keep my phone off as much as humanly possible (lest it overwrite the empty areas where the "deleted" photos reside.)
3. almost without saying - id like to avoid bricking my phone, (lest it destroy my "deleted" photos)
SOFTWARE RECOVERY SECTION
All known software recovery programs won't find any data on my phone because either they are made for scanning mountable drives, USB mass storage devices, or some simply cannot scan the device unless i root my phone (although I am not sure if rooting is directly correlated with successful scanning, or if rooting the phone simply allows me to carry on with other necessary steps prior to "successful scanning"- like allowing me to installing apps that allow me to mount the internal memory as a scannable drive). Enabling USB Debugging, or enabling/disabling MTP is not the same as enabling USB mass storage mode. Seeing the Nexus 4 as "portable Device" under my computer does not mean it is a mounted drive that i can scan with a recover program. No matter what, nothing seems to work with the Google Nexus 4 as it is now.
***I first tried installing the driver's through the ANDROID SDK, by unzipping the contents from the downloaded zip file and by double clicking the .exe file. Double-clicking the .exe file resulted in a cmd dos-style window popping up and immediately disappearing. Perhaps i needed to put the extracted folder on "C:\"?
REGARDLES....later, I have used WugFresh Nexus Root Toolkit v1.8.2 for ensuring proper driver installation for my phone. I have only used this software to install drivers. It walks you through bad-driver uninstallation/clean up, it retrieves the latest drivers, installs them, and then tests their workability for you and lets you know if the drivers were successfully installed.
I have not used Wug's toolkit to root or hack my phone... yet....
Below is a list of software I have used on my Windows machine and my mac. These simply will not work with the phone as it is right now.
Remo
TenorShare
Bycloud android data recovery
Android Data Recovery
Dr. Fone
Recuva
- i havent tried disk digger. but it requires a rooted phone.
SO simple methods will simply not work? Please correct me if I am wrong.
BIT BY BIT CLONE METHOD
This seems to be the most tedious (but thorough) method for actually preparing something that can be truly scanned for photo-recovery. This method seems to create a bit-by-bit copy of the phone to my computer, which can be converted and mounted and then scanned.
However, it requires rooting. Not to mention, it recommends non-destructive rooting. Which leads me to the next section ...
ROOTING section (and its problems)
In the fruitless sections listed above, it always seems to lead towards rooting as a requirement. Most people say you should root your phone when you first get it, because, i suppose rooting is "synonymous" with a wipe/reset. I believe this reset happens as a result of the bootloader being unlocked. According to MY limited understanding, this unlocking process essentially causes a "factory reset" which wipes the phone, and then catastrophically overwrites the precious space where the deleted photos currently reside. this is unacceptable. I imagine, this "reset" is for security reasons.
Most people seem to suggest that you make a back up before you root. This isn't helpful for my situation because we are talking about retrieving deleted data. I cannot make a back-up of deleted data.
Is it really possible to root without wiping the Google Nexus 4?
Is it even profitable to consider rooting a viable option? I don't imagine myself enjoying a rooted phone as much as others on this forum. I would hate to be creating a black hole for malicious software to breed. i am only concerned with data retrieval for this one time in my life. Is rooting the only viable option? If i root, won't that make the previously mentioned software-scanning section (e.g., Dr. fone), more viable than the BIT-BY-BIT section tedious and pointless by comparison?
All in all, I think it most likely that i will need to root my phone and do the bit by bit copy. If a rooting-first-step is the final conclusion, then I am looking for clear and careful advice for my specific phone on how to root it without jeopardizing the deleted photos (e.g., avoiding a "factory reset" from unlocking the bootloader, or perhaps avoiding unlocking the bootloader altogether) and how to hopefully carry on from there. I don't even know if avoiding "unlocking the bootloader" will virtually guarantee a non-destructive root method
Rooting gets crazy because it leads to necessary installations of SuperUser, busybox, kernels, roms, etc... There are so many unfamiliar vague terms for a beginner like me and it is taking tons of time to break through. I am uninterested in keeping my phone rooted, or maintaining a lifestyle with a rooted phone. if we can move expeditiously from point A to B and then back, (get in, get the photos, and get out,) that would be the most awesome plan.
LINUX METHOD?
is there another way to get to the deleted photos?.
I do not know if 'mounting' the phone is akin to 'mounting' a scannable drive. http://www.youtube.com/watch?v=fw2MKGIgyF4
maybe this is another wild goose chase?
IN SUMMARY
1. It would be helpful if there was a root-free photo-recovery software solution that actually works (this is unlikely to be in existence) with an unrooted nexus 4
2. It would be helpful if it is possible to root without destroying my chances of recovering my deleted photos, with the goal of allowing recovery software access (deeper access) to my phone, i.e. disk digger or if necessary... a bit-by-bit copy to my PC.
3. it would be interesting if the nexus 4 can be magically mounted and scanned on the linux operating system
4. It would be MOST HELPFUL if there was a clear consensus on what direction to take, because there is a lot of misinformation out there. One wrong step and i could end up shooting myself in the foot twice (if i inadvertently reset my phone), or three times (if i brick my phone).
5. can the phone be put back to normal (i.e. unroot) after rooting? or does this require that i make a full backup of the phone in its current state? ( i tried using WUGS toolkit to backup my media, but it wont do it unless i unlock the bootloader... back to that problem again )
I'm sorry for sounding like an idiot. I have been at this for a more than a few hours. I sincerely appreciate any help and consideration towards this specific situation in advance, and the hope that this forum has already offered me.
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
DrFredPhD said:
Impossible to root 4.4.2 without unlocking the boot loader and wiping the device.
Click to expand...
Click to collapse
Same problem.... There isn't a solution yet? :crying:
fabrollo said:
Same problem.... There isn't a solution yet? :crying:
Click to expand...
Click to collapse
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
Nope, you have to unlock the bootloader and that wipes the device
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
fabrollo said:
And after i should try to recover all the wiped files with diskdigger for example? Maybe the datas that we was searching will be found?
Thanks... if i must try this way to solve my problem i will bite the bullet...
Click to expand...
Click to collapse
The chances of recovering anything is very small
Sent from my Nexus 5 using XDA Free mobile app
Hi,
Is there *full version free download software* for *data recovery* (that *actually works and renders results*) to be used on ●*non rooted Android Note 4*●, in order to assist in recovering *deleted files* "*post 《factory reset》*".
The files in question are "*(.doc extension)*", that are associated with "*Colornote App*"; which were already available under, "*data" file*, in ●*Device Storage*● media, *prior* to process of"*《factory reset》*"and unfortunately,were "*not backedup*".
I do appreciate any *professional assistance* to restore my missing files...
I would say your chances are very low - you could try something like this (Method 2): https://www.gihosoft.com/android-recovery/recover-data-after-factory-reset-android.html
Probably stating the obvious here, but if you had done a backup with Samsung SmartSwitch or Kies or some other method before doing the reset, those files would probably be in the backup. 'Professional assistance' (ie Professional Data Recovery services) will likely cost quite a bit - so I guess it depends how much you really need the files back. The important thing would be not to use the device in the meantime, as you risk overwriting the area the files were stored on.
When I plugin my Samsung Galaxy J7 Prime and then select recovery module and it show as connected and then I select android data recovery option and then select recover documents only and then click next. Then it show and detected device model, downloading package and it went like that till 99% uncertain if it hit 100% or not and then it caused my device to reboot and after it reboot now it is asking for a password to start up device but I tried device screen password, google account password and samsung account password but all didnt work. Thus it shows have 7 attempts left before factory reset itself.
The boot up looks a bit different from normal too, unsure if it is coming through a different type of boot and if there is a way to reverse to how it was earlier?
In recovery mode it shows in recovery log pid 2064 ran. where first line filesystem table code was;
0/ efs ext4/ dev/block/platform/1354000.dwmmc0/by-name/EFS(/dev/block/mmcblk0p3) 0
and in following
#ls /cache/recovery
ksmg
-rw------root root 8190724 2022-04-02 11:19 last_ode_dumpstate_err_check_password.log
From what I could see further in log it seems like maybe dr fone tried to root phone since I see files seem to have been overwritten probably as same file name shown where earlier recorded in time stamp as either 2017 or 2008 and underneath that dst is run with today tim stamp.
What would be method to solve to get back to normal working state without any data loss?
It seems when check via dr fone transfer showing as mem capacity 2797mb and 1362mb used whereas it should show as 32Gb, also when start up it says Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying. Also in recovery mode it shows No support single sku supported api:3.
And when try backup option no files come up on scan does that mean the Dr fone recovery package that it installed wiped out the data? Or is it like in another different boot system for recovery? How to solve this problem?
Also any backup software you think could backup stuff before applying any drastic fixes
I think your phone internal storage is corrupted because of Dr. Fone and this is caused by the data encryption inside the phone and I think that it requires the encryption password, and to solve this problem, you must flash a modified recovery like TWRP or CWM and then pull all the data by making a MOUNT of the internal storage it will only works on old Android version 6.x or 7.x but you can try
My android is 6.0.1 so I think it should work, do you have any video tutorials or a thread with stepwise instructions to get twrp or cwm to backup current data and later restore?
Also any idea if use the dr fone repair device feature it might fix?
Dr.Fone only one thing do transfer WhatsApp chat between android and iOS all else features not work perfect so try another way, ask google how mount internal storage on android phones by twrp it’s easy and not need a tutorial just flash a custom recovery and don’t let device to boot enter recovery mode immediately and go to mount and press mtp or mount storage
Looks like the device name has got renamed as well best try to see if have a file explorer or manager for android so can see if files still intact? Any pc softwares that can be used to clarify without need to unlock screen since it is asking for a pass saying Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying.
If the files are intact then I can try twrp or odin cf root flashing to see if can flash home version file so files possibly stay intact. Or if they are anyways not then will try factory reset via recovery mode and then will need recommendation of good software to recover data for free
Any ideas?
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
blackhawk said:
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
Click to expand...
Click to collapse
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
NW_Work said:
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
Click to expand...
Click to collapse
Not on an unrooted phone. You can try this.
If you used Drfone it has likely already encrypted the data with their own encryption key.
Hopefully some of your data is backed up somewhere else because this is a dead horse... I believe.
I be more concerned about salvaging the phone at this point. It's a tough lesson from the U of hard knocks... don't repeat it. Sorry.