Quick question:
Running stock ROM, rooted, Voodoo enabled, ext4, etc. I want to do a FULL backup and try other ROMS but I want to make sure I can FULLY restore to my current ROM later.
1. If you do a FULL backup with CWM (red or green), would I be able to do a full flawless restore later?
2. What are the major differences between Green and Red CWM? I did a backup with both and the one i did with RED was a bit larger than the one I did with Green.
Any info on steps to properly backup and restore?
Excellent question. I've been wondering this myself
Post Infused by Infuse
I have a related question - which model are you supposed to select when flashing Cwm to the Infuse? There are two i9000 options - what is the difference between the two?
Very strange issue.
I cannot upgrade my ROM above 2.3.3 and I can't upgrade the Recovery Image to anything new as well.
Does not matter if Official ROM or Not.
I am grabbing the Official ROMs from here:
http://forum.xda-developers.com/showthread.php?t=1445570
I am currently with Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
and If I try to install, 2.3.4, 2.3.6, or 4.03 the phone wont get past the "Google Logo" right from the beginning of boot. The screen will go Blank and the 4 soft keys will light up.
Before installing each ROM I am formatting/wiping cache, data, system & dalvik.
And Each ROM installation will claim that it installed successfully.
Recovery: So I am able to install ClockWork Recovery 3.0.2.4 and have it work.
I install the latest Clockwork ver. 5.0.2.0 it will install successfully, but not work.
And stop right after the Google Logo, as with ROM.
I have been at this for 2 days now. Any help would be AMAZING!!!
One last note: The phone was dropped, so maybe some how related, but I don't see how. The phone just came back from store that replaced the LCD. They claimed it was in a Recovery Loop. So I asked them to put CynogenMod. However they strangely put CynogenMod v 2.3.1 and not rooted.
are you flashing the right cwm recovery 5.x.x.x for your phone(amoled vs lcd)? try twrp recovery. do you wipe data(factory reset)before flashing? you should.
to Start, Thank you for the reply. Its very much appreciated.
So Yes, I am performing a full factory reset before flashing. And all of my most recent trials I used the native factory recovery that comes with each of the ROM's.
And I tried all of the below listed ROMs with the issue as described abouve.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
And regards to the Custom Recovery(cwm) issue, I used what on the CynogenMod Wiki:
wiki(dot)cyanogenmod(dot)com/wiki/Nexus_S:_Full_Update_Guide
They don't have any differenciation between the OMOLED or Super LCD Versions:
(OMOLED I9020T, I9020A)
(Super LCD I9023)
Is there in fact different Recovery's for each of the abouve listed models????
Where would I find those recoverys?
And thank you again for your time.
Help - anyone? - Please :-(
vringo said:
Help - anyone? - Please :-(
Click to expand...
Click to collapse
try using twrp recovery, i find it more useful than clockwork recovery http://teamw.in/project/twrp2
---------- Post added at 04:26 PM ---------- Previous post was at 04:18 PM ----------
if you want to flash the official 4.0.3, then you need to flash the official 2.3.6 first. if youre flashing a custom 4.0.3, like cm9, then you dont need 2.3.6.
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
vringo said:
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
Click to expand...
Click to collapse
you should be able to. try a custom rom instead of an official. lots of aosp builds in the development section. they are pretty much pure android with a few mods. theres a pure aosp build in the development section too, its pure android 4.0.3 without mods. your bootloader is unlocked, right?
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
vringo said:
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
Click to expand...
Click to collapse
good luck
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
vringo said:
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
Click to expand...
Click to collapse
One more thing, anyway to know if the store that fixed my phone installed the wrong screen? LCD vs OMOLED?
clarification of the "issue" if ROM not working.
- Working phone (with 2.3.3) boot description:
You see Google Logo, and then the Logo will flicker momentarily, and Google Logo some more, and then the flying colored NEXUS logo animation, etc...
- Non functioning ROM boot description: You see the Google Logo, and then at about the time you would see the Google Logo flicker, that is when the screen goes black, and all 4 soft-keys light up. if you push the power button, sometimes the soft-keys will go black, and if you push again, light up again. At this point I have to pull the battery....
Same issue if I try to load the stock recovery from a non-functioning ROM. so Fastboot Mode will work, and then select Recovery, Google logo and then Black, with 4 lit softkeys, where the logo would normally flicker.
Why can't I install the stock firmware above 2.3.3????
I just tried the update ROM from 2.3.3 to 2.3.4 or 2.3.3 to 2.3.6 (all GRI40)
What could cause this issue????
could it be a partioning issue? what would cause such a weird issue?
Ive installed this NAND ROM according to the video and descriptions on the posts while i was using windows mobile: http://forum.xda-developers.com/showthread.php?t=769026
Now i want to have a backup the rom on my phone but i cant access cwm screen from magdr menu. When i go to the 8. option, which i used in order to launch cwm screen for the first time flashing of hyperdroid, but it says "invalid boot image header".
How can i access the cwm screen after installing HyperDroid CM7 MadMamba-v5.7.0 in order to have a back up? Or how can i get the backup of my rom?
Thanks.
Good evening/moring/day, dear community!
I have a problem occured with my deivce.
No it's not bricked... not completely. It's rooted, and I have tried different ROMs (atomic, Alacritous, stock). But after flashing gaple rom v1.1 (which is great, big thanks to bochan, (thumbs up)) - a problem occured. Now, I can't flash any different rom - either Alacritous or Inspiration rom. (for example)
After a re-flash of any different ROM, it boots fine, but during the samsung logo, the phone fades to a white screen and seems to freeze. A bit later it starts to vibrate (typycal "force close" gesture). Yes, I did format data/cache and did a full wipe, prior to flashing. What is strange that no other ROM seems to work - other than gaple v1.1
So, the questions are:
1)What I might be doing wrong
2)What causes a typical white boot (or fading to white, to be more specific)
3)Is it possible (or a good idea) to format phone completely (all internal memory) and start from scratch?
4) -any other suggestions are welcome.
Thank you in advance!
_________________
edit: (in case needed)
Model: GT-S7500
baseband: S7500XXLD2
CWM: recovery 6.0.1.2 (from atomods, by bochan)
xtreeme said:
Good evening/moring/day, dear community!
I have a problem occured with my deivce.
No it's not bricked... not completely. It's rooted, and I have tried different ROMs (atomic, Alacritous, stock). But after flashing gaple rom v1.1 (which is great, big thanks to bochan, (thumbs up)) - a problem occured. Now, I can't flash any different rom - either Alacritous or Inspiration rom. (for example)
After a re-flash of any different ROM, it boots fine, but during the samsung logo, the phone fades to a white screen and seems to freeze. A bit later it starts to vibrate (typycal "force close" gesture). Yes, I did format data/cache and did a full wipe, prior to flashing. What is strange that no other ROM seems to work - other than gaple v1.1
So, the questions are:
1)What I might be doing wrong
2)What causes a typical white boot (or fading to white, to be more specific)
3)Is it possible (or a good idea) to format phone completely (all internal memory) and start from scratch?
4) -any other suggestions are welcome.
Thank you in advance!
_________________
edit: (in case needed)
Model: GT-S7500
baseband: S7500XXLD2
CWM: recovery 6.0.1.2 (from atomods, by bochan)
Click to expand...
Click to collapse
you have soft bricked
you must flash stock rom from odin
then the roms will work fine
but after flashing stock rom
you must again root cwm , blah blah
hope you get me
amanmehta007 said:
you have soft bricked
you must flash stock rom from odin
then the roms will work fine
but after flashing stock rom
you must again root cwm , blah blah
hope you get me
Click to expand...
Click to collapse
yes try flash a stock rom with full wipe
oh, I'll try, thank you both for a quick reply!
+++++++++++++++++
I'm a bit confused - is it still a considered a "soft brick" if I do manage to use my phone, just only one specific ROM?
_________________________
UPDATE:
I reflashed stock rom with ODIN (worked fine) but I still can't flash other custom roms.
as a workaround, i flashed custim rom, and then atomods, where reflashed kernel... seemed to work for some reason -.-
can not get in download mode
my phone is stuck on boot loop, only samsung logo appears and the phone vibrate.
I can not get into recovery or download mode in order to flash or hard reset.
please help
I tried to update from CM10.1(can't remember date) to the latest nightly (using Cyanogen's built in update service) on my HTC One S. Everything was installing fine, phone restarted and this blue screen has now shown up. Any ideas? Or is that for my phone? Thanks.
Can you get to recovery? If so, try to flash it from there and then fastboot flash boot.img if you are S-on.
You also might want to wipe system, data and cashes before, since CM 10.1 and 10.2 are on different Android versions.