Related
I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.
so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.
Post Removed to maintain consistancy, see 1st post in thread.
root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title
Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.
Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.
Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise
HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!
New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need
confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).
You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk
i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.
My TF300 is on stock and is unrooted with a locked bootloader. However, despite this, it is no longer booting into the stock ROM. It gets stuck on the bootanimation phase with the loading circle constantly circling round, even after a few hours. It hasn't moved on from this stage unfortunately and I was wondering if there was anything that could be done? I know I could try wiping my data, but there are files and app data that I would not like being lost so is there any way they would be salvageable? Thanks for any help
If ADB is accessible, you could pull /sdcard/, and save it on your computer.
While waiting at the animation, plug it in to your computer, open a terminal, cd into whichever directory ADB resides, and run
Code:
adb devices
If it returns your tablet, then run
Code:
adb pull /sdcard/
adb pull /data/
It should copy everything from your internal storage and your app data into the directory containing ADB, but I'm honestly not sure if you could pull /data/ without root access. And even if you did, I'm not sure how you could safely restore the files without breaking something (or especially without root). At the very least, you'll have the contents of your internal storage.
At that point, you should be OK to wipe your data.
If that doesn't work, then assuming you're on the 4.2 bootloader, you could boot into the bootloader by holding Volume Down as you start your tablet, and you will automatically be in fastboot mode. This should allow you to flash a stock blob with fastboot. Instructions to do so have been posted throughout this forum.
If all else fails, it should still be under warranty since it's locked, so you could get a free replacement. I'm thinking the data wipe should be enough, though. Good luck.
Thank you kindly. I'll thank you later as I seem to be out of thanks today. Admittedly though, I'm not too experienced with this stuff and don't really know which directory ADB is in
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
UndisputedGuy said:
Am I right in opening the command window inside sdk--> platform tools?
If so, no devices show up when running the "adb devices" command although I can see my TF300 in device manager
Click to expand...
Click to collapse
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
EndlessDissent said:
That's the right place, unfortunately. I'm assuming you have the ADB drivers installed and everything. Otherwise, install them, and try again.
If you can still get into the bootloader, you should be able to fastboot flash a stock blob. I don't believe that wipes data or your SD card, but I could be wrong. I know that flashing them in a custom recovery wipes both, but I don't think the fastboot method wipes either. Unless tobdaryl or someone else more experienced than I can think of another option, your only next move is using your warranty.
Click to expand...
Click to collapse
Thanks again for your help. I'll need to look into using fastboot to flash a stock blob.
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
UndisputedGuy said:
I was able to find the device using adb and then run the "adb pull /sdcard/" command (thanks a ton for the help in doing that) but it seems like it's only pulling my files from my downloads and Ringtones folder and even then, it doesn't pull all of them within my downloads folder. Any idea on why this is happening?
Click to expand...
Click to collapse
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
EndlessDissent said:
No, I have no idea why it's only pulling a couple directories. It should pull everything from the internal storage since the command includes the whole /sdcard/ directory. I hope someone else knows. If you remember the names of your most important folders, you could try pulling them individually to see if it gives you an error message. If it does, we have a starting point to fix it. If it pulls them fine, then I'll probably be stumped.
Click to expand...
Click to collapse
Thanks! I shall probably try that soon, but I currently want my files from the download folder so will have another stab at that. Thanks again for the assistance :good:
I have been able to pull some files using ADB and thank you greatly for your assistance in doing so. I hadn't really used ABD before but now I'm more familiar with it, so thanks. I have a question regarding using the fasboot method to flash a stock blob. Do I need an unlocked bootloader for flashing a stock blob? The guides I've found have suggested as such. My bootloader is locked.
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
EndlessDissent said:
Honestly, I'm not sure. I would imagine it would do a signature check before flashing, and since you'd be using the official ASUS firmware, it would pass. All I know for sure is that fastboot works on locked tablets. I have no idea to which extent it works.
Click to expand...
Click to collapse
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
Thanks again. You've been a great help
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
I was just about to post that your first step should be to wipe data and see if it boots before we get caught up in fastboot. That is a last resort here. If wiping data may work, fastboot is more work than necessary.
Just to confirm that my tablet did indeed start working again after wiping the data although the stock Asus Backup App fails to restore my app backups from a while ago. It stops at 15%.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Edit: I found an older device of myself with which I was able to take some pictures (has very bad quality because it has a little crack in the camera)
On InternerSpeicherSeite1 you can see that on my pc it shows that storage is used up but on InternerSpeicherSeite2 you can see that it is empty if I open it.
In ES you can see that there is this /legacy instead of /sdcard.
In TWRP1 you can see that the whole /scard directory is nearly empty.
In TWRP2 is the /sdcard direcory that is now in /sdcard/0 but unaccesable from anywhere except TWRP.
R4gi3X said:
Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Click to expand...
Click to collapse
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
its a common issue with L, i even experienced it myself. first, there is a short terminal emulator command you can use. i dont know what it is, but a search should find it for you. itll move all back to where it should be. or secondly, you can do what i did. i didnt know there was a terminal command, so i used root explorer to move everything back manually. took me about 15-20 minutes.
GtrCraft said:
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
Click to expand...
Click to collapse
rootSU said:
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I already know how to adb pull but it just gives me the output seen on the picture...
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
simms22 said:
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
Click to expand...
Click to collapse
I've tried your command but it did nothing.
But I found a way simpler solution now, as I could still access my data in TWRP I was able to flash a 4.4.4 Rom (that I luckily still had on my phone^^) and now I can access everything including the "0" Folder on my pc again. So I'll move everything on my pc now and then copy it to the /sdcard directory
Thanks though for your help, really appreciate the support from the xda-community!!
But I gotta say good night now as it is already 1am but I will update this post one more time tomorrow giving a final result.
You already know /sdcard isn't working properly. Pull /data/media/0
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
If you could do something like that with a locked bootloader / unrooted device then all security for Android would be a sham. I'd be very discouraged if someone could hack into a secure device and pull out information such as pictures, phone numbers, messages etc.
If it is locked, you are done. It's encrypted. If it were unlocked you could easily get it off the phone.
Well, I'm not feeling optimistic at all now. So there is 0, nada, nothing I can do to save this video/file or fix my phone? All because the device decided to randomly get stuck in this bootloop, I am absolutely screwed?
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Unless you can get it to boot up then I do believe you are out of luck. You can't get into recovery menu?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
czbwoi said:
Fastboot > Recovery mode > No command screen > Power button hold + Volume up tap > Android Recovery screen with Reboot system now, Reboot to bootloader, Apply update from ADB, etc?
If that's what you mean, I can get there, I'm there right now.
Click to expand...
Click to collapse
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
bobby janow said:
Sorry afk. Yes, that is exactly where you want to be. Try an adb sideload of the latest OTA or even the last full image. I do believe you can sideload that but if not then the OTA. You might be able to recover that way. If something got corrupt then the sideload might fix it. Or is there an option to clear cache? I think there is, you can try that first.
Click to expand...
Click to collapse
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
czbwoi said:
No option to clear cache, the rest of the options are: Apply update from SD card, Wipe data/factory reset, Mount /system, View recovery logs, Run graphics test, Power off.
I have no idea how to sideload an OTA or image to try to fix this...if you could point it out to me step by step, literally, I'd appreciate it.
Click to expand...
Click to collapse
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
bobby janow said:
Don't have directions atm for sideload online but the way it works is you download the OTA from here: https://developers.google.com/android/ota Scroll down to Pixel latest U build 7.1.1. Download it and place it in your fastboot android sdk folder, I put it in the platform-tools so it's easy. Then click apply update from sd card by highlighting it with the vol keys and then power key to select. It will tell you what to do. I forgot exactly but it's something like "adb sideload <ota.zip> whatever the name is and then let it go. It will take about 10 min and after it's all done, highlight the reboot option. Power key and reboot. Hopefully that should fix it. If not, sorry I'm all out of ideas. Well other that adb sideload the full image although someone will have to verify if that would work.
Click to expand...
Click to collapse
Just sideloaded the latest OTA with the help of a friend, and no luck. Same old stuff. And I think sideloading an image would require the bootloader to be unlocked which would require a factory reset...
Here's another thing that crossed my mind, have any of you ever used EaseUS MobiSaver for Android? It's a tool that allows you to recover deleted files from your phone, similar to Recuva and hard drives. I used it before on my parents' Galaxies, this program is from circa 2014 though so I don't know if it would have much success on a new phone like this...but you never know?
For it to work you need to have your phone on (derp) and have it rooted. Here's the tricky part...if you erase your hard drive and use a tool like Recuva, even though you erased your drive the remnants are still "there" and files are recoverable with a tool like that. Do you think that the same concept would work with phones and EaseUS MobiSaver? Say that I factory reset the phone, set it up as a new device and don't transfer over any backup, I root it, and run said program to scan the deep contents of the phone's hard drive for old data. Do you think this will work in any way possible, like how regular hard drives that got erased work, or is the phone world completely different and incomparable?
EaseUS will not work on a factory reset. You can't recover anything.
bobby janow said:
EaseUS will not work on a factory reset. You can't recover anything.
Click to expand...
Click to collapse
Well then what about programs like these: https://youtu.be/iPCoyRpMrqw?t=58s
http://www.jihosoft.com/recover-data/recover-data-after-factory-reset.html
http://androiddatarecovery.co/recover-data-after-factory-reset-from-android-mobile/
Some people say they have had some success with these...
Let us know. I'll wager you won't get anything back on the Pixel. Good luck.
czbwoi said:
Pressed the home button while using Snapchat, phone froze, had to hard reset it, phone got stuck in constant Google logo bootloop. Getting a replacement shipped out...but I have a video I recorded yesterday morning that never backed up on Photos, any possible way to save it? Someone mentioned an ADB method..? But with my little research I think you need to factory reset the phone for that, which would make this method a waste as I need to get this video off it.
I never rooted this phone, I didn't unlock the bootloader. I did turn on developer settings. That's all I know regarding that.
Other information regarding the fastboot screen: Boot-slot: a, Console: DISABLED, Secure Boot: PRODUCTION, Device is LOCKED.
I've turned it off and on multiple times, same thing. Rebooted it during loops, or at least tried to, same thing. Went into fastboot mode from loops, pressed start, same thing. Went into fastboot mode from phone off, same thing. I don't know what else to do. There is no way to clear a memory cache apparently. And I am sort of n00bish in this world.
Anyways, what could I possibly do to save this video, or to fix my phone out of this bootloop to take the video off the right way before my replacement comes in? Anyway to do either of that via 'ADB', some lowkey program I don't know about that can rip the entire phone's data onto some type of file I can decrypt, a program like Recuva that will find the file(s) for me and yank them out, etc? I know there has to be somebody out there with the skills or capabilities to do something like this... I hope. Please help out and let me know, thanks.
Click to expand...
Click to collapse
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
TCPDump said:
You can often get ADB while it's booting. It just depends how far into the boy process is made it. I would power it up and see if you can ADB pull the file.
Click to expand...
Click to collapse
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
czbwoi said:
My friend was able to give it ADB commands on the fastboot/recovery menu, we sideloaded the latest OTA like that to see if it would fix it. What are you describing though, how would I be able to do that? Do you have any instructions or links on what to do? I don't know the file name for instance. The last video before that one was named VID_20170104_011325.mp4, I don't know how to find out the name of the next video file to even try to attempt what you're saying, unless you know of some way...
Click to expand...
Click to collapse
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
TCPDump said:
Well, IF it had booted enough to mount storage and start the adb daemon then you would use adb shell to locate the file.
Example:
adb shell
cd /sdcard/DCIM/
ls -la
Assuming your filename is in there, it its name is VID_20170104_011325.mp4 then you could exit the shell and do this:
adb pull /sdcard/VID_20170104_011325.mp4
Click to expand...
Click to collapse
Only place I can seem to enter adb commands is when I go to apply update from adb, and when I do so the only thing it responds to is adb devices and sideloading, presumably because that is all it allows me to do in that mode. When I enter adb shell I get error: closed
Recently updated my Pixel 4a and have run into an issue that causes a strange boot loop to a screen that states "Cannot load Android system. Your Data may be corrupt." and prompts to either factory data reset or try booting again. What's strange is that when attempting to boot it again, it is able to load into the device and I have normal access to the phone for about 30-60 seconds before it restarts and prompts a factory reset again.
My main issue is that I need to backup/upload about 900 photos to google photos that were not saved. So far the phone has been rebooting, connecting to wifi and uploading about 0-3 items to google photos per boot until it restarts. Eventually I may be able to secure all my photos this way but I want to know if there is a more efficient method to do this.
Things to know:
Bootloader is locked (can't unlock due to wipe) -> cannot use custom recovery/ flash twrp
USB debugging is enabled and I have sideloaded the latest OTA (sunfish) via ADB sideload in recovery mode but the boot loop has not resolved.
I can successfully use ADB pull /sdcard/DCIM/Camera for only up to 60 seconds until it force restarts. When I attempt to pull again on the next boot, it will pull the same files because it is copying and not moving them.
Does anyone have a solution to this rather than to just factory reset or continuously rebooting? It is frustrating because I still have access to the phone's files but only for about less than a minute. I have scavenged reddit threads, forums, and google for some way to do this but to no avail. (Also is there a way to use the stock recovery's "mount /system" option?)
It's not very elegant, but I could totally imagine a script that listed the files and then copied a few at a time, waiting for the phone to reboot before continuing...
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.
a1291762 said:
I have a python script that uses adb to "sync" a directory on the phone with a directory on the PC, but it's doing a push, not a pull.
Click to expand...
Click to collapse
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/
a1291762 said:
I modified my script a bit to pull instead of pushing, it's ... awfully rough (eg. you have to manually create a Camera directory to store the files it copies) but it seemed to work in principle. It might be enough for you, or it might serve as a base for a better solution. No doubt it'll need a few mods anyway, especially if you're on Windows (in which case ls won't work).
You might also try booting into safe mode, in case that stops the phone from rebooting? https://www.androidauthority.com/how-to-enter-safe-mode-android-801476/
Click to expand...
Click to collapse
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Booting into safe mode did not work unfortunately. Seems the time until restart was the same as well.
Expressionize said:
Thank you for the reply! I am on Windows and I am not too script savvy out of writing a few simple AHK actions so I am not entirely sure how to proceed with what you have there.
Click to expand...
Click to collapse
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.
a1291762 said:
I do have a windows PC for gaming so I'll fire it up and see if I can make it work there.
Click to expand...
Click to collapse
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
I guess it still doesn't solve the issue if someone else runs into my similar situation though, but it seems like a rare enough problem.
Expressionize said:
I was able to brute force the process and finally made my way through the photos. There was one lucky boot that allowed normal access for about 3 minutes and that was enough time for adb pull to completely grab what I needed. I appreciate your time and help.
Click to expand...
Click to collapse
No worries. I'm glad you got your photos.
I had to go out, but I got back and literally just finished updating the script so it runs on Windows and is a bit smarter (eg. waiting for the phone to come back when it goes away). I'll attach it here in the event someone else finds it useful
There's a few variables at the top to configure it. It needs python and adb but shouldn't need anything else.
python3 fetch_files.txt
It's got a .txt extension instead of the more typical .py because XDA won't let me upload a .py file.