Related
Normally I wouldn't post a thread, searching is quicker & requires less hanging around...but I am at my wits end now!
I am trying to install a new ROM on my phone but everything I try causes me issues.
I have got to the stage where I am trying to install a ROM (Darkyys). I have downloaded the ROM and put it into my internal SD card, home directory.
I have installed ROM manager, flashed clockworkMOD Recovery, and have restarted into recovery mode from that.
Now, the recovery mode is blue writing (if that helps).
I have cleared everything & go down to ''apply sdcard:update.zip'' and I get an error message which says:
'' E:signature verification failed. Installation aborted.''
Now, I have googled every tutorial, every error message and nothing has brought details up on how I get out of this loop.
Can anyone shed any light on it?
Cheers guys
edit: The recovery mode is 3e, and has - For BML - on it, if it helps?
the blue writing,, i think that is stock recovery mode, u need to get clockworkMod you will have to download that and flash it through recovery using the process you have already been trying for darkys rom..
when you have clockwork mod, your selecting the wrong thing. you wanna select update from sd card. then select chooze zip from sd card. then there you will see darkys rom (looks something like Darkyys vXX-wipe version.....zip)
Thanks for the post mate, the only options I have are;
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal SD-card
Which is what's throwing me off currently!
yes get yourself clockworkMod from here: http://www.multiupload.com/5CUIK88JM0
once downloaded put it on your sd card (internal) then apply sdcard:update.zip ( you may need to do this more than once) when its done the recovery menu will be different. than you can flash darkyys ROM
When I open ROm Manager, the top link says 'Flash ClockworkMod Recovery', I select this first and it seems to install it fine. Below it ssays:
Current Recovery: ClockworkMod 2.5.1.1
Latest Recovery: ClockworkMod 2.5.1.1
Selecting the option below to 'Reboot into recovery' just brings me back tot he blue writing above!
edit: Ill try that now, thanks mate!
Thanks mate, though I am now getting the error message:
E: Failed to verify whole-file signature
E: signature verification failed
Installation Aborted.
Damn
thats weird.. what version of darkys rom are you trying to flash, you could try flashing speedMod kernel thru ODIN, takes 10 seconds and will remove standard recovery and replace with clockworkMod. then you can flash any rom you want. and even option to root/unroot.. built in lagfix and tweaks. very good kernel im running it now.
The latest version...8.0. I cant even get to the stage of the flashing the ROM though, the recovery mode is just not playing ball.
I have spent all evening trying to sort this, I don't suppose you could give me a brief run down on ODIN could you? Searching brings up everything under the sun!
edit: I am downloading it now.
your downloading what ?
I have downloaded ODIN, but am struggling to find instructions on it. I can gather it is another form of installing a ROM onto the phone, but you need to do so in the download mode?
edit: downloaded ODIN, have the .pit file and the .tar file in a separate folder, how do I flash the ROM...is that done using ODIN? Sorry for the questions, struggling to find usable instructions that explain the steps properly.
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
Thats step by step guide to flashing a kernel.. that will put CWM as default recovery.. you dont have to keep the kernel as darkys 8.0 has its own built in voodoo kernel which is also really good.
but flash the kernel in the link above first ^^^ as that will allow you to flash anything you want thru CWM then you shudnt need to use ODIN again really..
Cwm only works on 2e recovery not 3e. Download cf root for your firmware and flash it with odin. Put the cf root file in the pda section and do nothing else. Put phone in download mode, connect to computer and hit start on odin. Done. You will have 2e recovery and can now flash darkys or other.
Sent from my GT-I9000 using XDA App
thats another way of doing it yes. thanks for pointing that out sxi200
cf-root attached,
I ran ODIN & followed those instructions to the letter. My phone has been sat there for 10mins now and ODIN hasn't changed off 'SetupConnection'.
How long does this take, is it normal? Thanks again for your help!
I take that file, put it in ODIN folder & select it instead of the speedmode Kernal?
are you trying to flash darkys WIPE version or NO WIPE version ?? flashing a kernel only takes ten seconds.. does it not say pass in the top box on ODIN ??
Andehh said:
I take that file, put it in ODIN folder & select it instead of the speedmode Kernal?
Click to expand...
Click to collapse
yes u have to extract it first to get the .tar file
Some progress, I have got the 2e recovery mode now. I went to apply sdcard:update.zip, hoping to change the recovery mode over to CWM...but it only looped back to where it was before...the 2e recovery screen with apply sd card, reboot, and wipe data & cache being displayed.
Tried it for a second time & I am now in the CWM recovery mode, with the green lettering. Only issue now is I can't select (using home button) any of the options, i can scroll up and down though!
edit: power button does select, not home...seems to be doing something now! Will report back shortly!
haha that got me first time i installed CWM if you flash ROM it can take a while to boot, sometimes on my phone upto 15-20mins so dont panic if your phone doesnt respond, just keep your eye on the writing on CWM once it says update complete / successful all is good.. it will boot eventually.
I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.
when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.
Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!
I was running "TheMIDTeam 1.3" ROM & decided to upgrade to version 1.4 using the so call "safe" method using the "restore" method in CWM. unfortunatly this failed making my phone un bootable but I could still get into "download" mode.
I then thought I'd flash a stock ROM using odin and go from there. I chose the Taiwan N7000ZSLPF_N7000OZSLPF_OZS ROM. This all went OK & everything seem fine. I then relised this was not the ROM for me as it didn't contain "English Australian" amoungst other things. So I thought, no problem, I'l just flash something else more suitable, but no matter what else I flash with odin I keep getting "Force Close" continually once the phone has booted up. I tried many different ROMS from Gingerbread to ICS & keep getting the "Force Close" error.
I then flashed back the Taiwan ROM & it works fine but I am now stuck with that ROM.
The only difference with the Taiwan ROM that I can see was that it contained not just the PDA file like most ROM's but it had a PIT & BOOTLOADER & PDA & PHONE & CSC files. I think this may be where i've gone wrong. Maybe if I could find the stock international versions of all these files I may be able to flash these & get back to stock & start again.
Any help would be greatly appreciated
Anyone know where I can get the stock PIT & BOOTLOADER & PDA & PHONE & CSC
files so I can get back to stock?
I was also confused about the pit & bootloader files. I have used N7000XXLC1 open Europe with PC Odin. I have just sellected PDA file and everything went ok. Now I'm on stock GB without any problems
have you already tried to flash any stock rom trough mobile odin?
jpsb said:
have you already tried to flash any stock rom trough mobile odin?
Click to expand...
Click to collapse
I have tried flashing 2 stock ICS ROMs & 3 different stock Gingerbread ROMs using PC odin only. They all give me continious "Force Close" error messages after bootup making the phone unusable.
If I flash back the Taiwan ROM all seems OK but I;m stuck with this ROM.
If I were you I would get a working version of the taiwan rom on the phone. Then flash a suitable CF kernel. Push a choice custom rom on your Sd card. And then flas that rom from CWM recovery. Only wiping cache and dalvik cache.
Just go into recovery and wipe all caches and factory reset and it will load fine it did it to me until I wiped all caches kept saying Google frame work has stopped
Sent from my GT-N7000 using xda premium
Well.... for quite obvious reasons I wouldnt recommend doing a factory reset on an official ICS kernel.
Something lile sssssuperbrick comes to mind.
This superbrick stuffs is getting on my tits how many people are wiping on there galaxy note using superbrick kernels and having no problems thousands?? hundreds of thousands??? but 20 people brick there phones and it's like Osama bin laden has created this emmc bug in the kernel to get us all.. We all know the dangers people could brick there phones using safe kernels because people make mistakes and or don't follow instructions
Sent from my GT-N7000 using xda premium
Belfia said:
If I were you I would get a working version of the taiwan rom on the phone. Then flash a suitable CF kernel. Push a choice custom rom on your Sd card. And then flas that rom from CWM recovery. Only wiping cache and dalvik cache.
Click to expand...
Click to collapse
Sonic1981 said:
Just go into recovery and wipe all caches and factory reset and it will load fine it did it to me until I wiped all caches kept saying Google frame work has stopped
Click to expand...
Click to collapse
Thanks for the replys.
The Taiwan ROM that works is a ICS ROM, N7000ZSLPF_N7000OZSLPF_OZS.
I have thought of doing a full wipe via CWM but I'm afarid of the "SuperBrick" issue. In fact I was think maybe there is some coruption in the emmc partition already causing the "Force Close" errors I keep getting
KTM690 said:
Thanks for the replys.
The Taiwan ROM that works is a ICS ROM, N7000ZSLPF_N7000OZSLPF_OZS.
I have thought of doing a full wipe via CWM but I'm afarid of the "SuperBrick" issue. In fact I was think maybe there is some coruption in the emmc partition already causing the "Force Close" errors I keep getting
Click to expand...
Click to collapse
Just clear your caches after each flash back from gb to ics vice versa and it will work fine
Here is your salvation installation
Dear KTM690 :
No need To Panic, here is your solution :
Let's suppose you are on the Stock LPF now :
1- Download the corresponding Rooted Kernel by Chainfire : I got it for you : http://download.chainfire.eu/176/CF-Root/SGN/CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
2- Extract it, you will have a tar file, Flash it with PC odin.
3- Reboot, now you are rooted and you have cwm recovery at the same time
4- Download the AbyssKernel V4.2 only : http://www.mediafire.com/?c65mndvpk6ocbaa
5- Put the zip file on your sdcard, don't extract it
6- Choose what ever ICS rom you like, let's say the TMT v1.4 that you wanted.
7- Put the zip file on your Sdcard.don't extract it
8- now shut off your phone, Press the Vol Up, Power and the Home Buttons at the same time, and you will be into cwm recovery mode.
9- Don't wipe anything, and Flash the AbyssKernel v4.2.
10- Don't reboot the phone, still in cwmr, go to advanced and choose reboot recovery.
11- You are now in recovery mode again, but with the Abyss Kernel instead of the rooted LPF one by chainfire.(now you have cwm touch recovery, tap with your finger now)
12- So It is totally safe now : wipe everything : data, cache, go to advanced and wipe dalvick cache, and battery stat, choose also Fix permissions while you are there.
13- choose back to go to the first screen,
Now you have Options, depending on what you have dowloaded as a Rom file...
14- If you want to flash the backup zip file from TMTv1.4 : choose backup and restore, and choose restore from internal sdcard, and look for your downloaded TMT zip file. (It should be clockworkmod/backup/TMT1.4...... Folder), I suppose you already have done it.!
15- If you have dowloaded the flashable TMT zip file, then choose install zip file, and choose file from internal sdcard..
In either cases : Reboot and you are done.
This is the cleanest installation you could have done, just don't skip any step !!!!
If this Helped, The thanks Button is next to you, ....and check my MOD : the 15 toggles in case .....
http://forum.xda-developers.com/showthread.php?t=1620625.
Good Luck.
Okay just flash whatever ROM you want (even if there are FCs), go into stock recovery (volume up home and power) and wipe data and cache. Reboot. This solved all the FCs for me when I had the same problem. Worth trying!
Sent from my GT-N7000 using XDA
kimifender said:
Dear KTM690 :
No need To Panic, here is your solution :
Let's suppose you are on the Stock LPF now :
1- Download the corresponding Rooted Kernel by Chainfire : I got it for you : http://download.chainfire.eu/176/CF-Root/SGN/CF-Root-SGN_ZS_OZS_LPF-v5.6-CWM5.zip
2- Extract it, you will have a tar file, Flash it with PC odin.
3- Reboot, now you are rooted and you have cwm recovery at the same time
4- Download the AbyssKernel V4.2 only : http://www.mediafire.com/?c65mndvpk6ocbaa
5- Put the zip file on your sdcard, don't extract it
6- Choose what ever ICS rom you like, let's say the TMT v1.4 that you wanted.
7- Put the zip file on your Sdcard.don't extract it
8- now shut off your phone, Press the Vol Up, Power and the Home Buttons at the same time, and you will be into cwm recovery mode.
9- Don't wipe anything, and Flash the AbyssKernel v4.2.
10- Don't reboot the phone, still in cwmr, go to advanced and choose reboot recovery.
11- You are now in recovery mode again, but with the Abyss Kernel instead of the rooted LPF one by chainfire.(now you have cwm touch recovery, tap with your finger now)
12- So It is totally safe now : wipe everything : data, cache, go to advanced and wipe dalvick cache, and battery stat, choose also Fix permissions while you are there.
13- choose back to go to the first screen,
Now you have Options, depending on what you have dowloaded as a Rom file...
14- If you want to flash the backup zip file from TMTv1.4 : choose backup and restore, and choose restore from internal sdcard, and look for your downloaded TMT zip file. (It should be clockworkmod/backup/TMT1.4...... Folder), I suppose you already have done it.!
15- If you have dowloaded the flashable TMT zip file, then choose install zip file, and choose file from internal sdcard..
In either cases : Reboot and you are done.
This is the cleanest installation you could have done, just don't skip any step !!!!
If this Helped, The thanks Button is next to you, ....and check my MOD : the 15 toggles in case .....
http://forum.xda-developers.com/showthread.php?t=1620625.
Good Luck.
Click to expand...
Click to collapse
Thanks for you advise kimifender & everyone else.
I carried this out and now everything is back to normal.
I was just too worried about wiping everything because of the SuperBrick bug.
KTM690 said:
Thanks for you advise kimifender & everyone else.
I carried this out and now everything is back to normal.
I was just too worried about wiping everything because of the SuperBrick bug.
Click to expand...
Click to collapse
Glad for you
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
adobih said:
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
Click to expand...
Click to collapse
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Samtan4326 said:
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Click to expand...
Click to collapse
First off all thanks for helping.
I tried this one:
CF-ROOT-4.4-I9000BGJW5-1187857
CF-Root-4.4-I9000BOJW6-CL1177078
CF-Root-JP6-v1.2-Busybox-1.17.1 (this one didn't want to start recovery at all)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
all I got from all of them is this
imageshack.us/f/805/08032008449.jpg (copy link to address bar )
Member Chainfire said "THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device"
I don't know really what that means. Probably that I have to install something else too, but what ?
Please can you tell me ?
And which of these CF-Roots is the right one, or the newest one, or how do recognize that ?
Thanks everyone who helps me.
eba
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After it's done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
adobih said:
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After is done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
Click to expand...
Click to collapse
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
beckzz said:
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
Click to expand...
Click to collapse
Well, I help you as much as I can and know, just write me where you stuck. And if you have some difficulties explaining it in English, dann kannst du mir auch auf deutsch schreiben, das verstehe ich auch
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & -->release buttons the moment u see bootanimation<--) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough). If not getting into recovery with waiting the first time just try to keep getting in recovery with 3 button combo & wait a couple of minutes. Eventually it does. I had the same thing 2 months ago coming from jb-->ics-->cm10, thats how I remembered.
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen. Didnt wipe nothing in between the flashing
Then flashed gapps & voila
Donovan662 said:
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & release buttons the moment u see bootanimation) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough)
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen
Then flashed gapps & voila
Click to expand...
Click to collapse
I tried like hundred times or more, but every time with the same result and I also tried with different kernels without success. Maybe some other error caused your status 7 error than mine. But anyway, it's always good to try all possibilities to resolve the problem.
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Donovan662 said:
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Click to expand...
Click to collapse
Unfortunately I wasn't that lucky, but I tell you something else. Now I know that no matter what I do and how badly i brick my phone I can always use that method to bring it to life back. So it's kind of final help that works if nothing else works
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Donovan662 said:
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Click to expand...
Click to collapse
I choose zip from sd card because I forgot to rename the file before copying to sd card, and when I lost my bricked my phone it was already to late to rename it. But i don't think that that was the problem, I mean it's just a name string that has no meaning after all.
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
beckzz said:
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
Click to expand...
Click to collapse
More or less I think we both had the same problem, because I also used this link wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide and heimdall 1.3.2 for flashing my phone. Just it always finished successfully so I didn't realize it was the root of all problems. I used also then Odin from the youtube video that I posted in a few posts earlier, installed Android 2.3.6 and then installed ROM Manager from Google play, and used the app to flash to ClockworkMod Recovery. After that I installed directly CM10 stable with success, and without CM9 detour.
i wonder if there is a way out of a bootloop that works no matter what, as long as you can enter download mode.
after reading for 3 days and flashing everything i could (flashing stock ROM, WIPE_I8190.tar.md5, PARAM_I8190.tar.md5, "LeFreu" I8190 серв. укр) it all gave me the same result: bootloop.
i made a back up before flashing a custom ROM (Dmod V6 and Virginity V3 as they seemed like the best ones) so if any of u help me access CWM recovery or TWRP i could do a restore and make my phone work again.
NOTE: the only way i managed to use CWM recovery the first time was rooting with odin "I8190XXALL2_I8190OXXALL1_HOME_rooted_by_avicohh" and then downloading rom manager from the playstore
the attached screenshot shows my device info from factory, can anyone help me restore my phone?
gimmesansa said:
i need serious help.
i have a galaxy s3 mini gt-i8190 and im stuck on a bootloop
i bought it in new sealed condition and it came with this firmware (see attached screenshot)
and when i tried to update it a window popped saying that my device was modified and that software update were not available.
i decided to root my phone so i could install a new rom.
i downloaded all the software i needed including drivers dor the usb samdung devices and enabled usb debuging in developer options
then i used odin to flash I8190XXALL2_I8190OXXALL1_HOME_rooted_by_avicohh
then i tried flashing custom recovery via odin also
everything went normal but custom recovery was not sticking, meaning no matter what type of custom recovery i flashed (twrp, cwm) i ended up having 3e stock recovery.. (NOTE: the 3e stock recovery before AND after flashing rooted ROM, had always a broken android on the floor with an exclamationg sign in its chest) so i tried another method:
i downloaded root checker from the playstore and rom manager. after checking i was rooted (wich i was) i flashed cwm recovery and succesfully was able tu boot into cwm recovery. i did a back up in both, internal storage and external sd, and procedded to flash Dmod V6. i followed the aroma installer and when it finished i selected reboot system now and got a bootloop.
i entered in cwm recovery and did a restore. did a full wipe (data, cache and dalvik) and tried flashing another rom: virginity ROM. followed the aroma installer and selected reboot system now, the result was bootloop.
when i was trying to do another restore the recovery told me that the system would try to flash stock recovery again and i choosed to keep the cwm recovery.
at this point my phone was able to turn on and boot normally. tried again to flash via cwm the virginity rom and got a bootloop again. so i went to do another restore and this time i choosed diferently (flash stock recovery) and when the restore ended i selected rebbot system now and got a bootloop AGAIN.
now i cannot enter CWM recovery (i guess that is obvious because i choosed to flash stock one)
i have readed 3 days now and tried everything that the forums say: flashing stock firmware, flashing WIPE_I8190.tar.md5, flashing PARAM_I8190.tar.md5 and still ended with a bootloop. tried flashing I8190 серв. укр (LeFleur) and nothing, absolutely nothing works.
i even downloaded Unified_Android_Toolkit_v1.2.8 and tried to flash stock firmware but nothing seems to work. all my phone does is bootloop, and boot into download mode.
can a serious developer help me solve this? im about to give up.... and that seriously affects me because im not a quitter.
any help would be greatly apreciated...
Click to expand...
Click to collapse
Odin v3.07 for Windows: http://androidcentral.us/2013/11/download-odin/
Samsung USB drivers: http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows;jsessionid=YQkGJjBRhc4x1DMTJZCy1pnhGKcb20v4yGtdQZp6NpjhsR5p2KBM!2021479002
A Rom from http://novafusion.pl/ for the Samsung Galaxy S3 Mini (select Downloads / CyanogenMod / KitKat 4.4.4 (CyanogenMod 11.0) 20140923 / odin)
And then perform this steps:
1) Install the USB drivers.
2) Run Odin v3.07.
3) In opened window, click on PDA button and select CyanogenMod rom with .tar.md5 extension.
4) Make sure that only Auto Reboot and F.Reset Time are selected on the left side.
5) Turn off your phone, and then use VOL- & HOME & POWER buttons combination.
6) If you see Warning screen, use VOL+ button.
7) Connect phone to computer and make sure it is detected by Odin (it will appear as COM device). If it doesn’t, try to use other USB port.
8) Use Start button. Wait until flash process will finish.
9) Your phone will restart.
10) Wait for boot.
11) If your phone restart, but won’t boot pull down your battery and use VOL+ & HOME & POWER buttons combo to boot into recovery.
12) Click on Wipe / Advanced Wipe, choose Dalvik Cache and Cache and swipe to wipe.
13) Reboot and Enjoy. :laugh:
Btw after the Rom you nead and Gapps from the same site (http://novafusion.pl/)
jstath1972 said:
Odin v3.07 for Windows: http://forum.xda-developers.com/show....php?t=1738841
Samsung USB drivers: http://www.android.gs/download-samsu...s-for-android/
A Rom from http://novafusion.pl/ for the Samsung Galaxy S3 Mini (select Downloads / CyanogenMod / KitKat 4.4.4 (CyanogenMod 11.0) 20140923 / odin)
And then perform this steps:
1) Install the USB drivers.
2) Run Odin v3.07.
3) In opened window, click on PDA button and select CyanogenMod rom with .tar.md5 extension.
4) Make sure that only Auto Reboot and F.Reset Time are selected on the left side.
5) Turn off your phone, and then use VOL- & HOME & POWER buttons combination.
6) If you see Warning screen, use VOL+ button.
7) Connect phone to computer and make sure it is detected by Odin (it will appear as COM device). If it doesn’t, try to use other USB port.
8) Use Start button. Wait until flash process will finish.
9) Your phone will restart.
10) Wait for boot.
11) If your phone restart, but won’t boot pull down your battery and use VOL+ & HOME & POWER buttons combo to boot into recovery.
12) Click on Wipe / Advanced Wipe, choose Dalvik Cache and Cache and swipe to wipe.
13) Reboot and Enjoy. :laugh:
Btw after the Rom you nead and Gapps from the same site (http://novafusion.pl/)
Click to expand...
Click to collapse
Links are broken...
gimmesansa said:
Links are broken...
Click to expand...
Click to collapse
Try now or search again here http://novafusion.pl/downloads/ (select Downloads / CyanogenMod / Extras)