[Solution inside] UrukDroid, I never have root acces? - Gen8 General

Dear users,
I don't know what I'm doing wrong but I installed UrukDroid 2 times like the installation say. I take already the simpel and the advanced method all go well but It doesn't install UrukDroid config 1.0 and also not superuser. If I install superuser it can not root it.
Can someone help me or tell me maybe what I do wrong?
- I installed SDE
- I downloaded the easy install file and copy the 2 files zImage and initramfs.cpio.gz as new kernel it says to restart the device.
- I go again in the SDE menu and select Boot "Developer edition" and select UrukDroid simple and upload the file "UrukDroid-install.tgz" It install I come in android but I don't see nothing special only the boot screen from UrukDroid but in the apps I don't see superuser, wifimanager, UrukDroid config, ...
Hope somebody can help me out.
Solution: Boot again in Developer mode after the easy install.
Thanks.

snakeboots said:
Dear users,
I don't know what I'm doing wrong but I installed UrukDroid 2 times like the installation say. I take already the simpel and the advanced method all go well but It doesn't install UrukDroid config 1.0 and also not superuser. If I install superuser it can not root it.
Can someone help me or tell me maybe what I do wrong?
- I installed SDE
- I downloaded the easy install file and copy the 2 files zImage and initramfs.cpio.gz as new kernel it says to restart the device.
- I go again in the SDE menu and select Boot "Developer edition" and select UrukDroid simple and upload the file "UrukDroid-install.tgz" It install I come in android but I don't see nothing special only the boot screen from UrukDroid but in the apps I don't see superuser, wifimanager, UrukDroid config, ...
Hope somebody can help me out.
Thanks.
Click to expand...
Click to collapse
It sounds like you forgot to boot into developer edition again. You have to do this every time you reboot to get into Urukdroid.

msticninja said:
It sounds like you forgot to boot into developer edition again. You have to do this every time you reboot to get into Urukdroid.
Click to expand...
Click to collapse
Actually if you shutdown Urukdroid, it writes omething "down", so that you dont have to do it every time just the first time
this even works with the openAOS Boot Menu, so i think uruk writes something into the bootloader, that it should boot the SDE the next time

Lenn said:
Actually if you shutdown Urukdroid, it writes omething "down", so that you dont have to do it every time just the first time
this even works with the openAOS Boot Menu, so i think uruk writes something into the bootloader, that it should boot the SDE the next time
Click to expand...
Click to collapse
I know it used a bootlock on $auron's multi-boot, but I don't think that's right lenn. If you haven't removed the stock Android entry, it's still going to boot stock. Pretty sure....

msticninja said:
I know it used a bootlock on $auron's multi-boot, but I don't think that's right lenn. If you haven't removed the stock Android entry, it's still going to boot stock. Pretty sure....
Click to expand...
Click to collapse
It still going to boot to the Boot Menu
It isnt going to boot urukdroid directly
My first entry is Urukdroid, so i dont have to press the power button
Sorry when i was not clearly enough

Lenn said:
It still going to boot to the Boot Menu
It isnt going to boot urukdroid directly
My first entry is Urukdroid, so i dont have to press the power button
Sorry when i was not clearly enough
Click to expand...
Click to collapse
No problem mate. He doesn't have the multiboot though, and hasn't removed the stock android kernel, so he'll still need to manually boot into developer edition.

msticninja said:
No problem mate. He doesn't have the multiboot though, and hasn't removed the stock android kernel, so he'll still need to manually boot into developer edition.
Click to expand...
Click to collapse
Jep, i know Just want to say as an option

msticninja said:
It sounds like you forgot to boot into developer edition again. You have to do this every time you reboot to get into Urukdroid.
Click to expand...
Click to collapse
Thanks m8, this is the solution.

Related

[Q] Can't boot into Recovery from Rooted SDCard

Using this thread, I've successfully installed CM7 to my uSD card, and everything works great, except that I can't successfully boot into Recovery Mode (CWM 3.2.0.1 installed). Current CM7 is 08082011-NIGHTLY-encore.
I've searched through the linked thread, but can't find a reliable solution to the issue.
No matter which method I use to reboot into Recovery, it tells me the SD card is already formatted, looks for install images, then "Preparing to shutdown" and shuts down.
This makes it rather difficult to update CM7 without completely reinstalling.
I'm now having the same problem...
"CWM 3.2.0.1 installed"
How did you get it installed?
votinh said:
"CWM 3.2.0.1 installed"
How did you get it installed?
Click to expand...
Click to collapse
Per the linked thread, as far as I know.
I don't have my NC with me now so I can't verify but I doubt verygreen implemented the latest CwM into his 1.3 image.
In fact, when using his instructions, we not even think about the CwM. Just burn his image into the uSD and good to go.
As for boot into recovery, there are 2 options
a. Combination of N and power button
b. Boot into Recovery by select the option during reboot.
So far, I have no problem with it.
Okay; thanks for that info. It'll be a pain to reinstall, but sure, I can do that. Would Titanium Backup help with reinstalling apps?
So...installing new builds, just copy to sd card and reboot? How do you get into recovery then?
Thanks again for the knowledge!
After a few rounds of reformat/reinstall, it won't be a pain, but just take time, if you (I, we) continue to use the NC, do expect multiple wipe/reformat/reinstall, let say by year end, when ICS is ready, I'm sure all of us will jump on it , so relax.
As for Tita.Bck, I personally don't use it but majority of members here do use. They will help you.
Assume you have a good CM7 on the uSD, yes, just drag/copy the new build into it (boot) and reboot into Recovery.
"How do you get into recovery then?" I just said in my previous post.
votinh said:
"How do you get into recovery then?" I just said in my previous post.
Click to expand...
Click to collapse
Whoops...missed that. Okies; will not install CWM then. Thanks again!
hello,
I have the same issue as OP. I want to reboot into Nook without removing the SD card. I was able to reboot into recovery once and I chose emmc reboot, but now it just shuts down after recovery boot. The "answer" above doesn't make sense to me. I can boot into recovery, it just shuts down. what am I missing?
Ken
chengka said:
hello,
I have the same issue as OP. I want to reboot into Nook without removing the SD card. I was able to reboot into recovery once and I chose emmc reboot, but now it just shuts down after recovery boot. The "answer" above doesn't make sense to me. I can boot into recovery, it just shuts down. what am I missing?
Ken
Click to expand...
Click to collapse
It will never make sense to you if you don't understand the question and the answer.
If you still need help, let's start from scratch. First thing, do tell us what your current system is, next tell us what problem you have?
chengka said:
I have the same issue as OP.
Click to expand...
Click to collapse
No... you don't.
chengka said:
I want to reboot into Nook without removing the SD card.
Click to expand...
Click to collapse
This is NOT what the OP or the topic states.
chengka said:
I was able to reboot into recovery once and I chose emmc reboot, but now it just shuts down after recovery boot.
Click to expand...
Click to collapse
If you are running from SD... What "recovery" are you booting to and why? If you are booting into the SASD recovery (verygreen's) then this is normal behavior... that mode is only for installing ROM's, gApps, etc.
chengka said:
The "answer" above doesn't make sense to me. I can boot into recovery, it just shuts down. what am I missing?
Click to expand...
Click to collapse
Starting your own thread for one... this is a completely different issue than the OP...
IF you are running from SD and want to boot into a ROM on your eMMC... just hold "n" and power on... you should get a boot menu... select eMMC and Normal boot... then select Boot Now.
Believe it or not, I do have the EXACT same issue as the OP. No doubt I am not as fluent in the terminology as a senior member, but I don't think your tone is called for. Btw, thank you for your answer hidden amongst the vitriol.
Happy Holidays!

CM7 Install Instruction - Step by Step for dummies

Just found an easy to follow video on a how to install CM7 on to your HP Touchpad
http://www.youtube.com/watch?v=997I8k1AIzc
i see the video and i see all step by step, but in the step moboot screen the tablet choose automatically choose the first boot webOS and the table not working the touch, and the scree says touch the android in the screen but the touch not working and i need power off the table for choose the second boot any help for me!!! i need back to moboot screen please help me!
at moboot screen you use the volume rockers to scroll through the menu. If you dont touch them then it boots to android in 5 seconds.
I followed this guide and had zero issues. very well done.
http://www.youtube.com/watch?v=fHoQM3KW1sU&feature=related
4.3 said:
Just found an easy to follow video on a how to install CM7 on to your HP Touchpad
http://www.youtube.com/watch?v=997I8k1AIzc
Click to expand...
Click to collapse
As a self-professed dummy, I can attribute to how easy an install this was.
Been running it for about 2 weeks now.
Joe
(version 3.3 now, woo hoo!)
I read the instructions on another post and watched the video twice before attempting this. Twice I've tried and when I get to typing novacom boot mem:// < ACMEInstaller and hit return nothing happens.
When I tried it the first time and nothing happened I figured I had missed a step or had typed something wrong, but no, when I tried it again and went VERY slowly and made sure I was completing every step the same thing happened. Everything up to this point went just fine.
Any suggestions would be greatly appreciated! Thank you!
thekarens said:
I read the instructions on another post and watched the video twice before attempting this. Twice I've tried and when I get to typing novacom boot mem:// < ACMEInstaller and hit return nothing happens.
When I tried it the first time and nothing happened I figured I had missed a step or had typed something wrong, but no, when I tried it again and went VERY slowly and made sure I was completing every step the same thing happened. Everything up to this point went just fine.
Any suggestions would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Same issue here. I checked under "my computer" and it doesn't see the touchpad at this point, though it did previously. I can't figure it out.
I may try on a different computer at some point.
Please let me know if you figure it out.
Thanks
I installed the sdk and then uninstalled and installed just the drivers. Still no love. What ended up working was a reboot to my computer.
Sent from my SPH-D710 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1308152
this helped me
TKG26 said:
at moboot screen you use the volume rockers to scroll through the menu. If you dont touch them then it boots to android in 5 seconds.
I followed this guide and had zero issues. very well done.
http://www.youtube.com/watch?v=fHoQM3KW1sU&feature=related
Click to expand...
Click to collapse
My Touchpad is working great on the latest XRON ROM, but my moboot seems to have as a primary choice to boot on WebOS if nothing is selected. (when I did ACMEInstaller command on cmd, it only appears to have installed CWM and Moboot, I had to manually install the XRON ROM.) Is there anyway to change preferences as to the preferred OS to boot on?
littleemp said:
Is there anyway to change preferences as to the preferred OS to boot on?
Click to expand...
Click to collapse
If you have Preware installed in webOS, download the application called CyBoot. I modifies the settings for moboot like the default boot option, the "next boot" option (Don't know what this is), and the time delay before automatically booting the selected OS.
I tried on a Windows PC and it would not work. I took it home and tried it on my MBP and it worked flawlessly.
Not to start fanboy war here, but it was a lot easier on my Mac, so if you know someone with a Mac, try it there. I didn't type in a single thing into Terminal. I just cut and paste the command and just dragged and dropped the necessary program and driver into Terminal and hit Enter. Two minutes later, I was at the Android "touch" screen.
I found this version to be the most telling and a NO miss step by step
what if u wanna install the xronified rom instead
Toney Starks said:
what if u wanna install the xronified rom instead
Click to expand...
Click to collapse
If thats the case do everything just the same way but put the xron file instead of the CM7, along with the moboot and cwm files.
Don't forget to rename the Xron file to have 'update-' at the start of the filename.
4.3 said:
Just found an easy to follow video on a how to install CM7 on to your HP Touchpad
http://www.youtube.com/watch?v=997I8k1AIzc
Click to expand...
Click to collapse
I can across that video too since I'm obsessively looking up how to flash CM to my TP that just came in today. I'm that nervous type that has to be fully prepared before rooting/flashing something.....lol
EDIT: The video you posted was actually different from the one I found and I like your findings better
Hey, why doesn't the video on Skype work in this os?
Works fine in webos..
upperkingjr said:
Hey, why doesn't the video on Skype work in this os?
Works fine in webos..
Click to expand...
Click to collapse
It hasn't been ported for the android tp yet.
upperkingjr said:
Hey, why doesn't the video on Skype work in this os?
Works fine in webos..
Click to expand...
Click to collapse
tomween1 said:
It hasn't been ported for the android tp yet.
Click to expand...
Click to collapse
Aww....dang...that was one of the primary reasons the wife let me put CM7 on the TP..I did not realize it did not work yet...
Oh well..it is still more than worth it!
Just installed this using his mac version, very simple.

[Q] Boot Loop on my MT4G

I'm new in this whole smart phones so pls be patient with me
So I have MT4G and i had before the cyanogenmod 7 system but I will shot itself down and i would get the boot loop. so I restored to manufacture settings worked ok i thing but then i tried to restore all the info with ROM Manager and it stuck again. played with it more and somehow got to my older system "Synergy Rom" and restored all the info with Titanium app (that i had as well)now its ok but it shot itself once in a wile. when i try to restart it i have 0% battery when the battery was 75% before. can someone tell me if there is any better system that i can download and what are the steps without erasing any info?
Thank you
Lital Lev said:
I'm new in this whole smart phones so pls be patient with me
So I have MT4G and i had before the cyanogenmod 7 system but I will shot itself down and i would get the boot loop. so I restored to manufacture settings worked ok i thing but then i tried to restore all the info with ROM Manager and it stuck again. played with it more and somehow got to my older system "Synergy Rom" and restored all the info with Titanium app (that i had as well)now its ok but it shot itself once in a wile. when i try to restart it i have 0% battery when the battery was 75% before. can someone tell me if there is any better system that i can download and what are the steps without erasing any info?
Thank you
Click to expand...
Click to collapse
erase/wipe everything.. EVERYTHING
install the virtuous unity ROM
and thats it. start from scratch.. its your best bet
DO NOT restore system data with Titanium. It might easily cause the problems you're describing. And of course, DO NOT restore /data partition from nandroid backup (the one you made using ROM Manager or directly in recovery), when it isn't a part of the ROM you've backed up and restored too.
You can selectively back up and restore SMS/MMS/Call log, and also WiFi/Bluetooth/bookmarks and some more useful settings. But it's hard in Titanium, you need to know which system app contains the info you need. You can search the internet and you'll see (these apps are marked in green in app list). The rest of system settings you should set up from scratch for any system, if you expect it to function trouble-free.
Wipe your phone clean, reinstall a ROM and restore user apps only, to begin with, and see if it stops the issues you're having (which will most likely happen). And if you like Sense, you'll be better off installing Virtuous Unity, as Grimey pointed above me. One ROM with virtually 0 bugs.
If u like Sense 3.0, LeeDroid has 0 bugs as well. Been usin it for weeks...
Sent from my HTC GLACIER using xda premium
Thank you, but could you tell me what are the steps to install me OS?
I cleaned the phone got back to the manufacturer setup but i can't find even the Market app (or google play app) to download the "Virtuous Unity ROM"
Lital Lev said:
I cleaned the phone got back to the manufacturer setup but i can't find even the Market app (or google play app) to download the "Virtuous Unity ROM"
Click to expand...
Click to collapse
you need to get s-off
you need to get root
you need to install a recovery
then you download the virtuous unity ROM from the development section or the virituousrom.com website. put it in your sd card. load recovery and wipe your system and cache and dalvik, then install the ROM..
So my phone is s-off and root i just don't know how to the install recovery if i can't find the market app and i don't know how to download it.
Lital Lev said:
So my phone is s-off and root i just don't know how to the install recovery if i can't find the market app and i don't know how to download it.
Click to expand...
Click to collapse
absolutely nothing to do with the market.
download the recovery image (clockworkmod or 4ext). rename it to recovery.img for easier access. place it in the same folder as adb/fastboot for easier access.
get into your bootloader, then get to fastboot mode, it should say something like "fastboot USB"
connect it to your PC
now in the adb/fastboot folder on your PC, hold shift and right-click then click on "open command window here"
finally, type "fastboot flash recovery recovery.img"
now when its done, you can reboot into the bootloader and get into the recovery, from there you just install the ROM
Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience
Lital Lev said:
Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience
Click to expand...
Click to collapse
if you already have clockwork mod, all you have to do is make sure you phone is off (pull the battery, or turn off hibernate mode)
hold down power + volume down
you will enter the bootloader, give it a few seconds to load
use the volume keys to scroll to recovery and hit power to select
then simply wipe everything and flash the rom
ps. youll need android SDK to get the latest adb and fastboot files
Lital Lev said:
Thank you again, now could you tell me how i get the "adb/fastboot folder " i googled it and found an link to download(not sure if it was the right thing to do)
another thing i have the clockworkmod already on my phone but just in case downloaded the 4ext to my PC and saved it as "recovery.img" now what should i do?
thank you for ur petience
Click to expand...
Click to collapse
Honestly, if I were you, I would go ahead & flash 4ext recovery. It is more stable & from the looks of things, you don't need any more problems than you already have. After you get recovery flashed, or if you choose to use cwm anyway, do this:
1- hold volume down + power you should enter the bootloader.
2- scroll down with the volume button until recovery is hilighted, & press power button to select.
3- You should be in recovery, and if so, choose "wipe data / factory reset" then "wipe cache" then "wipe dalvik"
4- Next, " format system, format data, format boot"
5 Next, choose install from sdcard.. choose zip from sdcard & find the Rom you have on your sdcard. Wait until it installs completely. Then reboot.
6. At this point be very patient and let it load. It could take several minutes...up to 5 or 6
And in a nutshell that is it..
Sent from my HTC Glacier
If I were the op I would leave my phone completely stock and do some more research before proceeding any further. If you break your phone you won't know how to fix it with your current android knowledge.
Sent from my HTC Glacier using xda premium
eqjunkie829 said:
If I were the op I would leave my phone completely stock and do some more research before proceeding any further. If you break your phone you won't know how to fix it with your current android knowledge.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I agree...I made that mistake & Jack_R1 helped me til he got pissed off,(rightfully so), & I realized it only takes a couple of days to read people's situations and you really learn more that way. I started off with an HTCDEV unlocked device, and it took me 2 days to figure out that I bootlooped it by flashing a 2.21 boot.IMG on a 2.34 Rom. I ended up figuring it out w/ jack_r1 helping me. Finally I relocked it and rooted it properly. Now, I can do it from start to finish in about 5 minutes or so...downgrading and all. But its best to read til u understand.
Sent from my HTC Glacier
Thank you all!!!
Would you believe me if i told you that it was a problem with the battery? I changed it to a new one and its all good (so far) i really hope that was the problem. If anything I'll do the steps that you adviced me ))
BUT I still have the problem to log in to the internet except google page and apps. I had it for a long time before but i don't know what causing it, i could log in with firefox thouh, what could be the problem?
thank you all again.
I would. A new battery fixed my co-worker's Desire S, that started crashing all around.

Motorola bravo help

I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
hotshot545 said:
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
Click to expand...
Click to collapse
Unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of CM. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red M" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
If you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
dr. Orange said:
unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of cm. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red m" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
if you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
Click to expand...
Click to collapse
thank u sooo much
hotshot545 said:
thank u sooo much
Click to expand...
Click to collapse
ok i just wanted to know is there a way to charge phone b4 doing this
hotshot545 said:
ok so if i flash it using sbf lite... will it run stock android 2.2 or will it's still run 4.1.1 and also will it still be rooted or will i have to restore root. and btw b4 i do this can i charge my phone in this "boot loop mode"... srry i am not the best at this kind of stuff... so I would greatly appriciate if you assisted me step by step if you could... thx in advance again..
**don't wanna brick my bravo xD
Click to expand...
Click to collapse
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Dr. Orange said:
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Click to expand...
Click to collapse
ok thx sooooo much.. approximatly how long will this take
hotshot545 said:
ok thx sooooo much.. approximatly how long will this take
Click to expand...
Click to collapse
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Dr. Orange said:
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Click to expand...
Click to collapse
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
hotshot545 said:
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
Click to expand...
Click to collapse
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Dr. Orange said:
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Click to expand...
Click to collapse
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
skeevy420 said:
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
Click to expand...
Click to collapse
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
hotshot545 said:
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
Click to expand...
Click to collapse
My fault, its Volume Down, and yes, the green blink before the blue is when you push it.
I got it confused with Stock Recovery, which is Power Button+Volume Up while turning on the phone.

[HOW TO] Root and Install CWM without USB, Odin, or Computer: 2013 Version

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?

Categories

Resources