Database Users

quick general flashing question? no zte zmax pro z981 forum?

Sorry i couldnt find a section for my device and i believe the bootloader question kind of depends on the phone.
Last i checked the phone was to new for root support or roms. Just dont have time to investigate every thread i find.
I think all i need to know is if the bootloader is unlockable and if the phone is cloneable . I have a zmaxpro with a broken screen but functions fine. And another matching one that looks new but is frp locked(google activation reset shiz). My plan was just to swap the guts and be done, but my android experience and love for this website makes me think i can just flash partitions from the broken one to the locked one overwriting the frp bs.
Any advice or link in the right direction helps. Thanks for reading

cwtechshiz said:
Sorry i couldnt find a section for my device and i believe the bootloader question kind of depends on the phone.
Last i checked the phone was to new for root support or roms. Just dont have time to investigate every thread i find.
I think all i need to know is if the bootloader is unlockable and if the phone is cloneable . I have a zmaxpro with a broken screen but functions fine. And another matching one that looks new but is frp locked(google activation reset shiz). My plan was just to swap the guts and be done, but my android experience and love for this website makes me think i can just flash partitions from the broken one to the locked one overwriting the frp bs.
Any advice or link in the right direction helps. Thanks for reading
Click to expand...
Click to collapse
Just FRP unlock it it's simple.

G900V CID 11 Running CyanogenMod 14 - Unable to make phone calls/Use sms

Hi, in an attempt to unlock Wifi Tethering capability on my phone, I installed [G900F]CyanogenMod 14.0-20161020-UNOFFICIAL-klte, and now I'm unable to make phone calls or use SMS/MMS.
Is there anything I can try to get service back?
I've tried installing a new modem with no success, using Odin, FlashFire, Terminal Server. I'm not confident I was doing it correctly though, or even if I was using the correct modem files.
I was able to root the phone with Stock firmware, but Mobile Hotspot/Wifi Tether wasn't built-in, and I had no success with any of the apps... FoxFi, Wifi Tether Router, Barnacle Wifi.
Some more information on the phone:
It's the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V. I took it to the Verizon MVNO PagePlus and they were able to activate the phone, and everything was working perfect, until installing CM14.0.
A roadblock I found out, that might be the root of some of the problems, is the phone may not have the ability to unlock the bootloader, possibly limiting some modding methods. When looking at /sys/block/mmcblk0/device/cid, it starts with 11, designating a Toshiba eMMC chip.
I'll take any suggestions, or alternatives... I don't mind using the stock firmware or any other Roms. The main feature I'd like to have is the ability to use Wifi Tether and the basics, make calls, send sms.
Thank you.

I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?

leotakacs said:
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
Click to expand...
Click to collapse
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.

You will not be able to run any version of Cyanogen on your Toshiba S5 properly. Your best course would be to install FlashFire from the play store and use it to install a TouchWiz ROM such as Moar (5.0) or Phoenix (6.0).

TechFellow1 said:
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
Click to expand...
Click to collapse
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip

Hariiiii said:
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Click to expand...
Click to collapse
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?

leotakacs said:
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
Click to expand...
Click to collapse
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.

Hariiiii said:
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Click to expand...
Click to collapse
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol

KaptinBoxxi said:
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
Click to expand...
Click to collapse
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Delgoth said:
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
Click to expand...
Click to collapse
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.

Hariiiii said:
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Click to expand...
Click to collapse
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).

Hariiiii said:
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Click to expand...
Click to collapse
alright, that makes sense. Thanks for explaining. Always interested in these things since i don't QUITE understand exploits at that level. I do mainly apk modifications and software dev

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD

Legitsu said:
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Click to expand...
Click to collapse
I understand plenty enough to know the difference in the flash chips cid's with such like that... The fact of the matter i was trying to get at is that most Straight Talk phones are unlocked entirely without a care in the world, regardless of their CID/branding. Without the proper commands and 3rd party support, I get that there won't be a way. That's why I check my CID's first before buying S5's or Note 4's

Unlock Bootloader?

Is it even remotely possible to unlock the bootloader? I would love to install a custom recovery and a custom ROM.
Thanks.

Not possible currently, probably never will.

Until someone at Samsung decides to give the keys to the bootloader, it will remain locked.
(Pssst, hey Samsung Developer, there is a fame and fortune for your leak. :angel: )

I vouch 400$ for unlocked bootloader and emotion/lineage os

If S6 is anything to judge by, the chances for an unlocked bootloader are slim at best.

The only reason I would love an unlocked bootloader is to be able to root the stock OS and not have to use an engineering kernel. Otherwise, I tend to run rooted stock on my devices until they get too out of date.
Unfortunately, that means when this S7 Edge becomes obsolete, that will be the end of the line.

No one is even attempting it. With most phones now root / unlocked bootloader is a thing of the past. If you want those feature it'd be best to get a Pixel or a 1+. The rest of the phone will kill all of that in the next year.
The last good for rooting phone from Samsung was the Note 4 and even that was only the Tmobile variant. As Samsung and Android pay roll out internationally it will get killed off over seas too.
Unless a new crop of Android hackers pop-up to replace all the devs who used to roit/unlock the phones rooting and flashing is dying

ShrekOpher said:
No one is even attempting it. With most phones now root / unlocked bootloader is a thing of the past. If you want those feature it'd be best to get a Pixel or a 1+. The rest of the phone will kill all of that in the next year.
The last good for rooting phone from Samsung was the Note 4 and even that was only the Tmobile variant. As Samsung and Android pay roll out internationally it will get killed off over seas too.
Unless a new crop of Android hackers pop-up to replace all the devs who used to roit/unlock the phones rooting and flashing is dying
Click to expand...
Click to collapse
I'm not sure I would go that far. Sure, Samsung has locked their phones down like nuts, but there are still plenty of developments on other devices. The Sunshine team has managed to S-off every HTC flagship from the M8 on, along with a reasonably sold list of Moto devices. If you aren't on Verizon/AT&T you can skip the hack by going to HTCDev. Too bad HTC has gone absolutely bonkers on their own devices...
The LG V20 folks got "lucky" with Dirty Santa (though I wouldn't touch that mess with a 10 foot pole since your warranty is going to be void at the same time LG is getting sued over boot looping phones). Still, if you manage to get lucky, you can load custom ROMs on that device, and it's a true flagship.
Other devices seem to either have unlockable (through a web-site) bootloaders or have proven relatively easy to mod/root.
One day root may be a thing of the past unless you can find a dev phone, but I don't think we are quite there yet. That, and there will always likely be leaked dev kernels.

Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!

It's not happening.

diligent7771 said:
Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!
Click to expand...
Click to collapse
I have to agree with Kcodya. With the S8 coming out very soon, I am sure the Devs are not really that concerned with the S7 and unlocking the bootloader. I have read a lot of posts about the very issue and anyone and everyone that has been working on this has dropped it or no longer working on it. Look at the S6. It is still without an unlocked bootloader.
I agree with you about the EngImg and I guess at the present time, that is about all we have to work with. I have settled with it and am happy at least to have root privileges.
But we can still hope...

If Samsung ever gets off their hindquarters and updates the unlocked version of the S7/S7 Edge to Nougat, rooted stock will probably be optimal anyway. I know this is XDA, and people love to mod with whole ROMs, but OEM ROMs have improved dramatically over the years. This isn't the era of requiring CM (or LineageOS now) just to have a functional device like it was during the Gingerbread era.
Unfortunately, Samsung isn't likely to ever sell developer friendly phones again, so if you are a developer or like beta testing ROMs, this isn't your device. There are too many options that are trivial to unlock and develop on for anyone to spend too much effort bucking Samsung on their lockdown strategy.

diligent7771 said:
Few things:
-Is there any work still being done to get the bootloader unlocked? This dev thread no longer seems to be only devs, rather a bunch of "+1s", "thanks", and "tweet posts". All great posts, but not dev related.
- All devs on this thread are without a doubt better than I regarding android roms, unlocking, etc, but thought id throw a few ideas it here. (Im new to this type of dev). Maybe i can provide new hope? I just recently got the s7 and found out the hard way the current status woth no way to get custom roms. I know the chain of trust, verity, etc are a major buzzkill, but parts have all been hacked before so we can't Judy throw in the towel, can we?!
- http://newandroidbook.com this has a lot of good material, this guy is a genius, too bag he isn't working on this! (Download the book there & supplements).
Couple of actual ideas:
-He mentions in the book, with root you should be able to modify parts of partitions. Add long as you don't modify the entire partition it wont check for integrity on startup. Now that root exists, is Amy of this possible, to modify three partitions and unlock the bootloader?
- He also talks about how the chain of trust works using signed keys, and where to find these keys in the actual image file; since we know exactly where the keys are, and what's expected, can't we fake it with a custom image using a binary editor? He (in that link) also refers to his free tools to inspect, etc.
Remember when wet push via odin the phone isn't online so had no way to verify via internet if something is in fact legit. Hacks happen all the time with fake digital signatures and keys, certs, etc.
- In other words, now that root exists in the engineering kernel, Im thinking new doors have opened.
Thoughts? Hope?!
Click to expand...
Click to collapse
WTF? Did you literally copy and paste my post from another thread?! https://forum.xda-developers.com/showpost.php?p=71604183 lol I know your intentions are great, but you should probably indicate this is a quote from the original author (me), otherwise it appears you were the one that wrote this post. Carry on...

locked bootloader
jshamlet said:
The only reason I would love an unlocked bootloader is to be able to root the stock OS and not have to use an engineering kernel. Otherwise, I tend to run rooted stock on my devices until they get too out of date.
Unfortunately, that means when this S7 Edge becomes obsolete, that will be the end of the line.
Click to expand...
Click to collapse
Hey man,i saw you online and i need help with something.
Is locked bootloader affects radio gsm,on unlocked phone by at&t if i upgraded fw and changed version of bootloader from v2 to v4?
Thank you in advance!

Man, this stinks
TomatoesOnBluRay said:
Is it even remotely possible to unlock the bootloader? I would love to install a custom recovery and a custom ROM.
Thanks.
Click to expand...
Click to collapse
It's strange that this device never got a stable root. The type of root I was looking for 7 months ago is never going to exist. Development on the root of this phone was forgotten when the S8 came out. I wish I could say the opposite, but unfortunately we couldn't develop a proper root fast enough for the inevitable growth of interest in the newest device.

TomatoesOnBluRay said:
It's strange that this device never got a stable root. The type of root I was looking for 7 months ago is never going to exist. Development on the root of this phone was forgotten when the S8 came out. I wish I could say the opposite, but unfortunately we couldn't develop a proper root fast enough for the inevitable growth of interest in the newest device.
Click to expand...
Click to collapse
It's not just that, Samsung also offers some fairly nice bonuses for not rooting and root just isn't what it used to be. The days of "this phone is completely unusable without root to fix all the broken crap" are gone.
I found that simply switching to the unlocked firmware solved 90% of the things I wanted root for in the first place, and probably another 8% were solved by judicious use of ADB and NetGuard. What little was left just wasn't enticing enough to put up with the irritations and work-arounds required for the eng-boot root. I already run Nova launcher exclusively, but even at that, the stock launcher isn't total crap anymore. On the plus side, the eng-boot root doesn't trip Knox, so you can always go back if you want.
Yeah, it's going to suck when updates for the S7 stop due to age, and it would be nice if Samsung would offer a bootloader unlock when that happens, but I suspect it will live the rest of its life with nothing more than the engineering root method.

jshamlet said:
It's not just that, Samsung also offers some fairly nice bonuses for not rooting and root just isn't what it used to be. The days of "this phone is completely unusable without root to fix all the broken crap" are gone.
I found that simply switching to the unlocked firmware solved 90% of the things I wanted root for in the first place, and probably another 8% were solved by judicious use of ADB and NetGuard. What little was left just wasn't enticing enough to put up with the irritations and work-arounds required for the eng-boot root. I already run Nova launcher exclusively, but even at that, the stock launcher isn't total crap anymore. On the plus side, the eng-boot root doesn't trip Knox, so you can always go back if you want.
Yeah, it's going to suck when updates for the S7 stop due to age, and it would be nice if Samsung would offer a bootloader unlock when that happens, but I suspect it will live the rest of its life with nothing more than the engineering root method.
Click to expand...
Click to collapse
I entirely agree with you. I haven't rooted my S7 since I tried the engineer boot, and it has been completely and totally usable. I also agree with you about installing the unlocked firmware as it removes most of the bloat that comes with the stock firmware. Root is nice, but not entirely necessary on this device.

TomatoesOnBluRay said:
I entirely agree with you. I haven't rooted my S7 since I tried the engineer boot, and it has been completely and totally usable. I also agree with you about installing the unlocked firmware as it removes most of the bloat that comes with the stock firmware. Root is nice, but not entirely necessary on this device.
Click to expand...
Click to collapse
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.

Havdaddy said:
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.
Click to expand...
Click to collapse
All US/Snapdragon S7s and S7 Edges are hardware identical. You can run any of the 5 variants on them with zero issue (even going between V/S and A/T). This means you can run the unbranded/unlocked firmware on any US/Snapdragon based device as long as the model number matches.
Now, SIM locks are a separate issue. You still have to go to the carrier that locked it (or one of the paid services) to get the unlock code even if you are running the U firmware because the modem firmware is entirely separate.

Havdaddy said:
So, where might one obtain an unlocked firmware for a G930A? I've searched high and low and have found several different f/w but they all seem to be for other versions of the G930, not the A. Tried to flash mine with one of those and got caught in an endless boot cycle, so had to go back to stock - still locked - and AT&T says the IMEI doesn't belong to them even though it plays their little tune and shows their logo and flashes their name on startup. Pretty useless to me without being able to unlock it. Thoughts or ideas?
Many thanks in advance.
Click to expand...
Click to collapse
The firmware for all G930 and G935 variants are interchangeable. When I refer to the unlocked firmware, I'm referring to G930U and G935U. This version can be found on the AT&T Samsung Galaxy S7 and S7 Edge forums on this site. When you install the unlocked firmware, you are not unlocking the device, just the firmware associated with the unlocked version of the phone. This means less bloatware, faster speeds, and no AT&T boot logo. Sorry for the confusion my previous comment may have caused!

Need guidance regarding compiling a rom

Good afternoon ladies and gents,
I am here today seeking your guidance on compiling the stock rom for the lg v20 h910 (AT&T) variant. I was able to grab the rom source and the kernel source from here .... as far as that being the right rom is beyond me lol... but it matches the model number so i thought i would give it a try. and i am wondering if anyone can show me the right direction in do so myself. i have a desktop pc running win10 64 pro build 1607 ( redstone 2 ), but i also have a macbook pro if i cannot use my pc. if i have to install linux i will do so. any guidance would be much appreciated.
I want to lock the bootloader after the dirty santa exploit and also return the device to at&t for an upgrade, i want to get the s8+ . The reason i want to lock it and unroot ( stock it basically ) is because i am afraid of at&t coming after me for the full price of the device, especially that i have the NATF mega rom with the static boot screen and i am also afraid that they would think the device is not functional. The extrior of the device is flawless, no scratches nor dents or anything of that sort.

Nothing?

Can you not use google to search the forums for the answers on using LGUP to maybe restore your phone to stock, thus negating the need to possibly install multiple operating systems, or compile code?
I do not use your variant of this device (i am on the LS997) so my answer should be immediately discarded, but by and large more devices can be restored to factory utiluzing LGUP than can not be restored.
Good night, and good luck.

elijah420 said:
Can you not use google to search the forums for the answers on using LGUP to maybe restore your phone to stock, thus negating the need to possibly install multiple operating systems, or compile code?
I do not use your variant of this device (i am on the LS997) so my answer should be immediately discarded, but by and large more devices can be restored to factory utiluzing LGUP than can not be restored.
Good night, and good luck.
Click to expand...
Click to collapse
If there was an available kdz for my variant I would have used lg flash tool. Or lgup. Thats why i asked for a guide in the right direction when it came to compiling. Because the source code is available for h910 which is the at&t variant but no available kdz. So i was simply asking to learn how to compile a kdz from source code.

S8 Snapdrangon bootloader Q's

hi so i have a few things id like to talk about. i was wondering why it is not possible to port aosp roms to s8 snapdragon? givin its the same android version. also when i was messing around when rooting my s8 i saw that the software i had installed in the steps i went into settings and saw that i could enable oem unlock it worked and whenever i go back to that software its still enabled however i could not use any fastboot commands still. also i flashed twrp (not safe strap already have that) and now my base recovery does not show up....

kadenball said:
hi so i have a few things id like to talk about. i was wondering why it is not possible to port aosp roms to s8 snapdragon? givin its the same android version. also when i was messing around when rooting my s8 i saw that the software i had installed in the steps i went into settings and saw that i could enable oem unlock it worked and whenever i go back to that software its still enabled however i could not use any fastboot commands still. also i flashed twrp (not safe strap already have that) and now my base recovery does not show up....
Click to expand...
Click to collapse
Aosp roms requires a custom kernel to work, this requires:
1, unlocked bootloader(not possible on the snapdragon variant)
2, a custom recovery (not possible due to locked bootloader)
Just using the oem unlock option does not unlock the bootloader, more steps are required for most phones in order to unlock the bootloader, if it was that easy it would have been exploited by now, most of the guides on the snapdragon version mention that the bootloader is not unlockable.
You more than likely will need to restore the recovery through odin or something,

sofir786 said:
Aosp roms requires a custom kernel to work, this requires:
1, unlocked bootloader(not possible on the snapdragon variant)
2, a custom recovery (not possible due to locked bootloader)
Just using the oem unlock option does not unlock the bootloader, more steps are required for most phones in order to unlock the bootloader, if it was that easy it would have been exploited by now, most of the guides on the snapdragon version mention that the bootloader is not unlockable.
You more than likely will need to restore the recovery through odin or something,
Click to expand...
Click to collapse
Thanks ya I fixed it! And ya I understand there are additional steps to doing this that's why I mentioned fastboot. If you could guide me in a direction to potentially learn more about the kernals and how they work or what I would need to be good at to exploit download mode or knox whatever is required to potentially exploit the bootloader I would not give up on it im fine with wasting my time. I had recently talked to Sam help chat and they told me someone could unlock the bootloader for me (a phone company near me) I talked to a guy over the phone that said it could be possible bc they have the Samsung tools to do so but he told me to call the next day because the other tech knew more then him, so I called the next day and he said they could do it but they would get in trouble for doing so. My plan is to go in when the guy that doesn't know much is working ? and get him to unlock it. Hopefully then I could upload the software here and free the snapdragon slaves!!! If your interested in the conversations I had with Samsung and this other company I could upload the screen shots thank you for your reply!

kadenball said:
Thanks ya I fixed it! And ya I understand there are additional steps to doing this that's why I mentioned fastboot. If you could guide me in a direction to potentially learn more about the kernals and how they work or what I would need to be good at to exploit download mode or knox whatever is required to potentially exploit the bootloader I would not give up on it im fine with wasting my time. I had recently talked to Sam help chat and they told me someone could unlock the bootloader for me (a phone company near me) I talked to a guy over the phone that said it could be possible bc they have the Samsung tools to do so but he told me to call the next day because the other tech knew more then him, so I called the next day and he said they could do it but they would get in trouble for doing so. My plan is to go in when the guy that doesn't know much is working ? and get him to unlock it. Hopefully then I could upload the software here and free the snapdragon slaves!!! If your interested in the conversations I had with Samsung and this other company I could upload the screen shots thank you for your reply!
Click to expand...
Click to collapse
I've never dabbled in making kernels or anything so I'm pretty useless with that. The phone has been out for over 3 years now and as of yet there is no software method to unlock the bootloader, android devs would have figured that one out by now if it was possible, if it is possible then maybe there some extra hardware thats required to unlock the bootloader, I honestly don't know enough, I'm experienced enough to know to do certain things but I don't know the ins and out of how bootloader are coded, how the instructions are carried out. But it would defo be interesting to see if they do this for you.

sofir786 said:
I've never dabbled in making kernels or anything so I'm pretty useless with that. The phone has been out for over 3 years now and as of yet there is no software method to unlock the bootloader, android devs would have figured that one out by now if it was possible, if it is possible then maybe there some extra hardware thats required to unlock the bootloader, I honestly don't know enough, I'm experienced enough to know to do certain things but I don't know the ins and out of how bootloader are coded, how the instructions are carried out. But it would defo be interesting to see if they do this for you.
Click to expand...
Click to collapse
Ya thanks man when I talked to the inexperienced tech guy he said I could come in and we could try but I didn't want to drive there and waste my time ? but the experienced dude said I could probably find another repair place that would do it (figured it's another one of their shops he was hinting at as there are a few around me) so I will attempt to do this and hopefully some how it works and I can upload the software here not sure if flashing it would unlock anyone elses bootloaders as I expect it to be some sort of key like the HTC phones used to require and is unique to each device. When I got that oem to appear I was trying anything and everything in adb and fastboot as I suspected if we could glitch the phone in fastboot mode we could unlock it lol at least that's what I hoped for, tried upload mode kernal panic the 3 different download modes and tried to replace the Samsung download mode driver and flash the fastboot Android driver on top of it but my lack of knowledge on these things hindered me from making any progress but I believe there's a exploit in this root software that was copyed from the s9 and simply devs don't want to waste there time because they believe it is impossible. I've seen much hard thing accomplished in this dev sight hopefully the right person can figure it out and Is motivated by this post or point me in the right direction ? thanks if you read all this if I get it unlocked you will def see another post lengthy post ?