Related
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<
I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up
Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.
I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated
Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.
If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on
No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.
Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser
If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.
Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up
The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium
MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
r34l1ty7 said:
This may humor some of you as to the stupidity I have displayed in messing around with rooting\rom'ing my i9505.
Sadly tho it's resulted in me bricking/semi-bricking the phone and I am tearing my hair out trying to fix it.
What I did to get me here:
- Within TWRP (existing recovery/root at the time) I wiped all my data from the internal storage. This in effect meant that I had no roms nor any backups to recover from. Super Doh! *facepalm* moment of the centuary... :S
- For one reason or another the existing rom i was on would not boot. I was effectively stuck in a boot loop on the Samsung Logo
What I have tried doing to fix it (and failed miserably):
- I thought that by at least getting a rom onto the device and flashing it I would be back in business however this proved to be a challenge as the samsung USB drivers do not work with TWRP so I cannot adb push or sideload as I have no rom/backup locally.
- So I rooted with CWM which worked a treat with sideload. So I rom'd the phone...however...the following now happens
- I cannot get into existing/current ROM. Boot loop
- I cannot get into CWM (frozen with blue text in the top left) and have re-downloaded ODIN, CWM several times and tried to flash several times. No joy...
- I can flash with TWRP however as mentioned above the drivers do not work so I cannot sideload.
Any ideas how to fix - very very very much appreciated.
Don't need comments how dumb I have been - I am kicking myself more than you ever will.
Click to expand...
Click to collapse
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
123hiten said:
Can u try flashing Stock firmware using Odin it should work and incase after flashing it does not boot go to stock recovery and wipe cache reboot
Click to expand...
Click to collapse
Just wanted to say a big thanks. Your solution worked a treat. :good:
I take it I can now root as usual? Nothing else needed? ...apart from not trying to be stupid again
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod on a stock Epic 4G (SPH-D700) running Gingerbread FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
IMPORTANT NOTE: Be sure to follow the exact procedure below.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- Backup your stock kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
12/08/2013: (Major Addition) Added important note. Added backing up stock kernel.
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Appreciate the effort and updated info.
Mr_You said:
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod (CWM) on a stock Epic 4G (SPH-D700) running FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- You may backup your kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Click to expand...
Click to collapse
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
TheKillah512 said:
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
Click to expand...
Click to collapse
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Yes, im sorry that i have to make u go through all this trouble because maybe im doing this wrong..
What i was trying to say is that the kernel also has 'su' in /sbin (im not sure if this is the problem but in my galaxy s3 the 'su' is only located in /system/bin and /system/xbin)
I also read this article where it said that the 'su binary' isnt supposed to be in /sbin because in this case (what i think its saying is) that everytime it boots up the /sbin is part of the booting process. Here is the website link: htt p://a ndro idsu.co m (cant post links yet damn)
" People with the su binary located in /sbin have a much tougher time. I’ve found that these are mostly Samsung users (with the notable exception of the Nexus S). I don’t know why it’s done this way, and if anybody does know, please let me know, but for some reason kernel and ROM devs for these devices put su in /sbin. /sbin is part of the boot.img, and therefore any modifications to that directory will be erased on boot."
What i first did is installed Framaroot nd rooted the phone, then got excited because i had been trying to root it for like 2 years now with no success, so since i thought i knew what i was doing, i trailed off nd tried to install CWMR through Rom Manager then went into recovery nd for some weird reason it just put me in the stock android recovery so i knew something went wrong... Then i got scared nd tried to go back to your method nd installed the kernel flasher so i flashed the kernel, rebooted, nd then went into the superuser app. It said the SU binary needed to be updated (got surprised because it didnt say that before i flashed the kernel) i put continue nd it showed me an option to install it through TWRC/CWMR or install normally,so i chose through CWM nd it actually booted me up into CWM but then it said something about a command not working [it was some couple days ago so i cant remember what it said exactly] so i messed around with CWM and tried to installed CyanogenMod which i had downloaded previously, did the signature verification toggle off, but it still said installation aborted because of the command or something... Then i rebooted the phone nd then the problems started, in the superSU app i tried to install normally but it said installation failed... Got the root checker nd said su found in /sbin /system/bin and /system/xbin but i had no root access so i panicked nd tried to root it again with Framaroot, it said success nd i rebboted but it didnt work. I ran the root checker again nd it was the same. I tried to go back to a backup i did when i only had root without the kernel but(which by the way by the end of the backup it said couldnt make md5 sums)but idk why but it took me to the stock android recovery so i couldnt make a restore. I felt trapped cs i couldnt go back to before i had the kernel. With no root access i couldnt also do the restore to the stock kernel(SGS Kernel Flasher app) because i made a backup of it in case something went wrong.. Unfortunately it did so now with no root access i cant really do nothing anymore... I was thinking of using odin to go back to its original state, but then i remembered that it was impossible because odin never recognized my phone while in download mode... Im short in options on what to do please help, im still a noob
Can you try to do a factory reset from the stock recovery and start over?
Mr_You said:
Can you try to do a factory reset from the stock recovery and start over?
Click to expand...
Click to collapse
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
TheKillah512 said:
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
Click to expand...
Click to collapse
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Mr_You said:
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Click to expand...
Click to collapse
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
TheKillah512 said:
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
Click to expand...
Click to collapse
I assume you've already tried uninstalling any SU-type packages?
Mr_You said:
I assume you've already tried uninstalling any SU-type packages?
Click to expand...
Click to collapse
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
TheKillah512 said:
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
Click to expand...
Click to collapse
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Mr_You said:
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Click to expand...
Click to collapse
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
TheKillah512 said:
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
Click to expand...
Click to collapse
Yes that is normal.
I see you say you tried reinstalling Framaroot, but try reinstalling again. But don't reboot. Afterwards go straight into ROM Manager and select "Boot into Recovery" and if rooting was successful I believe it should boot into CleanGBs CWM v3 recovery.
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Click to expand...
Click to collapse
For some reason all the forums posts images are broken for me. It seems to be a 404 error.
Ok lets try this:
Make sure you are rooted (install Framaroot again if you need to, don't reboot) and start SGS Kernel Flasher and flash your backup backed up stock kernel and reboot. Then try following the procedure again from the top as described to try to install CWM. Rebooting your stock kernel may or may not fix these issues. If it doesn't then it may require finding a way to fix it via a Terminal app or other method.
I seem to be rooted in some ways but not in others
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
cdupree said:
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
I would try reinstalling Framaroot (and don't reboot) then: Start ROM Manager->Reboot into Recovery
cdupree said:
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
Thats exactly what is happening to me too, friend...
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
Thats exactly what is happening to me too, friend...
Click to expand...
Click to collapse
Sorry you're mistaken. You just posted a pic of CWM v3. So your "Reboot into Recovery" from ROM Manager worked.
Did you try what I suggested here to fix your errors?
Ok, I'm new at this, here's what I've got, hopefully someone can shed some light:
-My RAZR M is fully encrypted
-It is successfully rooted
-I have installed Rom Manager with CWM 6 as the custom recovery
-I want to make a NANDROID backup (to eventually install Carbon), but whenever I try to reboot into the backup/recovery mode, it won't, it goes to what I think is the ADB screen? Not sure tho, this screen says "Connect data USB." Then, when I do, it just changes state and says USB connected, nothing else happens. Then I just reboot the phone normally and everything still works.
So after googling and researching a lot, I'm assuming since my phone is encrypted it won't access the CWM because it never asks me for my password to decrypt the internal storage. Ok cool, but here's my question now tho; if I perform a Factory Reset from the settings menu, will it actually do the reset and reinstall itself since I have CWM installed??
Thanks for any help.
Anyone got any ideas??
Is your bootloader unlocked?
Sent from my XT907 using xda app-developers app
Hmm. Is this screen where it says "Device is LOCKED" mean that my bootloader is locked? Btw, this is the screen that I referred to in my first post. It comes up whenever I try to select "Recovery"
Your bootloader is locked and on that version it can not be unlocked... So... unfortunately you can not install a custom recovery... Well you can use safestrap but the ROM selection is very limited...
Sent from my XT907 using xda app-developers app
So you say I cannot install a custom recovery, do you mean a different ROM that I would "recover" to install it? Or do you mean ClockworkMod (and its various counterparts)? Because in the ROM Manager app, it says I have CWM 6.0.4.4 as my "current recovery" (see attached screenshot)
Please forgive me if this is a dumb question lol but like I said, I'm new at this whole thing
It does say that huh unsure as to why... i do have a locked M around here somewhere ill see if it does the same thing to it...When I say custom recovery I do refer to cmw n twrp... With a locked bootloader you can not install those... we have for safestrap as a recovery for locked bootloaders it's been a year since I used it but I believe you can make backups on it... I would just sit tight and.wait on kit kat it shouldn't be to much longer... till then just freeze all the bloat and use xpossed to your liking... When kk comes out I'm sure development will pick up for locked bootloaders again..anyone else with more experience care to provide more in depth assistance..
Sent from my XT907 using xda app-developers app
So any further advice on what I can or can't do?
I would like to perform a factory reset on my device to get rid of this stupid encryption (it slows everything down), but with CWM installed (supposedly?), can I still do a factory reset? I guess what I'm trying to get at is what does the factory reset option use to re-flash everything from? The recovery partition where CWM is now supposedly installed? Will that affect the factory reset?
I hope this makes sense, I don't want to brick my phone...
Alrighty, for anyone interested:
I never tried the factory reset. What I did do is try the OTA KitKat update just like 2 hours ago. That was a mistake; upon downloading and automatically rebooting to start the upgrade, my phone would not reboot, it got stuck at the AP Fastboot screen with the error code 0x56 (see attached picture).
So, I powered off and powered on my phone, at which point it powered up normally, until after about 2 minutes on the home screen, it automatically rebooted itself (to presumably "continue" trying to install the OTA). Then it got stuck again on the AP Fastboot screen. This continued over and over and I soon realized I soft bricked my phone.
Did some further research, found the House of Moto program (http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/) which saved my life. If anyone is having any issues similar to the situation I was having, or just issues with the KitKat OTA, this House of Moto program will restore your phone to completely stock. Just follow the instructions on that web page exactly. Kudos to the dude who developed that.
Hi,
I have now rooted my phone and seemed to have removed the issue I was encountering. (IMS Framework)
However I have a few issues since rooting and am a bit unsure if what to do next
Any help to the following points is greatly appreciated. I am complete noob so only plain English and links to idiots guides please!
1) as a recent post states, I am also suffering from frequent restarts. They are quick restarts, only a few seconds (not like a hard reset etc) however there seems to be no specific reason or app causing it.
Posts suggest removing Knox might help?
I have a few root removal apps installed now so can someone tell me which Knox apps/programs can be safely removed???
2) when I press side button to unlock the phone, the screen sometimes freezes and doesn't respond. I have to press lock button again to lock, again to unlock then it works again
Not a major problem but annoying none the less
Any ideas??
3) I rooted to save battery by deleting the vodafone virus IMS framework however battery is still not as it good as it was before IMS framework. It doesn't drain within a few hours but again it's annoying.
Android system and OS are currently using more battery than the screen
So being a noob I'm. It sure where to go from here....
I've done a backup from nandroid manager app (in a cwm format it seems) and downloaded rom manager however CWM installer hasn't worked (something on the install guide says something about Samsung devices needing to install something but I can't find a guide on it)
(Please also confirm, the back up I did to external sd card has a few files including an md5 file, a few tar files and recovery img file. Is this correct? Is this the folder I would use to restore if I encounter issues later on??)
So I'm thinking I unroot and reinstall factory settings through kies etc (guide how to do this would be useful??!!)
Then root again and install a new rom (a nice clean one without the bloatware etc)
EDIT. IVE READ HOW TO INSTALL CWM FROM ODIN SO WILL TRY THAT.
QUESTION THEN BECOMES : WILL INSTALLING A CUSTOM ROM FIX POINTS 1,2 and 3????
Am I overthinking this or is there a quicker fix to my issues above?
Any help appreciated!!
1. If you have a custom recovery then flash knox removal script. Then you don't have to delete it manually. For example > http://forum.xda-developers.com/galaxy-s4/general/scriptknoxout-complete-brutal-knox-t2807172
2. Could be related to point 1.
Flash the script and it should solve most of your problems.
For your last question. There is no point in unrooting and using Kies if you want a custom rom. A custom rom will fix point 1, 2 and 3.
HELP!
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
rootromnoob said:
so i install the Knox Zip (through teamwin)
Phone said "updating apps" then stuck on samsung screen.
Rebooted again.
Done multiple reboots through TWRP. Still same - stuck on samsung screen
I wiped data/factory reset but issue is still same.
I can get to the screen by holding down power volume up and home button but reboot not working.
I looked for restore but it is blank (i did a restore on SD but its not showing!!!)
I need help!
Click to expand...
Click to collapse
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Lennyz1988 said:
Either reflash the stock rom you are on
or
Flash a custom rom that you want.
Click to expand...
Click to collapse
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
rootromnoob said:
Im guessing that has to be via Odin as there is no ROM file on my phone??
(or could i put a ROM on my External SDcard and flash via TWRP?)
Click to expand...
Click to collapse
Stock ROM (download it on your pc) -> Flash it via ODIN
or
Custom ROM having it in your SDCARD -> Install it via TWRP (Custom Recovery)
Took a while messing around with sd card but managed to flash liquid smooth and all working
Annoyingly Odin didn't recognise phone but that's ill sort that out another time
Thanks for help