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.
Related
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
Hello -
I have done weeks worth of research in my spare time before finally caving in and asking for help. I believe my situation irritatingly enough is different than typical no os corrupt sd card issues and I have not been able to find a solution here or on the www unless I am forgetting something simple. Here's why:
I am S-Off
I have super cid
I have access to bootloader
I have access to recovery which is TWRP 2.3.1 and I can access terminal command
My card WONT MOUNT (meaning no fixing permissions, no wiping external sdcard or side loading)
If I reboot system, it freezes at the initial boot screen image with the Viper logo and the red developer caution statement below it
Fastboot and ADB do not recognize my phone and I have used every one click, script, and trick on this website and others using different drivers, Android SDK and all the different drivers I can find. No Dice.
I DO HAVE AN HTC EVO 4G LTE that I htc dev unlocked, s-off, supercid etc on this very laptop (Windows 7) this week so I have a pretty good idea what what doesn't work in terms of drivers/scripts with my current laptop configuration.
I have used Ubuntu as an installed desktop and as a live cd. This is as close as I have been to having my phone recognized in adb or fastboot. I was using the SD FIX see here http://forum.xda-developers.com/showthread.php?t=1942519 (What I don't get is why that thread was closed. Makes no sense to me that since a particular version of TWRP becomes available, that it would render that fix obsolete when its obvious how many scenarios can come up in particular with these HTC One Xs and not everyone is going to have a specific version of recovery. Anyway... this brings me to Ubuntu. And this is as close as I have been to success with getting back into my sdcard so I can command prompt/flash my way outta this mess. It was the only version of the SD fix I could find which of course was for Mac, Linux or Ubuntu. In terminal when the script would initialize it comes back as "Fastboot: Permissions Denied" or something to that effect. That was last night.. or errr.. this morning and I'm determined to do this.
Has anyone heard anything about a way to create a virtual sd card using AVD in an old version of the SDK? From what I can see it looks fairly simple. What I have dug up sounds easy enough but not sure why I haven't come across it here or anywhere else or nobody else has mentioned it? However, I am not a dev and perhaps it being a couple years old, counter measures have been put in place by these phone companies... lol we'll see... Thank you so much for your time.
I have attached a snap shot of my bootloader screen. Yes, I know the screen is cracked lol
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
timmaaa said:
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
Click to expand...
Click to collapse
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
How did you wipe your sd card to begin with? If you wiped it in the bootloader with the factory restore option then this will currupt your sd and the only option is to connect to your pc or computer and under my computer right click the drive of your phone and format the sd card that way and this will restore your sd card to working order but you must have all the right drivers installed for your phone. Which installing HTC sync will install all the right drivers
Sent from my HTC One XL using xda app-developers app
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
31ken31 said:
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you mean literally plugging my phone into my pc...going into device manager, seeing if the sdcard is being picked up.. of course I have. I can freely go between recovery TWRP 2.3.1.0.0. and bootloader and I can even boot the system even tho there isn't an OS and get as far as the VIPER logo with the developers text below it in red. I have both windows and Ubuntu and I have tried everything. I have gone into what files and folders I do have on the phone and using terminal in recovery I have found all the proc contents in tact.. all the dev contents in tact and sub folders... all the usb folders and contents I believe are still there too. Including fastboot. HOWEVER, after days of trying every adb usb driver combination imaginable... including editing .inf files, and taking signature verification off win 7.. I still can't get my phone to be picked up when i plug it in. Every once in a while I will get the bell sound when I plug it in to a usb port but when I look in device manager nothing...but when I plug my evo 4g lte in its whamo... ding ding and no issues. As far as this phone goes...I see all the files and folders there but even even ran htc drivers in compatability mode with XP... nothing.
I am learning how to create virtual sdcard images and how I can potentially be able to attach it to a devices sdcard giving one the ability to transfer or delete files which could help some folks get back into their devices...Also, here is a really cool idea although still in its infancy and how you can mount an sdcard as an mtp device using a fuse filesystem based on libusb. https://github.com/hanwen/go-mtpfs So at this point there are options out there but only pretty heavy manipulation of data and extentions and stuff over my head lol..
dtonshel said:
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
Click to expand...
Click to collapse
Hey thanks. Yup. This is exactly what I need to do. It's just that last time I tried to run the sdfix script in terminal using ubuntu i ran into a permissions issue. fastboot-permission denied or something to that nature. Do you know what that means? Thanks tho I will give this a shot.
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
temme how to recover the system folder. i have a system folder on my desktop. help me. my phone isnt turing on
If you can get into fastboot and recover you can restore your phone. You just need a complete ROM, and restore it with mfastboot method.
It doesn't matter if you wiped system, you can do that in TWRP, if you reboot it won't boot into the OS (obviously) but go into fastboot mode.
Download mfastboot, a ROM image, and go through the command lines. There is a FAQ on how to restore.
felmaster said:
Hello there.
My phone is in a state which is widely being reffered to as "bricked". After hours of reading through hundreds of forums and trying out everything possible/impossible, I came to this - I'm posting here, and desperately asking you guys for help.
I have Moto G XT1032. I converted it to GPE, to install a 5.0.1 ROM few months ago. I used it without any problems. However, today I decided to try out the stock 5.0.2 ROM. But I read that I'll have to change my Data partition to F2FS (from EXT4). I did that (using TWRP v2.8.5.0), and then I did this terrible mistake: I decided to do a clean install, so I wiped everything. I wiped System, and Internal storage as well. Yes, I know that I'm stupid.
Now my phone is stuck at my custom recovery (TWRP) or at bootloader. I can switch between these two, but I can't boot to the system, because I don't have any system installed (because I wiped the /system partition - what an Einstein I am -_-). I thought that it would be easy - I just have to somehow push the zip file of the new ROM to my phone, and then install it from TWRP. The thing is - I can't transfer any files to the phone. I'm probably missing some drivers, but the problem is, that the phone doesn't have any operating system installed (besides bootloader, I guess) - so I can't get any drivers working. My PC is running Windows 7 64bit.
I tried installing Motorola Device Manager, I tried using the drivers from android-sdk, but nothing helped. When I type a command "adb devices" to a command line, it says: "List of devices attached >emtpy line<". When I connect the phone to the PC, it doesn't even try to look for drivers anymore. I tried deleting them (drivers), placing there some new, but again - nothing helped. If anyone can provide any help, I'd be very, very, very glad.
Thanks in advance.
//edit: Nevermind, I made my phone alive again. I just had to use mfastboot tools. Moderators can close or delete this thread, please. I'm sorry for creating it, since it was kinda useless.
Click to expand...
Click to collapse
Also TWRP/CWM has support for adb, u just need to install the drivers manually. Then you can push whatever you want.
Of course you can try restoring stock as suggested above.
How did u fixed it? :/
As a last resort there is always OTG (this thing has OTG support right?). Life was so much simpler when you could just put your sd card into a card reader and put your zip on there. A quick google search makes me think its got support, but who knows
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
Hello,
I am making this post, because I am truly desperate.
I got my Pixel 3XL today, and immediatly wanted to root it, because I had root before and didnt want to miss it.
So I locked up the Guide here on xda, followed it step by step. Everything worked fine until it came to installing Magsik. I downloaded the version 17.3 and tapped install in TWRP, combined with the TWRP installer. I rebooted, installed the Magsik Manager APK and looked into it. It said, that Magisk wasnt installed, therefore I tapped install, tried patching the .zip , it failed. So I once more tapped "install" in the manager, downloaded a .zip file, it didnt worked either.
Then i booted into TWRP once more, using fastboot. In TWRP I wanted to install Magisk again. I tapped on the .zip file and it didnt work and it tried booting. It aborted, put me in Fastboot mode and showed me "no valid slot to boot".
I went to Google and looked for the Factory Image, downloaded it, even edited the .bat-file, by removing "-w", started it, failed due to "not enough space". I found a thred targeting this issue (https://forum.xda-developers.com/pixel/help/unable-to-install-factory-image-t3668726), but I couldnt follow it, because when it came to booting some Images, it simply told me, that I was not allowed to flash a image, e.g. "keymaster.img".
Still not giving up I manually booted the boot.img, and it worked. It brought me back to Android.
But here comes the catch. The Touchscreen doesnt work anymore in Android. All other Key, like Volume, Power Button an Fingerprintreader, work perfectly. I then grabbed a USB mouse and plugged it into the type C port, which worked.
Not losing hope, I booted back into Fastboot mode, and started TWRP by using the command ".\fastboot boot <twrp-image>.img". I saw the Google Logo for about 5 to 10 secs, then i came to TWRP. The Touchscreen works absolutely fine there.
Then I started searching Google for a thread similiar to my Problem, but I cant seem to find one. Thats why Im here, begging for help.
Thanks for every help.
You are using an old or wrong version of fastboot. Delete everything you have downloaded.
Get the latest here.
https://developer.android.com/studio/releases/platform-tools#downloads
Then flash the factory image again after removing the -w. Make sure you have the right factory image.
Boot it up and make sure it is ok
Boot to TWRP and install the Magisk zip. Do not install TWRP, that gets complicated and is prone to error.
Thank you for your help, but after the removal of "-w" and the following flashing, it still gives me the error code "not enough space". Does it mean space on the device or on C:/, because that drive is pretty full.
DominikHofmaier said:
Thank you for your help, but after the removal of "-w" and the following flashing, it still gives me the error code "not enough space". Does it mean space on the device or on C:/, because that drive is pretty full.
Click to expand...
Click to collapse
How much free space do you have? Also, how much ram on the PC? Flashing the factory image takes a fair amount of free space and ram. I'm not sure how much, but the unpacked factory image is over 5 gigs.
Sent from my [device_name] using XDA-Developers Legacy app
Atm I have 5.97GB of 220 Free, due to the installation of 2 large Games on my SSD. RAM is 16GB. I can easily free up space on C:/ because of Win10´s "move" option under "apps". So does this error come from the PC?
DominikHofmaier said:
Thank you for your help, but after the removal of "-w" and the following flashing, it still gives me the error code "not enough space". Does it mean space on the device or on C:/, because that drive is pretty full.
Click to expand...
Click to collapse
Open a command prompt in your platform tools folder on the computer and type fastboot --version
If it says 28.0.1something then run the flash all again and post the contents of the command prompt output back here.
DominikHofmaier said:
Atm I have 5.97GB of 220 Free, due to the installation of 2 large Games on my SSD. RAM is 16GB. I can easily free up space on C:/ because of Win10´s "move" option under "apps". So does this error come from the PC?
Click to expand...
Click to collapse
I'd certainly free up more space and try again.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'd certainly free up more space and try again.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The version of Fastboot is 28.0.1-4986621.
The command prompt says the following:
"rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-crosshatch-pq1a.181105.017.a1.zip': Not enough space
Press any key to exit..."
And that happened with 70,5GB free.
Did you extract the zip file that's inside the first zip file you extracted?
Nope, but now I tried it. Same error. So I moved the .zip to a different folder, but left the unzipped folder. Then ran "flashall", this time came the error:
"error: failed to load 'image-crosshatch-pq1a.181105.017.a1.zip': No such file or directory
Press any key to exit..."
DominikHofmaier said:
Nope, but now I tried it. Same error. So I moved the .zip to a different folder, but left the unzipped folder. Then ran "flashall", this time came the error:
"error: failed to load 'image-crosshatch-pq1a.181105.017.a1.zip': No such file or directory
Press any key to exit..."
Click to expand...
Click to collapse
You sure you got the right factory image? That zip should be image- blueline.... Not crosshatch. You're working on a pixel 3, right
Crosshatch is the 3XL.
Sent from my [device_name] using XDA-Developers Legacy app
I do have the right Image, I have the 3XL. I downloaded the November image directly from Google. The cmd prompt even says I have about 23GB of free space on the device, which should be more than enough.
I just cant wrap my head around, why this error exists.
DominikHofmaier said:
I do have the right Image, I have the 3XL. I downloaded the November image directly from Google. The cmd prompt even says I have about 23GB of free space on the device, which should be more than enough.
I just cant wrap my head around, why this error exists.
Click to expand...
Click to collapse
My bad, you did say you had the XL in your post. I'm not sure what's going on either. Have you tried sideloading the Nov ota zip file using adb and the stock recovery? That's what I'd try next. Down load the ota file to your PC then boot into the stock. From your PC, from a power shell opened in the same directory as the ota, run adb sideload ota.zip. See if that will get you back up and running.
Sent from my [device_name] using XDA-Developers Legacy app
I tried it, the Poweshell only says the following:
" PS D:\Downloads> adb sideload crosshatch-ota-pq1a.181105.017.a1-feb712c3.zip
error: closed"
Is there any image that makes android 9 recognice the screen inputs? The wifi doesnt work either....
DominikHofmaier said:
I tried it, the Poweshell only says the following:
" PS D:\Downloads> adb sideload crosshatch-ota-pq1a.181105.017.a1-feb712c3.zip
error: closed"
Is there any image that makes android 9 recognice the screen inputs? The wifi doesnt work either....
Click to expand...
Click to collapse
Have you tried flashing just the boot.img to both boot_a and boot_b? Then rebooting the bootloader and then flashing the factory image. I'm grasping at straws right now, Google keeps making these harder to flashing anything to.
Sent from my [device_name] using XDA-Developers Legacy app
I did just now. And there is still the error "not enough space".
Is it possible to flash the Image through TWRP?
DominikHofmaier said:
I did just now. And there is still the error "not enough space".
Is it possible to flash the Image through TWRP?
Click to expand...
Click to collapse
You can't flash the factory image with twrp. You should be able to sideload the ota in twrp, but twrp still needs some work so I don't know if it will work. When you attempted to flash twrp did you use twrp for the 3 xl or 3. They are different. You might try flashing every partition with it's appropriate image file. There's a bunch of them and you'd need to do it for slot a and b. It'll be a pita but you might find out which partition(s) is giving you problems.
Sent from my [device_name] using XDA-Developers Legacy app
Although most of the images from the folder werent possible to flash, the system.img worked, both on _a and _b, which might have solved my issue!!!! I rebooted, expecting the screen to not work, but it worked!! Thank you SOOO much for your help!
Would you recommend me to try flashing magisk again and to root or should I stick to the phone as it is right now?
DominikHofmaier said:
Although most of the images from the folder werent possible to flash, the system.img worked, both on _a and _b, which might have solved my issue!!!! I rebooted, expecting the screen to not work, but it worked!! Thank you SOOO much for your help!
Would you recommend me to try flashing magisk again and to root or should I stick to the phone as it is right now?
Click to expand...
Click to collapse
You could root by booting into twrp and flashing magisk. I would not try to install twrp. There seems to be many problems doing that.
Sent from my [device_name] using XDA-Developers Legacy app
I booted into TWRP and installed Magisk 17.3 and it worked. Booted into Android and checked the Magisk Manager. Everything is fine.
I really really appreciate your help! Thank you very much!