Related
I've tried uninstalling superuser and all it has. I've tried like 5 times now the install for the new firmware update won't install i keep getting a android with the red exclamation sign and its front door open, then it boots in to android and says update failed. Help please!
Do I have to factory restore first or somthing? i really dont wanna have to cause i just got this phone from at&t as a referb for my old one that had battery issues and its not fun setting everything up over again lol
\
Hi buddy.
First of all, I don't entirely understand what are you trying to do. What to you mean with "firmware update"? Do you want to flash a new ROM?
mauchito said:
Hi buddy.
First of all, I don't entirely understand what are you trying to do. What to you mean with "firmware update"? Do you want to flash a new ROM?
Click to expand...
Click to collapse
At&t just pushed an ota firmware update that won't install stock ROM is on here only rooted
djshadowxm81 said:
At&t just pushed an ota firmware update that won't install stock ROM is on here only rooted
Click to expand...
Click to collapse
Got it. Check this thread: http://forum.xda-developers.com/showthread.php?t=2751263
You may find all the information you need there. Even if you can't, don't worry, is just a minor update, it is not Kitkat.
I've already been through that thread and haven't really found my solution to my issue. Any ideas?
djshadowxm81 said:
I've already been through that thread and haven't really found my solution to my issue. Any ideas?
Click to expand...
Click to collapse
Sadly no, my friend. Any reason in particular about why you want this specific update?
Let's hope somebody else in this forum can help you.
Are you running a stock recovery? Have you tried using Myth Tools to flash back to stock?
Its running stock rom from factory everything is factory right now
I kept getting the dead Android as well. We're you running a KK ROM on your phone before restoring to stock? I was running Validus and tried to use Myth Tools to flash a stock ATT 4.1.1 ROM which also failed to take the update. I then installed a 4.1.2 Bell stock ROM (my phone came from Bell) via Myth, let the phone boot, and then flashed a stock ATT ROM via Myth and it took the update.
audit13 said:
I kept getting the dead Android as well. We're you running a KK ROM on your phone before restoring to stock? I was running Validus and tried to use Myth Tools to flash a stock ATT 4.1.1 ROM which also failed to take the update. I then installed a 4.1.2 Bell stock ROM (my phone came from Bell) via Myth, let the phone boot, and then flashed a stock ATT ROM via Myth and it took the update.
Click to expand...
Click to collapse
I am on 4.1.1 from the factory. This is a referb phone from the factory like not even a week old yet. Boot loader isn't even unlocked. Its all stock and I'm getting dead android.
If you're getting the dead Android, it makes me believe that something may be wrong with the stock recovery. Some people were able to get the update to install using the latest Philz Touch recovery rather than stock recovery.
This might help from Skeevy: http://forum.xda-developers.com/showpost.php?p=52745043&postcount=7
ok i want to upgrade to lollipop stock tmobile and then root.. can i update by TWRP? download the stock lollipop tmo then just flash it? then use CF root to root it?
this is what im on right now..
re: lollipop update
markysd said:
ok i want to upgrade to lollipop stock tmobile and then root.. can i update by TWRP? download the stock lollipop tmo then just flash it? then use CF root to root it?
this is what im on right now..
Click to expand...
Click to collapse
You cannot update to lollipop using twrp.
It has to be done using odin.
If you want to stay 100% stock and rooted then you need
to odin flash twrp and cf-autoroot.
If you want to flash a custom lollipop rom then you will
need to odin flash lollipop official firmware and odin
flash twrp.
All custom roms are pre-rooted so no need to root them.
Good luck!
Misterjunky said:
You cannot update to lollipop using twrp.
It has to be done using odin.
If you want to stay 100% stock and rooted then you need
to odin flash twrp and cf-autoroot.
If you want to flash a custom lollipop rom then you will
need to odin flash lollipop official firmware and odin
flash twrp.
All custom roms are pre-rooted so no need to root them.
Good luck!
Click to expand...
Click to collapse
Thanks.. So can I just straight up update from what I'm on now?
Just put phone in download mode and update via Odin correct?
Will this erase my stuff internal memory? Movies/pictures
Yes you can. You should back up your stuff though because you'll want to do a factory reset or erase data to get the best results with lollipop.
Although, I did all that and I've got my movies and pictures.
Karakoram2 said:
Yes you can. You should back up your stuff though because you'll want to do a factory reset or erase data to get the best results with lollipop.
Although, I did all that and I've got my movies and pictures.
Click to expand...
Click to collapse
OK backed up my data and moved my stuff to my SD card...
So I'm on that 4.4.4 kit Kat custom ROM.. Just put phone in download mode and flash the lollipop tmobil stock ROM ? I'll just root it with CF after .. I want a clean stock ROM that's just rooted for now..
re: updating to lollipop
markysd said:
OK backed up my data and moved my stuff to my SD card...
So I'm on that 4.4.4 kit Kat custom ROM.. Just put phone in download mode and flash the lollipop tmobil stock ROM ? I'll just root it with CF after .. I want a clean stock ROM that's just rooted for now..
Click to expand...
Click to collapse
Be sure you get the proper version of the lollipop N910T tmobile
firmware from a reliable source like http://sammobile.com and
flash it using odin.
Before flashing new firmware it's always best to do a factory reset first.
Back up all your important stuff first.
Good luck!
Misterjunky said:
Be sure you get the proper version of the lollipop N910T tmobile
firmware from a reliable source like http://sammobile.com and
flash it using odin.
Before flashing new firmware it's always best to do a factory reset first.
Back up all your important stuff first.
Good luck!
Click to expand...
Click to collapse
OK thanks.. OK I finally have time to flash. And update... So it's ok and safe to factory rest on my custom ROM im on right now?
factory rest /put phone on download mode and update by Odin on my computer correct?
Sure is a big file to download :silly:
That's totally safe.
I just odin flashed.
I didn't erase data till I flashed my rom.
Admittedly within a minute of going through the process.
Mega's instructions are good. You just stop at 5
odin reads and i get the com light up and reads it but it wont find my lollipop firmware i downloaded on the pda part
re: odin
markysd said:
odin reads and i get the com light up and reads it but it wont find my lollipop firmware i downloaded on the pda part
Click to expand...
Click to collapse
You need to navigate in odin and find the location where you saved the firmware file.
There is a box next to the PDA slot and you need to click it and use it to locate the file.
Good luck!
Misterjunky said:
You need to navigate in odin and find the location where you saved the firmware file.
There is a box next to the PDA slot and you need to click it and use it to locate the file.
Good luck!
Click to expand...
Click to collapse
yes ive done it.. clicked the box and PDA to search my FW but wont see it..i even tried to extract it.. the sammobile FW was taking way too long and found another DL.. its legit FW.. i thought my FW DL was not good so i deleted it and now i was for the download again:silly: taking long... ived updated my kies and the drivers also...
is it safe to update using kies? i tried it and reads my phone and the FW but i chicken out when it said " might not work right if device is rooted" something like that
markysd said:
yes ive done it.. clicked the box and PDA to search my FW but wont see it..i even tried to extract it.. the sammobile FW was taking way too long and found another DL.. its legit FW.. i thought my FW DL was not good so i deleted it and now i was for the download again:silly: taking long... ived updated my kies and the drivers also...
is it safe to update using kies? i tried it and reads my phone and the FW but i chicken out when it said " might not work right if device is rooted" something like that
Click to expand...
Click to collapse
Yes it's perfectly safe and doing it that way you will not loose any data,
passwords or settings.
It also is a lot faster than downloading the firmware file.
I am not sure if rooting makes a difference, when I updated using kies
it worked fine for me, kies did tell me that I have un-official firmware
but it gave me the option to continue which I did without any issues.
With kies it takes less than 1/2 the time for it to complete the download and
install/update the firmware compared to a standard download and flash..
Good luck!
Misterjunky said:
Yes it's perfectly safe and doing it that way you will not loose any data, passwords or settings.
It also is a lot faster than downloading the firmware file.
I am not sure if rooting makes a difference, when I updated using kies
it worked fine for me, kies did tell me that I have un-official firmware
but it gave me the option to continue which I did without any issues.
Good luck!
Click to expand...
Click to collapse
ok thanks will try that.... thanks again..sorry for the new bee FAQ lol.. been a while :silly: just want to make sure..
Give it a try. There are faster ways to download it. Pretty sure we sure we showed you.
You're not going to break the phone.
Just in case we didn't
http://forum.xda-developers.com/showthread.php?t=3098187
(RESOLVED)
Alright so in order to not bore you all, ill get to the point. I messed up trying to do impossible things with my I537 because I didn't read any forums before trying... stupid I know. That being said I now have a "soft bricked" phone stuck in download mode. I have been looking around (I assume not hard enough) for the right file to flash with ODIN to get me back up and running so I can actually do my research this time before playing with different stock roms.
Can anyone point me in the right direction to get the right files to unbrick this thing?
First things first: this forum is for the SGH-I537 AT&T Galaxy S4 Active, not the I527 Galaxy Mega. I just want to make sure you have the right device. If you have the Mega (I527), you want this forum, and ignore the rest of this post.
If you do in fact have the Galaxy S4 Active (I537), then check out this thread, it has all the official firmware files that have been released for this device. I would recommend using the firmware files for NE3 (KitKat) to flash in Odin. The NE3 build is the easiest to root, and you can always use the keep-root method to upgrade to lollipop if you so desire.
Oh yes sorry that was a mistype. I did indeed mean to type I537. Ok Ill give this a shot and update on how it goes.
Ok so Im currently downloading the Full Odin package, but I have already rooted the phone with towelroot. Is that going to be an issue?
Nah it won't be a problem. Flashing firmware files with Odin will unroot your phone (it resets everything to original factory settings). You can always reroot with towel root again
Ok new problem though, I was able to get everything flashed through ODIN, it restarts; then I get the Samsung boot screen, att boot screen and then it just goes black. I put it back into download mode and tried to re-flash it a couple times but it keeps doing the same thing. Thoughts? This Is the section I got the file from;
I537UCUCNE3 (4.4.2) Released 2014-06-06 - OFFICIAL
Issue has been solved, I just had a battery issue but after changing that and letting the phone charge up it started up great. Thanks for all your help "thisisapoorusernamechoice"
I had problems of phone rebooting automatically and showing emc-read error and cannot boot normally and had to remove battery to start my canadian note 4 W8
the way i fixed this **** is by reverting back to 5.0.1 bootloader
the newest bootloader is the cause of all problems for us
you cannot roll back to the old bootloader just by flashing an old bootloader
but luckily i have found a trick to revert back to a older bootloader to replace **** COK3 (Newest for canadian ) bootloader
So to actually roll back to old boot loader you need a full firmware which has capability to format internal storage when it is flashed
i had a 5.1.1 firmware tar but it did not have the capability of formatting internal storage when it is flashed
But i lucky found a older 5.0.1 tar in my harddisk that has the capability which enabled me to go back to old baseband and bootloader and formatted internal storage and now everything fine
Phone flying as before without any reboots emc read error or lags (i think the reason why this tar worked and back flashed the boot loader is because it formatted the internal storage while the tar was being executed)
just to be extra cautious,once you have old boot loader flash recovery and wipe system,cache,dalvik and internal storage
*IMP GO TO WIPE>FORMAT DATA AND TYPE YES
*MAKE SURE TO RE-FLASH JUST 5.1.1 BASEBAND FOR NOTE 5 PORTS AND CM12.1/13 TO HAVE NETWORK
Attaching the error i had and pic of my current setup
FOR PEOPLE WHO STILL CANNOT DOWNGRADE BOOT LOADER YOU CAN TRY PARTITIONING YOU INTERNAL MEMORY TO FIX READ WRITE ERRORS
LINK OF THE FIRMWARE I USED
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
LINK TO PIT FILES FOR REPARTITIONING
http://forum.xda-developers.com/note-4/orig-development/note-4-pit-files-repartiton-f-g-c-t-w8-t3282641/post64569392#post64569392
Canadians having same issue can now flash this firmware to go back to 5.0.1 bootloader
*i think this would work for Tmobile users too but i am not sure about the risks of cross flashing
i checked my 5.0.1 and 5.1.1 tars and they both have same files so i cant tel which tar you should download for internal storage to be formatted
my most educated guess would be try and download early 5.0.1 builds as samsung must have implemented formatting internal storage when from kitkat to lollipop uograde
And odin 3.10.7
Help Me
Hi,
Can you please help me lookup stock firmware for SM-N910T(T Mobile Note 4) which I can use to rollback my bootloader.
Thank You
Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^
I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing
McMichael96 said:
I keep getting "auth" fails. I can only flash the 5.1.1 software
Please get back to us asap, it's driving me crazy with my phone consistently rebooting and freezing
Click to expand...
Click to collapse
Flash custom rom first
Maybe a cm 12 build and try again
thiennvbk said:
Please help me...
I'm using note 4 n910t and have the same problem of your phone before...very lag and auto turn off the phone,can't boot up or error "mmc read fail".
Can't use your firwame for n910t?!. I know that n910t and n910w8 can using same firwame
---------- Post added at 03:53 PM ---------- Previous post was at 03:47 PM ----------
Can you upload you 5.0.1 bootloader and the manual to fix this error?!
I think a lot of people have this issue when update to newest firwame from samsung, and they are watting for a way to fix their phone
Thanks a lots! ^^
Click to expand...
Click to collapse
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it
Ashwin Prabhunerurkar said:
Flash custom rom first
Maybe a cm 12 build and try again
Click to expand...
Click to collapse
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.
McMichael96 said:
I tried that. Still didn't work. And I have a pretty old copy of 5.0.1. I think it has to do with how T-Mobile/Samsung pushed security policy's to this device. I read up where the last ones actually prevent downgrades.
Click to expand...
Click to collapse
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released
Ashwin Prabhunerurkar said:
I checked on samfirmware
And the BOE2 firmware 5.0.1 i have is the last version of 5.0.1 just before 5.1.1 started rolling out
So download the last version of 5.0.1 just before 5.1.1 released
Click to expand...
Click to collapse
Will the Canadian firmware even work in odin for the t-mobile variant?
McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
Tmobile roms work out of the box for canadian note 4
But bootloader is on a whole another level
U can easily flash another baseband if phones gets busted but i dont know about bootloader
If you are in warrenty you should give it a try
McMichael96 said:
Will the Canadian firmware even work in odin for the t-mobile variant?
Click to expand...
Click to collapse
It might but u shld download the BEO2 equivalent for tmobile
I don't know if I have this problem or not. A few days ago I installed "[N910TUVU2DOK2] Debloated-Deodexed Stock ROM[Dec-18-2015]" along with TWRP recovery. It has seemed to be OK, but I did have a couple of unexpected random reboots. Today while using the phone, it just froze. It did not reboot. After battery pull, I tried to get into recovery, but nothing but short vibrations every 10 seconds or so.
I have not seen any messages about emmc_. The screen remained black entirely. I was unable to get into download mode or recovery mode. When I plugged in with USB, I was able to get it to recognized on USB and in Odin, but had not idea what mode it was in since the screen was black.
After letting it sit a while, I tried again, and was able to boot into recovery. From there, I was able to reboot into Andriod, and everything seems to be normal again.
Is this the same issue? Should I revert the bootloader? If so, what is the correct bootloader for the TMO Note4 N910TUVU2DOK2 ? I have stock ROM for 5.0.1 (N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5) which contains the file boot.img. But in the first post it says it is not possible to simply flash boot.img with Odin?
The required procedure is this?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Ashwin Prabhunerurkar said:
As i said before
just flashing the bootloader doesnt work
U need the full firmware with internal storage wiping capability to return to older bootloader
I will do one thing to help everyone out
Either i will track down the link to download the 5.0.1 firmware i used
Or
I will upload the full 1.7 gb tar firmware
Till then find a older 5.0.1 firmware for your model and try it
Click to expand...
Click to collapse
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.
timg11 said:
Hmm, it's not quite that simple. Just installing 5.0.1 would leave you downgraded to 5.0.1.
There are reasons to move to 5.1.1 (if it works right), so we're trying to determine how to get the BL from 5.0.1 and everything else from 5.1.1.
Click to expand...
Click to collapse
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network
thiennvbk said:
That mean I can download last 5.0.1 firwame and use odin to flash??.
I have try one and odin fail because binary. It isn't allow to come back 5.0.1 firwame.
Can you share the link of 5.0.1 firwame that you had been flash over odin?!
Thanks
Click to expand...
Click to collapse
i have a canadian W8 variaant and i am not sure about the risks of cross flashing
Luckly i found the link of the firmware i used
here it is
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
Download the link in first post
Ashwin Prabhunerurkar said:
you can flash the 5.0.1 firmware now and then flash a 5.1.1 custom rom
so the bootloader version doesnt matter as long as its lollipop
but for baseband you need 5.1.1 baseband for 5.1.1 roms to have network
Click to expand...
Click to collapse
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?
timg11 said:
OK, when I flash the 5.1.1 custom ROM, wouldn't that put the bad boodloader back int?
If I want to end up on 5.1.1 N910TUVU2DOK2, Is this procedure correct?
1) Flash the 5.01 stock firmware N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar .md5 (including the desired bootloader)
2) Boot into stock firmware
3) Select Factory Reset (to execute the data wipe capability in 5.0.1)
4) Shut down and boot into download mode.
5) Flash TWRP
6) Flash 5.1.1 N910TUVU2DOK2 (previously modified to remove boot.img from the tar.md5 file?)
( would this step 6 cause the full functionality of 5.1.1 to be available, but with the non-broken bootloader?)
Questions:
1) Why is the bootloader causing problems with random reboots? During the boot process it corrupts memory?
2) is the problem in internal memory or EXT-SD or both?
3) does the 5.1.1 bootloader continue to corrupt the memory? I.E. if the memory corruption was repaired by other means, would it soon be corrupted again by the bootloader?
4) The T-Mobile 5.1.1 stock ROM has been out since August. This seems like a huge bug. Nobody has seen this issue until now? Or is it specific to rooted devices or the Beastmode kernel?
Click to expand...
Click to collapse
boot loader is the problem
i was using an older version of 5.1.1 bootloader for months and everything was fine but as soon as i upgraded to latest, i started having problems
internal and ext are both fine but just to be safe and start fresh i recommend formatting internal storage
boot loader was not executing internal memory properly hence all the errors,older bootloaders are perfect and you wont face any problems
i haven't faced a single problem in 2 days
there are many versions of 5.1.1 stock roms with different names but i think the latest once is the culprit, so stay away from 5.1.1 recent builds and only flash 5.1.1 base band but try to keep 5.0.1 boot loader.
your procedure seems about right but my tar automatically executed internal memory format and not just factory reset
those are two different things
factory reset formats /data
internal memory formats /system /data /cache etc
so if you tar doesnt support inernal mem format
my suggestion would be to install twrp after 5.0.1 flash and go to wipe>advanced and wipe internal storage
dont flash 5.1.1 again unless you are sure its bootloader is working properly
you just need 5.1.1 baseband to have a well functioning phone
I believe you when you say it works for your variant, but man I don't think it's going to work for our t-mobile variant. Even though they're really similar, I don't believe the Canadian variant got the security policy update that prevents downgrading like we did.
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Have you all tried Smart Switch?
CodeNameRedNeck said:
Have you all tried Smart Switch?
Click to expand...
Click to collapse
Yes... Smart Switch gave me an error in 2 ways of restoration.
ZEDEK said:
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Click to expand...
Click to collapse
Paper-weight? That's bad... Can't you flash a custom recovery on Odin and install a custom rom? I still can do that.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
Click to expand...
Click to collapse
Interesting... So maybe I can wait for a nougat ZTO ROM an then try to flash? Anyway, thanks for the help
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and ..
Click to expand...
Click to collapse
Good catch, I hadn't even thought of that.
CodeNameRedNeck said:
Good catch, I hadn't even thought of that.
Click to expand...
Click to collapse
Well I figured out you can downgrade from Nougat to Marshmallow but that's only to a specific firmware version. Depending upon what bootloader has been flashed (meaning if you flashed Nougat bootloader you can only go back to Marshmallow with the same bootloader level).. But this is only working (surprisingly) on the locked bootloaders of Verizon and AT&T.. The other S6 Edge Plus I have with an unlocked bootloader and tripped knox that I recently acquired will not accept nothing stock which is unusual, but I'm still working on that one.