Related
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Hello everyone,
I am stuck while trying to root my new U11+. I can always get through every step until I have to use fastboot. Whenever I type fastboot devices nothing shows up. It does however show up in adb when it is fully booted up.
My phone is the International Version 2Q4D100 on firmware version 1.23.709.3. Even reflashing the correct RUU from the MicroSD card doesn't seem to fix the issue.
I have been at this the entire afternoon and keep hitting nothing but dead ends. Can anyone here maybe help me?
are you in "Download Mode" or "Bootloader Mode"? in Download mode, the top of the screen shows if your bootloader is locked/unlocked, etc. Bootloader Mode is where you select recovery, download mode, etc. you need to be in Download Mode to flash boot.img. fastboot works in Download Mode as well.
Yes, I was in Download Mode the entire time. I now restarted all my devices for the n-th time and finally got it working for me. I just can't quite figure out what the problem was...
And now another question came to mind: Will the phone still be able to pass SafetyNet with an unlocked bootloader and Magisk installed? I know that passing SafetyNet is the entire premise of Magisk, but I have not used it before.
warafreak said:
Yes, I was in Download Mode the entire time. I now restarted all my devices for the n-th time and finally got it working for me. I just can't quite figure out what the problem was...
And now another question came to mind: Will the phone still be able to pass SafetyNet with an unlocked bootloader and Magisk installed? I know that passing SafetyNet is the entire premise of Magisk, but I have not used it before.
Click to expand...
Click to collapse
Attached is screenshot of SafetyNet on my device which exactly the same as yours.
And mine.
Rooted with a patched boot.img in magisk app.
Unlocked bootloader.
m3johan said:
And mine.
Rooted with a patched boot.img in magisk app.
Unlocked bootloader.
Click to expand...
Click to collapse
Forgot to install Magisk in previous post.
Ok, thank you both for your pictures.
I think I will try going without root at first and see if I will miss it very much. But it is good to have this option available now!
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs
junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?
aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.
Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks
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).
Only to inform that after updating the row rom with march update, my problem with Netflix not working with widevine L1 was solved.
Before the update I had to install an old Netflix version (7.8) in order to work in full hd.
Great news!
thank you
Good news! May try my luck flashing this on my Chinese J706F in the near term.
blagoon52 said:
Only to inform that after updating the row rom with march update, my problem with Netflix not working with widevine L1 was solved.
Click to expand...
Click to collapse
Full HD is not working anymore in any version and this OTA (220312) does not contain any fix for Netflix, according to Lenovo technicians.
You are only seeing L1 and it's the same I can see with my tablet not updated but if you try to play test patterns you will see that definition played is 960x540.
We need to wait for the next OTA for a fix.
Is there still the "join Lenovo experience program" notification everytime tablet is restarted with this OTA?
I'm on TB-J706F_S210002_201015_ROW with bootloader unlocked + rooted, when trying to update to last OTA it just says "ota package installation failed", any solution?
MrCrayon said:
Full HD is not working anymore in any version and this OTA (220312) does not contain any fix for Netflix, according to Lenovo technicians.
You are only seeing L1 and it's the same I can see with my tablet not updated but if you try to play test patterns you will see that definition played is 960x540.
We need to wait for the next OTA for a fix.
Is there still the "join Lenovo experience program" notification everytime tablet is restarted with this OTA?
Click to expand...
Click to collapse
It is not showing since I made de update, but it comes with a new app called Tablet Center.
A bit off topic but I'd suggest everyone concerned with privacy to install NetGuard
It works kind of like a firewall without having root using a local VPN.
I am using it with whitelist so only apps and services I choose can access internet.
Not as powerful as AFWall+ but best alternative without root.
melones22 said:
I'm on TB-J706F_S210002_201015_ROW with bootloader unlocked + rooted, when trying to update to last OTA it just says "ota package installation failed", any solution?
Click to expand...
Click to collapse
OTA updates are not going to work if the system is modified, sometimes just unlocking bootloader will stop them I am not sure what's the case for this tablet.
I think the quicker way for you to update is to download the full ROM, make a backup of apps and data with something like Migrate, flash new ROM, restore apps.
MrCrayon said:
OTA updates are not going to work if the system is modified, sometimes just unlocking bootloader will stop them I am not sure what's the case for this tablet.
I think the quicker way for you to update is to download the full ROM, make a backup of apps and data with something like Migrate, flash new ROM, restore apps.
Click to expand...
Click to collapse
too bad, would have been great to avoid reflashing the rom again.
So from what I've understood no widevine L1 even with latest update?
melones22 said:
So from what I've understood no widevine L1 even with latest update?
Click to expand...
Click to collapse
With bootloader unlocked no.
With bootloader locked Widevine is L1 but the problem with Netflix not playing Full hd it's not solved yet.
They are testing the fix and OTA update should have been released end of March but has been delayed.
MrCrayon said:
With bootloader unlocked no.
With bootloader locked Widevine is L1 but the problem with Netflix not playing Full hd it's not solved yet.
They are testing the fix and OTA update should have been released end of March but has been delayed.
Click to expand...
Click to collapse
so widevine L1 but useless in a nutshell :/
is it possible to patch boot.img to get root and then lock the bootloader again? (might sound like a stupid question but it's been years since I hadn't get my hands on an android device)
melones22 said:
is it possible to patch boot.img to get root and then lock the bootloader again? (might sound like a stupid question but it's been years since I hadn't get my hands on an android device)
Click to expand...
Click to collapse
Nope, bootloader locked is a guarantee that nothing has been changed so it wouldn't make much sense.
I always unlock and root my phones but for this tablet I am still holding, what do you need root for?
NetGuard works sufficiently well as a Firewall but sure backups suck without root.
MrCrayon said:
Nope, bootloader locked is a guarantee that nothing has been changed so it wouldn't make much sense.
I always unlock and root my phones but for this tablet I am still holding, what do you need root for?
NetGuard works sufficiently well as a Firewall but sure backups suck without root.
Click to expand...
Click to collapse
I see!
My phone is an iphone jailbroken, so it would be sad if I would not be able to mess with android too adblocking is one of many examples ! hadn’t checked what magisk permits but I assume it’s similar to Cydia in a way
Ad blocking works with NetGuard, but if you want to have fun messing around (I totally understand the feeling) I would suggest to:
Unroot and lock bootloader again
Make a full backup with QFIL or edl
Unlock again and install a GSI rom
Have fun
BTW I never had an iphone but for what I remember Cydia just let you install software that is not in the app store, you can do that with Android without any effort.
Magisk is totally another level of personalization at system level.
Well Cydia is like Magisk then, you can customize whatever you want, like adding live weather particles on your homescreen, replace the phone app ui, put a cool live equalizer effect when a music plays on your lockscreen/homescreen/control center... anything!
if anyone needs a guide to get bootloader+twrp+root without having a headache (i haven't been able to found latest update rom file online so I dumped boot.rom myself) :
0. Dowload , unzip and rename img file to twrp.img https://www.mediafire.com/file/wdpxfr5t2z4mrye/TWRP-3.4.2B-1208-LENOVO_TBJ706F.zip/file
1. Enable OEM unlock in developers settings
2. Reboot in bootloader (adb reboot bootloader)
3. In bootloader enter :
Code:
fastboot flashing unlock
and answer yes when you're ready
WARNING: UNLOCK BOOTLOADER WILL WIPE YOUR DEVICE!!!!!
4. Run LMSA/RSA rescue to update your ROM as well as grab boot to patch
5. Do initial setup. DO NOT RESTORE
6. Install Magisk
7. Enter fastboot and enter :
Code:
fastboot flash recovery twrp.img
8. Reboot to TWRP (Vol up + Vol down + Power)
9. Get in shell (adb shell) and enter dd if="/dev/block/bootdevice/by-name/boot_b" of="/sdcard/boot.img"
12. Reboot and open Magisk, hit Install and select your boot.img freshly dumped
13. Transfer patched img to your pc and rename it to patched_boot.img
14. Go back to fastboot, enter :
Code:
fastboot flash boot patched_boot.img
15. Reboot and add riru and safety net fix on Magisk (you have to reboot 2-3 times)
16. Run safety net check and it should pass. If not, enable Magisk Hide and try again
17. Wipe Play Store and Google Play Services and reboot
18. Restore and add app onto hide list if the app detected root
Troubleshoot :
- TWRP will ask for a password if your device has pin/pattern to unlock, disable it to get access to user data
- wtf why my touch screen is glitched after going to TWRP? idk it's odd but just reboot and it'll be fixed
- Play store not installing apps? Format your SD card to external storage
- Can't install Netflix and other apps claiming to be uncompatible ? add play store in magisk hide then clear play store & google play services cache/data
(modified guide from https://forum.xda-developers.com/t/...-if-running-android-11.4374645/#post-86108685)
Great, I was looking for a guide like this for rooting since I may do it later on with my p11 pro, thanks!
frogduck said:
Great, I was looking for a guide like this for rooting since I may do it later on with my p11 pro, thanks!
Click to expand...
Click to collapse
no problem! it took me a lot of time to figure out everything since it's the first time i'm using adb and stuff, but i'm so happy with the final result :d
I saw this tutorial on 4pda to return Widevine from L3 to L1, i didnt tried yet.
https://4pda.to/forum/index.php?showtopic=1018820&st=1000#entry113135411 (use google translate)