[Q] How to install CyanogenMod 10.1 on my Samsung Galaxy S Plus - General Questions and Answers

hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop

The files you got are .ZIP files.
It should be possible to flash these using the recovery. I have To check back for further instructions cause i'm not familiar with the s+ but cwm should be installed automatically when the kernel has be installed.
Sent from my GT-I9100 using xda app-developers app

Did it work?
Sent from my GT-I9100 using xda app-developers app

Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app

lil.masoud said:
Hey dude...u must wipe data,dalvik....maybe it can help u...
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
You have to wipe data and cache, wiping dalvik cache is useless.

anoopgkris said:
hi folks,
Need information on how to load CM 10.1 Android 4.2.2 on my Samsung Galaxy S Plus.
Currently i have the CM 10 Beta 4 (JB 4.1.2) installed. Current recovery is Recovery-clockwork-5.5.0.4-ariesve.
I've downloaded these files.
cm-10.1-20130622-dev_connection_team-release2-ariesve.zip
DevCon-gapps-jb-20130622-signed.zip
cwm6032-Build2-ariesve-alireza7991.zip
Kernel_JB-4.2.2_3.4_20130622_Google-4.6_Stock_Signed.zip
When i checked the AriesDevCon team's link and XDA Wiki Samsung SGS+ link there was some confusion.
The Wiki link doesn't say anything about the recovery installation. Should i use Odin to install the CWM6032 or just put it in the SD card and reboot into recovery? I'd used Odin for the 5.5.0.4 recovery.
From the XDA forums on recovery (alireza7991's) saw that i could use Odin to install the recovery first.
Also, what do i do with the 3.4 kernel ? Should i load that too in the SD card before recovery mode for the installation?
My current kernel is 3.0.70.
Could someone with the proper knowledge please guide ? And please provide the exact steps and the files needed.
I've done the CM 10.1 already and it worked pretty well, but was not able to do any upgrade later (to release 2.5 etc). Had my phone soft-bricked two times and had to install the stock Gingerbread ROM to come back to JB 4.1.2 ROM.
regards,
Anoop
Click to expand...
Click to collapse
It is not necessary to install recovery before every ROM installation. CWM 5.5.0.4 is a stable and safe recovery for our device.
According to the kernel i recommend you to use K^Kernal 3.4.x. It is more battery friendly with good performance.
The procedure is as explained in there
1. Boot in to recovery and
2. flash CWM 6.0.3.2 (if you want to, otherwise skip this) and reboot in to recovery.
3.Wipe data(not necessary when you are coming from a previous build of the same ROM, but recommended), wipe cache, and wipe dalvic cache
4. Flash ROM, Flash Gapps and flash kernel and reboot,
You are done.!

[SOLVED] How to install CyanogenMod 10.1 on my Samsung Galaxy S Plus
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.

anoopgkris said:
Hey folks,
Thanks to all of you for the kind advises!
In fact, i checked for any reply one hour after posting my question and only H3llwar's one reply was visible.
Was too impatient and thought to go ahead with the Modding.
First tried to flash the latest recovery cwm-emmcbrickedpatch-ariesve-6.0.3.2-alireza7991.img using Odin.
This one stuck at one stage (<1> recovery.img download) and didn't move further. So disconnected the USB and removed the battery (I forgot though in what sequence). I expected this to happen since it had happened two times before when trying to flash a non-tar recovery. Also I expected my phone to be soft-bricked, but luckily it did'nt. :good:
Then went through some more info on XDA and other forums and found a WORKED.rar solution.
from http://forum.xda-developers.com/showpost.php?p=30015714&postcount=22
Used that AriesVE.ops version and the recovery-clockwork-6.0.1.0-ariesve.tar.md5 and was able to flash the new recovery.
The reason i flashed the new recovery is that because i always used to find on these forums to use a specific recovery for a specific ROM.
Anyway, then i loaded the CM 10.1 and Gapps into the SD card, set debugging mode on and restarted in Recovery mode.
Then backed up data (Nandroid). Then wiped data/factory reset and wiped cache partition.
Then asked recovery to install from zip card selecting the CM10.1 ROM followed by Gapps. These processes happened very fast this time.
Then rebooted and there it was, a new magenta Cyanogen footer logo along with with the Samsung logo.
Skipped the initial parts and went to the About Phone section with the Android 4.2.2 indication.
Was very happy to also see my Kernel updated to 3.4.49. Three days now on the new ROM and loving it, battery life improved by at least 5% (from the 4.1.2). But missing the 4.1.2 fonts for the clock etc. Although the other internal fonts are smoother and easier on the eye.
Pasting the info screenshot here.
Click to expand...
Click to collapse
You tried to flash .IMG recovery file via Odin. That won't work.! You need a .tar or .tar.md5 file to flash via odin.
Sent from my GT-I9001 using xda premium

Good battery life - CM 10.1
Hey Jabrief, thanks for the advise, I'll note it.
Until now, CM10.1 - 4.2.2 is running very smooth on my SGS+. Getting a very good battery life too. GPS is somewhat slow but maybe it's because odd the cloudy weather all the month.
Attaching a battery stats pic.
Got 32 hours and 40 mins on single charge.
About 16 mins of call, 45 mins of browsing in all.
thanks,
Anoop

Related

Infuse Loops at Recovery after RemICS flashed.

____________________________________Solved, thanks for all who offered help.___________________________________
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
________________________________________________Solution________________________________________________
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster.
Post sent to dev thread of this ROM, just hang tough, tell the storm troopers arrive....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2
rkkaranrk said:
Do u have the GB boot loaders ? If not flash them......will solve ur problem.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Gb bootloaders would not cause this problem...it only causes rainbow...I've had this happen to me countless times when I was porting Roms back when I had an infuse...I just came to the conclusion the the ics recovery is buggy and is borked easily
The fix, flash back to stock via heimdal or Odin, then get cwm recovery and flash the Rom using gingerbread instructions (double flash) (unless you flash the ics kernel...in that case one flash)
If you want detailed instructions on flashing or getting gb bootloaders (in case you have rainbow recovery) then check out my infinitum port thread (in my signature) at the bottem of the OP you will find some good instructions...I wouldn't reccomend flashing it though as it is old and doesn't have the latest fixes...but the flashing instructions are still good
Sent from my HTC PH39100 using Tapatalk 2
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
The bootloaders fixed the rainbow recovery, what fixed your whole problem was that you flashed stock...so you pretty much killed two birds with one stone, you fixed your rainbows and you fixed your soft brick...
The pink recovery you referred to is known as rainbow recovery
Sent from my HTC PH39100 using Tapatalk 2
Mate u missed the part i said i flashed stock twice first time with out the BL and then with the BL, When i flashed stock without the BL and from there when i flashed REM i lost recovery so and flashed again with the BL this solved.
I had read all aver that BL does not mess with flashing only gives u messed recovery on ICS and rainbow boot but i don't know how this worked for my friends phone.
Edit: i know how rainbow recovery looks like but the fonts are still in blue color but in this case the blue fonts were pink in color and were too small if the normal size of the font say 10 then the size in this recovery was like 2/3.
rkkaranrk said:
I had faced this same issue last night when I was trying to flash REM ics on my friends phone and it don't have the GB boot loaders I tried to flash the recovery from the OP and after flashing recvery I was not able to RAF anything the fonts were so tiny and were in pink color.
After all this I flashed it back to lb3 thanks to Scott and from there I flashed it again and this time lost recovery was not able get the phone to recovery, So finally I decided to flash the GB BL with heimdall (thanks to qkster) flashed stock one more time with BL ticked and the REM ICS, All good.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2
RemICS kernal question
I am currently using version 1.3 on my infuse. I have noticed that the past couple of days that the phone seems to be slowing down and doing soft reboots every once in awhile. I have gone through and deleted a bunch of apps and moved some to my sdcard and it has gotten faster, however I still have some slow downs and reboots, especially when coming back to the homescreen after exiting an app (It seems to take a few seconds to redraw the homescreen) or if an app locks up. I also have RemICS version 1.3.1 on my Captivate and it has a different kernel (Devil Kernel). I was wondering if there was a version of this kernel that would work with the Infuse as my Captivate seems to be rock-steady and fast. I have not overclocked or messed with the memory settings on the Infuse, but I have noticed that no matter what Rom I use on it (even stock Gingerbread loaded by ATT repair center), it seems to slow down and mess up over time. RemICS so far has seemed to last the longest and I would like to keep it going smoothly. Any suggestions would be extremely helpful. Thanks!
Chris Veverka
[email protected]
cx831 said:
Hi All, I have just flashed the RemICS ROM 1.3 and i have followed the set of directions for Gingerbread users, which I previously was. The installation had been successful until I did the final Reboot, where it loops back into the Recovery mode even after numerous of re-flash and reboots. I'm pretty sure the ROM is installed, yet it would not load into the OS, thoughts? Thanks everyone in Advance.
http://forum.xda-developers.com/showthread.php?t=1613523 I had the option C installed initially, for everyone's info.
Click to expand...
Click to collapse
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.
cx831 said:
Yes i have flashed the original stock gingerbread (the one listed in the OP) back onto my infuse last night. The phone is working flawlessly at this moment under the stock GB.
And the ICS Rom was flashed twice everything worked, cache cleared, factory reset, no rainbow, and the only problem was recovery looping. Im considering reflashing the rem ICS rom sometime soon but i doubt I'd see any difference, any chance i can get ICS working? Thanks for all the above replies
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
be positive, you can get ICS running in no time. follow our directions and you shouldnt come up with any complications
1. wipe data, cache, and dalvik
2. flash remICS
3. after reboot you will be stucked at samsung. pull out the battery and place it back in
4. enter recovery with 3 finger combo (vol up & down, and power). release power when samsung appears
5. flash rom again, and reboot
hopefully you should now see your phone booting up into ICS
http://forum.xda-developers.com/showthread.php?t=1783899
rkkaranrk said:
There is no reason for it not to work if done properly u will boot in to a new world.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
babamanan said:
yes it happens with me when i flash ics over gb and after every thing phone just struck up in blue recovery it happens coz some previous system files sometimes not completely deleted, dont worry just do following as what i do.
search and download infuse toolkit v1.10 and when u got in bootloop in cwm just flash this toolkit from cwm and follow the instructions till option full wipe or complete wipe after that it will again boot up in cwm recovery now wipe cach system and again install ur rom.
Click to expand...
Click to collapse
Thanks for the tip and I have made 3 more attempts today, which all failed. I have returned to the stock rooted GB as mentioned at the initial thread each time to return to a working OS. I have recorded my last attempt of the day throughout the duration, including the method you have mentioned. I'll list what I have done in short below;
youtube.com/watch?v=RGCEkRVlHog (Unable to embed links, my apologies for any inconvenient)
1. Factory Format, Wipe Cache, Wipe Delvik Cache,
2. Flash rom from internal SD,
3. Advance > Reboot Recovery,
4. Flash again after re-enter Recovery,
5. Boot-looped as expected, thus flashed Infuse Toolkit v1.1,
6. Wipe Cache and Complete Wipe,
7. Quit and automatic reboot,
8 -Stuck at Cyanegen Mod Screen, wont enter Recovery Mod again-, no matter what i do. I tried pulling battery out and reboot into recovery, stuck anyhow.
Then I entered Odin and flashed stock GB back and my phone is working fine. Please point out any missing steps or mistakes to the installation. I suppose it's a conflict with the internal SD rather than system error, welcome to any suggestions. Again, thanks for all the replies so far. Anything is appreciated!
ps: I will give other Ice Cream Sandwich ROMs a shot this weekend, hope the above would not occur on the other roms. :/
Don't use the reboot option from recovery and did u tried downloading the ROM file again.
Sent from my SGH-I997 using Tapatalk 2
Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.
cx831 said:
Sorry for the late update, but no luck for any other ICS roms available for infuse. All ended up the same, blue recovery bootlooped.
I'm wondering if there's any way that I can wipe all the data, including the stuff on internal SD like an ultimate factory reset with only the running ROM left so I can do a clean ICS flash? Thanks all.
Click to expand...
Click to collapse
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm
I had the OP's exact issue when I upgraded from CM7 to remics last week. I was running froyo bootloaders and LB's CM7 (http://forum.xda-developers.com/showthread.php?t=1195525) with whatever kernel came with that (it had blue CWM).
I followed the instructions for "coming from Gingerbread" in the original remics thread (before it was updated this week) and I ran into OP's *exact* problem with looping back into recovery. I got on the #infuse4g IRC and got help from Aerema(sp?) and entropy. I learned some new things and tried everything they suggested (a lot of which I'm reading in this thread)... but none worked for me.
To get to the point, in the end... and I know this doesn't seem to make sense, but what worked for me was using Odin to "return to stock", then flashing the kernel from the remics package and flashing remics.
I had been using qkster's Heimdall OneClick return-to-stock (http://forum.xda-developers.com/showthread.php?t=1524081). Heimdall always worked and didn't report any problems. I even used heimdall command line interface when I upgraded from froyo to gb bootloaders.
To this day, I don't understand why using Odin return-to-stock (http://forum.xda-developers.com/showthread.php?t=1705260) got me out of the recovery loop.
I *think* my upgrade path went like this.
Starting with CM7Kang/froyo BL
1) download remics1.3.zip, followed instructions exactly & flashed remics1.3.zip from blue CWM.
2) rebooted, ROM worked just fine but had rainbow recovery.
3) attempted qkster's heimdall OneClick GB BL upgrade (update bootloader checkbox). It failed.
4) updated to GB bootloader using heimdall command line (http://forum.xda-developers.com/showpost.php?p=24901128&postcount=3)
5) ** recovery loop ** seemingly tried everything from double-flashing kernel-only using heimdall command line to reverting back to stock (heimdall), format /system, Infuse Toolkit, etc and so on.
6) used ODIN return-to-stock and from there the upgrade went perfectly.
I, too, would like to express my gratitude to bradman117 and everyone else involved in making this ROM available to the general public. I'm really liking it. Nice to have ICS on a > 1 yr old device. Thanks to those who still visit the #infuse4g IRC chan as well.
TL;DR - I had to use the Odin return-to-stock to fix recovery looping, even though Heimdall return-to-stock appeared to be doing everything correctly.
Problem Solved.
qkster said:
It is possible that reboot recovery while in cwm got you in this recovery loop.
There may be a misc recovery img created.
You have to delete that misc with a prepare cwm-flashable script.
On the infuse, mounting usb in cwm doesn't work.
If you can get at it in adb, this command may work:
C:\> adb shell erase_image misc
You will have better luck in factory/data reset in cwm.
Put the phone in DL mode.
Odin or Heimdall back to stock with repartition and start over.
This time around, remember not to reboot into recovery while in cwm
Click to expand...
Click to collapse
Finally got my ICS working now. Can't thank you enough for qkster Heimdall One Click Gingerbread ROM:good::good::good:.
For everyone's reference, the following is what I've done;
1) Flashed the Heimdall One Click GB Stock rom, a big thanks to qkster,
2) Flashed the CWM Recovery just under the same thread,
3) Flashed the RemICS rom with factory wipe and formatting data, system and cache, again after reboot.
4) >Bootlooped at the SAMSUNG screen,
5) Followed the solution of bootlooping under the RemICS thread and flashed Heimdall GB Stock again,
6) Flashed Clockworkmod again,
7) Installed RemICS rom again (Step 3) & WORKING LIKE A CHARM NOW!
I suspect my initial problem was caused by internal conflicts between the Rooted ROM and ICS, yet it is not evident nor I'm experienced to make such conclusion. Anyway, glad that my Infuse is finally able to run on Ice Cream Sandwich and I really dont care about what had caused the problem prior.
Big Thanks to rkkaranrk and qkster. :laugh:

[GUIDE] Root + CWM Samsung Galaxy Ace Plus S7500 / S7500L - Easy Way

Download CWM Recovery.7z from attachments. Extract Recovery.tar
Download Superuser-3.1.3-arm-signed.7z (or newer from http://androidsu.com/superuser/). Extract Superuser-3.1.3-arm-signed.zip and copy it to your SD card (internal or external).
Put your phone in Download mode. Flash Recovery.tar using Odin.
Put your phone in Recovery mode. Flash Superuser-3.1.3-arm-signed.zip from recovery
Reboot and ready
Thanks developers!
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
I didn't needed. The other method posted makes the S7500L keep rebooting into recovery. So, I flashed stock firmware (S7500LVJLH1) with Odin and start over again, but same result.
I'd flashed again stock firmware and just flash recovery with Odin, then just write Superuser from recovery.
I hadn't time to verify if the problem was with boot.tar or with files that are installed in recovery mode by .bat file.
Sent from my GT-P1010 using xda app-developers app
شكراااااااااااااااااااااااااااااااا&#157
thanxssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
Can i use this Superuser 3.1.3-arm.zip for rooting Galaxy Ace S5830 ??
Sent from my GT-S5830 using xda premium
Yeah... For any phone with ARM CPU core
Sent from my GT-I9100 using xda app-developers app
issues after flashing gt-s7500T
lokeshsaini94 said:
So no need to make kernel un secure?
This post goes to my complete guide for Samsung galaxy ace plus...
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Android System Recovery (3e) problem
i flashed "recovery.tar" as PDA via Odin3...then went into recovery mod but it say "Android System Recovery (3e)"..i think its Samsung's default recovery ... so where is CWM???
hi guys!
i have a problem with my ace plus and i have to bring it to a warranty center.. so i have to restore the stock rom and un-root.. any help?
is there a guide to do it? do you know where i can find the stock rom?
thanks a lot
If I root my phone, any advantage in the new root between old 1....
Can someone help me?
My Galaxy Ace Plus (S7500) doesn't want to boot in download mode
Thanks guys, great work
However, my Ace plus is GT - S7500W (London 2012 limited edition)
Is there anyway to root it?
Thanks so much!
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
kol12 said:
Hi, Is there a easy way to unroot this method? Do all my files and settings remain intact when using this root method?
Thanks.
Click to expand...
Click to collapse
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
farodriguez said:
This method don't erase your data, just write a custom recovery and add SuperUser app and bin to your system.
The best method to unroot is installing stock firmware package.
Click to expand...
Click to collapse
Thanks. So does installing stock firmware not write any files to the data partition of android? What about the apps that are included in stock firmware sms app, contacts,call logs, maps etc, will those apps data be lost with installing stock firmware?
---------- Post added at 11:27 AM ---------- Previous post was at 11:23 AM ----------
The recovery.img you have is larger than the stock firmware recovery.img. Does this write more data somewhere?
here is Android 4.1.2 for Galaxy ace plus working
http://forum.xda-developers.com/show...5#post38450355
fido747 said:
I got my hands on a gt-s7500t yesterday and started xda searching on how to put a custom rom on it. i tried all the methods listed under s7500 to put cwm in it but none worked and whenevr i tried to enter either through pressing vol "+" "-" home and power it never enetred recovery nor it enetered through adb so i moved onto flashing cwm through s7500L guide. so by using http://forum.xda-developers.com/showthread.php?t=1725198 guide, i flased successfully flashed cwm and the phone was stuck in recovery boot loop.
I successfully rooted by through cwm and even installed a custom rom but the dammit phone never came out of the recovery loop, so i went to the next step and downloaded a stock UK vodafone firmware from sam mobile and tried flashing that since australian s-7500t stock rom is unavailable.
Now odin gave a "fail" meesage when it reached to flashing fat.bin, i tried almost 3 different stock roms but same problem. I took the battery out, and tried starting the phone the phone started but no display, so i connected it to samsung kies hoping kies will have a solution, well as it turned out that when i went into emergency firmware recovery, the device screen magically lit up for few seconds and went dark again.
i was baffled so i decided to repeat the process http://forum.xda-developers.com/showthread.php?t=1725198 and flash cwm and boot again. well this time when this completed and phone restarted the phone restarted normally and everything seemed fine, so through adb i went into recovery mode again just to see if all was working fine, but now its the same recovery loop again, have tried wiping the dalvik cache, factory reset and cache reset but nothing happening, HAVENT tried the advanced>recovery reboot> procedure, yet.
now am thinking of two options. first to try install another custom rom and see if that might hellp or since iv got another galaxy ace plus, try to extract the custom s7500T rom out of it somehow, (if u guys can tell me howto, cuz i tried titanium backuo but since it requires root and since i cant get into cwm without using s7500L technique which soft bricks i cant use titanium backup to extract the rom)
Anyone got any idea what to do? is there a pit,bootloader,csc,phone etc files that i can flash through odin rather than flashing a complete package through PDA?
or can i just flash boot.img from a stock rom using PDA and you guys think that will solve the problem>?
Click to expand...
Click to collapse
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Corsario_Negro said:
I've been having the exact same problem as you with my S7500L. Boot loop error after installing custom roms. I can, however, install CWM and obtain root without problems.
I really don't understand how the s7500L rom guys developed them... how did they get out of the boot loop.
I tried replacing the boot.img from the custom ROM with one from a stock rom... nothing.
Click to expand...
Click to collapse
Hi i have the same problem and the solution is flash this http://forum.xda-developers.com/showthread.php?t=2255561
i used odin, and works perfect.
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
vasilisaerox said:
i installed the cwm and i cant enter recovery it sthows a trinagle sith ! ander the samsung and after it boots normaly
Click to expand...
Click to collapse
Just flashed recovery and i'm having the same issue. Original 2.3.6 installed never touched.

[Q] Can't Flash ANYTHING!!!!

Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill

Phone won't boot into ClockworkMod Recovery

Hi,
I currently have ClockworkMod Recovery 6.0.2.3 installed and am using ROM Manager Premium 5.5.1.5 to attempt to install CyanogenMod.
I have the correct rom downloaded for the Verizon version, but every time I try to boot into the ClockworkMod recovery, the standard Android Recovery screen comes up instead.
I have followed about 3 different tutorials, and each ended in the same result.
Any idea what could be going on?
Thanks!
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Edgehood said:
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Click to expand...
Click to collapse
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
CAKELIE said:
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Click to expand...
Click to collapse
How did it fail?
Sent from my LG spectrum (that's right) blazing fast on cm10!
I am having almost the same problem. I rooted my phone using this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT6 - ZSLO2 Fixed for bootloop
ZCLSF (no bootloop fix, proper default.prop)
http://d-h.st/users/philz_touch/?fld_id=16061#files
taken from here: http://forum.xda-developers.com/showthread.php?p=31911620#post31911620
as it matches my phone make, build, kernel's date, model, etc. The trouble is when I go to recovery mode from ROM Manager it just stops on its way showing me this green little robot and a progress bar in the middle and it could stay like this for hours without moving anywhere. I have to press my power button and then it moves on and reboots into CWM. I have tried a whole lot of different rootings methods but ROM Manager v5.5.3.7 simply refuses to work with PHILZ-CWM6-DDLSC-ODD-5.06.1-SIGND.ZIP... I am completely lost...
Could anybody suggest / advise anything please? I would highly appreciate it Many thanks in advance!
I am on Android 4.1.2 Jelly Bean, Samsung Galaxy Note GT N7000, build number is JZ054K.N7000DDLSC, baseband version is N7000DDLS6, kernel version is 3.0.31 – 906407 March 6, 2013.

[Q] help upgrading from 4.1 to 4.3/4

ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app
Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.
resolved. thanks guys.
Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.
jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.
The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.

Categories

Resources