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] Won't boot rom or cwm recovery - only download mode

Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?

No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app

Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?

Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?

This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".

vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards

Recovery Fail!

So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?

kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!

Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?

Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.

Boot Loop - Please help!

Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop

An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?

By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.

Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.

lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.

Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!

Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.

Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.

{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