I have just cooked my first SGS3 Rom using Dsixdas kitchen.
When i flash the Rom in CWM it seems to flash ok, when i reboot to boot up the Rom, i get the Samsung logo, then a black screen and thats it.
I have to just pull the battery , I can get back into CWM no problem, just wondering if anyone has ever experienced this.
I used the stock bell Rom, it all went well through the Kitchen
Thanks
Related
THIS HAS NOT BEEN TESTED!!! USE AT YOUR OWN PERIL!!! Update: So far i have it working for DJ20 users. Still fighting it with some DL17 users. Make Odin files first!!!
Hey folks,
Jt1134 (awesome Samsung Fascinate dev) and I were discussing the current plight of the Samsung Continuum. Looking over things, it looks like we can make clockwork recovery work for you guys. Please note, I DO NOT have a Samsung Continuum, so I cannot test this procedure. IT IS ESSENTIAL that someone makes ODIN images PRIOR to this! While it should work, lets be safe, folks.
Once again, let me repeat, I do not have a Continuum to test this, so make sure you have proven, tested Odin images at your disposal. I found no kernels for the Continuum made, so I need to baseline for what works.
I made this cwm recovery Odin image for folks to try.
http://adrynalyne.us/files/odin/cont_cwm_recovery_2.tar.md5
This alone WILL NOT give you clockwork recovery. The next step is to download Rom Manager, choose flash clockwork recovery, and from the choices, choose Samsung Fascinate.
This downloads an update.zip to your sdcard. Rebooting from Rom Manager should boot into recovery. Manual booting into recovery takes you to stock recovery. You merely need to install update.zip from the menu for clockwork recovery.
I know bubby is porting something better, but in the meantime, hope this helps.
FOR DL17 users, try putting this on your sdcard and see if clockwork works. (need to Odin this recovery first)
http://dl.dropbox.com/u/2056318/update.zip
Just did this and it worked i got clockwork mod recovery!! Thanks alot
Cant mount vold on di17.
Sent from my SCH-I400 using XDA App
Yeah im on DJ20 maybe thats why it worked with out a problem for me.
whats the difference in the dj20 and di17? how do i know which one mine is?
actually i see that im showing DL17
DL17 is after the update that was just released, Dj20 is before.
Yeah apparently the code needs to be tweaked for DL17 still.
Interesting.... I am officially on DL17, and your clockwork still works wonderfully? At least I think xP it boots into it through cwm, and no errors?
Sent from my SCH-I400 using XDA App
One thing i did notice is that when the phone is off and i go to boot into revocery it goes into the stock recovery, But when i open rom manager on my phone and have it boot into recovery through that it goes into clockwork mod and works good.
Is it suppose to be like that? Any one know?
CrazyKnight122 said:
One thing i did notice is that when the phone is off and i go to boot into revocery it goes into the stock recovery, But when i open rom manager on my phone and have it boot into recovery through that it goes into clockwork mod and works good.
Is it suppose to be like that? Any one know?
Click to expand...
Click to collapse
from stock recovery you have to apply the update.zip manually to boot into cwr
Ahh ok thats what i thought it was just wanted to make sure before i started messing with things.
Updated......
adrynalyne said:
Updated......
Click to expand...
Click to collapse
Thank you adrynalyne for coming back for us It really is appreciated!
I can confirm that this works... Red CWM up and working xD There is a non-important warning saying that it can't find the bitmap, but that isn't neccessary
can anyone give me some pointers on the options when using odin to flash this recovery image?
DL17 version here...
dottat said:
can anyone give me some pointers on the options when using odin to flash this recovery image?
DL17 version here...
Click to expand...
Click to collapse
Follow this: http://goo.gl/oMc7H replacing modem with the file adrynalyne posted
Thanks.. it was the step to use "PDA" instead of phone that ran me aground last time i tried this.
I've searched for a topic like mine but I can't find one for the Epic.
I'm trying to flash Nebula Rom 1.0.7 after using Odin to get DK28 modem, then I root and install CWM. I then drag the Nebula zip onto the sd then power down the phone. I boot into CWM and choose the option to pick zip folder to install from. It goes through the paces and I get the "Nebula Rom installed successfully"
I then choose Reboot System from CWM menu. The phone shuts off, starts back up and sticks on the Samsung screen. I don't know what I'm doing wrong, I followed the directions to the T and I also tried flashing Frankenstein Froyo using CWM3.0 and the same thing happened.
Please someone can you help me out. I thought I had a grasp on these things but apparently I'm missing something. What am I doing wrong?
i downloaded cm9 and i got it to install during recovery and then i flashed the gapps, but then when i went to go and reboot the systems it just stays on the "Samsung galaxy sII" screen. then when i pull the battery and go into recovery it brings me into a recovery called "android system recovery <3e>" and when i try to install a diff rom it says "signature verification failed" i really need help
kjrehrer said:
i downloaded cm9 and i got it to install during recovery and then i flashed the gapps, but then when i went to go and reboot the systems it just stays on the "Samsung galaxy sII" screen. then when i pull the battery and go into recovery it brings me into a recovery called "android system recovery <3e>" and when i try to install a diff rom it says "signature verification failed" i really need help
Click to expand...
Click to collapse
Ok I understand your issue and just like to say that every thread I have read since yesterday tells you how to fix your problem. Also, in the future just try and do better research before jumping into things... Now to help you - boot back into recovery and do a system restore/full wipe. I understand its not a CWM based recovery but if you read the OP you would of noticed that. Your second choice is to use odin a CWM recovery and you can restore your old nandroid. The link to a CWM odin recovery is also in the OP of CM9
do you know why it wouldnt boot up for me?
kjrehrer said:
do you know why it wouldnt boot up for me?
Click to expand...
Click to collapse
no but you are not alone... its an issue for quite a few people and it depends on where you were coming from. Did you go into it from cm7? Touchwiz rom? Hey best bet just follow instructions to a tee and you should not have any issues. But if you are new to this read for a day or two before leaping.
I am a flashaholic and I still have not flashed anything after cm9 alpha 2. I know how it is give it a day or two and someone will come up with a proper working recovery and zip. No need to be an early guinea pig with everything....
yeah i flash alot all the time and i followed this one exactly and i did everything right it just got stuck for me. i just flashed a stock .tar through odin and i re rooted but i want to get cm9 working so bad
[[SOLVED]]
Alright, so I checked through a few pages on the forums, and I didn't see anyone posting about this issue I am having..
I purchased my S3 a few days ago, and instantly rooted it. I used the Odin3 v3.07 method with "root66_SPR_L10VPBLJ7.7Z" ROM. That went well and fine. Then I tried flashing CWM recovery, and when I booted into recovery, it was still the stock. So I downloaded ROM Mangager and flashed the touch CWM recovery, after it finished, it asked if I wanted to boot into recovery. I agreed. Then the phone restarted, and upon starting, it showed the SAMSUNG logo, and "recovery booting" in the top left corner for about half a second. Then it just stayed on a black screen. I could do nothing after that. I then took the battery out for about 5 minutes, threw it back in, and the phone started. So I tried to manually boot into recovery, and the same issue. Took the battery out again, phone started properly, so I then tried to get into download mode. That worked fine, so I downloaded the CWM recovery on my laptop, and connected the phone through Odin, and flashed CWM onto my phone. Odin said it passed, but I still have the same issue when I try to boot into recovery.
Any ideas on something I'm doing wrong?
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
m20120 said:
It is likely that your ROM is detecting the custom recovery and replacing it with the stock one. This was a change made to the stock ROM several versions ago. Before that you did not have to do anything extra to load the custom recovery.
The versions LG8 and later have code to detect an unsigned recovery and replace it with stock. You need to:
- Download TeamEpic-Root-from-Recovery-v5.zip and place it on your ineternal sdcard.
- Get into Download Mode and connect ODIN.
- Flash the custom recovery with ODIN but do not check the "Auto Reboot" box in Odin.
- Disconnect the phone from the PC once the recovery is flashed.
- Pull the battery to power down
- Boot directly into recovery (Hold Volume Up, Home and Power buttons until recovery appears. Do not allow the ROM to start).
- Once in the recovery you need to flash the Team Epic Root from Recovery.
- Reboot
All Done
Click to expand...
Click to collapse
Correct; and the reason for this is because the updated stock firmware as a script basically that re-flashes stock recovery upon boot if stock isn't detected. The team epic zip removes that. After doing that; I'd recommend flashing the twrp recovery.
Need some Help!
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Re: [Q] Recovery Broken, Need Help
shadowcop9514 said:
Ok guys got a problem! I have a new Samsung Galaxy Sprint S3 SPH-L710 4.1.1 and I flashed CMW ROM and did not do a back up of the stock OS. The phone still works with the ROM that I flashed cm-10.1m1. I already know befor you say it dumb right! Lol I'm kicking myself because I know better. I need help finding a mirror of the stock OS with all the drivers and kernels! Can anyone help out, thanks. :crying:
Click to expand...
Click to collapse
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Okay I did some research, and I found online that the Samsung phones need .tar.md5 not .img files for recovery.
http://forum.xda-developers.com/showthread.php?t=1484304
I did not use these directions since I don't run linux, and I wasn't going to download VMWare. Anyways, the way I fixed it, I purchased and downloaded Mobile Odin from the Play store. I put the recovery.img on my external SDcard, then opened the app. Under "recovery" I selected recovery.img and then scrolled down to "Flash" It flashed the recovery.img with no problems, then booted me into recovery. I then flashed mrRobinson_Ashaman.v2.20_signed.zip so I could uninstall some bloatware.
That last part was mostly for me, until I find a ROM I like.
CNexus said:
So whats your issue? Why do you need the stock rom...? The drivers are the same and the stock kernel is for stock only, not aosp
Sent from my PG06100
Click to expand...
Click to collapse
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
shadowcop9514 said:
I'm selling my phone and getting the Galaxy S4 and the person wants the stock back on the phone.
Click to expand...
Click to collapse
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
CNexus said:
Oh ok then, just run the latest Supersonic RUU (4.67 i think)
Sent from my PG06100
Click to expand...
Click to collapse
Ok, where do I find that ?
shadowcop9514 said:
Ok, where do I find that ?
Click to expand...
Click to collapse
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
CNexus said:
WHOOPS. Sorry, I was thinking about another phone
Look up "flash back to stock galaxy s3" on google and you should get some good hits. Ignore the RUU thing, I thought I was on the OG evo forums
Sent from my PG06100
Click to expand...
Click to collapse
Ok thanks!
Hello, I am on a n7100.
I firstly flashed my stock rom 4.1.2 from odin.
My phone works well with stock.
I have downloaded the omega rom v23 from here.
I firstly installed MJ5 Bootloader via Odin 3.9.
Then Flashed "TWRP recovery" via Odin 3.9 again.
I had already put omega rom zip to my external sd card.
So I have wiped all the ways i could ever do from twrp wipe section. (All except external data storage)
Then selected install zip, Omega logo appeared awesome.
I press next, Omega Rom Installation, Full wipe, Install Omega Rom, Default Installation, Next, Install!
It installs everything correctly.
Then, Reboot Device is already ticked, I press End.
Twrp says rebooting...
And Samsung GALAXY Note II GT-N7100 logo comes.
And never goes off. Boot stuck.
Please help me i dont know where i am failing at. I made way too much research, tried way too many install orders, please show me the true way...
I think you should try flashing another ROM and see how it goes.. Mine already got stuck at boot because of multiple causes... In my case it was mostly kernel issues... But I dont think that applies for you....
MdBst said:
I think you should try flashing another ROM and see how it goes.. Mine already got stuck at boot because of multiple causes... In my case it was mostly kernel issues... But I dont think that applies for you....
Click to expand...
Click to collapse
I had alliance rom v5.2 installed 5 days ago. It has 4.3 interface and note 3 apps aswell. But Omega Rom, I cant install. Now i got 4.3 stock rom. My bootloader updated with knox. Warranty is also 1 but still omega rom causes same issue. The thing i wonder is, If i install stock rom with odin, does it also reinstall the original bootloader?
Also, after getting newer stock rom, i cannot flash the mj5 bootloader anymore. It says it is outdated. I guess i have MK9 from now on. And cant go to MJ5. I dont even have no idea anout how to compare them. I am a noob rom flasher. But I am not a noob googler. Even so, I cannot find definite knowledge about MJ5 bootloader
Usually when you flash trough Odin you get the bootloader that comes with the ROM... But perhaps they added some aditional verification or something like that to make sure you don't revert the bootloader to the old one (without knox)... Even then I don't understand why some ROMs work and others don't... Acording to Omega thread you did everything right... Have you ever used Mobile Odin instead of Odin?
No, I have never tried Moblie Odin.
Edit: I am back on Alliance Rom, i won't probably check here later on, u do not have to reply anymore.