Database Info

Sdcard partition messed up, phone no longer boots

[This is a repost of my post over at Android Central]
Hey Everybody,
My Nexus S 4G has been unusable for a few days now and I need some help diagnosing the problem and determining if it can even be fixed.
What happened: I was running jstntp's Android 4.1.1 rom (ver 2.0). I liked the performance of version 1.2 a little better so I went back to it. Being 1.2 didn't have wifi tethering enabled I figured I'd try a 3rd party wifi tethering app just to see if it'd work (I can't remember the name of it). After install my phone rebooted itself (looking like a crash) and went into an immediate boot loop. I quickly booted to recovery and tried simply reinstalling 1.2. That failed. So I tried restoring a nandroid backup. That failed too.
What i've tried to fix it: I have tried flashing (via fastboot) stock gingerbread, stock ics, google's official stock gingerbread, google's official stock ics, sprint's official ics via odin, and a half a dozen different 3rd party roms such as some bugless beast roms that I have used in the past. The stock images all appear to flash fine with no complaints from installers. Even odin installed and displayed it's "passed" message.
Where it gets weird: In all of my recovery efforts I noticed a strange occurance happening. Everytime I would load something to the "sdcard" (whether it be by mounting in cwm or pushing through adb) it would appear in cwm while it was booted there (yet fail to install anything) and would disapear as soon as I booted out of cwm. Also, if I deleted any files while mounted (or deleted from adb shell for that matter) they would reappear after rebooting. At this point I figured the root of all of my problems is that my "sdcard" partition has a problem and needs to be fixed.
How i've tried to fix the "sdcard" partition:
- Chose to format /sdcard in cwm recovery. It said it was successful but didn't do anything at all
- Chose to format /sdcard in twrp recovery. It said "E:tw_format_rmfr: unable to locate volume for device "/dev/block/mmcblk0p3" "
- Did fastboot erase media
- Locked the device and unlocked it again agreeing to wipe all data (nothing got deleted)
- Pushed busybox over adb and ran mkfs.vfat on /dev/block/mmcblk0p3. It didn't complain and said it was successful. (still nothing deleted)
At this point I'm really at a loss. I will do anything to get this to boot. I don't care what version of Android I wind up on, I don't care that I have to lose all of the stuff on my "sdcard" (it's all backed up anyway). Just having a working phone would be great.
Thanks in advance,
- Phil -

Mount USB on Windows and just format it. Or before that you could try running chkdsk {yourdrive} /F
The chkdsk is on windows.

[Q] Check this out: Att One X - NO OS, SD card wiped and won't mount BUT..

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.

cannot use adb to solve continuous reboot - device offline

I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.

hardya said:
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
Click to expand...
Click to collapse
Did you try factory reset?

Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.

hardya said:
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
Click to expand...
Click to collapse
Okay,since you want to flash Aosp N,leave that factory reset thing.
https://forum.xda-developers.com/showthread.php?t=2788632
This thread should be enough atm.Everything has been explained,and it's just simple copy paste,so,even if you're unfamiliar with adb,you should be able to do just fine.
Just follow,install adb/fastboot drivers,unlock bootloader,and flash twrp.
Now,unlocking bootloader will format internal storage,which means everything....but,a simple adb command should be able to back everything up into your pc.
Ensure your adb/fastboot drivers are already installed,and using adb devices in cmd shows your connected device id,before below process!
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
Where "NAME" is the name of your Windows user name.
On the device, a new screen should appear. If you want to encrypt the backup, enter a password -- otherwise, tap Back up my data. The backup will begin, and you'll find the backup file in the folder declared in the backup command.
Depending on how much data your device holds, this process can take quite some time.
The restoration process is simple. Connect the device to be restored and (from the same location you issued the backup command) enter the command:
adb restore C:\Users\NAME\backup.ab
Where NAME is the name of the same Windows user from the backup process.
Again, depending on how much data is on the backup, the restore process can take some time.
Click to expand...
Click to collapse
When you're done doing all of this,just follow any rom's thread instructions to flash that rom.
Btw,you're on Cos13.1.x,yes?

So sorry for not replying to say thank you sooner, I have been busy with family issues.
Thank you so much for your response, I really appreciate it. I shall take a look at this soon and try to get regular android N on the phone soon. Thank you.

I'm just starting to read and work through this. Just to clarify, re my original post, is the fact that my phone is continually rebooting and that adb shows the device as offline a problem? Will I still be able to use adb to backup the phone contents? Do I need any special understanding to do that?

I finally came back to this and flashed a new rom carbon rom. I only noticed afterwards that there is very little support for this rom and I've had some issues.
If you think the issues are in some way generic and you have come accross them before you may have some ideas:
- there is no built in task manager and third party ones do not seem to cover the apps I am interested in. Any ideas why there is no built in task manager anymore like there used to be and how one might be able to turn it back on?
- the camera does not work and the open camera I installed instead has some image faults (or misunderstood feature). Big line down the middle of the image.
Any ideas.

SOLVED: Installed Magisk and now Bootlooping

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.

Sideload twrp backup?

So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers

Re-flash Stock ROM.

Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.

Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer

what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?

No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.

you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com