Database Info

Maybe a stupid question about Verizon Pixel 2's and rooting

Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.

D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.

I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?

tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.

Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk

Thanks. Glad I didn't try using the method I saw on YouTube, etc.

tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...

Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^

tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.

Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.

D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?

Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?

lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?

D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.

xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0

I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672

How did the OP pass the cert check and update checks?

TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit

lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.

Camera don't work after bootloader unlock + Sony Android 9 Flash with Emma

Hi guys, two days ago I flashed the stock sony android 9 on my xz2 (I had a branded device) but now the camera is not working properly, I can take picture but the screen always stay black. There is a way to fix this? I don't found anything simalar, but probably I did a bad research (if there is a post please give me the link)

ELDadda said:
Hi guys, two days ago I flashed the stock sony android 9 on my xz2 (I had a branded device) but now the camera is not working properly, I can take picture but the screen always stay black. There is a way to fix this? I don't found anything simalar, but probably I did a bad research (if there is a post please give me the link)
Click to expand...
Click to collapse
Did you unlock your bootloader to change firmware?
You are now going to need the drmfix for the rest of its life

marcogiannetta said:
Did you unlock your bootloader to change firmware?
You are now going to need the drmfix for the rest of its life
Click to expand...
Click to collapse
Ye I unlocked it. It's fine to do the drmfix, but how? I'm out of the flashing and similars since years I don't know how to do this.

ELDadda said:
Ye I unlocked it. It's fine to do the drmfix, but how? I'm out of the flashing and similars since years I don't know how to do this.
Click to expand...
Click to collapse
Bootloader unlock wasn't needed at all.
Anyway, search XperiFix here on xda, but I don't know if it's ready for xz2 family. Oh, it's a paid solution, about 19€.

marcogiannetta said:
Bootloader unlock wasn't needed at all.
Anyway, search XperiFix here on xda, but I don't know if it's ready for xz2 family. Oh, it's a paid solution, about 19€.
Click to expand...
Click to collapse
I just followed up the Sony site for the flash, btw maybe I'll spent this, but any free solution?

ELDadda said:
I just followed up the Sony site for the flash, btw maybe I'll spent this, but any free solution?
Click to expand...
Click to collapse
No

marcogiannetta said:
No
Click to expand...
Click to collapse
OK well, I'll do this little buy (19€ will not change my life at all) I'm upset of this ****ty trouble, none was said on sony site and Z2 doesn't have this trouble when unlocked...

ELDadda said:
OK well, I'll do this little buy (19€ will not change my life at all) I'm upset of this ****ty trouble, none was said on sony site and Z2 doesn't have this trouble when unlocked...
Click to expand...
Click to collapse
Z2 had even more troubles.
Maybe you never noticed, but the camera was really bad after bootloader unlock.

marcogiannetta said:
Z2 had even more troubles.
Maybe you never noticed, but the camera was really bad after bootloader unlock.
Click to expand...
Click to collapse
When I started to mod z2 I was more on the workpiece with fix and modding so I never cared too much of this troubles

At least it can take pictures, only the preview is black :silly:
Due to the lack of pie support of the pay solution at the moment, you can downgrade your phone to OREO, install the solution, take a picture and upgrade your phone to PIE again.
You need newflasher v13 from XDA and the stock Oreo ROM I uploaded in the TWRP thread.
And a downgrade requires factory reset.
Because of the encryption.
Feel free to ask for help.

MartinX3 said:
At least it can take pictures, only the preview is black :silly:
Due to the lack of pie support of the pay solution at the moment, you can downgrade your phone to OREO, install the solution, take a picture and upgrade your phone to PIE again.
You need newflasher v13 from XDA and the stock Oreo ROM I uploaded in the TWRP thread.
And a downgrade requires factory reset.
Because of the encryption.
Feel free to ask for help.
Click to expand...
Click to collapse
So I have to flash the previous version on mobile, run the fixer, and install again pie?

ELDadda said:
So I have to flash the previous version on mobile, run the fixer, and install again pie?
Click to expand...
Click to collapse
And use it a single time in OREO to take a picture.
And you need to backup your userdata before downgrading to Oreo.

MartinX3 said:
And use it a single time in OREO to take a picture.
And you need to backup your userdata before downgrading to Oreo.
Click to expand...
Click to collapse
Ye, understood. But it doesn't give me the root too right? I mean I can chose it? Cause otherwise pokemon go will not start on the phone

ELDadda said:
Ye, understood. But it doesn't give me the root too right? I mean I can chose it? Cause otherwise pokemon go will not start on the phone
Click to expand...
Click to collapse
Even with magisk hide?
You need magisk (it gives you root) to boot the phone after the twrp installation, because of Android Verified Boot 2.0

MartinX3 said:
Even with magisk hide?
You need magisk (it gives you root) to boot the phone after the twrp installation, because of Android Verified Boot 2.0
Click to expand...
Click to collapse
I have to see how it goes, maybe there is a way

ELDadda said:
I have to see how it goes, maybe there is a way
Click to expand...
Click to collapse
"Magisk hide" :silly:

Hello
Since I unlock the bootloader and install Android 9 with EMMA I have the same problem
Have you found a solution?
Sorry I'm really new I just wanted to change ROMs and I made the mistake of unlocking the bootloader
I look on the forum it offers solutions but with the level I have I really do not succeed

Matmani said:
Hello
Since I unlock the bootloader and install Android 9 with EMMA I have the same problem
Have you found a solution?
Sorry I'm really new I just wanted to change ROMs and I made the mistake of unlocking the bootloader
I look on the forum it offers solutions but with the level I have I really do not succeed
Click to expand...
Click to collapse
Go into my TWRP thread and install TWRP and magisk.
Root your phone, backup your apps with Titanium Backup
Downgrade to the Oreo firmware I uploaded there, use xperifix as DRMfix.
Boot into Oreo, use the camera to take one shot.
Upgrade to PIE and reinstall your apps with Titanium Backup.
Titanium Backup and xperifix costs some €/$
Then wait for xperifix PIE release to get your 100% photo quality back.

MartinX3 said:
Go into my TWRP thread and install TWRP and magisk.
Root your phone, backup your apps with Titanium Backup
Downgrade to the Oreo firmware I uploaded there, use xperifix as DRMfix.
Boot into Oreo, use the camera to take one shot.
Upgrade to PIE and reinstall your apps with Titanium Backup.
Titanium Backup and xperifix costs some €/$
Then wait for xperifix PIE release to get your 100% photo quality back.
Click to expand...
Click to collapse
I saw your thread, if it's the only solution I'll try it after. I am under Win7 and xperifix is ​​running under win8 and 10. Thanks for responding

Matmani said:
I saw your thread, if it's the only solution I'll try it after. I am under Win7 and xperifix is ​​running under win8 and 10. Thanks for responding
Click to expand...
Click to collapse
It should run under win 7 too
You're welcome
And a DRMfix reactivates every function back, like you never unlocked it.

Root your G7 with Magisk

Notice: before doing it, make sure your phone bootloader is unlocked or it won't work
This will require you to find a matching full ROM. To find your matching channel, go to Settings > About Phone > Software channel
Lookup the first two letters and find the matching ROM there
https://mirrors.lolinet.com/firmware/moto/river/official/
If your phone channel is "US Retail", download RETUS (retail US)
After you have downloaded the full ROM (you should keep the full ROM in case you want to revert to stock unrooted), unzip and get boot.img. Copy the image to your phone and use Magisk to patch the image. After that, copy the output image to your host computer.
Now turn your phone off, press and hold power + volume down to enter bootloader, connect your phone to host computer, and enter
Code:
fastboot flash boot
Press space once and drag and drop the output image file to command window.
If everything goes well, restart the phone and confirm it is rooted with Magisk
Now you have rooted G7

Nice solution. Did not even need TWRP for this either.

Seems to be oversimplified. I'm sure this makes perfect sense to those that go through the root process often or at least recently.
Unfortunately I'm not one of those. Last device I rooted was about 5-6 years ago.
I'll be doing my homework on the new tools and procedures while waiting for a more detailed step-by-step guide.
Thank you for your efforts and at least I know that root is possible.

Please can you guys make the steps easy to understand...some people here are new in this method.... Thanks

Question
What will my mirror be if Software Channel says Amazon?

O7ymand1as said:
What will my mirror be if Software Channel says Amazon?
Click to expand...
Click to collapse
I don't think Amazon version allows you to unlock the bootloader
Alternative method: look at the appendix of model on the box and find a matching one

O7ymand1as said:
What will my mirror be if Software Channel says Amazon?
Click to expand...
Click to collapse
I was able to unlock mine from amazon, it was XT1962-1 and said software variant amz and software channel amazon. For root I did have to flash with stock rom. The steps I took are listed in moto g7 questions thread. Look for amazon in the title.

I just picked up a G7 to play with today.
@mingkee I'm assuming these are similar to the Pixel devices when an OTA is sent we can just reflash the Stock boot.img and then take the OTA and re-root using the same methodology above?

Itachisasuke said:
I just picked up a G7 to play with today.
@mingkee I'm assuming these are similar to the Pixel devices when an OTA is sent we can just reflash the Stock boot.img and then take the OTA and re-root using the same methodology above?
Click to expand...
Click to collapse
Yes, as long as using correct boot.img

I tried with G7 Play - Channel
Did not work. These errors occurred in the prints.

Marcondes BR said:
Did not work. These errors occurred in the prints.
Click to expand...
Click to collapse
You should be good. The bad key error is normal. What happened on reboot?

Marcondes BR said:
Did not work. These errors occurred in the prints.
Click to expand...
Click to collapse
Don't worry about the error.
Install Magisk Manager and required components and that's it.
Keep the original boot in case to get OTA, but you should get updated full ROM and get updated boot and patch and flash again

timecutter said:
You should be good. The bad key error is normal. What happened on reboot?
Click to expand...
Click to collapse
Rebooted normally. When it starts, the screen turns completely black, and bad key is written in the upper left corner. It restarted in the same way.
---------- Post added at 02:06 PM ---------- Previous post was at 01:59 PM ----------
mingkee said:
Don't worry about the error.
Install Magisk Manager and required components and that's it.
Keep the original boot in case to get OTA, but you should get updated full ROM and get updated boot and patch and flash again
Click to expand...
Click to collapse
Can you explain this better? Did not quite understand.

This method works flawlessly. Thanks for the tip.

Marcondes BR said:
Rebooted normally. When it starts, the screen turns completely black, and bad key is written in the upper left corner. It restarted in the same way.
---------- Post added at 02:06 PM ---------- Previous post was at 01:59 PM ----------
Can you explain this better? Did not quite understand.
Click to expand...
Click to collapse
Boot.img should match ROM version or you may have trouble booting.
New OTA has been released for US, but it's recommended to wait for updated full ROM in order to regain root.

mingkee said:
Boot.img should match ROM version or you may have trouble booting.
New OTA has been released for US, but it's recommended to wait for updated full ROM in order to regain root.
Click to expand...
Click to collapse
Did not work.
My bootloader is unlocked.
The boot.img image is correct.
I did it step by step and it did not work.
I do not get root and magisk says that it is not installed.

Marcondes BR said:
Did not work.
My bootloader is unlocked.
The boot.img image is correct.
I did it step by step and it did not work.
I do not get root and magisk says that it is not installed.
Click to expand...
Click to collapse
Did you patch boot.img?

my moto g7 non variant river phone channel said "US Retail", but the required rom info was under River/Official/Retail, not River/Official/Retus. When I tried Retus, it bootlooped until I flashed Retail. FYI for anyone encountering same issue.

mingkee said:
Did you patch boot.img?
Click to expand...
Click to collapse
Yeah. I copied the patch boot to my computer and flashed with adb.

My software channel is "reteu2" and the software version is PPW29.98-28.
Under river/official/RETEU/ I cannot find a suitable software version. Is my version not available there?

Already unlocked bootloader on my pixel 4 XL

Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:

elsamuraiguapo said:
Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:
Click to expand...
Click to collapse
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!

Not from THAT link....
Sent from my Pixel 2 XL using Tapatalk

I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?

ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Sometimes it's about the peace of mind to make sure it's being done properly

ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Why put the link in there if it's not a valid link?
Sent from my Pixel 2 XL using Tapatalk

samteeee said:
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!
Click to expand...
Click to collapse
The Verizon version will be locked.

Have you tried booting Magisk on it yet?

Did you have to turn it on and enable OEM unlocking in Developer options first or nah?

did you try root it ?
mine is coming today
it shipped last night before i went to bed lol

please system dump

brownkid said:
Did you have to turn it on and enable OEM unlocking in Developer options first or nah?
Click to expand...
Click to collapse
You need to turn it on and enable it

I just got my Pixel 4 XL. I want to root, but without the system image how can I get the boot image to patch?
---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------
MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk?

MicroMod777 said:
The Verizon version will be locked.
Click to expand...
Click to collapse
Most likely.

MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk? @MishaalRahman

Followed the same steps as OP. Unlocked my 4XL the same way I unlocked my 3XL

northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
I think he means patching the boot image with magisk

northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
ZeroKool76 said:
I think he means patching the boot image with magisk
Click to expand...
Click to collapse
And then fastbooting the image that magisk patched :good:

For those asking, no I haven't tried to root it yet. I just wanted to start playing with the device and signing in to all my stuff. No point in doing that first without unlocking the bootloader cause just like with any other phone that will factory reset everything. Better to unlock the device first before you start customizing it to you liking. Most likely root can be achieved without wiping again.

What command are you using? I tried fastboot flashing unlock and it just shows the help menu and fastboot oem unlock gives an error. On win 10 here. That link is incomplete?
ETA: I ended up using a tool and setting it to pixel/ pixel xl and it worked but its all for not, I think I'm returning the phone. I just am not happy with the way the face unlock works with ambient display, it ends up unlocking the phone when I just want to check my notifications lol. C'est la vie!

RedMagic 3s software version?

This is so weird but i noticed it. My rm3s shiped with na global rom ig but im from India.

How do you find the phone so far? I'm in the US and waiting for it tomorrow. Already returned ASUS ROG 2.

Pointmanipo said:
How do you find the phone so far? I'm in the US and waiting for it tomorrow. Already returned ASUS ROG 2.
Click to expand...
Click to collapse
You order from redmagic directly? Mine took forever from them

suzook said:
You order from redmagic directly? Mine took forever from them
Click to expand...
Click to collapse
Yes, ordered it on the 1st, getting it tomorrow the 5th. I did pay for the expedited shipping.

Pointmanipo said:
How do you find the phone so far? I'm in the US and waiting for it tomorrow. Already returned ASUS ROG 2.
Click to expand...
Click to collapse
I love the phone. Its snappy and totally stock. There are people complaining about this but i totally adore stock android. Only issue are updates

apollo3x said:
I love the phone. Its snappy and totally stock. There are people complaining about this but i totally adore stock android. Only issue are updates
Click to expand...
Click to collapse
Me too! No problem with updates, it updated twice with I first powered it up.

apollo3x said:
This is so weird but i noticed it. My rm3s shiped with na global rom ig but im from India.
Click to expand...
Click to collapse
Even I was curious about this... I unlocked bootloader and was in need of the ROM for root.. Was confused and so put my activities on hold...
Now that I see one more device with V1.04, I will resume to root the device
Aru

B01070 said:
Even I was curious about this... I unlocked bootloader and was in need of the ROM for root.. Was confused and so put my activities on hold...
Now that I see one more device with V1.04, I will resume to root the device
Aru
Click to expand...
Click to collapse
Good luck, let me know what happened

apollo3x said:
Good luck, let me know what happened
Click to expand...
Click to collapse
I am currently rooted... With no issues...
Unlock Bootloader (Follow similar steps in RM3)
Install Magisk Manager App
Extract boot.img from the current rom, patch it.. Move it to PC and use fastboot to install the same..
you will be rooted..
BTW, had issues with EdXposed Module in Magisk.. Advise you to stay away from Xposed modules..
Aru

B01070 said:
I am currently rooted... With no issues...
Unlock Bootloader (Follow similar steps in RM3)
Install Magisk Manager App
Extract boot.img from the current rom, patch it.. Move it to PC and use fastboot to install the same..
you will be rooted..
BTW, had issues with EdXposed Module in Magisk.. Advise you to stay away from Xposed modules..
Aru
Click to expand...
Click to collapse
How do we patch boot.img? Via magisk manager?

apollo3x said:
Good luck, let me know what happened
Click to expand...
Click to collapse
apollo3x said:
How do we patch boot.img? Via magisk manager?
Click to expand...
Click to collapse
Yup... Aru

B01070 said:
Yup... Aru
Click to expand...
Click to collapse
yep, thanks for help. actually i was not able to flash via fastboot but then i discovered that the flash command needs to be put everytime you wanna flash via fastboot lol

apollo3x said:
yep, thanks for help. actually i was not able to flash via fastboot but then i discovered that the flash command needs to be put everytime you wanna flash via fastboot lol
Click to expand...
Click to collapse
Glad, you have a rooted device... But please be careful with root as we do not have an unbrick tool available for RM3S... Definitely you dont want an semi-brick device... A word of caution...
Cheers!
Aru

B01070 said:
Glad, you have a rooted device... But please be careful with root as we do not have an unbrick tool available for RM3S... Definitely you dont want an semi-brick device... A word of caution...
Cheers!
Aru
Click to expand...
Click to collapse
Yes, thanks. Bdw guide me how to go full stock again? I can just unroot and relock the bootloader and it'll be fine right?

apollo3x said:
Yes, thanks. Bdw guide me how to go full stock again? I can just unroot and relock the bootloader and it'll be fine right?
Click to expand...
Click to collapse
I wouldn't mess around at all with your rm3s. We have no way of recovering properly because we have no unbrick tool. Leave it as is. I have a non booting rm3sz that is only 3 days old. Its a $500 paperweight at this point? Might just sell it for parts.

suzook said:
I wouldn't mess around at all with your rm3s. We have no way of recovering properly because we have no unbrick tool. Leave it as is. I have a non booting rm3sz that is only 3 days old. Its a $500 paperweight at this point? Might just sell it for parts.
Click to expand...
Click to collapse
Oh bro. Goodluck. And i hope nubia provides a unbrick tool soon

apollo3x said:
Oh bro. Goodluck. And i hope nubia provides a unbrick tool soon
Click to expand...
Click to collapse
Very good chance we NEVER get it.

apollo3x said:
Yes, thanks. Bdw guide me how to go full stock again? I can just unroot and relock the bootloader and it'll be fine right?
Click to expand...
Click to collapse
suzook said:
I wouldn't mess around at all with your rm3s. We have no way of recovering properly because we have no unbrick tool. Leave it as is. I have a non booting rm3sz that is only 3 days old. Its a $500 paperweight at this point? Might just sell it for parts.
Click to expand...
Click to collapse
Agreed... I will not mess up with the device if it already rooted... Given that we do not have the unbrick tool.. I am wondering why we would need to go back to stock with locked bootloader? When returning the device to nubia for support? Ignore it as they will be able to identify if the device was unlocked or rooted... So waste of efforts..
Aru