Database Info

A small rooting dilema

Hello everyone, I'm completely new to androids and I recently rooted my phone with CF's Auto Root.
I've been scouring the forum for information on how to resolve my problem but none that really help me with my specific problem
I want to re root with clockwork but can't find anything on it
Can someone help me out here? Sorry for sounding really dumb, I just switched over from apple this stuff is a completely different world to me

Completly factory reset your phone n try rooting again . If it fails, you need to root using the same software as you did earlier
Sent from my HTC One S using xda app-developers app

sishirbaid said:
Completly factory reset your phone n try rooting again . If it fails, you need to root using the same software as you did earlier
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So with my original method I've rerooted my phone. How do I install clockwork mod on a rooted phone if it wasn't installed in the rooting process?

Take a look at the "goo manager " app and TWRP instead of CWM.
But CWM also has an easy install app if your phone is supported. Just see if it is or not and go from there either way.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
Take a look at the "goo manager " app and TWRP instead of CWM.
But CWM also has an easy install app if your phone is supported. Just see if it is or not and go from there either way.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for answering Pennycake.
I'm on Rogers Carrier OEM firmware right now and I'd like to flash the international firmware as to rid bloatware to my Note 2.
Which app would you recommend me to backup my rom with?

I've successfully rerooted, I found the problem with my phone. After it had been unrooted it needed to be rebooted in order for some effects to take change. So through the original method of CF-Auto Root, I rerooted my phone. I've installed the standalone ClockWorkMod app but it doesn't seem to make back ups properly. Through the app I hit back up and it shows the time stamp I hit 'ok' and my phone shuts off and starts up in recovery mode only not in ClockWorkMod but Android system recovery <e3> or something along those lines with only options to: reboot, install updates from adb, wipe data, etc.
What am I doing wrong?

Try installing the recovert img using clockworkmod before backups, because its not an app error, it is a user error. Using chainfires root method means no cwm. Using odin or lemme guess, you have a gs3, unified tool kit you get cwm.
Sent from my SGH-T999 using xda app-developers app

What recovery do you have right now? If it's twrp (team win) do that go with clockwork mod. Twrp (goo manager) is by far (in my opinion) the best and user friendly. But it's your call. And you don't have to un root and re root to do it. You just have to flash the new recovery via bootloader and it will work. For rom choices I personally like jedi xpx and jellybam. With jedi xpx you can overclock the sh*t out of your note 2 to 1920 and it's still stable.
I've used many recoveries and twrp is my choice hands down. And yiu make back ups easier. So dont unroot again and re root. Just download the latest twrp and flash through bootloader. but to each their own
Sent from my SGH-I317 using xda app-developers app

iKoolkid said:
Try installing the recovert img using clockworkmod before backups, because its not an app error, it is a user error. Using chainfires root method means no cwm. Using odin or lemme guess, you have a gs3, unified tool kit you get cwm.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm on the Galaxy Note 2 i317m in Canada. Clockworkmod isn't letting me back up, everytime I get the box with the timestamp to create a back up I hit 'ok', my phone reboots into recovery mode and its the stock recovery, so no option to restore. Also when my phone's model isn't listed in the clockworkmod flashing menu within the app. Is my phone not supported? The N7100 is the one listed when it asks you do confirm a phone model.
markbencze said:
What recovery do you have right now? If it's twrp (team win) do that go with clockwork mod. Twrp (goo manager) is by far (in my opinion) the best and user friendly. But it's your call. And you don't have to un root and re root to do it. You just have to flash the new recovery via bootloader and it will work. For rom choices I personally like jedi xpx and jellybam. With jedi xpx you can overclock the sh*t out of your note 2 to 1920 and it's still stable.
I've used many recoveries and twrp is my choice hands down. And yiu make back ups easier. So dont unroot again and re root. Just download the latest twrp and flash through bootloader. but to each their own
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
When I boot into recovery it says is Android System Recovery <3e> and below are listed a few options, reboot, wipe cache, install from adb, etc

Then you dont have twrp installed. And by the sound of it you dont have cwm either
Sent from my SGH-I317 using xda app-developers app
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
What ohone do you have?
Sent from my SGH-I317 using xda app-developers app

[Q] Flashed TWRP 2.3.3.0 now bootlooping...

i downloaded twrp 2.3.3.0 from goo apk it automatically installed. i booted into recovery wiped everything , but sd ofcourse, so to flash back to magiorom, and bootlooped every since. Cant reboot recovery, it flashes twrp then back into bootloop. adb does not recognize my device??? idk why never been a problem b4. any help would be appreciated. im s-off just ruud to 3.18 a couple days ago and touchscreen downgraded

Can you get into bootloader? How did you flash TWRP? Though fastboot or ROM Manager?
Sent from my Evita

If you can get into bootloader maybe you can fastboot flash the recovery again then try to access it
Sent from my HTC One X using Xparent Green Tapatalk 2

yes i can acess bootloader. i tried flashing a different recovery .img with success but now adb doesnt see my device. i initially installed through goo manager it was automatic i didnt know it would

traesnaidensdad said:
yes i can acess bootloader. i tried flashing a different recovery .img with success but now adb doesnt see my device. i initially installed through goo manager it was automatic i didnt know it would
Click to expand...
Click to collapse
Use twrp 2.3.3.1 all later versions have issues
Sent from my HTC One XL using xda premium

Ahh yeah goo manager what was I meant. So you've manually flashed a recovery now, does it boot into the recovery ok?
Sent from my Evita

So you can get into twrp now that's a start lol do you have a Rom to flash
Sent from my HTC One X using Xparent Green Tapatalk 2

I have fastboot flashed twrp 2.2.2.0, but it still won't go fully into recovery. The twrp screen comes on then goes black and back to bootloop
Sent from my Nexus 7 using XDA Premium HD app

traesnaidensdad said:
I have fastboot flashed twrp 2.2.2.0, but it still won't go fully into recovery. The twrp screen comes on then goes black and back to bootloop
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Fastboot erase cache....
Sent from my HTC One XL using xda premium

OK....trying now
Sent from my Nexus 7 using XDA Premium HD app

I was able to fast boot erase cache' but adb again can't see my device. Trying recovery manually
Sent from my Nexus 7 using XDA Premium HD app

I don't understand what you mean. Why are you trying to use adb?
Sent from my Evita

Woot! That worked! I'm still learning all about adb. I don't know ALL COMMANDS and why it would not recognize my device after each command that worked. Many thanks guys..many thanks
Sent from my Nexus 7 using XDA Premium HD app

timmaaa said:
I don't understand what you mean. Why are you trying to use adb?
Sent from my Evita
Click to expand...
Click to collapse
Because I could not access anything manually
Sent from my Nexus 7 using XDA Premium HD app

Fastboot was working because you were in bootloader. Adb requires you to be booted into a ROM with usb debugging turned on.
Sent from my Evita

Fastboot error

I get an error when I try to fastboot flash system system.img. It doesn't appear to write the system.img to the phone. It downloads but doesn't seem to write and I get an error that says sp space is not enough.
I have a dev edition unlocked and was trying to return to stock anticipating the update.

Which fastboot are you using ?
Sent from my XT1058 using XDA Premium 4 mobile app

planktoid said:
Which fastboot are you using ?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
moto fastboot. I am using the same computer/sdk/fastboot that I was using just a couple of days ago when I wasn't getting the error. FWIW it doesn't seem to actually affect anything. I just flashed twrp, formatted system, booted back to the bootloader and flashed the system and got the same error but the phone boots fine so it must be writing the system image. I am still perplexed as to what the error is. I had never seen it before until last night.

If you're not rooted and you are stock...how do you go about doing this?
Sent from my XT1080 using Tapatalk

justpastfinish said:
If you're not rooted and you are stock...how do you go about doing this?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Exact same way as all versions of the phone..... Follow the guide I posted in Dev Section, it gives detailed step by step.

How to Know before flashing custom recovery

Hello I have a chinese opo with cm11s installed.Whenever I run bootloader unlock it says time taken 0.00 sec
okay.Now Im not sure maybe the seller has unlocked the boot loader. Is there a way to know before flashing custom recovery?Thanks.Will flashing custom recovery on locked bootloader will brick my device?
Sent from my One using XDA Premium 4 mobile app

No it will not brick your phone. If your phone's bootloader is locked, it will simply not let you flash a custom recovery. If its unlocked, then it'll flash the custom recovery.
Ensure that update CM recovery in developer options is disabled (to enable the menu, tap build # 10 times in about phone and then go back into developer options)

Thanks it worked,I was right it was already unlocked
Sent from my One using XDA Premium 4 mobile app

Now can I update system officially with twrp.I have unchecked update cm recovery.I saw someone said that the update bricked his phone with twrp installed
Here
http://forum.xda-developers.com/showthread.php?t=2825514
Sent from my One using XDA Premium 4 mobile app

should i update?
Sent from my One using XDA Premium 4 mobile app

that guy used cwm... it seems that that recovery caused his brick.
i think you should use twrp or philz one...

Root 5.0.1?

Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.

jss2 said:
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.
Click to expand...
Click to collapse
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.

jss2 said:
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
Click to expand...
Click to collapse
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes, and the way to "manually re-root" is to flash the ZIP in a custom recovery. You the app installed, but not the SU binary. So flash it in TWRP.

dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CF Auto Root and flashing the superSU2.40.zip in recovery both root android 5(0.1/0.2). Did it myself and confirming root access.

You can root with the same chainfires files for 5.0, and then you can update supersu and twrp

dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.

JayR_L said:
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
Click to expand...
Click to collapse
Crazy. Done it to me a few times. I even decided not to help him ever again some time ago, then took pity on him yesterday or the day before and the he did it AGAIN!
He's just a school kid, but you'd hope he would learn from his attitude, but apparently not.
What's worse, is he isn't even picking up the knowledge that people give him or reading the stickies. He's been Here pretty much a year in the n5 forum and cannot even be bothered to.understand the basics. Asks the most basic questions every time.