Develop Bugs

[Q] Unrooting with a broken USB connector

My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?

EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.

https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.

mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.

efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?

Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.

efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.

Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.

efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.

Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.

More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!

I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.

mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.

I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?

Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.

The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.

scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2

efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.

It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2

Unrooting and relocking bootloader

I have a rooted and unlocked VZW Galaxy Nexus and I wish to flash the stock ROM and unroot, then lock the boot loader in order to download the OTA update, will this wipe all my data? If so, how would I restore the backed up files once I am back to stock?

This will wipe all your data.
You will still be able to update using the OTA method with or without root, so use TitaniumBackup to backup all your stuff and restore when you are back on stock ROM.

i think relocking bootloader does not wipe userdata.
that said, op, you dont need to relock bootloader to take the ota.
sent from my i9250

stevejr47 said:
I have a rooted and unlocked VZW Galaxy Nexus and I wish to flash the stock ROM and unroot, then lock the boot loader in order to download the OTA update, will this wipe all my data? If so, how would I restore the backed up files once I am back to stock?
Click to expand...
Click to collapse
What ROM are you currently using? If you are running stock IMM76K, no need to re-flash the stock ROM again.
Root makes no difference, neither does an unlocked bootloader.

See screenshot, I just wanted to get the official update without too much hassle.
Sent from my Galaxy Nexus using Tapatalk 2

stevejr47 said:
See screenshot, I just wanted to get the official update without too much hassle.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Based on your screen shot, I can point you in the right direction. Although you may think it is a lot of hassle, it isn't. Follow the steps to flash mysid IMM76K in the "flash" link in my signature. Then you should get prompted for the OTA -- if not, follow the steps in the "update" link in my signature to manually update your device (after doing the procedure in the "flash" link). If things are not clear, have a read of the "basics" link.
I don't advocate using shortcuts, as people come back when the next update comes around asking similar questions yet again.

Locking the bootloader will not wipe your data. I did it before with no problems whatsoever.

bk201doesntexist said:
i think relocking bootloader does not wipe userdata.
that said, op, you dont need to relock bootloader to take the ota.
sent from my i9250
Click to expand...
Click to collapse
I mean if he flash stock, phone will be nuked.
Beamed from my Grouper.

Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."

efrant said:
Based on your screen shot, I can point you in the right direction. Although you may think it is a lot of hassle, it isn't. Follow the steps to flash mysid IMM76K in the "flash" link in my signature. Then you should get prompted for the OTA -- if not, follow the steps in the "update" link in my signature to manually update your device (after doing the procedure in the "flash" link). If things are not clear, have a read of the "basics" link.
I don't advocate using shortcuts, as people come back when the next update comes around asking similar questions yet again.
Click to expand...
Click to collapse
Awesome guides.

fmcfad01 said:
Awesome guides.
Click to expand...
Click to collapse
Now if we could only get people to read them :S

stevejr47 said:
Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."
Click to expand...
Click to collapse
Any help on this?

stevejr47 said:
Any help on this?
Click to expand...
Click to collapse
How did you try to root? Did you follow the links I gave you?
http://goo.gl/wgDF2

stevejr47 said:
Not sure what you mean by "nuked", but I did the OTA update successfully after reverting back to 4.0.4 and unrooting. I am stil unlocked, but when i was proceeding to reroot, everything seemed to work, but when i went to the superuser app to regain root access, it fails. Also, not sure if it is a related issue, but when i try to save a screenshot or take a picture, the picture will not save to the gallery, it says "Cannot capture screenshot, storage may be in use."
Click to expand...
Click to collapse
What i mean is if you flash a stock image that you downloaded from Google Dev website, your virtual SD card will be wiped if you flash the userdata.img(this is your /data/ i believe).
Just follow Efrant's instructions, disregard what i said.

efrant said:
How did you try to root? Did you follow the links I gave you?
Click to expand...
Click to collapse
Yes, I sucessfully rerooted using those links, still having the picture/screenshot issue though where it is unable to save pictures and screenshots

stevejr47 said:
Yes, I sucessfully rerooted using those links, still having the picture/screenshot issue though where it is unable to save pictures and screenshots
Click to expand...
Click to collapse
try this
danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse

tried that, no dice

I am just hoping for a fix without wiping everything and starting over, but I'll do that if it is absolutely necessary
Sent from my Galaxy Nexus using Tapatalk 2

so i got a nexus today .. however i found it was already boot unlocked and pre rooted .. and had sm fkd up apex mod ics .. how do i revert to stock ? so i cont to t official updates ?

kunalwanvari said:
so i got a nexus today .. however i found it was already boot unlocked and pre rooted .. and had sm fkd up apex mod ics .. how do i revert to stock ? so i cont to t official updates ?
Click to expand...
Click to collapse
oh come on, seriously??? how lazy can people be these days. read the rules, search before you post.
and did you even read this thread at all?!
follow links in efrant's signature, reflash official google factory images with fastboot.
sent from my i9250

[Updating Pixel XL] After unlocked bootloader and rooted

So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.

https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk

wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?

[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.

Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.

TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks

Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk

Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?

Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.

Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?

Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.

TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now

[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.

mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..

lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.

Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.

The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk

Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot

Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk

awesome , thanks again everyone for your time and the help, very much greatly appreciated.

SafetyNet FAILED after stock rom and relocked bootloader? (Cant use Google Pay)

I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?

ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!

Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?

ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!

Thanks! I would have to install TWRP again maybe ?

ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.

uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive

ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option

a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.

From scorpion back to complete stock.

Hello.
I'm using the latest scorpion Rom on my pixel 3 xl.
Now I want to go back to Stock because I can't use my banking apps.
What is the best way to do it?
Kind regards

hyundai2010 said:
Hello.
I'm using the latest scorpion Rom on my pixel 3 xl.
Now I want to go back to Stock because I can't use my banking apps.
What is the best way to do it?
Kind regards
Click to expand...
Click to collapse
Download latest platform tools
https://developer.android.com/studio/releases/platform-tools
Download latest factory image
https://developers.google.com/android/images
extract all into same folder, hit flash-all.bat
This will wipe your phone. If you dont want to wipe it, open flash-all.bat with notepad and remove -w from the bottom line.
Code:
fastboot -w update image-crosshatch-pq1a.190105.004.zip

miffymiffy said:
Download latest platform tools
https://developer.android.com/studio/releases/platform-tools
Download latest factory image
https://developers.google.com/android/images
extract all into same folder, hit flash-all.bat
This will wipe your phone. If you dont want to wipe it, open flash-all.bat with notepad and remove -w from the bottom line.
Code:
fastboot -w update image-crosshatch-pq1a.190105.004.zip
Click to expand...
Click to collapse
nice thank you.
the bootloader is locked then?

hyundai2010 said:
nice thank you.
the bootloader is locked then?
Click to expand...
Click to collapse
Not until you lock it again.

how can i lock the bootloader again?
im on stock now!

hyundai2010 said:
how can i lock the bootloader again?
im on stock now!
Click to expand...
Click to collapse
The fastboot flashing command accepts both lock and unlock arguments. I would avoid locking the bootloader unless you absolutely have to.

Fastboot flashing lock
But as said, I wouldn't do it unless you're returning it to the shop or selling. Or, if you want to just get rid of the annoying notification at startup.

I want to Lock it because of OTA anderen Banking Apps

hyundai2010 said:
I want to Lock it because of OTA anderen Banking Apps
Click to expand...
Click to collapse
Have no idea how your banking app works, but can say unlocked bootloader has zero affect on OTA, and you can easily hide root almost all banking apps using Magisk hide? I would suggest you try all your banking apps with stock/unlocked before making the decision to re-lock your bootloader. If you do decide to re-lock you will be SOL when it comes to recovery in the future. You have to do the work and decide the trade off, not to mention the "wiping" of your data again.

watch out and flash on slot a and b because that's how i bricked my phone

Ok i will not touch the bootloader. I'm on stock with bootloader open, so if I get ots I can install without any problems?
Google pay is not working for now but with magisk hide I know it will work. So I will install Magisk now, I hope my Fidor bank app will still work then

hyundai2010 said:
Ok i will not touch the bootloader. I'm on stock with bootloader open, so if I get ots I can install without any problems? Google pay is not working for now but with magisk hide I know it will work. So I will install Magisk now, I hope my Fidor bank app will still work then
Click to expand...
Click to collapse
Stock and unlocked will get OTA's and they will update no problem... BUT when you root with Magisk the OTA may download but the update will always fail. There is just one more step you need to get a handle on. You will need to manually update your phone via fastboot using a full image rather than an OTA. When you manually update you will not lose your data or app settings, home screen layout, widgets etc. With each monthly update you need to re-install twrp (just need to "boot" it really) and then re-root with Magisk. Sounds like a lot, but with practice it takes 5 minutes. There are tutorials on how to apply monthly security updates to a rooted phone. Look around and read up. There are also plenty of people around willing to help if you get stuck. :good: