Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
I recently used Odin to update to froyo 2.2 from my eclair 2.1, and it "pass"ed but now my phone goes into recovery mode. Boot screen then recovery, even when its off and begins charging goes straight to recovery.
At recovery it says:
"update media, please wait
E: Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E;copy_dbdata_media: Cant mount SDCARD:
your storage not prepared yet. please usee UI menu for format and reboot"
But UI menu doesnt work, doesnt let me select anything, and download mode wont load so Odin gets stuck at "Setup Connection".
Help?
Thanks!
- try different versions of Odin's this is the most common issue.
- Make sure your using the correct Eclair 2.1 files the ones by Eugene the unbrickable one.
Mostly, try a different ODIN, and the one that works, don't switch from it.
Odin is the only thing keeping my phone good as new, and i dont need any updates on that.
xrider is correct, I would recommend the 1.7 Odin. You can then Odin back by first flashing Eugenes Froyo that does not brick, then back to JFD2.1
you can get all you need in the Stickies
From there you can root and then flash away
good luck,
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Dark619Cloud said:
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Click to expand...
Click to collapse
Wait, if you can't get into Download mode, then how are you getting COM6 on ODIN?
I have no idea. Phone just sits in recovery, I plug in USB and it says
<ID:0/006> Added!!
But when I try flashing anything, it stays at SetupConnection.
When I WAS able to get into download mode, it was COM8.
Wait for more replies, idk the solution. Sorry
Maybe new version of odin?
I really appreciate your help though.
I think it's just bricked. The froyo which I had updated to was probably faulty, causing this to occur. I mean, even the recovery menu is messed up. Up and down are inverted, and power button does nothing. Phone doesn't show charging screen(well it does for a second then go straight to recovery).
I'll just call T-mobile tomorrow. I wouldn't get charged right? I tried updating to THEIR firmware, had they made it OTA this wouldn't have occurred, right?
The fact it sees com 6 or com8 or com 4 really isn't important, sometime mine say com2 sometimes it say 6......... this is unimportant.
Follow this ...this should work, the only other thing I can think of is to get into factory recovery and wipe, cache, and memory, go into advanced and wipe the dalvik, then back to Odin and perform the following:
1. Odin 1.3 or higher I use 1.7 but not real important
2. Have the original JFD Vibrant rom
3. You will need the .pit file (this is for mapping)
4. You will Eugene froyo that does not brick rom.
The order is as follows:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! You will have flashed back to the original software. From there, you can do anything !!!
Next root the phone if you are confused about this go to youtube and look up the video by unlocker.com they do a great job showing how it is done.
After all this you can now flash a new rom.
The reason he's getting a COM port without being in D/L mode is because of the secondary bootloader in the sbl.bin. You may just be able to flash JI6.tar without a pit file and get past the Setup Connection
Whoa, nice feedback.
Downloading both Eugenes "Froyo that does not brick" and the JI6.tar.
Will try both methods and reedit my post.
Thanks a lot.
I can't press "Thanks" more than 5 times a day...
UPDATE:
Eh still nothing...Odin gets stuck at SetupConnection.
I believe this will persist until I find a way into download mode. Odin recognizes phone, hence the COM6, but doesn't fully connect since it does not go beyond SetupConnection. The recovery menu also isn't functioning properly, since I can't select anything.
Losing patience with this phone...
I called T-mobile and their sending in a new one.
Told them I was updating and this happened. Do you think I'll get charged?
Well, while you still got time with it...try a different version of ODIN and see if that works... 1.0, 1.3 or 1.7 dunno if there are more
All three versions get stuck at SetupConnection.
I looked into making a JIG, but I only have one USB cord and don't wanna go through the hassle. A JIG would put my phone into download mode, right? Even though it's not really bricked, just completely messed up.
Just now I was messing around with phone, and I got to a different screen!
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
(and some other stuff like that)
Then " POWER RESET OR UNKOWN UPLOAD MODE"
It shows up as COM7 in ODIN But still stuck at SetupCOnnection...grrr
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Dark619Cloud said:
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Click to expand...
Click to collapse
if you look at ODIN while you plug the phone in with that screen you'll notice it giving you a COM port....weird...but you can still ODIN the phone while on that screen. Flash back to JFD from there.
Yeah I know ODIN should recognize it, because it happened before and it did. But this time it's not. I tried different versions of ODIN as well.
tsk tsk ;P lol
u fixed it? or it remains broken ?
I did fix it, partially. It loaded and everything, but sound wasn't working, and volume rocker was inverted, I guess the rom I flashed was corrupted. So I did "adb reboot download" which took me to download mode to go back to JFD stock, and I did ODIN and everything but it stayed at SetupConnection again. I removed battery to put in download mode manually, and now it's bricked. PHONE /!\ PC. PC doesn't recognize it, and I tried every combo to get into download mode.
So no, it's not fixed.
Now that I have your attention, after a series of mistakes, I am stuck in recovery with a rom that won't flash, an sd card that won't mount and cwm recovery so I don't think I can use adb to move files. Also, no nandroids (learn from my mistakes children!)
I'm not used to samsung phones so I don't know if it is trying to flash the rom from internal memory or not but under mounts it says unmount /mnt/sdcard so I think that means its trying to flash from internal memory which I don't think is possible.
EDIT: Wait, now I just have the boot screen no recovery... HELP!
I see Sprint as your provider....is this to deal with a T-mobile Vibrant? Just asking...
Read about ODIN. It will get you right back to where you need to be.
http://forum.xda-developers.com/showthread.php?t=821625
Yes its a tmo vibrant (its my friends phone, luckily im bigger than him)
So after a couple hours of searching, I can get the phone into download mode, I have the right odin and software to go to stock, and supposedly the right drivers, but when I plug the phone in to get to download mode, my computer recognizes it, it goes into download mode, but odin doesn't see the phone(a box is supposed to go yellow?). The only thing I can think of is that I have the wrong drivers but my computer sees it just fine...
I think it's the phone not letting the computer get to it. I'm almost positive I have the right drivers but when I plug in the phone in download mode nothing happens in odin. Anyone have any ideas? Any help would be greatly appreciated.
Well, If you can get into recovery without CWM that is better Try the holding down the vol-up/down and hold the start/on button at the same time if it blinks on then off then on then off then release all buttons if that works you should see the recovery menu, if you have the rom in your internal sd card, then you can install by choosing install from sd card then choose select file next menu.
If not you may need to use
Get Odin going (version 1.7or newer) have the usb plugged into the computer not the phone remove the battery and this time only hold the vol up/down at the same time and then plug in the usb. That will get you into recovery and you can odin back or install from there.
READ the NOOB guide by S15274N in the General section sticky. It has a complete play by play on how to do this.
Good luck
Yea I currently have odin 1.7 with I assume the right drivers (ive never had the phone plugged in to this computer while operational) and I do exactly that to get the phone in download mode and odin never sees it. The computer dings and recognizes it (thats how im installing the drivers) but not odin.
Remove the battery, put back in
Open odin
Plug usb into pc, not phone
Go to download mode
Plug usb to phone
Com 3 or 5 connected?
And be positive you have the right odin
If you can get into clockworkmod you should be fine. Just select install from SD and scroll to the zip file of the rom. Give it time to reboot say 5 to 10 minutes. While that's working get the newer version of Odin 1.8??? If the Tom fails in clockwork then do a battery pull. Start Odin. Plug USB into phone only. Hold both volume up and down. While holding plug USB into computer.
I'll go to the computer in a sec and see if I can find a link for latest Odin.
Sent from my GT-I9000 using XDA App
Steps 1 through 4 but odin doesn't respond to the phone being plugged in.
If it makes a difference, to get to download mode, I have to boot into recovery, go to 'ULF Lagfix features' and select reboot into download mode. It also will go into download mode if I hold the volume buttons and then plug in the phone.
I really dont see what I'm doing wrong thats why I started a thread.
I have odin 1.7 ill go try to find 1.8?
Wait, why can't you just reboot? Did I miss something?
Um all the phone can do is go to recovery, and download mode, I have a rom on the phone that won't flash, after a little research, i'm pretty sure the md5 checksum of that rom is bad, therefore won't flash. Im not a samsung guy, is it possible to flash a rom from internal memory? Could I just push a rom through adb? All I have is recovery though and im pretty sure that doesn't support adb. I do have the option to mount usb mass storage though.This is why i'm using odin as a last resort because im used to htc phones this is my friends sammy.
Try this version of Odin...http://www.mediafire.com/file/z7e8fg365znsfpn/Odin3 v1.81.exe
Nope nothing. Damn could it be that I have the wrong files, but that wouldn't change the fact that odin isn't seeing my phone. Does odin take an extraordinary long time to find the phone or something because nothing happens when I plug in in download mode? BTW thanks for the help its nice to see some support
Also I'm not clear as to where your at exactly. When you flashed the rom did it reboot to the Vibrant screen or give you a message in clockwork that it failed. If it booted to the vibrant screen did you give it at least 5 minutes or more to boot (it can take awhile for the initial boot.)
Either way the newer Odin version should recognize the phone. I know I had problems with the older versions.
Yea I put the rom on let it sit for 15 min, came back changed the language then gave it a reboot to let it settle back in. It reset again on the reboot. After about another 30 min of messing with it, im like screw it lets go to another rom that I already had on the sd card, I booted into recovery, to find that it wasnt seeing the sd card. I then restarted (in norwegian) and put a new rom on the phone. (On my mac it recognized the sd card and the internal storage so I put it on both in case) I then went to flash this new different rom through recovery which failed. The new rom flash deleted the old rom but never flashed the new one, leaving me with recovery. After hours of trying to figure out if I can adb push a new rom into recovery, I decided to try odin. After installing drivers and finding all the stock files, im now at this point where odin wont see the phone. Thats just about the whole story give or take.
Edit: The only problem with your rom was that it reset the language every time I turned it on and that it lost my sd card because it was the wrong kernel. I'm now trying to flash a different rom, in an attempt to fix the sd card, but it failed for whatever reason, and has left me with nothing.
TheSilverStig said:
Yea I put the rom on let it sit for 15 min, came back changed the language then gave it a reboot to let it settle back in. It reset again on the reboot. After about another 30 min of messing with it, im like screw it lets go to another rom that I already had on the sd card, I booted into recovery, to find that it wasnt seeing the sd card. I then restarted (in norwegian) and put a new rom on the phone. (On my mac it recognized the sd card and the internal storage so I put it on both in case) I then went to flash this new different rom through recovery which failed. The new rom flash deleted the old rom but never flashed the new one, leaving me with recovery. After hours of trying to figure out if I can adb push a new rom into recovery, I decided to try odin. After installing drivers and finding all the stock files, im now at this point where odin wont see the phone. Thats just about the whole story give or take.
Click to expand...
Click to collapse
Okay got it now...First, did you try the newer Odin that I posted? Second are you able to ADB push to the internal still. If you can do either of these then go here..http://forum.xda-developers.com/showthread.php?t=870480 if doing ADB the get any of the .zip files, push to phone and flash. If able to use Odin then get any of the .tar files. Go into Odin UNCHECK repartition and only load the .tar file into PDA and click start.
Seems that there is a problem going backwards from 2.2.1 to 2.2
Hope this helps.
Yes the new Odin is the one I just tried and it's still not working. Also, when I try to start adb it says no such file or directory. I can only get into recovery and I dont think adb works from recovery. I guess what im trying to say is that my sd card won't mount, I can only flash from internal memory, but I cant add or remove from the internal memory because I don't have a rom to boot into. Also, for whatever reason, odin won't find my phone. Sounds grim unless I can try odin on a different computer (maybe that would make a difference) or I can adb push files to my internal storage from recovery.
Do you still have the my rom on there and have you tried to reflash it?
If not try that and then put one of the kernels from the last link on your phone and flash that first then flash the rom you are trying to get to. I am assuming that you are not trying to flash to the CM7 rom because that has a few steps just to get ready to flash.
EDIT; If you are able to reflash SimplyGalaxy2.3 let me know and we can go from there to get you back to where you want. Also which rom are you trying to flash to.
Hi guys:
So I have made so mistakes with this phone. When I got it I thought it was a Samsung Galaxy S 4G...
1. Rooted it using SuperOnClickRoot
2. Almost bricked it triyng to install a CFW done for SGS4G.
Then I realized that it was not a SGS4G and came here looking for some information...
I did that: Return to stock JFD (2.1) using that guide:
http://rootzwiki.com/showthread.php?t=702&p=11409&viewfull=1
And now I am a little more happier because the phone turns on, now the recovery works... But... When it get turn on it boot loop endlessly.
I tried so many times to do the same thing and I don't have a chance to get it fixed. Tried to move an update.zip to the external sd card without luck, I was triying to install ClockworkRecoveryMod.
So now I come here... The phone is boot looping and when Its turning on a lot of line with colors appear...
I know this have solution, just I want to know how to approach it.
Thanks for reading!
Redo the flash back to stock But this time 1st go into recovery and delete the cache then go into the advanced and delete the dalvik.
Then shutdown the phone and re open but this time you want to be in download mode (hold down the volume down only (or could just be the up only)) and on button at the same time to get you there.
Then hook up the phone to your comp after you have Odin up and then reflash stock
Then root> then flash whatever you want from there
good luck
oka1 said:
Redo the flash back to stock But this time 1st go into recovery and delete the cache then go into the advanced and delete the dalvik.
Then shutdown the phone and re open but this time you want to be in download mode (hold down the volume down only (or could just be the up only)) and on button at the same time to get you there.
Then hook up the phone to your comp after you have Odin up and then reflash stock
Then root> then flash whatever you want from there
good luck
Click to expand...
Click to collapse
I just have stock recovery... I don't have Advance button...
I have done it in Download Mode, then connected to Odin (PC), box turn yellow saying COM4 and then selected PDA and PIT file in the guide and hit START.
Everything seems to run fine on ODIN and finalize saying PASS but the phone continue doing the problems I have said in my first post.
Hello, I was trying to reset my tab completely and I wiped EVERYTHING. I have CWM version 6.0.1.0, My tab gets stuck on Samsung logo screen. It can go into recovery but nothing else. I was told that the reason it won't boot is because I deleted the rom and there is no rom for it to go to. When I try to mount it, it doesn't show up...I've tried to install CWM 6.0.4.6 zip from external SD but installation gets aborted. PLEASE HELP I NEED MY TAB BACK ! Also it shows charging when it's turned completely off...
thatechteen said:
Hello, I was trying to reset my tab completely and I wiped EVERYTHING. I have CWM version 6.0.1.0, My tab gets stuck on Samsung logo screen. It can go into recovery but nothing else. I was told that the reason it won't boot is because I deleted the rom and there is no rom for it to go to. When I try to mount it, it doesn't show up...I've tried to install CWM 6.0.4.6 zip from external SD but installation gets aborted. PLEASE HELP I NEED MY TAB BACK ! Also it shows charging when it's turned completely off...
Click to expand...
Click to collapse
When you say mount it do you mean trying to send the files over through ADB or just mounting the SD card or putting it into download mode?
If its the ADB issue, try to put your tablet into download mode by using the volume key and power button, then download odin and its stock firmware and flash it using odin. Your tablet should restore to factory defaults using that method
If its the SD card then use the method above as it sounds like recovery may have lost it a bit
If you can not put the phone into download mode (which i doubt is the issue you may want to think about a USB jig as they sometimes get past those issues but from your description I doubt its a hard brick as it gets to the logo
2 things you can try!
thatechteen said:
Hello, I was trying to reset my tab completely and I wiped EVERYTHING. I have CWM version 6.0.1.0, My tab gets stuck on Samsung logo screen. It can go into recovery but nothing else. I was told that the reason it won't boot is because I deleted the rom and there is no rom for it to go to. When I try to mount it, it doesn't show up...I've tried to install CWM 6.0.4.6 zip from external SD but installation gets aborted. PLEASE HELP I NEED MY TAB BACK ! Also it shows charging when it's turned completely off...
Click to expand...
Click to collapse
I really new to this, i mean writing to help people, so don't flock me.
First, you say your device still have the recharging lights on when shut down, it tells me it's not only a software error, but some short circuit has happend.
Have you tried a hardreset? search google for your model if you doesn't know how.
From what i can read you still have the CWM Recovery, so download Android-SDK and try flashing the recovery from ADB (Found in platform tools.
Last but most tricky, if nothing helps, you' have to disassemble your device and temporary disable the battery, them press and hold the start button down for 5 sec to remove the poweroverload, reassemble again and try ASB adain, you can't reinstall the recovery directly from the SD
Regards Sc0rpio