Related
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Anyone got any ideas?
I even installed fresh, LeeDroid last night and still it wont let me select OK to go in to ROM Manager?
Maybe something on my SD card?
CodeJACK said:
Hi,
I have my DHD root for some time and I followed instructions to retain root when I did the OTA in December. Since then I had many issues with superuser so i found a version that works correctly.
I decided to install and try Rom Manager to update my recovery to the latest.
Rom Manager opens, but at the prompt, it will not allow me to select OK to continue. I can cancel fine, so its not crashed/hung.
Is this the app not requesting root access in the same way as other apps?
Fastboot and busybox all work correctly with superuser.
Any help?
Click to expand...
Click to collapse
You are better off without the latest version of CWM if you have no plans of flashing CM7.
Damn, I just purchased the full Rom Manager in the hope that it would work.
What a waste of 4 Euro.
So I guess I wanted it for the ease of ability to manage ROM's as i use my phone more as a gadget rather than a phone. I like messing with all the great work chefs produce
Ill continue to flash via clockwork recovery and continue to upgrade clockwork recovery with the SDK.
I have a 16Gb Class 10 card on the way so when it arrives, ill do a full wipe and flash with a blank card to see what i get.
Any other suggestions greatly appreciated.
Going to bring this post back up as i was wondering if anyone had anything similar since?
I have gone totally back to stock now and done a fresh root and Eng and radio s-off but still Rom Manager opens but wont let me slect OK to continue.
I think its almost cetainly related to root access as I'm not able to choose allow when apps pop up requesting root. i have to deny them, close the app, then swap them to allow in Superuser and then run them again!
This is a real pain in my ass at the moment.
Is your superuser the latest version?
Yeah, have tried both the one in ChainsDD's thread which I know is very old.
Also tried the patched version that works properly with the later froyo build.
Have tried flashing LeeDroid and Revolution ROM's but still the same problem persists.
I went back to stock today, thinking it might have been a step i missed/screwed up. Still this problem persists.
I'm stumped. Could it be some hardware issue?
Well Damn crap n balls to it anyway!
Turns out after all this time, all I had to do was touch the search button at the bottom right of my HD to bypass the disclaimer of Rom manager.
I feel so dumb now. Still having issue with superuser allow button but I can work around that for now.
Sent from my Desire HD using XDA Premium App
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.
I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Mumonk said:
I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Click to expand...
Click to collapse
only thing i can think of Is Odin the stock rom and start all over with trying to root......
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Mumonk said:
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Click to expand...
Click to collapse
Get towelroot, is an apk that root your phone with one click, after that just download your favorite super user from the market and done.
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
RyeM8 said:
Recently, I have been introduced to Android Rooting and I have successfully rooted my phone with Towelroot. My friend installed Cyanogenmod 11 on his Galaxy S3 the other day and I have been having many problems doing the process myself. I have ripped xdadevelopers to pieces trying to find a solution, but nothing has ever been simple enough, well really efficient enough to fix my problem.
I have ROM Manager installed on my device and the latest CWM Recovery and when I get to the "Recovery" mode it does not give me all the options a normal "Recovery" screen would give me. I can not backup my current stock rom because there is no option. In doing this I accidentally wiped my phone and had no way to recover, so I lost a lot of temporary things, very frustrating.
Basically what I need to know is how to get CWM Recovery to work on my device, etc. Also I forgot to mention before that FreeGee messes up too. It says something about "loki" or something. I am sick of trying several methods that fail in the end. If you can tell me how to get CWM Recovery to work on my phone. I do have an SD Card and my phone is rooted. Please help me! I apologize if all the information is not present, but if you need to know anything specific I would be more than happy to answer your question!
Click to expand...
Click to collapse
Have you tried installing the recovery from G.Pro Recovery first? Freegee will not work for me, giving me similar errors, until I first do that. See the to the Bountyman G3 v4.x thread under 'Optimus G Pro Android Development' for more info. Works for me every time (though I choose TWRP; friggin' *hate* CWM).