Related
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit
I tried to install the illuminance Rom last night, and it kept getting stuck at the ATT logo. I reflashed back to stock did a master clear, flashed a stock 2.3.5 uckj3 gingerbread Rom with corn kernel v307 also ATT gingerbread boot loaders. I used CWM to install the ROM, it'll restart then get stuck and get stuck at the ATT logo....is there something I'm missing? I've installed other ROM and have had no issues until now?!?!
If you used Corn kernel, are you sure you where on RFS format and not ex4?
it was rfs format before I tried to install
Did you make the file (don't remember exactly wich) that disable Voodoo. There is no reason for it to bootloop. After you flashed stock did you let it boot up? Maybe try with Boog kernel to flash then flash wich ever kernel you want to use?
I'll try the boog kernel.....I also ensured that the lagfix for system and data was disabled through CWM recovery ....in the install instructions it stated that it would take awhile to boot, I let it set for two hours. One thing I noticed is that 150 jpegs were installed
Sent from my SAMSUNG-SGH-I897 using xda premium
Doubt this might be it but, If you set it on CWM to disable lag fix reboot in cwm then flash. Random thought.
LOL....did that also.
Sent from my SAMSUNG-SGH-I897 using xda premium
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
lilbigdude1 said:
Guess I'll start over clean again....
SGH-I897 Cappy
I897UCKJ3 2.3.5 Gingerbread
Corn kernel UCKJ3 V307
FASTY III V1 KJ3
Tegrak OC Ultimate
Click to expand...
Click to collapse
My boot getting stuck got fixed after Wipe data/factory reset in CWm, wipe cache, wipe Dalvik cache, - all three -then install illuminance. Tried that ? Starting from stock KJ3 no bootloaders.
Importantly: Can you boot with just Illuminance boog kernel (the one that comes wiht the ROM, no other kernel flashed)? I presume you cannot boot a fresh Illuminance install............if this is the case wiping as above should help.
I finally got illuminance to install, and is working great.
this may seem like over kill but everytime I flash a new ROM I start from scratch and flash to stock and master clear and then build from therethis is the first time that I ever had any issues by doing it this way. usually I have it setup up in 10 to 15 minutes it seems to save any issues later down the road as far as being buggy.
Glad to hear it
Hi, I tried to install Illuminance 1.1, but I think the file is corrupted. I downloaded it twice, from different locations, and its the same zip file.
I tried to decompress it before installing it, just to check file consistency, but lots of files can´t be decompressed.
Anyone had this problem? If not, any way /any where to safely download it?
Thanks!
In the Illuminance Rom Thread, in the OP, there is a link to IlluminatedOne's website, where u can find a good non-corrupted download and u will also find the installation instructions.
Not sure why u think u had a corrupted download ?? But u should b good to go once u get to the website.
As of this version 1.1 release, u should only be downloading the Illuminance Rom from said website.
Sent from i897uckj3
I downloaded my version from Mega-upload. I tried it again last night just for...you know....and received the same results of being stuck on the att logo for hours. as usual i flashed to stock and master cleared, GB boot loaders, reinstalled stock 2.3.5 and reinstalled luminance and before i rebooted i installed the samurai kernel, then rebooted and everything worked as normal....so being fairly new to the whole Dev scene i don't know why that would make a difference, but it works fine and it didn't get stuck on the att logo.
oh and thanks twin I'll try and go to the website and check it out
Update: Solved
Thank you for everyone's reply and help.
What worked for me:
Downloaded Mobile ODIN v3.10
Downloaded Goku v1.5-10 TAR (Kernel-Goku-V1.5-10.tar)
Flashed firmware with Mobile Odin with MD5 signature check
Can now boot into recovery
Currently on:
CM9 Version 9-20120515-Nightly-n7000
Build date Tue May 15 23:06:26
Kernel version 3.0.30-CM-q6804ca8
I cant seem to get into recovery while using any of the ICS roms. I've tried several CM9 bulds, Kindgroid, Stunner and a few others. I doesn't matter if i try to access it through the hardware keys (press and hold the Volume UP+Home+Power) or through one of the software options (reboot into recovery). After the samsung logo apears the screen will turn black. I'll have to restart the phone with the power key.
Everything else seems to be fine. I can get into download mode just fine. I have no problems downgrading to a gingerbread rom from pc odin or mobile odin. Also theirs no problem for me getting into recovery from any of the gingerbread roms I've tried.
I first noticed this while I was on ICS stunner. It was the build with the affected kernel. Everything was running smooth for me. Recovery and everything else seemed to be working fine but when i started reading posts about the brick scare i became afraid of doing anything else on that kernel.
I followed Entropy512's advise:
If you are running an affected kernel:
STOP USING IT IMMEDIATELY. FLASH A SAFE KERNEL USING ODIN/HEIMDALL.
DO NOT wipe in recovery
DO NOT flash anything else in recovery
In general, DO NOT use recovery at all
I flashed his DAFUQ releas using mobile odin while still on stunner. Everything seemed to go smooth. After flashing I checked under setting -> about phone -> kernal version and his kernel was properly displayed. I tried going into recovery but the screen would turn black after the samsung logo.
I've must of done something wrong while flashing Entropy512's kernel because ever since I flashed his kernel I havent been able to get into recovery while running an ICS rom.
TL;DR
Cant access recovery from ICS roms but recovery works fine while on gingerbread roms
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
jonpaslim said:
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
Click to expand...
Click to collapse
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
runnin4mayor said:
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
Click to expand...
Click to collapse
How about 4 wipes including format/system and also use jbroid even though your not installing a kernel but rom still use it.
Flash stock GB rom. Reroot it and then check everything is working fine? If yes then flash ICS rom.
Sent from my GT-N7000 using XDA Premium App
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
jonpaslim said:
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
Click to expand...
Click to collapse
Yes.. I've tried that before installing my current ICS rom. Actually I formatted both the internal and external SD while still on GB. I'm still wondering if the recovery stored in the same partition space in both GB and ICS. I can't understand why I can access CWM recovery on GB but not while I'm on ICS.
i too have the same problem even though i can access cwm manually cant install any zip file but if i use abyssnote kernell everything works fine the problem started when switched over to ics from gb
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
Wiping more than once is pointless... I don't know where people get silly ideas like "wipe 3 times".
When you switched to something else, did you flash it using CWM or Odin?
Try flashing a different kernel using Odin. I have seen that in rare cases on some devices, doing something like the following:
Flash one kernel from a recovery
Reboot directly to recovery using CWM's Advanced menu
At this point, the device will be stuck either always booting to recovery or never booting to recovery
Flashing a kernel with Odin/Heimdall - NOT "Mobile Odin" (I hate that name because it's completely different from Odin) or CWM often breaks these loops.
problem accessing recovery
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Thank you sir for your swift action.
deepalakshmidas said:
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Click to expand...
Click to collapse
How did you flash abyssnote kernel without being able to enter recovery?
Edit: Solved my problem. Updated 1st post
Hi I was running Helly Bean and I was experiencing some lag that i couldnt fix so i decided it was time to start fresh (phone was getting to be a mess anyways) so i formatted my phone and one-click to a stock rom. (rogers i896 2.3.3 with bootloader). I used heimdell to flash kernel with recovery, then flashed devil kernel, reboot recovery, then flashed helly bean as per thread instruction and my phone kept booting into recovery only. So i tried to start over 2 more times with the same results, I even tried to flash CM9 stable release and it yielded the same results.
Can anyone shed some light as to what i messed up? My only option now is to use stock app since i cant seem to get anything else to work...(pleas dont make me go back to touchwiz)
Any help is appreciated,
Thanks.
PS phone works fine on stock rom
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
korockinout13 said:
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
Click to expand...
Click to collapse
Thanks, works first time!!! Looks like im going to have IMEI problems but thats another battle lol
odin to stock 2.3.6, charge to 100%, then go to recovery, 4w, 2f, then install helly bean.
just went thru this last week.... accidentally flashed incorrect ROM to Captivate and phone started acting wiered.
Then came to know i have the wrong bootloaders and kernel. Just installed GB bootloaders and phone started booting to recovery.
then tried to flash ics rom and soft bricked my phone.
Used the "hold both volume buttons and plugin the USB cable to computer" to get into download. then ODIN to stock GB. then used KKroot and then flashed Slim ICS. Now the phone works great.
Hi guys
My friend has a Galaxy Ace running Froyo 2.2, everything went so OK till he tried to update into Gingerbread 2.3.4 via Odin & cooper
Device boots well and everything is smoothly good, but when he tried to access WiFi, it not works yet!!! The Bluetooth stopped working too
Tried to give him another version of GB 2.3.6 also flashable via Odin, nothing changed!! Tried to flash 4.2.2 CyanogenMod, thinking it's a Kernel issue, nothing changed too still not working
any help?!!
TeraXimoS said:
Hi guys
My friend has a Galaxy Ace running Froyo 2.2, everything went so OK till he tried to update into Gingerbread 2.3.4 via Odin & cooper
Device boots well and everything is smoothly good, but when he tried to access WiFi, it not works yet!!! The Bluetooth stopped working too
Tried to give him another version of GB 2.3.6 also flashable via Odin, nothing changed!! Tried to flash 4.2.2 CyanogenMod, thinking it's a Kernel issue, nothing changed too still not working
any help?!!
Click to expand...
Click to collapse
Flash a fresh stock via Odin and then do wipe data/factory reset and wipe cache partition if it doesn't work you could try to flash CF-Root b84 kernel over android gingerbread it contains useful libs and wifi modules
Recently he told me something strange!!!
he flashed CyanogenMod 4.2.2 without being rooted yet!!! only custom recovery was installed.... can it be strange??
TeraXimoS said:
Recently he told me something strange!!!
he flashed CyanogenMod 4.2.2 without being rooted yet!!! only custom recovery was installed.... can it be strange??
Click to expand...
Click to collapse
No, but I don't like this method CM roms are pre-rooted
Tried to flash the Kernel with CWM first time. It says installtion aborted
so Flashed another version of CWM and tried again.. it flashed successfully but WiFi still doesnt work at any case
Any help??
TeraXimoS said:
Tried to flash the Kernel with CWM first time. It says installtion aborted
so Flashed another version of CWM and tried again.. it flashed successfully but WiFi still doesnt work at any case
Any help??
Click to expand...
Click to collapse
...do 3 wipes via CWM 5.0.2.6 FIXED and then use Odin to flash a fresh stock finally do wipe data/factory reset and cache partition. Check out if your wifi works, if not flash ROOT + CWM and finally flash Cf-Root b84. If your wifi still not working, It might be a hardware trouble
Can it really be a hardware fail?? Everything was working PERFECTLY just before update!!
Up
TeraXimoS said:
Up
Click to expand...
Click to collapse
Try dialing *#*#526#*#* in Stock rom