Here is what happened. Flashed voodoo lag fix, Didnt notice any difference after 3-4 days. Then tried to flash back to stock(eclare). Here is where im stuck at, it wouldnt boot up using the stock eclare, So I tried one of the tuts here that said to use eugene rom. I used the pit 52 file+ eugene rom. Flashed those using oden, phone boots up fine, but I now have the not enough space problem when attempting to dl apps from the app store. When I reboot my phone after I have tried to use the market, the market app disappears. Ive tried using other roms and nothing works.
Every time I flash a rom I get "data failed to whipe" on first reboot.
Find a ROM you want and in recovery wipe cache, dalvik cache, wipe data, format system in mounts and storage then flash the ROM and see if that clears things up.
sent from the depths of helly bean
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
BTW, what ROM were you running before?
sent from the depths of helly bean
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
Just saw this in another thread, it might help you.
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
sent from the depths of helly bean
samsgun357 said:
Find a ROM you want and in recovery wipe cache, dalvik cache, wipe data, format system in mounts and storage then flash the ROM and see if that clears things up.
sent from the depths of helly bean
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
BTW, what ROM were you running before?
sent from the depths of helly bean
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
Just saw this in another thread, it might help you.
The only rom that will boot up is
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
sent from the depths of helly bean
Click to expand...
Click to collapse
The only rom that will boot is "eugenes froyo that does not brick". All others boot to the vibrant/samsung screen then to black screen where only the bottom 4 buttons light up, but nothing happens.
I was on the stock eclare rom.
Its also saying there isnt a partition for app2SD. Any way to fix this?
Have you tried this tar? I use it instead of flashing to eclair as most of eugenes roms repartition...XDA search for a link to this... Eugene_2E_JK2_froyo.tar.
Sugartibbs said:
Have you tried this tar? I use it instead of flashing to eclair as most of eugenes roms repartition...XDA search for a link to this... Eugene_2E_JK2_froyo.tar.
Click to expand...
Click to collapse
Thats the one Ive been using, if there is a tut to fix the vibrant on here, Ive already tried it.
I dont think thats the one, the eugene I use is Eugene373_samsungS_froyo_pda.zip, and it wont reboot, it will take you to recovery with an error message. you pull the battery, enter download, then odin eclair. Ive used it for corrupted flashes that result in failed odin rewrites to stock. Search that pda and it will take to a 4share download.
Sugartibbs said:
I dont think thats the one, the eugene I use is Eugene373_samsungS_froyo_pda.zip, and it wont reboot, it will take you to recovery with an error message. you pull the battery, enter download, then odin eclair. Ive used it for corrupted flashes that result in failed odin rewrites to stock. Search that pda and it will take to a 4share download.
Click to expand...
Click to collapse
That worked perfectly. Thx
Related
Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Try sbf if you can't get back into bootstrap recovery.
Sent from my DROID X2 using Tapatalk
itskevin94 said:
Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Click to expand...
Click to collapse
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
EvilTim said:
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If you have a backup you can get to it with the stock recovery.
Travisdroidx2 said:
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
How do u get to a backup using stock recovery?
Travisdroidx2 said:
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
Really now?
That would be nice.
Sorry must be a noob mistake. I thought while I was in there to clear data/factory thought I also seen a spot to load zip from SD. Guess I was wrong you all know more than I do I have only been at it now for a couple of months
Pretty sure there is an option to apply update zip but my backups aren't named update and they aren't zips so that poses a problem __
I see I never tried I just figure that yo ucould get to it like you do with recovery app. I did get bootloop when flashing to 2.3.4 and thought I was going to have to sbf again. However starting up in backup recovery and clearing data and factory reset again fixed the issue. Eclipse went smooth and is looking good! Just concerned on my battery life as I need a strong battery for work.
Yes u will have to clear data/cache from stock almost every time u sbf. I know I have.
i sbf back to 2.3.3 and reflashed the script and worked perfectly. thanks for all your help!
I odined back to stock from cm7.1 and in stock recovery gives me a count mount dev/datadata (file exists). Any suggestions anyone?
Did you ODIN to JFD?
Sure you used the correct Tar and Pit?
Sure you did PDA and not Phone?
Did you check/tick the repartition box?
---------- Post added at 11:27 PM ---------- Previous post was at 11:22 PM ----------
Here's a good guide, with files. Just in case...
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
So my suggestion would be ODIN again
I used ji6 odin. Correct pit and used PDA partition not checked. Odin finished and phone rebooted into recovery and gave me the could not mount the dev/memblc0/datadata or something like that. I have odin'd at least twenty times already and never had this issue
Sent from my SGH-T959 using xda premium
I've never ODIN'd to JI6, so I don't know if checking repartition will help.
But I do know that coming from CM7 back to stock, ODINing to JFD, I DO check repartition. CM7 uses MTD Partition Table...it just seems like the right thing to do. I'm not sure if checking the box actually does anything different, I just know that I do it, and it works. (also, it's suggested in that guide above)
I've had such good luck with JFD, that's the only thing I can really recommend.
Jfd worked. Everything is good. Your link to that thread gave me some info that helped me. Thank you much!
Sent from my SGH-T959 using XDA App
Okay i cant seem to get this working!
and its getting to me..
i cant get into CWM
i flashed it with odin and i still cant get in it?
cj316x said:
Okay i cant seem to get this working!
and its getting to me..
i cant get into CWM
i flashed it with odin and i still cant get in it?
Click to expand...
Click to collapse
How are you trying to get to it? What Rom and kernel are you running ?
tsm res1.2, TKSGB 11-14, lag fix
laureanop said:
How are you trying to get to it? What Rom and kernel are you running ?
tsm res1.2, TKSGB 11-14, lag fix
Click to expand...
Click to collapse
well am in the red recovery now but it wont flash n e roms,
theres always an error whrn i try to install them.?
the phones boots up goes to a samsung galaxy cynogenmod boot screen
and the recovery appears, does something and boots and its just a loop?
cj316x said:
well am in the red recovery now but it wont flash n e roms,
theres always an error whrn i try to install them.?
the phones boots up goes to a samsung galaxy cynogenmod boot screen
and the recovery appears, does something and boots and its just a loop?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1212239
Follow this link oh how to install anything mtd based like cm7 or pool party. Please back up your SD card, I repeat back up your SD card and preferably you should erase and re format it before installing cm7
tsm res1.2, TKSGB 11-14, lag fix
I got the same problem. I never backed up and formatted my SD card, but the error persists. HOWEVER, when installing the MIUI rom, it does it's own recovery and that seems to KINDA work. I'd flash that rom just for the recovery alone but some post that you must go back to stock before switching roms. I have the same problem as you, you can get odin and do the CWM voodoo lagfix recovery, but that just gives me a bootloop too. I got it going somehow once, but it never was really working. Backups I would make were unable to be restored which in all my years i've never see clockworkmod do. I've never seen it unable to run commands like this and flash roms, restore backups, etc. So keep trying and I'll post it up once I figure it out too.. I'm experienced enough to know that something is amiss here and needs a fix.
---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------
I am going to do that guide, I think that has solved my problem, the cwm recovery and all that. THANKS BRO!
So basically to flash anything mtd use the blue recovery in Brownsuperman or droidstyle's posts and to flash anything TW use jt' s red 2. 5 recovery. Both are very reliable
Sent from my SCH-I500 using xda premium
laureanop said:
So basically to flash anything mtd use the blue recovery in Brownsuperman or droidstyle's posts and to flash anything TW use jt' s red 2. 5 recovery. Both are very reliable
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
^This man speaks the truth!
I have an thunderbolt that I was running bamf 3.0 (I think), I havent used it for a while so I gave it to a buddy. He took it and started playing with the bamf toolkit changing the font, ever since then it gets stuck at the HTC screen. I can still boot into recovery and everything even still flash roms through CWM, but no matter what it sticks at the white HTC screen, can the excellent XDA peeps help me through this?
Even after you wipe the system, cache, and dalvik you still get stuck? Try updating your clockwork, or switch to twrp 2.0 and see what you can accomplish. http://teamw.in/project/twrp2
Did u try clearing data/cache each 3 times then restore a nandroid back up?
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
If that does not help you need to do this http://forum.xda-developers.com/showthread.php?t=1310014
What's up guys, I'm running into an unusual issue here and could really use some guidance. I tried searching around, and the only solution I KNOW will work is to start from scratch, using odin to go back to stock, re-rooting, and then slowly trying to work my way back to where I was before the FUBAR.
So, I was recently using LiquidSmooth 2.9 and went to make the leap to 3.0. Flashed everything, got confirmation that it went through ok, and then I just got stuck at the Samsung Galaxy s4 screen, nothing happens after that. So, I went to restore from the backup that I took earlier and I got a failure to restore.
Not to worry, I figured, I'll just reinstall from the zips for 2.9 that I still had on my SD card. Well, I do that and everything seems to work fine with the flash, but now I'm STILL stuck at the Samsung Galaxy S4 boot screen and STILL, nothing happens after that.
Any suggestions on what to do here? Flash a new kernel? Am I stuck going the long route and having to Odin everything back to stock and then re-root, etc?.
samstheman42 said:
What's up guys, I'm running into an unusual issue here and could really use some guidance. I tried searching around, and the only solution I KNOW will work is to start from scratch, using odin to go back to stock, re-rooting, and then slowly trying to work my way back to where I was before the FUBAR.
So, I was recently using LiquidSmooth 2.9 and went to make the leap to 3.0. Flashed everything, got confirmation that it went through ok, and then I just got stuck at the Samsung Galaxy s4 screen, nothing happens after that. So, I went to restore from the backup that I took earlier and I got a failure to restore.
Not to worry, I figured, I'll just reinstall from the zips for 2.9 that I still had on my SD card. Well, I do that and everything seems to work fine with the flash, but now I'm STILL stuck at the Samsung Galaxy S4 boot screen and STILL, nothing happens after that.
Any suggestions on what to do here? Flash a new kernel? Am I stuck going the long route and having to Odin everything back to stock and then re-root, etc?.
Click to expand...
Click to collapse
Id download the latest liquid file again just in case that file was corrupt somehow.
That's usually been the problem lately from what I've been seeing. You really shouldn't have to Odin.
Also the kernel shouldn't matter but I always flash kts latest kernel with liquid but others don't and have no issues.
Grab that file again
Do a couple wipes in recovery
Flash away
Sent from my SCH-I545 using Tapatalk
---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------
Also what recovery are you using?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Id download the latest liquid file again just in case that file was corrupt somehow.
That's usually been the problem lately from what I've been seeing. You really shouldn't have to Odin.
Also the kernel shouldn't matter but I always flash kts latest kernel with liquid but others don't and have no issues.
Grab that file again
Do a couple wipes in recovery
Flash away
Sent from my SCH-I545 using Tapatalk
---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------
Also what recovery are you using?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.5.02
samstheman42 said:
Using TWRP 2.5.02
Click to expand...
Click to collapse
Well I've seen others either upgrading their twrp or going with some version of CWM but that's obviously up to you. I'd try to download the latest liquid, which is a unified build, and try it again first..
Sent from my SCH-I545 using Tapatalk