[Q] How to root stock Rogers 4.0.4 (UXCLF3) without custom recovery. - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks

marclabrosse said:
Hello,
I've upgraded a Skyrocket to ICS via Kies the day it was released (Rogers 4.0.4), wife's phone. Went very well, nice and fast no issues.
So now she can finally use Apex launcher (bye Go Launcher!), but adding certain widgets and others functions via Apex require to be rooted (root helper).
The only way I found to root this stock ICS ROM so far is to install CWM Recovery, via this thread http://forum.xda-developers.com/showthread.php?t=1722506.
I would like to root it without installing a custom recovery. I checked the methods listed here, but seems to be for GB only... I'll keep looking but if anyone knows... It's probably just too early, soon enough methods should pop up.
Thanks
Click to expand...
Click to collapse
no, u need to flash su, gb or ics its still the same process, maybe w/oneclick but i never tried that method
but whats the problem using cwm, its very safe todo and its y we can do so many things with our phones, and if need b u can always flash back to stock ics w/sammobile.com firmware files

afraid to say you'll have to have a cumstom recovery. SuperOneClick wont work. It actuallt will only work on GB 2.3.5. 2.3.6 wont. And I'm pretty certain ICS wont either.

Thanks guys, yeah I tried GB methods or rooting without CWM Recovery before posting, no go...should have rooted before upgrading her phone via Kies...
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store.
I've had mine running CWM recovery from day one, but I can restore it to stock without a problem, she's not technical at all... its her "Facebook" phone...
I guess CWM recovery will be going on there shortly...

marclabrosse said:
I just wanted to keep it as stock as possible for warranty reasons, in case something happens when I'm not around and the device has to be brought in to a Rogers store...I guess CWM recovery will be going on there shortly...
Click to expand...
Click to collapse
You can flash back to 3e recovery without losing root. Unrooting is covered in post #10 here: http://forum.xda-developers.com/showthread.php?t=1726445

Related

[Q] What is the best way to disable system update notifcations?

Ok, here is what I've done and where I am.
I'm using a Nexus S I9020T (original T-Mobile version). In the past I've used cwm custom recovery, flashed custom roms and obviously was rooted. The last flash I did, I upgraded to 4.0.3 stock and all went smooth, but as of right now I'm just not a fan of it.
So now, I've downgraded back to 2.3.6 stock rom. I'm also now sporting stock recovery and am rooted. I know this is a little weird, but I'm wanting the ability to do OTA updates using stock recovery, but also want root access, which is all working well at the moment.
But, I don't want to go back to 4.0.3 as of right now. So, is there an easy way for me to disable the system update notifications and stay on 2.3.6 right now and later on just re-enable them to do the update later.
From what I've read online, my best bet is to probably edit the build.prop file, but I'm not sure what content would need to go in there. I've also seen about freezing files, but I'm already getting 4.0.3 update notifications, so I'm not sure that will work.
Any help is appreciated

2.3.6 Root questions/AOSP 2.3.x?

I have two questions...
1. I had rooted my A2 when it was 2.3.5 and deleted a few apps. When the OTA update to 2.3.6 rolled around, I couldn't update because ATT is a grouch. Anyway, to solve that problem, I had to flash stock 2.3.5 back onto the phone removing root access and everything. I then proceeded to update to 2.3.6 which is fine. that's running stock as I type this. My question is, if I root it again on 2.3.6 (I know it's there...) and I freeze apps, when another OTA update rolls around, will I be able to update again? I don't want to have to flash it back to 2.3.6...(can I even do that yet?) so any help here would be appreciated.
2. I was out and about, and was looking at one of my friend's phones. She has this HTC HD2 running Android 2.3.3 AOSP. She uses ADWLauncher, etc etc. This is a Windows Phone, originally. That got me thinking...is there a AOSP version of Gingerbread for my A2? Without Blur? I'm kinda scared to do anything to it, because I want to be able to get ICS come July. Any tips here would help.
Sorry for not using the searchbar, I was just having trouble finding this info. Thanks guys!
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
SeekerLoki said:
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
Click to expand...
Click to collapse
When a major update such as ICS is released, there will be alternate ways to install such as through bootstrap. Hopefully we'll find a leaked version of ICS before that, and pull the radio get CM9 working
Okay. So I'm planning on rooting it...now...but when I flashed 2.3.5 from the fxz someone provided, it said that once you updated to 2.3.6 you could never go back...but...
I'll try it.
What's bootstrap? I've heard about it and no one has been able to dumb it down for me...could anyone do that?
You can flash the FXZ after the update. It just requires a bit of modification and care. You might want to read the noob thread. It has lots of useful info.
Bootstrap is a way to backup, restore, and flash zips before android boots.
I just rooted the 2.3.6 it's running wonderfully.
Should I install the ibfaber deoxed rom? I mean I know I can do it per instructions but is it worth it?
It depends on what you want to do. If you want to apply any themes you will need to be running the deoxed rom. He also has a supercharged rom that has a lot more customization.

[Q] Planning to root and put a custom rom on a friends phone

Hi there, my friend is coming round soon and I was planning to give it a custom rom
Now, I've done this type of stuff before (on my nexus) I just want to see how you would do it for this samsung phone
Now, what recoveries can you get? I use 4EXT on mine
And, can anybody send me to a stable and up-to-date rom that can be used everyday and has nearly no issues? I need one without all the samsung stuff, just a normal default android one
And, how would I go by rooting the phone?
On mine, I used the zergrush exploit, does it work for this phone??
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
ak700 said:
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
Click to expand...
Click to collapse
Thanks, and how do I go about flashing the rom, would I have to root it first?
No need.
This is something to good to read http://forum.xda-developers.com/showthread.php?t=1372414
BTW to root the phone use super one click root (or sth like that )
Ah, I get it now, thanks
Just one more question, does ODIN delete the phones data before installing the rom?
You have to wipe all your data after flashing(or not if from Froyo to Froyo)
I mean from recovery. ODIN don't delete user data
I exactly I don't know the working of odin, but after flashing you are directly taken to the recovery and advised to wipe data and factory reset.

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium
good flashing
uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

Categories

Resources