Hey, im in Jamaica and ive got a challenge for Captivate users. No one has been able to figure this dilema out. Hopefully someone can solve this.
My captivates usb port has stopped doing anything. The details are:
1. The phone works fine and used to be rooted but the root is corrupt i think. Super user installed but the phone behaves unrooted and SU gives errors.
2. I cant flash ROMs since there is no usb.
3. Cannot sideload as the phone cant receive the AT&T OTA update since im in Jamaica.
4. I changed the USB port but same result (no charge, no connection to pc)
Im thinking the usb is bricked since the person i got it from says it charged the day before she reset the phone to give to me.
5. Cant update.zip via 3 recovery (i get e: siganture verification failed)
Can anyone figure this out!? Im thinking its impossible now. If only i could use sideload wonder machine wirelessly, then i could use Z4ROOT or Visionary to flash.
Maybe stupid question. But do u have the Samsung USB drivers installed? If yes then probably need a new USB cord. Try a different one.
saintnova said:
Hey, im in Jamaica and ive got a challenge for Captivate users. No one has been able to figure this dilema out. Hopefully someone can solve this.
My captivates usb port has stopped doing anything. The details are:
1. The phone works fine and used to be rooted but the root is corrupt i think. Super user installed but the phone behaves unrooted and SU gives errors.
2. I cant flash ROMs since there is no usb.
3. Cannot sideload as the phone cant receive the AT&T OTA update since im in Jamaica.
4. I changed the USB port but same result (no charge, no connection to pc)
Im thinking the usb is bricked since the person i got it from says it charged the day before she reset the phone to give to me.
5. Cant update.zip via 3 recovery (i get e: siganture verification failed)
Can anyone figure this out!? Im thinking its impossible now. If only i could use sideload wonder machine wirelessly, then i could use Z4ROOT or Visionary to flash.
Click to expand...
Click to collapse
You went through this thread yet? http://forum.xda-developers.com/showthread.php?t=1953930
1. Ive tried several usb cables but no response.
2. If the phone wont even charge via usb then im not sure installing the drivers will help.
3. Whats the jig supposed to do? Get me into download? If so, when i hold the volume buttons and power button, it takes me to a screen that gives me the options to clear cache, user data, and reinstall packages. but when i try various update.zip files i get the signed verification failed message. I think this is recovery mode but ill search for how to get into download mode. Does download mode work without usb?
Tried entering download mode but i guess since the usb doesnt work, thats why it doesnt function.
saintnova said:
1. Ive tried several usb cables but no response.
2. If the phone wont even charge via usb then im not sure installing the drivers will help.
3. Whats the jig supposed to do? Get me into download? If so, when i hold the volume buttons and power button, it takes me to a screen that gives me the options to clear cache, user data, and reinstall packages. but when i try various update.zip files i get the signed verification failed message. I think this is recovery mode but ill search for how to get into download mode. Does download mode work without usb?
Tried entering download mode but i guess since the usb doesnt work, thats why it doesnt function.
Click to expand...
Click to collapse
If the phone doesn't charge through the usb, you need a new usb port on your phone. If you know how to solder, you can probably get one for cheap and look at videos on how to do it. Otherwise, you can go through mobiletechvideos.com to get it replaced.
As for download mode, it's vol down + power.
BWolf56 said:
If the phone doesn't charge through the usb, you need a new usb port on your phone. If you know how to solder, you can probably get one for cheap and look at videos on how to do it. Otherwise, you can go through mobiletechvideos.com to get it replaced.
As for download mode, it's vol down + power.
Click to expand...
Click to collapse
The usb port was changed but the result was the same. All this happened after the person wiped the phone before i got it. Before that the usb port worked fine. Trying to put it into download mode now but a question again is, will it work if the usb port doesnt work?
Tried volume down + power but phone just boots as normal.
Im on froyo 2.2
saintnova said:
The usb port was changed but the result was the same. All this happened after the person wiped the phone before i got it. Before that the usb port worked fine. Trying to put it into download mode now but a question again is, will it work if the usb port doesnt work?
Tried volume down + power but phone just boots as normal.
Im on froyo 2.2
Click to expand...
Click to collapse
The other way to fix this would be sideloading but ATT doesnt allow the OTA where im at. Anyway to upload Z4root quickly to googleplay then download it? LOL. My phone only allows apps from google play.
saintnova said:
The other way to fix this would be sideloading but ATT doesnt allow the OTA where im at. Anyway to upload Z4root quickly to googleplay then download it? LOL. My phone only allows apps from google play.
Click to expand...
Click to collapse
There's a security feature, you can uncheck it in your settings.
And holding vol down+power while phone is off will boot it in download mode (don't have the usb plugged in). Also, formatting and resetting a phone doesn't break usb. My guess, the job wasn't done correctly.
Have you tried it on other pc? Perhaps your pc usb port is defective.
BWolf56 said:
There's a security feature, you can uncheck it in your settings.
And holding vol down+power while phone is off will boot it in download mode (don't have the usb plugged in). Also, formatting and resetting a phone doesn't break usb. My guess, the job wasn't done correctly.
Have you tried it on other pc? Perhaps your pc usb port is defective.
Click to expand...
Click to collapse
1. There isnt any such setting on the ATT version of my captivate. I guess that option came after the sideload OTA update.
2. I hold the volume down button and the power when the phone is off but it just boots up as normal. No download mode. Is there a site that keeps update.zips or OTA update that can be pushed?
saintnova said:
1. There isnt any such setting on the ATT version of my captivate. I guess that option came after the sideload OTA update.
2. I hold the volume down button and the power when the phone is off but it just boots up as normal. No download mode. Is there a site that keeps update.zips or OTA update that can be pushed?
Click to expand...
Click to collapse
1. I though I remembered being able to sideload back then (it has been a while) but could be wrong.
2. Not with the signature verification. You'd need a custom recovery (cwm).
Getting in download mode is something that always works (unless you mess up with the bootloaders = bricked phone), just like getting in recovery. It's something that comes with the phone.
Basically, not much can be done on the Captivate without a working usb.
BWolf56 said:
1. I though I remembered being able to sideload back then (it has been a while) but could be wrong.
2. Not with the signature verification. You'd need a custom recovery (cwm).
Getting in download mode is something that always works (unless you mess up with the bootloaders = bricked phone), just like getting in recovery. It's something that comes with the phone.
Basically, not much can be done on the Captivate without a working usb.
Click to expand...
Click to collapse
Any other suggestions with the download mode? I can get into recovery 100% of the time but the vol down + power just turens on the phone. Anyway to get a rooting app from google play? or bypass apk block? Is there anyway to update from att over wifi? I can check for update on the phone but it just hangs there. Guess its cuz im not in the states. Respect though!! If u figure out anything else to try let me know. Bless!!
A way to sideload apps without USB is to download the Google Drive app from the Play Store then upload the APK from your computer to your Drive. Next access your Drive on your phone and select the APK it should begin the regular install.
**you will need to allow 3rd party applications**
guidostein said:
A way to sideload apps without USB is to download the Google Drive app from the Play Store then upload the APK from your computer to your Drive. Next access your Drive on your phone and select the APK it should begin the regular install.
**you will need to allow 3rd party applications**
Click to expand...
Click to collapse
Trying that now. What do i need to do to allow 3rd party apps? Will it just ask me?
Damn!! the third party thing is the same thing that blocks me from installing apps normally! Damn Google/ATT monopoly!!
saintnova said:
Trying that now. What do i need to do to allow 3rd party apps? Will it just ask me?
Click to expand...
Click to collapse
It should ask.
How to do it really depends on which OS you're running.
guidostein said:
It should ask.
How to do it really depends on which OS you're running.
Click to expand...
Click to collapse
Doesnt work, Third party blocked. Trying this but cant find this option http://androidforums.com/inspire-4g-tips-tricks/340745-unknown-sources-now-can-allowed.html
saintnova said:
Doesnt work, Third party blocked. Trying this but cant find this option
Click to expand...
Click to collapse
try going to Setting > Security > Enable Unknown Sources
thats where it is on my phone but im running a custom Rom
if that doesnt work try to find anything in the settings that says enable unknown sources.
---------- Post added at 04:09 PM ---------- Previous post was at 03:57 PM ----------
So I did some reading and if your running stock at&t ROM you most likely are not able to allow unknown sources (because for some reason AT&t blocks it).
You might want to try download an app called AppInstaller by FunTrigger from PlayStore (I have never used this and I'm not sure if it will get around the 3rd party problem you are having but its worth a shot)
You should be able to use it to install the APK in your Drive.
---------- Post added at 04:37 PM ---------- Previous post was at 04:09 PM ----------
Okay I think I've got it. Note that i have not tried this myself and take no responsibility if something goes wrong.
How to enable unknown sources on AT&T phone:
Settings > Applications > Manage Applications > All > select Customization Settings Provider and then Clear Data
Next go back one page and select Settings and then Clear Data
Now in Settings > Applications you should see the option unknown sources select it.
Now unknown sources are enabled!
guidostein said:
try going to Setting > Security > Enable Unknown Sources
thats where it is on my phone but im running a custom Rom
if that doesnt work try to find anything in the settings that says enable unknown sources.
---------- Post added at 04:09 PM ---------- Previous post was at 03:57 PM ----------
So I did some reading and if your running stock at&t ROM you most likely are not able to allow unknown sources (because for some reason AT&t blocks it).
You might want to try download an app called AppInstaller by FunTrigger from PlayStore (I have never used this and I'm not sure if it will get around the 3rd party problem you are having but its worth a shot)
You should be able to use it to install the APK in your Drive.
---------- Post added at 04:37 PM ---------- Previous post was at 04:09 PM ----------
Okay I think I've got it. Note that i have not tried this myself and take no responsibility if something goes wrong.
How to enable unknown sources on AT&T phone:
Settings > Applications > Manage Applications > All > select Customization Settings Provider and then Clear Data
Next go back one page and select Settings and then Clear Data
Now in Settings > Applications you should see the option unknown sources select it.
Now unknown sources are enabled!
Click to expand...
Click to collapse
And this my friend is why search is amazing :thumbup:
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
And this my friend is why search is amazing :thumbup:
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This option does not appear in my list. Remember i told ya i was reading that hehehe. Dont know why it isnt there though. Sigh. Maybe putting the ATT chip back in will help although i dont think its still activated.
saintnova said:
This option does not appear in my list. Remember i told ya i was reading that hehehe. Dont know why it isnt there though. Sigh. Maybe putting the ATT chip back in will help although i dont think its still activated.
Click to expand...
Click to collapse
I don't know how set you are on keeping your data but why not try a complete factory reset?
And if that doesn't work then just flash a new CWM and ROM,,, there are ways to do that without connecting to a computer.
guidostein said:
I don't know how set you are on keeping your data but why not try a complete factory reset?
And if that doesn't work then just flash a new CWM and ROM,,, there are ways to do that without connecting to a computer.
Click to expand...
Click to collapse
He can't without a usb.. That's just how the captivate is from stock.
Related
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
have made a backup? to open recovery?
Shoib said:
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
Click to expand...
Click to collapse
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
maybe try a diffrent computer first or try the official motorola update software?
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
max_avatar said:
have made a backup? to open recovery?
Click to expand...
Click to collapse
No, I haven't made a backup yet. I haven't accessed openrecovery either, the guide gave me a headache.
sileshn said:
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
It says "Battery Ok
Ok to program
connect USB
Data Cable"
smokeymacweed said:
maybe try a diffrent computer first or try the official motorola update software?
Click to expand...
Click to collapse
I could try that by putting an official update.zip so the boot loader will accept. Problem is there isn't any updates further to what I have and froyo womn't come anytime soon unless you were referring to something else.
DummyPLUG said:
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Let me try this. I'm going to bed for now, Ill post results tomorrow.
You can try installing your usb drivers again and try.Since you did not get any error in the bootloader mode, it could be problems with your usb drivers.
Uninstall the usb drivers and reinstall them again. Then try.
BTW, which version of rsdlite are you using?
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
xdazoli said:
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
Click to expand...
Click to collapse
Ok, I did everything you said and flashed it with A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf. But now it still gets stuck at the moto sign
Edit: I think I might have a solution as I flashed the phone with vulnerable_recovery_only_RAMDLD90_78.sbf which will let me use an update.zip. The only problem is I can't access my memory card and I don't have anything that could at home.
Edit: Ok, I fixed my phone and now it has 2.2.1. Thanks guys, I appreciate the help.
I'm having some problems upgrading my wife's phone. I went to the website with the upgrade instructions, downloaded Kies mini, and installed all of the drivers for the phone. I put the phone in usb debugging mode and plugged it in, but Kies doesn't see the phone. I tried messing around with some settings (i don't remember what I did) and it worked one time. And the one time it did work, it said something like unsupported device and the upgrade phone button was greyed out. I've tried searching everywhere for an answer to no avail. I don't know what I'm doing wrong
Did you use the USB port on the back of the PC?
No, I used one of the ports on the front
What sort of configuration was the phone running before you tried the update. Any customization? Rooted?
no customizations, unrooted
Make sure in the USB setting it of set to Kies (Fireware Update). This is under settings/applications
Sent from my SAMSUNG-SGH-I897 using XDA App
I did that. when I did switch it to kies, it said I had to turn off debugging mode. After i switched it to kies mode, i turned debugging back on. Should I not have done that?
the_KEV said:
I went to the website with the upgrade instructions, downloaded Kies mini, and installed all of the drivers for the phone. I put the phone in usb debugging mode and plugged it in, but Kies doesn't see the phone.
Click to expand...
Click to collapse
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
clemmie said:
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
Click to expand...
Click to collapse
I have never used kies before this. I didn't think I needed it. The instructions says debugging mode should be enabled.
Captivate Froyo update crash and how to solve
Note my device is an ATT Samsung Captivate S SGHi897
Kies would crash on the update indicating a conflict AMINIFUS.EXE from the AMINIFUSREQLEV component. Also sometimes, kies would not present the upgrade screen althought KIES sees the device memory/drives.
Here's what fixed it for me.
On the device - go to settings / development turn ON USB debuging and turn ON Allow mock locations.
With KIES running - the Capivate USB screen may not appear when you connect your USB cable. But the upgrade screen KIES will appear and start your upgrade.
IF you have a external SD card - remove prior to the update. I was able to update with my external SD card installed but when the device rebooted the device screen would go to black AFTER the ATT and Capivate splash screens and appear to hang. I removed my external card - rebooted the Capivate and the device was able to work this the initial Froyo set up screens - then the external was fine.
Samsung is aware of this problem and fix is not widely known. I person I spoke with at Samsung only discovered this fix on his previous call.
Good luck everyone. Froyo is finally OH and lastly = ATT will be rolling out an over the air update for those who do not want to go through KIEs.
You should definitely remove your SIM and external SD before flashing any new firmware, as a matter of Due Diligence.
I'd give it a try first with it disabled.
Oh yeah I forgot to mention that when the phone is not in debugging mode, the phone says it's connected to kies, but kies says no phone is connected
clemmie said:
You should definitely remove your SIM and external SD before flashing any new firmware, as a matter of Due Diligence.
I'd give it a try first with it disabled.
Click to expand...
Click to collapse
OK I'll try again when my wife gets home with the phone. would it be a good Idea to uninstall everything and start from the beginning?
I did it with usb debugging on. The important part id make sure your in Touchwiz. Otherwise keis will not see the phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
shinji257 said:
I did it with usb debugging on. The important part id make sure your in Touchwiz. Otherwise keis will not see the phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
did kies automatically see it or did you have do anything after you plugged in your phone?
I suggest using the full KIES application itself opposed to KIESmini.
If you do a quick google search (or even search the forums here) for KIES you will soon come across a download link for the full KIES application.
KIESmini has been known to have issues with 64bit operating systems. So check into that as well.
I run Win7 64bit and I could not get KIESmini to work. It would crash (stopped responding error) every time the device was connected. So I downloaded the full KIES application and the problem was solved... Everything updated fine.
clemmie said:
May I ask why did you put the phone in debugging mode? You don't need to. You should do what Viper 714 suggested. Have you ever used Kies before this attempt at updating the firmware?
Feel free to PM me and I'd be happy to assist you.
Click to expand...
Click to collapse
I had the same problems. Not only do you need to turn on debugging but also allow mock locations.
RaptorOne3 said:
I suggest using the actual KIES program itself opposed to KIESmini.
If you do a quick google search (or even search the forums here) for KIES you will soon come across a download link for the actual KIES application.
KIESmini has been known to have issues with 64bit operating systems. So check into that as well.
Good luck..
Click to expand...
Click to collapse
Unless you modify the built in Access database for Kies, it will not recognize the i897 as a supported device.
Back when I used to check for updates with Kies Mini frequently I always had trouble getting the phone to talk to Kies Mini. What I found worked the best is as follows:
1. Restart the PC
2. Restart the Phone
3. Disable Bluetooth on the phone if it is enabled
4. Put the phone in "Kies (Firmware update)" mode in Settings | Applications | USB Settings
5. Plug the phone into a USB port on the computer that is not on a root hub shared by any other devices (especially a keyboard or mouse).
6. Launch Kies Mini
Step 5 is very important because the phone must negotiate a USB 2.0 connection. I found that steps 1 & 2 were almost always necessary, without a clean boot on both devices, I frequently had problems. Step 3 seemed to help, though sometimes I could get the phone to connect to Kies Mini with Bluetooth enabled. I was able to get it to connect in either Kies "Firmware Update" mode, or USB debug mode. The documentation may specify USB debug mode because Bluetooth has to be disabled for USB debug mode.
I think I got it!! I uninstalled everything. Then I just did what everyone said. Used the back of the PC, made sure the phone what kies mode, with debugging, and mock locations, removed sim card and sd card...but then kies kept crashing. Then I found another post somewhere that said to uninstall IE9. I did that and now its finally working! Thanks yall for your help.
anyway I can add solved to the title?
Long story short, I've been haiving a bunch of problems, and someone pointed me to an update.zip file that might help me unroot my phone without needing a USB connection. When I go into recovery mode and select "install package", I get this message:
E:signature verification failed
installation aborted
Does anyone know what I may need to do in order to clear this up freaking problem?
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
studacris said:
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
Click to expand...
Click to collapse
Omg.. Another signature failed issue lol
Thanks for taking care of this one Studa
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click. Does one of those methods allow for the fix without a USB connection (I do think I have the ability to get a file from the computer to my phone via the external SD card).
Girevik said:
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click.
Click to expand...
Click to collapse
What you mean you get an error connecting the USB? Could you be more precise?
Also, the signature failed fix is quite easy. Tbh, you simply have to have your phone plugged in in debugging mode and run the .bat file.
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
studacris said:
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
Click to expand...
Click to collapse
I know, I know. I was saying for when/if it works. Duh
When I try to connect via USB I get a "USB Device Malfuctioned" error. (Which I HAVE searched on ) that I can't seem to find a fix for. I've tried it on 3 different computers, each with a different version of Windows, with the same result so don't think it's a driver issue.
I've done a factory data reset (several atually) and am still having problems, so I'd like to get a warranty replacement. But my phone is rooted so I'm worried about them voiding my waranty. Basically where I am now is tryign to find a way to unroot my phone without the USB so I can get it replaced. That lead me to the signature verifaction error and the shame of a premature post.
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
studacris said:
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
Click to expand...
Click to collapse
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Girevik said:
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Click to expand...
Click to collapse
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
studacris said:
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Click to expand...
Click to collapse
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
quarlow said:
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
Click to expand...
Click to collapse
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Girevik said:
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Click to expand...
Click to collapse
The method is actually a bit different then what he mentionned:
Unplug usb;
Pull battery;
Hold volume buttons (and keep holding no matter what);
Plug usb in your pc and then your phone;
Put the battery back in and wait until the android with a shovel shows up.
It can take a few tries too before it works.
studacris said:
what you will have to try is fix the 3e recovery manually.
Click to expand...
Click to collapse
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
Click to expand...
Click to collapse
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
Click to expand...
Click to collapse
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
studacris said:
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Click to expand...
Click to collapse
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
BWolf56 said:
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
Click to expand...
Click to collapse
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
studacris said:
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
Click to expand...
Click to collapse
That was imployed but Fine be that way! lol
So yea, OP - Beside all that Team confusion we're having here.. Go read/keep reading the Sticky about 3e recovery fix and if you think you can do it. Do the manual fix (getting Root Explorer and moving the recovery file by yourself) and get Cognition on your external and move it to your internal sd card.
(There I'm being clear Studa )
I have the International non-developer version and it came with the stock ROM with Sense 5. I rooted it and installed Google's 4.2.2 stock ROM, but when the 4.3 version came out I updated it via OTA (I know I shouldn't have done that, but I guess what's done is done). After the update, whenever I plug in my phone it still shows up but when I open it there's nothing in it no matter how many times I refresh it. Also, when I try to use Nandroid Manager it says that my phone is not rooted.
Now I also can't use adb and fastboot as they both say there is no phone plugged in when it is actually plugged in. How do I solve this? Any help would be appreciated
Btw, I have the drivers for the phone installed along with HTC Sync Manager.
Enable the USB debugging in the Developer settings > that enables ADB
I assume you know, that you need to tap on the build number 7 times to let the developer menu pop up
Since 4.3 there is multiuser, you must move your data with a file manager from data/user to data/user/0
davebugyi said:
Enable the USB debugging in the Developer settings > that enables ADB
I assume you know, that you need to tap on the build number 7 times to let the developer menu pop up
Since 4.3 there is multiuser, you must move your data with a file manager from data/user to data/user/0
Click to expand...
Click to collapse
Well I didn't know about the developer menu thing ._. I thought there was no developer settings for the ROM.
Anyway, I did what you said but adb/fastboot still can't detect it.
ickytc said:
Well I didn't know about the developer menu thing ._. I thought there was no developer settings for the ROM.
Anyway, I did what you said but adb/fastboot still can't detect it.
Click to expand...
Click to collapse
That is strange...
It wont recognize from fastboot either?
davebugyi said:
That is strange...
It wont recognize from fastboot either?
Click to expand...
Click to collapse
Exactly ._. Anyway to solve this?
Could it be due to different pc configuration or a faulty cable ?
I myself have a couple knock-off cables with them i usually have
To remove and resert a couple times before a big file gets transfered
alay_ said:
Could it be due to different pc configuration or a faulty cable ?
I myself have a couple knock-off cables with them i usually have
To remove and resert a couple times before a big file gets transfered
Click to expand...
Click to collapse
I've tried multiple devices and cables.
ickytc said:
I've tried multiple devices and cables.
Click to expand...
Click to collapse
If that case try a different pc / laptop, then ull at leadt be sure whether its the pc/ laptop or the mobile device which is causing troubles ...
alay_ said:
If that case try a different pc / laptop, then ull at leadt be sure whether its the pc/ laptop or the mobile device which is causing troubles ...
Click to expand...
Click to collapse
I meant to say I tried different PCs
Okay now fastboot detects the phone but adb still doesn't detect it. Help anyone?
Try flashing a new recovery. fastboot flash recovery recovery.img
Sent from my HTC One using Tapatalk
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
The phone has to be booted into the os for adb to work. Fastboot only until you get a rom flashed.
Sent from my HTC One using Tapatalk
So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.
Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk
Have you tried reinstalling the drivers on your pc or tried a different pc?
spookykidmm said:
Well to start backwards, the stock recovery isn't really meant to flash zips, but it should go farther than saying Footer Is Wrong
Signature Verification has failed. For me, it says that, then if you wait a few seconds, it'll say a few other things, then install from sd card complete and it wipes data and cache then reboots. Next, you have to use an official cable for that, Media Transfer doesn't work correctly without oem cable
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I do use an oem cable. Same thing. The rest of what you said does happen though.
dustincrock said:
I do use an oem cable. Same thing. The rest of what you said does happen though.
Click to expand...
Click to collapse
The cord is funky sometimes. Try to "mangle" it a little bit to see if odin will say "Added!". I know I have to basically wrap mine around the computer to get it to work correctly
Sent from my SM-N9005 using Tapatalk
sparx said:
Have you tried reinstalling the drivers on your pc or tried a different pc?
Click to expand...
Click to collapse
Yes I have. Still the same problems.
dustincrock said:
Yes I have. Still the same problems.
Click to expand...
Click to collapse
Any luck?
Sent from my SM-N9005 using Tapatalk
spookykidmm said:
Any luck?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
No. No luck..
A Last Resort
dustincrock said:
So, I have a Galaxy note 3 G900A. Not sure what version and I don't have access to that. So, it has the Alliance rom installed on it. It was working fine for months with absolutely no problems. Then all of a sudden, earlier, it said NFC has stopped working, over and over again. Then, I turned off the phone and it failed to turn on. It will not get past the splash screen. It just wants to stay dark and if I leave it alone long enough, it automatically goes into recovery mode. I can get into recovery mode and download mode normally. I already tried factory reset and all of that. None of my computers will recognize the phone and I have tried multiple cables as well. Odin won't recognize it and neither will samsung kies. I tried installing stock rom through SD card and it says
Verifying update package:
E:Footer is Wrong
E: Signature Verification Failed.
It does that no matter what rom I try to install. I can't afford to get another phone right now and it is the only one I have and I just don't know what else I can do. Any help is greatly appreciated.
Click to expand...
Click to collapse
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.
zancro said:
As a last resort, put the device into download mode and connect to KIES 3. Go to tools and do a complete reinstallation. This will return you device to full factory specs and latest approved software, no custom ROM, no root, and no saved data. But at least you will have a functioning device. As soon as possible look into getting a new battery.
Click to expand...
Click to collapse
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode
dustincrock said:
I even used different batteries. And kid won't work because the phone isn't detected by the computer as being a phone. Kies doesn't pick up the phone, even in download mode
Click to expand...
Click to collapse
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.
G900A?
zancro said:
Your only remaining option might be to send your device away for professional help. In the past I have used the services of Josh at: http://mobiletechvideos.com/ . (I am not related to that organization in any way.) For around $50.00 they can do a complete refresh, and in my case offered to root and load the custom ROM of my choice for a small additional fee. It took about one week.
Good luck.
Click to expand...
Click to collapse
I checked back to see if you had solved the problem and noticed something I missed earlier... Your OP says you are using a G900A. Are you referencing a Note 3 or some other device?