Database Info

Bought new Xperia Z3 Dual D6633 with lollipop 23.4.A.0.546... Want to Root it...!!!

Hi guys.. I bought the new xperia z3 dual d6633 phone. It came with lollipop 23.4.A.0.546. I already made the a pre-rooted ftf build using PRFcreator on the latest lollipop build available. But when I was about to root, I came to realize that I would need a working root and Dual-Recovery manager installed on my phone to flash the pre-rooted latest build. I searched across the internet but its quite old and confusing. Here I believe as our fantastic experts on xda-forum, will know everything for everything got to do with the Android world. Please buddies help me out. I would be humble thankful to you. :fingers-crossed::victory::victory:

noob_coder said:
Hi guys.. I bought the new xperia z3 dual d6633 phone. It came with lollipop 23.4.A.0.546. I already made the a pre-rooted ftf build using PRFcreator on the latest lollipop build available. But when I was about to root, I came to realize that I would need a working root and Dual-Recovery manager installed on my phone to flash the pre-rooted latest build. I searched across the internet but its quite old and confusing. Here I believe as our fantastic experts on xda-forum, will know everything for everything got to do with the Android world. Please buddies help me out. I would be humble thankful to you. :fingers-crossed::victory::victory:
Click to expand...
Click to collapse
Google is your friend. You have to downgrade to kitkat, use giefroot tool to root, then install recovery and finally flash your PRF.

Beetle84 said:
Google is your friend. You have to downgrade to kitkat, use giefroot tool to root, then install recovery and finally flash your PRF.
Click to expand...
Click to collapse
It was much to have my post left only seen by the visitors but not left with a useless junk comment like yours. You came like a tornado, left a piece of junk and then simply flew past like lightning struck the tree and people never knew what burnt the tree. Neither you pinpointed where I will get this tool and secondly you didnt even bother to give the exact Kitkat build number to flash before even attempting to root using Giefroot tool. Anyways. I did find out myseld the giefroot tool and for you pathetic knowledge, it is stated that the tool doesnt even bother to work on the kitkat version i downloaded and flashed on my Z3 Dual D6633 phone. It's always giving me error that ADB server is out of date and killing. Will you bother yourself explaining to a noon like me to figure out what to do next when stuck in the middle of such a mess. Any further detailed elaboration would be highly appreciated by me. Thanks.
here is the screen shot for the error.:crying:

@noob_coder
Look, its not my fault you cant read. The first post in the giefroot thread says to use firmware from October 2014, and as for my pathetic knowledge, ill take it elsewhere and let you figure out what you have done. A bit of advice though..... Read read read before you do anything.

Beetle84 said:
@noob_coder
Look, its not my fault you cant read. The first post in the giefroot thread says to use firmware from October 2014, and as for my pathetic knowledge, ill take it elsewhere and let you figure out what you have done. A bit of advice though..... Read read read before you do anything.
Click to expand...
Click to collapse
For a sucker like yourself, its a burning news that this person found out everything and rooted without using your gfried crappy tool. Thank you. Please visit your mommy for the releif of burning sensations you might encounter afterwards.

noob_coder said:
It was much to have my post left only seen by the visitors but not left with a useless junk comment like yours. You came like a tornado, left a piece of junk and then simply flew past like lightning struck the tree and people never knew what burnt the tree. Neither you pinpointed where I will get this tool and secondly you didnt even bother to give the exact Kitkat build number to flash before even attempting to root using Giefroot tool. Anyways. I did find out myseld the giefroot tool and for you pathetic knowledge, it is stated that the tool doesnt even bother to work on the kitkat version i downloaded and flashed on my Z3 Dual D6633 phone. It's always giving me error that ADB server is out of date and killing. Will you bother yourself explaining to a noon like me to figure out what to do next when stuck in the middle of such a mess. Any further detailed elaboration would be highly appreciated by me. Thanks.
here is the screen shot for the error.:crying:
Click to expand...
Click to collapse
Try downgrading to 5.0.2 and then root using kingroot and then install recovery. Then flash a prerooted rom or stock based rom.:good:

Calling all mini owners

Calling all mini owners, donate to tdm, found a mini for $100 and sent him the info for it.
He has been working very hard to bring us root, now let's bring him a Dev phone!
Unlocking, root and custom ROM will come a lot faster if we get a device permanently in his hands.
https://forum.xda-developers.com/member.php?u=4126377

It is so nice to see that the community cares more about serving the consumer than the actual company does. ?

Well, i'd like to donate, but how?
fallen00sniper said:
Calling all mini owners, donate to tdm, found a mini for $100 and sent him the info for it.
He has been working very hard to bring us root, now let's bring him a Dev phone!
Unlocking, root and custom ROM will come a lot faster if we get a device permanently in his hands.
https://forum.xda-developers.com/member.php?u=4126377
Click to expand...
Click to collapse
Sent from my ZTE B2017G using XDA-Developers Legacy app

JoeGatto said:
It is so nice to see that the community cares more about serving the consumer than the actual company does.
Click to expand...
Click to collapse
I know right
Muggx said:
Well, i'd like to donate, but how?
Click to expand...
Click to collapse
I guess you would have to pm him to ask how you can donate to him, I thought he had a link up for donations.
I'd take the donations and buy the phone for him since I live closer to the seller, but I don't know if he got the PM I sent him about it and bought it or not yet.

He's gotten the device, use the link in the op to ask how you can donate to tdm and offset the cost, he plans on releasing custom roms soon.
Very exciting time to be a mini owner.

I'm excited and can't wait! I'm coming from a Nexus 5 and Nexus 5x those have very good development support, I can't wait to start flashing ROMs and kernels on this mini!

Hey @fallen00sniper hope you don't mind me hijacking this thread, but I wanted a place to update everyone on progress and I didn't want to start a new thread.
Current status as of Oct 3 2017
Unlock
Unofficial unlock tool has been released.
Waiting for official ZTE unlock.
TWRP
Alpha version posted in unlock thread. This uses the binary kernel and init from stock (including enforcing selinux) and does not have decrypt support, so it is not optimal.
Working on a full source build and eventual official TWRP builds.
Custom ROMs
I have just now successfully booted the device with a source built kernel based on the ZTE provided sources. I'm starting on Lineage 14.1 support. This will probably take at least a week or two.
Once Lineage 14.1 is working reasonably well, I will also do an AOKP build since that is my preferred ROM. I can help community members with other ROMs, but I won't maintain them myself.
Other
Collecting information on regional variants.
@saymonek has a single-SIM UK/Europe version that is reportedly stuck on 6.0. Are there any more variants?

@tdm, completely fine by me.
while you are in the rom getting them up and running, check into why the touch screen sucks at positional tapping, mine isn't 100% accurate lol

Did a bit of research on variants by trolling through ZTE support. So far I've found:
* USA version.
* UK Carphone Warehouse version.
* International "open market" version (eg. Austria).
* Hong Kong version.

First build done:
Package Complete: /home/tdm/out/laos-14.1/target/product/tulip/lineage-14.1-20171003-UNOFFICIAL-tulip.zip
This is going to need a fair amount of work before it boots and runs, but ... progress!

Oh also FYI... I've been cribbing from the HTC One A9 (hiae) device for Lineage builds. haie is maintained by intervigil, who I had the pleasure to work with at cyngn. I'd say he is one of the top four or five device people in the custom ROM world. And it looks like he has been actively working on Lineage 15.0 so we should get that soon after nightly builds start.

It's so exciting to see device development take off!

Just a quick update...
I had a ... uh ... "server malfunction" yesterday so didn't get a chance to do much. However, I'm back in business today.
So far today I've got linage to start the boot animation. Should be able to get all the way to the home screen tomorrow.

tdm said:
First build done:
Package Complete: /home/tdm/out/laos-14.1/target/product/tulip/lineage-14.1-20171003-UNOFFICIAL-tulip.zip
This is going to need a fair amount of work before it boots and runs, but ... progress!
Click to expand...
Click to collapse
Hello, can I change my axon 7 mini back to the US variant? It was originally US variant, I mistakenly switched US band in the engineering menu and Iost network services. I managed to get it working with the European firmware from ZTE Russia. Would like to revert to the US variant. I noticed in the bootloader version, the US version is P852A12 whilst the European variant is P852A11. Any luck on reverting to US variant?

Can you not access the engineering menu and switch back?
If not, my suggestion would be to use QPST and/or QXDM. These are proprietary tools but you can find them for download. They will allow you to program the frequency bands that your phone uses.
Good luck.
djeniuss said:
Hello, can I change my axon 7 mini back to the US variant? It was originally US variant, I mistakenly switched US band in the engineering menu and Iost network services. I managed to get it working with the European firmware from ZTE Russia. Would like to revert to the US variant. I noticed in the bootloader version, the US version is P852A12 whilst the European variant is P852A11. Any luck on reverting to US variant?
Click to expand...
Click to collapse

tdm said:
Can you not access the engineering menu and switch back?
If not, my suggestion would be to use QPST and/or QXDM. These are proprietary tools but you can find them for download. They will allow you to program the frequency bands that your phone uses.
Good luck.
Click to expand...
Click to collapse
I can access the engineering menu. The device is working but would have loved to switched back to US variant because it's a US variant initially but I am unable to install the US firmware I downloaded from ZTE US Support site

I'm sure we can get you back on US firmware.
What is the error when you try to flash the ZTE package?
djeniuss said:
I can access the engineering menu. The device is working but would have loved to switched back to US variant because it's a US variant initially but I am unable to install the US firmware I downloaded from ZTE US Support site
Click to expand...
Click to collapse

tdm said:
I'm sure we can get you back on US firmware.
What is the error when you try to flash the ZTE package?
Click to expand...
Click to collapse
Error Target machine P852A12 not found. I noticed my device bootloader has changed to P852A11 - Tulip. I checked my friend's Device which we bought at the same time from best buy in US, his own is still P852A12

Ain't it beautiful?
It's alive
Edit: can't get inline images to work, so you gotta click. Oh well.

tdm said:
Ain't it beautiful?
It's alive
Edit: can't get inline images to work, so you gotta click. Oh well.
Click to expand...
Click to collapse
:victory:
I am considering not even worrying about the warranty lol
Big questions are, everything working?, can you return to stock?, and how does the performance of the rom feel?

Any cook for Nougat ??

Hello people, due to the problems that I already commented on my other post, and that many of those who have the misfortune of having bought an ATyT phone, we do not find a solution to several problems, not even updates to Nougat as if they already have in Verizon and other companies. I contacted LG and they gave me a link where the source code was uploaded and everything needed to "cook" a Nougat ROM for the H900, only that ATyT leaves us dumped.
Going to the minds that are on this site, can someone cook the ROM? If I had the knowledge I would collaborate but never create one. We hope that some partner knows how and soon we have nougat in our V10. Then I leave the official link to download source code
http://opensource.lge.com/osSch/list?types=NAME&search=h900

Won't Work, Anyway...
MrRobot_84 said:
Hello people, due to the problems that I already commented on my other post, and that many of those who have the misfortune of having bought an ATyT phone, we do not find a solution to several problems, not even updates to Nougat as if they already have in Verizon and other companies. I contacted LG and they gave me a link where the source code was uploaded and everything needed to "cook" a Nougat ROM for the H900, only that ATyT leaves us dumped.
Going to the minds that are on this site, can someone cook the ROM? If I had the knowledge I would collaborate but never create one. We hope that some partner knows how and soon we have nougat in our V10. Then I leave the official link to download source code
http://opensource.lge.com/osSch/list?types=NAME&search=h900
Click to expand...
Click to collapse
You have to get the bootloader unlocked, and that's an AT&T limitation.
You're best hope is that if you have LP (5.1.1 - very unlikely), you can root.
But, upgrading to 6.0 breaks root, and installs an anti-rollback into the bootloader, so you can't root again.
Nougat (7.0) won't install at all with the locked bootloader.

I already upgraded to 6.0 and I'm facing those 6.0 issues... Anything that I can do to get my phone working fine again?

How do I root a Samsung Galaxy S7 Verizon (SM-G930V) Android Oreo 8.0?

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

Why no developmemt?

Hi there -
why is there no developmemt for the Find X2 Neo going on?
Nobody has this device? I have it since a week.
Is it maybe possible to root this device without unlocking the bootloader like installing magisk Manager and let it patch the original boot Image?
THX for Reading this and for replying.
-regards realrobman

Oppo Find X2 Neo is not available in all countries. Sometimes I think OPPO is not very interested to support this device by themselves. If you look at the UK-Supportpage you will find an update from 05/06/2020, at the Australian-Supportpage (and many other countries) from 02/09/2020 aaaand on the German Page you'll become only a description to make updates via OTA.
That could be a reason why nobody is interested to develop for this device.
But I have this Device and it's doing his job.