Related
Hi, I'm stuck with installing new rom, so I hope, that you'll help me.
There are steps what I've done:
- followed THIS topic and ROOT the device with ODIN and CF-Root 4.4 file.
- OKAY, I'm rooted, so let's flash the new ROM
- entered in Clockworkmod Recovery and format EVERYTHING ( /data, /system, /cache, /sdcard etc.... just everything) for clear system
- next I load package with ROM and than INSTALLL
and here is the most important part
- when installed ROM gets something like bootloop but with restart - ROM is loading and after about 40 sec its RESTART
- and the same thing over and over again - restart ->loading->restart.... System never start up correctly to the end
- then when I saw that it does not work, I tried go into the CWM, but there was no CWM (!!!) - it was erased (by installing new ROM maybe???)
- so I must flash (old and stock) ROM via ODIN and again root device with CF-Root (with CWM) - that was only functional rom, what I was able to run, and again did this procedure
I tried this way, perhaps with millions of different ROM and EVERY was stucked (restart) while loading.
I think there are some non-deleted files in device, which should be erased (and which cannot be erased by CWM) for clear start of new installed ROM, what do you think?
Would someone please help me? I don't want old Gingerbread with Kies
Thanks for every responce!
Does it say in the thread that you have to flash a custom kernel?? Give.me the link for the thread so I can make sure that you've done everything right
Sent from ma 5assak
there is a link, but in hypertext THIS, i repost it in full text:
http://forum.xda-developers.com/showthread.php?t=788108
I think, when I've root and CWM, there is no problem and install a new rom will be very least, so not as it seems
Dude this is a kernel not a rom what's the matter with you??:what:
Sent from ma 5assak
please read all my topic - i flash this kernel only for clockworkmod recovery
through CWM I can flash any other rom
through ODIN only stock - cant find any ICS or JB rom which I can flash via ODIN (.tar file)
What variant of i9000 do you have? Are you sure that the rom you are trying to flash is made exactly for your variant?
EDIT: Try Darky ROM, they have an ODIN flashable version called "Resurrection Edition" or something.
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Samsung Galaxy S I9000, i'm sure 100%. NOT I9001, NOT Samsung Galaxy S2. Tried many roms from Development section for I9000, tried from get.cm etc... always the same result bootloop with restart
donhashem.dh said:
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Click to expand...
Click to collapse
OK. For example: this rom cm-9.0.0-galaxysmtd and cm-9-20120815-NIGHTLY-galaxysmtd from http://get.cm/?device=galaxysmtd
Or this one last ([ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S) http://forum.xda-developers.com/showthread.php?t=1778526 and 20120808 build.
and [ROM][PORT][ANDROID 4.1.1][BETA] TAJB: Jelly Bean port for Galaxy S V7.1 http://forum.xda-developers.com/showthread.php?t=1747042
and this too [4.0.4][ROM] Dark Knight 5.5 [27/4/2012] http://forum.xda-developers.com/showthread.php?t=1510940
and many more....
realy unhappy from this
Nikishek said:
Samsung Galaxy S I9000, i'm sure 100%t
Click to expand...
Click to collapse
I meant I9000 or I9000B or I9000M or I9000T there's a difference between them
I9000 only, checked it several times
Ok so you can flash Darky Rom Resurrection Edition through ODIN with no problem. Its GingerBread if i remember correctly, but it should give you a recovery mode and fully operating phone. From this point you can flash whatever you want.
....And there is one more important thing:
When I have a stock kernel and stock rom from Samsung, cant get into recovery mode - VOLUME UP and POWER non functional. Only when I type: "adb reboot recovery" in terminal.
Just after when I flash a new pre-rooted kernel with CWM, VOLUPE UP and POWER is now functional
k4Z3666: OK, I try and give you an echo I think, when I format everything in CWM, there will be no sign of the earlier system and ALL WILL BE CLEAR
Nikishek said:
I9000 only, checked it several times
Click to expand...
Click to collapse
ok, flashing ICS, may need to be done twice, as first flash may bootloop, IF you want to return to stock to get out of this mess, since you are not sure as to where you are now, due to flashing many roms, use any kit from My Android Collections, link below to get you to a booting ROM, than add a kernel with CWM (use EZbaze package with kernels)
that's helped me too thank you
Sent from my GT-I9000 using xda app-developers app
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.
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
perceptorz said:
Hi fellows,
I need your guidance and expert advice in resolving a situation, I have ran into recently. I was trying to install CM10.1 on my brother's galaxy Note GT-N7000 international version which was running official ICS 4.0.4.
Since, I had experience in installing different ROMs on my Galaxy S2, Nexus 7 and Xperia Arc so I was not worried about it being a big deal. So, I followed the procedure described in this page http://techgoneinsane.blogspot.com/2012/08/installing-cm10-on-galaxy-note-n7000.html?m=1 and used Odin and file from 'speedmod' to gain root access and flash CWM which was successful. Then, as planned, I tried update zip in the CWM recovery for CM10.1 nightly. But, I came across error 'Status 7' installation aborted. This was new to me, so I tried few things like 'factory reset', wipe data etc and even tried installing stock ROM ICS XXLRK which was previously installed but no avail. I tried several other ROMs like stable CM9 and other nightlies but no success. The phone is stuck on the boot Samsung logo with yellow triangle. However, I'm able to go in the recovery and download mode.
Upon doing couple of Google searches, I came to know, quite a number of people have faced this error by I couldn't understand the fix properly so can anyone of you please guide me for the solution. Thanks.
Your help will be greatly appreciated.
Click to expand...
Click to collapse
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Solved
Kortxero said:
If you are on Speedmod's recovery (which is safe), you can try this:
1) Download the latest CM10.1 kernel and save it to your SD card.
2) Flash it in Recovery (Install zip from sdcard > choose zip from sdcard), then reboot in the new Recovery (advanced > reboot recovery).
3) Do a full wipe (even format preload and system in "mounts")
3) Flash the latest CM10.1 build
4) Flash the 4.2.2 Gapps
5) Do a data wipe / factory reset
6) Reboot
You got a yellow triangle because you flashed an unofficial kernel through Odin. To get rid of it, use TriangleAway.
Good luck!
Click to expand...
Click to collapse
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
perceptorz said:
Thanks a lot man. Issue has been resolved by following your procedure and phone is working all fine with CM10.1 on it. Xda rocks!!!
Click to expand...
Click to collapse
You're welcome. Glad I could help . If you feel like it, hit the Thanks button on Chasmodo's first message in the repository (where you downloaded your CM10.1 kernel). He really deserves it. You may also want to do the same on Entropy's first post in the unofficial CM10.1 thread :good: That way, you'll show your support and appreciation :angel:.
Hi everybody,
just got an old yet effective SGS and I wanted root and get rid of touchwizz and all the crap from my carrier
I was unable to boot into DL mode, i tried everything, so I had to do it with adb reboot
I never had to use Odin to do my hacking with android so i'm not used to it but short story : I rename my rom.zip into rom rom.tar, it failed and all I have is this now :
https://www.dropbox.com/s/wk42jbmp33a3ftu/IMG_20140715_152917.jpg
Also I need to unsimlock, flashing a new rom will also do the trick right ?
thanks
What you just did is bricking your phone. It it was a zip file you need to install it from the recovery. Renaming it is not the way it works. I'm not sure if now you can fix it. Sorry, man
Sent from my GT-I9000 using XDA Premium 4 mobile app
Do you know what I can at least try?
If you can get into download mode:
Follow sections 2 and 3 in this guide.
If you can't:
Follow this guide and after that do what I sails to do if you have download mode.
Does 3-button-combo not work to get into the download mode?
(power & home & volume down)
tetakpatalked from Nexus 7 flo
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
@Idealith simlock has nothing to do with the firmware.
You need now any root kernel for that firmware, it has to be compatible with the intiframs of your 2.x version and it will give you a custom recovery.
There you can flash first CM10.2 to get the modified partition sizes and KK ready recovery and after that you can flash CM11
IMHO, the new Mackay ICS 2014 rom based on CM9 is a lot faster than any KitKat and works better on the i9000
tetakpatalked from N7100
my question about the rom still applies cause this one is awful
but with what does it have to do then ?
EDIT : my browser didn't render the end of your answer
I'm afraid i'm not following though :/
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Idealith said:
I got my 2.3 rom to stop crashing
and I once boot into recovery mod idk how ..
I selected the 10.2 CM rom but it started rebooting over and over again
I'm really not following everything that is happening over here :/
Click to expand...
Click to collapse
Hey, could you tell me which country you are at? I could then take a few steps to help you
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Idealith said:
I am currently in France
last news : been able to reboot into CWM, I selected the mackay cm 9 based rom, it rebooted halfway thrugh only to reboot in TWRP (idk how, are both installed or is twrp in the rom too ???)
so i tried from twrp wiping everything before and it wen through, then on bot it told me it needed to factory reset, it never worker though
so now i can boot into CWM but can't access my sd card ...
thanks
Click to expand...
Click to collapse
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
tetakpatak said:
It was perfectly normal behavior, as after flashing the zip from CM, it will in firat step upgrade your recovery to TWRP 2.2.2.0
As you have wiped already before, it would be perfectly fine to just flash the rom.zip in the new TWRP recovery, and your gapps right afterwards. The recovery upgrade is totally common on the i9000 as first step.
The i9000 can easily be unbricked by flashing a stock image with Odin.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Idealith said:
I suppose my phone has been unbricked I made a 2.3 stock rom work
What i do now :
I flash the stock rom, go back to DL mode, flash the recovery, take the battery off, boot back in recovery, wipe everything ( do I really have to wipe system and all ?), select the ROM, nd once I'm in TWRP i reselect than same ROM
for the cm9 based mackay one it keep rebooting over and over again
for CM 10.2 it says the encryption failed and I need to factory reset, then nothing works
Click to expand...
Click to collapse
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
tetakpatak said:
Yes, that would be correct procedure. To install CM9 you will have to format data, cache and dalvik cache.
If you have never had a JVU or JVZ firmware installed, it is likely that you still have a Froyo bootloader which could be reason of the problems with Android 4.xx
tetakpatalked from N7100
Click to expand...
Click to collapse
and how do i get that bootloader set up ?
Idealith said:
and how do i get that bootloader set up ?
Click to expand...
Click to collapse
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
tetakpatak said:
Either by flashing a whole JVU or JVZ stock firmware, or by flashing a bootloader only.
Check my sticky thread here under the same section (help & troubleshooting), I have described whole the procedure in the OP. I have even attached the files and also video is there: http://forum.xda-developers.com/showthread.php?t=2444308
Right point would be to do it first.
tetakpatalked from N7100
Click to expand...
Click to collapse
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Idealith said:
thanks you so much i have now CM 10.2 running
would you know by any chance how to un simlock it ?
Click to expand...
Click to collapse
Ask your carrier, I assume the phone contract isn't new anymore (or expired) so you'll get unlock code for free. Here in Europe one can obtain the unlock code after 2 years for free.
Otherwise you can ask one of the online unlock services, it costs usually around 15-20$ to get the code
tetakpatalked from N7100
Idealith said:
so i tried the resistance thing but i was unable to find all of the part required so i bought one of these already done solution thingy
It worked, I'm now able to boot into DL mode
I also succesfully install a random 2.x rom from an unknown european carrier, no root, lots of crap installed, and simlocked
How do i get from that to my CM 11 rom ? (this time it's in .tar format via 7zip ^^')
I tried via Odin in PDA it says fail right away
what can I do ?
thanks fr all the answers guys
Click to expand...
Click to collapse
I'm glad that the JIG helped you (I know I'm late )
danielbe said:
I'm glad that the JIG helped you (I know I'm late )
Click to expand...
Click to collapse
yeah that worked like a charm
it was a good idea to buy it, i would have use the resistors so much
is there a more xda way to unlock it ? my carrier wants me to send the phone and have it unlock, they won't just provide the code :/
This is my second attempt to install custom ROM and I failed... I did everything step by step and it doesn't work. Or it doesnt boot at all or it craches in recovery mode while installing update.
This time i used some nightly unofficial and it stoped installing in recovery :S This is so annoyng
I downloaded stock lastest from code support for my Samsung S5830 because obviously there is non stable version of custom ROM right now.
I do not advise to go over Android 2.3.6 for S5830 or you will burn down your phone system...
Bugeera said:
This is my second attempt to install custom ROM and I failed... I did everything step by step and it doesn't work. Or it doesnt boot at all or it craches in recovery mode while installing update.
This time i used some nightly unofficial and it stoped installing in recovery :S This is so annoyng
I downloaded stock lastest from code support for my Samsung S5830 because obviously there is non stable version of custom ROM right now.
I do not advise to go over Android 2.3.6 for S5830 or you will burn down your phone system...
Click to expand...
Click to collapse
What did you do exactly?
Viper The Ripper said:
What did you do exactly?
Click to expand...
Click to collapse
Rooted phone with SuperOneClick successfully
downloaded CWM recovery, custom ROM, google apps and newcamera.apk
puted in SD
entered recovery mode, hard reset options (wipe data + catche)
installed zip from SD (CWM recovery)
rebooted recovery
installation of custom ROM stoped with error code (7)
from there i wouldnt be able to boot system
then i used code support and downloaded firmware flash files for S5830
odin installed it but also wont boot up the phone
then i pissed off and took old polish firmware installed with odin, after that did hard reset and now phone is working on 2.3.6
Bugeera said:
Rooted phone with SuperOneClick successfully
downloaded CWM recovery, custom ROM, google apps and newcamera.apk
puted in SD
entered recovery mode, hard reset options (wipe data + catche)
installed zip from SD (CWM recovery)
rebooted recovery
installation of custom ROM stoped with error code (7)
from there i wouldnt be able to boot system
then i used code support and downloaded firmware flash files for S5830
odin installed it but also wont boot up the phone
then i pissed off and took old polish firmware installed with odin, after that did hard reset and now phone is working on 2.3.6
Click to expand...
Click to collapse
Ok now you are unrooted on your new polish right. So now root it with UniversalGingerbreadroot.zip (google it.) Flash an older version of CWM(5.0) through the stock recovery. Finally install a stable custom rom initially do not go for CM roms as for testing try some other stock based rom and if successful you can advance to CWM.
All the best.
Bugeera said:
Rooted phone with SuperOneClick successfully
downloaded CWM recovery, custom ROM, google apps and newcamera.apk
puted in SD
entered recovery mode, hard reset options (wipe data + catche)
installed zip from SD (CWM recovery)
rebooted recovery
installation of custom ROM stoped with error code (7)
from there i wouldnt be able to boot system
then i used code support and downloaded firmware flash files for S5830
odin installed it but also wont boot up the phone
then i pissed off and took old polish firmware installed with odin, after that did hard reset and now phone is working on 2.3.6
Click to expand...
Click to collapse
Here you'll find ROOT and CWM files to get ready your Ace, than you'll be able to install Customs STOCK Roms, CM7.x, CM9.x, CM10.x
Read carefully the threads in GT-S5830 Android Development section and follow the dev's instructions
PS: To get CM11.x you'll need to flash CWM6.x or TWRP