Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help
Related
I'm not sure what I've done, but I now know that fiddling around with the clockwork mod while drunk is a recipe for disaster. I wanted to install the newest update from htc, and when I tried it took me to the clockwork mod screen and said that the sdcard mount failed. I reset it to factory settings, and I think in the process I also wiped the /system folder.
Now, I can only get to the bootloader, and when I select recovery to get to clockwork, it goes to the htc screen with the warning that it is a dev build and stays there. I got the All-in-one kit, but it doesn't recognize the phone. Windows sees it, but is unable to access the sd card.
Help?
euripaetus said:
I'm not sure what I've done, but I now know that fiddling around with the clockwork mod while drunk is a recipe for disaster. I wanted to install the newest update from htc, and when I tried it took me to the clockwork mod screen and said that the sdcard mount failed. I reset it to factory settings, and I think in the process I also wiped the /system folder.
Now, I can only get to the bootloader, and when I select recovery to get to clockwork, it goes to the htc screen with the warning that it is a dev build and stays there. I got the All-in-one kit, but it doesn't recognize the phone. Windows sees it, but is unable to access the sd card.
Help?
Click to expand...
Click to collapse
No your fine, Never use CWM for the One S. The One S It isn't supported, TWRP is better.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a TWRP recovery again.
4) Reboot into recovery (TWRP ). Use mount USB storage
5) Copy rom to phone and flash normally.
Remember you have to do an oem relock bootloader as well.
Sent from my HTC One S using Tapatalk 2
Ok, so I have the all-in-one kit open, but whenever I try to do anything, it says "error: device not found", even though I installed the HTC drivers from the all-in-one's menu. Am I missing something here?
euripaetus said:
Ok, so I have the all-in-one kit open, but whenever I try to do anything, it says "error: device not found", even though I installed the HTC drivers from the all-in-one's menu. Am I missing something here?
Click to expand...
Click to collapse
Do you have adb and fastboot installed on your computer??
Sent from my HTC One S using Tapatalk 2
Yeah, I downloaded the whole SDK bundle, but when I enter "adb devices" it doesn't recognize the phone.
euripaetus said:
Yeah, I downloaded the whole SDK bundle, but when I enter "adb devices" it doesn't recognize the phone.
Click to expand...
Click to collapse
Turn on android debugging on the phone. It's under developer options.
dc211 said:
Turn on android debugging on the phone. It's under developer options.
Click to expand...
Click to collapse
If you can't boot into the os who do you propose its done?
Sent from my HTC VLE_U using xda premium
Install HTC fastboot drivers. then flash recovery and from there flash a ROM
euripaetus said:
Ok, so I have the all-in-one kit open, but whenever I try to do anything, it says "error: device not found", even though I installed the HTC drivers from the all-in-one's menu. Am I missing something here?
Click to expand...
Click to collapse
You must to switch all <in <one <kit in C:\. can not go in D:\ because they will not recognize the phone after that and will not work. When unpak all <in <one <kit to folder C:\ restart the computer when the computer turns start all<in <one <kit from folder C:\ All in one kit, and everything will work
I have same problem :silly:
Thanks guys! Turns out, my desktop didn't like the phone. I installed the all-in-one, adb, fastboot, etc on my laptop and it worked right away. Thanks for your help!
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
shadowboxx said:
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
Click to expand...
Click to collapse
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
brickdummy said:
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
Click to expand...
Click to collapse
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
when i flashboot the recovery.img file it goes to the red triangle.
brickdummy said:
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
Click to expand...
Click to collapse
Hi the program is actually called 4EXT Recovery Touch. I finally was able to open it through fastboot....Now all thats left is to find the right zip file to put my phone back to stock.
shadowboxx said:
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
Click to expand...
Click to collapse
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
shadowboxx said:
(on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Click to expand...
Click to collapse
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
brickdummy said:
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
Click to expand...
Click to collapse
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
As for your post in your other thread, read my signature.
bananagranola said:
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
Click to expand...
Click to collapse
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
brickdummy said:
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
Click to expand...
Click to collapse
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
bananagranola said:
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
Click to expand...
Click to collapse
Ok, one more thing. I have S-ON. does that matter?
----
It did not, lol anyway it worked. Thank you everyone for you help. I really appreciate it.
-----
For those wondering I found the stock rooted rom here http://http://forum.xda-developers.com/showthread.php?t=996368
http://forum.xda-developers.com/showthread.php?p=26617631
Instructions to flash the rom
http://http://forum.xda-developers.com/showthread.php?t=2168500
brickdummy said:
Ok, one more thing. I have S-ON. does that matter?
Click to expand...
Click to collapse
Yes. You need to read the part in my signature about being stuck in the splash screen.
bananagranola said:
Yes. You need to read the part in my signature about being stuck in the splash screen.
Click to expand...
Click to collapse
ok, got it. Thank you again
Dear friends,
I have this problem: I got a brand new TCL S720 and the Google Play did not work, being a known rom issue. So, before doing anything, I've managed to make a backup of it's original rom with MTK Droid tools whichI supose it did it well. Then I've tried to install a CWM recovery to try a custom rom for it. The CWM recovery seemed to install succesfully but I didn't manage to install the new rom. If I remember well, it stucked on boot logo. Then tried to revert at it's original stock recovery, managed to have the phone back as it was in initial state, but doing more tries, It remained stucked on boot logo. The problem is that my computer doesn't recognise it anymore, when I connect it to USB it tries to install MTP usb driver but even before the driver was installed well, now it refuse to install, like the driver is not good or the proper driver doesn't exist. So the only thing I can do is to boot on stock recovery but even I tried to copy the original rom update.zip on external SD and to flash the phone using install update from sd card in recovery mode, It doesn't find the external sd card. So I'm stuck here, the computer doesn't detect the phone to try flashing it with SP flash tool or MTK Droid tool, and I also can't flash it from sd card. Have you any idea how to make it work again?
Thanks in advance.
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
EDIT 2: I have finally solved the problem! I have quoted the important parts below in case anyone else has the same problem.
Basically I had some problems with the drivers the whole time on Windows 8. So what I did was disabled driver signature enforcement in Windows 8 (I think it re-enables after some time). I downloaded the drivers from this post and followed this other post , specifically this part:
jpasher said:
Making Windows recognize the TF300T
You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface
Open the file android_winusb.inf in the naked drivers directory.
Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
Code:
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83&REV_0232
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83
After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.
Click to expand...
Click to collapse
Then I booted up the tablet and connected to my computer. The drivers finally worked! I went into command prompt and typed "adb devices" and the device was there! Then I typed "adb reboot bootloader" and I got into the bootloader.
I had to look for the SKU too and since I couldn't find it cause I couldn't boot into Android it was in really small text in the bootloader at the top. Unfortunately after trying to flash the firmware in the bootloader it would not write over the system every time. So I followed this post instead: http://forum.xda-developers.com/showpost.php?p=49164067&postcount=167
After following the procedure it finally worked! Thanks cmendonc2 and everyone for your help, my friend is happy!
firtvid20 said:
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
Click to expand...
Click to collapse
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
cmendonc2 said:
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
Click to expand...
Click to collapse
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
firtvid20 said:
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
Click to expand...
Click to collapse
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
cmendonc2 said:
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
Click to expand...
Click to collapse
Okay that's good to know. I am still unfortunately not able to get into fastboot. So I'll have to figure out what version the bootloader is before flash the firmware over.
Okay I got access to APX mode (useless from my understanding since my friends has no backups via nvflash), the bootloader while the recovery is loaded (although the driver isn't working for the bootloader), but I CANNOT GET INTO THE BOOTLOADER VIA VOLUME DOWN + POWER. Please help, somebody!
Here's a video explaining my problem.
firtvid20 said:
Here's a video explaining my problem.
Click to expand...
Click to collapse
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
cmendonc2 said:
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
Click to expand...
Click to collapse
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
firtvid20 said:
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
Click to expand...
Click to collapse
Its an option somewhere in TWRP called "ADB sideload".
cmendonc2 said:
Its an option somewhere in TWRP called "ADB sideload".
Click to expand...
Click to collapse
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
firtvid20 said:
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
Click to expand...
Click to collapse
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
cmendonc2 said:
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
Click to expand...
Click to collapse
Sorry, what is test mode? I am on Windows 8.
firtvid20 said:
Sorry, what is test mode? I am on Windows 8.
Click to expand...
Click to collapse
This should help: http://www.wugfresh.com/faq/8/
cmendonc2 said:
This should help: http://www.wugfresh.com/faq/8/
Click to expand...
Click to collapse
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
firtvid20 said:
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
Click to expand...
Click to collapse
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
firtvid20 said:
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
Click to expand...
Click to collapse
I vaguely remember someone posting that he succeeded to use adb/fastboot by installing a VirtualBox with Linux. You might have to search for the details.
Sent from my TF300T using Tapatalk
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
Just an update. I got it working!! I did the following on this post to the universal drivers and then tried installing them on Windows 8. After booting my tablet to TWRP and plugging it in to my computer ADB works! I can reboot into fastboot now. Now I either have the option of flashing a JB compatible recovery or flashing the Asus firmware...
Since I'm not able to boot into Android would anyone be able to tell me what is the SKU on the picture below? So I can flash the correct firmware.
EDIT: Found it in the bootloader in small text. -.- It was the "WW" version.
Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:
You can ADP from TWRP so all is not lost
apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.
Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((
[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
sabeel43 said:
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
Click to expand...
Click to collapse
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
ReboundGuy said:
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
Click to expand...
Click to collapse
Sometimes it gets ON normally and after some time it reboots itself and then it keeps doing it again and again, and sometimes it gets on and goes straight to the recovery mode, and yes i can get my phone into download mode too.
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.2. When in recovery mode, select the option, "Apply update from ADB."3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:List of devices attached[device id] sideload4. Navigate to the folder that contains the update file. It needs to be a .zip file.5. Type in the command, "adb sideload [file name]".
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
ReboundGuy said:
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.2. When in recovery mode, select the option, "Apply update from ADB."3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:List of devices attached[device id] sideload4. Navigate to the folder that contains the update file. It needs to be a .zip file.5. Type in the command, "adb sideload [file name]".
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
Click to expand...
Click to collapse
I tried to update from ADB but it said, unauthorized access!
and I also think it is a hardware issue
Can you start in safe mode?
ReboundGuy said:
Can you start in safe mode?
Click to expand...
Click to collapse
Yes if it boots normally and then i can go safe mode too.
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
ReboundGuy said:
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
Click to expand...
Click to collapse
now Its not turning on , not even on charging
Ikes! Are you able to try and downgrade to your original stock firmware? Seems like the issues began with trying to update.
where can I download original stock firmware from the internet? Can you provide me the link kindly? Last time I used Frija (desktop app) to download firmware.
Pretty much everyone on xda (including me) uses this website for firmware: https://www.sammobile.com
You have to create a free account but it's worth it for all the firmware they have available.
I believe you already know this, but I'm just going to cover the bases anyway, make sure to download firmware for your specific model G930T.