Related
To preface, I've been off the phone hacking/ROM flashing scene for a couple years now; previously working with Windows Mobile, so I know a lot has changed but I'm not largely unfamiliar with the general process of what we are doing here.
Droid 2 In Question:
System Version - Version.2.3.20.A955.Verizon.en.US (After OTA Update 03 NOV 10)
Baseband - BP_C_01.09.07P
I've got a stubborn Droid 2 that just WON'T boot to recovery. I bought a fresh Droid 2 last week, rooted via the 1-2-3 'One-Click' successfully. Then I attempted to follow AngDroid's Fission install step by step for my first ROM flash. http://forum.xda-developers.com/showthread.php?t=823473
Issues:
ROM Manager wouldn't do ANYTHING when I would select 'Reboot into Recovery' or attempting to select ROM using 'Install ROM from SD Card'.
Found and installed Koush's Bootstrapper, got 'SUCCESS!' pop-up when selected 'Bootstrap Recovery' yet when I tapped 'Reboot Recovery' nothing happened.
I then attempted to re-install the SBF (which I'm still not 100% clear on what the role of the SBF is, perhaps just the Baseband?) using both AngDroid's instructions in his Fission thread as well as using RSD Lite 4.7+patch AND 4.8 AND 4.9 instructions from this thread. http://forum.xda-developers.com/showthread.php?t=827624 All those attempts where unsuccessful. RSD wouldn't allow me to 'Start' the SBF flash which I can only assume is because I had the latest version on my Droid 2.
I then decided to restore my phone to factory and start over, so I booted the device pressing x, then search and selecting wipe data/factory reset. Once done, it rebooted and to my surprise it still had the Superuser Permissions app that was installed during the 1-2-3 One-Click process.
I went as far as to install the full Android SDK/Eclipse setup for ADB use and continued to run into 'operation not authorized', 'root not allowed on production ROMs' and 'failure' with any command attempting to remove SU Permissions app and install a diff. SU app/reboot into recovery.
I checked to see if I still, in fact, had SU permissions by re-installing Barnacle, it stated that it needed su but the Superuser Permissions app never prompt me to authorize su. There is also no way (that I see) to manually authorize su for barnacle, or any app, in the SU Permissions app.
Way Forward?
I believe that I either need to re-root and try to reboot to recovery again but I am not confident that will work.
I am starting to think that ROM Manager and Droid 2 Bootstrapper apps didn't have SU and might be why they didn't respond when I selected 'Reboot Recovery' options? As I stated I do not know how to manually authorize.
With this information, what am I to do from here?
That's strange. After root, you should be able to install SU from the market if the one click root doesn't already do it for you. When you run Koush's bootstrapper, the first time you should get a pop up from the SU program asking you if you want to allow or deny the bootstrapper. After that, everytime you load up the bootstrapper you should see a little pop up stating that it has been granted superuser privileges.
Try rooting again, this time use the 1 click root for 2.3.20 found here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html, and then go through the steps again and report back
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
wjones said:
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
Click to expand...
Click to collapse
Id wipe cache and wipe data/factory reset and start fresh. I've never had any of your problems and I think they can be fixxed with a factory reset.
Sounds like you didn't get rooted properly.
If it were me, I'd sbf and start over.
- Charge battery fully
- Get drivers from Motorola and install them (wait for it to finish)
- Get RSD 4.8+, and 2.3.20 sbf (make sure you get the full file)
- Wipe data and cache in stock recovery (access by power + X key, then search key)
- Boot into bootloader (power + Up key)
- Load RSD and make sure your device shows
- Choose the sbf and click Start
If you follow those steps exactly and sbf doesn't work, then you probably have a hardware problem either on your phone, your PC, or the USB cable.
karnovaran said:
Sounds like you didn't get rooted properly.
- Boot into bootloader (power + Up key)
Click to expand...
Click to collapse
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
wjones said:
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
Click to expand...
Click to collapse
Yeah I don't know why some methods recommend PC Mode. Sbfs are meant to be flashed in bootloader.
Honestly, it sounds like everything is working like it should be, it's just some steps are being skipped or overlooked. Like the SBF in bootloader, and the sbf doesn't erase your data, you need to do a factory reset after sbfing so thats why your superuser app was still there.
There really is no such thing as a phone being stubborn, and majority of errors like that are from the user. Not to be insulting but thats just the case. The only time I have ever seen a stubborn piece of hardware is from overclocking, where some can go higher than others due to having a better piece of wafer. But if you rooted correctly, bootstrapped, etc, there is no reason that you wouldn't be able to install a ROM.
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
wjones said:
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is this solved now? May I close it?
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
wjones said:
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No problem! I'm in no rush to close it, was just curious Hope it all goes well
DONE!
It worked like a charm! Thanks for all the support!
wjones said:
It worked like a charm! Thanks for all the support!
Click to expand...
Click to collapse
Awesome. Could you add [SOLVED] to your thread title before the mods close it?
So I've been running MIUI 1.8.whatever for a few weeks and finally realized there hadn't been an update in a while. After discovering MIUI move into the 1.9.Xs I downloaded 1.9.16 and proceeded to update via CWM. While updating it told me 1.9.16 runs off the Gingerbread kernel. At that point I got worried since I had been running the Froyo kernel since I rooted my DX.
After the update I told it to reboot and now it gets stuck at the white M logo. I can boot into regular recovery but I CANNOT get my phone to boot into CWM recovery so I can run the backup!
I've tried every button combination with no luck. i've booted into regular recovery and selected reboot having read that it will boot back into CWM recovery. Needless to say that didn't work either. And lastly I tried running RSDLite to SBF the phone to .602 but since the phone can't fully boot up RSDLite doesn't see the phone.
That is where I am at and I seek the help and guidance of you much smarter folks to help me get my phone at minimum to CWM recovery.
PLEASE HELP!!!
Boot the phone into bootloader mode, then SBF.
Sent from my DROIDX using XDA App
I got it into bootloader mode now, but my computer isn't finding the OMAP drivers and the installation keeps failing. How can I get these drivers onto my computer? RSD isn't seeing the phone even in bootloader so these drivers seem to be the key.
You can find the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
I got RSDLite to see the phone. Now when I try to flash it, it makes it all the way to checking the checksums (which all pass) then tries to switch the phone to BP passthrough. It keeps failing to switch the phone to BP passthrough and now my phone will only boot to the Bootloader screen and says Code Corrupt. It'll let me run the flash again but RSDLite keeps failing at that BP passthrough switch.
Thats where i'm at now.
Try a different SBF file. I had problems like this when i tried to SBF once, but once I found the SBF file that works for me, its always worked since. (I've had to SBF like 6 times now haha)
will find an older sbf file and try that. Wil let you know.
Alright we've made progress! I was able to finally get the phone SBF'd to .602. Then I rocked the Pete's Droid Rooting program and all seemed to have gone smoothly... Except I cannot boot into CWM recovery at all! I've ensured ROM Manager has the correct flash for CWM installed, but when I click Reboot into CWM Recovery, it'll reboot normally. So I turned the phone off and held the Home + Power button to boot into regular recovery. I get the ! logo with the green android, but when I hit hte Search button nothing happens.
So now I'm rooted, but can't get to CWM Recovery to install ROMS.
What do you guys think?
Yeah, Reboot into Recovery from ROM Manager doesn't work for me usually either...in fact, I had to go into the Bootstrapper app, install the recovery again, and then hit Reboot Recovery. This is on Apex though, but can't hurt to try it.
Yea I finally got it figured out. Its been so long since I originally rooted my phone I forgot all about D2Bootstrapper. And I didn't read the how-to guide for updating to MIUI 1.9.16 so that was all on me.
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
I would recommend reading the Droid X wiki at the Cyanogenmod website. I had some of the same issues until I followed the downgrade + root method and then installed ROM Manager and CM7 manually through recovery. Good luck!
Sent from my DROIDX using XDA App
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Don't use ROM manager and don't use dxbootstrap (unless you have usb debugging unchecked). I use d2 bootstrap always. And you will have the occasion of it going in to cwm when you boot phone back up. I dealt with it for while. And cwm should be 2502 or something like that when you're just rooted 605. Did you make a nandroid of your rooted 605 before you tried to flash liberty
? Hopefully you did. Go back to that. Then use d2 bootstrap to get in to recovery, wipe data, cache and dalvik, then select install ip from sd card, then choose zip, then scroll via volume down to the liberty file, select that and flash.
I used directions posted over at Androidforums.com under the All Things Root forum for the Dx. I had a couple of hiccups, but it was user error. I now have Liberty 3 running smoothly on my Dx. Check it out, including the guide and ROM lists.
HTH
chaz_
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Just re-flash ur phone dude. do you know how to do that? It's a pain in the butt. but it is always failsafe.
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
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?