Database Users

[TUT] T-Mobile UK Upgrading/root/lag fix and De-branding.

I take no credit for any of this work. I have added it all to one post to help make life a little easier for those who are wanting help in getting rid of any need of waiting for T-Mobile to release any firmware again. Credits will be added to all post at the bottom of the respective page. This TUT will also work with other networks.
If you have 3 Button Download mode you can jump to page 2.
Post 1: 3 Button Download Mode.
Post 2: Upgrade to Froyo.
Post 3: Rooting and lag fix.
Post 4: De-Branding.
3 Button Download.
I have run out of time to add this today i will finish off tomorrow. For now follow this http://forum.xda-developers.com/showthread.php?t=821698

Upgrade to Froyo.
PRELIMINARY NOTE:
[WARNING!] Do Not flash Any ROM (firmware) until you can get the 3 buttons DOWNLOAD MODE working, even with this Kies trick.
If you want to test the 3 buttons download mode then notice that you can switch back to normal mode by pulling the battery out and then back in. At the next boot the phone will be back in normal mode.
LAGFIX USERS:
[WARNING!] Remember to disable lagfix before to update.
This will avoid filesystem errors that may occurs at the boot of the new flashed firmware.
INSTRUCTIONS:
1) Download latest Kies Registry Patcher, tool is attachment. Note: It require Microsoft .NET Framework 3.5 or later version.
2) Update Kies to 1.5.3.10103.102.
3) Launch Kies Registry Patcher; If you patched the dll in the past with an older version of the patcher then be sure to launch new release as administrator since it have to revert the dll to the original version as the patch isn't needed anymore (Right click on application > Run as Administrator).
4) Launch Kies and connect your phone; Wait for Kies to recognize it properly.
5) You have 2 possibilities now:
5a) Drop down the combo-box "Spoof Product Code as" and select the wanted one. It should automatically fill the "Spoof Software Revision as" textbox with the needed data necessary to find your update.
This feature was added in order to give all the opportunity to use the needed product code. (Special thanks to MCOGW that shared with me his database of product codes/sw revisions).
The label above will be completed with the country related to the chosen product code.
5b) From patcher select:
File > Load Backup
Open the backup that you want to use (e.g. kies-backup-XEU.xml if you want to spoof your phone as XEU, or if your phone is XEU yet and you want to flash it again).
6) From patcher answer "YES" in order to apply the registry update.
7) From Kies you can now update as normal.
Remeber that this patch will remain ACTIVE until you set "Enable Spoof" field to False!
It's not a problem but ater you update the phone it's suggested to put that value to false so the patch become inactive.
Full Post: http://forum.xda-developers.com/showthread.php?t=835628
Credits:
Nodial

Root/Lag fix.
Download the attached files, place them on your memory card and install them on your handset by navigating to them in My Files app and click on them to install.
Once installed run z4root first, then run OCLF.2.3.0 and except Superuser permissions.
Inside OCLF2.0 application click on the following:
1st: Install EXT2 Tools (follow instructions)
2nd OneClickLagFix V2.2+ (follow instructions)
Congrats you now are rooted and have applied a lag fix.
Full Post z4root: http://forum.xda-developers.com/showthread.php?t=833953&highlight=Z4root
Full Post OCLF: http://forum.xda-developers.com/showthread.php?t=833953&highlight=oclf
Credits:
RyanZA
z4ziggy
Sebastian Krahmer's rageagainstthecage

De-branding.
To truly de-brand you need to get rid of the branded product code and have the correct CSC. Follow the steps below.
[WARNING] Make a full backup of your \efs folder just in case you go wrong or any errors occur.
You will need to be rooted and have the root explorer app installed from the market.
Copy your \efs folder to your pc and open nv_data.bin with note pad, Search for TMU and replace with XEU. If you can not find TMU try KOR. Save the file and and copy it back to your \efs folder on your handset. Delete the nv-data.md5 file off the handset and reboot. repeat steps with the nv_data.bak file.
Once completed change your CSC to XEU by typing *#272*(yourimei)# and click on XEU.
Now when Samsung release a new update you will get it straight away.
Sorry if I have missed any people in the credits. Please post with name and post number if poeple need to be added.

Hey I want to get Froyo, tired of waiting for T-mobile but i dont have the 3 button combo on my phone so is there any safe way of doing this or fixing 3 button....?

hey n1kon nice idear b4 barry shuts down the forum on T,M
have you used the root/lag fix ??

Great post, tired of waiting for t-mobile to release 2.2
Thanks.

n1kon said:
Upgrade to Froyo.
5a) Drop down the combo-box "Spoof Product Code as" and select the wanted one. It should automatically fill the "Spoof Software Revision as" textbox with the needed data necessary to find your update.
This feature was added in order to give all the opportunity to use the needed product code. (Special thanks to MCOGW that shared with me his database of product codes/sw revisions).
The label above will be completed with the country related to the chosen product code.
6) From patcher answer "YES" in order to apply the registry update.
7) From Kies you can now update as normal.
Credits:
Nodial
Click to expand...
Click to collapse
I'm rather new to all this and before I attempt to update my T-Mobile Galaxy S using the described 5(a) option, I would appreciate some advice, please.
I understand the instructions right up to the end of para 5(a) but at this point there is no "yes" button to click. However, there is a "Read Registry" button. Presumably I click this and will then be asked the click a "Yes" button to proceed with the update.
What then happens? What should I expect to see on the PC and on my phone?
Some step-by-step instructions would be much appreciated to boost my confidence!
P.S. I've already checked that I have the three-button system restore active on my phone.

Ain't done no root because I wil be ****ed if it bricks and I don't know no way of rooting without restore mode.
Sent from my GT-I9000 using XDA App

I've been running 2.2 on my T-Mobile UK Galaxy S for some time, but have never used or even installed Kies. I just installed the relevant USB drivers, then flashed a ROM I've downloaded from mirrors linked here with Odin3 (I've always had download mode working properly). Currently I'm using JPO with SpeedMod Kernel K10H, which provides root.

Hi i upgraded via the kies registry way all works well apart from i cant find where to switch between 2g and 3g. It was in mobile networks on 2.1 but its not there now also having issues using myplayer and beebplayer once again they worked in 2.1 but not on froyo atm. other then that alss good

I used this guide to fix the 3 button combo issues - http://forum.xda-developers.com/showthread.php?t=785201

It still is in there 2g is gsm
Sent from my GT-I9000 using Tapatalk

blazevxi said:
I used this guide to fix the 3 button combo issues - http://forum.xda-developers.com/showthread.php?t=785201
Click to expand...
Click to collapse
Im looking into the safest one to use but am at work right now
Sent from my GT-I9000 using Tapatalk

I use both root and lag fix
Sent from my GT-I9000 using Tapatalk

Surely the easiest way to debrand is to just flash a new ROM via ODIN?

Is that way safe, dont want to brick my phone?

-Elvin- said:
Is that way safe, dont want to brick my phone?
Click to expand...
Click to collapse
I've done a branded Orange and Vodafone by flashing XXJPO via ODIN.
It's very hard to totally brick your phone with ODIN, but there can be complications.
Before you do anything, make sure you have working 3br and download mode. If you don't have it, I don't recommened using Kies or ODIN.

Rawat said:
Surely the easiest way to debrand is to just flash a new ROM via ODIN?
Click to expand...
Click to collapse
Flashing with odin will not allow u to update with kies when the next release is issued as your product will stay the same and your software versions will be wrong so you will need to use odin again. Plus if odin is used wrong it can brick you phone
Sent from my GT-I9000 using Tapatalk

n1kon said:
Flashing with odin will not allow u to update with kies when the next release is issued as your product will stay the same and your software versions will be wrong so you will need to use odin again. Plus if odin is used wrong it can brick you phone
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Nope, if you flash a full ROM via ODIN, including the CSC, it'll work fine. It'll even work on kies (although i don't know why anyone would want to do that )
Kies can also brick your phone >_>;

[GUIDE] Not quite newbie guide for moving to 5.1.1

In one of the development threads a request was made for a step-by-step for transitioning to a 5.1.1 ROM from an earlier version and an example was given from another device. Well I modified the example to make it apply to the Sprint Note 4.
All files needed are linked at the end of this post. This is my first attempt at a guide, so any suggestions for improvement will be gladly accepted.
Prerequisites:
1 - Latest Samsung-USB-Drivers (1.5.55.0) installed
2 - Odin v3.10.6 installed
3 - Two files either on an extsdcard in the phone or on your PC for sideloading through adb:
UBERWIPE.zip (Only for use if you have an extsdcard), BETA-SuperSU-v2.49.zip
**** - If you do not have an extsdcard you will need adb installed on your PC in order to get the SuperSU
file onto your phone for flashing.
Loading Stock OG5:
1 – Run Odin v3.10.6 as administrator
2 – Load the appropriate tar in the AP slot
--If you are on OB7 Bootloader and wish to keep it load Hybrid_OB7sbl_SPT_N910PVPU4COG5.tar
--For complete OG5 upgrade load N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5.tar.md5
3 – Click on the ‘Options’ tab avove the Log window
4 – Uncheck the reboot option in Odin.
5 - Click on the ‘Log’ tab above the Log window
6 – Phone off. Enter download mode by holding down Vol Down, Home and Power to first screen presence
7 – Enter download mode by moving cursor – Vol Up.
8 – Plug phone into PC. Drivers are already installed so look for Connection in Odin.
9 – Start Odin on good battery charge. Don’t touch phone until complete, 5-10min.
10 – Close Odin, disconnect cable from phone, turn phone off and remove battery.
Removing the battery is the only way to turn it off at this point. Not exactly true but that's all you need to know. It's the best way.
Rooting via TWRP touch recovery:
1 – Put battery back in and enter download mode as above.
2 – Run Odin as administrator and load twrp-2.8.7.0-trltespr.img.tar in the AP slot
3 – Click on the ‘Options’ tab avove the Log window
4 – Uncheck the reboot option in Odin.
5 - Click on the ‘Log’ tab above the Log window
6 – Plug in phone to PC and watch for Odin to establish connection
7 – Start Odin. It will be quick.
8 – When done close Odin. Unplug phone, Power Down and remove battery.
9 – Replace battery and enter Recovery Mode by holding Vol Up, Home and Power to first screen presence
10 – Let TWRP load
11 – If you don’t have an extsdcard then navigate to Advanced > ADB Sideload and use adb to transfer BETA-SuperSU-v2.49.zip from your PC to your phone
12 – Navigate back to the main screen the to Install and choose the location of the SuperSU file
13 – After flashing BETA-SuperSU-v2.49.zip choose Wipe Dalvik/Cache option.
14 - When wipe is completed you have two choices:
--Choose reboot in which case you will have a rooted stock system
--Wipe the current system and install a custom ROM (see below)
If you choose to flash a custom ROM:
1 - Wipe the current system
--If you have and extsdcard with UBERWIPE.zip on it all you need to do is install that zip and when the
recovery automatically reboots your phone will be clean and ready for a new ROM
--If you don’t have an extsdcard I recommend the following:
A - Navigate to the Wipe submenu
B - Perfom a factory reset 3 times
C - Choose format data, type yes on the following screen then enter. Do this 3 times
D - Navigate back to the Wipe submenu and choose Advanced. Then choose everything except extsdcard
and execute. Do this 3 times.
(At this point if you don’t have an extsdcard you will need to navigate Advanced > ADB Sideload and tansfer the ROM of your choice from your PC to your phone)
2 - Navigate to Install and choose the location of your ROM file
3 - When the flash has completed choose the Wipe Dalvik/Cache button
(At this point I always flash the Beta-SuperSU file and wipe Dalvik/cache again, but I’m just OCD)
4 - Reboot the phone and LET IT SIT AT LEAST 15 MINUTES before you touch it to set anything up!!!
Here is a list of the files and executables you'll be working with: (Links either lead to thread of the file on XDA or direct download from my person Google Drive account)
Samsung-Usb-Driver-v1.5.55.0.exe
Odin3_v3.10.6.zip (3.10.7 is avaiable now as well)
Either:
HYBRID_OB7sbl_SPT_N910PVPU4COG5.tar
- or -
N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5.tar.md5
twrp-2.8.7.0-trltespr.img.tar (unless a newer version has been released)
Sprint_Hybrid-X_3.0_N910PVPU4COG5_Deodexed,zip Or any other custom 5.1.1 ROM
BETA-SuperSU-v2.49.zip
Optional -
UBERWIPE.zip by:millerboy3
MD5_and_SHA_Checksum_Utility.exe (I personally never use it unless I run into serious problems after multiple downloads)

thank you so much worked like a charm

Good job wolf. Even though the rom OP's have the needed info some people get a little overwhelmed by the amount of info so it will be helpful to many to have a step by step. Good job.

Thanks for this thread. However, it did not work for me. Only way I could get to OG5 was by Odin to N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar and taking the OTA to OG5. I was just running stock rooted with the newest TWRP . Followed everything to a T. Maybe today just isn't my day.
MACKIE

Which file did you use to try and Odin to OG5? The Hybrid with OB7 bootloader or the pure stock OG5?
Sent from my SM-N910P using XDA Premium HD app

DreamingWolf said:
Which file did you use to try and Odin to OG5? The Hybrid with OB7 bootloader or the pure stock OG5?
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
Tried both.
Sent from my SM-N910P using Tapatalk

00_MACKIE_00 said:
Tried both.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mackie, exactly which rom do you want to flash?
Post a screenshot of the last 7 entries in "about device" in settings.

@00_MACKIE_00
Don't mean this to be an inquisition but what failures did you get with Odin or boot or function when following this tut?
Both tars not getting you there is an answer but details, please. TIA. Glad you managed on your own. Not doubting you but curious enough to ask.
Sent from my SM-N910P using Tapatalk

samep said:
@00_MACKIE_00
Don't mean this to be an inquisition but what failures did you get with Odin or boot or function when following this tut?
Both tars not getting you there is an answer but details, please. TIA. Glad you managed on your own. Not doubting you but curious enough to ask.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I'm curious as well.

Thanks people who have either replied in this thread or messaged me.
The erorrs I was having was with Odin. It would not write at all for either Hybrid_OB7sbl_SPT_N910PVPU4COG5.tar or N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5.tar.md5. In fact, Odin would get an error within about 5 seconds of pushing start. Again, the only way to get around it was to Odin back to OF5 and taking the OTA OG5. Once I was on OG5, I was able to flash TWRP in Odin and also install the ROM of my choice with no issues.
For what its worth, tried 3 different revisions of Odin. I used 3.10.6 for TWRP . Seems funny to me I could Odin OF5 but not OG5 . This device is a replacement I got from Assurion about a week after the Note 4's were no longer being sold. It came with OF5 .
Have a good day all!
MACKIE

00_MACKIE_00 said:
Thanks people who have either replied in this thread or messaged me.
The erorrs I was having was with Odin. It would not write at all for either Hybrid_OB7sbl_SPT_N910PVPU4COG5.tar or N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5.tar.md5. In fact, Odin would get an error within about 5 seconds of pushing start. Again, the only way to get around it was to Odin back to OF5 and taking the OTA OG5. Once I was on OG5, I was able to flash TWRP in Odin and also install the ROM of my choice with no issues.
For what its worth, tried 3 different revisions of Odin. I used 3.10.6 for TWRP . Seems funny to me I could Odin OF5 but not OG5 . This device is a replacement I got from Assurion about a week after the Note 4's were no longer being sold. It came with OF5 .
Have a good day all!
MACKIE
Click to expand...
Click to collapse
Well u should have done your reading about your bootloader. You're stuck on og5 only roms now. Bottom line, I treat my note 4 like it's irreplaceable............ Because it is.
**** the note 5, and **** replacements

ryanalan82 said:
Well u should have done your reading about your bootloader. You're stuck on og5 only roms now. Bottom line, I treat my note 4 like it's irreplaceable............ Because it is.
**** the note 5, and **** replacements
Click to expand...
Click to collapse
Is there a need to troll my post? I can assure you I have been in this since you were in diapers. Find another thread to post useless information.
MACKIE
Sent from my SM-N910P using Tapatalk

00_MACKIE_00 said:
Is there a need to troll my post? I can assure you I have been in this since you were in diapers. Find another thread to post useless information.
MACKIE
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mackie, check out this thread :
http://forum.xda-developers.com/showthread.php?t=3185274

New Firmware 5.0.0-RU1.1.99

You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!

Thanks for that muchly dude, hadn't checked that for a while.
Update seems to be stability improvements, power efficiency improvements and some yotamirror and panel improvements and features.
Its not 5.1, but it's an update, I'll take it.
And yeah, super glad moved to the RU ROM. Backing up now, will OTA flash update once that's done. SuperSU has been flashable everytime after an update so far so fingers crossed.

All up and running .
I was rooted, running RU 1.87 with TWRP - phone handled it all just fine - downloaded OTA, pressed install - it went to TWRP > flashed stock recovery back over itself > rebooted and installed.
Phone booted up, all working fine. Lost root - simple reboot and flash the SU.zip had sitting there from the last update. Cache and Dalvik wiped for good measure.
Reboot and all is well and back to normal but with a few improvements, lovely.
About as easy as it's even been done really.
Hope everyone else gets to enjoy the update through similarly smooth procedures .

Yeah, I ended up doing a fresh installation plus rooting, everything smooth. I'm never too sure what an update leaves behind.
It's really a great device, hopefully they'll keep updating things for a while. Of course version 6.0 would be welcomed... Apparently, by the numbering they use, next step would be either 1.2.xx with Android 5.1 or 2.x.xx with 6.0. Let's see.

Fair play, I toyed with idea of it, but was fresh from last install and honestly don't have the time to set everything up again.
My hope is they take all their good ideas from this and can at least join someone else in making a great device.
Saw a working bendy phone the other day, lets you turn pages on reading app by bending corner as you would a book etc. I thought if that could be combined with yota tech, then you have damn near the perfect tablet.
Honestly I don't think we'll get 5.1, let alone 6.0. They're refining their ideas in prep for Yotaphone 3, that and the possible tablet are their main focus right now.
Interestingly, the update flashed it's stock recovery over twrp - someone prepared for the possibility of root owners this time around. So they are still paying attention .

So any idea what's the difference between the EU and the RU rom? I mean there has to be some reason they are two separate roms.

To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.

Jeopardy said:
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Click to expand...
Click to collapse
FYI the difference is essentially the product package configuration (app bundles that are pre-loaded) but there are also some differences between the resources used for the stock apps. One in particular (my personal fav ) is the dialler - the RU variant includes cyrillic characters regardless of language/locale setting (feature). The EU will give you a regular english-only dialler if you're using english locale settings

Vuche said:
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Click to expand...
Click to collapse
Ho to flash the update zip file? I m stuck on 4.4.3...

does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos

Does the new update solve the keyboard sensitivity issue??

zute333 said:
numerous guides and how to's in this forum and across XDA, as well as google.
download fastboot + adb > boot to download mode > flash twrp via fastboot commands > boot into twrp > flash zip.
There's obviously more to it than that, up to you to do the research.
Click to expand...
Click to collapse
i'm using this post as a minimalistic guide for myself (so i keep it up with my "discoveries" )
and ofc for been helped by everyone who wants to help me because i am completely new to android world cause this is my first android phone ever!
so.. let's get started!
i downloaded [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
version 1.4.3 doesnt works for me so i downloaded the 1.3 as suggested and worked.
then i enabled the download mode following the procedure:
Turn off the phone, then press and hold the volume down key + the power key at the same time. This should boot you into download mode.
Click to expand...
Click to collapse
note: phone MUST be disconnected form pc to be turned off.
now..
*does install twrp invalidate warranty?
EDIT: answer is YES cause of
TWRP 2.8.5.0 YotaPhone 2 recovery image said:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem
Click to expand...
Click to collapse
*is installing TWRP a mandatory step?
EDIT: the answer is NO. it seems that the mandatory part is to unlock the bootloader (the bad part for the warranty.. and that can erase ur data..) and this can be done following this guide How to Install TWRP Recovery on YotaPhone 2 untill point 6 included - which i am reporting here for easy of use.
How to Install TWRP Recovery on YotaPhone 2 said:
How to Flash TWRP Recovery on YotaPhone 2
1 - Setup ADB and Fastboot on your Windows PC.
2 - Enable USB debugging from developer options on your YotaPhone 2.
3 - Connect it to PC with a USB cable, if it asks for debugging authorization, permit it.
4 - Go to the folder where you downloaded the TWRP recovery image from the download link above on your PC and open a command window inside that folder by doing “Shift + Right click” on any empty white space inside the folder, then select “Open command window here”.
5 - (Skip this if your bootloader is already unlocked) Now to unlock the bootloader, type in the following command:
└ Beware that unlocking the bootloader may wipe your phone’s data. Make sure to backup first before proceeding.
adb reboot bootloader
Click to expand...
Click to collapse
└ This will reboot your phone to bootloader mode
fastboot oem unlock
Click to expand...
Click to collapse
└ This will unlock bootloader on your device.
6 - Now if your phone has rebooted and is no longer in the bootloader mode, then boot it back into bootloader mode with the “adb reboot bootloader” command.
Click to expand...
Click to collapse
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
error: cannot open 'firmware/emnc_appsboot.mbn'
error: cannot open 'firmware/boot.img'
error: cannot open 'firmware/system.img'
error: cannot open 'firmware/recovery.img'
error: cannot open 'firmware/cache.img'
error: cannot open 'firmware/radio/NON-HLOS.bin'
error: cannot open 'firmware/radio/sbli.mbn'
error: cannot open 'firmware/radio/rpm.mbn'
error: cannot open 'firmware/radio/tz.mbn'
error: cannot open 'firmware/enmc_appsboots.mbn'
Would you like to flash userdata[Y/N]:
Click to expand...
Click to collapse
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx

Hello guys, I downloaded Lollipop from the ftp but installation fails: no MD5 file found!
I downloaded all russian versions and also the 1.6 EU version... but no way I always get this error.
I'm using TWRP 2.8.5, I guess the last one, and in the tutorials I see this version...
Does anyone know how to solve? :crying:

giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
The info is described in various posts across the yotaphone forum. Are you rooted? If not then there also many many guides across the internet for that.
Not walking you through the whole process, sorry. We all had to learn, once you do it's all much easier.

It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status
in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.

Melting Blaze said:
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Click to expand...
Click to collapse
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167

TKPL said:
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
Click to expand...
Click to collapse
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
JAMMANDROID said:
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Click to expand...
Click to collapse
yeah. is exactly what i did, but super panicing like a chicken without head

Melting Blaze said:
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
yeah. is exactly what i did, but super panicing like a chicken without head
Click to expand...
Click to collapse
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening

giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
Hi, download YotaFlasher, it permits you to download and flash firmwares in an easy way, and you don't need to know any shell command
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
TKPL said:
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
Click to expand...
Click to collapse
Hello! I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB :laugh:
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.

I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
Click to expand...
Click to collapse
seems that is the same for a lot of people if not everyone..
cause of this problem i am using this app gravity screen on/off.
it halves the problem cause now i have no problem for the amoled. and for problem i mean use the pwer button instead of simply swipe.
for the e-ink panel i still have to use the power button, only way it works.

Problem started after phone was rooted. Need help please!

Before my phone was rooted, here was my configuration:
Android Version: 4.4.4. Verizon
Build Number: KTU84P.G900VVRU1ANK2
Kernel Version: 3.4.0
I was able to successfully root my phone and verify via Root Checker! Problem started when i try to upgrade to Marshmallow and install a custom ROM. Here are the steps i made:
Installation Instructions for VZW S5 with Unlocked Bootloaders
Copy the G900V_PF4_Stock_Rooted_ROM.zip (or the deodexed and debloated version of the ROM) to your device’s internal storage on external SD card.
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G900V_PF4_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the checkmark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G900V_PF4_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your Verizon Galaxy S5 will reboot automatically.
The problem is now when i turn on the phone, a message would pop. SECURE FAIL: KERNEL on upper left corner and a START UP FAIL with a YELLOW triangle and an exclamation point inside. At the bottom it says YOUR DEVICE DIDN'T START UP SUCCESSFULY. USE THE VERIZON SOFTWARE REPAIR ASSISTANT ON A COMPUTER TO REPAIR YOUR DEVICE.
I should have just been content with a ROOT phone since my main goal was to remove bloaters. I should have not upgraded to Marshmallow 6.0
and install a custom ROM.
Was hoping for your expert advice since i am not a techy myself. Thanks in advance for all your input.

chicagoboyrn said:
Before my phone was rooted, here was my configuration:
Android Version: 4.4.4. Verizon
Build Number: KTU84P.G900VVRU1ANK2
Kernel Version: 3.4.0
I was able to successfully root my phone and verify via Root Checker! Problem started when i try to upgrade to Marshmallow and install a custom ROM. Here are the steps i made:
Installation Instructions for VZW S5 with Unlocked Bootloaders
Copy the G900V_PF4_Stock_Rooted_ROM.zip (or the deodexed and debloated version of the ROM) to your device’s internal storage on external SD card.
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G900V_PF4_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the checkmark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G900V_PF4_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your Verizon Galaxy S5 will reboot automatically.
The problem is now when i turn on the phone, a message would pop. SECURE FAIL: KERNEL on upper left corner and a START UP FAIL with a YELLOW triangle and an exclamation point inside. At the bottom it says YOUR DEVICE DIDN'T START UP SUCCESSFULY. USE THE VERIZON SOFTWARE REPAIR ASSISTANT ON A COMPUTER TO REPAIR YOUR DEVICE.
I should have just been content with a ROOT phone since my main goal was to remove bloaters. I should have not upgraded to Marshmallow 6.0
and install a custom ROM.
Was hoping for your expert advice since i am not a techy myself. Thanks in advance for all your input.
Click to expand...
Click to collapse
is your cid 15 or 11? if it is a 15 is your bootloader unlocked?

klabit87 said:
is your cid 15 or 11? if it is a 15 is your bootloader unlocked?
Click to expand...
Click to collapse
What is a CID and how do i know if it's 11 or 15? So sorry i'm not a techy person. i just appreciate you trying to help me. Thanks.

here is an excerpt from the bootloader unlock thread
You can check this by reading the file
/sys/block/mmcblk0/device/cid
Just the first 2 15xxxxxxxxxxxxxxxxxxxxxx or 11xxxxxxxxxxxxxxxxxxxxxxx(my number of x's are random, just read the first 2)
Click to expand...
Click to collapse
so check that and let me know.

Did you get your device fixed? @chicagoboyrn

Bryanx86 said:
Did you get your device fixed? @chicagoboyrn
Click to expand...
Click to collapse
Unfortunately not. No one seems to be able to help me..

chicagoboyrn said:
Unfortunately not. No one seems to be able to help me..
Click to expand...
Click to collapse
Reflash official firmware through odin onto your device, tbe last version you know that is rootable. Then go through the bootloader unlock process again

Bryanx86 said:
Reflash official firmware through odin onto your device, tbe last version you know that is rootable. Then go through the bootloader unlock process again
Click to expand...
Click to collapse
Thanks, i will try tomorrow. Since you seem to be knowledgeable with phones, can i ask you one more question? Have you heard of Samsung galaxy s5 (Verizon) having rotational problem? Thanks in advance.

chicagoboyrn said:
Thanks, i will try tomorrow. Since you seem to be knowledgeable with phones, can i ask you one more question? Have you heard of Samsung galaxy s5 (Verizon) having rotational problem? Thanks in advance.
Click to expand...
Click to collapse
My s5 started not rotating about a month ago
After doing a lot of research and changing rooms etc I came to the conclusion that it is a hardware failure (the gyro). As a work around you can install a rotation app. I use an app called Rotation Control

Need help unbricking my Galaxy S7 edge SM-G935P phone

I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.

Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse

just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.

epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.

bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS

epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?

bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it

epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.

https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375

Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.

epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?

bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help

thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.

epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.

Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.

epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.