Dear Android Brothers and sisters,
I am wanting to update the firmware on my S6 (downloaded from SAMmobile) but am in an odd position...
My S6 main board failed (unable to see mobile networks), and after trying everything in the known universe to fix this, concluded it was hardware and purchased a second hand main board off eBay, that I've now fitted. It was working OK, but is from France (I am in England).
It worked OK but had an ancient stock ROM. The first thing I wanted to do was install Lineage, however there didn't seem any option to allow for the bootloader to be unlocked to allow me to flash the TWRP recovery. After much 'jiggary pokery', I downloaded the English firmware from SAMmobile, extracted all of the binaries and tried to flash them individually using Heimdall (I run Linux not Windows). Whilst this worked for some, there appeared to be a mismach in the partitions that were expected - I guess this is something to do with the France firmware being structured differently? So after a bit of soft-bricking, I managed to get Lineage on the phone, which is mostly working, but behaving somewhat strangely. At the end of the day, I want the latest firmware (radio etc.) and to have Lineage working OK.
Is it possible for me to somehow flash the English firmware on this French board (including the PIT which I assume relates to the partition structure which will allow it all to work)? Any ideas how I'd do this? If I'd have to use Odin, so be it, I'll do it work on my windows box, but ultimately I would like someone to confirm I can do this without bricking my phone. I've read around and people seem to suggest it would be OK but I don't know the best way to do this. I assume the best way to get to my stable end, would be to flash the latest English firmware from SAMmobile, unlock the bootloader, flash TWRP then install Lineage in the 'normal' way?
Any thoughts or suggestions (including pointers to other posts I may have missed) really gratefully received !
Cheers,
Neon
Related
I have been looking for the official firmware of SHV-E150S for the past three days, and I came up empty.
I have tried various methods, such as the KIES hack, without any luck.
In case you are wondering SHV-E150S is the Korean version of the Galaxy Tab 7.7 LTE
The problem with SHV-E150S is that since it's not a popular phone in Korea, Samsung is neglecting its support for the phone.
Thus, there has not been a single firmware update since its release early this year. So I do not think I can use KIES to obtain the firmware
I am really desperate right now, and any help to find a firmware for SHV-E150S will be greatly appreciated.
By the way, according to the KIES registry information, the Software Revision version is E150SKRFB25, which I'd assume it to be the firmware version.
Also, if other (foreign) firmwares can be used for the phone, please give me some pointers or directions.
I really don't care about maintaining the locality or korean-specific aspects of this phone
Thanks in advance.
I didn't even know there was a Korean LTE version, let alone one with PHONE functions. I wonder if a dev can hack an image of that tab to work on the i815 to gain phone functionality. The E150S seems to have different LTE bands tho ;[
E150S: http://pdadb.net/index.php?m=specs&id=3436&c=samsung_shv-e150s_galaxy_tab_7.7_lte_m16
i815: http://pdadb.net/index.php?m=specs&id=3257&c=verizon_samsung_sch-i815_galaxy_tab_7.7_lte
I can dream, right ?
Sorry tho. I Wish I could help.
Maybe a dev here can help you obtain CWM for the device so that you can create a stock nandroid image?
Actually all I need to do is root the phone, since I need it for development.
Since a rooted firmware does not exist, I just assumed that I would need the stock firmware for rooting.
Please correct me if I am wrong, and let me know how to root it without getting the stock firmware.
This root method has worked so far for the 6800, 6810 and i815 versions. Maybe it would work for you?
http://forum.xda-developers.com/showpost.php?p=21584547&postcount=1
ngeroons 41.75.
Thanks for the input,
But it says,
E:signature verification failed
Installation aborted.
And, something funny about my tablet is that it seems like it's not reading from the SD card. I had to save it in the tablet for the recovery tool to see the file.
Problem Solved!!
I finally got the firmware thanks to
samsung-update.com
SAMMOBILE
The firmware for SVH-E150S can now be found at either
sammobile.com
samsung-updates.com/latest-firmware
It seems like I can't post the urls since I am new to this forum....
So can't write down the full URL, but I figure most of you should know these websites already
GalaxyTab 7.7 LTE - ICS_UH11
http_://www_.mediafire_.com/_?aqt3cf3pijp9j
Rom file download via the following link.
Ps. '_' Delete
must root shv-e150s
Dear kthlee,
It appears you were able to download the ROM image and root your galaby tab. I bought a shv-e150s in Korea last year. And I very much want to root it to get rid of several annoyances that are useless if you are not in Korea. Can you perhaps post a step-by-step of how you did it? I know how to download the image from sammobile, that is not the problem. What to do afterwards is what I do not know. I fear I will just end up with a newly formatted tablet, still not rooted. Thank you in advance.
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
Ok. I got an AT&T Galaxy Note 8 back in early-mid 2018. The first thing that happened when I booted it up and connected to a wifi hotspot was that it downloaded the latest update.
That was the last update I received.
I am trying to install Android P onto my device through Odin (Using 3.13.1B PatcheD). I tried OTA first, but when checking for updates, it says that my phone is up to date. I am currently on build U4CRD7.
I called AT&T and they told me that I have to contact Samsung to download the update, and also that it could be a hardware issue (?) and to possibly send it in to Asurion. After that, I called Samsung, and they told me I had to take it to the closest Best Buy. Now, I don't have a way to travel the ~30 miles to the closest one. So, I decided to try Odin. (I have used Odin before, so I am somewhat familiar with it)
I downloaded firmware version U7DTC1_USC from a post here on the forums. I placed all files in the correct areas, went to download mode, tried flashing, and failed. I've gotten three different fails. I changed cables and ports and failed. I tried downloading firmware version U7DSK3 and flashing that one, thinking I might have skipped too many updates (if that is a thing... I've read conflicting information). Failed.
The last failure was a "Complete(Write) operation failed"
Besides taking an expensive rideshare to the nearest Best Buy, is there something that I am missing in trying to update this phone? Could it be a hardware issue? Have I missed too many updates? Do I need to progressively update my phone? (I don't need answers to all these questions, just the most relevant answer please)
If I have posted this in the wrong area, I am sorry. This is my first post on XDA, and I usually don't post in forums anywhere, I just lurk and look for answers to my questions. I haven't been able to find a matching problem.
Edit:
More digging and I found this in another thread.
MrMike2182 said:
...You need to manually update it yourself to the next update version which I think is ... using Odin and then it'll be able to do it on it's own.
Click to expand...
Click to collapse
In further replies, he suggests updating to the firmware version that I am currently at. What is an "update version?" Do I need to just go one firmware update up? Do I need to go one BL version up?
Phone successfully updated
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
G-Man Cometh said:
So, I downloaded firmware version U5DSC1, dug up my 10 year old laptop and switched from the patched version to the normal Odin3 3.13.1.
I don't know which change allowed the update, but I was able to update.
After U5DSC1, I had no problem updating to U7DTC1 through Odin (though the system update feature on the phone still did not pick up any updates after U5DSC1).
Click to expand...
Click to collapse
Your problem was simply because you were trying to use the patched version of Odin and should have just used the newest updated version of Odin. There's no reason to use the patched Odin to flash the normal firmware. People use the patched Odin when they're flashing modified firmware.
Edit: By the way, if it's an AT&T device and you're using say a T-Mobile or Verizon sim card it will not update unless you put an AT&T sim card back in it. It's apparently picky like that. For instance let's say it had AT&T firmware on it and you have a Verizon(or other) sim card in it, the phone is expecting to find and download the AT&T firmware for updates the problem is that Verizon(and others) do not carry AT&Ts firmware they only have their own versions of firmware that's the reason some people don't get updates.
Hello everyone,
So I have been using my canadian G955W (Rogers, but I've been using it in France, if that matters) for a couple of years now, until I got an OTA September 2020, which apparently bricked the modem as described in this thread .
Back then I didn't have time to try any fixes, apart from factory reset, but it still didn't work. Weirdly, a couple of weeks later (late November), when I tried to put back my SIM it worked fine again.
Then I kinda forgot about it and got a new OTA in January 2021 and had the bad idea to update it - so again the same problem : no signal.
So I tried to flash an older version and also the newest version of the firmware (as suggested in the thread above), using Odin v3.13.1 but wasn't able to install anything older than G955WVLU8CTF3 (August 2020), probably because of the bootloader version (?), and still no signal.
I also tried to flash a US version of the firmware (latest one G955USQS8DTJ1), so now I have a G955U, but still no signal.
I'm kindof a noob in all this (sorry for that), but still would like to fix my phone, as the rest is working really fine.
Would you have any advice on what I could do next to find a workaround ?
- I've been willing to root my phone, so should I try this method which also will go to V7 bootloader ? https://forum.xda-developers.com/t/...e-snapdragon-g955u-u1-v8-bootloaders.4128321/
But I'm kind of hesitant, since there's quite a risk of bricking my phone completely..
- Is there another way to go back to an older firmware version ?
- Also what version of Odin works best for the G955W/U ? I have the feeling that v3.13.1 fails quite often with my device.
Thanks a lot for any help !
Good evening ladies and gents,
I got a phone today from Amazon Galaxy Note 10 Plus. SM-N975F/DS.
Got it activated on AT&T which took a bit of trickery but finally got it activated.
So now I am in the process of rooting it and noticed that there are many region specific firmware (you have to use Magisk to patch the firmware (the .md5)). For example mine is N975FXXU6FUCD-MID which was difficult to find and difficult to identify. I have located this (MID) region and its Iraq. As I type this that exact firmware is downloading from SMAMOBILE. I will be flashing a custom ROM within the next few hours. I was wondering tho, since there is no USA Firmware version, will the custom ROM change the firmware thus rendering this entire post irrelevant? Does the firmware matter if the phone is activated and functioning, or is there anything else anyone would suggest? For example should I flash a firmware from perhaps Mexico since its the same continent?
I ask because as I stated above, I am downloading the N975FXXU6FUCD-MID firmware now, and I have to use Magisk to patch the firmware so I just figured I would patch the exact same firmware that is on the phone currently but should i patch a different firmware instead?
Anyway, If anyone has any insight into this I'd love to hear it. Thank you!