Related
This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app
1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.
1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.
dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.
I intend to buy the chinese variant XT1635-03 at Gearbest. Is it possible to flash the XT1635-02 rom on it or will I be stuck with the chinese rom? If that is possible, would I receive the OTA updates?
You can flash the every rom you like i have the Chinese version and i flashed the Russian rom on it you just need to unlock your bootloader
RED LONDON said:
You can flash the every rom you like i have the Chinese version and i flashed the Russian rom on it you just need to unlock your bootloader
Click to expand...
Click to collapse
Thank you very much. Your answer was decisive for my decision on buying the device, and I think the chinese version comes already with the bootloader unlocked.
joseph_s1lva2 said:
Thank you very much. Your answer was decisive for my decision on buying the device, and I think the chinese version comes already with the bootloader unlocked.
Click to expand...
Click to collapse
Mine had weird bootloader it was locked but I wasn't able to unlock it with the code that moto gave me if you had the same problem pm me ill tell you how to unlock it
RED LONDON said:
Mine had weird bootloader it was locked but I wasn't able to unlock it with the code that moto gave me if you had the same problem pm me ill tell you how to unlock it
Click to expand...
Click to collapse
Thank you.
You won't receive OTAs.
mahdif62 said:
You won't receive OTAs.
Click to expand...
Click to collapse
It's not a big deal, as long as I can flash the latest roms.
RED LONDON said:
You can flash the every rom you like i have the Chinese version and i flashed the Russian rom on it you just need to unlock your bootloader
Click to expand...
Click to collapse
Sorry to bother again, but did you flash the entire rom? I read at other thread that it is dangerous to flash modem, fsg and bootloader from another variant.
joseph_s1lva2 said:
Sorry to bother again, but did you flash the entire rom? I read at other thread that it is dangerous to flash modem, fsg and bootloader from another variant.
Click to expand...
Click to collapse
I read on another thread that he flashed a -02 firmware without the modem files and no partition wipe (64 vs 32 GB).
Is there a full "HowTo" to go from XT1635-03 Dual-SIM to a XT1635-02 Firmware? Of course, Dual-SIM should still work afterwards. OTA will not work in any way, right?
Are there custom Roms which can be used on the XT1635-03 ?
Thanks
i have a problem
RED LONDON said:
Mine had weird bootloader it was locked but I wasn't able to unlock it with the code that moto gave me if you had the same problem pm me ill tell you how to unlock it
Click to expand...
Click to collapse
I can not unlock my bootloader with the code of the bike my pc does not even recognize the device in fastboot, it only recognizes as an idle device called fastboot addison s. you know what to do?
Any progress to what can be done with the chinese moto z play?
Hi,
I got Moto Z from gearbest too and it also comes with ADDISON_CHINA_CUST image.
I was able to unlock bootloader with 'fastboot flashing unlock' and then I flashed it to retail 7.0 (via fastboot), then updated successfully to 7.1 (via adb sideload).
Unfortunately it still shows retcn channel and ADDISON_CHINA_CUST as baseband.
Is there any way to change it too?
Thanks!
janus123 said:
Hi,
I got Moto Z from gearbest too and it also comes with ADDISON_CHINA_CUST image.
I was able to unlock bootloader with 'fastboot flashing unlock' and then I flashed it to retail 7.0 (via fastboot), then updated successfully to 7.1 (via adb sideload).
Unfortunately it still shows retcn channel and ADDISON_CHINA_CUST as baseband.
Is there any way to change it too?
Thanks!
Click to expand...
Click to collapse
To be short: no, there is no pracical way to change the software channel and modem version (they are tightened to hardware)
I do no think you receive any OTA but if so do not install them
freeman_g said:
To be short: no, there is no pracical way to change the software channel and modem version (they are tightened to hardware)
I do no think you receive any OTA but if so do not install them
Click to expand...
Click to collapse
Thanks for your reply! Sounds like buying a phone from gearbest is not a good idea if you want to receive OTAs and stay with official ROM.
One more thing: after I updated the phone to 7.1 it shows during startup 'ID: bad key' (apart from 'Your device has been unlocked and can't be trusted'.).
When being flashed, it also returned:
writing 'boot'...
(bootloader) Image signed with key bad key
and
writing 'recovery...
(bootloader) Image signed with key bad key
Btw, maybe it's a stupid question, but is it justified to consider retcn channel and modem version (ADDISON_CHINA_CUST) as kind of backdoor? It still not official software (or at least the latter)...
hi
Hi,
I received a Moto Z Play from Banggood as exchange for another phone under warranty.
I unlocked the bootloader, and via fastboot with RSD lite I updated to nougat 7.1.1
but the chineese version fot XT1635-03. I got it from here :https://mirrors.lolinet.com/firmware/moto/addison_cn/RETCN/
This rom is much worse than the original one, it's a chineese rom with only chineese and english language, no play store, no googleapps, no chrome...
At this time, I don't find the way to flash another Rom.
edit: repaired flashing another 7.1.1 custom rom
abs0lut3z33r0 said:
Any progress to what can be done with the chinese moto z play?
Click to expand...
Click to collapse
If you install the Verizon version your device will update automatically
My bootloader was already unlocked when I got it from banggood, which is similar to gearbest.
Install this via rsd lite and you will have updates via ota:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Anyone know if it's possible to lock the bootloader of -03 using -01/-02 ROM?
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.
somebody can help me? i have all title problems, i can't flash a firmware because my bootloader is locked and i cant unlock the bootloader cuz i cant pass from start up config, is same as a google count lock, but i know the Gaccount the problem is i dont have internet, wifi or mobile data cuz baseband not found
1st reboot to recovery and do a factory reset to see if that gets your basebands back.
If that doesn't work, try using Bluetooth to sign into your google account so you can enable oem unlocking and unlock your bootloader, that will give you some wiggle room.
If neither of those work, then try flashing the latest firmware for your variant. In most cases with a locked bootloader you can only flash the same firmware version or newer. If you succeed here, check everything and go back to step 1 if needed.
If none of that works, the only thing left to try is a blankflash. https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
If all of your problems occurred because you tried flashing a pie firmware not intended for your variant, you might be out of luck at the moment. People are getting into real trouble that they can't fix doing this.
Good morning, I have the same problem, no wifi and no mobile data, I tried to install the same rom and a superior and nothing, I'm working the android 9 pie to see if I can recover my device, because not even with bluetooth connected I could unlock the oem option.
fallcaoalves said:
Good morning, I have the same problem, no wifi and no mobile data, I tried to install the same rom and a superior and nothing, I'm working the android 9 pie to see if I can recover my device, because not even with bluetooth connected I could unlock the oem option.
Click to expand...
Click to collapse
Did you sign in to google, or were you able to?
41rw4lk said:
Did you sign in to google, or were you able to?
Click to expand...
Click to collapse
I already signed in to google, already reset, reloaded the google account, already changed the date and nothing, I'm running out of options
41rw4lk said:
If all of your problems occurred because you tried flashing a pie firmware not intended for your variant, you might be out of luck at the moment. People are getting into real trouble that they can't fix doing this.
Click to expand...
Click to collapse
theres nothing i can do?
bogante said:
theres nothing i can do?
Click to expand...
Click to collapse
If you know where the contact points are, you can attempt a jtag. Other than that, no one has been able to fix the Pie update messing up another variant.
Edit. This is why I gave the disclaimer in the below post... Never flash a zip not intended for your model or major patch version.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783/post74297905
If u have USB Ethernet connector, use it via USB otg. It work for me I was able to enable unlock and still trying to find why mobile and wifi doesn't work after flashing back original firmware.
Murali_ch21 said:
If u have USB Ethernet connector, use it via USB otg. It work for me I was able to enable unlock and still trying to find why mobile and wifi doesn't work after flashing back original firmware.
Click to expand...
Click to collapse
it works even when im on start up config?
bogante said:
it works even when im on start up config?
Click to expand...
Click to collapse
Yes... I was having same problem when I tried to downgrade from RETIN pie version to my device original ROM RETAPAC. so I used it and was able to developer setting and enabled bootloader unlock. Later I flashed with RETIN PIE version.
Murali_ch21 said:
Yes... I was having same problem when I tried to downgrade from RETIN pie version to my device original ROM RETAPAC. so I used it and was able to developer setting and enabled bootloader unlock. Later I flashed with RETIN PIE version.
Click to expand...
Click to collapse
finally you can recover your baseband or you're still with no baseband?
bogante said:
finally you can recover your baseband or you're still with no baseband?
Click to expand...
Click to collapse
Did u try to connect the Ethernet conection? If u get internet connection that should be able unlock ur device bootloader. As far as for me I was able to unlock my bootloader but still not able to find how to enable WiFi and mobile data on my stock version. I'm still running the device on RETIN version.
Murali_ch21 said:
Did u try to connect the Ethernet conection? If u get internet connection that should be able unlock ur device bootloader. As far as for me I was able to unlock my bootloader but still not able to find how to enable WiFi and mobile data on my stock version. I'm still running the device on RETIN version.
Click to expand...
Click to collapse
maybe you will need to wait for firmware pie for your channel
so, you dont have baseband (wifi or mobile) at all?
bogante said:
maybe you will need to wait for firmware pie for your channel
so, you dont have baseband (wifi or mobile) at all?
Click to expand...
Click to collapse
Yes... And just waiting for official release.?
Murali_ch21 said:
If u have USB Ethernet connector, use it via USB otg. It work for me I was able to enable unlock and still trying to find why mobile and wifi doesn't work after flashing back original firmware.
Click to expand...
Click to collapse
https://www.steren.com.mx/adaptador-usb-c-a-ethernet.html this will work?
bogante said:
https://www.steren.com.mx/adaptador-usb-c-a-ethernet.html this will work?
Click to expand...
Click to collapse
Sorry I can't open the link .... U can look for USB to Ethernet connector and USB otg adapter to connect phone. It will give u data connection to the phone.
Murali_ch21 said:
Sorry I can't open the link .... U can look for USB to Ethernet connector and USB otg adapter to connect phone. It will give u data connection to the phone.
Click to expand...
Click to collapse
this is only what i need?
If you've upgraded to a pie modem you can't go back to oreo modem. The best you can hope for is that either the correct firmware for your variant will be released, or that another pie variant will have a baseband that you can use.
41rw4lk said:
If you've upgraded to a pie modem you can't go back to oreo modem. The best you can hope for is that either the correct firmware for your variant will be released, or that another pie variant will have a baseband that you can use.
Click to expand...
Click to collapse
i know that bro, but i dont have the bootloader unlock, ill can install the pie firmware for my phone when release it with bootloader locked?
bogante said:
i know that bro, but i dont have the bootloader unlock, ill can install the pie firmware for my phone when release it with bootloader locked?
Click to expand...
Click to collapse
If the firmware is for you phone you should be able to. With a locked bootloader you can typically install either the current firmware version or newer.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Yes, I put my self in prison by locking bootloader, I already downloaded this firmware, but how can I update this firmware via ADB Sideload or Micro SD?
as you know bootloader locked and there isn't a simple way, with locked bootloader I can't flash this file, (Remote Failure) error
thanks a lot
41rw4lk said:
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hello, anybody?????
There is any way to Upgrade Android 8 to Android 9 with locked bootloader?
My Device state: flashing_locked
is it possible to FORCE UNLOCK?
or is it possible to open hardware device and make it force unlock?
please help me,
someone?
solution
I need help, PLEAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSSEEEE
Have you tried using Lenovo moto smart assistant?
Leonardoliveira said:
Have you tried using Lenovo moto smart assistant?
Click to expand...
Click to collapse
Yes, I did, not work
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
I couldn't do anything, I just send to Motorola repair and they change mainboard
sorry, I didn't find any solution
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
41rw4lk said:
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
Click to expand...
Click to collapse
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
gamc01 said:
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
Click to expand...
Click to collapse
You shouldn't flash firmware from other variants like att, etc. However, if you're able to flash those firmwares and not get any permission denied errors then your bootloader is unlocked, which is good. If you have NOT flashed a pie firmware, good, do NOT do it until everything is up and running and you're sorted. If you have, then you'll need to use pie firmware to fix it since once you flash a pie modem there is no going back to an oreo modem.
Run this command from bootloader/fastboot mode and post back your output.
PHP:
fastboot getvar all
You can omit your imei and your serial no. for privacy.