Related
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.
Hi. I am a noob at rooting. Which of your unlocking and rooting method should I use for a Verizon HTC DNA that is updated to its current version of Kit-Kat? Firewater? I just did a factory reset for a fresh start. I have not installed any "user apps." Basically it is cleaned. This is my first at rooting a phone, but I have rooted Kindle Fire once. I do know about the warranty. I would also like to know a method to unroot as well incase I want to go back for any reason. Need help as soon as possible.
crazyleopard77 said:
Hi. I am a noob at rooting. Which of your unlocking and rooting method should I use for a Verizon HTC DNA that is updated to its current version of Kit-Kat? Firewater? I just did a factory reset for a fresh start. I have not installed any "user apps." Basically it is cleaned. This is my first at rooting a phone, but I have rooted Kindle Fire once. I do know about the warranty. I would also like to know a method to unroot as well incase I want to go back for any reason. Need help as soon as possible.
Click to expand...
Click to collapse
Did you unlock the bootloader via HTCdev.com already?
LS.xD said:
Did you unlock the bootloader via HTCdev.com already?
Click to expand...
Click to collapse
No, I have not started on anything because not sure what the first step is. Sorry for my question. I have been looking online, including youtube for the answer. I most likely find how-tos that are outdated and wasn't sure if they would still work.
crazyleopard77 said:
No, I have not started on anything because not sure what the first step is. Sorry for my question. I have been looking online, including youtube for the answer. I most likely find how-tos that are outdated and wasn't sure if they would still work.
Click to expand...
Click to collapse
GO HERE
press "unlock bootloader" and follow the instruction
press "unlock bootloader" and follow the instruction [/QUOTE]
Ok thank you. I am assuming that is my first step. Do I need to set up or install anything on laptop before i press unlock bootloader? Do I need to come back to get more of your directions or is that it?
crazyleopard77 said:
press "unlock bootloader" and follow the instruction
Click to expand...
Click to collapse
Unlocking the bootloader is fully guided on HTCdev.com. You will need more steps like installing a custom recovery and a superuser app using the custom recovery. If your not sure about what to do, you can use Teamviewer and i will perform unlocking / rooting for you
This toolkit may also help you WinDroid HTC Toolkit
LS.xD said:
Unlocking the bootloader is fully guided on HTCdev.com. You will need more steps like installing a custom recovery and a superuser app using the custom recovery. If your not sure about what to do, you can use Teamviewer and i will perform unlocking / rooting for you
This toolkit may also help you WinDroid HTC Toolkit
Click to expand...
Click to collapse
ok. i had just installed teamview both on phone and pc.
crazyleopard77 said:
ok. i had just installed teamview both on phone and pc. my id there is xxxxpassword isxxx name is Stephanie.
Click to expand...
Click to collapse
DONT POST ID+PASS PUBLIC!!!!!!!!!!!!!!!!!!! Set new password and send it via PM !!!!!!!!!!!!!!!!!!!!!!
Are you crazy????
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
bump
I don't think this will work unless we get our Bootloader unlocked (which hasn't been done yet as far as i know)
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
this is kind of lame.... why chainfire release a auto root if the thevice have bootloader locked down? and onlockable?
Confused myself
I want to say root is possible, there are tons of sites with instructions: https://www.google.com/search?q=SM-...i57j0j69i60.9343j0j4&sourceid=chrome&ie=UTF-8
Of course, XDA doesn't seem to have a specific G930T thread for rooting with instructions, then see threads like this today. I was all set to give it a try, but unsure if should proceed...
Did find this: http://forum.xda-developers.com/tmobile-galaxy-s7/help/sm-g930t-root-doesnt-void-warranty-t3415936
EDIT: so the one linked in original comment was the bleeding edge root process and seems like had a really high failure rate. Most current I've seen is: http://lifeatsamsung.com/root-t-mobile-galaxy-s7-sm-g930t-2/
Seems a little more clean cut and easy. I'll edit again if I find a newer solution or at least commentary on success/fail
In comments OP posts:
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
Click to expand...
Click to collapse
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
So the solution and all the fixes, etc is right here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Worked for me, no problem. Even installed the debloated, deox'd ROM. Unfortunately after root you will need to follow rest of guide, otherwise you will see some lag issues.
On the other side of it, phone is great, fast, if not faster than before, and got root. Let me know if you would like some screenshots proving a TMO phone is rootable or if can answer any questions
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Mordred said:
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Click to expand...
Click to collapse
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
TH3B0SS said:
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
Click to expand...
Click to collapse
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Mordred said:
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Click to expand...
Click to collapse
This means that the only rooting method right now isn't as stable as it would be if it had a unlocked bootloader the root right now will cause some issues but they can easily be fix from some of the steps after rooting guides that are in the xda forums and yes it using a Qualcomm processor Witch is pretty much the snapdragon and there hasn't been any luck this past year of getting the bootloader unlocked for full and smooth rooting I'm really ****ty at explaining sorry if your still lost
The Chainfire method he released does NOT work. I'm not sure why he released it...maybe he knows of a future bootloader unlock that we don't know about.
@troby86 I see you have yours rooted. How did you accomplish this?
Mordred said:
@troby86 I see you have yours rooted. How did you accomplish this?
Click to expand...
Click to collapse
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Thank you. Lots to look through.
troby86 said:
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Click to expand...
Click to collapse
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Mordred said:
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Click to expand...
Click to collapse
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
KillerClaw321 said:
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
Click to expand...
Click to collapse
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Mordred said:
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Click to expand...
Click to collapse
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
KillerClaw321 said:
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
Click to expand...
Click to collapse
Sorry for being daft... I don't see a driver link and how do I remove the previous version?
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.
Hi,
Unfortunaltelly my magisk cant hide gpay (safetynet true). Im wondering about unroot my pixel3.
Please tell me, which way is the best to unroot/lock bootloader? If I flash blueline-image with - w in flash-all.bat, can i lock bootloader with any problems (bricks)? Sorry for my english.
Thx for advice.
Wysłane z mojego Pixel 3 przy użyciu Tapatalka
If you successfully flashed the factory image (no errors) without removing the -w flag you should be able to relock the bootloader, yes. I believe locking the bootloader will induce another wipe so be sure you have things backed up if you have used the phone since flashing the factory image.
I have not rooted my devices since Pixel 1 and things have changed since then so someone else can chime in to confirm, but flashing the full factory image should be a reliable way to return to pure stock.
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
83097markcynt said:
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
Click to expand...
Click to collapse
That's good to know. I don't use gpay so didn't know that.
Unlocking Verizon Bootloader
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
I'm not sure what you're asking? Is what possible?
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
jd1639 said:
I'm not sure what you're asking? Is what possible?
Click to expand...
Click to collapse
You cannot unlock the bootloader on a Verizon device. It's software locked based on IMEI. The ones sold at Best Buy are Verizon versions and are fully locked.
Gpay works fine with magisk. If it's not working for you, I'd dig into why before unrooting and relocking.
If you don't want to do that, just flash the magisk uninstaller to get rid of root and then flash a custom kernel. Pretty much all custom kernels will hide an unlocked bootloader and allow you to pass safety net.
New here to this community.
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
NightWingJbr said:
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
Click to expand...
Click to collapse
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
jd1639 said:
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
Click to expand...
Click to collapse
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
NightWingJbr said:
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
Click to expand...
Click to collapse
See the "Factory reset via fastboot" section at https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
This will not remove the warning at boot, but is a necessary step. To lock the bootloader, read all the posts (especially the ones that detail the consequences of relocking) at https://forum.xda-developers.com/pixel-3-xl/help/how-to-lock-bootloader-t3866074 and pick a method.
I strongly recommend against relocking the boot loader, though. It is easy to brick your phone during the relock process. Also, a locked bootloader severely limits your ability to recover a bricked phone. Just ignore the warning at boot message. Removing it may come at a high cost.
Thank you so much. I will ignore then..
what is -w..
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
comic_nightwing said:
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
Click to expand...
Click to collapse
In the flash-all batch file in the factory image the -w (part of a line in the batch file) controls whether it wipes clean or does a dirty install leaving apps and data (user).