Database Info

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

Pantech Element TWRP Recovery and Stock Rooted Roms

This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible

Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads

just in case i need another

Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)

mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium

Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA

mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium

jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!

I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium

dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.

jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4

dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium

jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.

1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!

Delete!

Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-

Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL

I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?

marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app

[HOWTO] Root Stock i9505G (any version)

This was done on a stock rom (works for 4.4)
I unlocked my bootloader first
http://forum.xda-developers.com/showthread.php?t=2363025&page=1
(you need to do the driver part for adb) (Windows 8 may need to change the "Samsung device", and set the driver to be "Android Bootloader Interface")
if you get a "error: device not found" your drivers are not setup, or you didn't accept the cert on the phone.
Thanks broodplank1337
Download root from
http://download.chainfire.eu/supersu
or for more info read here
http://forum.xda-developers.com/showthread.php?t=1538053
and put it in "C:\adb\sdk\platform-tools" (this is my adb.exe folder)
Download the "Samsung Galaxy S4 (i9505) / Download Recovery" from below
http://www.clockworkmod.com/rommanager
save the recovery-clockwork-6.0.4.4-jfltexx.img to the folder "C:\adb\sdk\platform-tools"
Now open up a command prompt (I did this as "run as administrator")
type "cd C:\adb\sdk\platform-tools" (or what ever the directory you extract your files)
enter this command
adb reboot bootloader <enter>
(or hold vol+/- while booting)
Once in bootloader,
In the command prompt type:
fastboot boot recovery-clockwork-6.0.4.4-jfltexx.img (this takes 1min to load after the file is sent)
This will boot into ClockworkMod
goto "install zip"
goto "install zip from sideload"
in the cmd type
adb sideload UPDATE-SuperSU-v1.80.zip
This sends to the phone and write to the phones Rom.
Now reboot, if asked, select no about the stock recovery overwriting the phone
when you boot into the OS download SuperSu from the market
and we have root without ODIN on a I9505G
I disappear alot and i DON'T read everyone's post
I update this when i need re-root
Sorry for the errors in this post
1. I still receive OTA Update with this root (I had to "clear data" on the "Google Service Framework" and then check for updates).
2. As long as you don't flash a different recover it should allow you to apply new updates. The first time i applied a update it failed half way though it. My phone booted but i could install any apps. It only worked after i put the recovery back and re-updated.
3. Once you have root you can flash a recovery using DD in the shell (backup the recovery first) read "[HOWTO] dump your rom"

Good job on writing this for the i9505g users ^^. I'm glad my root zip worked! hehe

:3
Good one! :good:
btw....
Download ClockworkMod 6.0.3.3 NORMAL from below
http://forum.xda-developers.com/show...light=recovery
aka Miustone_CWM_flash-NORMAL.zip
extract the recovery.img to the folder "C:\adb\sdk\platform-tools"
Click to expand...
Click to collapse
your link is not working... this LINK here is working

hey thanks!!
will give it a try tonight!

Will this work on 4.3?
Sent from my GT-I9505G using xda premium

Attempting to do this and for the life of me I can not get adb sideload to work correctly.
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
I want to get this working so that I can root my device and make a backup of my stock images since I just got the 4.3 OTA. When I first got the phone I managed to flash TWRP on it and then put the SU file on the internal memory and flash it from there but I want to get a backup of the stock recovery before going that route in case there is a 4.4 update at a later point.
So could anyone please tell me what I am doing wrong. When my phone is in recovery my computer sees it but adb doesn't.
I am using windows 7 and (I believe) the latest tools from google. I got them right after I got the GES4 so they are at most a month old.

ChaoticUnreality said:
when my device is booted I can see it with adb however when I boot into recovery adb doesn't see the device. I have tried unplugging/plugging the cable on my phone.
Click to expand...
Click to collapse
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I'll have to try that when I get home. thanks.

ChaoticUnreality said:
I'll have to try that when I get home. thanks.
Click to expand...
Click to collapse
Another quick trick that has worked for me in the past is to simply plug the cable into a different USB port on the computer. Does the same thing as the other suggestion without going through the extra steps. Either way should resolve your problem.

Finally got a chance to try this worked perfectly once I changed USB ports and redid the drivers. Thanks

Great write-up
This was my first ever root on my first ever Android device. It went well.
There were a couple things confusing about the post, I just want to make sure I did things correctly.
]Link to Brood's unlocking the bootloader - Was that just to get the USB drivers installed? I didn't use that Clockworkmod or root.zip file
Not selecting yes on final reboot - With so many "no's", I thought it best to not say yes. Does that mean that if there's another OTA update, root will be lost and have to be redone?
Besides that, the biggest issue was getting good USB drivers. Visiting the Samsung site shows zero downloads for the i9505G phone, so I ended up getting the drivers from "phones-usb-drivers.blogspot.com" (can't post links yet), search Google for "free-download-samsung-gt-i9505g-galaxy", it should be a top hit. The actual download was from Samsung, and that got the drivers working for regular operation and the bootloader.
However, I couldn't find drivers that worked for the sideload of the SuperSU. Ended up having to add entries to the Google USB driver (android_winusb.inf) with the VID and PID values. Here's what I added to the x64 section, in case it helps someone else out:
Code:
;Samsung i9505G (GAA attempt to get adb drivers working)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
At that point when it booted into CWM recovery, I installed the drivers and was able to complete.
Now the happy owner of SuperSU running phone. Thanks again warwolfx0

I hope no one minds, but, I automated this.
<see new version later in thread>
Download that, extract it to a folder, install Koush's universal ADB driver in the ADB_USB folder, and then execute the run.bat and follow instructions.
Credits:
warwolfx0 for the OP
Koush for the universal ADB driver found here: https://github.com/koush/UniversalAdbDriver

warwolfx0 said:
Now reboot, if asked, select no about the stock recovery overwriting the phone
and we have root without ODIN on a I9505G
Click to expand...
Click to collapse
Sorry for what might be a stupid question, but I was not 100% sure based on how you word this.
So, if we follow your method, will we leave stock google recovery intact? I.e. we aren't overwriting it with cwm recovery? If so, that would be nice. All my other rooted devices I've installed custom recovery, but it would be nice to leave this one 100% stock except for the rooting.
Thanks.

Correct.
Etched in blood by a katana

Chahk said:
Try re-installing the USB drivers while in recovery mode.
Start --> Control Panel --> Device Manager, then find and right-click the "SAMSUNG" or "MSM..." unrecognized device with the yellow exclamation point, choose "Update Driver Software" option, then "Browse my computer", then "Let me pick from a list of device drivers on my computer", then if presented with a list of categories select "All devices", then click "Have Disk..." button, and point to the same place where you downloaded the drivers. Pick "SAMSUNG Mobile USB Composite Device" and click Next. It may complain about the driver not being digitally signed, select "Install anyway."
Click to expand...
Click to collapse
I had the same problem but was able to get it working by following the above instructions but then selecting “SAMSUNG Android Phone,” followed by “SAMSUNG Android ADB Interface." (I didn't have an option for "SAMSUNG Mobile USB Composite Device.")

I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
Yes.

carrot34 said:
I just rooted my phone following these instructions and it all worked great. Does anyone know if a phone that's been rooted like this will be able to accept and install an OTA update?
Thanks, Alan
Click to expand...
Click to collapse
SamuriHL said:
Yes.
Click to expand...
Click to collapse
I don't have the 9505G yet (couple more days!), but there was a similar issue/discussion on the Nexus 7 board recently, and it was determined that if you were using SuperSU versions prior to 1.55 (which just came out in like the last 24 hours), the root would indeed block OTA's (because of an immutable system flag which was being inadvertently/unnecessarily set by the root process).
Discussion here.
But again, SuperSU 1.55 which just came out fixes the problem, so OTA's will indeed work again. So if you ever get stuck with an OTA, make sure to update SuperSU to latest first.
This is all assuming that the same issue would have presented itself on 9505G, which I would think it might. If not, then ignore this post.

Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip

occupational_hazard said:
Apparently we also have a device specific Odin flashable auto-root file.
The link below goes to ChainFire's website. The zip includes a version of odin.
http://download.chainfire.eu/348/CF-Root/CF-Auto-Root/CF-Auto-Root-jgedlte-jgedlteue-gti9505g.zip
Click to expand...
Click to collapse
We do. I got to test it yesterday and it works great. Restores the proper stock recovery when finished.
Sent from my Xoom using Tapatalk 4

Wiped EVERYTHING by Mistake NEED HELP

Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?

Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4

playya said:
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
Click to expand...
Click to collapse
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.

Nosferatu1923 said:
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Click to expand...
Click to collapse
teh roxxorz said:
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Click to expand...
Click to collapse
I believe above post was meant for you OP
Sent from my A0001 using Tapatalk

Did Advanced wipe without ROM image | Please help

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.