I like my droid mini so much I went out and got another.
To my good fortune, I discovered this "new" one has SU4.21 !!!
That means the efuse has not been blown and I could bootloader unlock.
The question is, was there ever a free method or is sunshine the only way?
Dreaming of cyanogenmod and twrp on the mini, would be perfect.
aha, motopocalypse by the original researcher Dan Rosenberg
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Droid Mini/Maxx is not listed but there is always a tiny chance it will work.
Well NOW there's a free bootloader unlock
http://bits-please.blogspot.com/2016/02/unlocking-motorola-bootloader.html
https://github.com/laginimaineb/Alohamora
Now to wait for someone who knows what they are doing to see if it will work on the mini/maxx/ultra
_ck_ said:
Well NOW there's a free bootloader unlock
http://bits-please.blogspot.com/2016/02/unlocking-motorola-bootloader.html
https://github.com/laginimaineb/Alohamora
Now to wait for someone who knows what they are doing to see if it will work on the mini/maxx/ultra
Click to expand...
Click to collapse
No, there isn't. Just like the other 10 motorola device forums you posted this in, this vulnerability is for MSM8974 ONLY, and its not new.
--beaups
beaups said:
this vulnerability is for MSM8974 ONLY, and its not new.
Click to expand...
Click to collapse
very sorry for the posts, I was excited and genuinely thought this was a new cross-motorola exploit and didn't realize the specifics
8960 is different enough from the 8974 to be immune?
again my apologies
ps. the Droid Razr series was also 8960, how come motopocalype doesn't work on the mini/maxx ?
_ck_ said:
I like my droid mini so much I went out and got another.
To my good fortune, I discovered this "new" one has SU4.21 !!!
That means the efuse has not been blown and I could bootloader unlock.
The question is, was there ever a free method or is sunshine the only way?
Dreaming of cyanogenmod and twrp on the mini, would be perfect.
Click to expand...
Click to collapse
If your phone is eligible, Sunshine is a cheap way to unlock your Bootloader. $25.00 last time I checked
_ck_ said:
very sorry for the posts, I was excited and genuinely thought this was a new cross-motorola exploit and didn't realize the specifics
8960 is different enough from the 8974 to be immune?
again my apologies
ps. the Droid Razr series was also 8960, how come motopocalype doesn't work on the mini/maxx ?
Click to expand...
Click to collapse
No worries. I haven't looked into Razr much, but typically these vulnerabilities are quickly patched by Motorola. I would guess that device released after motopocalypse was released or was patched shortly after.
--beaups
beaups said:
No worries. I haven't looked into Razr much, but typically these vulnerabilities are quickly patched by Motorola.
Click to expand...
Click to collapse
very exciting update
I've been told (very reliably) that a new exploit is on the way and will work on the 8960 pro (ie. mini/maxx/ultra)
unclear if it still requires the SU4 rom from June 2014 vs will work on the newer SU6 patched rom (even sunshine will not work on SU6) but it was verified by directly examining aboot and that the trustzone is only slightly different on the 8960pro vs 8974
(this time I won't post it in a dozen places - I suspect the release will pretty much spread like wildfire on its own)
_ck_ said:
very exciting update
I've been told (very reliably) that a new exploit is on the way and will work on the 8960 pro (ie. mini/maxx/ultra)
unclear if it still requires the SU4 rom from June 2014 vs will work on the newer SU6 patched rom (even sunshine will not work on SU6) but it was verified by directly examining aboot and that the trustzone is only slightly different on the 8960pro vs 8974
(this time I won't post it in a dozen places - I suspect the release will pretty much spread like wildfire on its own)
Click to expand...
Click to collapse
I'd like more info on this
leerpsp said:
I'd like more info on this
Click to expand...
Click to collapse
I would too but it's not out yet.
If I had to guess I'd suspect he is doing the proper notifications first to Motorola before releasing it. In which case as long as we don't accept OTA updates we should be okay.
_ck_ said:
I would too but it's not out yet.
If I had to guess I'd suspect he is doing the proper notifications first to Motorola before releasing it. In which case as long as we don't accept OTA updates we should be okay.
Click to expand...
Click to collapse
Will for one your not well informed Motorola is not sending down any more OTA updates for us they told us they were not they left us dead in the water and stuck on 4.4.4. Also you don't have to contact Motorola about bootloader unlocks don't know who told you that and who would take the time all its doing is allowing us to install user made/custom roms and android is open source so its legal.
leerpsp said:
Will for one your not well informed Motorola is not sending down any more OTA updates for us they told us they were not they left us dead in the water and stuck on 4.4.4. Also you don't have to contact Motorola about bootloader unlocks don't know who told you that and who would take the time all its doing is allowing us to install user made/custom roms and android is open source so its legal.
Click to expand...
Click to collapse
1. there are plenty of minor updates from SU4 to SU6 that were OTA and it stayed 4.4.4, they are just patches and there could easily be one that makes it SU6-7.4 - are you misunderstanding me that I am saying they are doing something more? What I meant was, if there is a a SU6-7.4 do NOT install it - though we can still always roll back to SU6-7(.0) via RSDlite - the nightmare would be a SU7 that prevents rollback to SU6
2. I assure you there is another bl unlock coming, this is completely confirmed.
I just don't know exactly when he is releasing it and I don't want to pester him - he's already proven he knows darn well what he is doing and is fully capable of producing the unlock and has already done so for other models - the catch is the unlock is not going to be phone specific so someone is going to have to package it for us
You've got me curious now. I haven't seen anyone else release a bootloader unlock in years.
Sent from my XT1254 using Tapatalk
beaups said:
You've got me curious now. I haven't seen anyone else release a bootloader unlock in years.
Click to expand...
Click to collapse
Oh you know who it is, he just did the other one.
He assures me this one will work on far more devices and even inspected the aboot on the droid mini for me - exact quote:
the TrustZone code there is slightly different, but it has a variation on the vulnerability I'm releasing and so it should work more-or-less out of the box
Click to expand...
Click to collapse
You'll need to change the symbols to match your version, but that's pretty much it.
Click to expand...
Click to collapse
so I'm going to shutup now because we need to leave him alone on his own timetable - I have to assume he is doing disclosures to motorola first, hence the delay
_ck_ said:
Oh you know who it is, he just did the other one.
He assures me this one will work on far more devices and even inspected the aboot on the droid mini for me - exact quote:
so I'm going to shutup now because we need to leave him alone on his own timetable - I have to assume he is doing disclosures to motorola first, hence the delay
Click to expand...
Click to collapse
He didn't release a bootloader unlock for "the other one" either. In fact, the POC he did release required an unlocked bootloader, and custom kernel.
beaups said:
He didn't release a bootloader unlock for "the other one" either. In fact, the POC he did release required an unlocked bootloader, and custom kernel.
Click to expand...
Click to collapse
I'm not sure what you mean. Motorola sent him a bootloader locked X and he unlocked it. He even shows every step and released the source.
Unless I am completely missing something.
_ck_ said:
I'm not sure what you mean. Motorola sent him a bootloader locked X and he unlocked it. He even shows every step and released the source.
Unless I am completely missing something.
Click to expand...
Click to collapse
He (re)documented the vulnerability and documented a full exploitation technique(and did a great job). However the code he released can not be used to unlock a production device. The code requires an unlocked bootloader and a custom kernel. If you read the comments on his disclosure page, you will see that.
--beaups
beaups said:
The code requires an unlocked bootloader and a custom kernel.
Click to expand...
Click to collapse
that sounds really weird though, why would you bl unlock an already bl unlocked device?
anyway, all we can do is wait and see what he does - he has no reason to lie, it's not like he is making money off it
_ck_ said:
that sounds really weird though, why would you bl unlock an already bl unlocked device?
anyway, all we can do is wait and see what he does - he has no reason to lie, it's not like he is making money off it
Click to expand...
Click to collapse
I'm not implying he's lying it all. The vulnerability he documented is certainly legitimate. I'm just stating you might not get some "clickheretounlock.exe". Somebody might have to do some work to code/package/turn the vulnerability into working unlock solution. Or maybe he will do it.
--beaups
beaups said:
Somebody might have to do some work to code/package/turn the vulnerability into working unlock solution. Or maybe he will do it.
Click to expand...
Click to collapse
oh I get that distinct feeling that he does not intend to release an actual executable, for reasons unclear, either legal or less responsibility
but I suspect he is going to lay out the steps pretty clearly and likely some source code and there is enough talent and desire around here to make it happen shortly after that
Related
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
dweezle said:
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
Click to expand...
Click to collapse
I'd recommend finding a comfortable place to sit and wait because you will probably be there a looong time.
dweezle said:
Verizon is teasing an October OTA update to 4.3 for our Galaxy S3s. I am on rooted and unlocked, stock 4.1.2, VRBMB1 with TWRP 2.6.3.0. I am hoping to see a rooted, unlocked version available here shortly after the 4.3 OTA releases. I think i am not the only one in this boat. Can someone outline the steps I would need to either, 1.) accept the OTA, or 2.) flash a pre-rooted version, if and when it appears here? Thanks
Click to expand...
Click to collapse
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
http://ezandroidapps.info/samsung-galaxy-s3-and-s4-will-get-android-4-3-jelly-bean-update/
SlimSnoopOS said:
Link to these teasers please?
Also, the update (if said update exists) could potentially lock down the bootloader in similar fashion to the S4 or Note II so unfortunately outlining steps to reroot and unlock won't help you in the event this occurs. The existing exploits definitely support the existing firmware but saying anything more would be irresponsible.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
That's sound advice there. I'm not OTAing nothing until the devs say it's okay or they make a flashable zip.
dweezle said:
http://ezandroidapps.info/samsung-galaxy-s3-and-s4-will-get-android-4-3-jelly-bean-update/
Click to expand...
Click to collapse
Ahh, there's no mention of an update specifically for Verizon. When OEMs state an update for phone models and do no specify the exact ones, they always mean their international variants. International varants are not tied to carriers and therefore do not need to go through a certification process before being pushed to handsets. If there's an ota coming at all for any US variant, it would't be on Verizon for another few months. It would foreseeably go T-Mobile/Sprint then AT&T/Verizon a month or two later.
Also, any site that has as many grammatical or syntax errors for sentence structure should not be viewed as a reliable source. Try here for example, the info is more clearly detailed and presented.
Yeah wouldn't hold my breathe, If Samsung release in Oct the soonest verizon could/would roll anything out would be jan/feb and pretty sure looking at past performance from verizon the s3 will reach end of life around the same time. meaning no update
I am reaping the benefit of a lot of generous, and smart, people who have kept my Moto Xoom alive and kicking way past what most would consider it's end of life. One of the reasons I chose the S3 was because of the large numbers that were sold. I assumed that the community support would outstrip any "official" support from either Samsung or Verizon. What are chances that someone will cobble together a great 4.3 ROM for the i535, after the release of 4.3 by Samsung?
nujackk said:
Yeah wouldn't hold my breathe, If Samsung release in Oct the soonest verizon could/would roll anything out would be jan/feb and pretty sure looking at past performance from verizon the s3 will reach end of life around the same time. meaning no update
Click to expand...
Click to collapse
Normally I'd agree with you whole heartedly but as PrDog stated they want us to buy that watch. So it just might be sooner than we think.
Sent from the S3 of The Afro Samurai
TheAfroSamurai said:
Normally I'd agree with you whole heartedly but as PrDog stated they want us to buy that watch. So it just might be sooner than we think.
Sent from the S3 of The Afro Samurai
Click to expand...
Click to collapse
I would be extremely surprised and happy if it did, but sincerely doubt it.
SlimSnoopOS said:
Ahh, there's no mention of an update specifically for Verizon.
Click to expand...
Click to collapse
I did the same thing as you, I looked for the word "verizon" and didn't find it ! Heh, I'm running Android 4.3 on my S3 already, albeit w/o Touchwiz....
dweezle said:
What are chances that someone will cobble together a great 4.3 ROM for the i535, after the release of 4.3 by Samsung?
Click to expand...
Click to collapse
For reasons beyond my knowledge level, ports from international versions of the S3 don't get done for the VZW, ATT, and so on variants of the S3. I know the non-US models have a different CPU (and chipset ?) so that could be the reason. Proprietary drivers and libraries that hook into the kernel are NOT "free" or open-source. It's not as simple as just re-compiling the Samsung-released kernel as important pieces of the puzzle are missing and it won't work without those pieces....
I'm just wondering I jumped conclusions on this device originally and made a hasty rant about the phone in aggravation over the locked BL.. Which was my fault .
I have since second guessed that and repurchased a 2nd s7 it's a truly great phone really believe that .
I'm only here to get real opinions on the likelihood we will get what we want which is A method to unlock bootloader what's everyone's honest thoughts that it either likely will or won't happen even at this point .Any reputable sources anywhere showing progress besides the petition?
I read an article that the phone can be rooted under developer settings "oem unlock" then Odin the .tar file for US version....
Found it on PhoneArena.com
Don't know how legit it is
mikesincredible said:
I read an article that the phone can be rooted under developer settings "oem unlock" then Odin the .tar file for US version....
Found it on PhoneArena.com
Don't know how legit it is
Click to expand...
Click to collapse
I'm talking about rooting the U.S version not the international I know that can be rooted already.
Is that what your referring to .
mikesincredible said:
I read an article that the phone can be rooted under developer settings "oem unlock" then Odin the .tar file for US version....
Found it on PhoneArena.com
Don't know how legit it is
Click to expand...
Click to collapse
How does Odin a stock tar root ?
What script method are you referring to?
I kind of meant and was talking about rooting the tmobile variant.
Got a Link to that phone arena article
T-Mobile is supposed to be working with Samsung to unlock the bootloader if you look at John's tweet about it. I don't know how far that'll go or how much they care, though.
Fortunately, if you look through the replies, T-Mobile's official account replied on the 21st
@riclee19 @JohnLegere This is something we are looking into for your family, and many others. We hope to have an update soon. *AshleyH
Click to expand...
Click to collapse
So maybe there is hope.
codabrink said:
T-Mobile is supposed to be working with Samsung to unlock the bootloader if you look at John's tweet about it. I don't know how far that'll go or how much they care, though.
Fortunately, if you look through the replies, T-Mobile's official account replied on the 21st
So maybe there is hope.
Click to expand...
Click to collapse
My idea Is that this s7 Bootloader issue thats so important to the root community and actually myself which we happen to be a small fraction of the over all consumer base.... is likely considered minor and extra headache in the big scheme of things to Samsung.. they figure the loss of loosing root community consumers is a future gain to not have to deal with us down the road .
Anything is possible with getting a tool or method to unlock but these tweets aren't implying much at this point ..another words the feedback and progress is who knows .
One recognized developer mentioned that if we do get it will likely be the end of the course run for this device by the time it arrives.
androidddaaron said:
How does Odin a stock tar root ?
What script method are you referring to?
I kind of meant and was talking about rooting the tmobile variant.
Got a Link to that phone arena article
Click to expand...
Click to collapse
Yea let me see if I can find it..it mentioned US version was all
......
Oh yeah it is international, just shows what to do to access the unlock portion
http://www.phonearena.com/news/How-to-root-the-Samsung-Galaxy-S7-and-S7-edge-Exynos_id79321
edit:
FireType, won the auction!
Now if anyone happens to know of some helpful developers...
Wow nice find! If someone gets a hold of this we def have potential to find a way to get a bootloader hack.
x000x said:
this isn't my auction but I just saw a Moto Z XT1650 engineering developer's edition on ebay. Would such a device possibly help in unlocking the bootloader?
http://www.ebay.com/itm/232184346157?_trksid=p2060353.m1438.l2649&ssPageName=STRK:MEBIDX:IT
Click to expand...
Click to collapse
Too bad I already updated to Nougat (no downgrading) I would have bought this phone for sure.
Thanks for sharing.
Maybe we could set up a pool if there's an expert willing to take a crack at it and interested in buying it. This might be the only shot at getting such a device. Still unsure if it would be helpful for people with retail versions of the Verizon moto z.
auction ended, did anyone from here actually bid on it? If not, this is probably the only time one of these would ever be made available
x000x said:
edit: well the auction ended... I wonder if whomever got it actually visits this forum
Click to expand...
Click to collapse
Won it.
FireType said:
Won it.
Click to expand...
Click to collapse
Great! Just out of curiosity, are you a dev?
rczrider said:
Great! Just out of curiosity, are you a dev?
Click to expand...
Click to collapse
No, I'm not a developer. But I believe that this device is a simple version of Z with an unlocked bootloader. The rear panel has a "moto" logo, while Verizon devices has "droid" logo
as soon as I get it I'll write about it here
Wow! I'm shocked someone from here won it. I thought for sure it would have gone to some unknown person and we'd never see another one like it.
x000x said:
Wow! I'm shocked someone from here won it. I thought for sure it would have gone to some unknown person and we'd never see another one like it.
Click to expand...
Click to collapse
What's the diff between that developer edition and global bootloader unlocked edition? Can you downgrade the bl on the developer devices?
Sent from my Motorola Moto Z Droid using XDA Labs
I'm really not sure what value this has in terms of root and (unofficially) unlocking bootloaders. I feel like it's just the device that's released to select developers prior to the official, public release. Even if there's something substantially different about it - in terms of software - that would give insight into unlocking, it's not much use unless it's in the hands of an experienced dev.
Interested in learning more nonetheless, though.
yes, the next step would be to find an experienced dev that might could offer some guidance
x000x said:
yes, the next step would be to find an experienced dev that might could offer some guidance
Click to expand...
Click to collapse
I suppose it's possible it could be a situation similar to the one @elliwigy describes here: https://forum.xda-developers.com/showpost.php?p=70407652&postcount=438
Short version: debug firmware from special pre-release phone + Dirty Cow exploit + experienced dev = unlocked bootloader and root for phone with virtually unlockable bootloader
I believe @elliwigy used to be a dev for Moto devices before moving to LG. They might be able to provide some guidance in determining the value of this "engineering" edition phone and its firmware. With the exception of tagging them in this post (twice ), I don't want to bug them too much since they likely can't do much without the phone itself.
FireType said:
No, I'm not a developer. But I believe that this device is a simple version of Z with an unlocked bootloader. The rear panel has a "moto" logo, while Verizon devices has "droid" logo
as soon as I get it I'll write about it here
Click to expand...
Click to collapse
I'm curious, any updates?
x000x said:
I'm curious, any updates?
Click to expand...
Click to collapse
another 1 week please =) im from Russia. Our POST is......................
Hello friends, I have the bike z 1560-03 but this team has the August 2016 follow-up that requirements (other than unlocked booloader) should I have? Can I install any firmware?
My computer is 64 gb dual sim.
Thank you.
Got it!
1) 3 GB RAM =)) LOL
2) Power Button is located above the volume buttons (another LOL)
3) Android 6.0.1 very buggy
4) Moto MOD connector have different hole in the middle. mods installation is impossible
5) No fingerprint scanner (it is not real)
6) Bootloader:
AP Fastboot Flash Mode (Not Secure)
BL: 90.02(*) (sha-2884c1d, 2016-03-16 16:41:30)
Baseband: M8996_1000.21.01.53p SHERIDAN_VZW_CUST
Product/Variant: Sheridan XT1650-01 32GB P1A
Serial Number: (it does not matter)
CPU: MSM8996
UFS: 32GB TOSHIBA THGLF2G8J4LBATR FV=0101
DRAM: 3GB SKHYNIX LP4 DIE=6Gb M5=06 M6=03 M7=00 M8=04
Console [NULL]: null
Battery OK
engineering
Software status: Modified
Could a dev/hacker find a way to unlock all bootlader using this prototype?
xterminater07 said:
Could a dev/hacker find a way to unlock all bootlader using this prototype?
Click to expand...
Click to collapse
I wouldn't count on it, if for no other reason than we don't have any seasoned devs interested in the Moto Z (as far as I can tell, anyway). So even if there was a dev interested in helping us out (without the actual phone), they likely would never even see this thread. Maybe @erfanoabdi can weigh in, but I think they've given up on rooting the VZW variant (and I don't think they were ever working on a bootloader unlock).
Interesting that it's a Verizon (XT1650-01) prototype, though. I still haven't updated my VZW variant to Nougat in hopes of root, but I think at this point it's a lost cause (which I assumed to be the case when I opted for the VZW variant in the first place). I suppose it's always possible this phone could be used in conjunction with DirtyCow to come up with something, but that would only work for folks still on Marshmallow.
My Moto Z is dead since 3 weeks now. It won't boot/charge. Even the PC doesn't recognize it. Pleas help me unbrick it if you find a way.
How do I do it
I got the same exact one 3 days ago. It's on 8.0.0 now. I have been reading a lot to find answers how to root or install twrp. It looks like there is not a straight forward answer. Just development guides that are not so clear on if there is are for sure way to root or unlock bootloader.
Everything looks to lead me to the same answer. Snapdragon us variants like ours are bootloader blocked so no twrp. Can we use safestrap? What can we do to root and install custom? Even if it's it's a touchwiz. I have an s4 I'm also playing with. I wish my s7 could do what the the s4 does. But samsung us trying to let carriers like Verizon block our bootloaders Hendering our abilities to use the phones like we want. It sucks.
I hope for a method soon myself. I hope that someone can steer us the right way.
8996?
Scottie32583 said:
I got the same exact one 3 days ago. It's on 8.0.0 now. I have been reading a lot to find answers how to root or install twrp. It looks like there is not a straight forward answer. Just development guides that are not so clear on if there is are for sure way to root or unlock bootloader.
Everything looks to lead me to the same answer. Snapdragon us variants like ours are bootloader blocked so no twrp. Can we use safestrap? What can we do to root and install custom? Even if it's it's a touchwiz. I have an s4 I'm also playing with. I wish my s7 could do what the the s4 does. But samsung us trying to let carriers like Verizon block our bootloaders Hendering our abilities to use the phones like we want. It sucks.
I hope for a method soon myself. I hope that someone can steer us the right way.
Click to expand...
Click to collapse
You echo my Frustrations. It feels good not to be the only one thinking these things. I think the reason there aren't any straightforward answers is because people are afraid of being sued. Why stop there? It begins with the owner of the phone who wants to root in the first place. They should sue themselves.
it doesn't seem logical to me. If I'm driving and, God forbid, I kill someone with my car do the people that taught me to drive get sued? it isn't an exactly perfect Analogy, but it's enough to start discussion, anywhere but here on this thread. LOL
Another thing is that phones are already very customized in that there are so many of them and they all function so differently even with the same ROM on a different provider Network does different things. it's probably difficult to give you the exact perfect set of instructions for your specific phone. Therefore knowing about Android and Linux and stuff is very helpful for filling in the gaps I will inevitably have. I have no such training and the times I have delved into it I"ve become completely lost.
A rudimentary understanding I do have. So I choose settings with the mindset of increasing the device lifespan, but nothing monumental.
Cruel_Carlos said:
You echo my Frustrations. It feels good not to be the only one thinking these things. I think the reason there aren't any straightforward answers is because people are afraid of being sued. Why stop there? It begins with the owner of the phone who wants to root in the first place. They should sue themselves.
it doesn't seem logical to me. If I'm driving and, God forbid, I kill someone with my car do the people that taught me to drive get sued? it isn't an exactly perfect Analogy, but it's enough to start discussion, anywhere but here on this thread. LOL
Another thing is that phones are already very customized in that there are so many of them and they all function so differently even with the same ROM on a different provider Network does different things. it's probably difficult to give you the exact perfect set of instructions for your specific phone. Therefore knowing about Android and Linux and stuff is very helpful for filling in the gaps I will inevitably have. I have no such training and the times I have delved into it I"ve become completely lost.
A rudimentary understanding I do have. So I choose settings with the mindset of increasing the device lifespan, but nothing monumental.
Click to expand...
Click to collapse
What firmware version do you have on your device?
cooltt said:
What firmware version do you have on your device?
Click to expand...
Click to collapse
Sammy S7- Oreo 8.0.0-0016- API 26- arm-64v8a- Qualcomm 822 (I think) boot loader RS8CRK2
Build: R16NW. G930VV RS8CRK2
See, not knowing anything forces me to give all this information when a few keystrokes would do
Cruel_Carlos said:
Sammy S7- Oreo 8.0.0-0016- API 26- arm-64v8a- Qualcomm 822 (I think) boot loader RS8CRK2
Build: R16NW. G930VV RS8CRK2
See, not knowing anything forces me to give all this information when a few keystrokes would do
Click to expand...
Click to collapse
The Qualcomm variants (your phone) are a little more difficult to root and there are several guides online how to do it but you have to make sure the guide says it is to root RK2 firmware on Oreo. RK2 has the December security patch i believe so there may not be a specific guide for that firmware yet but you can try and earlier guide which still works on your device after the December security patch.
This is to root G930V on Nougat from Jan 9 this year, it may work on Oreo too https://www.skyneel.com/root-samsung-galaxy-s7-verizon-sm-g930v-twrp-recovery
You could of course flash G930U firmware too which is unbranded USA and is known to work on Verizon devices. Sammobile XAA and USC. There is a modified version of Odin 13 to flash Verizon phones.
cooltt said:
The Qualcomm variants (your phone) are a little more difficult to root and there are several guides online how to do it but you have to make sure the guide says it is to root RK2 firmware on Oreo. RK2 has the December security patch i believe so there may not be a specific guide for that firmware yet but you can try and earlier guide which still works on your device after the December security patch.
This is to root G930V on Nougat from Jan 9 this year, it may work on Oreo too https://www.skyneel.com/root-samsung-galaxy-s7-verizon-sm-g930v-twrp-recovery
You could of course flash G930U firmware too which is unbranded USA and is known to work on Verizon devices. Sammobile XAA and USC. There is a modified version of Odin 13 to flash Verizon phones.
Click to expand...
Click to collapse
Wow, I thank you for directly addressing in a way I could better understand. "I've been busy" doesn't even begin ... I'm only getting to it tonight and last night a little. Cheers!
Cruel_Carlos said:
Wow, I thank you for directly addressing in a way I could better understand. "I've been busy" doesn't even begin ... I'm only getting to it tonight and last night a little. Cheers!
Click to expand...
Click to collapse
I just bought a g930v with the same bootloader. Did you have any luck with rooting or switching to the g930u firmware?
Sent from my SM-G930V using Tapatalk
Jiv4n said:
I just bought a g930v with the same bootloader. Did you have any luck with rooting or switching to the g930u firmware?
Click to expand...
Click to collapse
Yes just follow the same instructions.
cooltt said:
Yes just follow the same instructions.
Click to expand...
Click to collapse
Great thank you
Sent from my SM-G930V using Tapatalk
The most awaited request of users has been accepted by HMD and they just Published the source code for Nokia 7 plus.We can now hope for more development for our device.:victory:
Link for the source code:fingers-crossed:
https://t.co/tdWISOzeAv
dark_lord said:
The most awaited request of users has been accepted by HMD and they just Published the source code for Nokia 7 plus.We can now hope for more development for our device.:victory:
Link for the source code:fingers-crossed:
https://t.co/tdWISOzeAv
Click to expand...
Click to collapse
Since some got their bootloaders unlocked with an exploit before August, does this mean people can start development on TWRP and ROMs?
Yes devs have started building TWRP now .You can expect the official twrp in the comming days
Dont we need an unlockable bootloader though? From that article it looks like HMD are just doing what they should be in sharing the code.
divvykev said:
Dont we need an unlockable bootloader though? From that article it looks like HMD are just doing what they should be in sharing the code.
Click to expand...
Click to collapse
There was an exploit (bug) found in Oreo [Edit: Also in Pie Beta, before August] before August security patch, which allowed some people to unlock their bootloaders permanently.
So, now, those people can start developing custom ROMs and custom recoveries like TWRP for our Nokia 7 plus using the source code. :good:
SirGarmaples said:
There was an exploit (bug) found in Oreo before August security patch, which allowed some people to unlock their bootloaders permanently.
Click to expand...
Click to collapse
i can confirm, have unlocked half year and after some problems (missed gestures/liftup/playcertification with magisk installed, not upgradable without patching boot.img etc) finaly after november update all(not ota) work fine, also play is certified and updatable...
edit: i unlock with pie dp before august
So, the kernel code will be useful only for those who have unlocked their bootloader. For others, it doesn't make any difference, right?
What is that mean and what can we do now, geniuses? ??
fanboy_android said:
So, the kernel code will be useful only for those who have unlocked their bootloader. For others, it doesn't make any difference, right?
Click to expand...
Click to collapse
Yup. If Nokia does release a bootloader unlock for us other users, then it'll be useful for us too. But eh, I wouldn't count on it.
Emad tober said:
What is that mean and what can we do now, geniuses? ??
Click to expand...
Click to collapse
This means that those people with unlocked bootloaders (though there are only a few with those) can now start making or use TWRP and Custom ROMs.
This was not possible without the source code, so this is a thing to be mildly happy about, as still, most of us can't unlock our bootloaders yet.
This means that those people with unlocked bootloaders (though there are only a few with those) can now start making or use TWRP and Custom ROMs.
This was not possible without the source code, so this is a thing to be midly happy about, as still, most of us can't unlock our bootloaders yet.[/QUOTE]
Thanks. I liked this phone with oreo much more than pie. It became heavy and slow..