Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
You could e-mail the editor of the mag and complain
Sent from my GT-I9100 using xda premium
ultimatebestusername said:
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
Click to expand...
Click to collapse
I suggest you restart from scratch following these steps:
1. read everything about flashing and rooting you can find on this site (read stickies first)
2. same as 1.
3. same as 1.
4. flash the latest stock firmware for your phone
5. root your phone
6. finally flash some other ROM
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM...
Performs a wipe date , factory reset , then follow the guide;
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Simple way to root and unroot stock kernel without flashing insecure kernel.
Don't worry about custom counter and yellow triangle, with this method they never appear, because we only rooting, it's a rooting script not a custom kernel.
This rooting script included Busybox installer.
Rooting
Download this File first and put in your SDCARD
- CWM via stock recovery ;( http://dl.dropbox.com/u/34053267/CWM.zip) , or download zip from http://clockworkmod.com/rommanager
- SU-Busybox-Installer.zip ( https://dl.dropbox.com/u/34053267/SU-Busybox-Installer.zip )
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard or external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
Quote:
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
Related
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
hozza94 said:
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
Click to expand...
Click to collapse
did you root your phone?
what rom are you actually using?
did you try to update Rom Manager to an earlier version?
I assume your phone is rooted already. Don't continue if it's not.
I thought there was an official one released for the phone. Are you using the newest version of ROM Manager?
If yes, and our phone model is still not listed, then you'll need to install Clockworkmod Recovery by following this thread:
http://forum.xda-developers.com/showthread.php?t=1151396
It involves downloading a program called ODIN. You need to flash (transfer) the Clockworkmod file to your phone through USB. It's all in the thread above.
I had the same problem - installing the latest Rom Manager (free version) from the store didn't have Galaxy5 listed as a ClockworkMod possibility.
I flashed the whole thing by hand with ODIN and installed CyanogenMod - and presto; the version supplied with it had Galaxy5 support and I had no problem doing the "read only partition" installation.
Rom Manager is pretty crappy anyway - I prefer manual installation over it...
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Rigardi said:
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Click to expand...
Click to collapse
Why did you say that??? If the phone is rooted you can download CWM by RomManager without fear.. the important is that when the popup with phones versions come up, you choose only - ONLY! - Galaxy 5 voice! If this voice is not present into the popup, don't choose nothing at all! Choosing another phone might brick yours!
I downloaded and installed and even only update CWM by RomManager a lot of times and everything was always fine! No problem at all!!
You cannot scare people for nothing: your problems are not bug or issues, but only YOUR problems! and YOUR errors!!!
So, boyz, don't worry installing CWM by RomManager.. but remember to choose only Galaxy 5 voice, no other phone, 'cause you could brick your phone selecting a CWM that is not compatible with our GT-I5500..
Hello,
I recently made some mistakes with my Galaxy S2 GT-i9100 while following this a tutorial on Galaxys2root.com (Can't link to the precise article because this is my first post) I flashed the CWM recovery tool linked by this website to my device through the latest version of Odin and afterwards my phone would not turn on. I was able to get into the Clockwork recovery mode however but couldnt install anything because I had forgotten to place any ROMS on my device beforehand. To try and resolve the problem I did a factory reset in the recovery mode but this did not effect anything. I am now unsure what to do next. I would still like to root my phone so that I cant get rid of all the bloatware put on it by Orange mobile as well as update my phone to Kitkat(Currently running Android 2.2) Can someone tell me what I have done wrong and what is the next step for me to take?
Thank you for any help that you can offer
the kernel you flashed it is the problem
ZK1990 said:
Hello,
I recently made some mistakes with my Galaxy S2 GT-i9100 while following this a tutorial on Galaxys2root.com (Can't link to the precise article because this is my first post) I flashed the CWM recovery tool linked by this website to my device through the latest version of Odin and afterwards my phone would not turn on. I was able to get into the Clockwork recovery mode however but couldnt install anything because I had forgotten to place any ROMS on my device beforehand. To try and resolve the problem I did a factory reset in the recovery mode but this did not effect anything. I am now unsure what to do next. I would still like to root my phone so that I cant get rid of all the bloatware put on it by Orange mobile as well as update my phone to Kitkat(Currently running Android 2.2) Can someone tell me what I have done wrong and what is the next step for me to take?
Thank you for any help that you can offer
Click to expand...
Click to collapse
is this site you are talking about:
http://galaxys2root.com/cwmtwrp-recovery
im guessing that is the problem(Installing CWM/TWRP recovery will most likely break the ROM you are running currently as it overwrites the ROM’s KERNEL).
If iam right,that means you have to flash another kernel,i suggest Siyah kernel 2.6.14 its for gingerbread version(it has CWM recovery and auto-root):
http://forum.xda-developers.com/showthread.php?t=1263838
after that you can flash the KK rom you want through CWM .
Hello,
I've read random threads for the entire day but I'm a bit confused about how to proceed.
cm wiki requires the phone to have stock ICS
I remember something about the baseband, using russian Windows tools to update
I don't have Windows
I'm running osx 10.9.4.
What should I do? I'm also afraid of the superbrick bug.
What I've done:
got root with zergRush
tried to install CWM through ROM Manager, got custom recovery 2.5.1.2 (useless? very old?) but can't boot into recovery, first error was something about signature, when rebooting with volume up+home+power I get "can't access to system/csc/hui/system" instead
I tried then updating stock fw with kies for osx; i was stuck in "connecting" forever
tried installing kies in a windows vm; it couldn't even see the phone and failed to recognize it as a media device
What I know:
I can probably obtain a temporary cwm 6.* (supposed to be not affected by superbrick bug) by loading a zip through stock recovery mode
What I would like:
finally get KK
avoid windows
avoid heimdall; i have bad experience and could never compile it, months ago
avoid yellow triangle
BUT
If heimdall is now a working software and It solves everything (baseband included) by running a one line command, it is a welcomed solution.
Thank you!
p.s. hope I'm in the right forum section
You have really old recovery.
If you want to get newest recovery and avoid windows and have root as you said use Mobile Odin pro to flash the newest CWM (6.0.4.5 I think) and afhter that flash CM via new recovery
I don't know why ROM manager installed something so old.
I thought about Mobile Odin. Does it fix the baseband problem?
ROM managers etc. is balast which made a lot of problems. Don´t be lazy and flash manully
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.