No su access, no root.
This was the tutorial I followed:
http://forums.androidcentral.com/ep...95-rooting-ei22-gingerbread-instructions.html
I saw Chris41G's download site had a 'epic4g' version of the ACS recovery. Do I need this instead? What am I doing wrong? No su icon, no 'su' access in ConnectBot, no Android Wifi Tether. Odin worked fine.
Not sure what that procedure says to do but you would Odin in clockworkmod recovery 5.0.2.7, with reboot unchecked. Pull battery when done, put back in and boot right into CWM with 3 finger salute and flash a prerooted custom ROM of your choice from Development.
Sent from my SPH-D700 using XDA App
I had the same problem when rooting stock EI22. I flashed ACS recovery 1.0.0.5 (or whatever it was) and then first tried to flash the su binaries which worked but I was unable to maintain root access. Anyway, long story short, I flashed the CleanGB kernel w/ root from recovery and that worked perfectly. That also made ACS Recovery (CWM) stick on reboots.
Final procedure I used:
1) Boot phone into download mode (pwr + 1)
2) Flash ACS Recovery .tar file (uncheck everything)
3) After flashing, pull battery, pull USB (phone turns off)
4) power on into recovery (pwr + vol down + camera)
5) Install zip SD card. Choose cleanGB kernel.
6) Reboot and enjoy rooted EI22.
Sent from my SPH-D700 using XDA App
is this considered a 'CleanGB'?
http://www.youtube.com/watch?v=b4D0D1Qb7e4&feature=relmfu
No, that is Legendary ROM. I was just saying to flash the kernel and keep the stock 'ROM'. CleanGB is another ROM but the dev has separated out the kernel so it can be flashed separetly. This will maintain all your data (not cache or dalvic).
Sent from my SPH-D700 using XDA App
Related
First off.. newbish 2 part question... I just rooted last night using the 2.2 update from xda regaw... I used and flashed the 2.2-update.zip clockwork he provided...
(also now have Rom manager installed with clockworkmod installed)
For me to use the deodexed 2.2 (rooted deodexed rev3 from steel) I just download place on root of SDcard, then boot into bootloader(vol down+power) apply update.zip and that's it?
If I missed any steps please let me know!!!
(thinking I might missed something please fill in what I missed)
Also would this wipe phone completely as in fresh start?
Having to redo all apps and settings?
Thanks in advanced!!!
All help is appreciated!!!!
(And I did use search before posting)
Sent from my PC36100 using XDA App
First, I would suggest flash the Amon_RA recovery from ROM Manager. Then download the ROM, place on root of sdcard, reboot into recovery ("adb reboot recovery" or shutdown, power + vol dn, select recovery), wipe data/cache/dalvik-cache twice, and finally flash from sdcard (the ROM you downloaded). Reboot. Done.
Sent from my PC36100 using XDA App
sombdy said:
First, I would suggest flash the Amon_RA recovery from ROM Manager. Then download the ROM, place on root of sdcard, reboot into recovery ("adb reboot recovery" or shutdown, power + vol dn, select recovery), wipe data/cache/dalvik-cache twice, and finally flash from sdcard (the ROM you downloaded). Reboot. Done.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay so....
in Rom manager flash the ra recovery v1.7.0.1
Download 2.2 deodexed Rom then place on root of SD card.
Then reboot into recovery(can I do this in Rom manager?)
Thanks again....
Really want this deodexed 2.2 so I can mess with themes and stuff..
Sent from my PC36100 using XDA App
Ep3n3wp said:
Okay so....
in Rom manager flash the ra recovery v1.7.0.1
Download 2.2 deodexed Rom then place on root of SD card.
Then reboot into recovery(can I do this in Rom manager?)
Thanks again....
Really want this deodexed 2.2 so I can mess with themes and stuff..
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Get rid of ROM manager. It's messy. Do it the old fashion way with a PC.
Go to Amon_RA's thread to download his recovery. Latest is 1.8.0.1.
Afterwards, download the ROM, move to your sdcard, boot into recovery, wipe data/cache/dalvik-cache twice, and then select flash from sdcard. Flash the ROM. Done.
ROM manager is just rather limited and leaves room for error. This way you get a clean install every time.
Sent from my PC36100 using XDA App
sombdy said:
Get rid of ROM manager. It's messy. Do it the old fashion way with a PC.
Go to Amon_RA's thread to download his recovery. Latest is 1.8.0.1.
Afterwards, download the ROM, move to your sdcard, boot into recovery, wipe data/cache/dalvik-cache twice, and then select flash from sdcard. Flash the ROM. Done.
ROM manager is just rather limited and leaves room for error. This way you get a clean install every time.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
+1 on these instructions! AmonRA is my preference. Also, if you want to reboot to recovery easily from your phone, go to the market and download "QuickBoot"
This is the story about what happened to my phone today during the ROM upgrade from FC15 to FC18 and how to get out from Samsung Galaxy S II logo screen (if phone is frozen in there), and finally successfully installed FC18 from previous version. I believe my situation that I've experienced today would be most common situation that many people bricked their phone these days and posted their problems in our Q&A session.
OK. Let get started.
I think I was lucky(?) enough today because I've experienced the same thing that lots of people these days reported the issue happened during flashing their Roms. I gave them lots of advice but couldn't solve the issue directly because there are lots of possibilities. My case would be one of the possibilities but may help lots of people too.
One scenario that your phone could stop during the flashing -> Not consistent flashing.
Sometimes I've used Calk's Rom and some other times I've used one-click odin package to flash the rom, kernel and modem. Most recent my pass was, Calk's FC07 Rooted Stock -> sfhub's one-click Rooted FC15 -> Calk's FC18 Rooted Stock. I think if you are moving between Rogue recovery mode and odin mode, the chances that your phone could be bricked are getting bigger.
Before explaining what I did to successfully install FC15, what I'm writing in here is informational purpose only. If you want to follow the same step, please do it with our own risk.
The steps that I followed:
1. The base Rom was FC15 and it was installed thru one-click odin. I installed this version from Calk's FC07.
2. To install Calk's FC18, I flashed Rogue_ET-Stock-1.1.4 tar file thru mobile odin
3. After the Rogue Kernel installed, during the reboot, I moved to Rogue Recovery by pressing vol up + power
4. From the Rogue recovery, I manually cleaned cache/Dalvik/Battery and ran the Calk's modified format all zip file (I do not want to delete my data and spent lots of time to recover it after the rom installed)
5. Installed Calk's Rooted Stock FC18 Rom - *same recovery session, no error
6. Installed Calk's FC18 modem - *just after rom installed, no error
7. Ran Calk's Bare Rom converter 1.3 - *just after modem installed, no error
8. Reboot
9. Now the phone was stuck at Samsung Galaxy S II first screen forever (feeling like bricked or frozen)
The above steps were the steps showing how my phone was stuck in boot screen.
Now let's move to the next step. The following steps were my trial steps to successfully install FC15 rom.
10. My phone was stuck on boot screen, power button and vol up + power didn't worked. Only showed the battery charging status, not moving to other state.
11. Only the key combination was power + vol down (Download mode) and this means that only odin could work.
12. Plugged usb cable to pc and flashed the previous rom again using one-click odin (FC15-CL256308_ROOTED_NODATA-oc-sfx.exe). Flashing didn't show any error and successfully passed.
13. Phone rebooted (stock recovery) and I was able to see everything again from my phone (apps + data).
14. Flashed Rogue FC07 based recovery at this time using mobile odin (rogue_ET-recovery-1.2.2-FC07-rc0.tar
15. At this time did not stop the phone during the reboot and phone completed rebooting. Updated profile and prl. Rebooted phone and moved to Rogue recovery again (vol up + Power)
16. Clean everything again and ran the Calk's modified format all.
17. Installed FC18 rom only at this time
18. Reboot and phone stopped again at Samsung logo.
Repeating the steps again
19. moved back to the step 10 and proceeded to 11.
20. from step 12, instead of flashing whole build, I only flashed FC07 Kernel only thru the odin v1.8.5 (SPH-D710.FC15_CL256308_KERNEL-sfx.eve)
21. Reboot and system came back!
I think some of you already caught the idea in here.
The following steps are the core steps that I did to get rid of stuck boot screen and successfully flash FC15. Because above steps were trial error, you can just follow the below steps.
Final Steps to successfully flashing FC18 from stuck Boot screen:
The following way is only for the case your phone is stuck during the boot.
1. Install Rogue recovery (current version is now based on FC18). I used Rogue recovery 1.2.2 which is based on FC07 Kernel. Rogue recovery 1.2.2 and 1.2.3 are only for ICS roms, so if your current rom is GB based then you have to use 1.1.4 or 1.1.3.
2. From the recovery, wipe all (if you want to keep previous data, don't wipe the data and that's what I did) or run the Calk's format all or modified format all (same as not deleting data).
3. Install Rom and Modem (your choice which one goes first) without reboot
4. Reboot
5. Again phone is stuck on boot screen
6. go to Download mode by pressing vol down + power key at the same time
7. (requires odin PC version) flash the kernel only. You can use the working previous kernel in here or FC18 kernel if it is available.
For me, while I'm working on this issue, stand alone FC18 kernel was not available. So, I unzipped Calk's zip file, extracted zImage file and used it for odin.
8. Reboot
9. Bingo! No stuck on boot screen. After the reboot, if you used previous kernel, then update the kernel thru mobile odin. Or go back to DL mode and odin the kernel again using most recent one. For me, I usually use the zImage file to update the kernel. Be careful when you use the zImage file because I have some experience that this zImage file size is different when it's extracted from phone and PC. I'm not sure it's caused by corrupted zip file or applications extracting the zip file. The total zip file size was same but extracted zImage file size was different (this also could be a reason why phone is stuck on boot screen) - just my guess.
10. All done! Go to setting and update the profile and prl.
Above is all about my story today. There could be something that I missed or incorrectly described. Please be generous and let me know if you want to fix any information from above.
Few ways to avoid troubles
1. Check downloaded file's MD5 checksum and compare it with op's checksum
2. If possible, copy the file to sdcard using USB mass storage method. This is the fastest and safest way to copy the file to sdcard. Sometimes, copying the file thru wifi could be an issue.
3. Plan your scenario to flash
4. if flashing stopped with error or frozen, don't go further unless you know what to do and visit this forum again to ask
5. Always make nandroid backup and be sure no errors on your backup
6. Don't use old CWM Recovery for ICS Rom
7. Don't use any supporting tool (rom manager, rom toolbox, etc...). Go directly to recovery and flash from there (or backup).
8. if possible, stay on same kind of roms (do not jump between ICS and GB many times, especially do not go backward)
If there's more, I'll keep adding on.
I downloaded the .zip file for the upgrade from alpha3 to alpha4 off CM's website, put it on my SDCARD, booted into recovery - looks like stock recovery, (following the steps on CM website) then applied the zip -> it looks like its doing something for about 20 seconds then the little android guy dies and has a red triangle with an exclamation point coming out his stomach. What am I doing wrong?
baseband version: FE10
Kernel Version: 3.0.15-SPH-D710.FD10-CL377892
You need to be using a clockwork mod recovery to flash, stock recovery will not work.
First make sure you are rooted.
Next use either Odin 1.85 or Mobile Odin to flash the EL26 kernel.
Upon reboot, go into recovery mode using volume up+power. If you miss your chance to do so, just pull the battery and try to get into recovery again.
Using CWM, flash per the install instructions.
so do i just odin the kernel back to el26 w/ CWM? the reason i dont want to do a clean install is because i wodnt want to wipe my data. If i odin to EL26 w/ CWM do i need to go back to gingerbread?? Or is there a way i can sat on ICS and upgrade?
what if i used this kernel? [NEW][KERNEL] FE16 Repack with ACS recovery
mazostyle said:
so do i just odin the kernel back to el26 w/ CWM? the reason i dont want to do a clean install is because i wodnt want to wipe my data. If i odin to EL26 w/ CWM do i need to go back to gingerbread?? Or is there a way i can sat on ICS and upgrade?
what if i used this kernel? [NEW][KERNEL] FE16 Repack with ACS recovery
Click to expand...
Click to collapse
If someone tells you how to do it safely, and you choose to do it your way done come crying when you brick, because it still says don't use recovery with ics kernels...
Sent from my Sprint Galaxy Nexus CDMA using Tapatalk 2
dante32278 said:
You need to be using a clockwork mod recovery to flash, stock recovery will not work.
First make sure you are rooted.
Next use either Odin 1.85 or Mobile Odin to flash the EL26 kernel.
Upon reboot, go into recovery mode using volume up+power. If you miss your chance to do so, just pull the battery and try to get into recovery again.
Using CWM, flash per the install instructions.
Click to expand...
Click to collapse
Do exactly what he said here... You're not going back to GB or wiping data. You're just re-flashing a CWM recovery. When you originally installed CM9 alpha 3, you used a CWM recovery. But the CM9 ROM re-flashes a stock recovery (which you can not use to upgrade from alpha3 to alpha4).
So all you do is Odin the EL26 kernel/CWM recovery image (phone in Download mode), and then you reboot and hold vol+ and power to get the phone into the CWM Recovery Mode. From there, you just install the CM9 alpha4, you don't wipe data or lose anything.
thanks man, it worked.
I am new to the forums and didn't want to make a new thread. I am having issues with the GPS (Maps App.) The app loads up i enter the destination i want to go to but it wont find my location where i am at. It just keeps searching for my location...
So i went ahead and downloaded another GPS app ( tele nav.) same issue. I was wondering is there a way to fix GPS issues on this rom? I would like to fix that issue..
anyone have a solution to fixing the GPS issue on this rom???
Please bring me back. I installed CM9 pre5 but forgot to update kernel to get CMW with 3 fingers and now I installed battery mod beta4 and phone justs loops.
I made a backup when I updated before installing battery mod but I don't know how to get phone back into clockwork mod since i didn't install kernel for it after CM9 update.
I need instructions to get phone back up please save me.
Thanks for your fast input...
The Cm9 update includes the kernel. Just three finger boot into recovery.
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Great but what if?
wow that was fast and accurate, many Thank You Zeinzu. I did not know it had CWM on CM9 thinking you had to flash kernels like nyan 5 or shadow cm9 6.3.3 to get it to work.
If by any chance that 3 finger didn't work I would need to use odin to:
via ODIN
1.To begin, download the CWM 5.0.2.7 tar file from the link above.
2.Run ODIN and make sure Re-Partition is unchecked.
3.Click PDA and choose the recovery you downloaded.
4.Boot your phone into Download Mode. (Power it off and holding down the 1 key on the keyboard, press the Power button.)
5.Connect the device to your PC and once you see it connected in ODIN, hit the Start button to begin the flashing process.
6.Once the recovery is flashed, the phone will reboot
does F.Reset Time checkboxes need to be selected?
or
odin back to OFFICIAL SPH-D700-FC09-8Gb-REL.tar then I need to root it again? lost here never had to go back so just wanted to know from the Pro's...
Thanks m8 =)
lanboy said:
wow that was fast and accurate, many Thank You Zeinzu. I did not know it had CWM on CM9 thinking you had to flash kernels like nyan 5 or shadow cm9 6.3.3 to get it to work.
If by any chance that 3 finger didn't work I would need to use odin to:
via ODIN
1.To begin, download the CWM 5.0.2.7 tar file from the link above.
2.Run ODIN and make sure Re-Partition is unchecked.
3.Click PDA and choose the recovery you downloaded.
4.Boot your phone into Download Mode. (Power it off and holding down the 1 key on the keyboard, press the Power button.)
5.Connect the device to your PC and once you see it connected in ODIN, hit the Start button to begin the flashing process.
6.Once the recovery is flashed, the phone will reboot
does F.Reset Time checkboxes need to be selected?
or
odin back to OFFICIAL SPH-D700-FC09-8Gb-REL.tar then I need to root it again? lost here never had to go back so just wanted to know from the Pro's...
Thanks m8 =)
Click to expand...
Click to collapse
Nooooo!!! Once on mtd (cm9 is mtd) do not flash another recovery.... there Is no flashable or .tar for cwm for mtd roms.. cm9 installed the recovery you should stick with (there is a touch recovery, but its buggy imo)
If you cantget to the recovery you will need the fc09 with victory.pit wth repartition an auto reboot checked...
Cool
flastnoles11 said:
Nooooo!!! Once on mtd (cm9 is mtd) do not flash another recovery.... there Is no flashable or .tar for cwm for mtd roms.. cm9 installed the recovery you should stick with (there is a touch recovery, but its buggy imo)
If you cantget to the recovery you will need the fc09 with victory.pit wth repartition an auto reboot checked...
Click to expand...
Click to collapse
Thank You Flashnoles you also saved me from bricking my phone.
I got confused into thinking I needed to install extra kernals on CM9 to get CMW but I followed Zeinzu advice and was saved. I was just about to odin a CMW.tar when I had my doubts and decided to ask the kind m8's of XDA.
Does CM9 stock kernal have the 3 Button Reboot or you only get that with Nyan Colonel v5 or ShadowKernel CM9 v0.6.3.3 because I try to do a fast reboot but keep getting volume going up or down?
I noticed when I installed the Nyan Colonel v5 it installed TeamWin Recovery Project (twrp) instead of CMW but I reverted back using restore-cwm.zip. Is this the "touch recovery" you were reffering to because I also found it buggy and was not confident using it for Recovery and tools?
So If a new CMW version pops up the only way to get it is to odin back to stock BML to install it then use Restore in CMW to get back to your saved Rom?
Could I use epic4g-fc09-sdcard-utility-v3.tar to temp bypass MTD and install CMW updates?
Thank You again both for your advice and great responses...
Lanboy
=)
lanboy said:
Thank You Flashnoles you also saved me from bricking my phone.
I got confused into thinking I needed to install extra kernals on CM9 to get CMW but I followed Zeinzu advice and was saved. I was just about to odin a CMW.tar when I had my doubts and decided to ask the kind m8's of XDA.
Does CM9 stock kernal have the 3 Button Reboot or you only get that with Nyan Colonel v5 or ShadowKernel CM9 v0.6.3.3 because I try to do a fast reboot but keep getting volume going up or down?
I noticed when I installed the Nyan Colonel v5 it installed TeamWin Recovery Project (twrp) instead of CMW but I reverted back using restore-cwm.zip. Is this the "touch recovery" you were reffering to because I also found it buggy and was not confident using it for Recovery and tools?
So If a new CMW version pops up the only way to get it is to odin back to stock BML to install it then use Restore in CMW to get back to your saved Rom?
Could I use epic4g-fc09-sdcard-utility-v3.tar to temp bypass MTD and install CMW updates?
Thank You again both for your advice and great responses...
Lanboy
=)
Click to expand...
Click to collapse
MTD uses a completely different recovery. The recovery is overwritten whenever you flash a rom or kernel. When thee is a new recovery, you will automatically get it when you update cm9.
Sent from my SPH-D700 using Tapatalk 2
i tried rooting my galaxy s3 and i followed a guide i apparently cant post cause its an outside link, all was going great but i didnt realize that i wasnt supposed to unzip the Team Epic root from recovery folder, so when i tried to install from zip it wasnt a zip it was unzipped. I was thinking i could just put the zip on the internal but now i cant access it i get the feeling this is because of clockwork... so what should i do? i just need to install the zip folder if i could get it on my internal, if i could figure out how to go to stock thatd be good i just need to access it again. Help anyone? i thought it said something about not booting into the rom cause it deletes some files so it wouldnt work, is it safe to just power off? (i removed the battery once, do it again?)
You need to get the Team Epic zip on your internal sdcard. If you can not get there without rebooting that is ok. You will lose the cwm recovery when you boot. At that point you need to download the team epic zip and start over from the beginning. No harm done.
Sent from my SPH-L710 using xda app-developers app
m20120 said:
You need to get the Team Epic zip on your internal sdcard. If you can not get there without rebooting that is ok. You will lose the cwm recovery when you boot. At that point you need to download the team epic zip and start over from the beginning. No harm done.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
so you are absolutely sure if i remove the battery and boot normally to access the internal that i will be fine and it has not deleted files?
sorry im such a complete noob at rooting and stuff
WARNING: Do not boot into Samsung's ROM without first applying our Root .zip. Samsung's OTA updates install /system/etc/install-recovery.sh and /system/recovery-from-boot.p, which cause Samsung's ROM to replace the recovery image you had just flashed with the stock recovery. Our Root .zip removes these files, thus preserving your custom recovery. Follow the directions below to boot directly into CWM recovery.
Ya all that says is you will lose what you just flashed, basically starting you over.
Sent from my SPH-L710 using xda app-developers app
If you flash a custom recovery and do not also flash the Team Epic Root from Recovery ZIP (or something similar) the ROM will detect that you have a non-stock recovery when it boots. The ROM performs a signature check and if the recovery fails the check it will replace it with the stock recovery. That essentially puts you back at square one.
You can then download the Team Epic Root from Recovery file and save the ZIP to your internal sdcard. Then start all over.
- Power off the phone Boot into Download Mode (Vol-Dwn + Home + Power)
- Run ODIN and connect your phone.
- Load the CWM recovery (do not have Odin reboot when complete).
- Disconnect the phone and pull the battery when complete.
- Power up the phone in Recovery (Vol-UP + Home + Power)
- Flash the Team Epic ZIP.
- Reboot.
- Enjoy your rooted phone.
If you fail to flash the Team Epic file before rebooting the rom will not "delete any files". It will simply restore the stock recovery.
Flash this in Odin instead of the custom recovery. It will root you and reboot. You can then get the custom recovery with goo manager or ROM manager.