Related
I have a huge problem.
I rooted my wife's (yea...my wife's...) Fascinate last night. The root method I used worked like a charm. I installed ROM Manager. Again...no problem. Flashed ClockWork Mod no problem as well. I selected "reboot to recovery" to do a nandroid as I've done on numerous other phones. In fact, ALL of this I've done on numerous times on half a dozen different phones.
When it rebooted, instead of it being in Nandroid, it was in the regular stock recovery. My stomach sank...lol
It would just reboot...that's it. Is there a loop with the fascinate? How do I get out of it if so?
At one point, the phone wouldn't do ANYTHING...all that would happen when I plugged it in was a little computer and cell phone would pop up on the screen. No recovery, no nothing. So, after lots of digging and reading, I found the files here that I thought I'd need to reflash the system using odin. I got the /system file, the kernal and the recovery. I flashed the kernal...worked perfectly. Flashed the recovery...again, perfect (and recovery is back but still in a reboot loop...) When I try the .tar.md5 system file, it says md5 is invalid so I changed it to a straight .tar file and it worked all the way up to the very end, then it stops. That's it.
I just need the phone to work again for my wife. I don't care if I even flash a new custom rom (which I can't fine one of that works!) or if it's just simply restoring the stock system files.
ANY AND ALL HELP GREATLY appreciated, guys. Thanks!!
To get to cwm, you have to select "apply update.zip" from stock recovery. This is how fascinate and a few other galaxy s cwm works. Also don't ever delete the update.zip file from sd card.
But to start out....
Step 1: Start with Odin:
http://forum.xda-developers.com/showthread.php?t=782204
A. Flash system and pit together
B. Flash kernel
C. Flash recovery
*Important note: in Odin, always use PDA!!!! Using phone will cause huge issues.
Step 2: Flash cwm:
http://dl.dropbox.com/u/458252/CWMrecovery.tar
*note: this is an Odin file, again flash using PDA
Your phone will end up stock, rooted and with cwm.
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Rooting aside if you want to just fix it, I can help you with that. Nothing more though. Interested?
Sent from my SCH-I500 using XDA App
rmp5s said:
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Click to expand...
Click to collapse
What do you mean for the "stupid fast replies"?
tats_06 said:
What do you mean for the "stupid fast replies"?
Click to expand...
Click to collapse
I think he means that your replies were just as fast as geeknik's kernel. The only other interpretation is that although your replies were quite quick, unfortunately they were also stupid. But thats obviously not true, so it must be the former. ;-P
Sent from my SCH-I500 using XDA App
I think some of us are showing our ages, "stupid" is the new "awesome."
Sent from my SCH-I500 using XDA App
Hey dont worry i had same problem
http://www.mobilephonenews.info/and...fascinate-restore-is-it-really-that-easy.html go here and follow instructions!!!
then update phone manually to get latest update!! might take a few times or many times because it failed to get update many times but eventually youll get it!!
goodluck
Sherwood, in his case he needs all Odin files, not just system.
Fallingup was first to put this up, credit to his post!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin%...in3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin%...System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin%...covery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin%...00-VZW-pit.pit
Yea...I mean it's almost stupid how fast I got good, meaningful, educated replies.
In other words, you guys kick ass. Thanks again!!
similiar issue, please help me out.
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
aabfalter said:
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
Click to expand...
Click to collapse
sam problem here, i can get to cwm recoery and thats it. someone please help
justin94 said:
sam problem here, i can get to cwm recoery and thats it. someone please help
Click to expand...
Click to collapse
I had the same problem when I flashed the non-voodoo over voodoo and spent hours trying to fix the boot loop. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=782204 but still running into the boot loop (recovery mode) then I flashed with the file from here via ODIN http://adrynalyne.us/files/kernels/DI01package3.tar.md5 and it restored my phone back to factory. From there you would have to do the root procedure again. Hope this helps.
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
The update.zip to get to clockwork??
http://sharesend.com/g2jbl
First time I've ever hosted a file so let me know it if works lol.
Sent from my SCH-I500 using XDA App
This could be one of the rosiest phone ever to unbrick, unless you are a noon of coarse.
Sent from my DROIDX using XDA App
tswtech2 said:
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
Click to expand...
Click to collapse
There is no update.zip method to unbrick. You will need to re-download a working copy of Odin or figure out how to make Odin work to do a factory restore with it.
Download the di01 complete package and use pda in odin to restore it.
http://forum.xda-developers.com/showthread.php?t=867648
After power is only a white Google logo in the center of the black screen and then stays.
Can someone help me?
Thanks
I need more information.
Rooted? Rom? Kernel?
What did you do.
Sent from my Nexus S using Tapatalk
Did root. Wanted to put back the original rom will only start after the Google logo
And how did you attempt to put the google rom back on?
Did you have a custom recovery?
Sent from my Nexus S using Tapatalk
I installed the rom on recovery. Unfortunately, the wrong dan grh78 I wanted to make an update on grh41. My Nexus was formerly a rom grh78c
You didnt answer my question. Do you have clockwork recovery or the stock one? If its clockwork then its easy to fix.
Sent from my Nexus S using Tapatalk
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
deltoro84 said:
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
Click to expand...
Click to collapse
go into recovery, enable the usb storage option, put the right rom on your "sd" storage, turn off the usb storage option, wipe data(factory reset), flash the right rom, then reboot.
deltoro84 said:
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
Click to expand...
Click to collapse
Okay heres what you do. Is your phone currently off? If it isn't then, pull the battery out. Put the battery back in.
Hold Volume Up + Power.. KEEP HOLDING THESE TWO and you should be in bootloader. Volume down to Recovery. Does it work? Yeah? Clockwork Recovery?
Okay. Now you have two choices:
1) Stock: download: http://forum.xda-developers.com/showthread.php?t=968403
Mount the phone via USB in Clockwork Recovery. Download that file and put it in /clockworkmod/backup/ (make sure you put it correct.. otherwise Clockwork wont see the file). Unmount, Check nandroid backup/restore is it there? If it isn't, recheck if you put it correctly. If so, reboot into recovery again.
2) Download a custom ROM such as CM7, Axura, GingerS, NSCollab, MIUI, whatever you want.. mount your phone via USB and put it on your sd card.
Wipe dalvik,cache,factory and flash that ROM (if you flash CM7.. you'll have to flash Gapps right after; MIUI.. flash English Language Pack right after).
Reboot. And it should go past the Google screen.
Alternatively, you should be able to plug your phone in the computer and using ADB by typing "adb reboot recovery" should get you into the recovery as well.
Edit: or do what simms suggested. Either way, you have to go into Clockwork Recovery to fix this.
it isnt working. i just come into a fastboot modus. how should i put the rom into a sd???? The mobile is recognized by the usb.
deltoro84 said:
it isnt working. i just come into a fastboot modus. how should i put the rom into a sd???? The mobile is recognized by the usb.
Click to expand...
Click to collapse
yes you're supposed to be on a screen that looks like http://2.bp.blogspot.com/-qW-hye-fsWM/TWJgxyBheCI/AAAAAAAAAEE/dIO-8DPEs1M/s1600/s1.jpg
if you volume down to the third one, it says Recovery.. that should get you into Clockwork Recovery (Orangeish) http://www.addictivetips.com/wp-content/uploads/2010/12/Clockwork-Recovery-3.jpg
if it looks like http://cdn.androidcommunity.com/wp-content/uploads/2010/12/device2-540x324.jpg (yeah aside from Dell) then you dont have clockwork recovery.
When you get into Clockwork recovery, there is a option in there to mount your USB. If you're able to get into Clockwork, I'd go to either of the steps I linked above.
Stock, CM7, Axura, MIUI, ETC. You need to replace your ROM with one of these.
Since you seem pretty new, I'd just stick with stock because that's what you're most comfortable with.
Zephik is trying really hard to help you here man. You need to read what he has written very carefully, supply more information, and follow the instructions really carefully. Then you can fix your phone without a problem.
Let us know how it goes.
zephiK said:
Okay heres what you do. Is your phone currently off? If it isn't then, pull the battery out. Put the battery back in.
Hold Volume Up + Power.. KEEP HOLDING THESE TWO and you should be in bootloader. Volume down to Recovery. Does it work? Yeah? Clockwork Recovery?
Okay. Now you have two choices:
1) Stock: download: http://forum.xda-developers.com/showthread.php?t=968403
Mount the phone via USB in Clockwork Recovery. Download that file and put it in /clockworkmod/backup/ (make sure you put it correct.. otherwise Clockwork wont see the file). Unmount, Check nandroid backup/restore is it there? If it isn't, recheck if you put it correctly. If so, reboot into recovery again.
2) Download a custom ROM such as CM7, Axura, GingerS, NSCollab, MIUI, whatever you want.. mount your phone via USB and put it on your sd card.
Wipe dalvik,cache,factory and flash that ROM (if you flash CM7.. you'll have to flash Gapps right after; MIUI.. flash English Language Pack right after).
Reboot. And it should go past the Google screen.
Alternatively, you should be able to plug your phone in the computer and using ADB by typing "adb reboot recovery" should get you into the recovery as well.
Edit: or do what simms suggested. Either way, you have to go into Clockwork Recovery to fix this.
Click to expand...
Click to collapse
If i go into recovery , i have 4 options.
1. reboot system now
2. apply update from/ sd card
3. wipe data/ factory reset
4. wipe cache partition.
Which obe should i choose? What should i do?
deltoro84 said:
If i go into recovery , i have 4 options.
1. reboot system now
2. apply update from/ sd card
3. wipe data/ factory reset
4. wipe cache partition.
Which obe should i choose? What should i do?
Click to expand...
Click to collapse
You don't have Clockwork Recovery then. Do you have the SDK installed? You need to go through the guides to set up SDK if you don't have it installed already.
- http://forum.xda-developers.com/showthread.php?t=895545
- Nexus S Drivers: http://forum.xda-developers.com/showthread.php?t=878786&highlight=Driver
Pretty much.. you just need to fastboot flash http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Download the clockwork recovery recovery-clockwork-3.0.0.5-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Click to expand...
Click to collapse
You need USB drivers for the Nexus S for the device to be recognized on your system.
Once you get Clockwork Recovery up and running (that orangeish recovery that I linked above) you should be able to refer back to my previous post. Once you complete that, your phone should be up and running.
go zephik go!
great display of patience
zephiK said:
yes you're supposed to be on a screen that looks like http://2.bp.blogspot.com/-qW-hye-fsWM/TWJgxyBheCI/AAAAAAAAAEE/dIO-8DPEs1M/s1600/s1.jpg
Snip..
Click to expand...
Click to collapse
This may be the most helpful post ever.
Sent from my Nexus S using Tapatalk
[hfm] said:
This may be the most helpful post ever.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
cool you love to "troll" me. congratulations
its better than explaining what a bootloader looks like.. especially to a novice user (not insulting anybody).
a picture is a million words. troll me all you want, i really dont care. as long as im helping somebody rather than attempting to insult people over the internet. im doing more than you, so please.. continue "trolling", it'll get you really far in life.
Have you tried using odin to restore to stock?
Sent from my Nexus S using XDA App
bajansurfer said:
Have you tried using odin to restore to stock?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Or that.. but Odin isn't very popular with the Nexus S.
http://forum.xda-developers.com/showthread.php?t=947950
Option is there if you want to go that route. I used to use Odin for the Vibrant but I'm not too familiar with it for the Nexus S as its not as popular. If the OP decides to go with Odin then I can't assist you.
I really want to see how this pans out. He cannot be any more of a noob than I was very recently and I got the hang of it (zephik helped me too) so he should be able to fix it.
It's amazing the help you can get for free on this forum. If zephik was running a mobile phone shop be would be making money with the information he's providing ( although it would be much easier for him to take the phone away from the OP for 15 minutes and flash it himself ;-) ).
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
couldn't agree more. i rooted my phone the other day with a kernel change, but now i want to isntall a rom but cant even start to work out the way to get cwm on to flash a rom!!! annoyinh to say the least.... the x10 and sgs1 i had were a breeze
da.trute said:
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
Click to expand...
Click to collapse
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Freedom to choose is a great thing. I like having options.
pulser_g2 said:
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Click to expand...
Click to collapse
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Intratech said:
Freedom to choose is a great thing. I like having options.
Click to expand...
Click to collapse
It is yes, however you seem to have misunderstood the thread, having different methods being forced up you by different cooks is not choice, choice would be that all methods were compatible and interchangeable, they are not apparently. Some require different roots / kernels.
EDIT. not suggesting anything is really being forced on us, I appreciate all dev work, just hoping for a bit more conformity of installation process.
da.trute said:
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Click to expand...
Click to collapse
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
seshmaru said:
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
Click to expand...
Click to collapse
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
da.trute said:
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
Click to expand...
Click to collapse
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Wow. He's just asking a question. Why belittle people for asking?
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Because I see exactly 3 threads on the same page that could either answer his question or link him to the answer. But people are too lazy to read.
Due to people like this we have a thread here which isn't needed at all since there is conformity to flashing across all ROMs. All because people make claims about things when they don't even know how it works.
The big difference in swapping from one custom rom to another is not the method of flashing but do you need a clean phone to install a custom rom on top of another one .
My personal choice is a fully wiped phone before installing a new custom rom .
Methods CWM or Odin mostly CWM as thats the major choice for devs .Kies is not a rom flash tool .
Choice also gives a better recovery option .
Villain on top of or below Cognition both use same flash method via rooted CWM flash .
The problem on this forum is not three or four choices but a complete refusal by many to even bother reading any instructions .
jje
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Hi, you get used to these ***** after a while
seshmaru said:
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Click to expand...
Click to collapse
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
da.trute said:
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
Click to expand...
Click to collapse
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
seshmaru said:
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
Click to expand...
Click to collapse
what does this actually mean then?
"Make sure you got CF Root CWM (not the clockworkmod root)"
I have flashed all three roms using the exact same method .
Changed kernels four times this week using CWM .
Revived one bricked phone using Odin .
jje
Hollow.Droid said:
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
Click to expand...
Click to collapse
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
da.trute said:
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
Click to expand...
Click to collapse
No, there is only 1 method for ROM flashing, CWM. Every ROM has CWM, CWM is the end all be all for you, no matter what different apps do, they all use 1 method CWM. CWM CWM CWM. Stop being dense and read up before posting dumb factually wrong claims.
Every single ROM can be flashed by holding volume up, center button and power, how difficult is it to grasp this concept?
Here this video should help you.
http://www.youtube.com/watch?v=JmvCpR45LKA
there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
xriderx66 said:
there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
Click to expand...
Click to collapse
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
SamsungVibrant said:
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
Click to expand...
Click to collapse
but thats my actual question... which one should i download? Is one better or has any advantages than the other?!
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
edit:
am i meant to follow THESE instructions?
cashyftw said:
Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
If you have installed or updated CM7/MIUI and lost your baseband, IMEI, or both, this should help you. Due to the amount of people currently having this problem, I would recommend this be stickied at least temporarily until things are straightened out, so people can find it easily.
For Windows only, I do not have a Mac.
Step 1 - Read the entire post and understand everything involved before you attempt this. This is a long ride, probably 30-40 minutes from start to end. This is not for new people, and will assume you have a certain amount of knowledge because you attempted to flash CM7/MIUI.
DO NOT SKIP OR SHORTCUT ANY STEP IN THIS PROCESS, UNLESS I SPECIFICALLY STATED YOU MET THE CRITERIA TO DO SO. DO NOT EVEN THINK ABOUT TRYING THIS UNLESS YOU CAN REACH DOWNLOAD MODE AND RECOVERY USING BUTTONS WITH THE PHONE OFF!
Step 2 - Gather what you need...
1 - The AIO Vibrant Toolbox : http://forum.xda-developers.com/showthread.php?t=954509
Install according to directions in the post. Donate to this guy. He spent alot of time making this easy for you to do.
2 - The old CM7 install files : http://www.mediafire.com/?gn4qoonoe3cjyp6
Unzip to a location that is easy to get to.
3 - The new version of CM7/MIUI you want to install, from the thread of your choice. Donate to the developer you are using, they spend alot of their free time making your phone better. They don't get paid for it, and they dont charge you for it.
4 - Your phone, with a full battery.
Step 3 - Odin to JFD and install Clockwork 2.x
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but power it down and pull your battery. See that sticker under it that says IMEI? Write it down! You will be referencing it a few times throughout the process. Start Odin and select your pit and pda files, they should automatically come up if you are using the toolbox. Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should go to download mode, and see Odin connect. Hit start and let it fly. Once it reboots, unplug your phone. Go to settings/about phone and you should have a JFD baseband. Hit status, and check your IMEI. See how it matches the one you wrote down? Yay! Move on to the next item. If it does not, you have some reading to do because you really screwed something up, and it is beyond my power to help you...
2 - Mount phone and put the following files on the root of the sd card:
vibrant-efsbackup.zip (if you already have a backup/efs folder on your sd card you do not need this)
cm7-vibrant-initial-20110224.zip
The zip file of the new CM7/MIUI rom you want to flash.
3 - Download ROM Manager and install clockwork recovery 2.x (if you already have the update.zip on your sd card, which you should, you can also skip this) and power down your phone.
4 - Boot into recovery using the 3 button method (holding volume up and down and power, releasing power when the word VIbrant appears on your screen), hit reinstall packages, you may have to hit it twice to get to clockwork recovery. Choose to install zip from sd card, and select vibrant-efsbackup.zip. Let it do its thing. Then select reboot, and when it does, check your sd card for a backup/efs folder. Got it? Good. Power down the phone. (Obviously, if you already have the efs backup completed, you could have skipped this step.)
Step 4 - Install Clockwork 3.x and Old CM7
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but pull your battery. Start Odin and hit the pda button, select the file cm7-vibrant-initial-kernel.tar from the CM7 package you unzipped (Remember, in a place that is easy to find). THIS IS IMPORTANT - UNCHECK AUTO REBOOT!!! Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should enter download mode, and see Odin connect. Hit start and let it fly. Once it is finished, pull the usb cable. With the download mode screen still on your phone, boot into recovery using the 3 button method. You should now be in clockwork recovery 3.x. Move on to the next item! If you did not get in, you can try to pull your battery, replace it and boot into recovery from there. If you still can't get there, you get to go where the people who do not properly follow instructions go... back to Step 1.
2 - In clockwork 3.x, choose factory reset, and let it do it's thing. Then go to mounts and storage, and format system, data, and cache. Choose install zip from sd card and choose cm7-vibrant-initial -20110224.zip. As it is installing, one of the last things you see should be "restoring efs". Hit reboot when finished, and boot into CM7. When it boots, make sure you toggle the lockscreen a couple times so it connects to service. Check baseband and IMEI again. Baseband should have changed, but it does not matter until we get to where we are going. IMEI still the same right? Awesome! Power down the phone, move to the next step! It's not? You my friend, get to meet all your other friends back at Step 1.
Step 5 - Installing what you really want...
1 - Boot into recovery using the 3 button combo. Do a factory reset, wipe cache partition, go to advanced and wipe Dalvik cache. Choose install zip from sd card, and pick that shiny new version of CM7/MIUI you picked out. You are almost there. Flash it! Reboot, and when it comes back up, take note of what time it is and DO NOT TOUCH THE PHONE FOR 15 MINUTES. You have no idea the amount of bugs this squashes. After that, check the baseband and IMEI, even though you already know it is right anyway. If it is not, do i have to say it again? You know where you are going...
2 - Destroy the paper you wrote your IMEI on, you would not want that info in the wrong hands...
3 - Enjoy your new rom
FAQ:
Q: I did everything you said, and it did not work!
A: You either skipped a step, or did not stop at the point I told you you were screwed.
Q: No, seriously, I did everything you said!
A: Seriously, I have done this 5 times in the past 3 days, and it worked every time.
Q: I installed CM7 nightly #9,10,or 11 with this method, and I have no sound on calls. What gives?
A: These builds have known issues with in call audio. Flash CM7.1
Q: Once I am on CM7/MIUI, do I have to do this every time or can I update normally?
A: Once you are on CM7 or MIUI with the proper IMEI and a good baseband, you should be able to update via the rom posting instructions. If you decided to switch from CM7 to MIUI or vice versa, I would go back to this process to get your initial installation.
Q: I installed CM7.1 and then tried to go to MIUI, and lost everything again, what happened?
A: There are changes betweeen CM7 to 7.1 that have made this difficult due to compatability issues, which is why I recommend doing this process again if you want to switch between the two.
Q: I thought there was an easier way to do this, why so many steps?
Read the first paragraph of the post, but I guess that is also asking too much...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xriderx66 said:
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
Click to expand...
Click to collapse
Just install the one you linked to, the one direct from miui.us.
The other Lithium one looks like it's customized, overclock kernal, stuff like that.
I disabled vodoo lag fix. I odin back to 2.1. Then I installed stock 2.2.
Then I followed the instructions exactly. Wipe dalvic cashe, format system/data/cache, wipe factory restore, etc etc.
Not sure if I had to install 2.2 first, but I did anyway since the install instructions were for upgrading from a 2.2 rom and not a 2.1 rom.
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
No, that lengthy install instruction is outdated
xriderx66 said:
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
Click to expand...
Click to collapse
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT by me samsungvibrant..OR THE STOCK VERSION OF MIUI could be flashed here)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
belushi7 said:
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
Click to expand...
Click to collapse
It's a very smooth rom, it has fast animations and i love em'
The only thing bugging me right now is battery life drains way faster than what i'm used to. I'll find out more on calibrating the battery/changing kernels etc.
SamsungVibrant said:
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT..OR THE STOCK VERSION OF MIUI)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
Click to expand...
Click to collapse
Yeah, thanks, i figured that out.
Any specific kernels you're using for better battery life?
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
how do i make my phone stop vibranting everytime i get a text message?
belushi7 said:
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
Click to expand...
Click to collapse
With root explorer, free from market. Enable root within that app in settings. Also enable root with superuser app in tools folder. Then navigate to efs folder copy and paste it.
Sent from my GT-I9000 using XDA App
xriderx66 said:
how do i make my phone stop vibranting everytime i get a text message?
Click to expand...
Click to collapse
It is in settings, sounds.
Sent from my GT-I9000 using XDA App
I always flash MIUI still being on Voodoo and I don't notice anything.
Sent from my GT-I9000 using XDA Premium App
Is it ok to flash with gb bootloaders???
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
From what I have seen Lithium is actually meant to be more of a development ROM for new features. The other ROM made by that developer is the SS series which is meant to be more of a daily driver (eg. more stable), and it has additional tweaks from the official MIUI release to try to achieve things like better battery life as well as a OC or UVable kernel.
SS can be found here:
http://forum.xda-developers.com/showthread.php?t=1099533
and here:
http://forums.miui.us/showthread.php?7067-ROM-SS-11.1-%281.9.30%29-**UPDATED**-10-01-11
Unrelated to the OP, but if you're using Launcher Pro you're missing out on one of the best aspects of MIUI: No App Drawer! Instead you organize your apps into folders on the Home page. It makes you wonder why there ever was an app drawer. Seems like a silly concept now that I've been using MIUI for a while.
Alanrocks15 said:
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
not true anymore, can be flashed with GB bootloader.
Sent from my GT-I9000 using xda premium
Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?
What happens if you put it on download mode and then cancel with vol down
It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.
And if you pull the battery and put it back in does it try to boot?
What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.
megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.
megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.
Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems