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
Related
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!
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
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snoping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT: Just saw help thread, Ill post there.
EDIT 2: I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.
jsauder2 said:
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.
Click to expand...
Click to collapse
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:
JJT211 said:
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:
Click to expand...
Click to collapse
You need the latest Platform Tools. Happened to me last night after I messed up installing TWRP and had to install factory images.
Its still not working. Let me summarize exactly what ive done.
I think im installing the platform tools correctly.
According to guide (windows) I just open command line and type:
adb --version
fastboot --version
That means Platform tools have been installed.
I then take the unzip the new factory image and place it inside the Platforms tools folder. I then navigate to the factory image folder from command line and type:
flash-all
I then get:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
followed by a failed message
So do yall think im bricked? Can anyone confirm what I've done above is correct?
Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening
JJT211 said:
So do yall think im bricked? Can anyone confirm what I've done above is correct?
Click to expand...
Click to collapse
Very doubtful you're bricked. Try downloading the newest platform tools from Google's page if you haven't already. If it still doesn't work, I would try flashing the pieces individually through fastboot instead of using the flash-all command
Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?
I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
JJT211 said:
Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?
Click to expand...
Click to collapse
arodey said:
Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening
Click to expand...
Click to collapse
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??
I don t know why but when I got my Pixel 3 I had to use Windows 10 Power Shell and fastboot commands were recognized. Min fastboot would not show fastboot commands but only ADB commands as operable.
JJT211 said:
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??
Click to expand...
Click to collapse
Archangel said:
I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
Click to expand...
Click to collapse
IT WORKED!!
So not only do you need to extract that 2nd zip file into same directory but apparently you also need to keep that 2nd original zip file in there as later on during the install, the script tells it to extract it. It wont work without that original zip.
Thanks everyone!!
Awesome brother glad you got it working!
JJT211 said:
IT WORKED!!
So not only do you need to extract that 2nd .zip file into same directory but apparently you also need to keep that original .zip file in there as later on during the install, the script tells it to extract. It wont work without that original zip.
Thanks everyone!!
Click to expand...
Click to collapse
Good work man!!!
Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Sent from my Pixel 3 XL using Tapatalk
bigdave79 said:
Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Click to expand...
Click to collapse
Yes.
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
I had to RMA mine it did the exact same thing
JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
Flash Factory image . I had the same thing after messing some magisk modules.
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.