I know how to flash roms. Been doing it for the past few months. Now when I restore to stock and isntall latest 2.5.1.x clcowkork along with superclean 2.9.2 it vibrates a crap ton and refuses to boot. It probably a FC boot or something idk, I wiped data and dalvik and all that jazz. Was coming from d101. Any help?
Edit: was not rooted before flashing if that makes a difference.
Have you tried using Odin to install the one in all froyo package?
Was about to try that.
Related
Guys,
We all know you have to pay to play.....
Used rom manager to restore my 2.1 backup I made before I flashed to bionix 1.3.1.
Just wanted to learn how to do the restore should I run into issues.
Everything went fine, I say it copying the files, etc etc. Didn't see any errors, phone rebooted on it's on but never came on fully.
Phone has been stuck on "VIBRANT" logo on the screen for quite a while.
What's the steps to get my phone working again?
I hope it's not a big UGH.
EDIT: I just restarted phone and with the two volume buttons depressed and after vibrant flash I hit the home button and somehow got into clockwork recovery mode. trying to restore the bionix 1.3.1, will report back shortly
EDIT: restore worked with bionix and is back up and running.
Why did the bionix restore work but not my back up for 2.1????? Is this because the original restore was performed from rom manager and second restore was performed from clockwork recovery mode?????
Did I luckily avoid a brick situation?
Doesn't back up your kernel. So you restored a 2.1 rom running a 2.2 kernel =bootloop
Sent from my SGH-T959 using XDA App
odin or reflash bionix if its still on your sd card then put a 2.1 kernel on then flash that then restore ??
So as per my OP I restored bionix and all worked fine.
What was the point of backup up my 2.1 version if I can't restore back to it since the kernels are different???
If I want to restore my 2.1 version, via clockwork recovery, what's the process. Is there a way to delete the kernel or wipe it first if I need to go back to 2.1?
I know the odin way, but the clockwork recovery console is so easy and convenient?
download any 2.1 kernel and put it on your internal sd . After you have your kernel just restore your nandroid and before rebooting flash the 2.1 kernel .
I'm new to the whole kernel thing to be honest. By putting it on the internal SD card, what does that accomplish, I'm sure it has to get installed somehow, no?
Another quick question, why do some roms require to clear davlik and cache and some don't?
Is it something that can be done regardless if a rom directions say to do it?
Just getting more noob stuff out of the way.
sometimes they include that in the rom so u dont have to but as a rule always wipe dalvik and cache and data.
Excellent, thank you
kero4 said:
I'm new to the whole kernel thing to be honest. By putting it on the internal SD card, what does that accomplish, I'm sure it has to get installed somehow, no?
Another quick question, why do some roms require to clear davlik and cache and some don't?
Is it something that can be done regardless if a rom directions say to do it?
Just getting more noob stuff out of the way.
Click to expand...
Click to collapse
Like I said flash the 2.1 kernel. You could download a flashable zip. Place it on your sd then after restoring your nandroid backup flash the kernel by selecting "install zip from sd" in recovery.
Sent from my SGH-T959 using XDA App
I wouldn't post normally but I've tried everything.
Odin EB01 with PIT JT's CWM Wipe CM7 build 4 nothing
From ComRom 2.0 JT'S CWM Wipe CM7 build 10 nothing
Those aren't the only one's I've tried but numerous variations of each. I get everything from status 7 errors with build 10 to SD card mount errors with build 4. I really want to try CM7 but I just can't get there.
Can anybody help or just throw some ideas out there?
By build 4, do you mean 7/4? If not, the 7/4 build seems to be the best to start with. That is what I had to do. Also, did you flash the CWM fix?
Sent from my SCH-I500 using XDA App
Yes that's what i meant.
I followed the same procedure and got a boot loop the first couple of times. Finally I read something about not wiping data (factory reset), that did the trick. I just wiped cache and dalvik when going to build 9 (I guess it should work with 10 as well)
Kazba1626 said:
I wouldn't post normally but I've tried everything.
Odin EB01 with PIT JT's CWM Wipe CM7 build 4 nothing
From ComRom 2.0 JT'S CWM Wipe CM7 build 10 nothing
Those aren't the only one's I've tried but numerous variations of each. I get everything from status 7 errors with build 10 to SD card mount errors with build 4. I really want to try CM7 but I just can't get there.
Can anybody help or just throw some ideas out there?
Click to expand...
Click to collapse
I've gone back and fourth three times between com rom 2.1 and cm7 and
Every time I just odin eb01 and the atlas pit, fully boot, odin cwr 3-30 fix all, immediately three finger boot into recovery, wipe everything, flash cm7 build 7/04, boot fully, back into recovery via power menu, flash test build 9 ...(don't remember the date) without wiping...hope this helps?!
Sent from my SCH-I500 using XDA App
So you flashed CM7 build 4 not using JT's CWM?
Sent from my SCH-I500 using XDA App
efan450 said:
I've gone back and fourth three times between com rom 2.1 and cm7 and
Every time I just odin eb01 and the atlas pit, fully boot, odin cwr 3-30 fix all, immediately three finger boot into recovery, wipe everything, flash cm7 build 7/04, boot fully, back into recovery via power menu, flash test build 9 ...(don't remember the date) without wiping...hope this helps?!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks man-this worked for me when nothing else would.
This is crazy how I can't get absolutely anything to work
I was in the same desperate situation you are until i did the following (worked on mine and my brother's phone):1- odin back to eb01 with the atlas 2.2 pit file and let it load
2- odin the cwm recovery.all file
3- install Evil Fascination 3.6 though cwm (wipe data factory reset, cache partition, and dalvik first). Evil will do the voodoo conversion don't touch it until it loads completely.
4-Flash jt1134's cwm fix thats found in his cm7 op. Reboot recovery and make sure you're on it. I think it is 3.0.7x
5- On jt's recovery, do a factory reset, cache partition and dalvik wipe
6- Install cm7 09-04 build and let it do the conversions and load. I swear it installed in less than 5 min.
7- Once it loads up get into recovery which at this point should be4.0.x. Flash gapps. Reset and let it load
8- Go back to recovery(always through power button) and flash build 10 09-13 NO WIPES.
9-profit
I tried that didnt work I just gave it up at this point I'd been trying for hours. Thanks
Sent from my SCH-I500 using XDA App
Thank you very much. I thought I was screwed. I was able to get back to stock. Now I will be eventually making my way to CM7.
Edit: I followed the steps perfectly and was able to get to CM7 7/13. Thanks again.
Phone: SCH-I500vzw
I've been trying to install MIUIwiz 1.1.1 to no avail. I start with a freshly Odined ED05 (performing a full boot). I then flash the DC09 modem and CWM flash the patch to ED01 with a full reboot. I then flash to JT's TW 415 voodoo kernel and allow it to convert to ext4. I then wipe data, cache, and dalvik, before finally flashing tsm_miuiwiz_1.1.1.zip.
The phone makes it through the Samsung boot without error, but the MIUI loading boot/loading screen is an endless loop of what seems to be something crashing (one vibrate, a pause, and then two vibrates and the screen refreshing). I've tried every 'fix' I could find (that's where the ED01 modem bit came up), but I can't get the rom to boot. Any advice would be greatly appreciated. I was previously on MIUI mtd 1.8.5, but experienced com crashes fairly often and some sort of phantom crash (one vibrate, followed by three) on a very regular basis. It appears my phone just hates MIUI. I suppose I'll try another rom for now.
try the steps in this guide. Just replace vgb with miui
http://forum.xda-developers.com/showthread.php?t=1212239
can i reflash miui asop 2.3.7 for a clean install? or do i need to odin back to stock? im fimilar with cwm but i haven't learned how to use odin yet. im on a vibrant, dont have any nandroid backups and im getting force closes on EVERYTHING. i read other people are getting them too with the latest update. should i reflash the previous update via cwm, wipe dalvik, fix permissions (is that automatic? or do i need to know about the permissions?), factory reset (does that delete files on my interal sd? if not what does?) when i installed this rom, i came from bionix v 1.3.1 and all i did was wipe dalvik and installed from sd, and it worked fine, but i dont think im doing a "clean" install
Hey guys.
I'm on LA4 and i want to flash a custom ROM onto my SGS2.
I treid CM7 (flashed is twice) and som other ROMS but everytime i flash it, i get in a boot loop.
I hope i'm doing it the right way?
I copy the .zip file to my sdcard and press "install zip" in the recovery mode.
Did you wipe data/cache/dalvik before installing the rom? It's pretty much important, especially if you're going from LA4 to CM7
yea,sure!
before and after the flashing i wiped all
Edit: Also try format /system after you wipe the 3 said above.
Try going back to your stock image and flash a stock KERNEL afterwards, boot CWM, flash a stock image, when done, flash a stock kernel and newest radio.
I'd say it might be a kernel issue. I had it when I flashed MIUI, and in reverse when I flashed back to others..
Sent from my Galaxy Nexus using xda premium
Try avoiding wiping it afterwards. Just wipe everything out, flash it and immediately reboot.
I also hope you did a nandroid backup as well. If you did that and it still boot loops, try restoring it and going back to it and having another go.
oh my gosh i figured it out!
CuraeL, you're right.. its a kernel problem
i have to flash the kernel again after the rom update.. weird but only that way it's working!
thanks
No worries. I have had to do it on a lot of the roms I installed myself, on my SGS II, back in the days. Wonderful phone, a bit weird the way the whole kernel thing is made. But I suppose that's cause the kernels are written for 2 different "builts" of the system.
Keep it in mind, as you might need to do it again some day, lol.
Have fun. ^^