Develop Bugs

rooting with CWM?

Hello,
i have a question. Can you rood the galaxy gio after installing CWM recovery? If so, how do u do that?
I taught my phone was rooted and installed cwm recovery. But now it turned out that my something went wrong in rooting and cwm is allready installed.
Can i still root my phone without installing stock rom again?
I tried to go to update from sd card in the cwm recovery, but i can not choose any file.
I can only choose between no and yes install update. If i pick install update he installs something, but it is not the root file..

djemz said:
Hello,
i have a question. Can you rood the galaxy gio after installing CWM recovery? If so, how do u do that?
I taught my phone was rooted and installed cwm recovery. But now it turned out that my something went wrong in rooting and cwm is allready installed.
Can i still root my phone without installing stock rom again?
I tried to go to update from sd card in the cwm recovery, but i can not choose any file.
I can only choose between no and yes install update. If i pick install update he installs something, but it is not the root file..
Click to expand...
Click to collapse
Hi,
You can try this, only for Gingerbread:
http://forum.xda-developers.com/showthread.php?t=1111414
Use update.zip in the recovery mode.

[SM-T210] Problem on root / OS install

Hi,
i have run into a little problem,
After CWM install and then rooting (suing method/files from sticky) following happens
1. System started once
2. All colors were replaced with electronic green (if you know what i mean)
3. System doesn't restart anymore
4. System restarts always and only to CWM
5. On each exit from CWM, User is asked to flash ROOT
6. On each and other system flash, device reboots to CWM only,
any help?
ps. i tried to reflash CWM, root and system all with same effect
regards
Vercy

Vercynogetorix said:
Hi,
i have run into a little problem,
After CWM install and then rooting (suing method/files from sticky) following happens
1. System started once
2. All colors were replaced with electronic green (if you know what i mean)
3. System doesn't restart anymore
4. System restarts always and only to CWM
5. On each exit from CWM, User is asked to flash ROOT
6. On each and other system flash, device reboots to CWM only,
any help?
ps. i tried to reflash CWM, root and system all with same effect
regards
Vercy
Click to expand...
Click to collapse
I am not a pro (n00b), but I would update it with the official Android first (http://androidcentral.us/2014/01/update-galaxy-tab-3-7-0-sm-t210r-to-official-android-4-1-2/) .. and start all over again

rajmisc said:
I am not a pro (n00b), but I would update it with the official Android first (http://androidcentral.us/2014/01/update-galaxy-tab-3-7-0-sm-t210r-to-official-android-4-1-2/) .. and start all over again
Click to expand...
Click to collapse
hi,
i did, no help, seems that the CWM image is broken

Vercynogetorix said:
Hi,
i have run into a little problem,
After CWM install and then rooting (suing method/files from sticky) following happens
1. System started once
2. All colors were replaced with electronic green (if you know what i mean)
3. System doesn't restart anymore
4. System restarts always and only to CWM
5. On each exit from CWM, User is asked to flash ROOT
6. On each and other system flash, device reboots to CWM only,
any help?
ps. i tried to reflash CWM, root and system all with same effect
regards
Vercy
Click to expand...
Click to collapse
2 things indicate that your system partition is messed up.
Only boots to recovery
CWM ask to flash root
CWM will ask to flash root, only if it can't find the "root" files in the system partition. If it asks every time, then it isn't able to properly install those root files for some reason.
Download the stock firmware from sammobile.com.
Do a format of your system and data partitions in recovery.
Then, boot into download mode and use Odin to reflash the stock firmware.

gr8nole said:
2 things indicate that your system partition is messed up.
Only boots to recovery
CWM ask to flash root
CWM will ask to flash root, only if it can't find the "root" files in the system partition. If it asks every time, then it isn't able to properly install those root files for some reason.
Download the stock firmware from sammobile.com.
Do a format of your system and data partitions in recovery.
Then, boot into download mode and use Odin to reflash the stock firmware.
Click to expand...
Click to collapse
Hi,
i did, on reflash with CWM same story all over,
im currently flashed with TWRP and everything is fine,
cannot however use CWM (unless try to flash CWM over TWRP)

[Q] TWRP doesn't install recovery

So i went through the rooting process just fine. Go to install TWRP with the Install TWRP app. When i get to the install part, i choose the recovery version to install then click install recovery, reboots found then i get a dead android with a red triangle.
From what i assume something is locked. the bootloader i believe?
I've searched and searched and all i can seem to come up with is having to downgrade to kitkat. Is this true and no way around it?

I think you are on lollipop .. Cos it doesnt work on lollipop

forget about twrp manager. use auto rec to get custom recovery.
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Take a look at this, it is a response to rooting and getting TWRP on 20l
http://forum.xda-developers.com/showpost.php?p=61029248&postcount=2431

kp_q said:
forget about twrp manager. use auto rec to get custom recovery.
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
for some reason when i first tried this nothing happened the other day.
just tried it again and it did install TWRP for me finally. So thanks!:good:

Custom recovery issues! Help please!

Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?

Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!

I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?

hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.

Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img

Rooting went fine Flashing rom almost bricked me due to directions??

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly

Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app

I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?

nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done

Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?

nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good: