I have clockworkmod and I updated the recovery to 3.0.0.8. When I boot into recovery and try to install EC10 comavolt and it won't let me. I also tried to install other recovery's via Rom Manager but it says download failed.
ddb1984 said:
I have clockworkmod and I updated the recovery to 3.0.0.8. When I boot into recovery and try to install EC10 comavolt and it won't let me. I also tried to install other recovery's via Rom Manager but it says download failed.
Click to expand...
Click to collapse
Rom manager is not compatible with our phones. You will likely need to revert back to an older version of cwm.
Sent from my SCH-I500 using XDA App
akellar said:
Rom manager is not compatible with our phones. You will likely need to revert back to an older version of cwm.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ohhhhhhh OK well how would I go about reverting back and I am looking for the info while Im sending this
ddb1984 said:
Ohhhhhhh OK well how would I go about reverting back and I am looking for the info while Im sending this
Click to expand...
Click to collapse
I too would also like to know where I can get this older version of cwm.
http://forum.androidcentral.com/ver...roms-w-root-clockwork-updated-3-25-a-389.html
There should be a link to a cwm.tar file (not the exact name) on this page. Flash it via odin and there you go.
Sent from my SCH-I500 using XDA App
emarohl said:
http://forum.androidcentral.com/ver...roms-w-root-clockwork-updated-3-25-a-389.html
There should be a link to a cwm.tar file (not the exact name) on this page. Flash it via odin and there you go.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats my problem I cant use my USB right now and I can only zip at the moment but barely can do that do to the Recovery messing up
Can't use USB right now...? I think you might be confusing transferring files to the USB card while the phone is booted, with flashing a TAR file via Odin.
Remember--when you're flashing via Odin, your battery is pulled, the phone is off, and then--while you do plug in your USB cable--it's only receiving power through that USB connection.
Use BDE's "How to customize.." guide here, and go directly to step 2. If you don't already have it, grab the "Red" Recovery from this thread (also linked to in BDE's guide); grab the TAR file listed there. Then go back to the guide and follow the instructions for Step 2.
That should get your recovery back to Red recovery, and I think from there I'd make sure everything else is working and the phone boots before doing anything else. Once it's up and running, then maybe give the kernel another shot.
EDIT: Thought of what else you might mean; if you're unable to get Odin to recognize when your phone is plugged in, hit up the Samsung website to get the Samsung USB drivers. Then, when you hold the volume down key as described in the guide, you should see one cell of Odin turn yellow, which tells you your phone has been recognized. Assuming you have a Windows PC, at least.
ChromWolf said:
Can't use USB right now...? I think you might be confusing transferring files to the USB card while the phone is booted, with flashing a TAR file via Odin.
Remember--when you're flashing via Odin, your battery is pulled, the phone is off, and then--while you do plug in your USB cable--it's only receiving power through that USB connection.
Use BDE's "How to customize.." guide here, and go directly to step 2. If you don't already have it, grab the "Red" Recovery from this thread (also linked to in BDE's guide); grab the TAR file listed there. Then go back to the guide and follow the instructions for Step 2.
That should get your recovery back to Red recovery, and I think from there I'd make sure everything else is working and the phone boots before doing anything else. Once it's up and running, then maybe give the kernel another shot.
EDIT: Thought of what else you might mean; if you're unable to get Odin to recognize when your phone is plugged in, hit up the Samsung website to get the Samsung USB drivers. Then, when you hold the volume down key as described in the guide, you should see one cell of Odin turn yellow, which tells you your phone has been recognized. Assuming you have a Windows PC, at least.
Click to expand...
Click to collapse
Yea I even put in another post about my USB issues and can't seem to find a solution. I may just purchase another phone. My girls works perfect and no connection problems but I may of damaged it or something but it only charges doesn't work other wise. ADB, USB file transfer, nothing.
ChromDog's post was a mess. I'm ignoring it.
So you're saying you can't even get the phone to work in Download mode? Will the phone actually boot up into Download mode?
add144 said:
ChromDog's post was a mess. I'm ignoring it.
So you're saying you can't even get the phone to work in Download mode? Will the phone actually boot up into Download mode?
Click to expand...
Click to collapse
Yea I get the yellow screen with the android saying downloading. I have tried 3 cables and 5 diff computers. I even went to cellular south and got a new cable. When I figured it was my phone was when my girls phone worked with the same equipment. Also sometimes when I plug it up to the PC doing download mode it will say USB Not Recognized and I have the drivers installed I even tried to select the specific driver but didnt know which one to do out the that folder of many LOL
Have you tried opening ODIN in Download Mode anyway just to see if it'll recognize the phone?
add144 said:
ChromDog's post was a mess. I'm ignoring it.
Click to expand...
Click to collapse
Rare is the occasion that wiser words than these have been uttered. XD
While I was getting pretty wordy with my answer, Add's more or less on the same track as me: Even with the USB not working when the phone's booted normally, does Odin recognize it even so, or is Odin what you've been trying and not getting to work?
ddb1984 said:
Yea I get the yellow screen with the android saying downloading. I have tried 3 cables and 5 diff computers. I even went to cellular south and got a new cable. When I figured it was my phone was when my girls phone worked with the same equipment. Also sometimes when I plug it up to the PC doing download mode it will say USB Not Recognized and I have the drivers installed I even tried to select the specific driver but didnt know which one to do out the that folder of many LOL
Click to expand...
Click to collapse
The different computers you tried wouldn't really matter unless each one had the Samsung USB driver installed. Also, does your girlfriend have the same model phone as you? If not, it's not necessarily a fair test.
It does sound like you've tried using Odin, and it just hasn't worked (based on the bolded part). So, try this:
http://www.samsung.com/us/support/downloads/SCH-I500RKAXAR
Go to the above link. Underneath where it says "Download Center for SCH-I500RKAXAR", look for "Manuals | Software". Software should be a blue link; click on that.
You should see a list of four items you can download. Look all the way to the right, under the "File" column; there should be four little icons. Click on the first of the four, and Agree to their user agreement. Save the file somewhere easy to remember, and run that file. I'd suggest doing this on any home computer you might connect your Showcase to.
Then, try putting the phone in Download mode and connecting to Odin once again.
Does it work after that?
I dont know how or why but I was able to get odin to work on a XP machine and I flashed the odin files for pick and pack and the odin files for cwm recovery all and was able to get both the recovery and 2.2 but I have more problems LOL. My internal memory is 0. I factory wiped and wiped cache via red recovery but to no avail. Still getting 0
If you can get into your phone and do stuff in Android, I'd run a Titanium Backup of your apps and stuff. If not, you may be SOL.
I'd start by just finding a stock ROM for 2.1 or 2.2.1 and Odin'ing that over to the phone. Start completely clean, no custom ROMs. Then load up CWM Red again.
ChromWolf said:
If you can get into your phone and do stuff in Android, I'd run a Titanium Backup of your apps and stuff. If not, you may be SOL.
I'd start by just finding a stock ROM for 2.1 or 2.2.1 and Odin'ing that over to the phone. Start completely clean, no custom ROMs. Then load up CWM Red again.
Click to expand...
Click to collapse
I have been looking for 2.1 Stock Rom for CS but I have not been able to. I have my apps backed up but unfortunately I can't install them in this Rom yet but I will keep trying to get it.
Ouchie! I just had a look throughout the Mes Dev thread, and the one post I saw for EB11 for Showcase had the link removed. Couldn't find any other reference for an actual stock 2.1 or 2.2.1 specifically for the showcase; the guys *may* tell you the Mesmerize ones work for Showcase, but DO NOT use them until one of them says so. I would guess not, but don't know for sure.
I'd see about hitting the IRC channel and asking for a clean stock ROM from there, and/or maybe getting some "in-person" advice that way. ...or hope Phidelt82 or Elijahblake come across this thread to get it to you/help you out otherwise. XD
LOL IKR but I have already asked them for a Stock 2.1 Rom for CS and I was pointed to someone but they haven't responded to me so idk. And thanks for some of the info and I am happy I was able to get the files b4 he removed his comments. I had them already saved on the computer.
ddb1984 said:
LOL IKR but I have already asked them for a Stock 2.1 Rom for CS and I was pointed to someone but they haven't responded to me so idk. And thanks for some of the info and I am happy I was able to get the files b4 he removed his comments. I had them already saved on the computer.
Click to expand...
Click to collapse
Some individuals were trying to put together a 2.1 stock image but weren't able to get one working, the one they have is stock 2.2 and that is the only pure stock ROM they have, but there is no reason to go back to 2.1 unless you planned on using it and staying with it, so a clean flash to 2.2 should fix any issues you may be experiencing.
bdemartino said:
Some individuals were trying to put together a 2.1 stock image but weren't able to get one working, the one they have is stock 2.2 and that is the only pure stock ROM they have, but there is no reason to go back to 2.1 unless you planned on using it and staying with it, so a clean flash to 2.2 should fix any issues you may be experiencing.
Click to expand...
Click to collapse
I am with Cellular South and I don't believe there is a stock for us just yet. I was also able to put the SDcard in a card reader and put Superclean 2.9.2 on it for Showcase. Pray I get internal storage and my phone works.
YES!!!!!!!! Internal Storage w/ Superclean and a working recovery. Well I have more issues to attend to but that's wonderful to me.
Related
I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.
matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.
TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950
matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?
Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App
matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App
TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk
TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.
Let me know what happens.
Sent from my Nexus S using XDA App
matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.
I've been trying to figure this out for hours...
I recently got a Charge (I also have an old Fascinate). and I'm trying to root it. It came out of the box with EE4. I primarily use a macbook pro, but have learned that I can't root EE4 with it. So, I booted up my old school desktop PC.
I can't get Odin 1.82 (or 1.3 for that matter) to recognize my Charge or my Fascinate. I've tried 4 different Samsung driver files, and the computer recognizes the phones in USB Storage mode just fine (telling me that the usb cable is working fine). I can transfer files and everything. And yes, the phones have the yellow road sign looking thing and say "Downloading..."
But when I put either in download mode:
USB device not Recognized.
One of the USB devices attached to this conputer has malfunctioned and Windows does not recognize it. For assistance click this message.
Basically, acts as though no driver is installed. and when I click the message and go to Update the driver (while still in download mode), I went to C:\Program Files\Samsung\USB Drivers\, but there's tons of folders and non of them contain a working driver for download mode (I tried them all).
I don't care about the Fascinate. I only mentioned it because I thought there was something to neither phone working. And this is the first (and only) time I've tried to get Odin to work (ie. it hasn't worked ever).
I've searched all over the forums, internet, and soul trying to figure this out. I can't be the only one this has happened to. Or I'm missing something really fking obvious.
I'm on an old custom made desktop with an AMD 1700+ processor running Windows XP (not 64 bit).
tifford said:
I've been trying to figure this out for hours...
I recently got a Charge (I also have an old Fascinate). and I'm trying to root it. It came out of the box with EE4. I primarily use a macbook pro, but have learned that I can't root EE4 with it. So, I booted up my old school desktop PC.
I can't get Odin 1.82 (or 1.3 for that matter) to recognize my Charge or my Fascinate. I've tried 4 different Samsung driver files, and the computer recognizes the phones in USB Storage mode just fine (telling me that the usb cable is working fine). I can transfer files and everything. And yes, the phones have the yellow road sign looking thing and say "Downloading..."
But when I put either in download mode:
USB device not Recognized.
One of the USB devices attached to this conputer has malfunctioned and Windows does not recognize it. For assistance click this message.
Basically, acts as though no driver is installed. and when I click the message and go to Update the driver (while still in download mode), I went to C:\Program Files\Samsung\USB Drivers\, but there's tons of folders and non of them contain a working driver for download mode (I tried them all).
I don't care about the Fascinate. I only mentioned it because I thought there was something to neither phone working. And this is the first (and only) time I've tried to get Odin to work (ie. it hasn't worked ever).
I've searched all over the forums, internet, and soul trying to figure this out. I can't be the only one this has happened to. Or I'm missing something really fking obvious.
I'm on an old custom made desktop with an AMD 1700+ processor running Windows XP (not 64 bit).
Click to expand...
Click to collapse
the pc itself doesn't sound like the problem, at least not directly... the only things I can suggest would be to either try different USB ports, a different cable, uninstalling and reinstalling the driver: http://dl.dropbox.com/u/34782489/SAMSUNG_USB_Driver_for_I510_v1.3.1900.0.exe (which is made specifically for the Charge), disabling any antivirus that may be installed (or running Odin as administrator), and making sure USB debugging is ticked off under 'development' in applications settings
thanks for the quick response, but unfortunately, i've tried all of those except for disabling debugging. and, sadly, that didn't do the trick.
i've tried all of the usb cables i own (about 7). i've uninstalled and reinstalled divers from every link posted, and rebooted after each time. i've tried all of my usb ports on my computer. i've even cleared out the usb history in regedit.
::sigh::
tifford said:
thanks for the quick response, but unfortunately, i've tried all of those except for disabling debugging. and, sadly, that didn't do the trick.
i've tried all of the usb cables i own (about 7). i've uninstalled and reinstalled divers from every link posted, and rebooted after each time. i've tried all of my usb ports on my computer. i've even cleared out the usb history in regedit.
::sigh::
Click to expand...
Click to collapse
well if it was just the Charge I would say there may be a problem with the phone or somethings not being done right, I have heard of some people having phones (Fascinate mostly) that won't go into download mode for Odin but will work perfectly with everything else... however both phones not working seems to be some kind of issue with the pc or cable, but I couldn't say for sure as I'm not knowledgable on the hardware of android phones
1700+. That's REALLY old school.
Sent from my Droid Charge running GummyCharged 2.0
still can't get it to work...
is there any way to go back to eb01 or whatever without root or Odin?
or can someone post the Download Mode driver?
tifford said:
still can't get it to work...
is there any way to go back to eb01 or whatever without root or Odin?
or can someone post the Download Mode driver?
Click to expand...
Click to collapse
If anyone is an ADB guru here they may know how to do it with that, like pushing CWM to the phone and then you can probably flash to stock... I only know how to do basic things like install apk's and logcat
I know with most phones, you can't go back without root because the system doesn't let you. I'm used to the Droid incredible and incredible 2, where rooting and flashing roms is easy as pie with some knowledge of adb and cwm. none of the ed01, ee4, fu69 stuff to worry about. Odin seems very easy, and its damn near impossible to permanently brick your phone if you have it. BUT I can't get it to work.
is there an adb / non-Odin root method for ee4?
if I understand correctly, the gingerbreak method and one click method don't work with ee4. (I've tried both of those too)
Sent from my SCH-I510 using xda premium
Your on Mac? Have u tried using heimdall?
Sent from my SGH-I897 using XDA Premium App
I've tried using heimdall on my Mac and can't get it figured out. heimdall 1.3 (older heimdalls like 1.1.1 wont open) requires a framework.XML file which Odin roms don't have. I can create one but the only way I can do that is by using a .pit file (which creates a partition) which I'd have to take from other rom files. the only way can see it working is by Frankensteining it together to get it to flash which does doesn't seem right.
I could be completely misunderstanding how to get it to work. I could just use heimdall in terminal, but I don't understand it enough yet to attempt. heimdall 1.3 looks nothing like the way I thought it would (where I select all the recovery, bootloader, etc files individually)
grr...
Sent from my Xoom using Tapatalk
You know we DO have a PIT file right?
Sent from my Galaxy Tab running MIUI
which should I use? depending on the rom I use, does it matter which PIT file I use?
Sent from my SCH-I510 using xda premium
tifford said:
which should I use? depending on the rom I use, does it matter which PIT file I use?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
there's only one PIT file and its for getting to stock 2.2 Froyo
so, I should only use it for flashing back to stock 2.2?
can I use it for flashing a 2.2 rom like gummy charged 1.9.1?
does it matter which stock 2.2 I use? ed01? ee4?
Sent from my SCH-I510 using xda premium
tifford said:
so, I should only use it for flashing back to stock 2.2?
can I use it for flashing a 2.2 rom like gummy charged 1.9.1?
does it matter which stock 2.2 I use? ed01? ee4?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
yes only for stock 2.2 because it is what reformats your partitions after they've been converted to ext4 with lagfix/voodoo
as for stock roms EE4 is the latest and hasn't given me any problems when Odining but I suppose the others like ED1 or ED2 would be fine
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
tifford said:
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
soft brick, you need to odin EE4 stock with the PIT file and it'll be back to normal.. its almost impossible to permabrick this phone through user error, only if the boot.bin files are corrupted afaik
blazing through on my 4G Droid Charge
tifford said:
just bricked it.
I was trying to revert back to ed1 so that I could root from there with gingersnap / gingerbreak through adb
I downloaded the Verizon stock ed1 file and pit file, inserted all of the files in the correct place (param = parameters.rfs etc.) it got to uploading kernel and failed. now my phone boots into a picture of a cellphone then an arrow pointing at a computer with a yellow triangle with a !
and I have no way of unbricking it.
I'm going to borrow someone's windows laptop and Odin it back to health (hopefully)
then I'm returning it for a thunderbolt. this phone has driven me mad.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
We don't root through ADB.
Sent from my Droid Charge running GummyCharged 2.0
i borrowed a friend's windows laptop. i used Odin to go back to stock ED1
Then ROOTED THROUGH ADB on my mac...
i'm a happy camper now.
Thanks for the help guys
Have fun with ED1.. . If you update it will break root.
Sent from my Droid Charge running GummyCharged 2.0
My wife's GS4G connects to the computer but only charges. The phone does not recognized that it's plugged in to the computer, and the computer doesnt acknowledge the device either. I doubt I have a driver issue because the computer would at least tell me that it couldnt find them. The phone only charges when it's connected. I want to know if there's a way to root the phone without using the computer. I could then use wireless adb after that I guess. I looked at this one tutorial but I couldnt flash any Rooting Zips from the bootloader because my bootloader is version e3 (?) and I guess you need e2. Is there a workaround for this or am I forever doomed?
Assuming you're on Froyo, download the update.zip from this post:
http://forum.xda-developers.com/showthread.php?t=1099374
That will get you CWM.
Download the Bali kernel from this thread:
http://forum.xda-developers.com/showthread.php?t=1080871
Once you put it on your sd card and use the update.zip from the first post to get into cwm, flash the new kernel since it's got a newer version of CWM + root. You'll be able to tinker with your phone after that. Note that you will only have support for Froyo CWM roms after that so don't try flashing any Gingerbread CWM roms until you manage to get your computer to recognize it.
Great! Now what's restricting the ROM flashing to Froyo only? I've talked to a few people that think the usb port on the phone is broken. I've gotten no other explanations. It doesn't look like I'll be getting it connected at all.
damastah said:
Great! Now what's restricting the ROM flashing to Froyo only? I've talked to a few people that think the usb port on the phone is broken. I've gotten no other explanations. It doesn't look like I'll be getting it connected at all.
Click to expand...
Click to collapse
To upgrade to Gingerbread you need to install a new bootloader that is only installable via samsung kies or via odin/hemidall. All of which require you to be hooked to a computer.
eollie said:
To upgrade to Gingerbread you need to install a new bootloader that is only installable via samsung kies or via odin/hemidall. All of which require you to be hooked to a computer.
Click to expand...
Click to collapse
What eollie said is true. We've tried experimenting with flashing bootloaders via CWM, but that just wound up bricking phones, so you WILL need a computer to get on Gingerbread.
Maybe you can try to get a phone repair company to fix your USB port for you once you verify that it IS broken.
FBis251 said:
Assuming you're on Froyo, download the update.zip from this post:
http://forum.xda-developers.com/showthread.php?t=1099374
That will get you CWM.
Download the Bali kernel from this thread:
http://forum.xda-developers.com/showthread.php?t=1080871
Once you put it on your sd card and use the update.zip from the first post to get into cwm, flash the new kernel since it's got a newer version of CWM + root. You'll be able to tinker with your phone after that. Note that you will only have support for Froyo CWM roms after that so don't try flashing any Gingerbread CWM roms until you manage to get your computer to recognize it.
Click to expand...
Click to collapse
cwm recovery didnt work. esignature verification failed or something like that.
What colors were the letters when it said signature verification failed?
Sent from my SGH-T959V using XDA App
FBis251 said:
What colors were the letters when it said signature verification failed?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Red
Sent from my computer using Google Chrome
damastah said:
Red
Sent from my computer using Google Chrome
Click to expand...
Click to collapse
And you got that after trying to flash bali?
Once you put it on your sd card and use the update.zip from the first post to get into cwm, flash the new kernel since it's got a newer version of CWM + root. You'll be able to tinker with your phone after that.
Click to expand...
Click to collapse
No, you said flash cwm first... I couldnt do that so I didnt want to continue. Didn't want to risk bricking her phone.
damastah said:
No, you said flash cwm first... I couldnt do that so I didnt want to continue. Didn't want to risk bricking her phone.
Click to expand...
Click to collapse
"use the update.zip to get into cwm" The update.zip file will get you yellow cwm. Don't worry it won't brick her phone if you're on Froyo and you have the SGH-T959V. The bali kernel won't work unless you flash it from the yellow CWM. If the screen you're trying to flash from has mostly blue letters, you're in samsung recovery which will only let you flash the update.zip to get yellow CWM.
Ok, This is what I did. I downloaded the second linked file from the thread you linked. It was an update.zip. I booted into the screen with the mostly blue letters,
did you select install update zip bro?
yeah. Thats how I got to what you see in the second image
Since your phone is probably not rooted you'll need to use this exploit to get it rooted directly from the phone:
http://kimete.com/z4root.html
Skip steps 1 through 4 since you're gonna download the apk directly to your phone.
Yeah, the phone's not rooted. I'll try that.
How long does z4root take to run? It just spins and spins for me...
damastah said:
How long does z4root take to run? It just spins and spins for me...
Click to expand...
Click to collapse
Hmm, it took less than 2 mins in the description video I watched.
damastah said:
Ok, This is what I did. I downloaded the second linked file from the thread you linked. It was an update.zip. I booted into the screen with the mostly blue letters,
Click to expand...
Click to collapse
Is the name of the update.zip actually "update.zip" if it isn't then the recovery isn't going to recognize it.
It was named update.zip... and z4root didn't work for the phone... it crashes at the end
Im trying to figure all this out and do it safely. I guess I bricked my 1st phone blue light only no power? I'm hoping to NOT do it again :good: ... Not very easy to get help around these forums since most ppl think you should already know. Im on ff18 and root per Qbkings vid, agat 0.2.1. Im timid on flashing now due to the brick. I have flshed about 10 roms when i was on el29 and never had any problems until i tried to flash an ICS rom.
So if im on ff18 root agat can I just use the format all and flash safely. And also how do you know when your going between roms that you are doing it safe? I want to try a few out?
Gtalk or emial [email protected] for any help offered.
Thank you in advance
Even though there is custom recoveries for ics. Many of us still use the tried and true method by using the el26 kernel.
Also format all does not play well with ics. Just wipe caches and do a factory wipe.
Sent from my SPH-D710 using xda premium
gilbydakid said:
Even though there is custom recoveries for ics. Many of us still use the tried and true method by using the el26 kernel.
Also format all does not play well with ics. Just wipe caches and do a factory wipe.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Cool so stay away from the caulk format all?
I flashed gingerbread roms over and over, after a bit my restores wouldn't work , then went for the milestone rom and bricked... I was supposed to use el26 according to vid and I think I tried to do it using clockwork instead of Odin(was I supposed to use Odin)? The only time I've used Odin was to root when I was on el29 and to root after i got ff18 ota. So do you use Odin each time and install the 26 kernel each time I want to install a new rom to be safe? ( if so then cool but I want to make sure I understand ) do I also have to are install cwm each time ( like meaning a safe version of it )
Right now the few rooms I'm seeing that I would like to try is cm9, the universe rom, and I hear about the " goodness rom"?
OK, so heres situation I'm on agat 2.1 and ff18 . Out of those three can I just download the rom and flash one or do I need to go to the 26 kernel and then do it EVERYTIME to be safe? I was sent a link for a safe kernel and said to " use and flash "? That just doesnt make complete sense to me yet?
Any and all is soooooo appreciated! I'm going to get this figured out so I can be comfortable and pros like some of you! I m really looking forward to it and if anybody wants to help a bit you can hit my email and I will not try to just waste ur time lol...
Thank you
A guy who doesn't wanna be a noob 4ever
I used this
http://forum.xda-developers.com/showthread.php?t=1525495
jpeclf said:
Cool so stay away from the caulk format all?
I flashed gingerbread roms over and over, after a bit my restores wouldn't work , then went for the milestone rom and bricked... I was supposed to use el26 according to vid and I think I tried to do it using clockwork instead of Odin(was I supposed to use Odin)? The only time I've used Odin was to root when I was on el29 and to root after i got ff18 ota. So do you use Odin each time and install the 26 kernel each time I want to install a new rom to be safe? ( if so then cool but I want to make sure I understand ) do I also have to are install cwm each time ( like meaning a safe version of it )
Right now the few rooms I'm seeing that I would like to try is cm9, the universe rom, and I hear about the " goodness rom"?
OK, so heres situation I'm on agat 2.1 and ff18 . Out of those three can I just download the rom and flash one or do I need to go to the 26 kernel and then do it EVERYTIME to be safe? I was sent a link for a safe kernel and said to " use and flash "? That just doesnt make complete sense to me yet?
Any and all is soooooo appreciated! I'm going to get this figured out so I can be comfortable and pros like some of you! I m really looking forward to it and if anybody wants to help a bit you can hit my email and I will not try to just waste ur time lol...
Thank you
A guy who doesn't wanna be a noob 4ever
Click to expand...
Click to collapse
Sorry it took so long to get back, it got kind of hectic at work.
Here is my formula of flashing.
Odin el26- make sure it is in the pda slot.
Go into recovery. From there I wipe dalvik, cache, factory 3 times apiece. You don't have to do it that much, it just gives me piece of mind.
Flash rom from zip. Reboot. Then I flash my modem through Odin- make sure the modem bin file is in the phone slot.
Hit run wait for it to reboot and enjoy.
Also don't worry about asking me any questions unlike most of the xda members I'm not a prick that will tell you search and read.
I can read a calculus book until I'm blue in the face. Doesn't mean I'm going to know how to do calculus after unless I'm given some guidance.
My current setup is -
Cm9- 6/21 build from Chris g
Kernel- ff11
Modem- el29
Sent from my SPH-D710 using xda premium
Odin v1.81 will not see phone in download mode
Hi,
my Epic4gTouch is currently on IMM761.FH13 and I want to go back to prerooted EL29.
I follow the instructions from this link by sfhub
http://forum.xda-developers.com/showthread.php?t=1409634
I downloaded and loaded Odin3Excution v1.81
a) Put my phone into download mode with power and volume up.
1) The software never recognized my phone and I get no yellow com port. My window 7 PC does recognize my phone even in download mode.
2) If I do the same thing for my wife's phone which is still on GB then it sees the com port, but not on the phone with ICS installed already.
I tried to search and see if people have the same issue and did not find anything. For those who have already downgraded from ICS to EL29
can you please tell me which software you use and how you did it.
Thank you,
-Doan
gilbydakid said:
Sorry it took so long to get back, it got kind of hectic at work.
Here is my formula of flashing.
Odin el26- make sure it is in the pda slot.
Go into recovery. From there I wipe dalvik, cache, factory 3 times apiece. You don't have to do it that much, it just gives me piece of mind.
Flash rom from zip. Reboot. Then I flash my modem through Odin- make sure the modem bin file is in the phone slot.
Hit run wait for it to reboot and enjoy.
Also don't worry about asking me any questions unlike most of the xda members I'm not a prick that will tell you search and read.
I can read a calculus book until I'm blue in the face. Doesn't mean I'm going to know how to do calculus after unless I'm given some guidance.
My current setup is -
Cm9- 6/21 build from Chris g
Kernel- ff11
Modem- el29
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
doan_group said:
Hi,
my Epic4gTouch is currently on IMM761.FH13 and I want to go back to prerooted EL29.
I follow the instructions from this link by sfhub
http://forum.xda-developers.com/showthread.php?t=1409634
I downloaded and loaded Odin3Excution v1.81
a) Put my phone into download mode with power and volume up.
1) The software never recognized my phone and I get no yellow com port. My window 7 PC does recognize my phone even in download mode.
2) If I do the same thing for my wife's phone which is still on GB then it sees the com port, but not on the phone with ICS installed already.
I tried to search and see if people have the same issue and did not find anything. For those who have already downgraded from ICS to EL29
can you please tell me which software you use and how you did it.
Thank you,
-Doan
Click to expand...
Click to collapse
http://hotfile.com/dl/145140482/1e58...Stock.zip.html el29 file
http://forums.acsyndicate.net/showthread.php? 2685-Odin-1-85-download-for-the-Epic-Touch-4G odin 1.85
http://www.youtube.com/watch? v=_vmEmheJnyg
Btw download mode is power and volume DOWN then once your there you press the up button you get into download mode before plugging in.
If odin doesnt recognize phone with yellow com ..try a different cable
hope it helps
Sent from my SPH-D710 using Tapatalk 2
doan_group said:
Hi,
my Epic4gTouch is currently on IMM761.FH13 and I want to go back to prerooted EL29.
I follow the instructions from this link by sfhub
http://forum.xda-developers.com/showthread.php?t=1409634
I downloaded and loaded Odin3Excution v1.81
a) Put my phone into download mode with power and volume up.
1) The software never recognized my phone and I get no yellow com port. My window 7 PC does recognize my phone even in download mode.
2) If I do the same thing for my wife's phone which is still on GB then it sees the com port, but not on the phone with ICS installed already.
I tried to search and see if people have the same issue and did not find anything. For those who have already downgraded from ICS to EL29
can you please tell me which software you use and how you did it.
Thank you,
-Doan[/QUOTE
Glad you got it fixed ... when you roll back you will probably start getting an OTA update that will annoy the S--T out of you as it did me! Use this method it easy and make sure to hit thanks for him ...this was a life saver!!!! http://forum.xda-developers.com/showthread.php?t=
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!