hi all, i have an insteresting problem while upgrading from GB 2.3.6 to ICS.
i tried all the versions of kernels and ROM's here and was unable to find a solution.
1. when i am on GB i go into CWM, do all the possible wipes
2. i install from SD the new ICS version
3. after the installation i do all the wipes again
4. then i reset the device.
each time, the device is showing me the startup animation and then i get a screen saying that the encryption was unsuccessful.
nothing helped from there, i did wipe to factory default again - did not help, i re-flashed again - nothing helped.
i am stuck on GB without being able to use the good ROM's we have in this forum.
please help if you can.
thanks in advanced.
Did u try slim ICS rom http://forum.xda-developers.com/showthread.php?t=1488096
Boot into recovery(CWM)
Do factory reset
Wipe cache
wipe dalvik cache
Flash the base file
Flash the essentials file
wipe dalvik cache
reboot
no, did not work.
after i finished all the steps the device started with the boot animation and again - encryption unsuccessful .
BTW, an interesting issue, after the encryption unsuccessful i got the device back into recovery mode and when i tried to load another zip from the sdcard i got an error in the device saying that my sdcard cannot be found.
any solution to that?
Did you check this thread ?
http://forum.xda-developers.com/showthread.php?t=1447303
i have done this a long time ago.
and got to step 9, which afterwards i was supposed to have the ICS working but still i got the "encryption unsuccessful " error.
i was actually looking also for ICS files to use via Odin (maybe that will solve the problem) but did not found any.
Try asking in the same thread abouth the encryption error
dvdscr said:
hi all, i have an insteresting problem while upgrading from GB 2.3.6 to ICS.
i tried all the versions of kernels and ROM's here and was unable to find a solution.
1. when i am on GB i go into CWM, do all the possible wipes
2. i install from SD the new ICS version
3. after the installation i do all the wipes again
4. then i reset the device.
each time, the device is showing me the startup animation and then i get a screen saying that the encryption was unsuccessful.
nothing helped from there, i did wipe to factory default again - did not help, i re-flashed again - nothing helped.
i am stuck on GB without being able to use the good ROM's we have in this forum.
please help if you can.
thanks in advanced.
Click to expand...
Click to collapse
From jvu, to install Slim ICS 2.8, in cwm factory reset/wipe cache/wipe delvik/format system/format cache/format datadata , flash 2.8 Essentials i9000 first then Base 2.8 (if bootloops pullout battery, put it back, enter recovery, reset, wipe, flash base again) and then Essentials again.
Related
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me
Hi,
I read many posts about external_sd not detected properly on MIUI Roms..
Recently someone advised me to put GINGERBREAD bootloader first in order to have external_sd recognized correctly:
http://www.galnetmiui.co.uk/content/...l-not-detected
What I did tried so far:
1. http://forum.xda-developers.com/show....php?t=1089989
Download the right version from section above
Reboot your phone into Download mode
Connect your phone to computer
Run EZOdin
Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5 as a PDA file in EZOdin
Check the "Phone Bootloader Update" checkbox
Click Start
Wait until phone reboots and make it reboot into Recovery
Flash a custom CWM ROM
2. Then flashed Galnet 2.3.2b stable
but right after that I ended up in a bootloop. Only when I remove memory card, it finishes installation.. But with the same problem...
Please can you advise me with step-by-step instructions how to do that correctly ? (flashing correct GB bootloader and then MIUI rom...)
Thanks a lot!
cosmo
I installed miui and had this problem. I wiped cache dalvick cache and did a factory reset and reinstalled miui and now it works fine.
Sent from my GT-I9000 using XDA
_brymo_ said:
I installed miui and had this problem. I wiped cache dalvick cache and did a factory reset and reinstalled miui and now it works fine.
Click to expand...
Click to collapse
Really ? MIUI without GB bootloader doesn't support external_sd mounting. It is well described in many articles online. Which is exactly my case.
Can you please reply to me with step-by-step instructions what you did ?
Don't forget to mention FROM which ROM version did you do the upgrade and TO which version alsol...
thanks!
Hi,
I have many times tried to flash CM7, but always happens weird thing.
I have stock 2.3.5 XXJVS with Semaphore 2.5.0 kernel
1.I boot into CWM
2.I wipe cache then wipe data/factory reset then i go advanced and choose wipe Dalvik cache
3.Choose .zip from sd card
4.I choose update-cm7.1.0-GalaxyS-signed.zip
5.My phone flashes it
6.It reboots
7.Normal Galaxy S GT-i9000 then Galaxy S
Cyanogen Mod
8.It goes to recovery and posts text very fast then reboots again
9.It repeats everything what it does from section 7.
Im very confused so please help!
Have you tried flashing it again?
redo step 3 and onwards,
sometimes you just need to flash twice.
It seems like a corrupted download... Are you flashing from internal or external? Have you mounted before?
i tried to flash from internal
What version of CWM recovery do you have? Maybe flash a different ROM just to update CWM, and then flash the rom you want?
I had the same, or atleast a similar problem whilst trying to flash CM9. I fixed it by flashing the rom again.
You also might want to redownload the file incase it's corrupt.
i have CWM 5.0.2.7 and i downloaded the CyanogenMod file again so i try to flash it again
Any luck with your efforts this far?
yes, i succesfully installed CM9 about 3 months ago.
I'm not sure which build it was but it was the newest build
I wanted to flash custom rom on my galaxy S. I flashed clean rom, then kernel with CWM, but there is a problem. Everytime I try to flash rom it ends with bootloop. I tried cm7, cm10, rootbox, miui 2.4. Every time is the same. It starts installing (only few secodns), then screen becames brighter, then restart and bootloop. I tried different kernels, roms but still same result.
ps. sorry for my english
Hi, here is a great guide to fix bootloops:
http://forum.xda-developers.com/showthread.php?t=1660596
Usually, doing factory reset, wipe cache and wipe dalvik cache before and after intalling the ROM should fix the issue though.
I'm doing all necessary wipes, I can recover from bootloop easly but I want flash custom rom and I can't. Istalling zip lasts few second, not few minutes, there is a problem.
Sorry if this is too basic, but are you using the right ROM for your phone?
of course...
I don't know if I'll be able to help you, but can you please list the exact model of your phone just in case? You can see the different variants here:
http://en.wikipedia.org/wiki/Samsung_Galaxy_S#Variants
It is just GT-I9000. Now I managed to flash CM7.2 but if I want install CM9 or CM10 im getting bootloop and can't enter recovery mode ;o
Sorry, I can't really give you an answer with that information. If you are following the steps in each ROMs thread, you should have no problems patching as far as I know (someone more knowledgeable than me may say otherwise).
Maybe posting the exact steps you are following would help me or others to find out what the issue is.
I'm following right steps. It's not my first phone. I know how it should be but it isn't. Here are my steps:
Flash stock ROM w/ODIN v1.85 - OK
Flash CF-Root w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.1.0 from CM site)
Flash completes in just a few seconds
Phone reboots automatically
Now stuck in boot loop
Remove battery
Go to CWM again and reflash CM7.1 zip
Now i have CM7
Reboot to recovery, facotry reset, wipe cache, wipe dalvik
Flash CM9/CM10, finishes in few sec, reboots, then black screen, can't go to recovery mode ;(((
Flashing stock with odin again...and every time is the same, sometimes when I choose CM10 i see info: "Incompatible Partition Layout" so it may be the reason (something with partition, idk)
My phone has never rebooted like that, so I'm not sure what the problem is. I do know I use ODIN v3.07. I also have CWM 6.0.2.7
Best of luck finding a solution, sorry I could no be of more help.
I think CWM6 would help but I can't find this version for cm7
IGNORE ALL LINKS BELOW, they are for the wrong phone
I don't think it matters what CM you have on your phone, you should be able to upgrade CWM from recovery: Maybe not in i9000...
http://forum.xda-developers.com/showthread.php?t=1843825
Doesn't work in i9000 as far as I can tell: You can also try installing TWRP, which I like better than CWM and have in a different device:
http://forum.xda-developers.com/showthread.php?t=1694617
Finally, and don't take me on this because is just a guess, maybe your bootloader is not working properly? I don't really remember how to do this myself:
You are showing me links to CMW and TWRP for i9001, I have i9000...
You are right, please ignore those links... I do know I patched CWM 6.0.2.7 through ODIN on my phone, so maybe that's the only way. In any case, I'll let you look for the actual links.