So my vibrant won't boot up. I've tried odining it back to stock, and no matter what I do, it will almost get to the galaxy S screen (freezes as it is forming the S). Download mode and recovery mode both work.
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Sk3tchy said:
Are you able to "Reinstall Packages" from recovery or does that fail?
Did you check re-partition when converting to stock?
You may have corrupted your internal SD
Click to expand...
Click to collapse
The reinstall packages fails. It says: "can't open /sdcard/update.zip" (no such file or directory).
Woodrube said:
Pull the battery, boot into recovery and wipe factory reset, wipe cache, and advanced->wipe Dalvik. The reboot. Will take longer b/c it has to rebuild Dalvik but it should work out fine. I had the same thing happen the two nights ago coming off ICS.
Don't forger you won't have CWM and it isn't in the market for 2.1 anymore. You can download it from my signature. Put Update.zip in internal and hit reinstall packages twice (that is if you want flash or restore).
Click to expand...
Click to collapse
I don't have the option of wiping the Dalvik in recovery. I think its because it went back to the default "Android system recovery <2e>"
I tried wiping everything, but when it boots, it goes to the vibrant screen, then to the tmobile screen (the boot sound works), but then, the screen turns black and it goes back to the vibrant screen again (and it just keeps looping).
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
cashmundy said:
Maybe try ka7 or kb5 instead of jfd? Investigate /mnt/efs and the copies in /sdcard/backup? Don't know much about eds, might be worth a look. Reflash SBL for good measure?
Click to expand...
Click to collapse
So I flashed ka7, and it gets past the S logo now, but then it turns black and now it says "Kernel Panic" upload mode:
RST_STAT=0x4
PMIC_IRQ1=0x0
PMIC_IRQ2=0x0
PMIC_IRQ3=0x0
PMIC_IRQ4=0x0
PMIC_STATUS1=0x40
PMIC_STATUS2=0x2C
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Woodrube said:
Go to the dev section and download the Toolbox. It is stickied. It has drivers, Odin and the Pit/Tar files to get you back to stock. Get back into download mode and re-run Odin with those files.
Don't forget that you don't have to see the DL mode on your screen as long as the COM box is yellow in Odin.
Also check out this thread.
Click to expand...
Click to collapse
I tried using the toolbox and reflashing the stock rom, but it just gets to the t-mobile "stick together" screen, then screen turn black, then it goes to the battery charging screen.
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
cashmundy said:
If you're doing Odin right, with a good rom and pit file, and still have trouble, I guess you could flash the SBL. I had a rom flash (via zipfile) do something unknown which made it nearly impossible to get into download mode. Once I did, I flashed the SBL and I was fine. No idea what happened. I even had a nandroid backup, not a restore, hose my phone once. When the other Phone Gods turn against you, Odin is your friend.
Click to expand...
Click to collapse
But I can get into download mode. And which sbl should I flash?
Probably the closest-to-stock Froyo SBL you can find.
I'm using a GB SBL from this thread, and he has Froyo also:
http://forum.xda-developers.com/showthread.php?t=1117990
I got stuck in this loop a few months back flashing back to stock from CM7 when Odin froze.
I could get to Download Mode and Stock recovery but had the same error when attempting to "Reinstall Packages" from recovery. The internal SD partition had corrupted.
I flashed Eugene_2E_JK2_Froyo with Odin, which fixed the Internal SD.
If you follow the write up on unbricking when you have the little triangle and phone error on your screen it will get you out of this one.
Your bootloaders are not the issue here. 2e Recovery isn't seeing the Internal SD Card and that it what is causing the hangup on boot.
Yeah, probably just flashing a decent kernel would fix you up, but unless you can find an Odin kernel file, you need to do the whole rom.
BTW, with Linux, you can use
tar -tf <rom file> if you want to see what's in a rom.
You can download the Odin flashable Overstock Kernel which contains the red recovery and flash it. That would give you the ability to format the internal SD and then Mount it to your PC through recovery and copy a Rom over to flash.
Otherwise the Unbrickable Froyo I mentioned before will also work.
The only thing you can do when stuck in a boot-loop, if the previous suggestions don't work, is to just reflash it. You can flash back to stock easily using Heimdall One-Click. http://forum.xda-developers.com/showthread.php?t=1278683
We're missing some info here. What ROM were you using before you flashed back to stock? Did you use a pit file in addition to the pda file in ODIN?
If you were using an ICS (android 4.0.x), flashing back to stock and didn't use a stock pit in addition to stock pda, it would definetly be giving you problems. ICS uses a different partition scheme then does stock (which is on android 2.1). The pit file tells odin how to partition your phone.If you're flashing from Froyo, then this should not be relevant as it uses same partition scheme as stock.
Related
So I followed the instructions and ReadMe and flashed everything at once on Heimdall Frontend. Now the phone is stuck on the Samsung loading screen, and trying to get into recovery is no good as it just sits on the samsung screen. The only thing I did not flash was the PIT as when I selected it it turned the start gray.
What is causing this??
Running Windows 7 on computer, and trying to flash the dl01 package that was opened into individual files.
Anybody know?
Posting this in two different sections was necessary?
If it's a question, which this clearly is, it goes in the Fascinate Q&A.
I understand it's in the Q&A now...but now there are two of the same thread.
I tried to delete, can someone else delete the other one. I didnt notice the Q and A section at the time.
tried reflashing seperate parts such as kernel factoryfs recovery but still hangs on samsung screen. Cannot get into recovery as well I have tried holding both volumes and power and then releasing power but still sits on samsung logo.
Why not just use download mode and use Odin?
when I try odin it hangs on recovery, I have tried now doing it through odin and it will hang on recovery when doing the complete package and hang on factoryffs when doing it individually.
Flashed clockwork recovery now it keeps booting and rebooting and saying movi_check start and then it goes through wiping data cache and everything fails.
Formating FOTA
fail
Formating DAta
fail
formating cache
fail
formating dbata
fail
When I flash the other recovery it just hangs on the samsung logo screen...
David1po said:
Flashed clockwork recovery now it keeps booting and rebooting and saying movi_check start and then it goes through wiping data cache and everything fails.
Formating FOTA
fail
Formating DAta
fail
formating cache
fail
formating dbata
fail
Click to expand...
Click to collapse
These are the steps to restore to stock from any ROM/Kernel, Rooted/Unrooted, etc...
Download: T959UVJFD.tar (PDA), Odin3.rar, s1_odin_20100512.rar (PIT) and samsung drivers
Linky for downloads: http://forum.xda-developers.com/showthread.php?t=734475&page=59
Extract: s1_odin_20100512.rar pit file
Extract ODIN3.rar
Open Odin3_v1.0.exe
connect USB to phone
Go to Download mode. The phone should show up in ODIN. If not reboot and try download mode again. Select PDA and PIT file. I selected re-partition checkbox. Click start button.
My phone had Froyo 2.2 custom Rom (Trigger) and Kernel Overstock, was rooted and had clockwork. Now I have Eclair 2.1 update1 with all stock apps and icons.
--
http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&sort=a&sortMode=q
network0 said:
These are the steps to restore to stock from any ROM/Kernel, Rooted/Unrooted, etc...
Download: T959UVJFD.tar (PDA), Odin3.rar, s1_odin_20100512.rar (PIT) and samsung drivers
Linky for downloads: http://forum.xda-developers.com/showthread.php?t=734475&page=59
Extract: s1_odin_20100512.rar pit file
Extract ODIN3.rar
Open Odin3_v1.0.exe
connect USB to phone
Go to Download mode. The phone should show up in ODIN. If not reboot and try download mode again. Select PDA and PIT file. I selected re-partition checkbox. Click start button.
My phone had Froyo 2.2 custom Rom (Trigger) and Kernel Overstock, was rooted and had clockwork. Now I have Eclair 2.1 update1 with all stock apps and icons.
--
http://files.androidspin.com/downloads.php?dir=androidspin/samsung/vibrant/&sort=a&sortMode=q
Click to expand...
Click to collapse
You should have noted that these instructions are for the Telus Fascinate only...
So, disclaimer. I'm an idiot today. Don't mind me.
So today I decided to go to jt's CM7 from ComRom 2.1 (non gingerbread)
Backed up everything, made a nandroid, wiped everything installed cwm 3.x.
Went and started to flash CM7. That didn't exactly like me too much as it went into a 45min long bootloop saying that it failed. No big deal. Nows the fun part. Rewiped everything, started to reinstall the ComRom. That didnt like me either, it says that it cannot mount Cache/recovery/log etc. So I thought. Okay, well I can always ODIN!
Ideas folks?
Thanks in advance.
Sorry about the bump/post, forgot to edit this one instead.
OK! Ignore above, used odin so now im on stock eb01 but still when i use odin to flash cwm 3.0.2.8x it still says it cannot open or mount cache/recovery/log and recovery/last_log.
At this point, I just want to get it so I can nandroid back to where i was on comrom.
Ideas?
What I did, ODIN the atlas2.2 and ebo1 Froyo package, boots up to stock fine no problem.
Attempted to flash CWM 3.0 in ODIN. flashes fine.
3 finger salute. doesnt boot, have to hold it for about a second then cwm just pops up saying it cant mount recovery.
Then I re ODINd eb01, deleted all voodoo, cwm, update.zip etc from sdcard.
re tried to flash cwm 3.0
same thing.
Completely lost haha
New ; odin's dl09, OTA'd up to current. What steps should I take next given my issues with CWM?
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
schu9120 said:
By deleting the file named clockworkmod on your sd card, you most likely deleted all of your nandroid backups. unless you backed up you sd card to your computer, im pretty sure they are gone. Im sorry. As far as the rest of your problems... I know a stock kernal will overwrite clockworkmod every reboot.
Click to expand...
Click to collapse
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
tkirane said:
I did back up everything, made sure of that haha. So I should try reflashing a kernal? or would that have been included in the ODIN package/ OTA updates I did?
Thanks
Click to expand...
Click to collapse
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
efan450 said:
there may have been a kernel in the ota updates, the problem us you need a non stock kernel..stock ones over write recovery in every boot
My suggestion....
odin eb01 with the atlas 2.2pit and repartition checked.
Fully boot after eb01 flash
Odin cwr 3-30-all and immediately three finger boot into cwr....wipe everything
Flash cm7 build 7/4 completely reboot
Use the power menu to access recovery...this time it will be cwr 4.x.x.x flash the
Cm7 build your want with no wiping, thats what works for me
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
tkirane said:
I believe I attempted that last night at home, I will definitely try again after I am out of work. Would you happen to have a link to download of cwr 3-30-all?
Also, would I be correct in the assumption that same steps would apply to ComRom installation.
Also too, I am currently on the ED04 non-rooted stock OTA. Do same rooting methods that I used way back on dl09 still apply?
Sorry for the multiple idiotic questions, just much different this time around do to the inability for CWM (either 2.5 or 3.0) to be able to locate/mount the cache/recovery/log.
Would that have to do with Root? thats my main concern is getting into CWM for it to say it cannot mount. After this point I have it reboot system and it does not boot up again. It boots into CWM immediately. So it is unable to bot back into the actual phone mode. So then I reflash dl09 or eb01 in ODIN and start over.
Click to expand...
Click to collapse
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
efan450 said:
rooting has no effect on wheather or not recovery (cwm) sticks, its the stock kernel that is overwriting it as soon as you boot. com rom 2.0 comes with a kernel in the flash so if you do this exactly you'll be on comrom rooted with recovery
The steps for going to com rom would be the same this method may be overkill but it should get you cleared up....you said you odin'd ebo1 and the atlas pit before in your previous post,so im going to assume you know how to properly get into download mode and what do, and not do in odin, so down load cwr 3-30-fix all here, and save it on your pc in your odin folder
http://forum.xda-developers.com/attachment.php?attachmentid=556634&d=1301538947
download com rom (ukb) 2.0 either from your phone or from your pc, connect your usb cord and move it to the root of your sd card.(ie.not in a folder)
pull the battery,and odin the ebo1 tar with the atlas 2.2 with repartition checked, when its done insert batt and boot fully.
when done pull batt, odin cwr 3-30-fix all, when done insert batt and right away hold volume up, down, and power and continue to hold until your see the red cwr screen.
wipe data(factory reset)/wipe cache/go to advanced and wipe dalvik
go to install zip from sd, and find the comrom ukb zip and select install...when its done select reboot and done...at this point your phone will look like its not doing anything and its important to be patient you will hear the voodoo lady talking to you and this is good, when your phone fully boots hit the power button and select recovery and at the recovery screen go to backup and restore and select nandroid backup and run it, when its done reboot and enjoy
if you want to go to ukb 2.1 just download the patch, boot into recovery and flash, no wipe needed.
as a side note the 3-30 file you odined will not be your recovery after this is complete because comrom comes with its own recovery, after you get on to this rom the recovery that came with it will be the one you see.
i used these same steps to go to cm7 but i have only had success by, odin cwr 3-30 fix all, wipe everything and then install build date 7/4 and reboot completely, and power menu to recovery and flash the 7/13 build.
Click to expand...
Click to collapse
I definitely know my way around odin and recovery haha thank you very much for the help. I'll try it out once I am out of work and let you know how it goes. I was doing just that only with cwr 3.0 not the fix all. so hopefully that does the trick. Hopefully I wont be seeing and mount cache errors.
So I did use the recovery-all last night to no avail, still says that it cannot mount certain items.
I have to three finger salute it, then let go after a while for it to boot to CWM, then it cannot mount cache:recovery/command and recovery/log and dev/block/st111
Also when trying to wipe data it cannot mount datadata
Then I do reboot system now and it reboots to CWM with same errors.
EDIT : Found an ODIN for EC01 ComRom 2.0
Going to try that out and see what happens.
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
tkirane said:
I'm an idiot. I realized I kept ODIN'ing pit with CWM, aka, BAD idea. All fixed and running.
Thanks everyone!
Click to expand...
Click to collapse
Lol glad to hear your up and running...I've had my share of idiotic moments and lucky our phones are pretty brick proof...and now we can add to the list that using a pit file and trying to odin cwr while it won't allow your phone to work..... you can still recover even from this with out perma-bricking!
Sent from my SCH-I500 using XDA App
I was using odin to flash a rom and I knocked it off my desk and unplugged it in the process. It will still get to the download screen for odin and have tried to odin roms but they fail to install. The error usually is it can not mount or wipe : DATA. I have odin'ed CWM and can boot to that. I have tried every thing I can think of.
Any suggestions?
ouch. you may be able to fix this via heimdall but I'm not sure. have you tried resetting it to factory settings? maybe something with repartitioning? of course, you'll have to do the research.
JJHunterx said:
I was using odin to flash a rom and I knocked it off my desk and unplugged it in the process. It will still get to the download screen for odin and have tried to odin roms but they fail to install. The error usually is it can not mount or wipe : DATA. I have odin'ed CWM and can boot to that. I have tried every thing I can think of.
Any suggestions?
Click to expand...
Click to collapse
Try to odin stock froyo with the PIT file and reformat checked. Might try it a few times if it fails the first. I got stuck on the modem once and it never went past that till I restarted it.
links as follows....
2.2 stock froyo (PDA BUTTON ONLY) - http://www1279.megaupload.com/files...d9dd20ca/CI500_VZW_EB01_FROYO_REL.tar.md5.tar
PIT file (PIT BUTTON) - http://download180.mediafire.com/09z19r6ojbwg/26xbh796jmwvwqb/atlas_v2.2.pit
Make sure your "reformat" box it checked.
Okay, as the thread title states and as I had searched for a Samsung Vibrant related thread about this issue I haven't found any. My issue as stands is when I try to perform a Factory Data Reset on my Samsung Vibrant t959VUVKD1, 2.2.1 Froyo, it only comes up with this set of words on the recovery screen.
-- Wiping data...
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Formatting DBDATA:...
Db data wipe Failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk;files, please wait
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:copy_data_default_apk:Can't mount DATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Click to expand...
Click to collapse
So, as one can see this is evidence of my attempt at rooting and using Clockworkmod Recovery.
What I used was SuperOneClick 2.2 and successfully rooted my phone but then I decided to unroot after finding out ClockworkMod Recovery wasn't able to create a backup on my phone, also, I used a 3e_recovery_installer batch file I found somewhere which managed to unlock my Android system recovery so I could get into Clockworkmod Recovery but ever since I unrooted and uninstalled Clockworkmod Recovery it won't allow me to perform a factory data reset. I was able to do it TWICE after unrooting my phone but now I can't perform the factory data reset and I do not understand why.
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Never used Odin or Toolbox before because I've never found a concrete tutorial on how to correctly flash/root my vibrant. I would like to flash but I just don't feel safe about it even though I had downloaded a supposedly stock rom of the UKVD1 rom for Vibrant.
nomadrider123 said:
Have you tried to odin back to stock or use the toolbox?
http://forum.xda-developers.com/showthread.php?t=954509
Click to expand...
Click to collapse
Erm, I used the Toolbox to use "Flash to Stock" and when Odin opened up I selected Pit.pit and it showed a yellow to green color on the first box and my phone turns off then nothing happens. What does this mean?
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Sugartibbs said:
1. When odin opens select pit
2.click the Pit.pit file after screen change and click open
3.You should be returned to odin main.
4. click pda
5.click pda file and click open.
6.you are returned to main odin.
7.set phone down, click start and do not unplugg
8 let it run till pass, and auto reboot
Click to expand...
Click to collapse
I did all that just now but now I'm stuck on a looping charging screen or a looping Samsung Vibrant screen. However, this isn't the same as the original T-Mobile screen and even so how do I get past the looping screen?
1. pull the battery
2. insert the battery
3.hold down volumeup/ volumedown buttons
4. insert the usb cable, you should enter download.
5 reset toolbox and select flash to stock, odin should appear,
My experience.
When you are facing boot loop, it's very hard to get in to download mode.
I tried button trick for download mode, but I failed.
So I used adb and tried to reboot into download mode by command.
I repeated it until I could get into the mode.
Anyway, download Toolbox and once u get into the mode,
try to go back to stock. That 'll fix everything.
I also know that the logo changed after I flashed back to stock.
I faced I9000 logo which wasn't before.
FYI: + the version will be eclair, and I couldn't get the official update.
Anyway good luck.
---------- Post added at 03:09 AM ---------- Previous post was at 03:02 AM ----------
If you never get into download mode.. Try to use JIG.
Another way is to disassembly your phone and do something.
I suggest you buy a JIG.
Problem is, I can easily get into Download mode by:
1. Remove USB Cable
2. Pull battery and re-insert
3. Plug in USB cable
4. Hold Volume - and +
And it's in Download mode
But I want to get the original Smasung Vibrant 2.2.1 UVKD1 Rom back on but it appears the provided files aren't it?
Btw, what is a Pit and and PDA file supposed to be, I'm a complete noob at this point.
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Sugartibbs said:
The pit and pda files in aio toolbox are the stock rom the vibrant is shipped with, if you want anythig else on it you have to download it and flash it through odin, rom manager, or cwm.
Click to expand...
Click to collapse
I see. But now when the phone starts up it shows a buncha dots in consecutive order to the Samsung Vibrant screen after I flashed to stock using the pit and pda files and it just loops continuously until I pull the battery. Is there anything that can be done to get past the looping?
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Woodrube said:
Does the pitcure look like a phone....!....computer? If so then you are softbricked and just get back in download mode and re-Odin, but make sure that when you Odin, you DO NOT have the repartition checked. Probably what happened.
If it is not the above, can you get into recovery? Can you now do a factory reset? Wipe cache, dalvik and reset usually clears the bootloop problem.
Click to expand...
Click to collapse
Unfortunately I can't get into recovery. I also Odin'd with the given Pit.pit and PDA.tar files with Repartition unchecked but that didn't change anything.
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Sugartibbs said:
I cant figure how you could be in a bootloop coming out of odin. Is the AIO you downloaded for vibrant. I think theres one for fascinate and captivate.
Click to expand...
Click to collapse
I used the AIO Toolbar for Vibrant as provided by the link by the person earlier. The loop just continues forever and ever until I remove the battery.
The three button method of entering recovery hasnt worked?
You mean hold Power and Vol + and -?
No, it doesn't work.
i am hesitant to advise anything, the fact that factory reset didnt work, and recovery has been removed is troubling. when i get a fail message when flashing to stock ive used eugenes froyo that does not brick. If all else fails you might google it and read the op. Its a pda file used by odin.
What I find strange is that download mode works perfectly fine but nothing else.
what I find strange is coming out of odin and looping, you should come out in recovery with an error message. a cannot mount data or bdata. storage not ready. Removing recovery may have removed more than was expected. check the op on eugenes froyo you have to get back to stock.
I know why it happened, it was caused by me as I wiped the factory reset without cleaning the cache. As every rom, kernel and Android version change configuration is unique.
Unfortunately, usually I'd boot into recovery and re-flash it there. But when I do, the CWM/recovery logo appears for a second and then continues to boot forever. Not in a boot loop, just stuck at boot. I've tried installing a different recovery, no change. It may be skipping that as it's stuck in first boot after a flash.
Odin3 will find my phone, but it doesn't seem to support zip files like CWM does.
Is there any way I can flash a rom, clean cache or anything, without the recovery?
Sorry for bolding my text, I know how tiresome some people find reading.
Odin recognizes. tar files not the zip files... Just download . tar file for your recovery and then flash it via Odin.. read a guide for that before doing that...
Sent from my GT-I9300
Download this: http://www.sammobile.com/firmwares/3/?download=26624 . Put the phone in Download mode, connect it via USB, add the firmware in the PDA section and hit start
kunal1540 said:
Odin recognizes. tar files not the zip files... Just download . tar file for your recovery and then flash it via Odin.. read a guide for that before doing that...
Click to expand...
Click to collapse
Unfortunately recovery doesn't always seem to work these days, I suspect it ignores recovery on first boot.
Andr3y29 said:
Download this: http://www.sammobile.com/firmwares/3/?download=26624 . Put the phone in Download mode, connect it via USB, add the firmware in the PDA section and hit start
Click to expand...
Click to collapse
Sweet as, it's unbricked now.
I had similar experience
Was on devil kernel, reformatted to f2fs all workng.
Tried dual boot, was in 2nd rom
The internal storage was showing no free space, checked and I was only using 3G of the 12
System was not happy
Dropped into recovery and formatted /intsd
Recovery rebooted automatically and would not do anything,
Reboot, entered recovery, rebooted, etc,etc
Dropped into download, Odin flashed cwm recovery,
Formatted partitions back to ext4, restored nandroid.
All back to normal....
Leaving f2fs alone for now