Yesterday, I started having problems on CM9 with my touchscreen not responding (couldn't unlock my phone, capacitive buttons still worked). Neither rebooting nor factory reset helped, so I figured I would Odin back to stock JFD and see if that would help.
Fired up Odin, loaded the PIT and JFD tar, selected repartition, flash finished successfully and then... nothing. My phone would boot to the Vibrant screen and sit there; can't even get into recovery (download mode still works fine). Tried messing around with different files (JDF, JI6, KB5, Eugene's Froyo) with no joy.
Decided on a whim to try flashing the boot.img through Heimdall and behold, I can now get to recovery! However, attempting to flash a ROM does not work; my phone will continually boot into recovery no matter what I flash (cm7.2, cm9, ICS Passion).
TL;DR: Odin to stock = phone stuck at Vibrant screen; flash cm9 boot.img = only boot to recovery
I've never run into a problem like this from flashing or using Odin before. Any ideas on how to fix this?
1) Did you try Odining again after the boot.img flash?
2) Try heimdalling with the files. Unzip the tar and add the partitions for each file in the Flash tab.
Just tried using Heimdall to do the full flash (de-compressed the JFD.tar file) and it's still a no go. And yes, I had tried using Odin after flashing the boot.img. I also thought I might be able to recover by nandroid backup from stock, but that didn't work (got a boot recover error)
Can you get at dmesg with adb shell?
Code:
adb shell dmesg
I cannot connect through adb when I flash stock, but when I use the CM9 boot.img I get the following from dmesg, see attached
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
whatiznt said:
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
Click to expand...
Click to collapse
Download mode does work while you have CM9 installed. And there's no option to boot to download from CWM recovery afaik.
whatiznt said:
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
Click to expand...
Click to collapse
I can get into download mode just fine from CM9, but screwed up my phone when attempting to Odin back to stock. Also, I tries flashing CM7.2 a few time without success. Good thought, though; it's saved me before.
If it helps, when I flash cm7, the boot logo changes, it just continues to boot into recovery. Might it have to do with cm needing mtd whereas I've flashed back to bml? Is there any way to force mtd formatting from the cm kernel?
Can you get to JFD and get it to boot up completely? I think that you should do that first to make sure your partitions are as they should first. Then once you do that, I suggest flashing a simple CM7.1 stable and get that to boot you completely. If at any point something goes haywire, we will have a better chance at diagnosis and able to rule out some things here and there.
Codes to check your partitions either through ADB or terminal app.
Code:
Su
Df busybox -h
If you need ANY files like CM7 or bootloaders or a GB bootloader enhanced JFD package PM me and ill send them to you. Won't be until later on tonight though.
Woodrube said:
Can you get to JFD and get it to boot up completely? I think that you should do that first to make sure your partitions are as they should first. Then once you do that, I suggest flashing a simple CM7.1 stable and get that to boot you completely. If at any point something goes haywire, we will have a better chance at diagnosis and able to rule out some things here and there.
Codes to check your partitions either through ADB or terminal app.
Code:
Su
Df busybox -h
If you need ANY files like CM7 or bootloaders or a GB bootloader enhanced JFD package PM me and ill send them to you. Won't be until later on tonight though.
Click to expand...
Click to collapse
Unfortunately, I cannot get into any form of stock (even recovery). If I use a CM kernel, it then will boot into recovery, and only recovery. I was on stock bootloader, but I flashed it again this morning, just to be sure.
Here's the output from my df (I believe you meant 'busybox df -h'...)
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 173016 32 172984 0% /dev
/dev/block/mtdblock3 81920 2528 79392 3% /cache
/dev/block/mtdblock2 192000 138676 53324 72% /system
/dev/block/mtdblock6 176128 4864 171264 3% /datadata
/dev/block/mmcblk0p1 14086752 99936 13986816 1% /sdcard
/dev/block/mmcblk0p2 1935192 1555788 379404 80% /data
Yes, you are correct about the code. Sorry about that. I was on the bus on my way home from work and mistyped.
What I think that you need to do is Odin back JFD and let it boot up. It will have the Froyo Bl's and stock recovery. From what I am reading, you are trying to run a "Stock" ROM wiht a CM9 kernel and that can't happen. The kernels are not cross-OS compatible. We want to get you booted up to a running ROM without messing with boot.imgs or somehow corrrupting your data.
Here is what I would do. Odin to JFD (not a 2.2 "stock") and then get it to boot up. Then flash CM7 and get it to boot up, again without messing with CWR or boot.imgs. Then we can go from there. After that we can go to an ICS variant.
From what I can see, your /data partition is still in tact, which means that you have NOT been hit with the Encryption Bug. This is good, but I suspect that if you keep messing with the boot.imgs, different versions of CWR or mis-matching kernels to ROMs, then you are flirting with disaster. First things first. Get to full Stock 2.1 and then go from there.
Woodrube said:
Yes, you are correct about the code. Sorry about that. I was on the bus on my way home from work and mistyped.
What I think that you need to do is Odin back JFD and let it boot up. It will have the Froyo Bl's and stock recovery. From what I am reading, you are trying to run a "Stock" ROM wiht a CM9 kernel and that can't happen. The kernels are not cross-OS compatible. We want to get you booted up to a running ROM without messing with boot.imgs or somehow corrrupting your data.
Here is what I would do. Odin to JFD (not a 2.2 "stock") and then get it to boot up. Then flash CM7 and get it to boot up, again without messing with CWR or boot.imgs. Then we can go from there. After that we can go to an ICS variant.
From what I can see, your /data partition is still in tact, which means that you have NOT been hit with the Encryption Bug. This is good, but I suspect that if you keep messing with the boot.imgs, different versions of CWR or mis-matching kernels to ROMs, then you are flirting with disaster. First things first. Get to full Stock 2.1 and then go from there.
Click to expand...
Click to collapse
He can't get stock to boot though.
Ok then. I thought that I had read that he was flashing a CM7 ROM with a CM9 kernel. There are two similar threads going on about something like this and I might have mixed up some of the posts.
I'll work on the other guy for the time being and check in here every once in awhile. Thanks FE!
Well, good news! I stopped by T-Mobile and they were (somehow) able to get my phone to boot! The first guy looked at it and couldn't get anything done and couldn't help me much since my phone's out of warranty, but another employee picked it up and got it working; said she "just pushed buttons" until it started, mainly did a "master reset" until it continued booting. Tried flashing CM7 and it worked. Think I might try going back to stock to see if I run into the issue again, but kinda don't want to risk it.
By the way, FaultException, while I (kind of) have your attention, have you had anyone else report issues with their touchscreen all of a sudden not responding in CM9? It seemed to happen rarely for me until right before I had this problem...
I've had something similar happen. Like the screen only wanting to go on dim and maybe one time it couldn't be touched. A reboot should clear it up though.
Sent from my SGH-T959 using xda premium
Download mode doesn't work on my vibrant? Tried hundreds of times from CM9.
Sent from my iPad using Tapatalk HD
whatiznt said:
Download mode doesn't work on my vibrant? Tried hundreds of times from CM9.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
How are you trying? Powered off + Hold volume keys + Plug in USB?
FaultException said:
How are you trying? Powered off + Hold volume keys + Plug in USB?
Click to expand...
Click to collapse
Every single method, not once working.
- From my iPad!
whatiznt said:
Every single method, not once working.
- From my iPad!
Click to expand...
Click to collapse
Well adb reboot download doesn't work. Plugging it in while holding both volume keys while it's off works for me.
Related
So I went to Odin my phone back to stock JI6 in Odin and I used the tar and pit file and select re-partition to wipe everything. Everything went fine and it rebooted, but now it brings me to the Recovery menu and says:
e:Can't mount /dev/block/st110 (Invalid argument"
E:copy_dbdata_media:Can't mount DBDATE:
copy default media content failed.
I've tried to reboot into download mode via the keys, and through adb, but I can't get there to install the OS...
Any help?
Thanks!
sano614 said:
So I went to Odin my phone back to stock JI6 in Odin and I used the tar and pit file and select re-partition to wipe everything. Everything went fine and it rebooted, but now it brings me to the Recovery menu and says:
e:Can't mount /dev/block/st110 (Invalid argument"
E:copy_dbdata_media:Can't mount DBDATE:
copy default media content failed.
I've tried to reboot into download mode via the keys, and through adb, but I can't get there to install the OS...
Any help?
Thanks!
Click to expand...
Click to collapse
1.) Make sure you are using something that is NOT 'Odin3 1.0' the best versions are 'Odin3 1.3 & Odin3 1.7' IMO
2.) Make sure you are using JFD Stock to odin back.
Master™ said:
1.) Make sure you are using something that is NOT 'Odin3 1.0' the best versions are 'Odin3 1.3 & Odin3 1.7' IMO
2.) Make sure you are using JFD Stock to odin back.
Click to expand...
Click to collapse
I am using Odin3 v1.30.
But how am I going to get JI6 or even JFD on the phone? It won't start up, just keeps going to this menu where my only options are reboot system now, reinstall packages (does nothing) delete all user data and delete cache data..
sano614 said:
I am using Odin3 v1.30.
But how am I going to get JI6 or even JFD on the phone? It won't start up, just keeps going to this menu where my only options are reboot system now, reinstall packages (does nothing) delete all user data and delete cache data..
Click to expand...
Click to collapse
You don't reinstall packages.
Just use JFD that is the one that is most likely to work. Not all work for everyone.
JI6 doesn't work for me.
To use Odin, you go into download mode. You don't use recovery.
Master™ said:
You don't reinstall packages.
Just use JFD that is the one that is most likely to work. Not all work for everyone.
JI6 doesn't work for me.
To use Odin, you go into download mode. You don't use recovery.
Click to expand...
Click to collapse
That's the thing, I can't get into download... Neither the hardware buttons or adb will get me there.. I type adb reboot download, and it takes me to the menu with the above options I mentioned.
sano614 said:
That's the thing, I can't get into download... Neither the hardware buttons or adb will get me there.. I type adb reboot download, and it takes me to the menu with the above options I mentioned.
Click to expand...
Click to collapse
So you are hardware locked? The following MAY or MAY NOT work...
1.) Turn off your phone, remove battery/sim/micro SD
2.) Press & Hold the VOL UP+VOL DOWN
3.) Plug your phone into your computer (Keep holding those buttons)
4.) Download mode should pop up.
Master™ said:
So you are hardware locked? The following MAY or MAY NOT work...
1.) Turn off your phone, remove battery/sim/micro SD
2.) Press & Hold the VOL UP+VOL DOWN
3.) Plug your phone into your computer (Keep holding those buttons)
4.) Download mode should pop up.
Click to expand...
Click to collapse
I shouldn't be hardware locked, I flashed the file to get rid of the hardware lock before I used Odin earlier and was able to get into Recovery via the buttons (didn't try download though.. DOH!)
I was able to get into download mode now, though, and am flashing JI6 while JFD downloads (very slowly). JI6 finished and same error... Will wait for JFD to be done.
Thank you very much, Master. Merry Christmas.
I'm all set now. Thank you for all your help, Master.
how did you get the phone running again, i mean i can go to the download screen, but after any update I still recieve the same recovery screen with error.......... tried so many things none of them work, what to do?
jaiiscool said:
how did you get the phone running again, i mean i can go to the download screen, but after any update I still recieve the same recovery screen with error.......... tried so many things none of them work, what to do?
Click to expand...
Click to collapse
What are you trying to flash? I had to use Odin to flash JFD, not JI6 as that just kept sending me to that same recovery screen with the error.
sano614 said:
What are you trying to flash? I had to use Odin to flash JFD, not JI6 as that just kept sending me to that same recovery screen with the error.
Click to expand...
Click to collapse
I have a Galaxy S with this error, I am trying to flash the DDJP6 firmware with ODIN, I had checked the repartition by mistake and got this error, don't know what to do now.
Hello everyone, if your reading this you likely have the error mentioned above. Recently, a friend of mine came to me with this same problem. I looked long n hard and every link I found was broken. Every odin file I needed was removed. I even noticed that eugene kindly took down his odin to stock package...that was pretty cool of him At any rate, I still had eugenes odin to froyo zip luckily, I tried flashing this normaly thru odin and got the same error. What ended up working for my buddys phone was, using eugenes odin package and putting a check in "re-format" in odin. That fixed it right up. If your having the same errors, please feel free to contact me. Id be happy to link you or do anything else in power to help. This worked like a champ! Good luck. If this helped ya, please feel free to hit my thanks button. I only have 3!
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
EricDET said:
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
Click to expand...
Click to collapse
Nope, nothing to do with bootloaders. It has to do with jfd being the only realeased odin package that contains dbdata.rfs of the .tar. None of the other ones do.
Sent from my SGH-T959 using XDA App
I went to partition my sd card through rom manager, I have all the files on my computer (all different versions since November). It went into recovery, mounted sd, was formatting and next thing I knew it is stuck on the overstocked logo. I am running Trigger 3.0 & flashed in overstocked (through rom manager) and themed with a splash of color with other modifications.
The thing is, is that I also have the vibrant galaxy s 4g and was using the 16gb sd for both until my 32 came in and realized, not a good idea. So until the 32 came in I decided to just work on this phone but wanted to get any signs of the 4g off this phone so was cleaning it up and now here I am.....
Read the threads here and have gotten into the download mode, with nothing to download but it goes right back to the "overstocked" logo or bouncing to the "vibrant" logo and battery sign.
Any suggestions would be greatly appreciated.
EricDET said:
JFD is the only one that carries all the necessary files for the check-repartition ODIN install...
Something to do with flashing both bootloaders.
Click to expand...
Click to collapse
I used Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit. I checked re-partition and left F. reset time and auto reboot checked. This solved the e:Can't mount /dev/block/st110 error. Idk if this will work for everyone, but using the exact same files but without re-partition checked left the same error, checking it fixed the error. Just thought Id share my results because that can be a very frustrating error which in my friends case caused fc's all over the place, while booting up and a bunch of apps as well.
Deleted... if you want a good guide that I made:
Check it out here.
I did ODIN back to Eclair 2.1 last night and was planning to start rooting and flashing roms. Would you suggest me to NOT do it and if so, what should be the plan of action in such cases?
Go for it.. you are not going to hurt anything. Please report back if the guide works as it should, or if CWR does not flash. You will know because when you go to re install packages it will reboot... where it would normally bring you back to the stock recovery and you would press re install packages again.
This is very weird, because i rooted and flashed a new rom/kernel using your guide with my vibrant and it turned out fine.
I tried the exact same thing with my gf's vibrant this morning and got the issue of just rebooting of the phone instead of going into the red Clockwork recovery.
I'm going to try this new update.zip and see if it makes any difference and will post again if it results in a different outcome.
Same thing used to happen to me. Your EDIT (unsure about file because I don't need to try it but deleting old update.zip files) works. For some reason, when I would JFD back it would double the size of the update.zip file. I have one that is 633kb on my computer so i have to delete the doubled one, drag and drop the one on my computer, reinstall packages blah blah blah.....
I have a question.
If I use a different version of the ODIN than the one you have on your guideline. 1.85 vs 1.70 does it make a difference? Can I use the 1.85 version?
No difference
I tried that! I tried to Flash a new rom using ROM MANAGER. When all was done, I came back on Stock Eclair and I can't get into Recovery Mode by pressing Vol Up + Down + Power button anymore! However, I did manage to get into Recovery Mode using CWR and then selected to apply zip updates. My WiFi interent wasn't working before but it seems to be working now. I can't find the option to turn on my 3G internet though!
zee.syed said:
I tried that! I tried to Flash a new rom using ROM MANAGER. When all was done, I came back on Stock Eclair and I can't get into Recovery Mode by pressing Vol Up + Down + Power button anymore! However, I did manage to get into Recovery Mode using CWR and then selected to apply zip updates. My WiFi interent wasn't working before but it seems to be working now. I can't find the option to turn on my 3G internet though!
Click to expand...
Click to collapse
Sounds like you need to odin to jfd
Sent from my SGH-T959 using XDA Premium App
ok, so I dont know why but this is how i got it working.
On step 5 of the Back to ODIN guide, it states "Now, You could power off, but you do not need to. Hold in both volume buttons and power for a good bit. Do not have the phone plugged into a usb. Once you see VIBRANT, release all buttons."
At this stage, I turned my phone off and then went into stock recovery to reinstall package. So instead of going into stock recovery from when the phone was on, I went into it from when the phone was off. This allowed me to go into CWM recovery.
Give this a shot and maybe it will work for those who are having this issue too too.
^ which update.zip did you use?
If the latter, that makes sense.
Can anyone try the update.zip below?
http://www.multiupload.com/PS7ILU1WTX
s15274n said:
^ which update.zip did you use?
If the latter, that makes sense.
Click to expand...
Click to collapse
I used the one that's on the first post of this topic.
I tried both the old step of booting into recovery from when the phone's on and that didn't work. So I turned off the phone and then went into recovery to reinstall pkg, then it worked.
laylovj said:
Can anyone try the update.zip below?
http://www.multiupload.com/PS7ILU1WTX
Click to expand...
Click to collapse
That's the one that I posted already...
i had to do this a few weeks ago because my update.zip was messed up it would just reboot when i tried to install packages im not sure what happened to it though
I had this problem myself too! I went back to stock JFD twice, once when coming from CM7 back to froyo and another when coming from Asgard to Froyo (this time).
The first time I use a guide from this forum (don't feel like looking for it atm), it was a guide that I used when I first got the phone to root and stuff... it was pretty long. Fortunately, this time I found this thread and the update.zip works, so basically it's way easier this time around. You might have to install twice for it to work... I'll try to explain what I did.
1. Flash back to stock JFD.
2. Download update zip and put on SD card.
3. Power off phone
4. Start in recovery mode.
5. Reinstall packages.
6. Power on phone.
7. Repeat steps 3-5 and when you reinstall packages the second time it should automatically restart into green recovery.
This the way to do it and work always
Flash update1.zip from attachment after you rename it as update.zip
then you will have root.
Then reboot phone in recovery and flash update2.zip after you rename it update.zip and delete the previous one.
http://www.multiupload.com/8ZKCZWI5U7
The 1.72mb update.zip in the OP works when re-installing pkgs. Even when I somehow lost root with other update.zip files, this one still worked for me without ODINing to JFD
the possible fix mentioned worked for me.
Coming back from GB, followed your guide. When I reinstalled packages it rebooted to stock the first time, reinstalled again and went into CWM. Didn't have to mess with the update.zip.
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
vindication84 said:
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
Click to expand...
Click to collapse
Okay, I've never had this issue personally, nor have I read of anyone else having a similar issue. However, despite the lack of CWR, you can still restore the device back to stock via Odin. There is a guide on the usage of Odin that can be found here. Download links to the program along with the required .pit and .tar files can also be found in said guide. Once you've got the device restored, you can go through the process of installing CyanogenMod... But, keep in mind that the installation process is going to vary slightly depending on what version of CyanogenMod you wish to install. Are you trying to install CyanogenMod 7 (Gingerbread), 9 (Ice Cream Sandwich), 10 (Jellybean 4.1), or 10.1 (Jellybean 4.2)?
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
vindication84 said:
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
Click to expand...
Click to collapse
You could use Heimdall, an alternative to Odin that is compatible with OS X. You can download it here.
Now, in regards to the process of installing CM10, you could refer to this video... http://forum.xda-developers.com/showthread.php?t=1812882. Hopefully you won't get that weird CWR issue this time around. Let me know how it goes. :fingers-crossed:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
vindication84 said:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
Click to expand...
Click to collapse
Hmm... Perhaps this post might be of some help? Sorry, but I don't own a Mac, nor have I ever personally used Heimdall... So I've never had that issue before. However, a little Google searching uncovered a bunch of threads discussing this exact error. Perhaps a little digging may uncover your answer? Link. Again, best of luck dude.
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
danvsullivan said:
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
Click to expand...
Click to collapse
I already have the update.zip on the phone. I can get into the stock recovery and flash it (it says "replacing recovery with Clockwork" and everything), but every time I attempt to flash it, the phone reboots to the stock recovery. I can't add files to the internal SD because the only options are Reboot System Now, Reinstall Packages, Delete All User Data, and Delete Cache Data"
One-Click doesn't see the phone either. I'm starting to get really worried. Is there some sort of driver or something I need to have installed on the system?
SOLVED!
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Glad to hear the good news!
Hope this time you'll be able to update the phone seamlessly, and your friend can enjoy a newly updated Vibrant. If you ever have any questions, don't hesitate to PM me. I'll try my best to help you out.
danvsullivan said:
Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683).
Click to expand...
Click to collapse
Although I had heard of Bay_wolf's AIO Vibrant Toolbox, which is also a one-click software (but only compatible w/Windows), I had never heard of "Heimdal One-Click". This is good to know about, and I've added the program to the The Official XDA Vibrant Bible Thread. I learn something new every day. Thanks!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Great news! You can follow the instructions I wrote out to install a custom ROM from stock. Just put all the files on the internal SD, wipe everything and flash update.zip and then the ROM and gapps.
If you have questions, you may PM me as well.
Good luck!
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem