Database Info

Straight talk s7 follow under?

hello i got a s7 from straight talk . and it model is SM-G930VL
what does that follow under .. i was thinking verizon but verizon doesnt have the L in it . Also would i be able to root using that method that in the forum . also Which roms would i be able to use when i root it?
thank you

Adaken13 said:
hello i got a s7 from straight talk . and it model is SM-G930VL
what does that follow under .. i was thinking verizon but verizon doesnt have the L in it . Also would i be able to root using that method that in the forum . also Which roms would i be able to use when i root it?
thank you
Click to expand...
Click to collapse
It should be under the Verizon model. Usually tracfone does not lock the bootloaders on their variant. On another thread a guy flashed the verizon firmware to this model with no bricks and issue. but doing that WILL lock the bootloader. I hope he responds to my post. want to know to what extent it was flashed and if knox got tripped.

aromerblz said:
It should be under the Verizon model. Usually tracfone does not lock the bootloaders on their variant. On another thread a guy flashed the verizon firmware to this model with no bricks and issue. but doing that WILL lock the bootloader. I hope he responds to my post. want to know to what extent it was flashed and if knox got tripped.
Click to expand...
Click to collapse
would you be able to show me the right direction to where he got the method to root his.? also if you learn anything else from him . can you let me know. so this mean I have an unlock bootloader? doesn't that mean I can root easier?

Adaken13 said:
would you be able to show me the right direction to where he got the method to root his.? also if you learn anything else from him . can you let me know. so this mean I have an unlock bootloader? doesn't that mean I can root easier?
Click to expand...
Click to collapse
I should be able to get one of these mids august hopefully and will use it as a test device to see what bricks it and what hack can be done. In the past tracfone has release the SM-S975L(Tracfone Unlocked bootloader) which equals to an SGH-I337 (AT&T Locked bootloader), they released the S5 & S6 which equal to the SM-G900V and SM-G920V, both have Unlocked bootloaders. So i dnt think the S7 is any different and equals to the SM-G930V. Any root method that works for the SM-G930V should work on the SM-G930VL. But again this is just my say based on past experiences, i wont know until i get the phone and try all this. For what I know so far he was able to flash the complete verizon firmware which i think will flash a locked bootloader and no going back after it.
Yes will share my experiences.

Adaken13 said:
would you be able to show me the right direction to where he got the method to root his.? also if you learn anything else from him . can you let me know. so this mean I have an unlock bootloader? doesn't that mean I can root easier?
Click to expand...
Click to collapse
So i was able to flash the full latest verizon firmware and fully ended up converting the phone to an SM-G930V. SO provided that you flash the firmware on which root was achieved for the SM-G930V, then there is really no stopping you from rooting this phone. As expected due to flashing the verizon firmware the phone has a locked bootloader now but root was achieved regardless.
Proceed at your own risk.

I have the Sm-g930vl (tracfone) and would like to confirm the bootloader is unlocked. I can boot into both recovery and download mode but cannot connect with fastboot to get device info. Is there another way to check?

KericF said:
I have the Sm-g930vl (tracfone) and would like to confirm the bootloader is unlocked. I can boot into both recovery and download mode but cannot connect with fastboot to get device info. Is there another way to check?
Click to expand...
Click to collapse
Bootloader is locked and cannot be unlocked. Samsung devices do no use fastboot.

edit build.prop
aromerblz said:
Bootloader is locked and cannot be unlocked. Samsung devices do no use fastboot.
Click to expand...
Click to collapse
Thanks for the info. Do you know if I can edit the build.prop with adb without rooting? I've never messed with Samsung. Seems a different beast.

KericF said:
Thanks for the info. Do you know if I can edit the build.prop with adb without rooting? I've never messed with Samsung. Seems a different beast.
Click to expand...
Click to collapse
No way you can modify build.prop without root. What are you trying to accomplish?

aromerblz said:
No way you can modify build.prop without root. What are you trying to accomplish?
Click to expand...
Click to collapse
I was hoping to enable hotspot. I've read where people have flashed the 930u firmware and can enable it but I'm already on Nougat even on tracfone firmware.

KericF said:
I was hoping to enable hotspot. I've read where people have flashed the 930u firmware and can enable it but I'm already on Nougat even on tracfone firmware.
Click to expand...
Click to collapse
I see, the only way I see this working for you is by third apps or flash a firmware that supports it.

[UNLOCK] Bootloader Unlock Package

Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359

So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?

Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse

This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.

trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.

The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse

Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...

How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.

So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse

Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.

Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse

i get a message saying "cant update from sd card?"

yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.

JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard

Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.

JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware

Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.

JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.

here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?

The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse

[GUIDE][SM-G965U/U1] How to Use Engineering Mode

Hey guys! I haven't seen any other guides about this so here you go. How to use Engineering mode in the G965U and G965U1. Engineering mode doesn't let you do much, but if you're interested in testing some root methods it is definitely worth your interest. The two things that are most interesting to me is that SELinux is in Permissive and the OEM unlocking option appears, but it seems enabling OEM unlock does nothing. Still, all the files for the regular S9+ software is there, it just seems to boot a different mode. If someone can figure out how to make the normal UI and settings show up and inject root this could be our method. DON'T DO THIS IF YOU DON'T MIND RISKING MESSING UP YOUR DEVICE. USE A GOOD USB CABLE AND ONLY FLASH THE RIGHT FILES FOR YOUR MODEL. YOU HAVE BEEN WARNED.
Screenshots:
https://i.imgur.com/Uynre9O.jpg
https://i.imgur.com/h1MGsNJ.jpg
https://i.imgur.com/zYyno9m.jpg
So first. Go ahead and download the ENG boot and CSC for your device HERE and HERE. These files are courtesy of @wolfgart . Please give him thanks on his post, all credit goes to him for his work.
Second, extract both zips and you will have two .tar.md5 files. You need the latest odin to install this. I was unable to restore to stock with regular odin but patched odin let me return to stock. Download it HERE.
Go ahead and download the latest stock firmware as well. There a plenty online but I suggest using one from HERE as it worked for me.
Extract the firmware zip and reboot your phone into download mode by holding Bixby + Vol Down + Power. Plug in and open up odin and select the CP, BL, and USERDATA from the stock firmware and use the ENG boot file for AP and Combination file you downloaded earlier for CSC. Hold on to that stock firmware because you'll want to be able to return easily. Go ahead and start the flash process in ODIN. This will take a few minutes. If you have an MD5 error simply remove the .MD5 from the end of the filename for AP and/or CSC.
That's it! If all goes well you will have ENG boot. It isn't much right now but I'm sure with all your brilliant minds it could be the pathway to something much bigger.

"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.

LinneaDenVarg said:
"Allow the bootloader to be unlocked"? It can't be that easy on Snapdragon, can it??
EDIT: My bad, missed the part where you said it doesn't seem to do anything. I'd just delete this if XDA allowed me to.
Click to expand...
Click to collapse
LOL no problem! I'm sure most of the devs probably already have this set up I just threw this guide together since there isn't one yet. It gives us some extra opportunities to tinker around and as far as I know it's pretty safe to use it doesn't even trip knox.

That's it! If all goes well you will have ENG boot

hjfgdsg said:
That's it! If all goes well you will have ENG boot
Click to expand...
Click to collapse
Yup..... Now root.. and the wait continues. This isn't anything experienced people didn't already have. This is a nightmare waiting to happen for a n00b. Don't mess with this unless you know what you're doing.

hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm

thatruth132 said:
hey need some help with ENG BOOT for N976U
found a site that claims to have it just wanted so help in pm
Click to expand...
Click to collapse
Should probably ask in the note 10 threads this is for s9 and +

I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?

osvaldo3091 said:
I would like to know if it is working on Android 10 I have a sm-g965u Verizon been attached and if it is necessary to unlock the bootloader?
Click to expand...
Click to collapse
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock

TheMadScientist said:
No it is not And you cannot unlock this devices bootloader All the U W And U1 are permantly locked with no hope of unlock
Click to expand...
Click to collapse
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings

osvaldo3091 said:
I understand, what I would like to know is something I have this device is a sm-g965u with csc xaa is from Verizon I am in RD the security patches take a long time to arrive and the updates too.Do you think if i change the firmware to sm-g965u1 i would receive updates Faster? Thanks greetings
Click to expand...
Click to collapse
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked

TheMadScientist said:
Not necessarily It just depends who gets their updates out the fastest Sometimes U1 is faster others carrier is faster then U1 unlocked
Click to expand...
Click to collapse
Ok I understand thanks for the explanation I think I would not benefit from changing firmware. I explain something to you: I have this mobile and when they gave it to me the active csc was the vzw and I looked for a tutorial and managed to change it to xaa which is the one used in my country for unlocked device, the device doesn't have a Verizon app not anything like that but when I was in vzw it had already been updated to the April security patch but as I changed the csc I only received the March one and to be able to update the patch I had to install a firmware with the updated patch greeting again

Unlock bootloader and flash twrp with Spflashtool

Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??

This methode work with So Flashtool ?

I'm going to make SPflashTool working. I have some issue

Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.

I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.

bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD

redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).

bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it

bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.

redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:

guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please

Help with flashing!

I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.

damion675 said:
I have a SM-G930VL and have seen many threads from 2016-now that have been able to flash the 930U firmware but anytime I try flashing it can not get it to boot. I'm either in a bootloop or a recovery loop where it will never boot into recovery. Any help would be appreciated! I can answer almost any questions but I don't want to list them in case anything important gets lost in the list.
Click to expand...
Click to collapse
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.

cooltt said:
Yes but you still need the correct G930U firmware for your region/country.
Your phone needs OEM and usb debugging enabled, not essential when flashing firmware but often helps.
Click to expand...
Click to collapse
I am flashing the version for track-fone off of sam mobile and enabled OEM and Usb debugging

You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.

Beanvee7 said:
You'll need a patched Odin to flash G930U on a different model, otherwise you get mismatch errors. You can get it from here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
The OEM unlock step only applies to Exynos since that unlocks their bootloader, the toggle does nothing on USA/Snapdragon devices.
Click to expand...
Click to collapse
I feel like such a dunce...........I used this one to flash the 930U onto my 930A model so I even already had it. I just thought I had already tried it. After ~8 hours of working on this, it is done. Thank you so much!! I guess if you thought you tried something always try it again to be sure haha.