Develop Bugs

[ODIN][TAR][OCG] Stock firmwares

I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!

jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Thanks been looking for this

Ahahahahahahaha! I believe roms can be crafted!

jamcar said:
I present the latest stock ODIN firmware directly from Samsung. The current latest is G925TUVU1AOCG. These are for the T-Mobile Galaxy s6 Edge (SM-G925T) ONLY! DO NOT flash this on any other device.
Instructions:
1.) Make sure you have ODIN 3.10 setup (there are many tutorials on xda and youtube for this).
2.) Download the latest firmware zip from below.
3.) Extract the tar.md5 file from the zip.
4.) Add the tar.md5 file to the AP section of ODIN.
5.) Under Options make sure to ONLY select "Auto Reboot" and "F. Reset Time". DO NOT select repartition (or really anything else)!!!
6.) Click start and let it flash.
(Again there are plenty of tutorials on how to use ODIN)
This won't wipe your data (probably). (It didn't during my test but always make backups just in case.)
Downloads:
G925TUVU1AOCG SHA256 (of zip): 70146cbcf5fe157ca1691085db15e8ffaa7cbdeaa16a6043567a1c5796a6cb93
Flashing anything is dangerous and I am not responsible for anything you do to any of your devices!
Click to expand...
Click to collapse
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.

Docmjldds said:
Appreciate the first downloadable tar. Maybe a better place would be in the Android Development section. Just a thought. (Or original android development. ) Not sure which would be more appropriate but I'm sure a lot more users would see this. Just my 2c. Thanks for the post.
Click to expand...
Click to collapse
Unmodified stock ROMs do not belong in the android development section so general seemed like the better choice. Any mod, please correct me and move this thread if I am wrong.

Always seem to remember them being in general or Q and A.
Word

THANK YOU for upload to MEGA. I'm getting really sick of the rapidgator spam.

Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!

ShermCraig said:
Just when I think I'm getting well versed in rooting, etc. I ask a question like this:
What is the reason to install the stock firmware? I'm rooted with stock recovery flashed.
Thanks!
Click to expand...
Click to collapse
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?

Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse

ShermCraig said:
Yep that helps! So, aside from that, if I am up and running - albeit very slowly and with significant battery drain - is there any reason for me to flash this firmware?
Click to expand...
Click to collapse
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating Cured by flashing the stock ROM Firmware.

SuperSport said:
Those TWO reasons are exactly why you should try this. MANY, including myself have had the battery drain, lag, and overheating cured by flashing the stock ROM.
Click to expand...
Click to collapse
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!

ShermCraig said:
@SuperSport - you said you flashed the stock ROM - @jamcar is talking about flashing the firmware. Two completely different things. Can someone clarify? FWIW, I did flash the stock ROM a few days ago, but after reinstalling everything, I'm back to being laggy and battery drain.
Thanks all!!
Click to expand...
Click to collapse
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...

Okay, that makes sense. I have been having Amazon FC's since rooting. Frustrating but not as bad as it was at its worst. Using Clean Master for the lag issues and Greenify for the battery. Not sure if they counter each other though. Anyway, I will try flashing the Firmware and report back. Thank you again for clarifying.
SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse

SuperSport said:
Yes, I said that wrong. I meant Firmware. There are many reports that the issues go away after flashing the Stock Firmware back on. I was using Smart Switch to do it, but Odin is a great alternative if Smart Switch does not work for you. I'm not sure why your issues returned, maybe the Root is bringing it back, or maybe an incompatible app. I've found a few apps that Force Close on me that never used to on my Galaxy S4 (ie: 'dji-vision' app for the Phantom Drone), so it is possible other apps are drawing too much power, etc...
Click to expand...
Click to collapse
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.

jamcar said:
@SuperSport correct me if I'm wrong but aren't there two reasons for @ShermCraig issues? First would be the outdated build and second would be the recovery deep sleep issue if they're rooted.
Click to expand...
Click to collapse
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.

SuperSport said:
Yes, and Yes. But I have heard some report that they Rooted after flashing the Firmware that has the OCG update included and they did not have the deep sleep issue anymore. Although, I believe they replaced the recovery with the original again. I myself have not rooted, so I'm not speaking from experience, just what I've been reading.
Click to expand...
Click to collapse
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!

ShermCraig said:
So, I cannot access Mega from my office - can anyone possibly put it in either dropbox or drive? DISREGARD - I am getting it by tethering off of my shiny S6 Edge!
Click to expand...
Click to collapse
I've now rooted, and flashed the Stock Recovery back to my phone. Deep Sleep is working fine. I'll monitor it over the next few days to see what the battery life is like.
Here is the Stock Recovery for T-Mobile Edge SM-G925T.
https://drive.google.com/file/d/0B3nX3DCjdq6MWS00NHFqRVhOVlk/view?usp=sharing

jamcar said:
Lets says the rooting process borked your phone (or maybe you installed some experimental ROM/kernel, etc.). You can still get into download mode but can't get anything else to work right. Flash back to stock and start again.
See how it's useful?
Click to expand...
Click to collapse
This is exactly the the situation that I am in. I am glad OP posted the stock firmware.
Does anybody know why my phone gets stuck in a boot loop when I try to root. I used the S6 version as was suggested in the root tutorial, everything goes smoothly but then it just bootloops.

Where are the roms at guys I'm trying to build one as soon as I finish fixing my pc

How many here are rooted/running custom ROMS?

I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.

rbtrucking said:
I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.
Click to expand...
Click to collapse
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk

just_visiting said:
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I was always a huge fan of theming! Hmm, perhaps it's time to pull the trigger!

I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.

Just like buzzboy for the most part:
- Theming. (Domination from daveyannihilation on the playstore)
- Ad blocker.
- Custom ROM.
- For pushing theme ready apps to system/data partition.
- Kernel manager app (EXKM)
- Certainly other things I forget right now...
Cheers...

buzzboy said:
I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.
Click to expand...
Click to collapse
Ya, I was looking into that PureNexus rom too.

rbtrucking said:
Ya, I was looking into that PureNexus rom too.
Click to expand...
Click to collapse
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...

pure nexus + elementalx because perfect performance

Forgot about AdBlock and custom kernel. Also few other things that are escaping me at the moment.
Sent from my Pixel XL using Tapatalk

5.1 said:
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...
Click to expand...
Click to collapse
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.

rbtrucking said:
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.
Click to expand...
Click to collapse
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...

5.1 said:
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...
Click to expand...
Click to collapse
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do? it's saying your devices software cab't be checked for corruption please lock the bottloader, then it says visit link on another device g.co/ABH

rbtrucking said:
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do?
Click to expand...
Click to collapse
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?

5.1 said:
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?
Click to expand...
Click to collapse
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop

rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16

rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
No offence here. Just, the method you tried is not up to date... If you took the time to search a little bit before proceeding you would have known that. All infos you need to flash/root/mod are most likely already posted here. All questions have already been answered as well. Use the search function next time or at least, wait for someone to reply :good:
Good luck...
PS: hoping you'll get it fixed. 3am here, I'm off to bed...

TonikJDK said:
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16
Click to expand...
Click to collapse
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb

rbtrucking said:
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb
Click to expand...
Click to collapse
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.

TonikJDK said:
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.
Click to expand...
Click to collapse
Yes I did get it booted but the usb is still not working and it's saying the file in the link you provided is not compatible.

Well it looks like this is a problem with the phone because i cant access anything when I hook it to my mac either.

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light

Question Touchscreen not working

Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.

zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money

persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.

to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful

persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash

I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.

persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong

Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.

persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters

Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).

persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.

Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.

persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.

Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.

Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.

persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.

So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.

persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.

As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.