Develop Bugs

I can't seem to root

I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?

You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.

Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).

bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.

I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^

The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?

Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!

Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2

If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.

[Q] Problem with custom roms

so i have the desire hd and i love the phone a lot but not the os too much. so heres the deal i tryed installing cyanogenmod.I unlocked the bootloader left the s-on and installed custom recovery via fastboot without a problem. next thing is I installed 3 recoverys non touch everyone different but when i install zip file with the rom it gets stuck every time on boot screen. the thing is i tried cyanogen 7.2.0 9 and 10.1 non of them worked and got stuck right on after it at the htc green logo,. whats the problem i pulled out the battery tried with only usb nothing worked. then i got scared that it isnt bricked dowloaded the original stock rooted rom as it was and installed through the same recovery .then it worked without a problem not even a glitch . i dont get it .im confused. apologies to the admin if it isnt in the right section.
my android version is 2.3.5 withe sense 3.0 and thats it . cant figure whats the problem . i flashed ducent of phones from symbian to iphone and even java based phones and even few htc ., but never had that boot loop problem., anyone please help

Fastboot flash the ROM zip's boot.img.

bananagranola said:
Fastboot flash the ROM zip's boot.img.
Click to expand...
Click to collapse
so i need to flash boot.img from the rom and flash it with fast boot then install software with custom recovery . i use boot image from stock rom or cyanogen ?

alenkosb said:
so i need to flash boot.img from the rom and flash it with fast boot then install software with custom recovery . i use boot image from stock rom or cyanogen ?
Click to expand...
Click to collapse
No, flash ROM from custom recovery first, then the boot.img from fastboot. Use a custom, not stock, recovery (CWM, 4ext, or TWRP).

bananagranola said:
No, flash ROM from custom recovery first, then the boot.img from fastboot. Use a custom, not stock, recovery (CWM, 4ext, or TWRP).
Click to expand...
Click to collapse
i used 3 diferent custom recoverys for desire hd. ill try the method.btw you cant install cyan with stock recovery .boot img from stock rom ?

no, the boot.img inside the zip of the Rom you´re going to flash at this moment

alenkosb said:
i used 3 diferent custom recoverys for desire hd. ill try the method.btw you cant install cyan with stock recovery .boot img from stock rom ?
Click to expand...
Click to collapse
I have no idea what you're trying to say. What recoveries have you tried to flash? How have you tried to flash them? How are you trying to flash the ROM? What is "cyan," ClockworkMod (CWM) or CyanogenMod (CM)? What is a "stock recovery .boot img"? You can't flash anything from the stock recovery. You can't flash the stock ROM's boot.img with a custom ROM. Recoveries do not have boot.imgs that you need to worry about. I am saying that you need to have a custom recovery, like CWM, 4ext, or TWRP, installed. You do that through "fastboot flash recovery recovery.img." You then need to download a ROM zip, boot into recovery with power and volume-down, factory reset, and install the ROM. You then need to extract the boot.img from the ROM zip you just flashed and flash it from the computer with "fastboot flash boot boot.img."

bananagranola said:
I have no idea what you're trying to say. What recoveries have you tried to flash? How have you tried to flash them? How are you trying to flash the ROM? What is "cyan," ClockworkMod (CWM) or CyanogenMod (CM)? What is a "stock recovery .boot img"? You can't flash anything from the stock recovery. You can't flash the stock ROM's boot.img with a custom ROM. Recoveries do not have boot.imgs that you need to worry about. I am saying that you need to have a custom recovery, like CWM, 4ext, or TWRP, installed. You do that through "fastboot flash recovery recovery.img." You then need to download a ROM zip, boot into recovery with power and volume-down, factory reset, and install the ROM. You then need to extract the boot.img from the ROM zip you just flashed and flash it from the computer with "fastboot flash boot boot.img."
Click to expand...
Click to collapse
Sorry for the misunderstanding. heres the deal ive had 3 clockworkmode recoverys and different versions tried 3 zips(roms) with each one and every time de same thing.BUT now thanks to your help i flashed the boot.img file and it works perfectly

How to keep DualRecovery after flashing CM based rom?

I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?

SethPDA said:
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
Click to expand...
Click to collapse
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.

levone1 said:
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
Click to expand...
Click to collapse
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.

SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse

levone1 said:
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
You can't because CyanogenMod uses its own Recovery based of CWM ( I think? ). You could try however, using a custom kernel that has its own Dual recovery ( for e.g. PhilzTouch and TWRP )
Click to expand...
Click to collapse

SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
Click to expand...
Click to collapse
I just remembered something else. See my post here- http://forum.xda-developers.com/showpost.php?p=62114382&postcount=534 - latest version of Rashr doesn't seem to work on some ROMs. Try this one...
Edit - I just successfully flashed twrp 2.8.7.0 on latest RR using Rashr. Make sure to use this version, not the latest Play Store.

Okay so I tried what @levone1 said. I installed that Rashr which you uploaded. I tried flashing the recovery with this, and it worked! Thank you very much guys for your help!

hey thanks to levone1 i got twrp running on crDroid rom.:good::good::good:
i did it like he said: Use his Version of rashr and flash his twrp. done!

TWRP gets overwritten

I'm on latest ob18. I am able to flash it, and run it once, but after reboot, the stock recovery gets Back. Any ideas?

Just Reflash twrp via flashify or adb in fastboot mode, that could be normal if u r flash an unmodified stock rom

Yep. On latest ob-Oos or H2o for me recovery stays, after instaltion of the rom. But on a second reboot, stock recovery shows and i reflash custom recovery again.

Guys I flashed latest H2OS beta over OOS Beta18 and lost access to recovery. These are the steps I followed, please help.
1. Backup current ROM (OB18)
2. Dirty Flash New H2OS version
3. Flash recovery image again
4. Reboot system
ROM booted without any problems and all my data is present but I lost access to TWRP.
Solution attempted: Reboot to fastboot and flash recovery image again, the process is successful but still TWRP is not coming up.
Please help. Thanks in advance

Stock rom always over writes recovery best way to get it to stick is flash stock zip than twrp reboot to twrp and reboot or flash mods/root

liam_davenport said:
Stock rom always over writes recovery best way to get it to stick is flash stock zip than twrp reboot to twrp and reboot or flash mods/root
Click to expand...
Click to collapse
Thanks this worked

TWRP - Permanent Installation or Temp?

Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.

My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!

I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.