Related
i have a droid razr max hd XT926 (verizon) is has 4.2.1 android installed ..but it is so buggy and i want uo upgrade it to kitkat which is available in system updates ..i want to ask if i update to kitkat will my phone be locked to verizone sim cards only or i can use other providers sim cards as well i live in pakistan .
desperately waiting for answer .sorry for bad English or if i double the post
thanks.
mshayan27 said:
i have a droid razr max hd XT926 (verizon) is has 4.2.1 android installed ..but it is so buggy and i want uo upgrade it to kitkat which is available in system updates ..i want to ask if i update to kitkat will my phone be locked to verizone sim cards only or i can use other providers sim cards as well i live in pakistan .
desperately waiting for answer .sorry for bad English or if i double the post
thanks.
Click to expand...
Click to collapse
If your are on GSM networks outside U.S., it won't be carrier locked to Verizon, whatever ROM you're using. SIM lock on GSM networks is only valid in U.S. by default (though could be worked around).
So you can upgrade to KitKat, your phone won't be SIM locked.
nagim said:
If your are on GSM networks outside U.S., it won't be carrier locked to Verizon, whatever ROM you're using. SIM lock on GSM networks is only valid in U.S. by default (though could be worked around).
So you can upgrade to KitKat, your phone won't be SIM locked.
Click to expand...
Click to collapse
thanks nagim your reply gave me hope but on inserting other sim it wil give me a message that sim is from other provider if i am not wrong and i just need to ignore it? ,furthermore i want to ask if this kitkat update is buggy or not? like on my current jellybean there are lots of bugs and wifi sometime dont connect fone to internet,some random errors etc..
mshayan27 said:
thanks nagim your reply gave me hope but on inserting other sim it wil give me a message that sim is from other provider if i am not wrong and i just need to ignore it? ,furthermore i want to ask if this kitkat update is buggy or not? like on my current jellybean there are lots of bugs and wifi sometime dont connect fone to internet,some random errors etc..
Click to expand...
Click to collapse
It will probably say that SIM is from unknown source, but you can ignore this, it won't affect your usage.
I cannot comment on the KitKat update, as I have not received my XT926 yet. You could check out the topics in the forum like this one:
http://forum.xda-developers.com/showthread.php?t=2771542
nagim said:
It will probably say that SIM is from unknown source, but you can ignore this, it won't affect your usage.
I cannot comment on the KitKat update, as I have not received my XT926 yet. You could check out the topics in the forum like this one:
http://forum.xda-developers.com/showthread.php?t=2771542
Click to expand...
Click to collapse
thanks a lot ..
mshayan27 said:
thanks a lot ..
Click to expand...
Click to collapse
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
nagim said:
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
Click to expand...
Click to collapse
lol i am newb to this phone lets see what happen
nagim said:
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
Click to expand...
Click to collapse
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
iBolski said:
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
Click to expand...
Click to collapse
Thank you for this info, I wasn't aware of that. Surely saved us from some troubles! :good:
nagim said:
Thank you for this info, I wasn't aware of that. Surely saved us from some troubles! :good:
Click to expand...
Click to collapse
No biggie. The latest soak I believe just started getting pushed out in the last couple of days. I was part of the soak test, but I've since gone back to CM11 which is better IMHO, especially with the WiFi.
mshayan27 said:
lol i am newb to this phone lets see what happen
Click to expand...
Click to collapse
After what iBolski wrote, I would suggest that you look around the forum, see how you can flash the firmware. Remember, always read twice if you're not sure what you're doing!
iBolski said:
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
Click to expand...
Click to collapse
i think my phone is still a verizon because on inserting my sim it still gives me error that simcard is from other user but my simcard does works normally well now the question is is my phone still lock with verizon or how can i unlock it i have no information i just brought fone yesterday from a local market and give me some links to get the best kitkat on my fone ultimatly i just want it to wirk perfectly fine like a free phone with no errors and bugs
thanks
iBolski said:
No biggie. The latest soak I believe just started getting pushed out in the last couple of days. I was part of the soak test, but I've since gone back to CM11 which is better IMHO, especially with the WiFi.
Click to expand...
Click to collapse
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
mshayan27 said:
i think my phone is still a verizon because on inserting my sim it still gives me error that simcard is from other user but my simcard does works normally well now the question is is my phone still lock with verizon or how can i unlock it i have no information i just brought fone yesterday from a local market and give me some links to get the best kitkat on my fone ultimatly i just want it to wirk perfectly fine like a free phone with no errors and bugs
thanks
Click to expand...
Click to collapse
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
nagim said:
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
Click to expand...
Click to collapse
i have no idea about boot loader lock ...i am talkin about simlock and i was asking if i update it to official kitkat will it then work in my country (pakistan)
nagim said:
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
Click to expand...
Click to collapse
You're surprised? Why? They don't want unlocking the bootloaders on the XT926s in the first place. The whole bootloader unlocking of the XT926 was due to a security exploit, not because Moto allowed it.
On JB, there was a version that allowed the bootloader to be unlocked until they patched it.
Then, when the initial Kit Kat OTA came out back in May/June, they accidentally re-introduced the bootloader unlock exploit. After the initial OTA, another soak test started and with that, they fixed the exploit again, so nothing surprising there.
This is the FXZ you want to flash to your phone (do NOT take the OTA just in case it's the latest soak which patches the exploit that was re-introduced with the first KK OTA) -> http://sbf.droid-developers.org/download.php?device=5&file=902
Go here to learn how to flash it and then unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
iBolski said:
You're surprised? Why? They don't want unlocking the bootloaders on the XT926s in the first place. The whole bootloader unlocking of the XT926 was due to a security exploit, not because Moto allowed it.
On JB, there was a version that allowed the bootloader to be unlocked until they patched it.
Then, when the initial Kit Kat OTA came out back in May/June, they accidentally re-introduced the bootloader unlock exploit. After the initial OTA, another soak test started and with that, they fixed the exploit again, so nothing surprising there.
This is the FXZ you want to flash to your phone (do NOT take the OTA just in case it's the latest soak which patches the exploit that was re-introduced with the first KK OTA) -> http://sbf.droid-developers.org/download.php?device=5&file=902
Go here to learn how to flash it and then unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Click to expand...
Click to collapse
OK, my bad then again. When I first heard about this, it sounded like and official thing. But maybe I confused it with the Developers Edition.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
mshayan27 said:
i have no idea about boot loader lock ...i am talkin about simlock and i was asking if i update it to official kitkat will it then work in my country (pakistan)
Click to expand...
Click to collapse
It will work.
nagim said:
OK, my bad then again. When I first heard about this, it sounded like and official thing. But maybe I confused it with the Developers Edition.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
It will work.
Click to expand...
Click to collapse
Correct, the developers edition can always be unlocked, no matter what. But, not many have the developers edition as it was a limited release.
Most XT926 devices are the non-developer's edition and can only be unlocked via an exploit.
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Jut install SuperSU ZIP using TWRP recovery
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Could you read my post first?
squid2 said:
Your bootloader must be unlocked to use this recovery.
Click to expand...
Click to collapse
unlocking bootloader = voiding warranty.
shawly said:
Could you read my post first?
unlocking bootloader = voiding warranty.
Click to expand...
Click to collapse
If you're worried about voiding the warranty, you're on the wrong site.
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
I used to root in one click in just one method on my previous phone xperia sp but i dont know this phone have any toll which will work or not?
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
---------- Post added at 10:39 AM ---------- Previous post was at 10:33 AM ----------
zephiK said:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.
Its like saying, you're going to break your windows to get into your house when you can just unlock the door.
Just unlock the bootloader and flash supersu for root.
Click to expand...
Click to collapse
Also this.
Ragarianok said:
Being a smartass is kind of my thing.
You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever.
Generally speaking, both KingRoot and TowelRoot are used on devices where using those two methods are the only way to root those devices.
Unlocking the bootloader will have no ill effect on your device other than voiding the warranty, and, if you're worried about voiding your warranty, you shouldn't be trying to modify your device.
In the words of the always optimistic Ms. Frizzle: "Take chances, make mistakes, and get messy!"
Click to expand...
Click to collapse
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, I also don't plan on using custom roms, I just want the root features so I can undervolt like I said and IF I could root it permanently without unlocking the bootloader, why not?
I'm not worried, it would just be convenient to have root without losing the warranty, that's it.
As far as I know you may be able to do it search kingroot in Google then download the apk and install it then open in and follow the instructions
shawly said:
Who said I'm afraid of unlocking the bootloader? Who said I never unlocked the bootloader of other phones before?
I just don't wanna lose my warranty in the first two or three months, in case my phone breaks unexpectedly, ...
Click to expand...
Click to collapse
Then leave the device stock ...
If you want the best of both worlds (root & warranty), then go buy a Nexus. Motorola drew a line in the sand as to what they will support, while still empowering owners with the option to unlock the bootloader.
Sent from my MotoG3 using Tapatalk
Ragarianok said:
If you're worried about voiding the warranty, you're on the wrong site.
Click to expand...
Click to collapse
Not really. While I've unlocked my previous phones, my new g3 I'm leaving locked for the first year, while the warranty lasts. But this site still has a few helpful stuff.
Ragarianok said:
...You're afraid to unlock your device's bootloader because you'll lose the warranty, but you're perfectly fine with risking the security of your device by rooting it, right? Seems odd to me, but whatever...if you're worried about voiding your warranty, you shouldn't be trying to modify your device...
Click to expand...
Click to collapse
He just wants the warranty, but he doesn't care about rooting it because there's not really anything wrong with rooting if you know what you're doing and how to fix it.
Sent from my MotoG3 using XDA Free mobile app
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
And to answer the question; you need to unlock the bootloader to root
Sent from my MotoG3 using XDA Free mobile app
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Jdwright0819 said:
Question, I attempted to use towelroot on my stock g3 and got a message saying my phone is not supported. Any help is greatly appreciated. Also, fairly newbish, so be gentle!!
Click to expand...
Click to collapse
Towelroot is exploiting a bug in the Linux Kernel in order to root a device. This bug was already fixed in June 2014.
On all Kernels with a later build date Towelroot will most likely not work.
For sure it will not work on the Moto G3 with a kernel build date more than one year after this bug was fixed.
Thanks!
shawly said:
Hi peps,
I just switched from my crappy HTC One X to my new Moto G3 and I'm in love!
I don't really want a custom ROM, but I'd like to undervolt this babe. But since a root requires unlocking the bootloader = voiding the manufacturers warranty, I don't really wanna do that..
I've bought it over Amazon and I live in the EU, so I technically still have the retailer's warranty and Amazon would replace it without a hassle, but yeah.. it's new and all.
But I know there are apps like towelroot, KingRoot and what not, do they work with the Moto G3? I'm on 5.1.1.
Click to expand...
Click to collapse
It's probably been answered already but those exploits are security flaws with the SE Linux system and so with each release of android these have been patched, by 5.1 these security holes have been fixed and now by locking the bootloader
It's like just locking down and modifications to the system partition so unfortunately you can't root without unlocking, unless you have android versions lower down
shawly said:
Thanks for this unnecessary input. :good:
On previous versions of Android there were exploits that allowed rooting the phone without unlocking the bootloader, which means you could keep your warranty and I just asked if it works on the current Moto G3 with Lollipop 5.1, why do you have to be such a smartass? It's a normal question, why can't I have a normal answer?
Click to expand...
Click to collapse
I have unlocked bootloader and i m on stock recovery amd on stock rom without rooted. Can i install twrp without pc
Are you root yet
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Ankur1 said:
I have moto g 3, its bootloader is unlpcked but when I tried to root it using SuperSU and twrp recovery then I ended up corrupting it software. Can anybody tell me how to safely root it...?
Click to expand...
Click to collapse
What version of TWRP did you use coz I know there were some bugs on the moto range with TWRP 2.X.
I would completely wipe device using stock recovery, including dalvic/cache/data everything just to be on the safe side, then download the TWRP zip to your computer and flash it on using ADB.
Boot up normally and move the superSU zip from the link to your phones internal storage. Then reboot to TWRP, select install and pick the zip file.
superSU.zip:
http://dl-1.va.us.xda-developers.com/3/6/5/5/4/0/1/BETA-SuperSU-v2.62-3-20151211162651.zip?key=u0OeGV4-4s02KJXqrXJ-gg&ts=1466705675
If you get stuck this might help:
https://motog3.com/unlock-bootloader-install-twrp-root-moto-g3/
No longer works
Osid said:
Jut install SuperSU ZIP using TWRP recovery
Click to expand...
Click to collapse
Perhaps you can offer wisdom on this? I rooted my Moto G 3rd Gen once, wrecked something and had to go back to factory, then try to reroot again. Problem. No matter what I do in setting the device back to factory, the bootloader stays unlocked and reads the system software as "modified" which then seems to bork installing SuperSU. I install SuperSU via twrp and it goes fine, no errors, but when I reboot the system is lost in a loop of the "bootloader unlocked" screen.
So I cannot RE-lock the bootloader (ala setting the phone back to true factory) and after I flash SuperSU the phone refuses to successfully bootup.
Any aid? Ideas?
I had failed to backup my phone the first time with twrp and so to set to factory I downloaded the stock retail xml.zip for my phone and reflashed the entire thing via fastboot. Reinstall twrp, and try to root and the endless boot loop begins.
So I came to this thread to look into the possibility rooting my phone via another means that MIGHT work.
Hi guys, just a couple noob questions:
I'm planning to update to Marshmallow but, if I don't like it can I go back to Lollipop?
This is because maybe I'll have bugs like most people here and also because I want to root it(when they find an exploit) and that can only be done while in Lollipop am I right?
Thank you for your help.
Yes you can go back to lollipop if you want by flashing lollipop firmware with flashtool.
There is root for MM.
Is there root?
But I have to unlock the bootloader right? I'll just wait until there's a way to root without doing that.
No that's not right if an exploit is found on marshmallow then there would not be need to go to lollipop unless the exploit was found on lollipop. Also marshmallow has far less bugs than lollipop. But as @gm007 said there is unlocked bootloader root and you can downgrade by flashing firmware with flashtool
Sent from my Xperia™ Z5 using Tapatalk
GeramanX said:
Is there root?
But I have to unlock the bootloader right? I'll just wait until there's a way to root without doing that.
Click to expand...
Click to collapse
In case if you didn't know, if you're waiting for root without unlock because of the loss of functions e.g x-reality etc., check this link:
http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
(Sony credentials restore after unlocking the bootloader), It simulates the sony credentials to get the sony functions back.
If you are waiting for different reason, just ignore my post.
Fleet.tw said:
In case if you didn't know, if you're waiting for root without unlock because of the loss of functions e.g x-reality etc., check this link:
http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
(Sony credentials restore after unlocking the bootloader), It simulates the sony credentials to get the sony functions back.
If you are waiting for different reason, just ignore my post.
Click to expand...
Click to collapse
Thank you for your help guys, I'll update to Marshmallow and just keep waiting, I'm familiar with waiting since the PSP and PS3 era.
I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
No
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
No
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
haha, thought so.
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
ShadowWeasel said:
Ever since I learned about the Google Pixel being unlocked and rooted with Verizon 7.1.1 version, I've been kicking myself for stupidly updating to 7.1.2. Well, it been a while and my phone is pressing me to update to 8.0. I've been searching for a temp root to edit the build.prop with no avail. My Question is after hesitating then giving kingroot one more shot for root access, is there a workaround for access? Here's what I have so far....
According to kingroot, it says "root successfully" however it also says "Notice: this model restricts ROOT authorization"
Looking at the OEM unlock from developer options, it's still greyed out.
Any help or solutions here?
Click to expand...
Click to collapse
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
Digital DJ said:
I have the Google Pixel on Verizon Android version 7.1.2 and Build Number NHG47Q with the latest August 5, 2017, security patch. Is it possible to unlock the bootloader and root? I purchased the Soft-Skip toolkit from mskip but have been unsuccessful trying to root and that thread doesn't have much action in it. I've read in a few other threads that it isn't possible to root with unlocking BL. So I'm confused and am wondering if any of you have other information.
Click to expand...
Click to collapse
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
Click to expand...
Click to collapse
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about bootloader and root.
---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------
ShadowWeasel said:
It claims to be rooted, but is not.... Any tips? I'm still trying both mobile and PC version. I'm kinda thinking of something between injecting thru ADB (not side loading) to finding out a way to decompile dePixel8 to make changes then recompile it to make it work. Only thing about the latter is it's years that I have done any type of actual programming and would like some steps from jcase or beaups.
---------- Post added at 02:15 AM ---------- Previous post was at 01:26 AM ----------
Here's everything I've done on rooting so far.... And supposedly kingroot apk is only way.
Others that failed includes kingroot (PC), iroot (both variants), kingoroot (both variants), skipsoft unified toolkit, Nexus root toolkit (don't ask, I leave myself open to possibilities), towelroot, z4root, pootroot, weaksauce, etc. (Even root methods as far back as to gingerbreak.)
One thing that is on my mind though is when you bring up the bootloader it shows it's being ran by Samsung?!? Any theories on that? I'm kinda leaning on looking backwards on how Samsung bootloader's were unlocked through ADB or fastboot. I remember back then there was a certain way of doing that, but my mind is moving so fast that I'm having a hard time remembering.
Click to expand...
Click to collapse
I don't have any tips. Just trying to clear up a misunderstanding about a unlocked bootloader and root.
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Sent from my Pixel using Tapatalk
baknblack said:
If I had the skills I think I would find someone with a pixel 2. Load an assembly language debugger and run the fastboot command that unlocks the pixel 2. If the same command could be injected into the pixels fastboot binary running on the phone you might trick it into unlocking just like the pixel 2.
Click to expand...
Click to collapse
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
ShadowWeasel said:
Assembly language debugger? Hmm. If this is true, wooden somebody had saved file and upload it to XDA? I'm getting curious now....
Click to expand...
Click to collapse
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Sent from my Pixel using Tapatalk
baknblack said:
Not many hackers are versed in assembly language. I've used it a few times over the years to patch an executable but, I had specific step by step instructions on how to do it. There are a lot of people around that know what they are doing but, I doubt we find them hanging around an android forum.
Click to expand...
Click to collapse
I may check the deep web for some answers
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Nick80835 said:
Knowing or not knowing assembly won't help, you cannot modify the bootloader in any way when it's locked basically making this a fruitless effort.
Click to expand...
Click to collapse
Don't need to modify the bootloader. Would just need to jump into the fastboot code in the same exact place with the same exact instruction that caused the rogue routine to run on the pixel 2. I would think it would be reasonable to assume the same coding bug that exists on the 2 might also be present in the other pixels. But, we'll never know unless someone with the knowledge were to try it.
Sent from my Pixel using Tapatalk
Tulsadiver said:
You don't have to have an unlocked bootloader in order to root. I've had plenty of Samsung's with root and no unlocked bootloader.
---------- Post added at 06:19 PM ---------- Previous post was at 06:04 PM ----------
In general an unlocked bootloader is not a prerequisite for root. I've had several phones with a locked bootloader but with root.
Click to expand...
Click to collapse
For the Pixel yes you do. You can't root without an unlocked bootloader
For what it's worth, it is relatively common any more, from what I hear, that an unlocked bootloader is required to root. The VS985 (Verizon) LG G3 was an exception in that the bootloader had an exploit that could be taken advantage of to effectively allow everything that an unlocked bootloader does. The HTC 10 is an exception in that you can just S-OFF and never unlock the bootloader and it's just as good if not better. There are always exceptions - when there are other avenues someone is clever enough to find, but as a rule going the other direction, if you can unlock the bootloader of a device, then you can usually easily root the device. As someone else said, on the Pixel, an unlocked bootloader has always been required to root.
so per xda rules i cannot post where to go to unlock your bootloaders on the nokia 6.1 but if you google search you will find it. it's $5 and you provide your IEMI and i had the code and was unlocked within 10 minutes.
im not a dev but id love to start a discussion on how to build twrp and achieve root. i wanted to extract my boot.img and try to patch with magisk but im positive you need twrp to see the partition scheme and temp root to make a system dump. since this is an android one device its possible it follows the pixel scheme and has a/b partitions which makes it even harder for development of roms. but root should be possible if we have someone with the knowledge how to achieve it.
i just wanted to start a discussion and see where this takes us. this is a nice budget device and it deserves root.
im still not sure why its against the rules here to pay for a unlock when jcase used to promote the sunshine app to s-off and unlock bootloaders for $25 per phone.
ive attached a screenshot of my unlocked bootloader so people don't think im full of it. i have the USA 32gb / 3gb ram model from best buy.
let the fun begin! :fingers-crossed:
What carrier do you use? Does your phone normally after unlocking bootloader?
Hedied4me said:
What carrier do you use? Does your phone normally after unlocking bootloader?
Click to expand...
Click to collapse
its a gsm unlocked phone but I use it on tmobile. yes its works fine. once you unlock the bootloader it does factory reset and wipe data.
it seems the only way to do a system dump is to buy a edl usb type c cable since we have no temp root or official firmware from nokia. if anybody has one of these cables and gets their bootloader unlocked we can get a system dump including the recovery.img to build twrp and the boot.img to patch with magisk.
I succed to unlock bootloader. I pay for it. I want to back up rom and find way to make custom recovery to flash magisk
why your bootloader ui is different ?
there's a word "one" after "android" ?
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
is there any twrp for nokia 6.1 ?
fix-this! said:
it seems the only way to do a system dump is to buy a edl usb type c cable since we have no temp root or official firmware from nokia. if anybody has one of these cables and gets their bootloader unlocked we can get a system dump including the recovery.img to build twrp and the boot.img to patch with magisk.
Click to expand...
Click to collapse
i have no knowledge to back up stock rom and recovery
Shame no magisk currently or I would be off to buy a unlock key! Bought this phone on contract a month or two ago and am kinda missing magisk.
Just got my Nokia 6.1 yesterday. Got it unlocked. Any updates on rooting with Magisk?
I'll try with it tonight to check if any chance to do twrp and root our Nokia 6.1
Maherabed1986 said:
I'll try with it tonight to check if any chance to do twrp and root our Nokia 6.1
Click to expand...
Click to collapse
Keep us updated... Thank you
Danny1976 said:
Just got my Nokia 6.1 yesterday. Got it unlocked. Any updates on rooting with Magisk?
Click to expand...
Click to collapse
How did u unlocked and rooted it please tell me i wanna improve battery life and want on Android P on it please help
Sameervillain said:
How did u unlocked and rooted it please tell me i wanna improve battery life and want on Android P on it please help
Click to expand...
Click to collapse
You should read/search more...
In almost every thread is link how to unlock (because people needs to talk about that everywhere), for now no option to root, unless we have TWRP or the boot image. And you need to wait for Android P, it should be out in August, I think...
Sent from my Lenovo TB-8704F using XDA Labs
fix-this! said:
it seems the only way to do a system dump is to buy a edl usb type c cable since we have no temp root or official firmware from nokia. if anybody has one of these cables and gets their bootloader unlocked we can get a system dump including the recovery.img to build twrp and the boot.img to patch with magisk.
Click to expand...
Click to collapse
I can buy the cable and try to do that. I never done it, but I can Google it and try it.
I ordered the cable yesterday. I will try to get the files necessary for TWRP.
Danny1976 said:
I ordered the cable yesterday. I will try to get the files necessary for TWRP.
Click to expand...
Click to collapse
No need i have it worked already need to fix last backup issues then boom
Maherabed1986 said:
No need i have it worked already need to fix last backup issues then boom
Click to expand...
Click to collapse
It only cost me $8, but I least I have it for future usage or to fix phone if bricked. Thanks for working on rooting this device. Everyone will be grateful for you time and work. I don't think I would have the knowledge needed to do it and would have had to do some research to learn about it. Thank you.
If someone make a twrp we can root it throw magisk. I am on android p
chriskleov said:
If someone make a twrp we can root it throw magisk. I am on android p
Click to expand...
Click to collapse
How us P compared to Oreo ? Speed and fluidity .?
I think oreo has better battery. P never stuck very quickly Rom and stable. Now that on holidays I found a new add. You can use phone and Google maps can run in.small window! Usefull .. the ROM came with the basic stock Google tools. I like it. I don't like that I can't make modifications like xposed remove some Google apps like player and add others. I don't like that Nokia hasn't software that you can unbrick your phone (lg has the lg bringe). I don't like that Nokia isn't official unlock the bootloaders.