Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.
murph187 said:
Hello guys, so before I go any further I'll say that I have spent two days attempting to figure out ways to get my self out of this trouble and I've come close, but no cigar. The limiting factor here is the inability to connect to a PC.
Ill begin with the intent: format all partitions to F2FS. I finished backing up all important data to cloud storage and what little I could to my PC (photos only). While I was able to connect my phone to the pc, all I could get it to recognize was as a camera device, not an MTP device, so I was limited as to what files I could back up (hence the cloud storage used for the rest). I tried many different drivers (LG mobile device drivers, Google USB driver, Installing google SDK tools, etc).
I admit that I messed up not realizing I would've needed to restore the f2fs roms previously downloaded in order to re-flash in TWRP. I went ahead and formatted the phone to F2FS and all I have is TWRP 2.7.1.1. I have tried mounting through TWRP in windows XP sp3 and also in windows 8, I can not get the phone to mount the internal SD card in order to drop an f2fs compatible rom to flash.
So I basically have a useless phone at the moment (TWRP and no OS). I was hoping there would be an option to flash a rom image using ODIN, but I can't seem to find any helpful instructions online. Any help at this moment would be greatly appreciated. I'll answer any questions I can.
Click to expand...
Click to collapse
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery. If you don't know how to do that, I don't know why you're messing with your device at all. If that's the case, first link of my signature for threads on how.
Lethargy said:
ODIN? This isn't a crappy Samsung device. Flash factory images with fastboot in bootloader, or adb push a flashable ROM zip to your internal storage and flash it in recovery.
Click to expand...
Click to collapse
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?
murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7).
Click to expand...
Click to collapse
Theres a thread for diagnosing driver issues. You might have to disable signature enforcement on Win8.
Flashing factory images will reformat it to ext4, I'm pretty sure.
Also, there is hardly any UI difference in 8 compared to 7. Even the "start menu" is theoretically the same, just with a different layout. Pinned shortcuts and a list of shortcuts.. You can install a 3rd party start menu if you're someone that can't adapt to something new. Any complaints that "Windows 8 is terrible" are just stupid.
murph187 said:
I've attempted to ADB push but I can't get my phone to be recognized. I've checked using "adb devices" also "fastboot devices" and had no luck. I'm currently on a windows 8 laptop (hardly productive, I'm used to windows 7). I would need to reformat the partitions to ext4 in order to fastboot flash stock images no?
Click to expand...
Click to collapse
Make your suffer short. Try lg flashtool. Link in my signature.
bitdomo said:
Make your suffer short. Try lg flashtool. Link in my signature.
Click to expand...
Click to collapse
Your method worked thank you very much! Mod can close thread.
Related
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
SD card not found
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
emueyes said:
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
Click to expand...
Click to collapse
What USB cable are you using? Try to use your Xoom oem cable. Also, make sure that you try different USB ports, especially the ones tied more directly to the pc motherboard. It's finicky like that. Recheck your drivers. I'm not familiar with that PDAnet source. Motodev is the place to get them from. You may also need the java sdk from oracle.
There are some useful guides on setting up adb/fastboot/rooting in General...you may have to go back a few pages but it will be worth it to make your task easier.
Good luck!
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
emueyes said:
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
Click to expand...
Click to collapse
Which recovery mode are you talking about? Have you unlocked and installed a custom recovery, as in a ClockworkMod-based recovery? If so, which one? They have some different behaviors. If it is stock recovery, I don't think it sees the external sdcard at all.
Also make sure usb debugging option is enabled. And flash another recovery image.
You don't really need to root. Just unlock the bootloader. Push the recovery image. Reboot to recovery. And flash a pre rooted rom from team EOS.
Sent from my MZ601 using Tapatalk 2
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.
m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php
I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media
m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...
Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.
I still haven't had any luck. Does anyone have any ideas?
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2646279
berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so
Whoops, forgot screen shot
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...
berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
I was trying to install a couple of different custom roms on my phone. I have TWRP as the recovery tool. I tried a rom called ATT Buckeye and it seems to have bricked the phone. I don't have any other roms copied to the internal storage to try to flash them. I can reset to factory defaults both through holding the volume and power down and through TWRP, but I'm not able to start into a system. The only thing I can do is boot into TWRP 2.7.0.0
I saw that I can copy files using ADB, but it says "device not found" when I am connected and run adb shell. I have the drivers from LG's website installed, but there is a yellow exclamation mark on it in device manager. I found a thread where it says that I should be able to get the drivers from the Android developer SDK. I also found the individual download for Google USB drivers. In both cases, Windows isn't able to find any drivers in the USB drivers folder. I'm not sure what else I can do to revive my phone. At this point, I'd like to just get it working again any way possible.
I used this to fix my phone http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Then I was able to load Cloudy G2 http://forum.xda-developers.com/showthread.php?t=2783192
Good to go
Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.
dheerajc17 said:
Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.
Click to expand...
Click to collapse
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.
you can also try using adb sideloas
I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.
daedric said:
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.
Click to expand...
Click to collapse
Sorry, but am new to this. Can you please provide instructions to get my phone back to normal.
Thanks in advance
aciupapa said:
you can also try using adb sideloas
Click to expand...
Click to collapse
Sorry, but as am new to this, can you please help with instructions on how can I get my phone back to normal?
Thanks,
focus-pocus said:
I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.
Click to expand...
Click to collapse
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?
dheerajc17 said:
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?
Click to expand...
Click to collapse
You need to add path to adb.exe to Windows PATH variable, then reboot and cmd should recognize adb commands, or you can just navigate to folder with adb.exe in cmd. Then check if adb can see your device, if it does, then just do adb sideload of ROM, and flash your ROM in TWRP.
If it's all too complicated, just return to stock using instructions from Google factory image website.
Put a rom on a flash drive, and connect it to your phone. In TWRP, go into "Mount" options, mount the flash drive (cant remember the exact wording), and then...can't remember quite vividly how, but it's easy from there to navigate inside your flash drive and install the rom.
REMEMBER: the flash drive should be formatted in FAT32 for TWRP to recognize it.