My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
martinwahlstrom said:
My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
Click to expand...
Click to collapse
You only have to flash a custom kernel
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
martinwahlstrom said:
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
Click to expand...
Click to collapse
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
dylanel98 said:
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
Click to expand...
Click to collapse
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
martinwahlstrom said:
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
Click to expand...
Click to collapse
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
dylanel98 said:
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
Click to expand...
Click to collapse
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
martinwahlstrom said:
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
Click to expand...
Click to collapse
Btw, installed Update-SuperSU-v2.02.zip from SD using TWRP.
Great... Now in bootloop... Help!
Edit: Recovered from looping.
Still no root after several tries.
Related
I was trying to disable FSYNC using the method described by poofyhairguy. I did it via terminal, in su. I mounted /system in rw mode, I copied libsqlite.so and libsqlite_jni.so into backup copies, and overwritten them with copied provided by poofyhairguy. Alas, I forgot to chmod, so they were left with whatever permission they came from. I rebooted the tablet and now it is permanently in the starting screen with big ASUS letters across. I cannot even turn it off!
Help, please, what do I do? I don't really know much about Android, so please use simple explanation.
Just to add some details. My Prime is stock, rooted but not unlocked.
I also don't seem to be able to reach it from ADB. I did install ADB and drivers on my PC a while ago, when I rooted it. I'm trying this now:
- connect Prime to PC
- reboot with volume down, select a USB symbol
- PC says "installing drivers" and "ready"
- in adb shell, when I try "adb devices" it shows an empty list
Any help?
OK, here is more information and more questions. I can start the tablet in fastboot mode (USB symbol on screen). After reinstalling ASUS suite and Google SDK I connected the tablet to my Windows 7 laptop. It searched for drivers for a while, installed and said "ready".
"adb devices" returns and empty list. "fastboot devices" returns one entry, a long hexadecimal number and the word "fastboot". Does it mean that I can see my tablet via fastboot but not adb? Does adb work when tablet is in fastboot mode at all?
Does it mean that the only option is to reflash ASUS firmware?
@Felisek Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Sorry, I'm not much expert in android underhood that I can help you more but looking at your problem doesn't look like you have bricked your device so keep hopes. Someone having more knownledge might come and help you.
btw; AFAIK, adb and fastboot are different kinds. You see fastboot.exe in the sdk package? yes that links with fastboot option on the devices. But I might be wrong as well.
May be you try entering into fastboot and use fastboot.exe, then go to the path where you modified the files. Either replace them to original ones or chmod. But I don't know whether this gonna work.
CRACING said:
Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Click to expand...
Click to collapse
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Felisek said:
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
Click to expand...
Click to collapse
Hmm may be you are right so reflashing whole ROM is required.
Felisek said:
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Click to expand...
Click to collapse
Recovery? but you said you haven't unlocked or you mean stock recovery?
Yeah, upon reflashing, you will lose root but hey, you can root again using the new method (motorola's) and its not at all risky as unlocking. :good:
May be you can wait for sometime, I hope someone comes up guiding you how to replace/modify the system files using adb or fastboot.
CRACING said:
Recovery? but you said you haven't unlocked or you mean stock recovery?
Click to expand...
Click to collapse
There is a "RCK" option on startup, I thought that was recovery. But, yes, I mean stock recovery, if this is how it is called. Download stock firmware, put it on a microSD, rename it to EP201_SDUPDATE.ZIP, reboot and apparently it installs automatically.
When I was making my guide I tried using the old ICS libsqlite.so and libsqlite_jni.so files and softbricked in the same mannor. The only way I found to fix it was to flash the stock ROM as it says to do in my guide.
Note that unless you purposefully wipe your data in the recovery your data should remain intact from my experiance with it. The way the stock Asus recovery seems to do it is to blow /system away (so yes you must re-root, etc).
Good news. I unbricked my Prime by reflashing the stock ROM, using the method described by poofyhairguy. All my apps and settings survived. I only lost root, so even rootkeeper cannot recover it. Not too bad, after all.
Sent from my Transformer Prime TF201 using Tapatalk HD
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 16 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
flo (Nexus 2013 Wi-Fi): CF-Auto-Root-flo-razor-nexus7.zip
deb (Nexus 2013 LTE): CF-Auto-Root-deb-razorg-nexus7.zip
Very happy to see you here too. Thx for your work.
Sent from my Nexus 7 using xda premium
Chainfire said:
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
Click to expand...
Click to collapse
For Flo, bootloader is volume down and power.
Newbie question - Once rooted with this method will I still get OTA updates? If so will it retain root?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
User_99 said:
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
Click to expand...
Click to collapse
Thats not true... I got the 4.3.1 update for my deb and had root+twrp. After hit install it boot to twrp and installs the ota after boot up root is still there. No Problems here
Great that it works fine for you!
But that will work not for all customers. Some reported that after they recived and downloaded the OTA they got an error while installation in custom recovery.
I rooted my Nexus 7c LTE..
now i can see an unlock logo in startup... anywhere i can remove it?
thanks!
No, that's normal for unlocked bootloader. Only not shown when you close the bootloader again.
Thank you!
any idea how to close the bootloader?
http://www.wugfresh.com/nrt/
Nexus Toolkit - easy way to lock the bootloader. But, for Root, you need an Unlock Bootloader...
decide...
THANKS!!!
is the auto-root still working on new kit-kat update?
ritz_cal78 said:
is the auto-root still working on new kit-kat update?
Click to expand...
Click to collapse
Nope. Already tired twice.
so if i want to install TWRP recovery, i have to flash it after i install CF-auto root?
how do i get to the steps u mentioned using mac?
xdviper said:
Nope. Already tired twice.
Click to expand...
Click to collapse
It worked perfectly for me first try. I should say that I had just rooted my Nexus 7 LTE with Chainfire's method before I updated my N7 OTA. After the update, root was lost. I simply went through the steps again and re-rooted it. I should also state that I did not lose any of my data on during the 2nd root.
I'm going to donate to Chainfire.
same here, only difference,
I came from a factory image fash. Auto root worked
Send from the N7²
Will this work a stock n7 2 running KK?
xbs said:
Will this work a stock n7 2 running KK?
Click to expand...
Click to collapse
Worked OK for me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
So here it goes!
I have this phone, a Cherry Mobile Aeon [ full specs: please find on google. Can't post links yet, apparently. ], and rooted it. It rooted successfully the first time ( with usb debugging enabled and everything. ) and so, as idiotic as I am, I installed CF3D on a JB phone so it ended up bootlooping. And so I data/factory reset it by STOCK RECOVERY then I tried recovering it by ADB but then, everytime I type the su command, it always says UI CONNECT - TIMED OUT or something like that.
And so I've searched Google on why is that happening and found out that it prompts if the device is unrooted!
Now I can't root it back cause I don't have USB Debugging enabled. And I can't get it to the service center because they said that they don't have the software for this phone yet! WHICH IS VERY IDIOTIC!
Please halp.
LockeMishil said:
So here it goes!
I have this phone, a Cherry Mobile Aeon [ full specs: please find on google. Can't post links yet, apparently. ], and rooted it. It rooted successfully the first time ( with usb debugging enabled and everything. ) and so, as idiotic as I am, I installed CF3D on a JB phone so it ended up bootlooping. And so I data/factory reset it by STOCK RECOVERY then I tried recovering it by ADB but then, everytime I type the su command, it always says UI CONNECT - TIMED OUT or something like that.
And so I've searched Google on why is that happening and found out that it prompts if the device is unrooted!
Now I can't root it back cause I don't have USB Debugging enabled. And I can't get it to the service center because they said that they don't have the software for this phone yet! WHICH IS VERY IDIOTIC!
Please halp.
Click to expand...
Click to collapse
Your phone not booting after installing cf3d?
Hell_X said:
Your phone not booting after installing cf3d?
Click to expand...
Click to collapse
It's stuck on bootloop.
LockeMishil said:
It's stuck on bootloop.
Click to expand...
Click to collapse
dont worry
cf3d creates a backup zip which can be flashed if you get bootloop simply boot to cwm recovery and then flash the zip it will be on /sdcard/ something related to cf3d.zip
Hell_X said:
dont worry
cf3d creates a backup zip which can be flashed if you get bootloop simply boot to cwm recovery and then flash the zip it will be on /sdcard/ something related to cf3d.zip
Click to expand...
Click to collapse
That's my problem. Since my phone is kinda new on the market and a very remote brand for that matter, I haven't been able to find a CWM that would be compatible on my phone. Which sucks.
And also, I haven't seen that back-up you are saying. I think it is stored on the internal sdcard. :/ Which I cannot access, obvs.
LockeMishil said:
That's my problem. Since my phone is kinda new on the market and a very remote brand for that matter, I haven't been able to find a CWM that would be compatible on my phone. Which sucks.
And also, I haven't seen that back-up you are saying. I think it is stored on the internal sdcard. :/ Which I cannot access, obvs.
Click to expand...
Click to collapse
If you have your Rom Backup than flash that?
Hell_X said:
If you have your Rom Backup than flash that?
Click to expand...
Click to collapse
As I was saying, I am only rooted, no cwm, no way of flashing and since I am an idiot. I didn't have back up too. Can you suggest an easy way on porting CWMs though?
So.. My first tread here.
Anyways, let's jump into the topic itself.
So today foolishly, I used TWRP and "kind of" deleted the whole operating system by accident.
How could I recover it, and no, I do not have ANY backups, I used to have but seems like I deleted them aswell..
The phone is Nexus 4 and Android version is 4.4.4
This is kind of urgent, since I need my phone to work right now.
All help is appreciated, waiting for your replies,
-Toquu
Anyone..?
Toquu said:
Anyone..?
Click to expand...
Click to collapse
You have 2 options:
Use adb to push a new rom to the phone and install in TWRP.
Use fastboot to flash the stock img files to the phone while in bootloader/fastboot mode.
es0tericcha0s said:
You have 2 options:
Use adb to push a new rom to the phone and install in TWRP.
Use fastboot to flash the stock img files to the phone while in bootloader/fastboot mode.
Click to expand...
Click to collapse
Could you find any step-by-step tutorials? I can't
Toquu said:
Could you find any step-by-step tutorials? I can't
Click to expand...
Click to collapse
I am new so i can't post links but type in google accidental wipe android nexus 4
Toquu said:
Could you find any step-by-step tutorials? I can't
Click to expand...
Click to collapse
Did you bother to look in the Nexus 4 forums here?
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
My preferred method would be by adb though.
adb push nameofrom.zip /sdcard
while in recovery.
If you need adb http://forum.xda-developers.com/showthread.php?t=2317790
maybe it's impossible
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Rortiz2 said:
What version of FireOS?
If you're on 4.X root it and flash a working recovery with dd.
Click to expand...
Click to collapse
I'm on 5.6.1.0, I've found no way to root without recovery.
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
Not without recovery, all the guides require to flash an update via adb on recovery
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
detesto said:
Did you ever figure this out? I'm having the same issue with pretty much the same scenario. I can boot to the bootloader/fastboot mode but recovery is not working.
I've tried some of the bootloder unlock methods to try to flash recovery but to no success. Other than that, the table boots to the stock ROM ok, but that's really no fun. I can't even factory reset because that needs recovery, lol.
Click to expand...
Click to collapse
detesto said:
I'm on 5.6.1.0, I've found no way to root without recovery.
Click to expand...
Click to collapse
Rortiz2 said:
Dang. So you can downgrade to 4.5.3?
@bibikalka is possible?
Click to expand...
Click to collapse
detesto said:
Not without recovery, all the guides require to flash an update via adb on recovery
Click to expand...
Click to collapse
Rortiz2 said:
Sorry for the late reply.
There's ONE solution.. It's not easy...
You can flash recovery with aftv-tools but IDK the recovery adress. Maybe @bibikalka can help us?
Click to expand...
Click to collapse
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
bibikalka said:
Unfortunately, the aftv-tools were patched a while ago, sneaky Amazon updated boot0 on firehd 2014 via some hidden data in either LK or TEE1. So that method won't work.
So without a recovery or root there are really no options.
Now, there is always the path to trigger the BootRom mode via some contacts (as on other models), but nobody spent the time yet to figure that out:
https://forum.xda-developers.com/fire-hd/general/diy-fire-hd-6-7-bootloader-unlock-t3894996
Pinging @k4y0z and @xyz` for completeness.
Click to expand...
Click to collapse
Dang. So there's no pic of the board? For see what points can be..
Rortiz2 said:
Dang. So there's no pic of the board? For see what points can be..
Click to expand...
Click to collapse
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
bibikalka said:
Plenty of good pics:
https://forum.xda-developers.com/fire-hd/help/jtag-t2933430
Also, one user tried to find the contacts, but was not successful. xyz' indicated where he thought the contacts might be:
https://forum.xda-developers.com/showpost.php?p=78789821&postcount=90
Click to expand...
Click to collapse
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Rortiz2 said:
Nice pics. Maybe with root you can easy brick it an enter to bootROM mode no?
Code:
echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=/dev/zero of=/dev/block/mmcblk0boot0
echo 'EMMC_BOOT' > /dev/block/mmcblk0boot0
md5sum /dev/block/mmcblk0boot0
Click to expand...
Click to collapse
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
bibikalka said:
But if I have root already, why would I mess with Bootrom??? I don't have amonet for this device, so I would essentially brick a working tablet
Click to expand...
Click to collapse
Yep, you're right.. It needs to be ported to MT8135 and it qould be difficult... The only user that knows how to do it is @k4y0z.
He needs the tablet for test it.
reedradar said:
A lot of post are about being 5.x.x and can't access recovery mode but I am on 4.5.3 and I have flashed TWRP before on this firmware. I used the CM-11 rom and realized it's only Android 4.4.4 and needed Android 5.x.x well i flashed back to stock fire os and the stock firmware still 4.5.3
MY problem:
When i boot into recovery mode it just shows "Amazon" and reboots back to stock OS, I have root and flashify it just won't boot into recovery. Any help?
Click to expand...
Click to collapse
I managed to get the stock Amazon recovery on to the fire tablet on 5.6.10 using EX Kernel Manager and from there could sideload the OS i needed to get back in to TWRP.