So I moved onto a new phone once I screwed up my phone a couple months ago, but if I can save it in a way that would be cool. Basically right now it has no os and no backup, but I can still go to twrp. I had issues with the usb being recognized to my computer even when the phone worked, I don't believe I can get my computer to see my phone, even though it charges though it. Doesn't help that the usb port is loose. So I just wanna see if there is any way I can get my computer to see my phone to get it running again.
hav u tried changing the usb port on the phone and or use different cable or pc!!!
percy5911 said:
hav u tried changing the usb port on the phone and or use different cable or pc!!!
Click to expand...
Click to collapse
Like try to take the phone apart and replace it? No, I did try various cord on two pcs, no dice.
You will have to ADB Fastboot and then flash a ROM
what about a USB otg drive? load up OS files and flash from TWRP
I suppose that is the last thing to try, I'll order one today.
If you can get your 6P to recognize a USB-OTG device after mounting OTG in TWRP then you can save a ROM and GAPPS to your OTG device and flash it from TWRP.
Sent from my Nexus 6 using XDA-Developers mobile app
Update
So I got my otg-usb was able to see the storage device in recovery. However I was having trouble flashing a rom, well more specifically I couldn't flash a vendor img. But eventually I installed the latest twrp, and was able to install a vendor img and rom, and I was able to get it running I'm so happy!! Thank you for the otg suggestion,I thought this phone was a paper weight.
pjanobe said:
Update
So I got my otg-usb was able to see the storage device in recovery. However I was having trouble flashing a rom, well more specifically I couldn't flash a vendor img. But eventually I installed the latest twrp, and was able to install a vendor img and rom, and I was able to get it running I'm so happy!! Thank you for the otg suggestion,I thought this phone was a paper weight.
Click to expand...
Click to collapse
That's awesome!!! glad to hear that it worked.
Were you able to boot into fastboot?
Related
Hey guys, I just made the move from Blackberry to the Fascinate from Verizon, it is stock with the DI01. I am familiar with rooting using ADB etc and I have been doing it for a few friends. My issue is when I plug the Fascinate via usb I get a CD-Drive icon with a few software like Samsung_Mobile_USB_Driver and TooLauncher_Bootstrap and when I mount SD I get the same CD-Drive icon with error message windows can't access this disc. Also ADB shell also reports Device not found with USB Debugging and Allow mock locations enable.
The SD settings is set to Mass storage and I have the Samsung driver installed.
Can anybody point me how to get the SD mounted as a storage disk so I can have access to it?
Thanks allot guys
Can you post what OS you are using for clarification?
The issue I had with this was I didn't realize I had to authorize the mount from the pulldown up top when I plugged it in. You probably did that, but just in case.
Swyped w/ XDA App. When in doubt, mumble.
Im on Win 7 x64 with Samsung USB x64 driver install.
The funny thing I had another Fascinate in just last week and I was able to connect and mount the SD card as a disk drive just fine.
Any tought?
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Here are some posts by people with the same issue:
rmtobler said:
Well I finally got the computer to recognize the sdcard, but I had to flash the d101 odin files a bunch of times and start over. But after awhile on DJ05 the same problem happens again. I tried to check to make sure the sd was recognized after each step I took, but it seemed it seemed to have stop working overnight and now is just not recognized at all or as my cd-rom (drivers show 'samsung cd-rom usb device', though the sdcard is still working on the phone
Click to expand...
Click to collapse
rmtobler said:
I got mine to work again. Although I'm not exactly sure why it worked. But I un-installed and re-installed the samsung usb drivers and then later when I restarted my phone with the usb plugged in (and usb debug on) the computer started loading up the drivers correctly while the phone booted and it has worked since then.
Click to expand...
Click to collapse
nike984 said:
This worked for me too.
Basically you have to restarted the phone with the usb plugged in.
After than that the problems was gone.
Thanks rmtobler!
Click to expand...
Click to collapse
cseeley said:
I am not totaly sure that the connection issue is related to DJ05, or full DIO1 package. After running into the problems with the debug connection, I was not able to root because of the connection issue.
Luckily, I saved off a rom manager backup od my DJ05 after rooting it the first go around, as it seems as though something of DJ05 stays around, and breaks all my DI01 roms.
What I ended up doing, to get back up and running is as follows;
I formatted the SD card just in case that had a problem. Put my rom manager backups back on their, and then I flashed back the DI01 package to get me back to the factory radio. Then I flashed clockwork, I then copied update.zip from the clockwork thread to the root of the sd card, and booted into recovery. Next I restored my DJ05 backup that already had root, and then back into recovery and flashed the DJ05 radio, and Kernel.
I am now back up and running. Not sure on the debug connection, I will have to some things.
Thanks,
Chris
Click to expand...
Click to collapse
rmtobler said:
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Click to expand...
Click to collapse
Don't know if anybody ever told you this!
You're the man, it works, I have access the SD card via USB.
Thanks ALLOT bro.
none of the above methods work for me. All trouble began when i installed DJ05. I used the **87284 through dialer to confirm its on USB mode. Now i don't have debugging and sdcard mount failure.
Under windows 7 x64 device manager other devices got loads of question marks on Data Interface.
I was looking at other post for EVO4G
http://forum.xda-developers.com/showthread.php?t=695243
The fastboot option is only available on HTC models i guess.
I was wondering about a fix for fascinate through Odin.
I would just suggest trying the different odin files for dj01 modem, system, recovery until you get a combination that gets the usb working again. The first time I used odin it worked great, then the second time it didn't work and I just kept doing it until it did. Then once I went to dj05 and flashed anything using clockwork the USB would go back to not being recognized but a restart w/ the phone plugged in fixes it.
Downloaded latest files & instructions from irc samsung-fascinate channel. it used to mount as CDROM earlier. That is gone now. Still shows question marks under Data Interface win7 x64. Tried various combinations. Went back to stock now.
However the baseband modem is DI01 and build number is DH12. Similar issue reported by http://forum.xda-developers.com/showthread.php?t=854704.
In search of DH12 baseband modem now. Hoping this will fix the issue i'm having. I've got a nandroid backup but that does not restore the baseband modem to DH12.
Ok I have a big problem here and need help fast... I rooted my Kindle quite awhile ago and installed a IcS rom.. It worked perfectly...i had back ups for the Stock and ICs rom on TRWP so I got a new rom Ics with kernel 3.0 or something... flashed it worked perfectly...... but i went to flash it again in Twrp i went to WIPE and did factory reset but SOME how i clicked Sd card it removed everything I was very very scared.......I go back to restore nothing is in there i go to install everything is gone Idk what to do how am i gona get a rom in here to flash please help me... i dont wanna lose my kindle fire
I bricked a kindle fire pretty bad but was still able to get a working rom on there after using firekit and the usb boot mode trick. Was able to install firefirefire and twrp using ubuntu on a usb stick and some motherboard shorting. I'm still waiting for my factory cable to arrive in the mail but found this trick while waiting.
Firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
Usb boot mode trick:
http://forum.xda-developers.com/showthread.php?t=1405052
Was pretty scary because I accidentally touched a paperclip to a power source and caused a spark on the kindles motherboard but apparently nothing was damaged. Just make sure you stay away from the ribbon cable below the shorting point.
This is a last resort for when you can't even adb shell into your device.
tombombman said:
I bricked a kindle fire pretty bad but was still able to get a working rom on there after using firekit and the usb boot mode trick. Was able to install firefirefire and twrp using ubuntu on a usb stick and some motherboard shorting. I'm still waiting for my factory cable to arrive in the mail but found this trick while waiting.
Firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
Usb boot mode trick:
http://forum.xda-developers.com/showthread.php?t=1405052
Was pretty scary because I accidentally touched a paperclip to a power source and caused a spark on the kindles motherboard but apparently nothing was damaged. Just make sure you stay away from the ribbon cable below the shorting point.
This is a last resort for when you can't even adb shell into your device.
Click to expand...
Click to collapse
Doesn't sound very smart to me, I wouldn't fudge with my motherboard
Sent from my Amazon Kindle Fire using XDA
7r3d said:
Ok I have a big problem here and need help fast... I rooted my Kindle quite awhile ago and installed a IcS rom.. It worked perfectly...i had back ups for the Stock and ICs rom on TRWP so I got a new rom Ics with kernel 3.0 or something... flashed it worked perfectly...... but i went to flash it again in Twrp i went to WIPE and did factory reset but SOME how i clicked Sd card it removed everything I was very very scared.......I go back to restore nothing is in there i go to install everything is gone Idk what to do how am i gona get a rom in here to flash please help me... i dont wanna lose my kindle fire
Click to expand...
Click to collapse
I'm sure you've figured out by now that you've deleted everything on your /sdcard partition. What you need to do now is "format" that area again. You can do this in one of two ways...
1) Use TWRP's Mount -> Mount USB Storage feature to get mount onto your computer's OS. It will ask you to format... you should be OK after that.
2) If that doesn't work out for some reason, you'll have to use parted to "make filesystem" which is just "format" in linux-speak...
http://forum.xda-developers.com/showthread.php?t=1424784
You can follow the directions in there to get it done, but it might ask a couple of times what partition and what filesystem type you want. It's always going to be 12 and fat32 for those questions. Don't mess with anything but partition 12. Type "quit" to get out of the "parted" program.
If you don't know how to use adb, read the posts in this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
I suggest you read it from the beginning, but the information you need is mostly located in the 3rd post.
Hey, I said it was a last resort. I probably should have waited for the factory cable but i'm impatient. It all worked out though.
It should have just reformatted the sdcard partition. Try to mount usb from twrp and copy a Rom to flash.
Sent from my Amazon Kindle Fire using xda premium
brizey said:
It should have just reformatted the sdcard partition. Try to mount usb from twrp and copy a Rom to flash.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
The shortest recommendation (the one above), is the right one.
I don't know wth tombombman was talking about, that relates nothing to a formatted SD card
TRY to find the smallest possible OS install in megs. It'll increase the likelihood that a SD card data recovery program might be able to find your old backups, should it NOT be overwritten by any new data that's created on the SD card.
Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution
today ive got my new tmobile g2. first think i did is to root and install twrp . ive downloaded custom rom and i made i mistake by wiping everything in twrp. And i dint know that i cant mount internal sdcard on my pc in twrp. now im stuck on twrp and bootloop. and cant install LGMLauncher i comes to the 75% and get stock on win 7 64 bit. please help i have no idea what to do now. any way i can mount internal sd card twrp or other solution ? thanks in advance
Sorry mate, I cant help you, Im just wondering why people chose TWRP over CWM recovery? TWRP seems.. Very risky. Wiping everything, breaking on OTAs, etc.
Wouldn't it be safer to go with CWM, assuming its out for your version though?
Didn't even bother with the stock rom huh??
It's such a nice rom too.
LG G2
I think your best bet will be getting ADB installed and get it working on your PC. You should be able to send the file via ADB (command-line) and have it flash while TWRP is running.
Help out google search: "adb push in twrp"
I also disagree with SweStag's opinion about TWRP. It's not worse or risky, just more geared toward a power user. I switch to it when they first got their Touch Recovery interface and I haven't looked back to CWM yet.
chiljig said:
today ive got my new tmobile g2. first think i did is to root and install twrp . ive downloaded custom rom and i made i mistake by wiping everything in twrp. And i dint know that i cant mount internal sdcard on my pc in twrp. now im stuck on twrp and bootloop. and cant install LGMLauncher i comes to the 75% and get stock on win 7 64 bit. please help i have no idea what to do now. any way i can mount internal sd card twrp or other solution ? thanks in advance
Click to expand...
Click to collapse
here is the guide to install cwm. this is also what i use. twrp has never worked right for me in the past, you may be able to install the cwm recovery image through your pc
http://forum.xda-developers.com/showthread.php?t=2468858
if not likes you may have to kdz back to stock.
http://forum.xda-developers.com/showthread.php?t=2432476
SweStag said:
Sorry mate, I cant help you, Im just wondering why people chose TWRP over CWM recovery? TWRP seems.. Very risky. Wiping everything, breaking on OTAs, etc.
Wouldn't it be safer to go with CWM, assuming its out for your version though?
Click to expand...
Click to collapse
FWIW, I've never had any trouble with TWRP.
rfarrah said:
FWIW, I've never had any trouble with TWRP.
Click to expand...
Click to collapse
OK how da heck can I push anything in to this devise. adb doesnt see it any more. even windows is saying faulty driver even it used to work before. phone is completely cut off from outside world. please any sugestiobs ?
chiljig said:
OK how da heck can I push anything in to this devise. adb doesnt see it any more. even windows is saying faulty driver even it used to work before. phone is completely cut off from outside world. please any sugestiobs ?
Click to expand...
Click to collapse
This worked for another person in a similar situation (http://forum.xda-developers.com/showthread.php?t=2492911):
Buy a usb otg cable and use a thumbdrive or better, get a microusb thumbdrive like this one:
http://t2.gstatic.com/images?q=tbn:A...Una2lIDP2w&t=1
Place the image of whatever ROM and mount it?
Or, by connecting the cable mentioned above it would allow you to get into download mode and then heading in this direction: http://forum.xda-developers.com/show....php?t=2471370
Good luck!
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.