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.

Cant Flash ROM using TWRP

Hey guys.
Little review of what happen:
Woke up today and my phone wasn't able to use any of my apps. So, I though no problem let me flash my rom. ( I use SlimKAT)
When I downloaded latest stable ROM I was ready to flash. I come across error while flashing "Executing update binary in <zip name>".
Things I tried:
Wiping:
davlik cache
cahe
system
Rebooting and flashing again. gave me same error.
Any suggestions?
UPDATE:
Now I cant even enter TWRP.

I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.

qwerty3656 said:
I don't know what went wrong, but at this point there is really no downside to just starting over. You could use odin to return your phone to stock then install TWRP or CWM then flash supersu then flash your rom again.
Click to expand...
Click to collapse
Honestly im not sure what I am doing at this point.
My ODIN MODE setting are followed:
Product Name: SGH T999
Custom Binary Download: Yes(4 count)
Current Binary : Custom
System Status: Custom
Qualcol Secure boot: Enabled
Warranty Bit: 1
Boot-loader RP SWREV:1
Im not sure how can i flash my stock rom.
Can you suggest where to start.
Thank you.

I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom

qwerty3656 said:
I'm no expert so do your own research - I think you can skip a step and get the route 66 version of your ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
IT should be the NC2 rom. follow the instructions there to use odin and install the route 66 rom onto your phone - you should then have a rooted stock phone. Then you can install cwm or twrp and flash your rom
Click to expand...
Click to collapse
My problem is that i cant boot in TWRP mode at all. It wont let me enter there.
When i try to flash via ODIN it wont pass.
Any other suggestions?
I got a feeling it have something to do with Custom Binary.
UPDATE:
I was able to get TWRP to boot from ODIN and it passes.
When I try to enter my TWRP it wont let me enter it will skip and go to loading screen of my rom and that's when it get stuck.

To use ODIN, you don't boot into TWRP. You put your phone into Download mode (hold the DOWN volume along with home and hit the power button - when the screen comes up hit the UP volume). You need to be running odin on your PC.

Had to reflash G920PVPU3BOL1 on Sprint S6 after FRP lock, now mods lock touchscreen?

Ok, I made a mistake when using another ROM, and had to flash stock firmware mentioned above because I had OEM unlocking turned off at the time.
The problem is, now when I install TWRP or unikernel for root through odin, it says, depending on which I try to boot,
KERNEL IS NOT SEANDROID ENFORCING
or
RECOVERY IS NOT SEANFROID ENFORCING
Using odin.
and the touch screen is completely disabled. The only way to get touchscreen working again is to flash stock firmware again.
What do I do? OEM unlocking is turned on. What am I missing?
Does it have something to do with installing a ROM and choosing that Samsung option of security/remote locking or whatever during setup?
I cannot figure out what to do. As soon as you use kernel or recovery that is not seandroid enforcing, the touchscreen becomes unusable.
---
Also, as I try to fix this, is there a way to just extract only the kernel from this firmware so I can reflash just it if this happens again? I tried just extracting boot and recovery via odin but recovery doesnt resolve the kernel error and boot just makes it reboot in a loop.

H0wdy said:
Ok, I made a mistake when using another ROM, and had to flash stock firmware mentioned above because I had OEM unlocking turned off at the time.
The problem is, now when I install TWRP or unikernel for root through odin, it says, depending on which I try to boot,
KERNEL IS NOT SEANDROID ENFORCING
or
RECOVERY IS NOT SEANFROID ENFORCING
Using odin.
and the touch screen is completely disabled. The only way to get touchscreen working again is to flash stock firmware again.
What do I do? OEM unlocking is turned on. What am I missing?
Does it have something to do with installing a ROM and choosing that Samsung option of security/remote locking or whatever during setup?
I cannot figure out what to do. As soon as you use kernel or recovery that is not seandroid enforcing, the touchscreen becomes unusable.
---
Also, as I try to fix this, is there a way to just extract only the kernel from this firmware so I can reflash just it if this happens again? I tried just extracting boot and recovery via odin but recovery doesnt resolve the kernel error and boot just makes it reboot in a loop.
Click to expand...
Click to collapse
---
UniKernel-v6-920P-072915.tar
this one worked.
After that, using twrp manager from google play then letting it install twrp worked.

I ****ed up when trying to install flash TWRP 3.0.2

Hello,
I was trying to flash the newest version of TWRP on my Note 4 by flashing the image within TWRP(as the instructions suggested). What I did not notice was that I had an older version of TWRP installed than the one recommended in the instructions. After flashing the image and reboots the phone enters the download mode, and I am not able to proceed into recovery mode.
I downloaded the newest version of odin and flashed TWRP using the AP mode. By utilizing the auto-reboot setting I was able to boot into the OS, and everything seems to work fine. However when trying to reboot into recovery I still get the download mode. Is there any way to fix this?
All answers are greatly appreciated.

Sorry for bump.
Anyone?

fezken said:
Sorry for bump.
Anyone?
Click to expand...
Click to collapse
Are you Rooted, or are you trying to root using this method? If you're rooted download flashify and download TWRP, or CWM, or Philz for the device and it should be successful. If it's not, please reply back and i can see what's going on.

Thank you for the reply. Yes, I am indeed rooted. I tried flashing TWRP through flashify, but my phone still enters download mode when rebooting after flash. "Could not do normal boot" in the top-left corner. To make the phone boot into the OS I have to flash TWRP through Odin. This solves the "booting into the OS"- part,but when I try to boot into recovery I get the download mode aswell. I am thinking that I might have to wipe everything and re-install TWRP and the custom ROM(emotion rom MM). What is the best way of doing this?
Jonas

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!

Flash the stock patch recovery as boot??

orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up

i have just helped someone through this on TG so it defo works :good::good::good:

It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.

drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!

@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.

Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?

KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?

I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device