samsung fascinate dl09 radio, rom and 2.6.29.6 kernal i tryed to ryan lagfix it said to reboot i tried and now it stuck on samsung no matter what i try and it says
E:can't mount /dev/block/still
(invalid argument)
E:can't mount /dev/block/still
(invalid argument)
when i try to reboot i have tried to odin it and nothing should i get my motorola droid out cause i fried this samsung please help
Head over to the fascinate irc channel for real time help (irc.droid-life.com #fascinate). Ryan lagfix is outdated and has been known to brick phones. Hopefully that is not the case for you.
Sent from my Vanilla Froyo Fascinate
Take your phone back and buy John's phone.
i have tired to get on irc.droid-life.com and it said i have no permission
alusher said:
i have tired to get on irc.droid-life.com and it said i have no permission
Click to expand...
Click to collapse
Have you tried using ODIN to flash stock DL01/DJ05 or DL09 .tar's to restore to bone stock yet
i have tried dl09 and im downloading the stock dl01 bone stock
i used odin with dl01 v3 and it works thank you two guys for your help
Yeah... Don't use that lag fix. It is completely outdated, and you probably don't need it.
Related
i have a rooted sprint epic. I was on the viper rom and tried the ec05 update from clockworkmod v2.5.1.0 and it said failed, then i tried installing [ROM][ACS] SyndicateROM Frozen 1.1.0 (Takiya) : and it said complete, when i rebooted it was stuck on the samsung screen for 15 minutes. I tried a different rom and it keeps saying aborted. I tried doing a restore through clockworkmod and it gets stuck on restoing chache, lost and found. it just sits there and does nothing.
when clockwork opens up it saids E:cant open /cache/recovery/log
can someone help me as to what i should do to get my phone running again?
gt2776 said:
i have a rooted sprint epic. I was on the viper rom and tried the ec05 update from clockworkmod v2.5.1.0 and it said failed, then i tried installing [ROM][ACS] SyndicateROM Frozen 1.1.0 (Takiya) : and it said complete, when i rebooted it was stuck on the samsung screen for 15 minutes. I tried a different rom and it keeps saying aborted. I tried doing a restore through clockworkmod and it gets stuck on restoing chache, lost and found. it just sits there and does nothing.
when clockwork opens up it saids E:cant open /cache/recovery/log
can someone help me as to what i should do to get my phone running again?
Click to expand...
Click to collapse
going to have to odin to stock... then start over...
can you send me link to stock?
any way to do it straight from my phone? at work right now and cant install anything on the work computer.
Yes odin and start over. Also you need to be on ext4 to flash Syndicate rom
Sent From My Evo Killer!
how do i change to ext4 ?
what do you mean odin and start over? what exactly is start over?
sorry my knowledge of how this works is very light, thus me screwing up my phone today
gt2776 said:
how do i change to ext4 ?
what do you mean odin and start over? what exactly is start over?
sorry my knowledge of how this works is very light, thus me screwing up my phone today
Click to expand...
Click to collapse
Use this thread and do the steps under : Stock EB13 Deodexed EXT4 + CW 3.0.0.6
http://forum.xda-developers.com/showthread.php?t=853209
After that you can use any EB13 or EC05 ROM that uses EXT4.
You will also want to use odin to update your modem to EC05; you can go here
http://lostandtired.com/android-development and click on the link for EC05 Modem Package (Odin), after you get your ROM up and running.
put the tar in the PDA area and the pit in the pit and update the modem, faster 3G is what most have experienced with the EC05 modem.
Hope that helps, good luck
put your phone in downloading mode and flash back to the stock of your choice.
xda is, AWESOME
thanks to everyone who cared to help
a few months ago i rooted and installed clockworkmod v2.5.1.0 and installed a rom on my phone, everything went smoothly until a few days ago i wanted to try another rom, so i backup my phone on clockworkmod and do what i remember i had to do, and installed the new rom, but my phone just stayed in the turning on logo, right now i cant use my phone or restore my old rom and i keep getting E:can't open /cache/recovery/log
after pretty much any command i try. i need urgent help so i can use my phone!
I'm no expert or anything but I believe if you were using clockworkmod 2.5 you are running rfs (I believe it is) and you were trying to install a new rom which most likely is ext4 which is what caused the boot loop. So to make it eaiser to understand you tried to flash a newer rom on clockwork mod 2.5 when you needed clockwork mod 3.0+ (ext4 enabled). So now your going to have to use odin and go back to a stock of your choice ec05 I would say.
Check the wiki in android development and see what you need to go back to stock with odin, that will help
Sent from my SPH-D700 using XDA Premium App
Promni said:
a few months ago i rooted and installed clockworkmod v2.5.1.0 and installed a rom on my phone, everything went smoothly until a few days ago i wanted to try another rom, so i backup my phone on clockworkmod and do what i remember i had to do, and installed the new rom, but my phone just stayed in the turning on logo, right now i cant use my phone or restore my old rom and i keep getting E:can't open /cache/recovery/log
after pretty much any command i try. i need urgent help so i can use my phone!
Click to expand...
Click to collapse
Yes, you need to Odin back to stock. There are stickies on top of the forums on how to fix a bricked epic, restore stock. My guess is you tried a ROM that required EXT4 file system. If you still wish to try these ROMs there is a sticky at top of Development for installing Clockwork Mod 3.0.0.6.
Do you BONSAI?
I'd agree. The kernel probably is what broke that down, with the ext4. Flash CWM3, make sure you have the correct modem for that ROM, and try reflashing the ROM. sometimes (SOMETIMES) that works, without having to ODIN back. I was on leaky gingerbread with ed12, which doesn't (yet) support ext4 / CWM3, i flashed the ec05 modem back in, flashed cwm3, and reflashed the SyndicateROM Frozen - without having to ODIN the stock- worked perfectly.
This may work for you-
Flash modem needed for ROM
Install CWM3
Reinstall <rom>.zip through CWM3.
there is one problem, my pc wont recognize my phone.
Ok i got it running again, thx everybody!
Promni said:
there is one problem, my pc wont recognize my phone.
Click to expand...
Click to collapse
If you can, try using a different cable. Lot of people have had this issue using the stock one.
i got a rooted mytouch 4g with clockwork 3.0.2.4 and miui rom and everything was fine till today it just froze on me and i toke the battery out to restart and i just stayed on the my touch 4g screen so i toke the bat out and went into recovery and its giving me this error
E:cant mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
i tried wipe data/factory settings and reinstalling the rom and it still says that and i still get stuck on the my touch 4g screen
i also tried to restore and still getting that and getting stuck in the my touch 4g screen
does anyone know how i can fix this
what do i need to do
thank you
There dozens of threads on this issue now. Do a little search and you'll find a lot of information on the problem. I'm sorry to say, but it sounds like you have a bad eMMC and it's essentially bricked.
thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/
drocha86 said:
thanks for the reply im a noob when it comes to this but i followed all the steps in rooting and installing roms everything was working fine for a good 3months i used to have cm7 and then switched to miui and had that ever since
so im pretty much screwed lol
i googled and i cant find nothing on how to fix :-/
Click to expand...
Click to collapse
Unfortunately nobody has been able to fix this yet. You could attempt to exchange it at t-mobile.
well now i think i got a full brink i tried doing the pd15img.zip trick and the only thing that turns on is the orange led wtf lol
if i send it back will they know that i rooted it can i just say i dont know what happend lol ??
I've had my wife's Samsung Fascinate rooted from the beginning and running various roms. I recently went to CM7. Everything worked fine until I tried to update the kernel. The phone would not but past the opening screen, No problem I had some backups. Unfortunately now when I try to do anything in CWM I get the following errors.
ClockworkMod Recovery v4.0.1.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open/cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Essentially at this point CWM is useless. I've tried to restore using Odin but Odin will not install anything. I have used Odin in the past to recover this phone with no problem.
Any thoughts?
You cant reboot using the hardware buttons in cm7, you need to hold the power button, select reboot, and select recovery for it to work.
Sent from my MIUI SCH-i500
Problem is I can't even get into cm7 anymore.
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
schnyd said:
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
Click to expand...
Click to collapse
Glitch kernel is by far the best kernel I've ever used, IMO. Compatable with cm7 and MIUI.
Sent from my SCH-I500 using XDA App
tripacer99 said:
Glitch kernel is by far the best kernel I've ever used, IMO. Compatable with cm7 and MIUI.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I tried glitch kernel and the phone wouldn't boot using it. Any particular version I should check out.
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
schnyd said:
Well I've got most of my problem solved. I just need a kernel that is compatible with cyanogenmod 7. Anyone have any recommendations.
Click to expand...
Click to collapse
I am having exactly the same problem as you had, though I got my problem from flashing a custom rom. I am on a Desire S with ClockworkMod 5, how were you able to fix it?
Whats up guys I have a Sprint Tab. It's not working anymore.
First off, I'm not an expert, or even half way expert. But I do follow walk through instructions well.
Initially, I was using the tab with GB 2.3 rooted and pretty much stock.
After a while I decided to put Cyanogenmod on it to improve my tab experience. It worked for about a month and a half, and then I ran into some problems with it. It started to reboot and get stuck at the boot screen and got no further. I tried upgrading to a newer build of Cyanogenmod but that kept getting stuck too. After trying different builds and a whole bunch of other things I realized that it wasn't going to work.
I figured it was an issue with Cyanogenmod and CWM.
Anyway, I decided to sell the tab and get a Galaxy S3 so I wanted to return it to stock.
I tried Heimdall one-click and Odin to get it back to stock. Guess what? No success.
The Tab initially had the Sprint Splash screen. And it is sitting here next to me stuck at the samsung screen just looping. Pretty useless.
What is the problem? Again I am far from an expert, I do NOT know what to try next.
Any suggestions?
Hey,
Your Tab did not work after new build is probably because of incorrect 'upgrade' procedures. The early CM9 build was based on a non-MTD partition system. The later build is based on an MTD partition system. You would need to restock to GB 2.3.3 going from a Non-MTD to an MTD rom.
Now that you want to re-stock, you will need
CDMA stock ROM 2.3.3 (preferable than the 2.3.5 or 6)
correct .pit file
dbdata.rfs
Flash the CDMA stock ROM while re-partition with the .pit file you have. (re-partition is a MUST going from ICS back to stock 2.3.3).
Once you are done flashing and re-partition, do a factory reset data wipe, cache wipe, dalvik wipe. see if you can do those successfully. If you get a mounting error message (most likely you will, and you will still be stuck at SAMSUNG boot loop), proceed.
Flash separately a dbdata.rfs from the CDMA stock rom you have (extract it from the ROM package and create a separate .tar for flashing or you can search in XDA). Reboot back to recovery and do another all wipes. This should take care of your problem (Hopefully).
you can do all those using heimdall or ODIN.
I hope this helps.
ill try that, thanks. But one thing.... I know you said improper installation of CM9 could cause this. But how come out of the blue it happened and not the first time I did the installation of it?
I definitely remember all the steps at least 9-10 times before I did the upgrade. So I don't think I missed anything at all. Maybe I did, maybe I didn't .
Not sure what to make of it.
ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?
throwback1718 said:
ok guys I tried the dbdata.rfs flash
didn't work either.
when I booted into recovery mode, I keep seeing
E: failed to mount /cache
E: Can't mount /cache/recovery/command
E: copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
So those are the three error messages that I am getting.
What can cause these errors?
Click to expand...
Click to collapse
Try this. Follow the link provided.
http://forum.xda-developers.com/showpost.php?p=27096519&postcount=2
Make sure you tab isn't plugged into a dock, u had major problems trying to flash that way. Sometimes u can't even have it plugged into a charger.
Sent from my ADR6425LVW using Tapatalk 2