I have a Droid Turbo already rooted with BHB27's Oreo ROM, works awesome. So I got my son the same phone and went about trying to root it and install the same ROM. I had software bricked it but used RSDLite and got a stock ROM installed and now I can boot into Marshmallow. But now the wi-fi doesn't work. I have tried flashing different radios and modems with no luck. I need the wi-fi to work so that I can download sunshine and connect so that sunshine can root. Any advice on how to get the wi-fi working? It might be the wrong stock ROM, but I can boot it. It was previously on Marshmallow 6.0.1 prior to all of this so if anyone has a link to the correct stock ROM I can try and flash it. I have downloaded so many "stock" ROMS I'm not sure which was is the proper one.
Thanks for any advice. Any questions just ask.
drtweakllc said:
I have a Droid Turbo already rooted with BHB27's Oreo ROM, works awesome. So I got my son the same phone and went about trying to root it and install the same ROM. I had software bricked it but used RSDLite and got a stock ROM installed and now I can boot into Marshmallow. But now the wi-fi doesn't work. I have tried flashing different radios and modems with no luck. I need the wi-fi to work so that I can download sunshine and connect so that sunshine can root. Any advice on how to get the wi-fi working? It might be the wrong stock ROM, but I can boot it. It was previously on Marshmallow 6.0.1 prior to all of this so if anyone has a link to the correct stock ROM I can try and flash it. I have downloaded so many "stock" ROMS I'm not sure which was is the proper one.
Thanks for any advice. Any questions just ask.
Click to expand...
Click to collapse
You will need To goo back to the sunshine thread and see which 6.0.1 is still rootable ...
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
Hey guys so recently I had rooted my i537 S4 active and have been researching and modifying here and there until i decided to get a custom ROM. I found WickedROM via this post http://forum.xda-developers.com/show....php?t=2491762 and considering it had worked on this person's i537 I decided to flash the ROM. After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE. Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4. I've tried other firmwares with no luck and have resorted to posting about this problem. please help and guide me in the right direction, my phone's been bricked for 3 days now. Trying to boot into recovery gives me the "there's been a problem with your firmware update, please run in Kies recovery" and Kies doesn't recognize my phone.
nickeon1 said:
After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE.
Click to expand...
Click to collapse
You forgot to flash the masterpatch which makes roms designed for the AT&T S4 (not active) work for our phone. If I understand correctly it needs to be flashed immediately after the rom is installed (i.e. still in SafeStrap, before you attempt to boot up).
nickeon1 said:
Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4 and Kies doesn't recognize my phone.
Click to expand...
Click to collapse
That link is for MF1, an outdated firmware. Here is a collection of stock i537 firmwares. I can personally confirm the NH3 file is usable since I used it to upgrade to the most recent firmware without losing root.
This thread will provide you instructions on how to use Odin to flash any stock firmware. I can only add I recommend using Odin v3.07, as I've used it with the most success and fewest issues. Also use NH3 firmware or at the very least NE3, because anything else is outdated, assuming you were on stock KitKat originally, and you will encounter similar issues if trying to downgrade to jellybean.
Also flashing with Odin deletes all your saved files/user info etc. on your phone. From the sound of it, fixing your phone is going to involve inevitably wiping it one way or the other, so I hope you have a backup saved somewhere other than your phone's internal memory.
nickeon1 said:
Hey guys so recently I had rooted my i537 S4 active and have been researching and modifying here and there until i decided to get a custom ROM. I found WickedROM via this post http://forum.xda-developers.com/show....php?t=2491762 and considering it had worked on this person's i537 I decided to flash the ROM. After flashing I had become stuck in a bootloop and I can't get to anything besides DOWNLOAD MODE. Due to this problem I decided to run a stock firmware via Odin with this one_click http://rootzwiki.com/topic/44121-sgh...axy-s4-active/ ... this filled up until the bar was about 90% and then all of a sudden fails at <ID:0/003> system.img.ext4. I've tried other firmwares with no luck and have resorted to posting about this problem. please help and guide me in the right direction, my phone's been bricked for 3 days now. Trying to boot into recovery gives me the "there's been a problem with your firmware update, please run in Kies recovery" and Kies doesn't recognize my phone.
Click to expand...
Click to collapse
When you flash back to stock, you can only flash a version that is equal to or greater than the version you were already on. So if you were originally on 4.4.2 you can only flash a 4.4.2 stock ROM, any other ROM will fail to flash.
thisisapoorusernamechoice said:
You forgot to flash the masterpatch which makes roms designed for the AT&T S4 (not active) work for our phone. If I understand correctly it needs to be flashed immediately after the rom is installed (i.e. still in SafeStrap, before you attempt to boot up).
That link is for MF1, an outdated firmware. Here is a collection of stock i537 firmwares. I can personally confirm the NH3 file is usable since I used it to upgrade to the most recent firmware without losing root.
This thread will provide you instructions on how to use Odin to flash any stock firmware. I can only add I recommend using Odin v3.07, as I've used it with the most success and fewest issues. Also use NH3 firmware or at the very least NE3, because anything else is outdated, assuming you were on stock KitKat originally, and you will encounter similar issues if trying to downgrade to jellybean.
Also flashing with Odin deletes all your saved files/user info etc. on your phone. From the sound of it, fixing your phone is going to involve inevitably wiping it one way or the other, so I hope you have a backup saved somewhere other than your phone's internal memory.
Click to expand...
Click to collapse
Thanks very much for this! I flashed an NE3 firmware and was able to get my phone in working condition. So if I wanted to flash a rom on my phone I would have to masterpatch AFTER the rom flash via Safestrap?
nickeon1 said:
Thanks very much for this! I flashed an NE3 firmware and was able to get my phone in working condition. So if I wanted to flash a rom on my phone I would have to masterpatch AFTER the rom flash via Safestrap?
Click to expand...
Click to collapse
Yes, but make sure the phone doesn't reboot in between flashing the ROM and flashing the Masterpatch.
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
mnemonicj said:
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
Click to expand...
Click to collapse
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
dirtydodge said:
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
Click to expand...
Click to collapse
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
mnemonicj said:
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
Click to expand...
Click to collapse
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
dirtydodge said:
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
Click to expand...
Click to collapse
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
mnemonicj said:
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
Click to expand...
Click to collapse
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
dirtydodge said:
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
Click to expand...
Click to collapse
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
mnemonicj said:
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
Click to expand...
Click to collapse
First off you can't flash cyanogenmod cause of the locked bootloader. We have to stick with TW base roms. I like the stability about TMS2.0 plus the fact that the dev is still working on it. Most all the other devs have went to other phones. TalkingMonkeys is a great dev and is constantly working on mods and features.
Hi. I've searched the forums for 2 days now, and can't find any solutions to my issue.
I have had stock rooted OC4 (Lollipop 5.0) from the FlashFire method for months now. Tried "unrooting" with SuperSU, rebooted, and now I am soft bricked. Looks like I am still rooted though.
When I try flashing a stock rom with odin I get the message "fused 4 > binary 3". I think this means the rom I'm trying to flash (G900AUCU3BOC4-OneClick) is below the version I currently have. I currently DO have OC4 though, so I don't understand. Is there a newer stock rom version around? Has somebody made a OneClick or other Odin flashable rom for AT&T S5 versions later than 5.0? Can somebody make one?
Or if anyone has another solution to help restore my phone to stock that would be great!
I seem to have the same issue as you, if you or anyone figure out something please share!
I have the exact same issue. I have tried everything from flashing using Odin, to sideloading the stock firmware, but nothing works!!!!
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.