Hi..
I want to clean install Android 4.0.4 OS on my Samsung galaxy s plus (GT-19001) device.
Clean install means that i 'll have to install OS from scratch. Does i need Micro USb Jig for this purpose?
I have below files.
1-> cm-9-20121011-ivendor-ariesve-rc5.zip
2-> gapps-ics-20120429-signed.zip
3-> recovery-clockwork-6.0.1.2-ariesve.zip
4> CWM-based recovery v5.5.0.4
Guide me in simple steps , i tried many times to install ICS (Android 4.0.4) but unfortunately unsuccessfull each time.
Why it didn't work for me?
I have tried in many ways. Thanks in advancee
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
support required
Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Perfectly simple guide! Thanks.:good:
The only thing I want to ask - what is the backup you have mentioned in point 1)? Is it back up of your personal data, or is it back up of your current ROM?
Hey man, glad I made it simple
Yeah, its a backup of your whole rom I believe- system apps, system files, all your downloaded apps all your data, so on so forth.
Helps you get back to what you were running before in case something goes wrong during installation.
Sent from my GT-I9000
---------- Post added at 02:29 PM ---------- Previous post was at 02:15 PM ----------
empnetsol said:
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Click to expand...
Click to collapse
Hmmm... Okay, I see...
What recovery did you start with before flashing CWM 5.5.0.4? Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
Again, hope I helped
Sent from my GT-I9000
hi .
i am trying to give answer in point:
What recovery did you start with before flashing CWM 5.5.0.4?
-> yes i t was exactly CWM 5.5.0.4.
Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
-> Could you elaborate the above sentence please? As long as i understood I initially installed CWM recovery through recovery mode by holding +Vol + Power+ Home.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
-> Yes i have been reverted through Odin Stock Gingerbread. How to root again? Could you please enlist in points?
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
-> I don't think it's a bootlooping situation. When i start my device , It dispays CWM recovery screen each time even after the sucessull completion of CM9 and gapps,
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
-> I tried it many time right now and 2-3 months ago too but it took almost 20 - 30 seconds in first attempt.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
-> I tried through Wipe and with it but could start my OS. Instead it display everytime a CWM screen.
=================================================================================================
In last , i did below steps :
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
Go into the cm10 thread by ivendor in developement section and in the middle of the 1st post is a download link for cwm 6.0.1.9. Flash it in recovery and reboot. The Problem should be gone.
Had the same issue.
Hope i helped
Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks
empnetsol said:
Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks
Click to expand...
Click to collapse
No i meant that you can install everything like in your guide and after that you install the cwm 6.0.1.9 and reboot, then you should be in recovery and then you have to reboot your phone and it should start normally
This solved it for me
Hope i helped
That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).
It should be the right way but you can skip step 5 and 9
Hope i helped
empnetsol said:
That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).
Click to expand...
Click to collapse
It should be the right way but you can skip step 5 and 9
Hope i helped
Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?
empnetsol said:
Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?
Click to expand...
Click to collapse
I don't know if cwm 6.0.1.9 supports cm9 but it should.
You could try it out and tell me back
when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.
empnetsol said:
when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.
Click to expand...
Click to collapse
Got the same error, i think its normal
Ok, then flash this file: http://forum.xda-developers.com/attachment.php?attachmentid=861538&d=1326841043 in recovery, reboot and tell me back if it works
Or you could try this way if the other isn't working: http://forum.xda-developers.com/attachment.php?attachmentid=928219&d=1330695090 its the stock recovery, flash it in recovery and reboot and tell me back. I think you should first try stock recovery and then the other file. Sry for the wrong order
Hope it will work again
hi markey.
how to flash these files? i didn't understand the flashing word.
Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
empnetsol said:
hi markey.
how to flash these files? i didn't understand the flashing word.
Click to expand...
Click to collapse
empnetsol said:
Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
Click to expand...
Click to collapse
I mean that you have to install them via recovery with install update from sd card or with install zip from sd card -> its called flashing
And i meant that you have to install the first file first and reboot and if its not working when you reboot then install the stock recovery and then the problem should be solved. But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
Hope i could help
Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?
empnetsol said:
Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?
Click to expand...
Click to collapse
Which recovery do you use?
Cwm or stock recovery?
If you use stock then you have to reboot without installing one of the files and the problem should be solved
I meant that if you want to install another kernel or custom Rom you have to install the cwm recovery because its better then stock and after installation of the Rom or kernel you have to reinstall the stock recovery
If you don't understand i'll write you a guide for what you have to do
Related
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Velshtein said:
Slight issue here, not sure if anyone has had it before.
Just acquired a Captivate as an xmas gift to myself (sick of that iPhone), and began the whole process of getting a new ROM onto it. Rooted, installed ROM Manager, flashed a clockworkmod recovery (2.5.1.2), and hit "Backup Current ROM".
The device reboots into the standard recovery mode with the usual options (reboot system now, reinstall packages, delete all user data, delete cache data).
No backup is made, and I just have to continue the reboot. I've tried flashing to an older version, clearing the download cache, and using the option to go to ROM Manager's recovery mode (just takes me to the default recovery boot).
Am I doing something wrong here? I followed all of the instructions step by step.
Click to expand...
Click to collapse
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
diablo009 said:
Try doing "reinstall packages".
Steps:
1. Copy the clockwork recovery "update.zip" attached to this post to ur sdcard root.
2. Reboot to recovery.
3. Select "reinstall packages".
4. It would say something like replacing recovery with clockwork recovery, and reboot into recovery. This happens only the first time u use this.
5. Select "reinstall packages" again.
6. You should be in clockwork recovery.
Click to expand...
Click to collapse
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Velshtein said:
Good deal. Worked perfectly. Out of curiosity, do we know why the phone was doing this?
Click to expand...
Click to collapse
Ok. I'll explain to the best of my knowledge.
The zip I gave u is the most non-intrusive way of CWM. No ROM manager installer is needed on phone apart from placing this zip on sdcard root.
When the phone boots up, it loads the default recovery console. When we select "reinstall packages", it loads "update.zip" on the sdcard root by default. Since the update.zip we have there is the CWM zip, it loads it therby loading CWM console.
If u don't want CWM, just delete this update.zip.
Hope this helps.
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
NISMOFO said:
I have this exact same issue ROM Manager is doing nothing but rebooting into recovery. So if I use your workaround, I need to keep this update.zip file on my device at all times?
Click to expand...
Click to collapse
Yes best to do so
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
MikeyMike01 said:
All ROM Manager does is download the update.zip that was posted and put it on your SD Card. The other steps need to be done regardless.
Click to expand...
Click to collapse
I got the ROM backup working. I guess I was too impatient the first time. I cleared/moved a lot of stuff off my internal SD card too....doubt that it mattered.
But it works quite well.
Phone will only boot into clockworkmod recovery, even after pulling battery and powering up using only the power button, it goes into recovery.
Here is what happend leading up to it:
- flash through rom manager the new clockworkmod
- used fireat's mod with mtd 125 2
- flashed aospCmod 2.3.3
- everything booted fine
- re-did firerat's mod with mtd 102 2
- now bootlooping into clockwork mod
I tried duplicating what worked initialy with no luck. Tried booting into hboot and htc reset menu (power + home + back) but not matter what it only goes to clockworkmod recovery.
For my install steps I followed romrepro "install from other rom" guide here: romrepo.info/wiki/index.php?title=Install_from_another_ROM
I have also tried the following:
- restoring through nandroid
- recovery flasher v1.3 to flash older version of clockwork
- lots of stinking google
All have resulted in no success.
Please help!
Are you s-off? You probably shouldn't mess with firerats if you're not. Mount your sdcard in recovery and change your mtd settings and then flash your rom and reflash fr boot.
~maybe I set it too high...
Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.
Wait, so it opens recovery by just turning on your phone?
~maybe I set it too high...
bphem3 said:
Thank you for responding. I am not s-off and I already tried changing the mtd part, flash rom, flash boot, and it still autoboots back into recovery.
I re ran the mtd part map with the following:
- 102 2
- 105 2
- 110 2
- 115 2
- 120 2
- 125 2
- 190 2
I also tried flashing aospMOD v9.2.2 (which is what I was originaly using) flashing boot and still no success.
Click to expand...
Click to collapse
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Wait, so it opens recovery by just turning on your phone?
Click to expand...
Click to collapse
Yes, exactly.
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
I will give this a try and report back. Will either be after lunch or this evening.
If you're changing mtdpartmap.txt (try 125 25) you need to wipe ALL, flash fr-recovery, wipe ALL again, reboot recovery (safely), flash rom/gapps, flash fr-boot, reboot. Once you're in the rom, open terminal (su) or adb shell and type "df -h" and it will show you how much system, data, and cache, are using, you then can change your mtdpartmap.txt accordingly, follow the steps I just listed.
Click to expand...
Click to collapse
Gave it a try, still boots directly into recovery.
bphem3 said:
Gave it a try, still boots directly into recovery.
Click to expand...
Click to collapse
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?
il Duce said:
what rom and gapps did you flash, and how are you "booting" - like with what buttons?
also, please list the EXACT steps you took. And what version of hboot do you have, and what recovery, and what version of firerat?
Click to expand...
Click to collapse
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
FYI step 13 is unnecessary, that kernel is already in aospCMod and boots at 691. I guess I would try FR-1.5.8 versions and see what happens (that's what I have), the steps look right to me. You could also try leaving out the gapps and see if just the rom boots, you could also try flashing the last working version of recovery you had (i.e. cwm 3.0.0.5). It's also possible you got a bad download of any one of the above items, so try new DLs too. Report back, I am now officially curious.
I am unsure how to flash another version of recovery, I always use RomManager and I am terrible with adb. I tried using some one of the herocimg.zip to "install from zip" and I kept getting "installation aborted".
I will try FR-1.5.8 and report back.
/me bangs head on keyboard
#eatshit1clickrootmethod!
/me bangs head on keyboard
#eatshit1clickrootmethod!
Click to expand...
Click to collapse
I first used adb and push and blah blah...... 8 months ago.
Then I discovered OneClick! I used to be way more into the technical side of this stuff and then got busy with work and now I am extra lazy!
FYI:
HERCIMG.zip is a partition zip flashable in hboot/bootloader and ONLY if you're s-off
HEROIMG.zip is the same thing, but for a GSM hero....
Hopefully you can figure it out. I hate to say it, but 99.9999999999999999% of the time something doesn't work that others have had success with, it's user error. I'm not trying to be mean, I often miss steps too and need to ask for help. I don't know what you COULD be missing since it sounded like you did everything right, but I would say re-read all the stuff you're doing and hope you see something you may have missed. Best of luck, and please report back if you fix it to help others who may see this thead in the future.
No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).
bphem3 said:
No offense taken. I have had plenty of practice with this with my phone and my wifes and never really had any problems other than user error that I usualy catch. And it's alwasy something silly like flash & wiping out of sequence.
Good information on the HERCIMG and HEROIMG, I did not know that.
Is there a way to RUU the phone from a recovery zip install, (seeming how that is all I can access).
Click to expand...
Click to collapse
Not that I know of but you should be able to do it from the bootloader (hold volume down press power - from an off state) and run the RUU.exe from HTC.com.
lol, yeah, that just puts me back in recovery...
bphem3 said:
lol, yeah, that just puts me back in recovery...
Click to expand...
Click to collapse
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?
il Duce said:
Well that's nuts. I don't know how you don't have a bootloader, but you do have a recovery... anyway, I guess grab the FR-remove zip that correlates with whatever FR version you have and run the steps again, i.e. wipe all, flash FR-remove, wipe all, reboot recovery, etc. Hope that works. By any chance did you format /misc in the mounts & storage menu?
Click to expand...
Click to collapse
Format /misc is not listed anywhere. I'm at a loss. I have tried everything over and over and I am still getting the same results. The only thing left I can think of is to redo everything via adb. I'm not 100% on how these phones or linux devices work but it's as if there is something worng with the boot sector and/or sequence of the device.
It doesn't make sense that the first run at all this was flashing aospCmod (mtd 125 2, FR-1.5.3) and everything was working normal. I decided to go back and redo the process with (mtd 102 2, FR-1.5.3). Now this has to be where I or something screwed up. Maybe I did things out of order, got a bad flash, something but I do not know what. When I rebooted, just a normal reboot, it went directly into recovery. Now I have flashed a rom before and had the mtdpartmap.txt too low it caused it to hang on the first boot when the logo for the Rom was shown during loading. To fix this I just adjusted the mtdpartmap.txt.
This time things are different. When I power the hero up the phone vibrates, the white backdrop with green HTC comes up, it sits for approximately 5 seconds, then recovery loads.
bphem3 said:
1. wipe data/factory reset
2. wipe cache partition
3. format /boot
4. format /cache
5. format /data
6. format /system
7. wipe dalvik cache
8. flash fr-recovery
9. repeat steps 1-7
10. reboot recovery (from advanced menu)
11. flash rom
12. flash gapps
13. flash kernel
14. flash boot
15. reboot system (from main menu)
aospCMod-HC-20110421-signed.zip
gapps-gb-20110325-signed.zip
aospCWMod-HC-20110421.img
DecaFuct-691.zip
FR-boot-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
FR-recovery-v1.5.6.zip (I have tried both 1.5.6 and 1.5.3)
mtdpartmap.txt
Not sure on the hboot. When I simply turn the phone on it boots to recovery. I used to have to press and hold power + home to get into recovery. I also used to be able to press and hold power + home + back and get intot he htc reset menu (or whatever it is). Prior to this happening I never tried to get into hboot (vol up/dn + power) however if I try to now it just goes to recovery. All combinations I have tried it just boots to recovery.
Click to expand...
Click to collapse
Something about these steps didn't seem correct to me, so went back and read.
After step 8. flash fr-recovery
It says you went back and repeated steps 1. - 7.
I believe you only need to repeat steps 4, 5, 6...the others are probably optional, but I'm pretty sure 3. format boot...is something you don't want to do AFTER doing fr-recovery. then again, I may be overthinking it, and might be completely wrong. I'm sure someone will tell me
My own personal rule is to not make any assumptions and follow the steps listed and don't add extras.
(also, I violate that rule occasionally and usually end up doing a lot more work)
Hello everyone,
I've tried to install CM9 on my Samsung Galaxy S I9000. However, I must have done something wrong in the process. I'm totally new to the whole custom ROM thing. I'll try to list the steps I performed to install CM9. I hope someone can point out where I went wrong.
Generally, I followed the instructions given in http://forum.xda-developers.com/showthread.php?t=1363593 .
1) Installed "ROM Manager" (https://market.android.com/details?id=com.koushikdutta.rommanager&hl=de).
2) Rooted my phone according to the instructions in http://androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvr-firmware/3/ . This uses Odin 3 v1.7 and also installed CWM Recovery (v3.0.0.5) . I checked that my firmware exactly matches the one for which the description is for.
3) Performed a backup using CWM Recovery.
4) Performed wipe (data/factory reset AND cache).
5) Installed CM9 using CWM which I had downloaded from the links given in the thread given at the beginning and placed the four .zip files (CM9, Google apps, Google apps fix and Faceunlock) on my external SD card. I only realized afterwards that the instructions said to place them on the internal SD card.
6) Installed Google apps, Google apps fix and Faceunlock using CWM.
7) Selected reboot in CWM. However, the device didn't boot into Android. First I saw the CM logo screen, then the phone got stuck on the "Samsung Galaxy S I9000" screen.
8) Read instructions again, realized that I forgort the wipe after installing Google apps. Performed the two wipes again, however the problem remained.
9) Read instructions again, realized that I was supposed to install the .zip files from the internal SD card. I assumed that was the step I went wrong. So I decided to restore to my stock ROM which I had backup'ed before. I used the restore option in CWM, selected my previous backup (located on external SD card) and performed the restore.
10) However, the phone still does not get pass the "Samsung Galaxy S I9000" screen. When I boot into CWM, the following appears on my screen
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:Unable process volume! Skipping...
Checking /cache...
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:Unable to process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
The same apperas if I try to do a "restore" from CWM again.
My questions:
1) Where did I go wrong?
2) What must I do to be able to attempt to install CM9 again?
Thanks in advance!
To get back to stock you have to flash a 3 file stock rom with repartition in odin.
i think the best is to get back stock, if you tried to restore a backup. then flash semapore kernel.
Then boot in recovery, wipe. Flash build 12 and gapps then reboot.
Sent from my GT-I9000 using Tapatalk
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
oxyris said:
Hi and thanks for your reply.
Sorry, I don't really understand most of your post
1) What is a "3 file stock rom"? I know what the stock ROM is, however, what is with the "3 file"?
2) Where can I get the proper stock ROM for my phone? Haven't I backup'ed my stock ROM when I did the backup in CWM?
3) What is repartition?
4) What is semapore kernel? Why do I need it? Where can I get it?
5) So according to you I did nothing wrong in my installation and it *could* work if I tried a second time?
Click to expand...
Click to collapse
First take a look in ramads thread: http://forum.xda-developers.com/showthread.php?t=1102881
1. Here you can read how to flash with odin and download the latest gingerbread stock rom
2 your backup will work, but you have to be on a stock rom first.
3. read how to flash with odin in the link.
4. Semapore kernel is a custom kernel, comes prerooted and stuff.
so after you are back stock you can flash this in odin, put it in pda and dont thick repartiton. No you are ready again. turn of phone, boot into recovery mode with 3 button combo, here you can restore your backup if you want. or wipe factory reset, wipe catche and dalvik catche flash build 12 and gapps from internal sd. reboot and enjoy ics http://forum.xda-developers.com/showthread.php?t=1112908 remember to download the correct kernel for your build.
5. hard to say, the best way to get correct cwm is to flash a kernel as semapore or cf root. maybe it was somthing with your cwm (recovery)
Edit: it take some time to boot the first time
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
oxyris said:
Thanks again for your reply.
So I managed to flash the stock ROM. I chose the "XFJV7/XXJVQ/OXFJV1/Sbl (MultiCSC)" which is the newest one for Android 2.3.4. I didn't tick "repartition" and didn't select Pit (what is this?) in Odin.
Now considering the Semapore kernel: how do I know which one to download in the thread you posted? Can I just take the newest one? Will I have root once I've installed this kernel? I'm asking because in the FAQ (semaphore.gr/faq) it says it requires another app (Superuser) in order to have root?
Click to expand...
Click to collapse
its not the newest. you should have thick repartition and 512 pit here. But if the phone boots up i think its ok. only kernel flash its important not to thick repartition.
its best to use this kernel http://download.chainfire.eu/124/CF-Root/SGS/CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
I tried flashing CM9 again with the Semapore kernel I had installed first. It seemed to work, however, after booting into CM9, a screen appeared that said something like "Device encryption failed" and I could not get into the OS. Any idea what that could have been?
I'll give it another try anyway, this time with repartitioning and PIT when flashing the stock ROM and with the other kernel you suggested.
Slightly off topic, but what's with this obsession about 3 file roms that's been going around for a long time? I have yet to see any evidence to support the belief that 3 files rom is someone better than single file rom.
@OP: Try flashing CM7 first. See if that works. Then flash CM9.
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
edit2: According to the CM7 thread (http://forum.xda-developers.com/showthread.php?t=1061946), "you're not able to flash any kernel or run any filesystem you want". So which kernel can I use?
oxyris said:
So what's the difference between a 3 file ROM and a single file ROM?
I've tried again with PIT + repartition, the CF kernel and CM9. However, the whole thing ended in a bootlop (Samsung Galaxy S I9000 foloowed by CM screen).
I don't understand what I'm doing wrong...
I'll try CM7 next...
edit: Something else I noticed. When I connect my phone as mass storage, the internal SD card still contains a bunch of files/folders that belong to apps from my original installation. Shouldn't these be deleted when I did the data/factory reset?
Click to expand...
Click to collapse
Hi,
I'll get 3 weeks ago SGS in a bottloop after flashing CM9 build11 (teamhacksung's) from latest CM7.
I went mad four about few hours, afterthat I decided to reflash stock 2.3.6 (JVX_JV3_JVT.tar).
After flashing with Odin, I end-up with in DBDATA error after rebooting..
So I flashed dbdata.rfs.tar and I've got original 2.3.6 working.
So:
-I've rooted my device again (CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar)
-Installed ROM manager
-Rebooted into recovery
-Flashed ICS port latest builds + GApps + face unlock (and wiped ALL).
No my device is working with ICS,
hope this will help you guys on flashing ICS and don't waste time.
Cheers
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
Phone unnecessarily gets data connection on device encryption password enter screen.
Click to expand...
Click to collapse
But I'm not sure if they're referring to my particular problem.
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
May be the only way is to wait devs to solve that issue.
I'm so sorry that my tips didn't work 4 u...
oxyris said:
Thanks. I've tried your approach, but I'm only getting the "encryption unsuccessful" screen after entering my PIN. It says something like the encryption was lost and can't be completed and that therefore, the data on the phone is not accessible.
In the "Known issues" list in the CM9 thread it says
But I'm not sure if they're referring to my particular problem.
Click to expand...
Click to collapse
One question, do you have your SD Card in your phone when you are going through the install process? If so, take that out before flashing anything. It has been the cause of problems for a lot of people coming to CM9.
Hi, thanks for your replies.
I seem to have solved the issue. When the "device encryption unsuccessful" screen appeared, I booted to recovery using the power button (a menu will appear letting you choose between shut down, restart or recovery) and came into CWM. There, I wiped everything (i.e. factory, cache and dalvik or whatever its called) and rebooted. I could then start the OS without any further problems (until now).
I also noticed that now my internal SD card is actually "clean" again, i.e. it only contains the folders and files that are there when you get your phone new. This wasn't the case when I performed a wipe BEFORE flashing CM9.
I'm using the CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.tar kernel you suggested, maybe that was the problem (I can't recall being able to boot into recovery the first time the "device encryption unsuccessful" screen appeared).
@ryanmat Yes, I did have my external SD card in the phone during the installation process, but thanks for your suggestions.
edit: I will report back if everything goes smooth for a few days.
ok, let me understand...
now you got CWM working and you've got CM9 after wipe all with rooted kernel I suggest you?
Exactly. Let me write down the individual steps I finally performed to get CM9 running.
1) Get Odin and PIT files -> http://www.multiupload.com/51MTA5K1H7
2) Boot phone to download mode
3) Start Odin on computer
4) Connect phone to computer (USB)
5) Flash stock ROM -> http://www.multiupload.com/PKVWPJJZMO (check repartition, put in the 512 PIT file and select the PDA, PHONE and CSC files from the stock ROM, then hit start)
6) Disconnect phone from computer
7) Restart Odin on computer
8) Boot phone to download mode
9) Connect phone to computer (USB)
10) Flash the CF kernel for root access -> http://www.filesonic.ch/file/2356034801 (don't check repartition, no PIT file, select the downloaded tar file as PDA, then hit start)
11) Boot the phone to the stock ROM. After the kernel was flashed, you should have CWM installed. Place the CM9 tar, as well as the gapps, gappsfix and faceunlock tars in your internal SD card. Start CWM and boot into recovery from there.
12) In CWM recovery, select install zip from SD card and select the CM9 ROM. After the installation, my phone automatically rebooted, booted CM9 and got into the "encryption unsuccessful" screen.
13) Hold the power button, select reboot and then select recovery to get back into CWM recovery.
14) Perform factory reset, cache wipe and dalvik cache wipe (found under advanced).
15) Select reboot in CWM recovery, you should now be able to boot into CM9.
16) Reboot into CWM again and install gapps, gappsfix and faceunlock if desired.
I don't know if all of these steps are required or if they must be performed in this exact order. However, it worked for me (CM9 build 12).
and now build 13 is out...!!!
Hi..
I was trying to upgrade my samsung galaxy s plus (GT-19001) device to Android 4.0.4.
i just installed CWM-based recovery v5.5.0.4 on my device by rebooting and selecting (install zip from sd card).
------using mentioned combination of keys -------
Then i placed the files in my phone's internal SD Card.
files are mentioned below:
1-> cm-9-20121011-ivendor-ariesve-rc5.zip
2-> gapps-ics-20120429-signed.zip
3-> recovery-clockwork-6.0.1.2-ariesve.zip
then install 1 by choosing from internal SD card and then 2nd file.
my device prompted completion success messages but it took very short time.
----------------------------------------------------------------------------------------------------------------------
now what happened after doing this. my device is displaying same booting screen of CWM-based recovery v5.5.0.4 on each re-boot.
i treid many times by unplug the battrey but unfortunately unsuccessfull.
After that i did Wipe data/factory reset and wipe cache partition.
----------------------------------------------------------------------------------------------------------------------
I tried it through window's based utility Odin v4.43 but it could detect my device usb driver even after success of USB driver installation.
it didn't display Added in message box.
now what should i do ?
i already installed samsung Kies but still undetected.
I tried some old version of Odin 3v1.8 , it detected the port and displayed Added but failed to write ROM on my device.
-----------------------------------------------------------------------------------------------------------------------
My desktop machine's OS : windows 8 64 bit enterprise edition.
----------------------------------------------------------------------------------------------------------------------------------------------------------
I am unable to install new ofor revert back my OS because when i Hold Vol Down + Home + Power, This is not putting me in Download Mode instead Ramdump Mode.
I need your guidence to resolve the issue. Thanks in advance.
Please ask for further details if required.
I'm not sure I got exactly what you did.
1) You installed CWM recovery.
2) You rebooted into recovery.
3) You installed the CM ROM zip.
4) You installed the GApps zip.
5) You rebooted.
Am I right ? And now you only get access to the recovery ?
If you're coming from a GingerBread ROM, this is normal. Simply, re-install the ROM again (and the GApps obviously). If it doesn't work, tell us.
support required
Einril said:
I'm not sure I got exactly what you did.
1) You installed CWM recovery.
2) You rebooted into recovery.
3) You installed the CM ROM zip.
4) You installed the GApps zip.
5) You rebooted.
Am I right ? And now you only get access to the recovery ?
If you're coming from a GingerBread ROM, this is normal. Simply, re-install the ROM again (and the GApps obviously). If it doesn't work, tell us.
Click to expand...
Click to collapse
Hi Einril.
I try to summarize in some chunks for better understanding.
=======================================================================================
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask further please if anything is unclear, i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Did you try to re-install the ROM from the recovery ? (flash cm-9-20121011-ivendor-ariesve-rc5.zip again)
new post
Einril said:
Did you try to re-install the ROM from the recovery ? (flash cm-9-20121011-ivendor-ariesve-rc5.zip again)
Click to expand...
Click to collapse
Hi Erinil,
I think i installed but not sure.
Could you elaborate the re-install ROM steps ?
I tried but same recovery display of CWM-based recovery v5.5.0.4, comes again and stay on recovery mode screen.
How my OS will be started?
It might be possible , i am doing something wrong.
Could you enlist the steps?
Ok.
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
This, I think, is the cleanest install you can do. Tell me the result.
Einril said:
Ok.
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
This, I think, is the cleanest install you can do. Tell me the result.
Click to expand...
Click to collapse
Einril I tried it same as you explained in steps.
It didn't worked nor display any error during this process.
I think my problem is that. when i start my device it automatically entered into the recovery mode of CWM-based recovery v5.5.0.4..
whether i hold Vol+ and Powerbutton or not, it entered into the recovery mode each reboot.
It might be possible that OS has been installed sucessfull but how the OS will be started now?
Hum, that's strange. You say you can access to Download Mode ? Are you able to flash back the Samsung stock ROM ?
Hi Einril,
What does that mean? Means that Reverting to Gingerbread through Desktop Window OS?
I am unable to revert from my One Laptop (i7 3610 & WIndow 8 - 64 bit) but i am able to revert from my OLD laptop (OS is : window 7 32 bit)
Ok, I heard that some people are having issues with USB drivers on Windows 8. But if you can restore Gingerbread with your old computer, this is great.
Can you try to re-install a stock gingerbread firmware, with re-partition enabled, and then to try again the procedure I gave you ? This way, we are sure that your previous attempts have no effects on the result.
Einril, I have installed stock gingerbread firmware on my device and it is working now.
now guide please how to re-partition? Do you mean using CWM recovery ?
Could you simply enlist the thing which i will have to do now on fresh gingerbread OS?
I 'll tell you today night because right now i am not at home.
Well, if your gingerbread frmware is working, you don't need to repartition.
Now, simply re-install ClockworkMod Recovery, and re-do the whole installation process I gave you. By the way, you said you installed ClockworkMod recovery by flashing a zip in recovery. Isn't it supposed to be a .tar.md5 to flash via Odin ?
Yes i installed ClockworkMode Recovery from recovery mode.
I haven't tried with .tar.md5 using Odin4.43.
I 'll try with both throught Clockworkmode and Odin.
In fact i have tried many time 2-3 months ago too through TeamWin Recovery . problem was same.
It didn't start my OS instead displaying its recovery screen and operations.
i tried but all in vain.
Couldn;t be successful.
it just start from CWM recovery mode and so. not switching into the other mode.
hi
i root my phone with kinGo app and it succees..
i also downloaded Rom manager and flashed clockwordmod 2.5.1.2 recovery..
however when i reboot to recovery, it shows me the "sumsong recovery utils" and not the clockwordmod recovery...
also, there is no any option for "install zip" for flashing Rom
what is the problem? can someone help me?
thanks alot
this is what i see:
Android System recovery <3e>
Samsung Recovery Utils - for BML-
Enter: OK Key. Select: Vol UP / Vol Down
Reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal sd-card
i have the same problem as here, however i didnt solved it yet:
http://forum.cyanogenmod.com/topic/34669-not-booting-into-clockworkmod-recovery/
What firmware are you on? You could try flash another kernel made for your firmware (CF-Root, Speedmod, Semaphore GB) and see if that fixes the problem
Sent from my GT-P7510 using Tapatalk HD