Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..
khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..
khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude
NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.
najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how
NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.
Related
i own a ATT note 3 i rooted with Kingoo, I got XBast app and modified my phone so when it boots up so i don't see the annoying ATT and samsung logo. with the new 4.4 update that was released i messed up and unrooted my phone from super user app which work but i could not get the update at all it keep failing at 27% install i have permanently lose the all the logos on my phone when i reboot my phone i still have the "custom" lock on dart up i tried re flashing MJ5 but now am left with NB4 build and Baseband MJ5 my phone is constantly looking for att software and i get a constant error (the device has detected an application attempting up permitted actions. To protect your device it is recommended you reboot. ) the phone still boots up and can do pretty much everything with it just those problems are there is there anyway i can just make it like the day i bought it. i tried re rooting with king no luck. someone please help
rajeev2liz said:
i own a ATT note 3 i rooted with Kingoo, I got XBast app and modified my phone so when it boots up so i don't see the annoying ATT and samsung logo. with the new 4.4 update that was released i messed up and unrooted my phone from super user app which work but i could not get the update at all it keep failing at 27% install i have permanently lose the all the logos on my phone when i reboot my phone i still have the "custom" lock on dart up i tried re flashing MJ5 but now am left with NB4 build and Baseband MJ5 my phone is constantly looking for att software and i get a constant error (the device has detected an application attempting up permitted actions. To protect your device it is recommended you reboot. ) the phone still boots up and can do pretty much everything with it just those problems are there is there anyway i can just make it like the day i bought it. i tried re rooting with king no luck. someone please help
Click to expand...
Click to collapse
Just flash full stock firmware using odin. Your phone should be Samsung SM-N900A. Pls check and BE SURE if its really like that before flashing anything provided in my post.
Here you can doenload the stock firmware AT&T and Odin --> http://www.sammobile.com/firmwares/3/?download=25106
You should install latest Samsung USB drivers --> download USB driver
For safety measures you should perform a EFS Backup using this APP
You personal data will be deleted during the flash process so take care of making a backup of everything you need.
Thats just what you need i suppose
LS.xD said:
Just flash full stock firmware using odin. Your phone should be Samsung SM-N900A. Pls check and BE SURE if its really like that before flashing anything provided in my post.
Here you can doenload the stock firmware AT&T and Odin --> http://www.sammobile.com/firmwares/3/?download=25106
You should install latest Samsung USB drivers --> download USB driver
For safety measures you should perform a EFS Backup using this APP
You personal data will be deleted during the flash process so take care of making a backup of everything you need.
Thats just what you need i suppose
Click to expand...
Click to collapse
Thanks MI9 I will try I though you could not downgrade? my build is NB4 and my baseband is MJ5
rajeev2liz said:
Thanks MI9 I will try I though you could not downgrade? my build is NB4 and my baseband is MJ5
Click to expand...
Click to collapse
Why should it not be possible to flash a older firmware? The point is that i have found just that version for your phone. Official firmware flashing via Odin will not affect KNOX. You can perform OTA update to newer version later i think. Just keep the EFS backup in mind
thanks
LS.xD said:
Why should it not be possible to flash a older firmware? The point is that i have found just that version for your phone. Official firmware flashing via Odin will not affect KNOX. You can perform OTA update to newer version later i think. Just keep the EFS backup in mind
Click to expand...
Click to collapse
thanks a lot i will try it out and let you know. have a good day
Failed
rajeev2liz said:
thanks a lot i will try it out and let you know. have a good day
Click to expand...
Click to collapse
i tried it but it keeps failing on ODIN fails every time. any other suggestions?
rajeev2liz said:
i tried it but it keeps failing on ODIN fails every time. any other suggestions?
Click to expand...
Click to collapse
Can you post full error description pls. NOT ONLY "odin fails"...
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!
Well... I've been an idiot.
I recently rooted my Galaxy S7 device whilest scanning the xda threads for a custom ROM.
I flashed Lineage OS 15.1 custom ROM. Everything awesome so far. Except... I didn't like the visual estate of the ROM.
So next step, I flashed the Superman ROM 3.0.1 FINAL. this is where things went wrong.
When i booted up my phone after flashing Superman ROM I lost my IMEI & baseband (both say "Unknown").
I tried to flash stock ROM and ended up with 2 "unknown" IMEI's whilest my phone is a single SIM device.
After that I wiped the lot, flashed Lineage again and still no luck. Although with lineage I have my single IMEI which is still "Unknown".
I've tried flashing stock the correct stock roms but whenever I try to flash the via Odin I get a fail after "sboot.bin".
Odin won't go any further.
So in short, I currently have my device unlocked, rooted, with lineage OS15.1 but no cell service due to
IMEI and baseband being "Unknown".
Any idea's how to fix this?
I've tried the guide with the title "[GUIDE] How to fix IMEI / DRK issues [ALL MODELS][COMBINATION UPDATE 03 NOV 2017]"
But no luck. I can't flash stock firmware due to fail after "sboot.bin" both with stock firmware and the combination file
given in the thread.
Now as part of me being an idiot, I have not made an EFS or baseband backup, nor have I got a Smart Switch backup.
I'm also not capable of finding a person with the Z3Xbox.
Kind regards!
Did you try this https://forum.xda-developers.com/galaxy-s7/help/guide-how-to-fix-efs-damaged-samsung-t3850032
Thanks for the reply! Yes,I've tried that guide too. Problem is that I can't flash anything but twrp through Odin. All the rest fails at "sboot.bin". I'm still trying to download latest stock firmware but all the sites are sooooo slow if you don't pay premium... So I'm still waiting for that file to download. I've tried to flash older stock firmware but didn't get past " sboot.bin" and I've read somewhere that since Oreo Samsung doesn't let you flash old firmware on the phone. So that is at the moment my only hope that I can think of.
Make sure you have the latest version of Odin...you can use updato for faster downloads
cippi21 said:
Make sure you have the latest version of Odin...you can use updato for faster downloads
Click to expand...
Click to collapse
I've used different versions of Odin (v3.12, v3.13, v3.11) and I can only download at 50kb/s with updato. They changed there policy. Donate for premium download speed.
I also went to a repair shop today to ask if they knew any solution. The repair guy I talked to didn't know what root or rooting was so that's a dead end...
Oh ok I am kinda running out of ideas I didn't know updato changed their policy....there is a thread on the forum with the stock roms that people shared you might get better speeds using that...also one last thing you can do is use smart switch there is an option for firmware recovery or something like that try that and see
cippi21 said:
Oh ok I am kinda running out of ideas I didn't know updato changed their policy....there is a thread on the forum with the stock roms that people shared you might get better speeds using that...also one last thing you can do is use smart switch there is an option for firmware recovery or something like that try that and see
Click to expand...
Click to collapse
Thanks for helping though! Every helping hand is welcome! Smart switch recognizes my phone but if I select to recover firmware it doesn't recognize my phone because of the lost IMEI. So downloading to recovering stock firmware from samsung is difficult!
Did you try version 3.13.1 of Odin some people that had the same problem as you said it worked for them and also what model of s7 do you have
cippi21 said:
Did you try version 3.13.1 of Odin some people that had the same problem as you said it worked for them and also what model of s7 do you have
Click to expand...
Click to collapse
Jep, exact version that I used. I have a Samsung galaxy S7 unbrandend from Belgium. (SM-G930F)
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
cippi21 said:
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
Click to expand...
Click to collapse
That's what I was thinking. I've read the exact same thing yesterday. So I started downloading the firmware you just mentioned and the PHN Netherlands one. If one fails I've got another to try. Problem is, with those magnificent download speeds, it takes 24hours to download one of them (yeeeey 50kb/s!!!!!) It should be on my hard drive by tomorrow.
I'll keep you posted if this gets me past the Odin troubles!
I really appreciate you thinking along with me good sir! Thanks for your suggestions!
diSke said:
That's what I was thinking. I've read the exact same thing yesterday. So I started downloading the firmware you just mentioned and the PHN Netherlands one. If one fails I've got another to try. Problem is, with those magnificent download speeds, it takes 24hours to download one of them (yeeeey 50kb/s!!!!!) It should be on my hard drive by tomorrow.
I'll keep you posted if this gets me past the Odin troubles!
I really appreciate you thinking along with me good sir! Thanks for your suggestions!
Click to expand...
Click to collapse
I did exactly the same mistake as you (Lineage, Superman ROMS) and even bricked it trying to fix it!
The reason for that error code in my experience was that I was attempting to put the original firmware on the phone. Thanks to XDA forums and about a week of reading I realised that I had the Oreo ROM on the phone before all this happened, so I did what the poster above recommends and used the latest Odin and the latest firmware for your country from Sammobile. Bam! My S7 is running better than ever!
cippi21 said:
Just read through your post again the superman rom is using the new bootloader 3 and as far as I know you can't downgrade to a bootloader 2 do you get a binary error in odin when you flash? Just trying to figure out what is going on when it stops at sbin
This is the latest rom for your country I know is branded as you can see but is the new bootloader 3 ...G930FXXS3ERI1 - GALAXY S7 SM-G930F PRO BELGIUM (PROXIMUS)
Found it on Sam mobile did you flash that one?
Click to expand...
Click to collapse
Old man android said:
I did exactly the same mistake as you (Lineage, Superman ROMS) and even bricked it trying to fix it!
The reason for that error code in my experience was that I was attempting to put the original firmware on the phone. Thanks to XDA forums and about a week of reading I realised that I had the Oreo ROM on the phone before all this happened, so I did what the poster above recommends and used the latest Odin and the latest firmware for your country from Sammobile. Bam! My S7 is running better than ever!
Click to expand...
Click to collapse
You guy's are all amazing! Thank you so much!
Today I had the chance to flash original firmware to my phone. Flashed latest stock firmware from Holland (because Belgium firmware was branded and my S7 was unbranded).
Rebooted the phone, filled in the start menu's went in to settings and BAM, lost IMEI was lost no more!
Inserted my SIM card and had 4G connection! I didn't even had to flash the COMBINATION file.
I learned from my mistakes and immediatly flashed TWRP and made an EFS en IMEI backup!
Again, thank you so much good sirs! You guys really helped me not to lose hope!
Glad you fixed your phone hopefully this will help other people
diSke said:
You guy's are all amazing! Thank you so much!
Today I had the chance to flash original firmware to my phone. Flashed latest stock firmware from Holland (because Belgium firmware was branded and my S7 was unbranded).
Rebooted the phone, filled in the start menu's went in to settings and BAM, lost IMEI was lost no more!
Inserted my SIM card and had 4G connection! I didn't even had to flash the COMBINATION file.
I learned from my mistakes and immediatly flashed TWRP and made an EFS en IMEI backup!
Again, thank you so much good sirs! You guys really helped me not to lose hope!
Click to expand...
Click to collapse
Absolutely my pleasure! This site has taught me so much, it's great to give a little back.
Hi diSke, Did you find any solution for your IMEI issue, as i also faced same issue and lost IMEI after flashing Superman ROM, and faced same issue. Please let me know steps if you resolved the issue. Thanks in advance.
tarun2k9 said:
Hi diSke, Did you find any solution for your IMEI issue, as i also faced same issue and lost IMEI after flashing Superman ROM, and faced same issue. Please let me know steps if you resolved the issue. Thanks in advance.
Click to expand...
Click to collapse
Flash the latest version firmware for your region/network provider. IMEI restored.
cooltt said:
Flash the latest version firmware for your region/network provider. IMEI restored.
Click to expand...
Click to collapse
Earlier i was trying to flash via wrong Odin version 3.14. But after using Odin 3.13 version the latest firmware was successfully flashed and IMEI is restored back successfully. Thanks a lot for your help.
So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.
PimpWithALimp95 said:
So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.
Click to expand...
Click to collapse
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.
cooltt said:
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.
Click to expand...
Click to collapse
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?
rheh104 said:
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?
Click to expand...
Click to collapse
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc
Huzaifa_Aziz said:
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc
Click to expand...
Click to collapse
EFS?
rheh104 said:
EFS?
Click to expand...
Click to collapse
Encrypted File System
rheh104 said:
EFS?
Click to expand...
Click to collapse
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.
Huzaifa_Aziz said:
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.
Click to expand...
Click to collapse
Send me a link to it please, thanks!
rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
You have Exynos or Qualcomm variant?
I would suggest you start off from here
[LINK]https://forum.xda-developers.com/galaxy-s7/help/help-thread-question-noob-friendly-t3341138[/LINK]
rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
I hope you have read about ODIN and FLASHING recovery by now,
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 go here and flash the TWRP RECOVERY and then install any custom ROM. or
Get original Firmware from Sammobile.com and Flash it via ODIN
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with