Database Users

[Q] Nexus 4 not bootin afer modifying build.prop :(

Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd

1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....

AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.

AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r

Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false

AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again

If you can enter recovery do a factory reset

Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem

no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok

Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.

Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909

[GUIDE] How To Unlock Tethering on Nexus 5X.

I'll start off by saying I didn't come up with any of this method myself, its just different information I found scattered on different threads on XDA and Reddit. Maybe some other 5X users will find it useful contained in this thread.
Secondly, this requires an unlocked bootloader, also working adb and fastboot with correct drivers for your 5X, enable USB debugging. I won't go over that here, there are plenty of other guides on how to do that, and know that it will erase all your data. As long as you can find your device via "adb devices" and "fastboot devices" you should be fine.
Lastly, you will get the corrupt data message on phone startup. I don't see any negative effects with this, other than an annoying message. Also I'm still able to use the fingerprint scanner as well as set up Andoid Pay. I can't verify Android Pay as I don't have any stores near me that accept it.
You also won't have to flash any custom recovery or root the device, which keeps it closer to stock, which hopefully will allow Android Pay to still function, hopefully someone with a Android Pay store nearby can test this to verify.
First grab TWRP for 5X from here. Save it in the same folder as your adb/fastboot install.
Make sure your phone is connected to your computer, open command prompt and verify adb sees your phone.
Code:
adb devices
Now reboot to bootloader.
Code:
adb reboot bootloader
Now we boot from TWRP without having to flash/install it.
Code:
fastboot boot twrp-2.8.7.0-bullhead.img
When TWRP finishes booting, click Mount and check the box for /system
Now we need to pull the build.prop file.
Code:
adb pull /system/build.prop
Using a text editor add this line to the end of the build.prop file and save it.
Code:
net.tethering.noprovisioning=true
Now we push it back to the phone.
Code:
adb push build.prop /system/
Make sure the permissions are correct.
Code:
adb shell chmod 644 /system/build.prop
And lastly
Code:
adb shell settings put global tether_dun_required 0
Now we just reboot
Code:
adb reboot
and your tethering should be working!
I'm currently using this method and it is working for me. I'm on Verizon with a Grandfathered Unlimited Plan, so I can't test it for any other carriers.
Most of this information I pulled from this reddit thread, I just did my best to condense it down and simplify it, and make it aimed toward the Nexus 5X specifically.
edit* People are confirming on the Reddit thread on their Nexus 6 that Android Pay is still working after making these changes!

Thanks! This works exactly as stated, even the "corrupt data" warning on boot.
I will add that - this being my first Nexus device since a Galaxy Nexus - the "fastboot oem unlock" step needed prior to this guide has an additional step where you have to enable the "OEM Unlock" option in the Developer Options menu, within the booted system. After confirming this you can unlock the bootloader via the standard "fastboot oem unlock" command prior to starting this guide.

Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!

Thanks. Worked great for me. I'm on AT&T, weird thing though, I never had any problem activating the hotspot on my OG Nexus 5.

AWESOME!

added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up

Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?

olivercervera said:
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?
Click to expand...
Click to collapse
This method bypasses the subscription check for tethering, those of us with unlimited data have to pay a separate fee to use tethering with Verizon, and this fixes that. It should be the same for other carriers as well.
Sent from my XT1060 using XDA Free mobile app

I was so excited to play with my 5x when I got home (that and dealing with my 2 sick kids) and I completely forgot to unlock the bootloader before I got too carried away. Now all the time I spent downloading apps and such is lost. Our DSL connection is slow, so all that took one time. I've been rooting and romming way too long to make such a rookie mistake.
So, I get the joy of blowing the whole thing way and re-setting it up again...

XF1ber said:
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
Click to expand...
Click to collapse
Could you confirm the steps?
Can you confirm you can still use supersu? I thought the kernel had to allow su.
Also, I guess you can also install the bootunlock app and see if that works?

Thank you thank you thank you!
This is huge for me.
BTW, I assume you can just push the original unmodded build.prop back for OTA updates. Anyone know if anything else is required apart from that?

Confused on why we need TWRP just to do this.

You're not flashing twrp, just booting into it. Twrp allows you to pull and push files to /system without root, which is needed to make these changes.
Sent from my Nexus 5X using XDA Free mobile app

Can someone confirm Android Pay actually works?
Sent from my Nexus 5X using Tapatalk

T-Mobile/MetroPCS users additional steps to enable tethering
If you are on T-Mobile or MetroPCS you will need to perform some additional steps for tethering to work. After you have performed the steps outlined earlier in this thread do the following:
Under Settings -> More -> Cellular Networks -> Access Point Names
Touch the name of the APN that is selected (there may only be one) then:
1) change "APN Protocol" to "IPv4"
2) change "APN roaming protocol" to IPv4
3) Edit "APN Type" and add "dun" to the comma separated list so it reads something like "default,supl,mms,dun"
4) OPEN THE MENU IN THE UPPER-RIGHT AND CHOOSE SAVE!
5) You MAY have to reboot for this to take effect

Ok needing it for that reason makes sense now.

So... I'm getting about 30% packet loss on att with my 5x.
If I take my sim out and pop it into my nexus 6(also with marshmallow), everything is fine.
Could someone with att run some extended pings from a device connected to your phones tether and note any ping drops?
I don't know if this is a sw bug, or hardware issue.

Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X

Ascertion said:
Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X
Click to expand...
Click to collapse
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?

MarkGbe said:
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
Click to expand...
Click to collapse
Ah my bad. It's not reading my /sdcard partition. No matter. That's what adb is for. Please disregard my post. I'll update my progress when I get home later today and try it on my personal PC.

[script]Remove password/fingerprint lock

Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.

great. will try

thanks!

animehq said:
Hi all,
I made this small update script because sometime when you try a rom and use a backup to restore the previous one the authentification get broken, so this script will just remove all locks and allow you to start your phone without any data lost.
I'm not responsible if something is going wrong.
Flash using any twrp will probably work.
Click to expand...
Click to collapse
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.

Great will try

c_/\/\_k said:
well we can delete gatekeeper files manually from the TWRP file manager, and everything is fine, no data lost.
Click to expand...
Click to collapse
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster

animehq said:
Yep probably, but for most of people here it's safer to use a script than let them find the files manualy.
And maybe faster
Click to expand...
Click to collapse
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..

Does it also removes the mi account? Device locked because mi account think the device is stolen.

c_/\/\_k said:
you deserve compliment for your work , but it takes only one file to delete to remove passwords or lock. and its neither lengthy nor unsafe, i have seen your script, it deletes to many things.. which is not required i think. And your updater script has spelling mistakes too bro..
Click to expand...
Click to collapse
Which file do you think is the only one to delete?

Rohit DK said:
Does it also removes the mi account? Device locked because mi account think the device is stolen.
Click to expand...
Click to collapse
Nop sorry and there is no easy way to do it as far i know.

Bogeyof said:
Which file do you think is the only one to delete?
Click to expand...
Click to collapse
If its patternlock, then its gatekeeper.pattern.key, if its password then its gatekeeper.password.key, you can delete both.

Successful Using RX & Deletion of /data/validity/template.db
Doesn't work for me! Ran rx from recovery, wiped caches, & rebooted. Typed in backup password, unlocked (same as b4). Went to the Settings for fingerprint this time it constantly rejects any attempt saying too many incorrect pls wait. Prior it wouldn't take fingerprint or password.
Any suggestions for this?
PS: Would be nice to list what each file does /is for. I am also an advanced user...
After running This Rx use (root) X-plore/etc F. M. Then DELETE:
[*W/Rx SUCCESS*] /data/validity/template.db [*W/Rx SUCCESS*]
Reboot. Type in Previously Used BackUp Password. Go to Fingerprint Settings & setup new fingerprint & backup password!
[*MIA*] data/system/users/0/settings_fingerprint.xml [*MIA*] Could not find this file, so I assume not needed.
This was done on Stock Base Marshmallow ROM N915 (Note Edge).
BTW Thanks for RX & Could You Please add the above file to RX?

6055U Root method found

Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu

F
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...

http://forum.gsmhosting.com/vbb/f606/vf-895n-smart-prime-6-stock-rom-flash-tool-2033867/
This should help with setting up sugar. The only difference here is to update it and you also need a username and password that I don't have on me at the moment. It will be a few hours until I get home but I will update asap.
Edit: nevermind lol, good luck friend. You may need a decent battery percentage as well

pauljulian said:
F
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
Click to expand...
Click to collapse
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:

pauljulian said:
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
Click to expand...
Click to collapse
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
---------- Post added at 03:36 PM ---------- Previous post was at 02:40 PM ----------
pauljulian said:
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
Click to expand...
Click to collapse
My point is that the site recommended seems to insist on Lollipop on the small beast... and there doesn't seem to be a recommendation for the .bin files, and, when installing on Win 10, it seems to install the Sugar app into some directory on my C: drive that is really not that accessible... Did it using a VMWare Win 7 32-bit virtual, and was able to access the directory, copy and paste to my regular C: drive (old Windows geek since Win 3.11... and DOS 3), and it seemed to run... (of course, running as Administrator), but it really doesn't seem to work for me... Again, I freely admit that I'm likely not doing something right, but even after some research and the included .chm file, I seem to be missing something.
Again, and begging your indulgence for seeming like a noob or a rube, but if I'm not making it happen, I rather think that the tips would be lost on someone for whom this is their first Android device...
Kinda frustrating, as, even though I've been a tech-support guy and database developer for more than 30 years, this thing has me stymied...
I found it fascinating for the *#*# command, earlier, from another noble soul, and, obviously, I also found that the device as configured says, basically... "Don't give a damn... you can turn this sucker on, but as soon as you exit this menu, I'm gonna turn it off again."
Just a little frustrating, and it seems that most of the tips and tricks elsewhere seem to be thinking that new owners of the 6055U are running Lollipop.... aaarrrgggghhh....
If it needs Lollipop to work, and if there's a relatively painless way to downgrade, and then upgrade from a ROM, I'm good with that... the Idol 3 seemed to require that, and it worked well for me, with just an evening's work. This one? Cricket seems to have had a warped sense of humor about it... I seriously dig the device, and, since my Idol 3 broke, and my lovely wife's LG G-Stylo (which was a pain in the ass, and next-to-impossible to root, and then be just perpetually stuck at the logo screen with an unfixable boot loop, if one screwed it up, and just required sending the beast back to LG, as long as one took out Cricket's warranty plan... <sigh>), we took the plunge on this one...
Not much for which I require root, but, since I spent good money on some legit apps (and lucked into a few ... ahem... not legit apps that worked for me), these things require root... I know there's a way to do it, and the Sugar app seems promising, but, mildly autistic guy that I am (and 60 years old, with a memory that doesn't work as it used to), a slimmed-down step-by-step doc would be helpful... should some noble soul put such together...
Apparently, the root method has worked for at least one member here.... But this weird old Jewish hippie doesn't see the mental diagram....
Any help would be welcome, my friends and mishpocheh... ("dear family" --- been here enough years, albeit a relatively quiet member, that y'all might as well be family... )

Hey everyone, sorry about the confusion. I installed on Windows 10 pro with no issues. As far as the page I linked you can disregard everything but the app itself. The update that downloads is marshmallow, and I've had no issues overwriting the latest version. I may have gotten sugar from a different location though, as soon as I get a chance I will do a better write up with everything. A helpful way to find the install directory would be right click on the shortcut from the start menu and click find Target / open file location. If it brings you to the folder with the shortcuts do it again and you will have the install directory. The app should be in (install dir)/tool and the downloaded updates go in (install dir)/bin under a folder that only shows up once you start the process within sugar. I will try to compile the information into a more user friendly format tonight but I can't make any promises on that.

Also just to clarify, I didn't use any chm file

I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond and all the recover videos apps require root

I got this to work last night. Typed up some instructions but didn't get them posted. They're on my PC at home and I'm at work.
Basically use the copy of sugar in the download package in this thread and then start it and let it update https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Those are the basic instructions too except we don't need to swap out bout and use the TWRP from deckersu thread.
Once flashed it'll automatically reboot. I found you had to make sure you caught this and booted into TWRP right away don't let the phone boot. Then transfer SuperSU in TWRP and flash.
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Asadullah said:
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond an ind all the recover videos apps require root
Click to expand...
Click to collapse
FYI this root method wipes your phone so I don't know if this will help your situation or not.

In sugar there is an option to not wipe, it's under session settings or something to that effect

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!

dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Appreciate the help

woodi5359 said:
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560.
Click to expand...
Click to collapse
Thank you for finding this thread, it is the same one I found but I couldn't remember where it was the other day when I started this thread. Hopefully this will help the people who have been having issues, although I will admit a more painless method would be preferable. I'm currently working on modifying a dirtycow exploit to simply flash the recovery and reboot into twrp, if I get it to work I will zip it all up and post it here.

woodi5359 said:
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
Click to expand...
Click to collapse
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
I just tested this and it indeed does work. Great find friend!

Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
Thanks for figuring this out!!! I'd been messing with it for a few days. The renaming the apk to .oat was the piece I was missing. That and a reboot got it working!!

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
so im getting ready to purchase this device so there is root and twrp for it or no

Dude, did you read the thread at all? I don't mind helping but you gotta do your part. Yes there is TWRP and Root

dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
do you hold volume down when it reboots

link22534 said:
do you hold volume down when it reboots
Click to expand...
Click to collapse
It's volume up and power

[EXP] Verizon Pixel/Pixel 2 (& XL) Potential Bootloader Unlock Method

Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
How to enable the experiment:
Download the attached APK
Sideload the APK
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[ ] com.pixeloembypass" is in the list
Type in "cmd overlay enable com.pixeloembypass", and hit enter
Reboot the phone
Go into Developer Options to see if "OEM unlocking" can now be toggled on. If so, congratulations!
If "OEM unlocking" is able to be enabled, do so, and reboot the phone into fastboot mode. Unlock as per directions on the factory images site.
NOTE: As usual, if bootloader is unlocked/relocked, a factory reset will be performed.
How to uninstall the experiment:
Open Command Prompt/PowerShell/Terminal, and type in "adb shell"
Type in "cmd overlay list" and hit enter
Confirm that "[x] com.pixeloembypass" is in the list
Type in "cmd overlay disable com.pixeloembypass", and hit enter
Go into Settings->Apps, and uninstall "Pixel OEM Bypass"
Reboot the phone

This is amazing! Will try it here in about an hour and report back

Maybe tell these guys. They've been at it for a while. You might even get the bounty.
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652

TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So? Come on dj! Lol
Sent from my Pixel 2 using XDA-Developers Legacy app

djkinetic said:
TBH I have serious doubts about this working im inclined to believe this is just an overlay to make the toggle look visible but doesn't actually toggle anything when u try to push the toggle..I'll try it out in a few minutes
Click to expand...
Click to collapse
have more faith.. john mccain posted it after all

Hope it works
Sent from my Pixel 2 XL using Tapatalk

PresidentMcCain said:
Since Android O implements a mechanism for us to "overlay" frameworks values via OMS, I thought maybe we could leverage that to find a way to disable the OEM unlock check that block Verizon Pixels from unlocking the bootloader.
For science, let's do an experiment If this works, then great, we have a bootloader unlock method for our Verizon brethren. If not, at least the APK is easy to uninstall.
Before proceeding, be advised that any experiments performed here may result in unforeseen consequences. By proceeding, you agree that neither I nor anyone else will be held responsible for said consequences, and that this will solely be at your own risk. Since this experiment applies only to Verizon phones, assume all warranties are null and void.
Prerequisites:
- Verizon Pixel/Pixel 2/XL
- Android OS updated to 8.1.0
- USB debugging enabled on the phone
- ADB installed and properly configured on your PC
- USB-C to USB-A cable (unless you have a USB C port on your PC, then you can use a C-to-C cable instead)
Click to expand...
Click to collapse
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Edit:
I downloaded it on my phone just to see what permissions is calls for and it doesn't open the file.

Didn't work for me. Any tips to try?

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything

elliwigy said:
u can decompile the apk lol.. pretty sure its just an overlay thats suppose to "ungrey" the oem unlock switch to allow u to toggle it.. had afew ppl trying it.. first report it didnt do anything
Click to expand...
Click to collapse
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.

thompatry said:
Ehh I am just lazy to decompile it. Just tell everyone what's inside of it from the get go and move on from there.
I figure it wouldn't work but hey, worth the try.
Click to expand...
Click to collapse
i understand lol.. when im lazy i just use a file browser n view as an archive lol

collinjames said:
Didn't work for me. Any tips to try?
Click to expand...
Click to collapse
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed

thompatry said:
Have you tested this? Also what is all included in this APK? My concern is just installing random APK files that are added to a forum. Sorry, I am not trying to be a Debbie downer.
Click to expand...
Click to collapse
That's okay, it's completely understandable. I agree - typically, you wouldn't want to install a random APK built by a stranger.
I wish I could test it myself, but both my Pixels are from the Google Store, and shelling out $650+ for a test device for a shot-in-the-dark experiment doesn't sound like very responsible spending.

Tried on my P2XL device and no luck..

nelsonTituaAa said:
Tried on my P2XL device and no luck..
Click to expand...
Click to collapse
Thanks for volunteering...have you gave this a try?
PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse

nelsonTituaAa said:
oops.. no haha.. will try again
Click to expand...
Click to collapse
PresidentMcCain said:
Thanks for volunteering...have you gave this a try?
Click to expand...
Click to collapse
tried it and still no luck.

PresidentMcCain said:
Only thing I can think of is, after step 6, do this:
Code:
cmd overlay disable android.auto_generated_rro__
And then reboot.
To revert, just re-enable it and reboot.
If it still doesn't work, then I'm afraid the experiment failed
Click to expand...
Click to collapse
Tried the command and doesn't seem like it disable android.auto_generated_rro__ on the overlay list.

tried this plus added recommendation and no luck. Verizon Pixel, 8.1

Anybody tried this on a Verizon Pixel 2? I'm willing to give it a shot, but would need a little more detail on the procedure if anyone is willing to help out.