Hi all,
A few weeks back , While trying to restore a Nandroid backup of rooted 2.3.6 Gingerbread Samsung stock XXJVU firmware, I accidentally ended up bricking my device. On of the helpful community members at XDA directed me to flash with Ezbase here and I could get my phone up and running. I stopped trying ICS roms back then, but I'd like to try a few ones now, particularly TiramiSlim v2. Can I flash the ROM right away from CWM recovery( it's not the latest version ) on top of the EZBase 2.3.3 that I am running right now or should I first restore my Nandroid backup to get to Gingerbread 2.6.6 XXJVU before flashing ?
No you can go straight ahead just remember backup efs and when going from GB to ICS the phone will reboot half way through install just go back into recovery and reflash
Sent from my Awesome I9000 running Slim Bean
Hampstead. teduredi
Latrop said:
No you can go straight ahead just remember backup efs and when going from GB to ICS the phone will reboot half way through install just go back into recovery and reflash
Sent from my Awesome I9000 running Slim Bean
Click to expand...
Click to collapse
Hey thanks for the reply. I tried to flash a CM9 nightly by going into CWM and tried to install the zip from sd card(after wiping cache and data 2-3 times) but every time, the phone shuts down seconds after the installation begins. After this the phone continues to run in a bootloop (the cyanogen splash screen followed by a very quick flash of some scrolling text ) and i cannot even enter recovery. I have to flash the EZbase ROM and then the CFROOT kernel again to get to CWM and on reflashing the entire cycle repeats itself. Any ideas why this could be happening ?
You have to remove the battery then enter cwm then reflash it reboots due to a change in the partition table
Sent from my Awesome I9000 running Slim Bean
Related
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
skiddyrow said:
Would appreciate if someone could help me with my problem - I had earlier used CF-Root to root and install recovery which went off well, took a nandroid backup and then tried to flash CM9 through recovery. WIthin a few seconds it rebooted, showed the Cyanogenmod splash screen and went back into recovery - only this time it was a newer recovery (6.0.0.2) than what CF-Root had installed. I'm not able to install through zip file and for some reason I am not able to restore from nandroid as it says the md5 does not match. So as of now I am stuck in recovery.
To add to this, I realize that I messed up as the instructions said to update to a GB rom if coming from Froyo, which I did not notice. Any idea what I can do from here? If I can still run through this process can someone point me in the direction of a suitable GB ROM I can install? My end goal is to be on CM9, but right now would just be happy to get back to the stock GB ROM as well.
Click to expand...
Click to collapse
you better use the overcome stock gingerbread safe 5 (the best stock for all situations) google overcome.com and get the files, you will find also a tutorial for how to stock your tab before updating it to overcome or cm9 etc...
If I helped you, please press the thanks button
MarlX said:
Flash to the stock firmware again? at SamMobile? That is what I did when my device did not boot up after installing CWM recovery and some rom.
Click to expand...
Click to collapse
so the reflash from scratch works for you
If I helped you, please press the thanks button
Thanks sos_sifou - worked great! I think I'll stick with the Overcome GB ROM for a while as it works pretty good, and look at CM9 / 10 whenever it gets stable!
Hi guys
Recently I installed CM10 jelly bean coming from CM9, everything worked well untill i realised that I didnt do a back up for my apps.
I had done a nandroid back up before coming to CM10, so i decided to go back to cm9 and get my apps back. This came up with an error.
So i thought it didnt work because i was on cm10, i downloaded cm9 again and installed it.
Nandroid back up worked, but now phone will not turn on samsung galaxy s screen just flashes.
I cant get into recovery only download.
Please help!
Hey
No issues...just downgrade to 2.3.6 using odin (Link Given Below) & root it..
Then flash CM9..reboot..
after the first boot goto CWM using the 3-button combo and restore from your nandroid backup..
Done..
Before flashing stock rom, download the newest Semaphore kernel and flash it using Odin (only PDA file, repartition NOT ticked). It may boot properly or at least it will get you to CWM
Cool123454 said:
Hi guys
Recently I installed CM10 jelly bean coming from CM9, everything worked well untill i realised that I didnt do a back up for my apps.
I had done a nandroid back up before coming to CM10, so i decided to go back to cm9 and get my apps back. This came up with an error.
So i thought it didnt work because i was on cm10, i downloaded cm9 again and installed it.
Nandroid back up worked, but now phone will not turn on samsung galaxy s screen just flashes.
I cant get into recovery only download.
Please help!
Click to expand...
Click to collapse
I had same issue when I flash JB Rom in first time.
When I feel ICS is better than JB(in this moment,I know JB will keeping improve).
FYR,my way as below to back to ICS and everything is come back.
1. In to recovery
2.do a 3wipe
3.falsh cm9(what you want),when flash completed reboot system.
4.Into desktop and run untill system is satble.
5.reboot phone to recovery
6.make a nadroid backup now
7.reboot phone.
8.reboot to recovery
9. restore previous backup data
final get a beer to celebration .
4.
Thanks guys solved it
I have had my captivate for a while now and I have had a few problems with flashing Cyanogen based Roms since I went to CM7 then back to stock a while back.
I had CM7 running fine and went up to CM9 for months. I just recently went to REMics and had a problem with the sound and at the same time I had problems with my power button I the flashed to Paranoid Android for a few hours and was driving around so I took my phone to the AT&T warranty center to see about them replacing it and im out of warranty so I had them flash it to stock now I cant get my phone to CM7 I can get it to run Serendipity just fine but no CM7 can someone PLEASE help? It seems like I need to COMPLETELY clear the phone of all old rom data. Any solutions?
Try using one of these Stock I897UCKK4 Android 2.3.5 One Clicks and then flash the KK4 Corn Kernel version 7.0A to get the CWM Recovery u need to move on to what you are wanting to flash per that Rom's specific install instructions.
Done that
I have put my phone back to stock KK4 with and without bootloader. I had this problem before when I was going to CM7 the second time. Its just getting SO annoying now. Thanks though!
I forgot to say that when I go to flash the rom through CWM it starts reboots the phone the samsung Cyanogen screen comes up flashes onces then goes into CWM flashes a few things quickly and the last image I see is the "dead" androind laying on its back with the sign aboveits open front door.
I'm starting to think there is no help. Maybe I can trade my friend my captivate for his.
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
jmtheiss said:
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
Click to expand...
Click to collapse
I have tried with cm9 but not 7. I will try that once I get sick of Serendipity. I just set everything back up on this rom and installed my apps so I will wait a few more days.
Thanks You!
Hi there.
I am trying to install 4.1.1 Rom, and I've got this problem, no matters which rom I choose. Here are the steps I follow:
1.- Install Official 2.3.6 firmware with Odin
2.- Install Clockworkmod with Odin
3.- Go into Recovery Mode and follow the install instructions from the ROM (wipe data..., install from sd card)
4.- And here it goes. I got "Samsung Galaxy Logo - ROM Logo - Installation init" again and again. The installation shows log messages that I don't have enough time to read (something about E unknown, or can't mount. I've tried flashing with dbdata.rfs.tar, but with no luck)
Any help? Thanks in advance.
Reflash you have to flash twice and also I recommend flashing on top is cm not GB as it seems to stop imei issues
Sent from my Awesome I9000 running Slim Bean
Keep pressed the Recovery Combo until you see the Samsung Galaxy S first screen. It will force to enter Recovery mode.
Then wipe again and reflash
Instead of directly installing clockwork mod, install the cf-root kernel instead, which gives you root and CWM. That's what I normally do anyway.
He/ She doesn't need too there flashing straight to another ROM don't need root
Sent from my Awesome I9000 running Slim Bean
Thank you all for the replies.
I'll try them tonight and I'll let you know if it works out
It does that to me everytime I want to upgrade frome Gb to ICS or ICS to JB
I pull out the battery to stop the bootloop, then put it back in and get in recovery mode with three-buttons combo, then flash again the rom, it shouldnt bootloop again.
I started with last solution (remove battery and flash rom again) and it has worked out! The thing is that after removing the battery and flashing it again, "another" recovery mod is loaded and then it all goes perfect. So, thanks all for the help!
Yes as it changes the partition table and needs a different recovery to handle it properly
Sent from my Awesome I9000 running Slim Bean
Just got my Galaxy S back from my Mum today (After I bricked it and sent for repair) she got a note2 omg... Decided to flash a custom rom..
Here goes..
First I followed this guide completelyhttp://http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. After I flash the CM 10, my recovery was upgraded to v6.0.1.5 after reboot. But I cannot get pass the recovery. I will have the cm boot animation, then back to recovery again. Tried reflashing the rom, doesnt say any errors but still gets stuck at recovery.
Then I went thru the method at the wiki.cyanogenmod again and successfully flashed cwm recovery 2.5 again. Tried flashing the CM10 rom again but this time round, It shows a long error message ending with "status 7"
I am still able to go into download mode.
Was on stock unrooted 2.3.3 DXJV9.
I made the super no.1 noob mistake of not making a backup........... But, why is rooting and flashing of this phone so hard.....
Pls, any help is greatly appreciated.
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
It will work
scpion said:
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
Click to expand...
Click to collapse
When u see red error message in stock recovery........u just wipe cache and reboot.......it will work.....
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
try this
scpion said:
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
Click to expand...
Click to collapse
U just use GB jw4(your region) ROM (don't use single file like PDA).........you use files separately like this [PDA,phone,CSC,pit(512 or 513)]...............use Odin 1.85 for flashing files......,when u complete the flashing it automatically reboot to fulfill the flashing...........then also it gives red error means........ clear only wipe cache and don't clear wipe all data...........reboot your system..... I think this will work for u...........:fingers-crossed:
Thanks. Have it solved. Flashed with another rom with seperate files. I was using the the all in one previously. Got it to run CM10 nightly though till now still not too sure how... But, I m real happy now. It works great so far and I couldnt understand why Sammy refuse to roll out official ones even for 4.0..
Still trying to figure out how to root, flash SGS though.. I have done so for many other device but by far,... this phone is the most complicating....
Aj rocker root
By processor only we not getting stock ICS rom but we getting custom ROM by hacking processor.............
For rooting the ROM u want to be in stock GB ROM like 2.3.5 or 2.3.6 and then u want to download this file(http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip)............. after download u want to open Odin 1.85 and select PDA then choose the downloaded file...........select start to flash the file.........reboot and enjoy the root bosssss......if u like this press thanks:fingers-crossed:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Try to see if you can flash another custom Rom, if that works then it could be that your files are corrupted..
Have you stated your problem over at CM forums..
# Sent from my blazing slimbean SGS i9000 using Tapatalk 2 #
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
Most times from GB to JB u have 2 flash custom 2, 3 times. So its normal when flashing custom the first time it takes u to bootanimation and hangs (take out battery and go to recovery with 3 button combo and flash again till it says install is completed) or directly into recovery.
If u wanna flash other jb rom just full wipe and flash new custom. Make sure u make a nandroid backup so u can go back easily