Hi.
I have a telecom new zealand i9505. I attempted to install a custom recovery but I'm not sure if it worked. I do have a recovery mode I can boot into but it doesn't have many options and I assume it's the stock Samsung recovery. My phone is currently running Android 4.3 but doesn't autoupdate bc I now have a modified the recovery.
Can someone suggest either
1. What stock rom should I flash to. Do I have to flash to another stock 4.3 rom using odin or can I flash a 4.4.3 rom? If I flash using odin can I use the autoupdate feature under settings?
2. Is there a fast stable rom that has built in auto updates without having to worry about flashing and backing up etc.
The reason I want to update is.
1. The phone is sometimes sluggish.
2. There was a Google update that caused a bug whereas every time I pah home button it askes which home screen and it will not remember the defaults and the ONLY solution was to uninstall the updates which means I don't have Google now anymore.
Thanks
Kiwi
Upgraded from Kitkat to Lollipop. Just. Need some help rooting.
So not being very experienced at Rooting/Flashing Roms this may come across strange.
Here is a little background to my problem.
I had a rooted Note 3 running KitKat before I decided to flash to Lolipop. I downloaded the Vodafone (UK) variant of the ROM from Sammobile not thinking anything of it at the time (As I am on Vodafone) I went through the usual procedure of going into download mode running Odin as admin and then connecting my phone, adding the Rom files to Odin and then Flashing. Flashing started fine as it got towards the end it Failed on Hidden(Something).
I panicked didn't know what to do so I unplugged my device and tried to reboot. It didn't. It said something along of the lines as there is a firmware error and got stuck on that screen. Panicked some more, decided I would try to google a fix. Came across one which required me to flash CWM Recovery onto my phone. I thought I would try it, Once it flashed which went fine I was told too try and boot straight into recovery mode once the phone starts and reboot through there. I took out my battery put it back in and then went ahead and tried to boot into recovery which worked. Once on CWM I went to reboot the phone As I hit yes too reboot It took me to another screen where it said I wasn't rooted and if I would like to reroot. I decided to click NO and restart the phone. It got stuck on a boot loop, I did a factory reset and cache wipe and it booted into life. (And working fine so far)
So here is where the problem is.
I am looking to get root back to the device. I think I have a locked boot loader as I installed the Vodafone variant of the 5.0 Rom. Would I be able to Flash the BTU Rom onto my device without bricking it, and after that would I be able to root Via CFAutoRoot which seems to be the easiest way to so. Or could I flash with CFAutoRoot Straight onto this ROM.
Info:
BTU ROM:
Date Country/Carrier Version PDA CSC
2015-07-01 United Kingdom 5.0 N9005XXUGBOF1 N9005BTUGBOD2
ROM I INSTALLED:
Date Country/Carrier Version PDA CSC
2015-06-01 United Kingdom (Vodafone) 5.0 N9005XXUGBOD6 N9005VFGGBOD2
Thanks for any help in advance.
I recommend installing TWRP and flashing supersu.zip from TWRP.
Search "CF Auto Root Note 3 xda" in Google.
That's easy.
Btw i too will recommend using TWRP as recovery.
Sent from my SM-N9005 using Tapatalk
Problem Solved, Flashed to another 5.0 ROM and then rooted via the normal CF Method. Thanks for the replys.
Dear Community,
I have managed to reach this wonderful error message on my S8. A few of you knew this maybe with "FRP" from other Samsung devices. However, I know I get this because I am using a custom rom and a modified kernel. I also do know a possible solution might be flashin a new stock firmware through Odin - so my question is, how can I save my data? I only need my Whatsapp folder and my pictures.
For the nosy readers, I did download a GPS Faker App from the Google Playstore, and I had to re-enable my developer settings. Sadly I forgot to push the button for "OEM Unlock" to yes.
Have a nice day!
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
ItsYeBoi2016 said:
Sadly there is no other way to fix this, the only way I got it to work again was to go into Odin mode and flash a stock firmware ( I also lost root access and TWRP, which I installed afterwards again )
You can YouTube how to flash a stock firmware
Hopefully this helped
Click to expand...
Click to collapse
Is there no other option like installing an unmodified kernel through odin? Tried with Jesse, but I was not able to transform the flashable .zip to a .tar.md5 for Odin.
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
ItsYeBoi2016 said:
I'm pretty sure to install a custom kernel you need OEM unlocked, but I might be wrong... I just installed the firmware i needed from sammobile and flashed it using Odin.
Click to expand...
Click to collapse
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
but what if the file i downloaded is just a *.zip file?
is there a way that i wont lose my data?
Same problem
Hello. I got stuck in the "custom binary blocked FAP lock" too. my question is: will there be any problem if i try to flash a firmware from another country? Also, what are the risks that i completely brick my phone?
I was on stock rom 8.0, with twrp and magisk installed.
dave7802 said:
Just to touch on this for future readers.
He already had OEM Unlocked (So to speak) He has flashed a stock ROM or Custom ROM, and continued with Rooted, TWRP and maybe Xposed.
But for one reason or another he has had to activate the developer settings to change a toggle.
In doing so, he changed the toggle needed, but this also Triggers the OEM Option.
If you do not select the OEM Option, then when you reboot your device, you are locked with this message.
It basically sets it self to off.
There is no way to bypass this message, the system has blocked itself from booted and thats that.
All you can do is flash the Stock Files via Odin again, You may be lucky flashing the Home_CSC file to prevent Data loss, But dont hold your breath
Click to expand...
Click to collapse
one of the lucky ones here.
I think my biggest obstacle is my Mac. Got all my pre-requistes sorted out , run jOdin, connected to phone, open up the firmware folder and designate the correct files, get the PIT file, and click start.... and get "A corrupted file was detected. In order to continue, you must select a valid Odin File" error . Downloaded several firmwares and cant get past this issue.. Not sure what to do (new versions of jOdin comptability? But even back in 2017, i tried flashing with jOdin but never succeeded despite following every step.
hello
is it possible to flash a custom rom via odin?
the reason i say this is for some reason now i cannot enable oem unlock in developer settings, keeps showing a device protection function and even when i click enable the slider switches on for a second then goes back. i have tried many stock roms using the latest versions from samsung.
so i am wondering if i can bypass the having to enable the oem unlock to flash twrp recovery then the custom rom and just flash custom rom straight from odin.
james
jamos316 said:
hello
is it possible to flash a custom rom via odin?
the reason i say this is for some reason now i cannot enable oem unlock in developer settings, keeps showing a device protection function and even when i click enable the slider switches on for a second then goes back. i have tried many stock roms using the latest versions from samsung.
so i am wondering if i can bypass the having to enable the oem unlock to flash twrp recovery then the custom rom and just flash custom rom straight from odin.
james
Click to expand...
Click to collapse
In simple terms, you can't flash anything thats not officially by samsung through odin or anything else if you don't have OEM Unlock enabled (or can't enable it due to any reason) ..
Plus as I know.. even if oem unlock is enabled.. odin can only flash official stock roms..
For flashing any custom rom you need to use twrp..
But twrp can be flashed through odin.
OK Got my prior issue sorted out and got the tablet back up and running with the original Firmware.
I have the bootloader unlocked, but not able to gain root. Want to remove a lot of bloat and need root based Ad Blocker.
Tried the root method that was posted but it wont boot with patched boot.img flashed in Odin, I suspect it is due to it being Android 13 and the release that came out earlier this month.
Can't seam to get the original firmware to flash completely either with Odin either.
Any know ways that work with current Software?
Thanks for input