Earlier today, I was running the ComRom GB 0.21 version. I decided I'd like to try some other roms, so I ODIN'd back to ED01 (atlas PIT, repartition checked)
From there, I re-insert the battery, and allow the phone to fully boot. I get the kernel and ROM I'm attempting to install (Glitch V11.1 and the OMFGB nightly build).
Pull the battery, ODIN the cwr-3_30_ALL_Fixed recovery. Boot into recovery. Wipe Data, Cache, Dalvik.
Flash the kernel, then the rom. Reboot. I get a boot loop with a 'failed to mount' error (it flashes by very quickly each time, hard to see exactly what it is).
So, I ODIN back to stock again, and try just flashing the rom ( I also repeat the ODIN back to stock, flash again with a different rom (fascinatemtd 11.1))
It says that the ROM flashes, however, on reboot, it goes right back to stock. Not sure what additonal info I need to provide or where to look for it, but I can poke around ADB for anything anyone thinks might be helpful.
Thanks!
EDIT: Seems to be really borked now. Attempting to go back to Stock causes the phone to boot straight into the stock recovery, doesn't even get back to the stock ROM. I've got coverage through Verizon, at this point I assume I'm looking at a replacement.
EDIT2: Ok, Heimdall seemed to get me back going stock. I must have screwed up something with a version of CWM and the scripting differences.
Related
I rooted my Vibrant yesterday, first timer, and everything went smoothly. I used the Classic way, had no problems. I got ROM Manager, to flash ROMs of course (I've gotten pretty impatient with Samsung and my Froyo) and I decided to partition the SD because I thought it would be a good idea. I did not know that it would partition the INTERNAL SD and brick my phone. After countless hours of Odin, rereading the instructions on this thread, trying to get it back to stock, I managed to get it running Eugene's Unofficial TMO Froyo Image. I am able to boot [Froyo] totally fine, but then when I try to revert back to build JFD or J16, I get the same black screen with only the capacative buttons on. My question is, is there any other possible way to fix this? I've tried almost every single method I've come across, read so many threads, and I've been unable to get back to stock. I've even created an elaborate scheme to walk into T-Mo to tell them I dropped my phone (playing the technologically disabled customer, of course) and asking for a replacement. I apologize for so much text, but I felt that explaining myself might work. Ideas would be much appreciated
With Odin -
Use this 512.pit
and this JI6.tar
These will take you to bone stock 2.1.
Thanks Drew, but I've tried that countless times and all I end up with is a black screen and lit up capacitive buttons. I want to go back to stock because for some reason, Eugene's version of Froyo doesn't allow me to install apps because the supposed, "internal memory" is full. Plus, going back to stock will allow me to redo everything from the beginning.
make sure you flash a 2.1 compatible kernel 1st before downgrading from 2.2 to 2.1..
Try flashing "Eugene's Froyo that doesn't brick" on odin then flash JFD/JI6 whichever you wanna go back to..
WARNING: Flashing Froyo that doesnt brick will wipe internal SD..
Good luck..
$0.02, why not just flash the rom you want over the stock 2.2?
just factory reset, wipe partitions, wipe dalvik cache, fix permissions ALL in CWM
Then flash ROM of choice.. Clean flash.
Can you link that file for me please?
Also, I just factory reset, and I'm still unable to getapps from the market ,so flashing from 2.2 would be impossible. For app space, it says I have 0.00 B
Had same issue, didn't want to go back to stock though . Look for a post with mbr check sum error, quick walk through
Really? I looked it up, but i don't remember getting that error.message.
Here's the story:
I was on the latest build of CM7.
I made a backup in orange recovery.
I decided to flash the glitch low-leakage kernel.
It crashed, as I was expecting (I was just trying it out).
So I 3-buttoned into blue recovery, and attempted to just flash the high-leakage kernel.
I did, but then it just stayed on the "Glitch" bootup screen and didn't go past it.
So I attempted a restore to the backup I made; the restore failed, saying it couldn't mount /system, /datadata, or /cache... but not before deleting my previous boot image (-.-).
So I then attempted a clean install of CM7 (factory reset, dalvik cache wipe)
Same problem with the bootup screen.
I've been unable to solve it... any help would be very much appreciated.
I would recommend following the steps in this thread (http://forum.xda-developers.com/showthread.php?t=1124391) and going completely back to stock with the atlas.pit file and making sure that works before reflashing cm7. If you can't even boot after returning to stock, you've got a real problem, but I don't think that would be the case (you probably got your kernels screwed up somewhere, which stock should fix). If stock works fine, upgrade to cm7 as normal.
It worked... partially. I got back to stock, but data doesn't work. Brought it to a verizon store and they're shipping me a shiny new fascinate as we speak . Perhaps I should rename the title of this thread, how to get yourself a brand new fascinate? lol
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?
In short, I have a US Galaxy 4.0 Player, and have been enjoying it immensely, I've messed around with a few roms and kernels, and thought I'd try out the newest version of Han's Ethereal rom, version 2.1, with the TerraSilent 1.3.5 kernel. I heard it would take a long time to boot the first time, between 10 and 15 minutes, and that it would appear like it's bootlooping when it actually is not. Unfortunately, it ha been doing this for close to an hour now, making me think there actually is a problem. Has anyone ever experienced this huge amount of boot up time before?
(Also, I changed the filesystem to EXT4, as per Han's instructions, but I heard going back into CWM under the TerraSilent 1.3.5 messes with that, would it have anything to do with it?)
The filesystem mix up could definitely be the issue. You're best just flashing and booting. If possible, just stick to RFS. I think EXT4 just makes things too messy.
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Nnn Noob said:
Your not alone on this one. I didn't change the file system, installed the same rom w/ the same kernel, and it's still looping
Click to expand...
Click to collapse
I have put a new version (2.2) that should fix the bootlooping issues (or at least help them). How many apps to each of you have? Sometimes you have to pull the battery to get it to finish booting up properly. The EXT4 filesystem should have nothing to do with it bootlooping on the bootlogo, if that was an issue, it should be looping on the bootloader (the splash screen you see before it starts booting).
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
silentdoh said:
Interesting, because once I went back to stock with the RFS filesystem and reflashed the same rom, it went just fine, booted in just over a minute. When I was trying to boot before, I had perhaps a couple dozen apps, so I thought that was unlikely to be the cause. But yeah, did the whole deal with the battery pull/reboot a couple times and still no luck. But once I went back to stock before I flashed it was no problem. I'm going to be flashing 2.2 soon, when I didn't mess with the filesystem, if everything goes smoothly, then I think that might be our culprit.
Click to expand...
Click to collapse
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Am I bootlooping?
hanthesolo said:
I have found out that if you wipe cache/dalvik, sometimes it will get stuck in a bootloop. If you head into recovery after that happens, and wipe cache/dalvik from there (again if need be), then hit fix permissions (might be necessary), it should boot just fine. I would also hold off until 1.3, as I am releasing it today, and it is finally stable.
Click to expand...
Click to collapse
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Fixed?
thirdeye73 said:
I downloaded the latest (v2.4) Ethereal ROM and flashed it, and I think I may have gotten myself into a boot loop. Either that or I'm just impatient.
I'm currently running Klin's Klassic R5, rooted. Never messed with the file system.
Here's what I did:
1) Reboot to Recovery. Wipe cache and Dalvik.
2) Reboot to Download, flash the tar file with Odin. (Did not check PIT). All threads completed.
3) Device rebooted, I get Samsung logo (with Steve's Kernel icon at the bottom), then it displays "ANDROID" and the screen sleeps, and occasionally comes back on for a few seconds. This continues for close to an hour.
4) I found this thread. Pulled battery, wiped cache and Dalvik again, fixed permissions, rebooted.
5) Same results as #3.
I did make a nandroid backup before starting this. Should I restore it and re-flash?
Thanks,
Scott
Click to expand...
Click to collapse
I am back up and running. Flashed TerraSilent kernel and got my device back up. I tried restoring from my nandroid backup and that made my bootloop worse--left me in a samsung logo bootloop. I'd love to know why the nandroid restore didn't work, if anyone has any ideas what I might've done wrong.
Tried flashing Ethereal again, no problems this time. Only weird thing is Holo Launcher kept force closing, had to uninstall it.
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
spiff72 said:
I recently had an issue with my Note 2 when I went to flash (yet another) ROM. I tried to run the "Wipe Data/Factory reset" from within CWMR (Touch), and it would lock up/freeze during the format /data portion of the wipe. It would eventually just reboot itself back into recovery mode.
I eventually got to a point where I tried flashing a TW4.3 (rooted) stock ROM, but it was flaking out because obviously the data partition never did get properly wiped (lots of FC's, etc after it finished booting). I tried to do a factory wipe from WITHIN the booted OS. This took me a the android with the spinning blue "heart" and pseudo-progress bar. It then just stayed on this screen for 3-5 minutes and then rebooted back to the screen over and over.
I eventually gave up and ODIN'ed it back to the a stock, unrooted state (but I chose NOT to go to the latest 4.3 release so I could still possibly unlock again).
For some reason, the stock recovery doesn't have any issues formatting the /data partition now. I actually went back to stock thinking I might have to file a warranty claim on the phone (and I could right now, since it appears to be fully stock in all the various places you might look for tampering).
I am still concerned, however, that there is a corruption present in the /data partition and I would like to know if there is a way to test for it. Do I need to re-root just to test it?
Click to expand...
Click to collapse
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
icedventimocha said:
I had this issue as well at one point, my phone actually soft bricked. What you need to do is use the pit file thru odin, flash any firmware in odin EXCEPT THE NEW OTA. Then you need to unlock again using the proper version of CASUAL for the base in which you relocked.
Sent from my Galaxy Note II
Click to expand...
Click to collapse
Thanks...
I actually went through the whole revert to stock with ODIN (but I used the PDA button/file). Was this the wrong approach? It sounds like I ended up at the same point as you...
And of course I couldn't leave it alone last night and unlocked and rooted with Casual last night. So far no issues with recovery data wipes.
I would like to understand what the problem was! Is it hardware, or a flash gone wrong?