Delete
Craz Basics said:
Would anyone be willing to test this for me? I replaced the "boot.IMG-ZIMAGE-file" (kernel) in the ENG bootloader with the one that is in the stock one, hopefully making this as stable as stock, and we can root. This I'm hoping will give is the same performance, so no more lag. Anyone who has this (the s7 or s7edge) that doesn't use it as a daily driver for example, and wouldn't be too sad if it bricked, would you mind checking this out?
"dm_verity_signature_checker" is still not in this boot.img, so I believe this should still have write protection off.
Thanks
S7Edge:https://drive.google.com/file/d/0Bygh6W_e2Fo5dnF5RE1sQ2w5X2c/view?usp=drivesdk
Flat S7:https://drive.google.com/file/d/0Bygh6W_e2Fo5Sm1aU3RZdUo3LTQ/view?usp=drivesdk
Just flash in AP and if successful try and root please - I used nougat files so I'd guess to be on nougat, not sure though
Click to expand...
Click to collapse
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.
r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
Click to expand...
Click to collapse
Okay thanks, I'll see if I can update
r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.
Click to expand...
Click to collapse
And this is from g930A, but shouldn't matter should it? Link is updated btw
I'm rooted and have no lag?
I tried flashing with princecomsy Odin and it failed. Some secure boot error came up.
sabresfan said:
I tried flashing with princecomsy Odin and it failed. Some secure boot error came up.
Click to expand...
Click to collapse
That's all I get as well. I can't seem to change anything and still flash. Try and flash with this?:http://glassechidna.com.au/heimdall/
riso123 said:
I'm rooted and have no lag?
Click to expand...
Click to collapse
How so?
I don't see how this would work. Has anyone had anything other than a brick or write fail error?
Craz Basics said:
How so?
Click to expand...
Click to collapse
No idea. I just don't. I'm not sure why rooting would present any lag anyway?
riso123 said:
No idea. I just don't. I'm not sure why rooting would present any lag anyway?
Click to expand...
Click to collapse
The point of this post lol. The ENG boot.img isn't meant for a daily driver. It's for samsung to test things (write protection is off). The kernel I guess wasn't tweaked for performance so it lags. Root doesn't make it lag, the boot.img does.
rlewis312010 said:
I don't see how this would work. Has anyone had anything other than a brick or write fail error?
Click to expand...
Click to collapse
Nope
r3xx3r said:
tried flashing the flat version in PrinceComsy's Odin and got "SECURE CHECK FAIL: boot"
which firmware version is this made from? I am currently on the 930U QE2 fw.
Click to expand...
Click to collapse
Try again through flashfire? Pretty sure you gotta mount system
Craz Basics said:
Try again through flashfire? Pretty sure you gotta mount system
Click to expand...
Click to collapse
Downloading the Chinese rom from your other thread, but I tried to flash the modified s7 edge eng boot (becasue I have the s7 edge) before you edited the post through flashfire and right after it was done secure boot came in and had to stop it. So im pretty sure that in order to flash a boot.img not from samsung that we would have to change the bootloader (which I'm hoping the Chinese rom would do). FIngers crossed! :good:
branstonmorgan said:
Downloading the Chinese rom from your other thread, but I tried to flash the modified s7 edge eng boot (becasue I have the s7 edge) before you edited the post through flashfire and right after it was done secure boot came in and had to stop it. So im pretty sure that in order to flash a boot.img not from samsung that we would have to change the bootloader (which I'm hoping the Chinese rom would do). FIngers crossed! :good:
Click to expand...
Click to collapse
How did secure boot stop it?
Craz Basics said:
How did secure boot stop it?
Click to expand...
Click to collapse
I'm pretty sure flashfire successfully flashed it and then when my device rebooted secure boot told me that the firmware was not authorized and in parenthesis it said boot.img.
branstonmorgan said:
I'm pretty sure flashfire successfully flashed it and then when my device rebooted secure boot told me that the firmware was not authorized and in parenthesis it said boot.img.
Click to expand...
Click to collapse
Okay sweet. Could you flash the stock bootloader (BL file of stock firmware, not Chinese firmware) and see if flashfire can flash it? If it can then we should be able to flash Chinese firmware
Pretty sure you know but mount system
Also, I believe you're downloading the wrong firmware (my fault, I only put flat s7 link up).
It's updated Now, links for both s7 and s7 edge
This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Sent from my SM-G935U using Tapatalk
Root-Maniac said:
This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Click to expand...
Click to collapse
Yeah this is pretty good
Root-Maniac said:
This is getting good. That's one thing that was never tried. Using flash fire to flash the Chinese firmware.
Click to expand...
Click to collapse
Check this out first! https://forum.xda-developers.com/s7...heoretical-variant-bootloader-unlock-t3627286
Related
https://mega.co.nz/#!K9x1USRJ!YnAw7R7_E8Ra0iCPAh4Siy1sNARO1AcoNko9Gxv5YqU
Need anything else - PM me. Original PIT is included. THIS IS NOT ODIN FLASHABLE, but the raw dump files. Includes modems (UEUAMFD).
[Edited for mirrors] Thanks @bmbm
For those who have a problem with downloading from MEGA, I made some mirrors:
http://xda.ftp.sh/i9505G_Full_Dump.rar
http://9505.eu/s4-google_edition/com..._Full_Dump.rar
crc checksums:
Code:
MD5
11865b66c248689bc2694c593ae361b7
SHA1
eb479b98bd4fc0a1f1777168f35f007bf2545e7d
sha256
f7c393e0e76998b54d4c615dd2dbb80db8ca8be0a190c00a590947faf0c79c28
Click to expand...
Click to collapse
donovanbrock said:
https://mega.co.nz/#!K9x1USRJ!YnAw7R7_E8Ra0iCPAh4Siy1sNARO1AcoNko9Gxv5YqU
Need anything else - PM me. Original PIT is included. THIS IS NOT ODIN FLASHABLE, but the raw dump files. Includes modems (UEUAMFD).
Click to expand...
Click to collapse
Any guide to flash the i9505 with this ?
MichelN said:
Any guide to flash the i9505 with this ?
Click to expand...
Click to collapse
That I have no idea. :|
MichelN said:
Any guide to flash the i9505 with this ?
Click to expand...
Click to collapse
It's not possible to flash the bootloader, modem and pit, but everything else should theoretically be directly flashable.
Theshawty said:
It's not possible to flash the bootloader, modem and pit, but everything else should theoretically be directly flashable.
Click to expand...
Click to collapse
theoretically yes. However, the mount points are different in the ROM. if you try and flash directly, you'll get stuck in a softbrick status. At least thats what happens on the 9505G when flashing a stock 9505 ROM.
Most likely gonna have to wait til someone can cook up a ROM based on this dump.
donovanbrock said:
theoretically yes. However, the mount points are different in the ROM. if you try and flash directly, you'll get stuck in a softbrick status. At least thats what happens on the 9505G when flashing a stock 9505 ROM.
Most likely gonna have to wait til someone can cook up a ROM based on this dump.
Click to expand...
Click to collapse
Someone should investigate why the bootloader, pit and modem cannot be flashed. The phones are identical.
donovanbrock said:
if you try and flash directly, you'll get stuck in a softbrick status.
Click to expand...
Click to collapse
Uh? It worked for @Aerys
how do we put these on our S4 I9505?
slikr said:
how do we put these on our S4 I9505?
Click to expand...
Click to collapse
Simply put: We can't.
Theshawty said:
Simply put: We can't.
Click to expand...
Click to collapse
Maybe Aerys can find that out, we have now the full dump.
Maybe write protection enable that we have in odin mode?
Sent from my HTC One using Tapatalk 4 Beta
Wonder what the chances are of flashing this (incluidng the modem) over to the tmobile m919 since its physically the same device as the i9505g.
So this may seem like a stupid question... but how would I be able to flash all of this back to my I9505G?
I did flash the other dumped files from before after I soft bricked mine but I still don't think it's back to 100% stock. I still think the recovery isn't correct (even though I tried flashing the other one). I guess my big question is, how do we go about making this a flashable Odin package?
I'm wondering if there's an issue with the PIT since the last thing I used that screwed something up was the "Quick Flasher" tool for the I9505 (to try to flash CWM recovery)... and I wonder if that screwed up my partitions.
mirror with checksums
For those who have a problem with downloading from MEGA, I made some mirrors:
http://xda.ftp.sh/i9505G_Full_Dump.rar
http://9505.eu/s4-google_edition/complete_dump_i9505G/i9505G_Full_Dump.rar
crc checksums:
Code:
MD5
11865b66c248689bc2694c593ae361b7
SHA1
eb479b98bd4fc0a1f1777168f35f007bf2545e7d
sha256
f7c393e0e76998b54d4c615dd2dbb80db8ca8be0a190c00a590947faf0c79c28
ack154 said:
So this may seem like a stupid question... but how would I be able to flash all of this back to my I9505G?
I did flash the other dumped files from before after I soft bricked mine but I still don't think it's back to 100% stock. I still think the recovery isn't correct (even though I tried flashing the other one). I guess my big question is, how do we go about making this a flashable Odin package?
I'm wondering if there's an issue with the PIT since the last thing I used that screwed something up was the "Quick Flasher" tool for the I9505 (to try to flash CWM recovery)... and I wonder if that screwed up my partitions.
Click to expand...
Click to collapse
So I'm quoting myself here, but I'm trying to figure out what went wrong originally...
Like I said, I used the Quick Flasher tool to attempt to flash CWM recovery, but it looks like that may have tried to flash it to the wrong partition. Looking at the QF utility, it tried to flash the Recovery to mmcblk0p21... but according to Donovan's other thread from the first system dump, p21 is apparently where the Boot partition is, not Recovery. So my partitions may still be screwed.
My head tells me that flashing this PIT with Odin and then flashing the System, Recovery, and Boot included here would get me back to normal. Thoughts??
ack154 said:
So I'm quoting myself here, but I'm trying to figure out what went wrong originally...
Like I said, I used the Quick Flasher tool to attempt to flash CWM recovery, but it looks like that may have tried to flash it to the wrong partition. Looking at the QF utility, it tried to flash the Recovery to mmcblk0p21... but according to Donovan's other thread from the first system dump, p21 is apparently where the Boot partition is, not Recovery. So my partitions may still be screwed.
My head tells me that flashing this PIT with Odin and then flashing the System, Recovery, and Boot included here would get me back to normal. Thoughts??
Click to expand...
Click to collapse
ack - weren't you able to restore with my other dump? if so, this will be no different. only addition to these files is the PIT and all the modems.
donovanbrock said:
ack - weren't you able to restore with my other dump? if so, this will be no different. only addition to these files is the PIT and all the modems.
Click to expand...
Click to collapse
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
ack154 said:
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
Click to expand...
Click to collapse
Thats the stock recovery. You're good to go brudda.
ack154 said:
I did... but my gut still tells me something's messed up (part of that is paranoia after soft bricking I think). The other part is that I still think my recovery is wrong. I'm pretty sure I booted into the stock recovery very early on to have a look and it didn't look like this (what mine is now)...
Click to expand...
Click to collapse
Your fine buddy :good:
donovanbrock said:
Thats the stock recovery. You're good to go brudda.
Click to expand...
Click to collapse
O Rly? That makes things a bit better then... thank you.
Still downloaded to save though...
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Obagleyfreer said:
Chainfire has updated his CF auto root for the annoying new MH8 firmware with new bootloader!
Yay we can now root our new firmware.
Here's his Google plus page for CF Auto Root download
https://plus.google.com/+Chainfire/posts/5ggu7naWtaW
Thanks Chainfire, you're the man!!!
Click to expand...
Click to collapse
Pointless thread. Everyone knows to find chainfires thread.
boterkaaseneieren said:
Pointless thread. Everyone knows to find chainfires thread.
Click to expand...
Click to collapse
Well yes, but still good to know and please don't be offended by his comment. That kind of comment is indeed pointless! We're all here to learn and have fun, keep this kind of comment to yourself please...
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
can we downgrade with this
pnr2020 said:
can we downgrade with this
Click to expand...
Click to collapse
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
donalgodon said:
Basically, looks like Samsung is pulling the same sort of crap they pulled with the S3 bootloader to prevent status resets under the false pretense of security improvements.
Click to expand...
Click to collapse
Yeah that's what I thought too.
Hopefully we can fix it in time
Obagleyfreer said:
No you can't
Once you flash it you're stuck on this firmware.
I found that out the hard way
Click to expand...
Click to collapse
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
pnr2020 said:
oh no my battery drained 30% over night phone laggy so i will not be able to put custom rom on phone anymore will we ever be able to downgrade or are we stuck
Click to expand...
Click to collapse
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
DjeMBeY said:
Try here and let us know please
http://forum.xda-developers.com/showthread.php?t=2401685 or http://forum.xda-developers.com/showthread.php?t=2354122
Click to expand...
Click to collapse
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Obagleyfreer said:
I'm really not sure.
Hopefully there will be a fix I don't know what I would do with a phone I cant run CM on, I'm so p**ssed off right now at this.
Does anyone know if we flash an older firmware in Odin with a .pit file would that fix things?
Click to expand...
Click to collapse
Flashing older firmware with PIT didn't work for me.
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
Let me know if it works for you - unfortunately didn't for me.
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Click to expand...
Click to collapse
Any chance of a step-by-step guide on how you did this? Especially what you deleted. Also is there any chance it would work if you wanted to go back to an older stock ROM? Reason I want/need stock is because I use the Bluetooth RSAP profile - unless anyone knows if this is included in the CM ROMS...
If you boot into recovery does it have any of the KNOX lines or is the recovery with CM different to stock? If so perhaps it would be possible to do something like (assuming I've understood correctly) : Root Phone -> Install CM -> Un CM the phone with a stock ROM?
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
please put up a step by step guide to what you did
pnr2020 said:
give me instructions on how to flash firmware with pit file and i will try i got insurance on my phone so dont care if it goes wrong i just need to downgrade
Click to expand...
Click to collapse
pnr2020 said:
will try it now and let you know asap oh my god 2hrs to download files i hate hotfile
Click to expand...
Click to collapse
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
@DjeMBeY
thanks for bootloader and i added here that same bootloader but for Odin cread as tar file
Zippyshare ---> http://www28.zippyshare.com/v/62712373/file.html
no work
DjeMBeY said:
I've prepared special ZIP, it should (in theory) downgrade bootloaders
NOT TESTED YET!!!! IT CAN BRICK YOUR PHONE!!
Instructions:
1. Download and copy ZIP to SD/ExtSD card
2. Check if you have BusyBox in /sbin, if not, copy and paste it from /xbin
3. Reboot into Custom Recovery (CWM/TWRP etc)
4. Install ZIP
5. Reboot
Please report how it goes
Click to expand...
Click to collapse
Im tested,and not working for me. Im use kt-sgs4 kernel with mh8 rom, with root, busybox and the system is ok...but the bootloader is nt cool, i cant intall any custom rom. No voice, and cant call. Odin .tar file no working nand flash fail...
I think install with odin mh1 rom, and install philztouch recovery and intall bootloader recovery...its fine?Thanx
Obagleyfreer said:
I just manged to get back to CM and my SElinux status back to permisive from MH8
I deleted a load of bloat from system app(knox is probably what helped) after rooting.
Then flashed official clockworkmod recovery image file using SGS4 Flasher.
Then booted to recovery and formated system (it wasnt mounted!!) cache and data and restored my backup
Im sooooo happy!
Sent from my GT-I9505 whilst taking a s**t
Click to expand...
Click to collapse
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
donalgodon said:
That info is going to come in handy to some users who bounce back and forth from Stock to CM.
Thankfully, I had not been tempted to do so and still have the old bootloader. Never going back to stock myself.
Click to expand...
Click to collapse
Hopefully it helps at least a couple of people.
The problem comes when you need to send your phone back to Samsung for warranty purposes.
Even if you have old firmware, reset flash counter etc. I can bet my bottom dollar when it returns from Samsung they would have flashed the new firmware and new bootloader to your device. They are great like that!!
Does it exist? Is there a full Nougat download (not just the OTA) for the K1 available that is stock and rooted?
Sent from my SM-N910T using Tapatalk
https://forum.xda-developers.com/sh...imized-stock-shield-tablet-k1-t3437791/page36
this is nothing for you?
wiQbold said:
https://forum.xda-developers.com/sh...imized-stock-shield-tablet-k1-t3437791/page36
this is nothing for you?
Click to expand...
Click to collapse
No, unfortunately that ROM is not rooted...just stock.
SJMarty said:
No, unfortunately that ROM is not rooted...just stock.
Click to expand...
Click to collapse
I assume you have TWRP since you need that to flash a ROM. So how hard is it to flash SuperSU immediately afterwards?
edisso10018 said:
I assume you have TWRP since you need that to flash a ROM. So how hard is it to flash SuperSU immediately afterwards?
Click to expand...
Click to collapse
The flashing part is not hard at all. The "working" part after the flash is where I'm hitting a wall.
I am having an issue where flashing SuperSU in SYSTEM mode does not work with Nougat. My tablet stalls at the boot screen. It works in SYSTEMLESS mode but I do not want to use SYSTEMLESS as some of my apps (for example, Titanium) do not work properly. This is why I was looking for a stock rooted Nougat ROM.
Here is a link to my first post in the other thread I mentioned. Please chime in if you have any suggestions. I'm pretty much out of ideas.
SJMarty said:
The flashing part is not hard at all. The "working" part after the flash is where I'm hitting a wall.
I am having an issue where flashing SuperSU in SYSTEM mode does not work with Nougat. My tablet stalls at the boot screen. It works in SYSTEMLESS mode but I do not want to use SYSTEMLESS as some of my apps (for example, Titanium) do not work properly. This is why I was looking for a stock rooted Nougat ROM.
Here is a link to my first post in the other thread I mentioned. Please chime in if you have any suggestions. I'm pretty much out of ideas.
Click to expand...
Click to collapse
I use CF-Autoroot for almost a year now with MM und N. You don't even need TWRP for it to work. And it always worked!
fastboot boot CF-Auto-Root-shieldtablet-wxnawf-shieldtablet.img
That's all.
Thank you
edisso10018 said:
I use CF-Autoroot for almost a year now with MM und N. You don't even need TWRP for it to work. And it always worked!
fastboot boot CF-Auto-Root-shieldtablet-wxnawf-shieldtablet.img
That's all.
Click to expand...
Click to collapse
I was having a hell of time getting recovery to work right on this tablet. Wont go in to details. Just tired. Saw your post and thought why not....Worked like a charm. I am now rooted and all is well. CF worked great....Now on to flashing twrp ; }
According to the Verizon Galaxy S5 Update Page:
Android® security patches and bug fixes.
Resolved a ring-back tone issue on calls to non-Verizon phones.
Fixed an issue where some users reported difficulty making calls to non-Verizon customers.
Click to expand...
Click to collapse
The security patch included is (most likely) the July one, since Samsung also just released a new software update to international models which includes the July security patch and Verizon has been updating the "Galaxy S" series phones with the July update over the past few weeks.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME_No_Aboot.tar.md5.zip
Appreciate that, but how do you get the Odin firmware file out of curiosity?
drewcu said:
Appreciate that, but how do you get the Odin firmware file out of curiosity?
Click to expand...
Click to collapse
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
drewcu said:
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
Click to expand...
Click to collapse
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Dudash said:
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Click to expand...
Click to collapse
Is this flashable with Odin only or possibly need to already be on a specific kernal? I have tried on two S5900V's through TWRP and both result in a failure message. Both are on jkruse de-bloated MM rom at the moment.
Kaliaila said:
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
Click to expand...
Click to collapse
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Odd. It works for me.
Sent from my SM-G900V using Tapatalk
Since no one wanted to chime in and help me out in my post, you need to unzip the file and load the md5 into Odin's AP slot and flash it. Then let the phone do its thing and flash the latest TWRP with odin after. Then go back into TWRP and flash supersu to gain root again. Trying to flash right within TWRP is not an option, not sure why its not explained.
So this update wont "factory reset" my device?
AWESOME1092387456 said:
So this update wont "factory reset" my device?
Click to expand...
Click to collapse
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
stuck on Verizon boot screen
After the update via OTA, my aunt's phone has been stuck on Verizon boot screen. Tried booting into safe mode, with same result. Any ideas on how not to lose all her data? Thanks!
This sucks I wanna download this so bad but my computer is down smdh is it possible someone can make and ota update zip file for me so can flash this through stock recovery on my phone ?
Sent from my SM-G900V using Tapatalk
I guess no one knows how to do it huh smdh
Sent from my SM-G900V using Tapatalk
Rumsfield said:
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
Click to expand...
Click to collapse
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
mastertech007 said:
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
Click to expand...
Click to collapse
I always flash super su and whatever else I need in recovery after I've flashed the rom so I cant give you a definitive answer. Both phones did upgrade without data loss and now advanced calling/wifi calling actually work now which is why I flashed in the first place.
Working?
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
JasonD1180 said:
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
Click to expand...
Click to collapse
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
JasonD1180 said:
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
Click to expand...
Click to collapse
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Rumsfield said:
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Click to expand...
Click to collapse
Ive not had twrp or root on this device but it went from saying vzw official binary to samsung original. Will i be able to root as long as twrp flashes?
Is there a stock RUU to get me back to stock everything? I looked but only found one for the unlocked version
AsuraDas said:
Is there a stock RUU to get me back to stock everything? I looked but only found one for the unlocked version
Click to expand...
Click to collapse
There's not one released yet. And most of us flashed other things that made it difficult to update. Later I will upload the patched system. Img and firmware zip. So others can have Oreo if they aren't able to update. Only downside is we lose twrp until I make one for 8.0 or someone else does.
twinnfamous said:
There's not one released yet. And most of us flashed other things that made it difficult to update. Later I will upload the patched system. Img and firmware zip. So others can have Oreo if they aren't able to update. Only downside is we lose twrp until I make one for 8.0 or someone else does.
Click to expand...
Click to collapse
Right now the phone is completely stock. Would flashing stock recovery allow me to upgrade to Oreo?
twinnfamous said:
There's not one released yet. And most of us flashed other things that made it difficult to update. Later I will upload the patched system. Img and firmware zip. So others can have Oreo if they aren't able to update. Only downside is we lose twrp until I make one for 8.0 or someone else does.
Click to expand...
Click to collapse
Right now the phone is completely stock. Would flashing stock recovery allow me to upgrade to Oreo?
AsuraDas said:
Right now the phone is completely stock. Would flashing stock recovery allow me to upgrade to Oreo?
Click to expand...
Click to collapse
It should let u
Do you know where I could get a stock recovery?
AsuraDas said:
Do you know where I could get a stock recovery?
Click to expand...
Click to collapse
There's the t mobile one linked in the twrp thread in the dev forum section. Twinn uploaded it
AsuraDas said:
Is there a stock RUU to get me back to stock everything? I looked but only found one for the unlocked version
Click to expand...
Click to collapse
there is now
http://dl3.htc.com/application/RUU_OCEAN_LIFE_UL_O80_SENSE90GP_MR_TMOUS_2.15.531.6.exe
twinnfamous said:
there is now
http://dl3.htc.com/application/RUU_OCEAN_LIFE_UL_O80_SENSE90GP_MR_TMOUS_2.15.531.6.exe
Click to expand...
Click to collapse
Nice.
twinnfamous said:
there is now
http://dl3.htc.com/application/RUU_OCEAN_LIFE_UL_O80_SENSE90GP_MR_TMOUS_2.15.531.6.exe
Click to expand...
Click to collapse
A big TTHHHAANNNKKK yyooouuu Twinnfamous. I made a big mistake & relived the bootloader & this definitely pull me out the tight problem I was in when my phone bricked
Anyone know where I can find the RUU now? That ^^ link is dead, and I'm finding it impossible to find it via google/duckduckgo