Hi,
I've the latest cyanogenmod 13 version on my Samsung galaxy Note 8.0 (aka N5100).
With the last nightly update my baseband has been corrupted.
I missed the migration phase to lienage OS, so that now I would have to wipe my device and install the current lineage OS from blank. I'm not prepared to do this fully reset now.
Is there anywhere out there someone, who has a working European baseband for the N5100 available at hand? I only need the baseband.zip file, that I can install with TWRP, to get my device fully operational again.
Thank you very much for any help leading to find a working baseband.zip file!
-morrga
Related
I am trying to flash my Galaxy note 2 (AT&T I-317). I can get into recovery mode but when flashing the rom it will always be unsuccessful and showing infomation as "your device is 't03g' and the rom you flashed is not compatible" From the CM website, seems the correct name of my device is 't0lteatt'. I have no idea why my device is detected as 't03g' and hoping anyone knows how to solve this problem.
My previous ROM is MyMIUI ROM based on android 4.1. Thanks in advance!
I attempted to flash my Samsung Galaxy note 10.1 2014 edition WI-FI tablet for the first time. When I attempted to Install TWRP it displayed an error message and rebooted my device into a TWRP UI. The touch screen would not work, prevemting me from doing anything on this UI. does anyone know how I could bypass TWRP or reinstall an older more reliable version?
Basic answer is do nothing until you understand .
Suggest you post this in the Note 10.1 2014 forum and use TWRP for your model as it reads as you have flashed for a different product .
Hi, my phone (G930L, Korean Exynos version), is rooted, and currently running a beta version of Nougat. I received a message both on my phone and also Samsung Switch program on my PC, that there was an update available. However, I'm unable to update both from the phone and Samsung Switch, due to being rooted.
Is there anyway I can update to the latest beta without having to flash factory stock firmware?
Thanks!
Sorry but i think you need samsung ofw for that.It won't work if you installed a rom based on touchwiz.
Hi,
I had Samsung Galaxy Note 10.1 GT-N8000 with Android 4.4.2 Yesterday I've decided to upgrade using
update-samsung-galaxy-note-10-1-android-7-0-nougat-lineageos-rom/
Wiped, Rooted, TWRP installed, Android 7.0 Nougat ROM installed, Google apps package installed. Every time positive acknowledgment. Everything seems to be OK, software seems to be installed properly.
However, the Android version (4.4.2) (Settings > About), Kernel version, Build number remained unchanged and greyed.
So I cannot install any new apps - they still read I use old Android and prevent installation.
Any idea of how to repair this? Can I change somewhere what >>Settings > About<< shows?
Hi,
if the userdata is also still the same like before,
your eMMC is locked.
I'm repairing these things...
I guess you have to change your eMMC to fix your tablet.
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
*I do not have any backups from Android 12 stable.
You tried flashing official firmware for U device right? You were using CSC file or HOME_CSC to preserve data?
Going back from beta to stable means wiping data, phone will factory reset when you flash back the stable firmware and you should use the CSC file (not HOME_CSC)
Yeah... I know how to operate Odin3... It literally says right there I tried flashing multiple stable builds and each time it fails with AUTH error. Tried HOME and regular CSC....
I have the same phone. I have not gone back to stock U firmware from beta. But I have gone from beta to stock U1 firmware. I believe once you go back to stock U1 Android 12. You can flash back with Odin not patched to U firmware.
zlib1 said:
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
Click to expand...
Click to collapse
Any chance you still have the flashing zip file for beta 1 s908?
The link for beta 1 in this post isn't working
If you do can you send it to me please?
Thanks