Develop Bugs

Progress: Boost Mobile Moto E4

Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible

NOTE: The below IS NOT Boost Mobile stock, it's sprint will update when I figure out Boost Stock
The sprint stock does fully work with the Boost Mobile device, LTE/data services seems to not work until you do a Factory Reset (in settings). ##72786# didn't work. It is now working for me fully after the factory reset from settings. The boost apps automatically install after the factory reset and after the celluar setup on first boot.. My Boost, etc.
After a few times of flashing and re-setup I've ended up with HFA error 701 which asks me to contact service provider to configure the device for service. Fixed by turning phone off for 20 minutes to an hour and the activation processed correctly.
If your experience differs, let us know!
Restoring to Stock
Install Motorola Drivers
Download RSDlite v6.2.4: http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Download the Sprint firmware file: https://androidfilehost.com/?fid=673368273298975628
Rename the zip to sperry.zip, the reason for this is to avoid the long file name error in RSD in some locations
Let the flashing process complete
Some people reported RSD not working in Windows 10, this is not fully true, install all moto and android drivers and it will show up fine as seen in below image
http://imgur.com/a/vdQxG
Thanks!,
rootjunky for RSD mirror
moto firmware team for the e4 stock 7.1.1

Have you check if this phone have gsm bands?

USA or International Variant?
zoofie666 said:
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
If you would like me to test anything you can hit me up on Discord: Zoofie#6780 and we can brainstorm
Click to expand...
Click to collapse
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.

Mensarius said:
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Click to expand...
Click to collapse
Read the root thread

@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.

amarc78 said:
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
Click to expand...
Click to collapse
You can only boot it

mendelgordon said:
You can only boot it
Click to expand...
Click to collapse
Yeah, I came to that conclusion. Just read it elsewhere also. I'm going to see what I can do about building twrp.

is it possible to take backup of Moto E4 stock rom with RSD lite ?

kartik verma said:
is it possible to take backup of Moto E4 stock rom with RSD lite ?
Click to expand...
Click to collapse
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.

amarc78 said:
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
Click to expand...
Click to collapse
For the international variant?

mendelgordon said:
For the international variant?
Click to expand...
Click to collapse
I have the Boost Mobile variant.

Is there anyone with the Boost Mobile variant that made a working system and boot backup? If so, could you please upload it for me? Mine got corrupted somehow and won't restore.

@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
The weirdness with the activation on Sprint/Boost seems to be normal, because I had trouble with two phones recently. The first was a retail unlocked e4 (to be used on Sprint), done before rooting, and activated at a Sprint corporate store last week by a rep who had trouble. The second phone was a retail unlocked Moto g4 Play (also to be used on Sprint), that I rooted first, got the SIM and back-end computer part taken care of by a rep at the same store yesterday, and did the rest myself.

hitokage004 said:
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
Click to expand...
Click to collapse
Yeah, I know all about that. I've already made a stock rom zip with sprint firmware but I want Boost so I can make a zip for that.
Sent from my LGLS755 using XDA Labs

I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.

CodyF86 said:
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
Click to expand...
Click to collapse
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!

amarc78 said:
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
Click to expand...
Click to collapse
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes

SykkNyzz said:
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
Click to expand...
Click to collapse
Hey, don't you have a LG volt?

Hello guys, i have two questions:
a) after you unlock bootloader on this device, is it possible to flash the non boost (international e4) rom on it? if so, have you done it?
b) i used to have a moto e2 from boost mobile (xt1526) and did this with the unlocked international e2 rom (xt1527) and i was able to use my gsm networks with it as i dont live in the U.S and CDMA bands dont work in my country, would it be possible with this device too? Because GSM bands are embeded in snapdragon chipsets, so flashing a stock unlocked firmware should make it work, but i want to know if you have tried it

custom recovery ?? for lg g4s(beat)

hi i rooted h735 device last night and i need twrp or any custom recoveries for that device . i couldnt find any information about it .could anyone help me to find it?

srdrylmz said:
hi i rooted h735 device last night and i need twrp or any custom recoveries for that device . i couldnt find any information about it .could anyone help me to find it?
Click to expand...
Click to collapse
The LG G4 S has a locked bootloader. You cannot install a regular custom recovery. However, steadfasterX has created a customized TWRP recovery for G4's with locked bootloaders. It works a charm and I recommend it highly. Keep in mind though, it will not allow you to flash a custom rom.
[LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all LOCKED G4 devices at: https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048

sdembiske said:
The LG G4 S has a locked bootloader. You cannot install a regular custom recovery. However, steadfasterX has created a customized TWRP recovery for G4's with locked bootloaders. It works a charm and I recommend it highly. Keep in mind though, it will not allow you to flash a custom rom.
[LOCKED][G4][TWRP][UNOFFICIAL] TWRP-in-FIsH for all LOCKED G4 devices at: https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048
Click to expand...
Click to collapse
I'm not sure if this works for his device I believe it has other technical specs then our regular g4 have...?
If they differ would be interesting in which parts so I may could adapt TWRP to get it working for his device as well
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
I'm not sure if this works for his device I believe it has other technical specs then our regular g4 have...?
If they differ would be interesting in which parts so I may could adapt TWRP to get it working for his device as well.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
My apologies if that turns out to be the case. Perhaps member srdrylmz would be willing to take the risk and test it out in order to pave the way for other LG G4 S owners as others have done for their particular models.

Thank you for your comments but i havent test it yet i turned to stock mm

steadfasterX said:
I'm not sure if this works for his device I believe it has other technical specs then our regular g4 have...?
If they differ would be interesting in which parts so I may could adapt TWRP to get it working for his device as well
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I did try the last version (5.0) on this model (H735) with LL, everything worked fine (0 errors) but upon reboot when i tried entering recovery i got stuck with the red led and black screen. After a battery pull when i got back into android it started optimizing apps (probably it had cleared the cache). I've tried getting the fish logs from the phone (followed the instructions in the
thread) but it appears there are none.

they have different chips so it wouldnt work G4s uses snapdragon 615

i can help porting it! I ported for unsupported LG devices in the past.

How to Root my new Moto Z2 Play?

OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!

Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.

First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.

WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.

pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.

The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.

New update and rooted Pixel 3 XL How to?

Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase" ?

Not sure about keeping Google pay, but I followed A/B slot update from here https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Everything is working fine on QP1A.190711.020.C3
You will need to reflash the kernel.
Only using systemless hosts and edge sense modules in magisk.

rob42ert said:
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase"
Click to expand...
Click to collapse
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)

rquinn19 said:
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
Click to expand...
Click to collapse
Gpay i got it working with BostonDan method.

Can you please link Boston Dan method?

skaforey said:
Can you please link Boston Dan method?
Click to expand...
Click to collapse
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks

henderjr said:
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
Click to expand...
Click to collapse
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.

sliding_billy said:
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
Click to expand...
Click to collapse
Good to hear.! I have a WearOS watch with Google Pay so I haven't had a need to use my phone much.

I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?

rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
How exactly have you determined that it is the kernel, and what does "many bug" mean? There are a lot of us who are using ElementalX on 10 with no issues including assistant squeeze. You can start by installing any other kernel available in the "Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other Development" section (you will need to re-root) and see if it makes any difference. It would also be a good idea if you posted in the dedicated thread for ElementalX. Besides getting user answers, @flar2 will be able to answer any questions specific since it is his kernel.
As for possible issues, how you installed could (dirty, clean, OTA/OTA sideload, factory image in BL) make a very possible difference as well as what version you have installed (specifically if you installed the new c3 image). It sounds like you have a bad Android 10 install and are going to end up needing a full clean install. Good luck.

rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
There are no bugs in ElementalX kernel.

Custom rom support

Hey all,
Early days of course, but just wondering if any devs wanna post if they're intending on getting this device to bring some custom rom magic?

I'm on it <3 Just published my Treble GSI flashing Guide over here too

Miustone said:
I'm on it <3 Just published my Treble GSI flashing Guide over here too
Click to expand...
Click to collapse
Ohh exciting! Thanks for getting getting in touch.
Just curious what your style of custom rom will be? Modified stock, pixel experience, Resurrection Remix style etc?
(UPDATE - just seen your GSI thread now - great work!)
Also you may not know this, but do you have an opinion on bootloader unlocking and camera features being lost? Apparently on older devices it was possible to backup the TA partition etc to avoid this, though indeed this may be unknown territory until we actually get the device (hopefully Thurs 18th June for me!)

cd993 said:
Ohh exciting! Thanks for getting getting in touch.
Just curious what your style of custom rom will be? Modified stock, pixel experience, Resurrection Remix style etc?
(UPDATE - just seen your GSI thread now - great work!)
Also you may not know this, but do you have an opinion on bootloader unlocking and camera features being lost? Apparently on older devices it was possible to backup the TA partition etc to avoid this, though indeed this may be unknown territory until we actually get the device (hopefully Thurs 18th June for me!)
Click to expand...
Click to collapse
Glad You found it. There is more to come...
About the bootloader unlocks. No worries! Sony isnt using the old Camera tech anymore. Means your Pictures and Videos will be Just fine after unlocking. You can dump Your TA with NewFlasher from XDA which is also recommended for flashing new Xperias with Treble. The only Thing You will loose is the Creator Mode somehow (Don't know how it works on the Mark 2 but i haven't Seen or missed it in my Xperia 5 yet...). It are good Times for Xperia and custom ROM Fans. Hope we will get a great Community again after so many years with ugly DRM fixing and lost functionalities...
Hope You will enjoy Your Xperia :fingers-crossed:
BR
PS: Check Out My Xperia 1 & 5 Threads. MARS_SOM will also Support the new Mark 2 once i have a Tester...

Miustone said:
Glad You found it. There is more to come...
About the bootloader unlocks. No worries! Sony isnt using the old Camera tech anymore. Means your Pictures and Videos will be Just fine after unlocking. You can dump Your TA with NewFlasher from XDA which is also recommended for flashing new Xperias with Treble. The only Thing You will loose is the Creator Mode somehow (Don't know how it works on the Mark 2 but i haven't Seen or missed it in my Xperia 5 yet...). It are good Times for Xperia and custom ROM Fans. Hope we will get a great Community again after so many years with ugly DRM fixing and lost functionalities...
Hope You will enjoy Your Xperia :fingers-crossed:
BR
PS: Check Out My Xperia 1 & 5 Threads. MARS_SOM will also Support the new Mark 2 once i have a Tester...
Click to expand...
Click to collapse
Ah this is fantastic news!
Ideally I'd love to root stock on day 1 of getting the device. Am I right in thinking that I should do the following:
1) Backup TA (what's the best way to do this?)
2) Unlock bootloader (via official Sony website)
3) extract boot img (via fastboot or download the latest stock rom? I'm new to xperia so unsure how it all goes for these devices!)
4) patch boot img with magisk
5) flash rooted boot img
Your help is greatly appreciated!
I for one will be active in the community and I suspect it'll grow rather popular!
Will check out the MARS_SOM....

cd993 said:
Ah this is fantastic news!
Ideally I'd love to root stock on day 1 of getting the device. Am I right in thinking that I should do the following:
1) Backup TA (what's the best way to do this?)
2) Unlock bootloader (via official Sony website)
3) extract boot img (via fastboot or download the latest stock rom? I'm new to xperia so unsure how it all goes for these devices!)
4) patch boot img with magisk
5) flash rooted boot img
Your help is greatly appreciated!
I for one will be active in the community and I suspect it'll grow rather popular!
Will check out the MARS_SOM....
Click to expand...
Click to collapse
1) Download NewFlasher from XDA. It will ask You as first or second step to backup TA (Trim Area). Use the included Drivers if needed and awnser all other Prompts with y for yes to flash full firmwares. Do this before unlocking as first step... NewFlasher is for newer Devices so please don't use the old flashing tools...
2) Correct. It will also give You the needed fastboot base for the following steps
3) Download XperiFirm and UnSin from XDA (Same Guy called Igor Eisberg or so). He's a VIP for us...
Download the Correct Firmware for Your Device and extract the boot Sin File with UnSin by drag and drop on the UnSin.exe.
4)You will get an boot Img File which can be rooted with the Magisk Manager before You flash it. Keep Recovery, AVB and Encryption Option Boxes marked under advanced options for the patching...
5) Flash the Patched Boot Image with fastboot like "fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img" to flash Root to both A/B Slots (Since it's a Treble A/B Device with 2 Slots).
That will be it. After that can You install the MARS_SOM if You want to. I'm releasing BETA2 today and hope it works on the Mark 2 too :angel:

Miustone said:
1) Download NewFlasher from XDA. It will ask You as first or second step to backup TA (Trim Area). Use the included Drivers if needed and awnser all other Prompts with y for yes to flash full firmwares. Do this before unlocking as first step... NewFlasher is for newer Devices so please don't use the old flashing tools...
2) Correct. It will also give You the needed fastboot base for the following steps
3) Download XperiFirm and UnSin from XDA (Same Guy called Igor Eisberg or so). He's a VIP for us...
Download the Correct Firmware for Your Device and extract the boot Sin File with UnSin by drag and drop on the UnSin.exe.
4)You will get an boot Img File which can be rooted with the Magisk Manager before You flash it. Keep Recovery, AVB and Encryption Option Boxes marked under advanced options for the patching...
5) Flash the Patched Boot Image with fastboot like "fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img" to flash Root to both A/B Slots (Since it's a Treble A/B Device with 2 Slots).
That will be it. After that can You install the MARS_SOM if You want to. I'm releasing BETA2 today and hope it works on the Mark 2 too :angel:
Click to expand...
Click to collapse
Great!
Regarding the TA backup, at what point would I restore that backup? As I really would wish to avoid such loss of any functionality (especially on day 1 haha) and so ideally I think I'll only go for this if/when it can be confirmed that unlocking the bootloader/restoring the TA backup has zero negative effects.
It'll be my intention, best case scenario, to root stock firmware (for theme, ad blocking etc), enjoy it for a short while to get a feel for the device, then play around with custom roms (plus gcam etc) ?
I'll be very keen to try out MARS_SOM, looks like you keep it all stock but with loads of extra tweaks for performance etc sounds great!

I already pre-ordered and can be a tester.. pre ordered the US version from Best buy.

daillcyruz said:
I already pre-ordered and can be a tester.. pre ordered the US version from Best buy.
Click to expand...
Click to collapse
When is your estimated delivery date, July?
I'm UK O2 and hopefully it's arriving this coming Thursday 18th
Unsure if I'm brave enough to unlock straight away for the risk of losing some camera functionality/features, so I may wait to see if someone less concerned tries first..... Lol

daillcyruz said:
I already pre-ordered and can be a tester.. pre ordered the US version from Best buy.
Click to expand...
Click to collapse
Would be an honor to Me! Contact me once You're unlocked :highfive:
cd993 said:
When is your estimated delivery date, July?
I'm UK O2 and hopefully it's arriving this coming Thursday 18th
Unsure if I'm brave enough to unlock straight away for the risk of losing some camera functionality/features, so I may wait to see if someone less concerned tries first..... Lol
Click to expand...
Click to collapse
After some more Research does it looks like that SONY isn't using DRMs for the Cameras anymore at all, after many claims from Customers over the last Years. The only DRM stuff thats left was for Netflix and the Xperia Services. I haven't seen any Claims or Problems besides that... But let's see If the Xperia 1 II suprises us

Miustone said:
Would be an honor to Me! Contact me once You're unlocked :highfive:
After some more Research does it looks like that SONY isn't using DRMs for the Cameras anymore at all, after many claims from Customers over the last Years. The only DRM stuff thats left was for Netflix and the Xperia Services. I haven't seen any Claims or Problems besides that... But let's see If the Xperia 1 II suprises us
Click to expand...
Click to collapse
Highly reassuring!
Out of curiosity at you please able to link me to this research? I'll give it a read.
Hopefully it'll be here this Thursday and so I'll enjoy stock for some time and then take the plunge to unlock!

cd993 said:
Highly reassuring!
Out of curiosity at you please able to link me to this research? I'll give it a read.
Hopefully it'll be here this Thursday and so I'll enjoy stock for some time and then take the plunge to unlock!
Click to expand...
Click to collapse
Haven't all links here, but My Xperia 5 proofs and this may also be interesting:
https://forum.xda-developers.com/xperia-1/help/xperia-1-drm-keys-locking-bootloader-t4079715
There will be no difference once You locked the BL and after flashing Stock again. Your unlock Key will be unique so You May want to keep it on a Safe place in Case You want to unlock again. But Like said, everything works fine over here except for Xperia Services where You can't Login after unlocking...

Miustone said:
Haven't all links here, but My Xperia 5 proofs and this may also be interesting:
https://forum.xda-developers.com/xperia-1/help/xperia-1-drm-keys-locking-bootloader-t4079715
There will be no difference once You locked the BL and after flashing Stock again. Your unlock Key will be unique so You May want to keep it on a Safe place in Case You want to unlock again. But Like said, everything works fine over here except for Xperia Services where You can't Login after unlocking...
Click to expand...
Click to collapse
Great stuff, thanks matey.
I reckon I'll run stock for a few days after getting it Thurs and mayyyybe I'll root over the weekend or after a week or so.
I'll keep in touch!
Thanks again

cd993 said:
Great stuff, thanks matey.
I reckon I'll run stock for a few days after getting it Thurs and mayyyybe I'll root over the weekend or after a week or so.
I'll keep in touch!
Thanks again
Click to expand...
Click to collapse
Here You Go! https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304/page16
Mate @Pandemic faced that the Repair after locking does the Trick. Missed to mentition that...

I will work on eXistenZ rom at some point.
If you don't know my rom, eXistenZ is stock with all best features from Havoc, Bliss, Pixel experience and Lineage ?

niaboc79 said:
I will work on eXistenZ rom at some point.
If you don't know my rom, eXistenZ is stock with all best features from Havoc, Bliss, Pixel experience and Lineage ?
Click to expand...
Click to collapse
That's wicked, I would love that!!

Does anyone know if ROMs are vastly different for XQ-AT51 (global single sim version) and XQ-AT52 (global dual sim version)? I preordered while it was not know that it is gonna be a single sim only in EU, so I returned the bundle and am gonna order the dual sim from Wondamobile. Guess flashing custom ROMs made for AT51 won't do the trick?

cd993 said:
When is your estimated delivery date, July?
I'm UK O2 and hopefully it's arriving this coming Thursday 18th
Unsure if I'm brave enough to unlock straight away for the risk of losing some camera functionality/features, so I may wait to see if someone less concerned tries first..... Lol
Click to expand...
Click to collapse
Well it did say 24 of July but I cancelled going to order from Amazon to get free headphones they say the same date also

vyp54 said:
Does anyone know if ROMs are vastly different for XQ-AT51 (global single sim version) and XQ-AT52 (global dual sim version)? I preordered while it was not know that it is gonna be a single sim only in EU, so I returned the bundle and am gonna order the dual sim from Wondamobile. Guess flashing custom ROMs made for AT51 won't do the trick?
Click to expand...
Click to collapse
Single or dual sim variant doesn't matter ?

Miustone said:
1) Download NewFlasher from XDA. It will ask You as first or second step to backup TA (Trim Area). Use the included Drivers if needed and awnser all other Prompts with y for yes to flash full firmwares. Do this before unlocking as first step... NewFlasher is for newer Devices so please don't use the old flashing tools...
2) Correct. It will also give You the needed fastboot base for the following steps
Click to expand...
Click to collapse
Hi Miustone,
Maybe you know what I'm doing wrong. Every time I try to run newflasher.exe I get the error
Code:
No usb device with vid:0x0fce pid:0xb00b !
USB debugging is enabled.
OEM Unlocking is NOT toggled.
USB is set to File Transfer mode.
I cannot change the controlled by setting from "This device" to "Connected device."
I am using the USB C to USB C cable that came with the phone.
I tried every configuration possible with this cable (even though it shouldn't matter).
ADB is recognizing the phone.
I tried running it as admin.
I tried with the drivers that come with the phone.
I tried with the gordonGate drivers.
I tried with the manual drivers from Sony.
Any help will be greatly appreciate!
Thanks
Edit: added another item to the list