Related
I had rooted my phone previously running 2.1 and yesterday decided to try cm7. (I've flashed many G1 roms but none for Captivate)
Sorry this is quite long but wanted to give as much detail as possible
I was reading and watching the guides. Installed rom manager and flashed ClockworkMod Recovery 2.5.1.0
Rebooted the phone and tried to see if I can get into download mode by holding vol up + down and plugging the USB cable.
Once it booted tried to copy some other roms (zips) to the phone but the USB wasn't working on windows for some reason so rebooted in Linux. Phone mounted at first (for about a minute) but something happen and I lost the mount. I unplugged/plugged the usb cable but wasn't able see the phone as a drive even with fdisk.
So I ftped to the phone:
3buttonFix.zip
captivate-efsbackup.zip
cm7-captivate-initial-20110304.zip
speedmod-kernel-i897-k13c-500hz-CWM.zip
Installed 3buttonFix.zip (should let me enter download mode) from recovery, rebooted but still couldn't get in download mode.
Installed speedmod-kernel-i897-k13c-500hz-CWM.zip from recovery. Not sure if I had to do anything special like reformat the filesystem with the new kernel?
After reboot the phone gets stuck on Galaxy S sgh-i897 screen. Got back in recovery and installed captivate-efsbackup.zip and cm7-captivate-initial-20110304.zip
The cm7-captivate-initial-20110304.zip fails when trying to write the modem
'assert failed: write_raw_image("/tmp/modem.bin", "radio")'
I plugged the phone into another computer at that point and was able to get into "Download mode" for the first time. Odin didn't recognize the phone though. Download mode is very flaky. It starts sometimes, sometimes it doesn't (battery charger starts) even on the same port with the same cable. I have tried installing captivate drivers and/or kies on 7 different systems (5 laptops 2 desktops) but Odin never recognizes the phone and windows trows out a "USB Device Not Recognized" msg
I think my usb is not working properly but the guides how to recover assume working Download mode with Odin. Any suggestions on what to do for that? Or I guess I can download a different rom and/or kernel on my sdcard than mount the sdcard through recovery and install that way?
Any advise is appreciated as I'm not very familiar with the kernel and rom differences for captivate
Well you messed up on the instructions but that is a separate point.
I went through your post quickly so if I am saying something you grave tried I apologize
What drivers are you installing
Have you tried multiple ports
Are you using oem cord
Have you restarted your computer
Have you ever used odin before
CM7
I have used the following drivers:
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe (just the usb modem driver)
2 different versions of samsung kies which include usb drivers (don't have the software versions handy but I can get them if that will help)
Ports:
Multiple computer and multiple ports. Will try few more options
Cables:
Used 3 different usb cables. 1 of them is from a BB phone. 1 of the other 2 is the one which came with the captivate (not 100% sure though)
Reboots:
4 of the 7 computers I tried on were rebooted. One version of kies requires this anyhow.
Odin:
Haven't used Odin at all. I think when the phone gets connected and odin recognizes it one of the top left blocks changes color right ? I tried to flash even when it didn't (just to make sure I wasn't missing something) and saw 0 successful / 0 failed
Do you have android sdk installed on any of the computers?
CM7
So many red flags that something wasn't right with your phone and you still tried to flash it? I just don't get it.
@Miami_Son: Yeah but i'm too thick headed - living dangerously but yeah you're right.
@mcord11758: I have android sdk installed on my linux build at home. I'll put it on a windows system at work and see if it can see the phone. Anything in particular I should do / look out for ?
At least you've got a good attitude.
I think if you have kies installed it conflicts with the samsung drivers odin uses. Try uninstalling them and flash odin.
Sent from my i897
Edit damn swype
1tontomato said:
I think if you have kies installed it conflicts with the samsung drivers odin uses. Try uninstalling them and flash odin.
Sent from my i897
Edit damn swype
Click to expand...
Click to collapse
Try this first
Sdk to install updated drivers if this fails
CM7
I've done almost the exact same thing...having the same issues. Phone would not connect to computer. Other captivates connect fine. The phone is now stuck on a boot screen and I can put it into download mode but Odin or the computer will not detect it at all. I don't think I can get into recovery mode, nor can I get into a rom...pretty much just download mode or a boot screen.
@1tontomato: Tried uninstall kies, reboot, install samsung usb drivers, reboot still don't see the phone connected in odin
@mcord11758 The sdk is trying to download the repository directly and I'm behidn a proxy server at work. I'll update tonight, it will be most likely very late by the time I get home.
@kwhee07 Yeah sux to see a download mode but not being able to download. I can get at least into recovery so I guess I can at least flash something that way. The ports really make difference, I've seen many would just charge the phone and some will get your phone into download mode at least. Try a different pc and cable if you can.
I have the sdk...I've tried about everything else I can find. Is there a possible method of fixing this via the SDK? I feel like if I could make the computer force [odins] data out the usb port, it would work, the phone would be in download mode awaiting data....but I cant get odin to see it
There is a package you can install in sdk for usb drivers. Dl it
Open odin
Get into dl mode
Unknown device pops up
Click on it
choose custom drivers
Navigate to c drive/program files/android/extras/google add ons/usb click ok (the path may be slightly different) the computer should try to install the correct drivers
If it works odin should now recognize your device. If not I got nothing
CM7
Got the USB drivers from the SDK and tried to force them when it sees an unknown device, but I get "The specified location does not contain information about your hardware"
I tried to force it to use the samsung drivers also but without success.
Is it possible to just download a rom or kernel and update my current state? So that the phone at least boots. I can install stuff through recovery. Download mode is nice and everything but I'm giving up on it, don't have any more ideas to try
I have been trying to see data on my sdcard from ClockworkMod Recovery 2.5.1.0 I go to
Mounts and Storage -> mount /mnt/sdcard
Install *.zip from sdcard -> choose zip from sdcard
I don't see /mnt at all I try and go under sd/ but it says No files found.
bestivo said:
I have been trying to see data on my sdcard from ClockworkMod Recovery 2.5.1.0 I go to
Mounts and Storage -> mount /mnt/sdcard
Install *.zip from sdcard -> choose zip from sdcard
I don't see /mnt at all I try and go under sd/ but it says No files found.
Click to expand...
Click to collapse
Under mounts and storage do you see the option for mount usb this might be able to force your computer to see it as a removable drive. If out does you should be able to copy another rom to the sd and flash. This may or may not work for you because you might still need to repartition which you only do with odin. Take this advise with extreme caution I really think you need odin If you do decide to flash another rom, use cognition because Dg's includes the fixed boot.bin. Probably because so many people use the one click and kill their button combos and don't know it. Other devs don't include it in their roms, because it's dangerous to over write something that doesn't need to be overwritten. Good luck
Sent from my Fusion 1.8 SAMSUNG-SGH-I897
I tried already the usb mount option from recovery at home and now at work also on few different systems/ports including a linux machine. I don't see the drive connected.
My only option left is to get somehow the sdcard mounted and install a rom from there. Or maybe just repartitioning/changing the filesystem might fix the getting stuck problem.
I ended up bringing my phone back to att, and they said that the 1010 batch was under product advisory..they exchanged my phone with almost no questions asked.
Now i have a 1008 and am running CM7
Finishing up the story in case it might help somebody in the feature.
I called AT&T to get my phone replaced and it turns out it has liquid dmg. There's a little white sticky that turns red when there's liquid dmg. Mine was pink but wasn't wait so no warranty for me. Turns out most of the time people get liquid dmg is if they leave the phone in the bathroom or close to the kitchen's sink, which is kinda bs but whatever.
I've tried few more times. Tried even on a Mac and on a Linux system (using http://forum.xda-developers.com/showthread.php?t=755265 )
I was about to give up and go seek one of the 'professional rooters' but last thing I tried was to use an 'air duster' and clean the usb port on my phone. After that Odin was able to see my phone. The connection was dropping on/off but it successfully finished a flash.
Not sure if I should even try to put another rom or the official froyo update but at least for now I'm up and running
Thanks all
Hello!
Here I am, floating through the Samsung waters
I've stuck on one part, of course; my phone is bricked, computer reads it only half way and ODIN doesn't even show any signs of life and I have no possibility to rewrite firmware up there.
What is it all about?
I've flashed the ICS up there through stock recovery before I saw on xda that new cwm or some other new recovery should be written. First, it gives me the tpm/sideload error every time I try to install new recovery, I can't even do the factory reset, anything. I can enter the recovery normally, it's just that I can't install anything. I've tried with several roms, some of them pass through normally, but the device doesn't want to boot, and when it is turning on, it just shows samsung logo and nothing else.
When I enter the recovery, it shows me this error:
Appling Muti-CSC
E: failed to mount /system (invalid argument)
and when I try to install something from that recovery it shows me this:
E: error in /tpm/sideload/package.zip
I must remark that the packages I downloaded are 100% valid, the card is regularly formated.
After that, I've tried with ODIN. I enter the download mode, but my device is recognized as modem mode. I've installed the drivers, I have good cable, I've done every little thing they mention on xda. So, let's say that my device is properly installed. But it is in modem mode only when I turn on download mode.
When I turn it to recovery mode, then it recognizes this:
-samsung usb CDC composite device (that is under the USB controllers and it is normally installed.)
-CDC abstract control model (ACM)
-CDC ACM data
-CDC Obex data
-CDC object exchange
These last ones are not properly installed, but when I send it to look for it in folder where the drivers of the device are unpacked, it says they are not found.
Is there a possibility that my computer did not manage to install all the drivers, considering that I installed them after bricking, and not before?
Is there a possibility that I manage to manually force it to recognize drivers and install them?
Is there any way that I can make it to connect with ODIN and write him official GB ROM?
Please help me, I wouldn't want to take it to service!
Using what version of cwm
Sent from my GT-S5570 using XDA
AndroidUser99 said:
Using what version of cwm
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
none. big problem is that before I upgraded to new recovery i made mistake and i flash new custom ROM.
Hello!
I am a complete noobie when it comes to rooting androids/installing new roms and so on but I for the life of me cannot get my head around this and I keep running into the same problem no matter which way I try.
I attained this phone from a Chinese (and funnily enough bought the phone in China too) friend of mine after she decided to buy herself an Iphone. Before she gave it to me she factory reset it and it came to me stock:
Model Number: GT-I9220
Android Version: 2.3.6
Baseband Version: N7000XXKJ6
Kernel version: 2.6.35.7-N7000XXKKA-CL726566
Build number: ANZHI.COM.AX918
So to start with one of the issues is that I cannot seem to get Windows to pick up my phone as a USB device no matter what I try. I've tried downloading the latest USB drivers from the Samsung Website, installing KIES to manage the device but nothing seems to work it simply will not pick it up as a USB device. I've tried multiple computers too so it would seem to me that there is something wrong with the phone, perhaps she damaged the connector port on it, it does however charge with no problems when connected via USB. This of course stops me from using ODIN or any forms of rooting that require it to be connected through USB. I've also followed the steps on the phone to tell it to connect via USB in the Wireless menu under "USB Utilities" and under the Applications menu for USB development support.
So that aside I was glad to see that there were other options for rooting/installing a new ROM but again I seem to run into issues that I can't explain.
First off, I struggle to find the correct rom for the kernel of my phone anywhere and when I did manage to find it, it was hosted on the HotFile website which has been taken down because of legal issues.
Second is, I've tried the other methods like the "ExynosAbuse" which tells me that my version doesn't need to be rooted and when I try simply installing a new rom (seeing as it seems I do not need to root my device) I keep getting the follow error:
E: failed to verify the whole-file signature
E: signature verification failed
I get these errors for EVERYTHING that I try to install through rebooting my phone into recovery mode and "installing update from external SD." Currently the only method I have for getting the files across to my phone from my PC is through blue tooth and then manually moving them onto the SD card.
The above errors also happen when I try to install the "Clockwork Recovery Mod" by unzipping the file and running it whilst actually logged into the phone and telling it to do a recovery installation.
So basically I am at a loss as to how I can install a new custom rom on my phone, so far everything I have tried just doesn't work.
Perhaps I'm just too green and missing some fundamental step, but I've been reading/googling now for the last 2 days and it just doesn't look hopeful.
Anyone out there able to shed a little more light into this for me?
Thanks!
You have a Gingerbread version of recovery and it does not flash zip file from recovery as you already tried. You will need to update to ICS or above to use that method of rooting. Unfortunately the imo the only way is to get the USB port working so you can either update the rom or install a recovery using Odin unless some other member has to add.
Have you tried a different USB cable?
nokiamodeln91 said:
You have a Gingerbread version of recovery and it does not flash zip file from recovery as you already tried. You will need to update to ICS or above to use that method of rooting. Unfortunately the imo the only way is to get the USB port working so you can either update the rom or install a recovery using Odin unless some other member has to add.
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yeah I've tried several different USB cables but still no luck.
So basically I'm screwed if I cannot get the USB to function?
Anyone got any ideas or can I pretty much just discard the phone if I can't get it to connect via USB?
Hate to post again but I'm sorta desperate, I need to know if there is something that I can with the phone or not.
Thanks!
When you try to connect to PC, if there is some action triggered by windows asking for driver somethingvthen it is driver problem. If there is no action from window then usb cable or port. You can also try to check in window device manager.
May want to try to clean usb port or look for a technician who can replace the port.
Btw, there seems to be a temporary cwm.zip which will flash and then it help you to flash proper kernel or rom. That cwm.zip is dangerous if you are using ics or jb rom. But GB rom should be fine. That is all I can think of.
Sent from my phone.
I don't think the temp cwm.zip will also be accepted by the GB recovery and will come as signature failed.
Thanks for the responses, I think the port is damaged so how because it just won't even respond in windows but it does however charge fine.
Anyways I'll look at getting a replacement port on it!
Thanks again!
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try another usb port and/or another usb cable. Also make sure that nothing with kies is runnung in background if you happens to have that installed.
When you connect with adb, also take a look on your phone screen if it asks for authorization to connect.
You got both download and recovery so problem is with connection/drivers.
zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try this :
If you have an external sdcard in your s3 mini then :
1. remove it and put it into a other phone
2. download a ROM and move the ROM what you downloaded to your external sdcard
3. Put the external sdcard back to your s3 mini
4. Go to recovery and choose "install from external sdcard"
5. And intstall the ROM
6. Done! You have a OS again.
It's very easy and if you don't have a external sdcard then you have a big problem bro
shelves mmerese
xXPR0T0TYPEXx said:
1. remove it and put it into a other phone
Click to expand...
Click to collapse
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.
MarisPiper said:
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.
Click to expand...
Click to collapse
Yeah i did this, but no luck at all.
Finally i change the usb driver, installed Kies again and voilá! Odin picked up the phone and flash were on .
Thanks to all.
Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.
MarisPiper said:
Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.
Click to expand...
Click to collapse
due to windows updates this should be expected that certain third party software like the drivers would need updates
so that leaves two choices
either keep your stuff up to date
or
get left behind and drowned in problems
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.
I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers