Hay Guys,
I have a German(Vodafone) Samsung Galaxy S9 SM G960F and I am stuck on the Samsung Startup Screen. I succsessfuly installed TWRP recovery and Magisk 17.1 after that I noticed that my phone froze on the lockscreen, after I let it sit for a while. So i decited to install a custom ROM. At first Lineage OS and the Problem accured for the first time. After that I tried a few others.
At this point i even downloaded the stock ROM and tried to flash it with Odin. And for some reason, Odin will always get stuck ether on recovery.img or System.img. Now I am out of Ideas and desperately reaching for help:crying:.
I am able to reach twrp and the downloadmode.
Make sure you're not trying to downgrade the bootloader (Check in Download mode for B:1 or B:2)
Firmware shows BL version here
G960FXXU2BRGA
You cannot downgrade from 2 to 1 for example, flash the same or higher
Related
It had clockwork mod on it, so I downloaded TWRP from their site and flashed it via clockwork mod and now the boot image get's all crazy and flickers and then black screens. I can still get into download mode so I guess it's odin for me. It's the GT-N7100 model. What version of Odin and which image do I use? I'm in the USA using T-Mobile. Thanks.
Use the right one for your phone, N7100. Try flash it with odin. If it still in bootloop, flash cf-auto root through odin, usually it will boot after auto root process done. Hope this help...
stonedead said:
Use the right one for your phone, N7100. Try flash it with odin. If it still in bootloop, flash cf-auto root through odin, usually it will boot after auto root process done. Hope this help...
Click to expand...
Click to collapse
I meant what country's firmware, mostly, since I didn't see anything for the U.S and I don't have any info about this phone other than that it's the gt-n7100. Anyway, I got past that bootloop, I used some UK firmware, kinda bootlooping between some o2 splash screen and a samsung logo now. I can get into recovery though.
Ok, I'm not boot looping anymore, just did a factory reset in the stock recovery and it worked.
Now I have another issue - I put my sim in, and it starts up and I have HSPA+. Then it drops to 3g after like 30 seconds, and in the initial setup I can't connect to any services to set up my accounts - it just flat out doesnt work. Then I get into the system after skipping all that and I have no data at all, and when I make phone calls it just hangs at dialing. What do I do? Thanks.
Okay so i went through the bootloader unlock process on my Note 4 without any major hickups, was running on CM13 ever since until i wanted to play with Gear VR which from what i could find required me to be on a stock based/touchwiz rom, first up was Omega which installed fine but would boot loop at welcome screen, so then i went with Evolution and almost same story, just boot loop. Figured it had to be a problem with the firmware version on my phone and without thinking i downloaded the CPF1 firmware and flashed with Odin. Flash went fine with no problems, booted into marshmallow just fine, enabled usb debugging and rebooted to flash TWRP for recovery and i get zilch. Every single TWRP and CWM recovery file i try to flash end in a failure. Can't even get Kingroot to give me root in MM so I think i'm stuck...dont even see the Unlock logo and Custom on the main screen after i hit the power button to turn on.
SO.........
Big question is, did i just re-lock my bootloader when i flashed firmware CPF1?
I think I did this same thing a while ago, were you on an older version of CM13 from May or so? Anyway, what I had to do was flash stock 5.1 in Odin with the up to date kernel, modem, etc and follow the guide to re-unlock your bootloader
Well got it re-flashed and unlocked again, gotta give a shout out to the great guys here on XDA.
Next question is do i need to flash a new bootloader or modem in odin/twrp before moving to a MM rom or is that stuff usually included in the rom? My experience in roms and stuff is from my old Razr Maxx HD and never jumped operating system version with it so i'm not sure on this one.
Hi i was helping my friend to update his firmware. after doing so the phone is now stuck in a weird bootloop. i had seen my fair share of bootloops but this seems weirder than others. the n7100 logo would loop very quickly (sorta like flash) and keeps doing so. can't enter recovery mode at all, only download mode. plug it to odin and whatever i can throw at it i just got nand write start fail, be it twrp, multiple versions of stock rom. im at the end of my wits, so what should i try next? thank you for any input
What is the Odin error when trying to flash the latest stock ROM from sammobile.com? Tried different USB cables and USB ports?
I kinda have/had the same problem.
N7100 logo would bootloop quiet fast (doesn't get to the point where it should load the rom).
Can't enter recovery bc of that.
Only thing that works is download mode.
After trying to flash newest stock rom (4.4.2) it failed once (I think my cable gets too old...)
Next try it worked without a problem.
Problem persists.
Next step was flashing an older repair firmware (4.1.2) but it failed (I think bc of the 4.4.2 bootloader? IDK)
Then I tried to flash the newest stock again but with the pit file. Flashed without a problem but the problem was still there.
Last step I made was to flash the newest stock with the pit file and nand erase + update bootloader.
Tried it 2 times but it failed.
Now I'm stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Download mode got a red message also: "RPMB: INVALID RPMB DATA"
I don't know what to do now. Please help.
PS: It was a "new" motherboard from aliexpess, it had a chinese version of the stock 4.1.2 if I remember right and was already rooted when I installed it. I wanted to flash the newest 4.4.2 for the new modem and stuff and then upgrade to lineage. :/
im so sorry for anytime this may take up..but i am desperate for help.my previous account was username doomtree i think
i had lost it when i messed up my phone.anyhow my phone is a VERIZON NOTE 4 SM 910V
i was trying out some new roms.i had flashed a ported edge rom to my device it was working but showed as T-MOBIL
i tryed a verison modem and brickked...i couldnt access twrp recovery..i did odin restore..my understanding was use a full firmware image
flash with odin.after many attemps i can now get it to flash and pass but i cant seem to flash any custom recovery
and i cant get it to boot up to a functioning system..if left to boot after a odin pass i get through boot to system but nothing showes
...stays blank throwing sytem ui error
simple search reveals...
https://forum.xda-developers.com/search/forum/3676?query=bricked
basically, you need to download samsung kies3 and let it return to stock firmware.
make sure you have a working usb cable as I had given up on un bricking my note 4 but it worked with a new cable.
Doomunit said:
im so sorry for anytime this may take up..but i am desperate for help.my previous account was username doomtree i think
i had lost it when i messed up my phone.anyhow my phone is a VERIZON NOTE 4 SM 910V
i was trying out some new roms.i had flashed a ported edge rom to my device it was working but showed as T-MOBIL
i tryed a verison modem and brickked...i couldnt access twrp recovery..i did odin restore..my understanding was use a full firmware image
flash with odin.after many attemps i can now get it to flash and pass but i cant seem to flash any custom recovery
and i cant get it to boot up to a functioning system..if left to boot after a odin pass i get through boot to system but nothing showes
...stays blank throwing sytem ui error
Click to expand...
Click to collapse
I have the following problem:
A couple of months ago I installed the unofficial Version of lineage os 15.1 on my Galaxy Note s 10.1 LTE because I really wanted to have Android 8. But the S-pen applications werent working properly, so i decided to downgrade to lineage os 14.1. I downloaded the TWRP App, then the wrp.img.tar for my device and tried to flash it via the app, but the file was not flashable, because obviously it was a .tar. I wasnt really thinking about what I was doing so i Just renamed the file to twrp.img so the app would recognice it, which worked out. After I flashed fhe file, I tried to boot into Recovery. But instead of doing so, it booted to Download mode. So I decided to boot into Recovery via quick reboot, which didnt work either and it booted to dowbload mode again. I shut off the device and tried a normal boot, but nothing happend. The screen just stays black. I Hope anyone can help me with that, I really need my tablet.