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
شكراااااااااااااااااااااااااااااااا
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.
I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?
This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2
I have a Tmobile Galaxy S 4G t959v which is rooted. Today I was reading I could flash kit kat rom on to it but I said I needed CWM 6.0.4.4 So I went on ROM Manager to update it but I couldnt find the proper version for my phone so I flash google nexus S which I think its 6.0.4.3 after I flashed it rebooted but it stays on root page I turn it on recovery mode but it still stays in the boot page. Dont know what to do ?
CartoonsAndCereal92 said:
I have a Tmobile Galaxy S 4G t959v which is rooted. Today I was reading I could flash kit kat rom on to it but I said I needed CWM 6.0.4.4 So I went on ROM Manager to update it but I couldnt find the proper version for my phone so I flash google nexus S which I think its 6.0.4.3 after I flashed it rebooted but it stays on root page I turn it on recovery mode but it still stays in the boot page. Dont know what to do ?
Click to expand...
Click to collapse
You made a couple common mistakes...first of all, you didn't do your homework. If you had read through the threads pertaining to our phone, you would have seen that ROM Manager doesn't work on our phones. Secondly, you tried to flash a recovery for another phone.
Please read Lumin's guide on how to use Heimdall to flash to rooted Gingerbread (http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2)...then read the developer's instructions on how to flash the KitKat ROM of your choice once you are have successfully flashed rooted Gingerbread.
Flashing ROM's requires reading and patience.
I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers
Hello everyone,
I have rooted 2 s5's so far using the step by step directions I found on a few websites. This was late last year. My friend recently got a new S5 from Sprint and it is blue. The box notes it as a G900P UD.
So I Odin'ed SuperSU and Philz on it, loaded back into the sprint stock rom, then applied root, deknoxed it, then booted it into recovery mode. I then attempted to load the MOAR NE5 v1.1 rom (After factory reset, clear cache, and clear dalvik cache. This is the same one I put on the other 2 S5's). When I rebooted, it would hang at the Android logo screen indefinitely. I then tried the newer version of MOAR v 6.0 OA6. With this rom, it loads the splash screen then hangs for about 5 minutes before booting back into recovery.
Any ideas? I found the link to the SM-G900P Full Restore with directions to just odin it on there. Will this fix it? Or is there anything else the community can suggest? I will be upfront and say I have never used ADB for any of this, but I am willing to learn
Antowas said:
Hello everyone,
I have rooted 2 s5's so far using the step by step directions I found on a few websites. This was late last year. My friend recently got a new S5 from Sprint and it is blue. The box notes it as a G900P UD.
So I Odin'ed SuperSU and Philz on it, loaded back into the sprint stock rom, then applied root, deknoxed it, then booted it into recovery mode. I then attempted to load the MOAR NE5 v1.1 rom (After factory reset, clear cache, and clear dalvik cache. This is the same one I put on the other 2 S5's). When I rebooted, it would hang at the Android logo screen indefinitely. I then tried the newer version of MOAR v 6.0 OA6. With this rom, it loads the splash screen then hangs for about 5 minutes before booting back into recovery.
Any ideas? I found the link to the SM-G900P Full Restore with directions to just odin it on there. Will this fix it? Or is there anything else the community can suggest? I will be upfront and say I have never used ADB for any of this, but I am willing to learn
Click to expand...
Click to collapse
If you want to install MOAR 6.0, follow all the instructions in this post from the MOAR FAQ.
In short you can't have a Samsung Lollipop rom on a Kitkat bootloader. Flashing the OA6 odin stock tar should do the trick. It will wipe your data so do a backup.