I realise I'm supposed to be an RC but it's been ages since I've visited XDA or even flashed anything on my phone so I need to be treated as a complete noob if possible!
So I was on PA 3.99 RC2 and tried to flash PA 4.0 BETA 6 in CWM but in a moment of pure stupidity didn't realise I may need to update the radio or bootloader. It resulted in a 'status 7' error during flashing which I understand to mean that recovery is detecting the ROM isn't compatible with the device. I've had a look at the solutions available for fixing status 7 errors but none of them worked. My backup failed on me so I can't revert to that.
My phone has no OS and is not being detected by the PC. I've tried setting up ADB using this guide (I had it on my old PC but that's completely gone) but it doesn't seem to have worked, I get a 'waiting for device' error when I try to type a fastboot command. From what I gather, this is caused by no drivers being isntalled but I don't know how to install the drivers when I can't enable USB debugging on the device and it's not detected by the PC. Typing 'adb devices' when the phone is connected in fastboot mode gives me an error saying
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
Click to expand...
Click to collapse
In CWM I can't mount my SD card so I can't seem to transfer files to or from the device in its current state. However, when I connect my device to the PC I do get a noise telling me it's been connected and it starts charging. I refuse to believe that I could have actually screwed myself over this easily so any suggestions are hugely appreciated even if they seem incredibly obvious or basic!
I don't know what other info may be required, my laptop is running Windows 8.1 if that helps.
I do have a friend with a heavily modded Nexus 4 who PROBABLY has a PC with the drivers and everything installed already, if there's no way I can fix it then he should be able to fix it... right?
Thanks in advance to anyone that decides to help me
UPDATE: Okay so I now have access to a PC without any of the Android SDK and stuff installed yet but my phone appears on the device manager under 'other devices' listed as 'Android' and the icon has a triangle with a yellow exclamation mark in it, is this progress?
You still don't have the drivers set up correctly. I would try the only tool I recommend, Google tool adb fastboot drivers xda.
You'll need to either push a rom on the phone using adb. Or if that doesn't work then fastboot the factory image.
jd1639 said:
You still don't have the drivers set up correctly. I would try the only tool I recommend, Google tool adb fastboot drivers xda.
You'll need to either push a rom on the phone using adb. Or if that doesn't work then fastboot the factory image.
Click to expand...
Click to collapse
Thanks, I sorted it out earlier by flashing TWRP via fastboot and then the ROM and everything seems to be working fine but for some reason my Titanium Backups aren't working, tbh I don't really care that much about my apps anyway haha
Related
Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Pedrau said:
Hey guys ,let's get straight. I'm totally dumb.
After flashing Lollipop factory img which reseted my internal storage (made a backup on PC), today I decided to try AOSP. Downloaded with my phone, flashed it. But the file was corrupted (bad download or something). Results : I only had that rom on my internal storage, my phone won't boot. I thought I could use NRT, although it as always worked fine, now it keeps telling me "adb device not found", "no fastboot devices". So, actually I can't do anything and I can't see what can I do.. already tried reinstalling drivers, but windows isn't even showing my nexus 4 on device manager
Looks like I need help, and sleep too..
Click to expand...
Click to collapse
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
zaclimon said:
Hmm can you get at least to the bootloader menu. If you can, there's still hope. At this time, you're better off using the manual commands rather than the NRT (the NRT use a set of pre-configured scripts and doesn't always end up where you would like to) Have you tried to also plug your device inside another USB port?
Click to expand...
Click to collapse
Yes I can acces to bootloader and TRWP. Tried another USB port, another USB cable, using manual commands it says " <waiting for device>" and nothing happen..
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
venu123 said:
What drivers are you using. I use the Google usb driver available here
http://developer.android.com/sdk/win-usb.html
How to install these drivers here
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
You also need the android platform tools installed on your pc for adb and fast boot commands to work. I use this installer
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have completed these steps on your PC before you connect it to your nexus.
Click to expand...
Click to collapse
Thanks buddy , but my drivers were fine before all this. And now i can't reinstall it that way since my nexus isn't even showing up on device manager, I used another method from NRT. Gonna test on w7..
EDIT: Problem solved using windows 7. There seems to have problem with drivers on windows 8.1
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
venu123 said:
Yes, in windows 8 you need to disable driver signature enforcement. In windows 7 no problem.
Click to expand...
Click to collapse
I didn't have to on Windows 8.1.
Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.
Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Catfish
Source Device Tree: Device Tree For Building TWRP
reserved
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
tfpiaoyang said:
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!BEFGBQKI!uetGnJxWqvG-JRmQNPeBvw
btw any qq grp to communicate?
MicrosoftBug said:
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery ***.img
restore to chinese version cant OTA, will get a big red "!" in recovery...
I have been out of the custom recovery world too long and never tried on a watch before. Trying to flash twrp on my new TW Pro (H) so I can flash janjans rom. Have ADB and drivers (windows 7), have twrp.img ready.
cmd prompt not recognizing adb command. Cant remember how to proceed...how to open fasboot, unlock bootloader.
I know im missing something simple but stuck. Can anyone help jumpstart me?
Update: Got twrp installed after flailing about for awhile. Bottom line, operator error.
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
Did you try running fastboot from bootloader? Also maybe try sideload the rom from twrp, that worked for me.
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks. I've tried three different chargers (though I'm not sure if the other two that I bought are actually capable of transmitting data) and three different computers. I ordered a new charger that says it is able to transmit data, so hopefully when that arrives it will work. Makes no sense to me that I can get into bootloader and twrp and yet not see the watch in device manager.
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
haplohaplo said:
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
Click to expand...
Click to collapse
You deleted the OS? What do you mean by that? Is the watch still working on its own?
Sounds to me like a faulty connector, I would send it back if it is still under warranty.
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
haplohaplo said:
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
Click to expand...
Click to collapse
Try 1. Flash boot.img via fastboot
2. Reboot and connect, check via adb if it's detected
3. Install via sideload ROM
(adb sideload file.zip)
This issue was that I couldn't connect with fastboot at all. That being said, it turns out the problem was with the watch itself. Mobvoi, replaced the watch with a brand new one free of charge so it's all good now.
Any chance you have, or know of, a TWRP for the TicWatch E2/S2 ?
Would be much appreciated.
Hey, is it possible to connect a SD card or usb flash drive to the watch via otg when booted into twrp to create a full backup?
Hello, what would I need to do in order to port this to the TicWatch Pro 2020? The hardware is almost identical, except it has more RAM, the codename is catfish_ext. I have an unlocked bootloader and tried to boot this recovery, but I get FAILED (remote: 'dtb not found').
EDIT: Nevermind, I have found that the recovery for the 4G EU verison also works with mine. Here is the link to a working image: https://drive.google.com/file/d/1XNejRoLecLeadEj1CAW_zrTUP5bkUJZ8/view?usp=sharing
And here is the original source: https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013