Database Users

Downgraded my Note 3 to kitkat now I have a bootloop

Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!

peety25 said:
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
Click to expand...
Click to collapse
Try this:
1. Full wipe first (system, data, cache and dalvik)
2. Flash the VIA Kit Kat firmware via ODIN unticking "Autoreboot".
3. Take out the battery and pull in it again when the flashing process finish.
4. Boot in Recovery and make full wipe again.
5. Reboot your device and it should boot normally.
6. Tell me if it worked for ya

Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.

try flashing MODEM with NON-HLOS, I think you have corrupted the EFS.

peety25 said:
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
Click to expand...
Click to collapse
You can flash TWRP recovery if you don't care about KNOX and follow my steps above :highfive:

Galaxy Note 3- Updated To Lolipop, Need Help Rooting

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.

SM-N910F > Bootloop // ROM Problems || Please Help

So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
// Edit:
// It is a German Device from Telekom.
// If that helps or makes a little difference.
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.

Try Samsung care

R3dRacoon said:
So.. hello.
Normally I don't come to forums to get help... but yeah. This is kinda bad.
I've got a little situation here.
I got my new Samsung Galaxy Note 4 (SM-N910F).
It was delivered with Stock 5.1.1.
First try:
I booted to the Downloader, fired up Odin, let it download the Autoroot.
Then I've got a bootloop.
Second try:
Booted into the Downloader, fired up Odin, let it install the 5.0.1 Stock ROM (Ending with 'BOB4')
It booted normally , then two things pop up constantly:
Something like "phone.xxxxxxxx.xxx Service crashed".
and "NFC crashed."
So I can't even unlock that phone.
Third try:
Booted into the Downloader, fired up Odin, let it install "N910FXXU1COI3_DevBase_alexndr".
Ended up in a Bootloop.
Then I tried to install the Bootloader aswell as the Modem and the Kernel, which are also in alexndr's Thread.
Ended up in the same Situation as the second try.
I don't no what to do anymore.
I'd really love to hear some help from you guys.
Greetings,
R3dRacoon
______________
UTC+1 (If I don't answer instantly)
And yeah, I've used search. And that for like the whole day.
Click to expand...
Click to collapse
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)

Battlehero said:
The third attempt was incorrect, that file is to be flashed from a custom recovery.
The second try might be because you did a dirty flash (Need to wipe data)
The first attempt boot-looped because in order to root in 5.1.1 you need a rootable kernel and the latest SuperSU (Not CF-Auto root)(Kernel is found in the Android Development thread)
Click to expand...
Click to collapse
Thanks for the response.
What can I do to get a correct working System back? (Theoretically, I got time and bandwidth.)
Since flashing the Stock ROM did not quiet work.

medo sator said:
Try Samsung care
Click to expand...
Click to collapse
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.

R3dRacoon said:
KNOX Flag is already 0x1. Means varranty is void, isn't it?
So I don't think they will help me.
Click to expand...
Click to collapse
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom

medo sator said:
ok first flash twrp via odin then flash your 5.0.1 bootloader and modem then boot to recovery and wipe all systems and data then bootinto download mod and flash any custom 5.0.1 rom
Click to expand...
Click to collapse
I've already tried to flash TWRP via Odin, but I've never seen it.
Flashed recovery was for trltexx.
Getting to Recovery should be the same as getting to Download Mode, or?
Anyways. Will try it with tbltetmo and report back.
// Just installed the tbltetmo.
// Can't see how to get into the recovery.
// Am I missing something?

Update:
Just signed up at sammobile and downloaded the BOB6 (4.4 i think) for T-Mobile.
Flashed via Odin.
Seems like it does work again.
Currently its installing like 260 Apps.
Let's see.
// Edit: Nah. It got even worse.
// But I got a Recovery. So that's something.
IT ****ING WORKS NOW
Went into the recovery and cleared cache and data. (Kinda stupid I did not do it inb4)

Do a clean install in Odin. Since it came with stock android 5.1.1, then flash the 5.1.1 stock firmware in Odin. If you have a locked device of a specific carrier it will be even better to use the firmware made for that carrier only. And check the "Nand erase all" option in odin before hitting the start button to flash. That will erase all the data from ur phone and will do a clean install. Your phone must then boot normally. Also note that android 5.0 root file may not work for 5.1. Also check the model number before flashing.

S5 900i - Rooting problems - "Can no do normal boot"

HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help

brendy79 said:
HI, I have tried to root my S5 900I but failed badly, have done other phones in the past but somehow stuffed this.
The phone is stuck on downloading screen and cannot do normal boot.
I Started with flashing "recovery.tar.md5" 1st which passed in Odin but phone stuck on downloading screen, then I went into recovery and tried reset and flash CF Auto Root but still not working.
Then flashed twrp.kit.tar and still no normal boot but I can get into recovery Team Win, have tried numerous wipes and installing more CF Auto Root's and also tried flashing Miui Rom.
I believe I have screwed up the stock rom and don't know what to do next.
appreciate any help
Click to expand...
Click to collapse
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.

iSergiwa said:
Same happened to my wife's Galaxy Grand Prime months ago; stuck at downloading mode after rooting and installing TWRP recovery. The problem was with the version of TWRP recovery I was installing. Looks like I was installing the wrong one (although the website I downloaded it from states that it's the correct one for the device model). I tried different versions from different websites and was about to wipe everything and flash the stock rom but finally I got the correct one and that fixed the problem. Hope that helps.
Click to expand...
Click to collapse
Thanks, I'll keep trying different TWRP, have tries so many but have changed the outcome yet

galaxy s10+ stuck in odin at boot img

When i try to flash latest firmware from sammobile using odin 3v3.13 it wont go past boot img????
Im losing my mind trying can someone please help me

adzo73 said:
When i try to flash latest firmware from sammobile using odin 3v3.13 it wont go past boot img????
Im losing my mind trying can someone please help me
Click to expand...
Click to collapse
Hello, I had the same problem.
Before you flash restore your phone to factory default ....settings.....general ......
or by stock recovery mode ...... https://android.gadgethacks.com/how...s10-into-recovery-mode-download-mode-0194521/
and perform a factory data reset .
Then I flashed with Odin 3.13. only the AP_File. (AP_G975FXXS3ASH1_CL16487975_QB25171324_REV01_user_low_ship_meta_OS9.tar)
This is the latest official Firmware for Samsung 10+ (Exynos).... SM-G975F_1_20190805141127_n52ujmrqr9_fac
Best regards
Antonio

granada_es said:
Hello, I had the same problem.
Before you flash restore your phone to factory default ....settings.....general ......
or by stock recovery mode ...... https://android.gadgethacks.com/how...s10-into-recovery-mode-download-mode-0194521/
and perform a factory data reset .
Then I flashed with Odin 3.13. only the AP_File. (AP_G975FXXS3ASH1_CL16487975_QB25171324_REV01_user_low_ship_meta_OS9.tar)
This is the latest official Firmware for Samsung 10+ (Exynos).... SM-G975F_1_20190805141127_n52ujmrqr9_fac
Best regards
Antonio
Click to expand...
Click to collapse
I'm just doing this with this advice here, and only running the AP_File as advised. Hope the S10 doesn't get bricked because I have not loaded other files.
Also seems Odin is in state, SYSTEM, which is now so far 20mins and don't seem to see more progress

for those who updated the german beta (android 12), remember to unlock your bootloader in settings, because the knox get triggered after detecting different system files and the original bootloader, if u unlock the bootloader, it lets odin rewrite it and get the PASS