First of all sory formy english
I did update two days ago,but I have problem with my phone,it is locking and loose signal telephone and 3g,also battery finishing quickly.What is the problem I tried to enter 3g options but *#*#4636#*#* not working,how can I back 4.1.2 version
thanks you all
You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr
cmh714 said:
You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr
Click to expand...
Click to collapse
yes I did but still same
trapper66 said:
yes I did but still same
Click to expand...
Click to collapse
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.
jewbydoo said:
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.
Click to expand...
Click to collapse
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do
trapper66 said:
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do
Click to expand...
Click to collapse
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.
iBolski said:
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.
Click to expand...
Click to collapse
Now,I have problem like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?
trapper66 said:
Now,I have problem like this
View attachment 2781977
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?
Click to expand...
Click to collapse
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.
iBolski said:
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.
Click to expand...
Click to collapse
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day
trapper66 said:
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day
Click to expand...
Click to collapse
There is no way to unlock it, ever. Don't wait for a fix, as there is no fix to unlock the bootloader. It was never meant to be unlocked. It was unlocked via a security exploit and that exploit was patched after 9.16.9. There is no way to "fix" it.
As for your phone restarting, I would say a factory data reset is probably your only cure. It wipes everything (including your internal SD card), so be sure to back up what you can, especially pictures, etc.
Related
Hi,
I've Xperia Z3 (T-Mobile) D6616 running on Android 5.0. I would like to install Android 6 on it.
I prefer to install Stock Rom of Android 6 On my Z3. Default , If there are a cool & good Custom ROM of Android 6.
I was not able to root it using Kingo Root too :crying: !!! Are there another way ?
Thanks
Get yourself another variant. The D6616 has a permanently locked bootloader. Flashing AOSP/CM-based ROMs is not possible.
stef-nix said:
Get yourself another variant. The D6616 has a permanently locked bootloader. Flashing AOSP/CM-based ROMs is not possible.
Click to expand...
Click to collapse
First, Thanks for you repay
My D6616 bootloader can be unlocked.
So, flashing AOSP/CM-based ROMs will be possible ?
Let you show the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's interesting, are you in Europe? or at least got your Z3 in Europe?
nadjibnet said:
First, Thanks for you repay
My D6616 bootloader can be unlocked.
So, flashing AOSP/CM-based ROMs will be possible ?
Let you show the picture:
Click to expand...
Click to collapse
how on earth. well try contacting t mobile and see what they say?
How was you able to get your bootloader Unlocked
lavin40 said:
How was you able to get your bootloader Unlocked
Click to expand...
Click to collapse
I have checked it before buying it
WHAT?! How?!
nadjibnet said:
I have checked it before buying it
Click to expand...
Click to collapse
Any idea? Can you ask the seller and maybe find out? That would be awesome if we could do it to ours too.
Sorry I can't because I leave this country.
nadjibnet said:
Sorry I can't because I leave this country.
Click to expand...
Click to collapse
Hello.
I'm in the same case (D6616 with unlockable bootloader) & I wanna know if there is any issue to install custom ROM. Did you successfully installed any other ROM on it ? or mayebe Rooted it? let me know please.
Root is possible and Recovery too, but there are no custom ROMs made for D6616.
I too have the tmobile z3 d6616, being used in the UK on ee......I wanted 32gb storage and only this model seems to have it out of the factory. Purchased via eBay from a seller in Hong Kong, fully expected it to be a used/fake phone but no, brand new genuine item complete with all the tmobile bloatware. Acording to the specs I can't get 4g in the UK as it has the wrong lte bands (3g is no problem and sufficient for me) though when I use mobile data it does say 4g on the screen.....anyway I digress, I too have 'unlock bootloader - yes' on my phone when you enter the service menu. Despite flashing roms/rooting/flashing different kernels on my old note 3/4 I am unable to take advantage of this feature as my developer skills are next to zero!
I also have this version of D6616.
I unlocked the bootloader and have tried various roms and other mods without much luck.
I wonder what the difference is in the devices (apart from the baseband) that stops us from flashing stock d6603 roms too it.
Maybe some devs can identify where we/I am going wrong
odunke01 said:
I also have this version of D6616.
I unlocked the bootloader and have tried various roms and other mods without much luck.
I wonder what the difference is in the devices (apart from the baseband) that stops us from flashing stock d6603 roms too it.
Maybe some devs can identify where we/I am going wrong
Click to expand...
Click to collapse
If someone who knows how to use adb could pull the partition layout and upload it in a Google Doc and link it or pm to me I could take a look at it. I think that the partition layout is different and that's why other roms or ftf will not work. You can run this command in adb shell
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
Thanks
https://docs.google.com/document/d/1Nl5Egwt4ubXDRpLNOEzVQRu0gNk2lxO2ad7nUkNTkD0/edit?usp=sharing
Sorry it took so long, I am at work and had to install SDK etc.
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
Comparing it to http://forum.xda-developers.com/z3/general/dev-d6603-stock-partition-table-t3288687
I can see no difference except for the extra 3 partitions on the end. (that is if the order doesnt matter only the numbers on the end of the partitions, if it does, then that could be our problem)
Btw, I relocked my bootloader before doing this, would that be a problem? (i dont think it would be)
I have the same model D6616 , would you please tell me how you unlocked your bootloader and which custom rom you preffer to install in it?
D6616
You can unlock boot loader but then you have just unstable custom MIUI V7 miui_Z3_liupan_6.6.17_4.4rom with no camera and Jaguar_Leo_December 14. rom a bit unstable.
So, after so many tries and soft-bricks ( once I had to press reset button for 120 sec with power wire +5 -5 V directly on magnetic pins ), I will stay with STOCK KK rom.
Hello! I have a D6616 and I successfully unlocked the bootloader, I successfully installed TWRP 3.0.2; Now the phone and my windows pc believe it is a Sony Xperia Z2. I love playing with Android and Sony products, don't you?
I tried the flashtool from XDA but no luck;
1. on the Z3 I press & hold "volume down" and plug in the USB cable,
2. the phone starts in "flash" mode, the XDA flashtool will recognize the phone,
3. I d/l-ed the appropriate .ftf file for the D6616, I attempt to flash the .ftf file,
4. the phone will reboot (idk why) and enter a boot loop until I manage to repeatedly press "volume up" and "volume down" and TWRP comes up.
I'm stuck, anyone at all that can help me out...please lend me any useful advice!
Could you please let us know how you unlocked the bootloader?
Guys please help! If anyone can get XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml stock rom please send the link... my moto turbo is soft bricked but no rom is flashing and recovery shows this "motorola/quark_reteu/quark_umts6.0.1/MGPS24.107-70.2-7/7"
bootloader locked and cant boot to enable unlock
Several Indians (including me) are facing the same issue as the desired version of stock rom is not available in the internet. Visit moto service center and ask them to flash the updated stock one
Is there any other way to get? The service centre is very very far away..
I believe no other way till now.
Sanjith2908 said:
Guys please help! If anyone can get XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml stock rom please send the link... my moto turbo is soft bricked but no rom is flashing and recovery shows this "motorola/quark_reteu/quark_umts6.0.1/MGPS24.107-70.2-7/7"
bootloader locked and cant boot to enable unlock
Click to expand...
Click to collapse
sourav92 said:
Several Indians (including me) are facing the same issue as the desired version of stock rom is not available in the internet. Visit moto service center and ask them to flash the updated stock one
Click to expand...
Click to collapse
The problem is Motorola apparently never publicly released the India (RETEU) "GS" region full image version of this firmware. They only released the partial image OTA.
XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml
The "GS" denotes a newer version than just the "G". Once you update to the newer version via OTA -- or try to -- you will be installing a newer version of the bootloader, which can NOT be rolled back.
If your bootloader was UNlocked, you can flash ANY region firmware or any previous India firmware to recover -- previous version of Marshmallow, Lollipop, even Kitkat for the XT1225. Region wouldn't matter, with an unlocked bootloader. (Just be sure to NOT flash gpt.bin!)
If you had an unlocked bootloader, you could flash any one of the BLUE 6.0.1_MPGS24.107-70.2_cid7 images in the screenshot below. (RETLA and RETBR would be the best choices as they are the Mexico and Brazil XT1225 carrier unlocked firmware. India XT1225 would still work just fine on those.) But, as you see the most recent publicly released India (RETEU) image (in red) does not have the "GS". With an unlocked bootloader you could even flash that -- as long as you leave off gpt.bin from the flash commands.
With a locked bootloader and no public release of the full image firmware you need, I'm sorry but you have to go to a Motorola service center. This is one reason you should always unlock your bootloader... It gives you more choices for recovery.
http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes @ChazzMatt, there is no other way if the bootloader is locked. I am the person who noticed that "GS" thing first, and we already had a discussion on that in other thread. That's why I gave him the only solution to visit Motorola Service center.
sourav92 said:
Yes @ChazzMatt, there is no other way if the bootloader is locked. I am the person who noticed that "GS" thing first, and we already had a discussion on that in other thread. That's why I gave him the only solution to visit Motorola Service center.
Click to expand...
Click to collapse
iv gone to the service center and gotten the latest update installed but it is kindoff bugged and freezes a lot when I launch some apps
also i enabled the oem unlocking and am trying to unlock the bootloader but it says failed to get unlock data when i do fastboot get unlock data
Sanjith2908 said:
iv gone to the service center and gotten the latest update installed but it is kindoff bugged and freezes a lot when I launch some apps
also i enabled the oem unlocking and am trying to unlock the bootloader but it says failed to get unlock data when i do fastboot get unlock data
Click to expand...
Click to collapse
Read my bootloader unlock guide. OEM bootloader unlock in Settings by itself does nothing, unless the OEM wants it to do something. This has always been true. In this case, Motorola is one of the OEMS who make you get a bootloader unlock code to actually unlock your bootloader; LG is another one that requires this. You request a bootloader unlock code and follow the steps in my guide.
[UPDATED GUIDE] How to unlock your MOTO MAXX/MOTO TURBO bootloader, install TWRP and gain root access
Hi everyone, I am selling my phone and would like to relock the phone and avoid having that message that appears every time I rebooot the phone..
Is it possiile to relock the phone without problems?
Could someone kindly show me how.
Thanks
Cheers
Make sure you flashed a full stock RUU first, just to make sure the software is absolutely original. Then you can do it via fastboot oem lock in download mode.
Sent from my HTC U12+ using XDA Labs
Hello friends,
I wanted to see if it worked.
I also want relock Bootloader. I have read that it can come to a software brick.
Thanks
Hollilightman said:
Hello friends,
I wanted to see if it worked.
I also want relock Bootloader. I have read that it can come to a software brick.
Thanks
Click to expand...
Click to collapse
what ever you do make sure you put on the original rom on, i made the mistake of doing it when I had a patched boot file and now it wont boot.
I'm not panicing just yet as from reading up I can just flash it using the SD card method. but i got to wait till I get home as i havent got a 16/32GB sd card with me.
Thank you.
just to be sure, this is what I need to do?
1. put an original RUU on your microSD card and rename it 2Q55IMG.zip. Then open the download mode and confirm the flashing.
2. then use "Fastboot OEM Lock" in download mode to lock the bootloader.
Did I understand it correctly?
Thanks
Hollilightman said:
Thank you.
just to be sure, this is what I need to do?
1. put an original RUU on your microSD card and rename it 2Q55IMG.zip. Then open the download mode and confirm the flashing.
2. then use "Fastboot OEM Lock" in download mode to lock the bootloader.
Did I understand it correctly?
Thanks
Click to expand...
Click to collapse
Yes, those instructions are correct.
Although I'm not entirely sure that will remove the message you're looking to remove but I might be wrong. Hopefully I am cause I intend to do the exact same thing as you.
Let me know how it goes
Thank you ,
But would be nice if someone could confirm, who has already done so with success ....
Hollilightman said:
Thank you ,
But would be nice if someone could confirm, who has already done so with success ....
Click to expand...
Click to collapse
Can confirm this is the way to do it, but make sure you put a stock rom on first as it doesn't like it if your boot is patched.
The message is phone is RELOCKED after its all done
HELP!!!
Hello again,
I have a problem. I have the
2Q55IMG_IMAGINE_UHL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528110_signed_2_4.zip
renamed 2Q55IMG.zip on the SD card and flashed. I have UHL (Single SIM) HTC_034.
Then i use "Fastboot OEM Lock" in download mode to lock the bootloader.
I confirm the query with Yes.
After that I have a bootloop, can't get out of it...
What can I do?
Did it boot into the rom before you tried to relock the bootloader. Also I wonder if the rom you used was to early. I used 1.53.401 when I did it. I assume that is the same rom for single / dual sim htc_034 models.
I would be getting a more uptodate rom and reflash again via sd card method
bigAL99 said:
Did it boot into the rom before you tried to relock the bootloader. Also I wonder if the rom you used was to early. I used 1.53.401 when I did it. I assume that is the same rom for single / dual sim htc_034 models.
I would be getting a more uptodate rom and reflash again via sd card method
Click to expand...
Click to collapse
Thanks,
yes, I had rebooted.
I don't have a link for the 1.53.401. Single SIM. (See picture)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The bootloader now says (see picture)
When flashing the end was "8 RU_SGNATURE_FAIL" (see picture)
delete
Hollilightman said:
Thanks,
yes, I had rebooted.
I don't have a link for the 1.53.401. Single SIM. (See picture)
The bootloader now says (see picture)
When flashing the end was "8 RU_SGNATURE_FAIL" (see picture)
Click to expand...
Click to collapse
Hopefully someone will know the code I checked 5m4rph0n36guru s thread and that error code isn't listed.
I assume you have tried reflashing again.
bigAL99 said:
Hopefully someone will know the code I checked 5m4rph0n36guru s thread and that error code isn't listed.
I assume you have tried reflashing again.
Click to expand...
Click to collapse
right, just download the 1.21.401.4 and try it...
Edit:
it worked with RUU 1.21401.4. Apparently the RUU 1.30.401.2 is faulty. ;o)
5m4r7ph0n36uru said:
Make sure you flashed a full stock RUU first, just to make sure the software is absolutely original. Then you can do it via fastboot oem lock in download mode.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
just a dumb question. if i want to unlock later, i need to do the steps via htcdev with the unlock token; right?
Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys
Scooberjake said:
Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys
Click to expand...
Click to collapse
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image https://developers.google.com/android/images#blueline
Instructions: Look towards the top of that same page, linked above
BBobby said:
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image
Instructions: Look towards the top of that same page, linked above
Click to expand...
Click to collapse
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?
Scooberjake said:
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?
Click to expand...
Click to collapse
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.
Tulsadiver said:
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.
Click to expand...
Click to collapse
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
Use the version that matches your carrier. If on VZ use that image. It will not lock the bootloader, just some modem changes.
You can go back and forth all you want.
Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
If the bootloader is unlocked, it was not purchased at Verizon. Verizon phones have locked bootloaders. I have a google purchased unlocked phone that works fine with a Verizon SIM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.
Scooberjake said:
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.
Click to expand...
Click to collapse
Yes, the VZ one.
No, only phones purchased through Google can be bootloader unlocked. VZ purchased phones can not. Some EU 3s can be bootloader unlocked after the contract is up.
All can be SIM unlocked.
One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.
Scooberjake said:
One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.
Click to expand...
Click to collapse
In your case flash the full factory image, including the wipe, since you're not real sure what firmware the phone is currently on. In the future you can do the ota if you want or the factory image without the wipe.
I have benn using Pixels since 2XL.
I am used to images being released immediately and where to get them from Google.
I havent had a OP since OP2.
I now have a TMob 8T, bootloader is unlocked, but I havent considered rooting yet as I cant find images anywhere.
Should I expect them to appear on OnePlus's website?
I would appreciate it if anyone has any historical knowledge.
thanks
parakleet said:
I have benn using Pixels since 2XL.
I am used to images being released immediately and where to get them from Google.
I havent had a OP since OP2.
I now have a TMob 8T, bootloader is unlocked, but I havent considered rooting yet as I cant find images anywhere.
Should I expect them to appear on OnePlus's website?
I would appreciate it if anyone has any historical knowledge.
thanks
Click to expand...
Click to collapse
How exactly did you bootloader unlock your device? OP's site is drunk for everybody how did you do it? Or do you mean to say that you are SIM unlocked?
I tweeted tmobile help
Explained to them I am a developer and purchased this phone because I want to get root access
They asked me to pay it off, so I did.
They unlocked the sim
Them OEM unlock switch became active
I did the fastboot commands and here I am trying to figure out how to root
parakleet said:
I tweeted tmobile help
Explained to them I am a developer and purchased this phone because I want to get root access
They asked me to pay it off, so I did.
They unlocked the sim
Them OEM unlock switch became active
I did the fastboot commands and here I am trying to figure out how to root
Click to expand...
Click to collapse
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Not be of which is my concern per my original post
The thread has gone off topic.
Again
I'm concerned about images
parakleet said:
Not be of which is my concern per my original post
The thread has gone off topic.
Again
I'm concerned about images
Click to expand...
Click to collapse
You can't root before being bootloader Unlocked
SmileBigNow said:
You can't root before being bootloader Unlocked
Click to expand...
Click to collapse
Yes I know that.
Again what you are discussing is not the topic of this thread.
parakleet said:
Yes I know that.
Again what you are discussing is not the topic of this thread.
Click to expand...
Click to collapse
You need to do two things, first, please stop being rude. People are trying to help you so don't be a butt. Second, you have to boot a TWRP img, DD your current booted kernel image, patch it with magisk, boot the patched img. Then direct install via magisk. As a developer you should not have any issues, but as the previous people said, you need to wait for an unlock bin to unlock your bootloader or you cannot flash anything. And thus no ROOT.
Soooooo, once you get the code, actually unlock your bootloader then boot TWRP and dd your boot image.
And remember,
Be nice
My BL is unlocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SmileBigNow said:
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Click to expand...
Click to collapse
I have gotten the Network Unlocked and can boot into fastboot.
Using the command: fastboot.exe oem get_unlock_code
I get: < waiting for device >
I've used adb to do some debloating so the USB drivers seem to be working.
Anyway to determine the root cause (other then my ignorance
SmileBigNow said:
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Click to expand...
Click to collapse
Can I unlock my KB2007? I'm not from the US but a friend gave me one as a gift. Now I can't use it because it's locked by T Mobile. What can I do? Is there a safe way to root it? I don't even use T Mobile and this carrier isn't in my country.
highland180 said:
I have gotten the Network Unlocked and can boot into fastboot.
Using the command: fastboot.exe oem get_unlock_code
I get: < waiting for device >
I've used adb to do some debloating so the USB drivers seem to be working.
Anyway to determine the root cause (other then my ignorance
Click to expand...
Click to collapse
Have you rebooted the phone into fastboot?
adb reboot bootloader
If you have it sound like a driver error.
Gabrielguti said:
Can I unlock my KB2007? I'm not from the US but a friend gave me one as a gift. Now I can't use it because it's locked by T Mobile. What can I do? Is there a safe way to root it? I don't even use T Mobile and this carrier isn't in my country.
Click to expand...
Click to collapse
As I have understood it from other threads on here, you need to get it sim unlocked with the help of TMobile first and then you can request a bootloader unlock token from oneplus. This seem to be difficult to do even for legit customers see https://forum.xda-developers.com/t/t-mobile-bootloader-unlock.4181339/
You need a unlocked booloader to root it or convert to a non T-Mobile rom.
Please all, lets keep it on topic and with respect.
Thanks for your help.