Related
Hello everybody!
I've been messing around, customizing my new SG S II using launchers, icons etc. But I kinda want to take it to the next level and rooting, going for the MiUi rom (http://en.miui.com/).
I have never rooted any android devices before, only playing with jailbroken iPhones. So I know some people on this forum is going to cut me into pieces now, but I really hope someone out there can help me.
I've searching around, unable to find a "simple" guide that can help me. Anyone got a guide out there? Or can help me out, starting from scratch?
Cheers!
First thing I would say is that you have a much better chance of getting a constructive answer if you've shown you've made an effort by providing as much useful information as possible and show you've done the basic research.
If you want to get root for your phone, the first obvious question is what OS are you currently running ?
sdunne said:
First thing I would say is that you have a much better chance of getting a constructive answer if you've shown you've made an effort by providing as much useful information as possible and show you've done the basic research.
If you want to get root for your phone, the first obvious question is what OS are you currently running ?
Click to expand...
Click to collapse
Well, considering the guy hardly knows how to root his phone, I would hazard a guess that he would still be on Gingerbread. And your being pretty harsh on him, still trying to follow the video we all are forced to watch before we join XDA?
Now Westerhoff, could you please provide your Phone, PDA and CSC by going to your phone dialler and typing in *#1234#. These are needed for Chainfire's CF-Root, which keeps the phone as close to stock as possible, whilst rooting the phone, and adding busybox and ClockworkMod Recovery, which is a life saver for making back ups of your current ROM incase something goes wrong, and to flash a new ROM to your phone, for example, the new Ice Cream Sandwich leaks.
Chris.
#sdunne Sorry for that, but I didn't knew if any information was needed and which ones.
#themadba Thanks, Chris! The Chainfire sounds good, keeping it as close to stock as possible.
Phone: I9100XXLPQ
PDA: I9100XXLPQ
CSC: I9100XXLPD
Just to point out... I am running ICS on my phone.
Westerhoff said:
#sdunne Sorry for that, but I didn't knew if any information was needed and which ones.
#themadba Thanks, Chris! The Chainfire sounds good, keeping it as close to stock as possible.
Phone: I9100XXLPQ
PDA: I9100XXLPQ
CSC: I9100XXLPD
Just to point out... I am running ICS on my phone.
Click to expand...
Click to collapse
get this file : http://download.chainfire.eu/152/CF-Root/SGS2/CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.zip
unzip to get .TAR file, put it in PDA section of the ODIN and flash,
Hope you have already installed drivers, if you have installed KIES then its enough, but make sure not running while using ODIN, check it in your PC system tray...
if you are new using ODIN you can get hints here : http://forum.xda-developers.com/showpost.php?p=13712988&postcount=1
only to select TAR file on PDA
Yes, Zaheedahmed is correct. I'm just curious, how does your phone have ICS on it if you don't really know how to root your phone?
Anyway, you need Odin, which is a flashing tool specifically designed for the SGS2: Just type in "Odin 1.85" without quotations into google and the first result should display "Odin - xdadevelopers - XDA Developers." Click on the link and Odin will download.
Now before going ahead with Odin, download Kies: http://www.samsung.com/us/kies/, which is like iTunes for Samsung Devices, the drivers are needed for Odin, but when the drivers have been installed, right click on your toolbar at the bottom of your desktop, I'll assume your running Windows 7, and going to Task Manager. Now find anything with Kies running in the Task Manager, right click on them and kill them.
Kies gets jealous of Odin for being better so it messes up Odin during the flashing process. So make sure you have the drivers installed from Kies and then killed off the Kies Processes.
Finally, lets get the flashing package required to root your phone. Here is the link to Chainfire's LPQ CF-Root: http://download.chainfire.eu/152/CF-Root/SGS2/CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.zip Also make sure you unzip the file to get your .tar file, Odin won't work with .zip files.
Now go ahead and put your phone into download mode. To do this, turn off your phone normally, wait till it is fully off, then hold down the power, home and down volume button until a warning screen is displayed. Then press the up volume button. If the screen says "In download mode. Do not turn off target" then you have got it!
Now fire up Odin when you have installed it, the Kies Air drivers and killed Kies processes off in Task Manager. Now connect your phone to your computer via your micro usb cable. The ID:COM box should go yellow and say ADDED!! in the box at the left hand side. Now make sure that the only options ticked in Option is Auto Reboot and F. Reset Time AND NOT RE-PARTITION. Now click on the PDA button on the right, and this will open your Explorer window up. Find your XXLPQ CF-Root file, and click ok. Then just click Start. In the top left hand corner, one of the boxes will flash blue (I think so) and then Green. The bottom left hand box will say PASSED!! Your phone will automatically reboot.
When it has, go to your app drawer, and check you have something called either "SuperUser" or "SuperSU." If you do, congratulations your rooted. Another way to check it has been successful is to shut down your phone, and hold the home, power and volume up button. If you get into ClockworkMod Recovery, your great!
Post back with any problems (hopefully not), or your success
Chris.
Thanks both. I'm on a business trip right now and I'm back again friday, I will be posting back with the result there.
To the ICS question, I'm from Denmark (EU), we already got the ICS update here ;-)
Sent from my GT-I9100 using XDA
Westerhoff said:
Thanks both. I'm on a business trip right now and I'm back again friday, I will be posting back with the result there.
To the ICS question, I'm from Denmark (EU), we already got the ICS update here ;-)
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
That's fine, just make sure to post back here with your progress as I want to know how you got on. Enjoy your business trip!
Chris.
Okay, so I'm back from my little trip, and I've just rooted my phone. Succesfully!
I must say it was great guide that helped me out all the way and I didn't find my self "scared" or in doubt of how it would all turn out, through out the process. Thanks a lot!
Now, I got some more questions..
I want to go the the MiUi rom? How do I do that?
Also, if i ever want to return my mobile back to normale, without Root, what to do?
Thanks again you two ;-)
Westerhoff said:
Okay, so I'm back from my little trip, and I've just rooted my phone. Succesfully!
I must say it was great guide that helped me out all the way and I didn't find my self "scared" or in doubt of how it would all turn out, through out the process. Thanks a lot!
Now, I got some more questions..
I want to go the the MiUi rom? How do I do that?
Also, if i ever want to return my mobile back to normale, without Root, what to do?
Thanks again you two ;-)
Click to expand...
Click to collapse
There are a few MIUI roms. There is the original, some other ones in the development section. Which every rom you decide to get, download it, put it into your sd card, boot into cwm, backup everything (nandroid backup), wipe everything and flash the rom. Usually every thread has some instructions in it, so just make sure to read it.
You can just use Odin to flash the stock rom to get it back to normal.
Now thats easy.
You go to this site and you shoul download this file miuiandroid_SGS2-2.4.6.zip
Then you put this file in you internal SD card of your phone.
Then you go to Recovery, you make a Backup of your old rom.
Then you go to wipe data and you pick yes.
Then do to instal from SD card and you choose install from internal sd card, then you chose the file you just transfered to you sd card ando choose it. Let to process finish, choose reboot and wait a little longer for phone to start and there you go.
Any questions just put in here!
Greatings from portugal!
Okay, so I've done it all and my SG SII is now running MiUi. Thanks alot.
However, most of the apps keeps "crashing" - They stopped working.. Is the ROM really that unstable?
Did you restore apps and/or data rather than clean install them ?
Yea. I have no other apps, than the ones coming with the MiUi rom.
Westerhoff said:
Yea. I have no other apps, than the ones coming with the MiUi rom.
Click to expand...
Click to collapse
And you did wipe data, dalvik and cache when you flashed the rom?
Just restored from my back-up before flashing, and wiped everything, data, dalvik and cache... Stil ain't working...
Could anyone tell me how to remove rooting from my phone, if I don't find a solution.
Flash a stock rom in Odin.
Westerhoff said:
Just restored from my back-up before flashing, and wiped everything, data, dalvik and cache... Stil ain't working...
Could anyone tell me how to remove rooting from my phone, if I don't find a solution.
Click to expand...
Click to collapse
Flashing a stock rom removes root .
jje
Cheers thanks!
I was thinking that the rom tcunha87 posted, might be damaged... On the official MiUi community i can't seem to find the ROM for SG SII..
NEVERMIND!!! Just found out they are currently only running GB for the SG SII.
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
weati said:
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
Click to expand...
Click to collapse
Are you following the instructions as stated in the op?
Sent from my SGH-I777 running AOKP
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
No
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Phalanx7621 said:
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
Click to expand...
Click to collapse
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
And because this phone isn't other phones, you can't use rom manager with it. It's a nono. And there is a sticky about it. And many threads. And posts. Warning about it.
thanks
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Butchr said:
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
Click to expand...
Click to collapse
weati said:
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Click to expand...
Click to collapse
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
mattdm said:
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
Click to expand...
Click to collapse
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
1. Kies generally only works with stock unrooted phones. Use Odin instead.
2. The phone has no "inability to take a new rom" if you do it the right way.
3. Apparently you don't know pretty well what you're doing.
4. The i9100 works exactly the same way as the i777, and if you try to use Rom Manager on it, you'll end up with the same result: a phone that won't boot.
5. AT&T will unlock an i777 for you if you ask them.
6. Just read the damn stickies, particularly this one and this one.
This thread is full of win.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
You resolved the problem by buying the unbranded version of the exact same phone?
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
So u paid 70 dollars to unlock a phone. Great hope it was worth it. Because like others have said they are identical.
Sent from my SGH-I777 running AOKP
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.