Related
I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue
necroside007 said:
I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue
Click to expand...
Click to collapse
Ooooh... That's tough. The only place I've heard of any kind of fix is in this thread:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
But, I don't think your situation applies... You're probably SOL.
There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.
rootSU said:
There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.
Click to expand...
Click to collapse
So i can throw away my phone?
necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
I wouldn't yet. Someone may eventually find a fix. But yes, you're going to need a new phone in the meantime.
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
This is a very good idea!
jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
It does say in post 1 that he asked Motorola
I'm confused. What did u do to screw up your phone
sent from your moms phone
necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
93fuelslut said:
I'm confused. What did u do to screw up your phone
sent from your moms phone
Click to expand...
Click to collapse
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.
rootSU said:
It does say in post 1 that he asked Motorola
Click to expand...
Click to collapse
"Hello Ms. Motorola, yes my mother called earlier today, she thought my N6 was in some sort of loop or something, man you know how moms can be. It just won't turn on, I have no idea why, I just know it was working great 1 minute and now, nothing. OK, where do I send it? Thanks"
The crap part would be if someone finds a fix after the phone is damaged. But, before you do anything, make the call.
I see many many threads regarding how to get free tethering, so I don't feel this is too out of place. Again, everyone has to work out for themselves whats right for them.
gee2012 said:
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.
Click to expand...
Click to collapse
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone
93fuelslut said:
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone
Click to expand...
Click to collapse
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.
rootSU said:
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.
Click to expand...
Click to collapse
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
You have to enable oem-unlock after every boot, it will not stick after a reboot.
93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
No. The "enable OEM unlock" setting allows you to boot to the bootloader, connect to a pc and use the "fastboot oem unlock" command to unlock the bootloader.
gee2012 said:
You have to enable oem-unlock after every boot, it will not stick after a reboot.
Click to expand...
Click to collapse
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone
93fuelslut said:
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone
Click to expand...
Click to collapse
I think we're confusing the issue. It doesn't need to stay ticked. All it stops you doing is unlocking the bootloader. Once the bootloader is unlocked, its unlocked.
The only reason you'll need to tick it is if you relocked the bootloader and then wanted to unlock it again. But this is dangerous because if your ROM breaks and you're locked, you cannot then unlock.
jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
With OTA should be fine.. If something goes wrong during ota thats covered by warranty, but i was impatient to wait for it, so i did for my self over USB thats not covered by warranty like when u **** up something with root permissions.. This method is not the original updating method. but its a bit confusing because this was an official google suggested method (https://developers.google.com/android/nexus/images) Terms of use, i accepted hurray!
"Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers."
I did it and they cant repair it.. No way to access to that software part
I wrote a brief thread regarding my phone before...
I'll just give the details:
I'm the second owner, phone died while updating.
Phone was bootloader unlocked, and with TWRP recovery.
As such, baseband and IMEI info are missing, I have the original IMEI but, no efs backup or anything.
Any ideas? I've tried to re-install factory stock via both Skipsoft Toolkit and another Toolkit [Yes, I realize this is no help, now]
I've heard restoring another EFS from another phone may work...? I don't know though, I have two Nexus 5's and I can pull an EFS just to try to get back my original IMEI or I've read EFS Pro could help but, again I'm quite lost and just need a hand here.
Thanks.
Ive been an active user on this forum and the rules is that you cant discuss changing the imei here, because its illegal in many countries
Skickat från min Nexus 6 via Tapatalk
No changing!
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
RedHazy said:
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
Click to expand...
Click to collapse
here's a silly question.. how did you lose your imei? its not an issue on the n6 like earlier nexus phones, people just dont accidentally lose their imei, or their efs., unless they are restoring a nandroid from another phone, that has their efs backed up also..
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Sidenote: I did mess around with Titanium Backup but, I don't see that erasing my IMEI.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
If know the IEMI for your device there are threads on XDA that may restore it. If don't know the original IEMI you are dead in the water from the get go.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
i dont think that you are a criminal, seriously. i was just curious, as on the n5 and n4 that happens often. it really does happen very rarely on a n6. i think the phone dying while updating might of done it. if your bootloader is still unlocked, flashing the factory image might help you. but you will have to do it right, via fastboot while youre in the bootloader. dont use any toolkits, seriously!
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
RedHazy said:
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
Click to expand...
Click to collapse
heres some instructions, dont lock tbe bootloader after, just follow the flashing the factory image instruction. and if tou run into trouble, let us know, so we can help you http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
RedHazy said:
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
Click to expand...
Click to collapse
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Fingers crossed!
simms22 said:
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Click to expand...
Click to collapse
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
RedHazy said:
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
Click to expand...
Click to collapse
wipe the phone, factory reset i mean
(sorry for getting back so late)
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
droid4lif3 said:
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
Click to expand...
Click to collapse
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
graydiggy said:
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
Click to expand...
Click to collapse
The IMEI is stored in the CID partition. The CID is a small datablock containing the processor UID, Channel ID (different CID), a bootloader unlock flag, and IMEI. The CID is unique to each device, and controls several aspects of the device. This datablock has a signature on it so that your device information cannot be modified. Should you corrupt this partition, you will lose your IMEI, and the ability to unlock your bootloader. This is the only likely scenario in which you lost your IMEI. If you boot into your bootloader, you may see an error similar to
Code:
CID Datablock Error! 0xDEAD
otherwise I'm going to assume that is still intact. The IMEI has not been stored in the EFS for many years now. Check your CID on the device and make sure it's not 0xDEAD.
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
Click to expand...
Click to collapse
Did you seriously just ask an iPhone question? ???
Seriously though, bring it back to T-Mobile.
Lol, no, I knew I shouldn't of put that she had a iPhone 6S, now I will never be helped. I am just saying that I used a different sim card to make sure that it wasn't the sim card that was messed up.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
Click to expand...
Click to collapse
You can check by running the command
Code:
fastboot getvar all
in fastboot/bootloader mode.
You should see something like this:
Code:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
The CID should be 0x00DE if it is not corrupt.
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.
OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
Run MsmDownloadTool V4.0 and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
Driver
Alternative driver
Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.
Wow nice. Now to test this on T-Mobile!! Let the flashing commence
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
im tempted to run this today on the tmobile model. how high is the risk of hard brick? will it leave me without fastboot if it doesnt work?
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
apparently the flash to 9.0.5 in the other thread overwrites the modem anyway. its the criticals that dont overwrite. worst case im within my 14 days still, can alwasy return
dreinulldrei said:
Don't think this is a good idea; from what has been communicated the Modem for T-Mobile is different or has a different signature; you might end up with a brick. We we obviously won't find out unless we try. The problem is... you don't have an image to re-flash the T-Mobile version, so you might have to send it in.
Click to expand...
Click to collapse
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
SourPower said:
I thought someone did dump a stock Tmo 9.0 out here?
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
https://androidfilehost.com/?fid=11410963190603845445
Click to expand...
Click to collapse
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
strictlyphat said:
Yep, if a Dev can chime in that I won't be left with a hard brick and will be able to go back to TMobile firm atleastsr I'll jump. The only thing holding me back is that sim unlock and unlock bin. I don't wanna go thru that again if have to exchange.
Click to expand...
Click to collapse
One of three things will happen.
One, it will recognize it as the wrong device and won't flash at all.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
Click to expand...
Click to collapse
Screw it. I'm gonna do this soon. Will report back
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Wanna find out? I'll probably test in a few, lol.
hartleyshc said:
It's not how this tool works. A raw dump doesn't equal a flashable fastboot dump doesn't equal a msmdownloadtool ops file.
Edit: apparently you can't use the not equals symbol. I wrote a lengthy reply and it's gone. I'll write a shorter version.
My assumption is there is no version for the T-Mobile, but this will work for a full conversion. OP support will most likely not use this on the T-Mobile version and it's why we had to void our warranty when we unlocked the bootloader. They probably defer you to T-Mobile if you brick your phone. Now that being said, I bet this tool works just fine on the T-Mobile version and will turn it into a full international device capable of OTA updates and everything.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
One of three things will happen.
One, it will recognize it as the wrong device and won't flash as at.
Two, it will flash and you'll have a hard brick.
Three, it will flash and you'll have a fully converted International version.
If you have to return it to TMobile, you shouldn't have any issues returning it. A dead device is a dead device, the reps don't care. Also getting your new one unlocked should be no issue as all since you already had your first device unlocked. Just tell support that. Your device was unlocked and you had to RMA it. They will SIM unlock no problem. You will still have to wait 7 days for the unlock bin.
Click to expand...
Click to collapse
Cuz I'm assuming it's the same as Samsung. One hardware multiple softwares.
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Dark Nightmare said:
Wanna find out? I'll probably test in a few, lol.
Click to expand...
Click to collapse
Dude I will owe you one. Ur much braver than I. If my son falls asleep I'm trying to. PLEASE LET ME KNOW. And please let me buy u a beer lmfao
strictlyphat said:
Screw it. I'm gonna do this soon. Will report back
Click to expand...
Click to collapse
Guess I'll wait on your results...
Dark Nightmare said:
Guess I'll wait on your results...
Click to expand...
Click to collapse
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
strictlyphat said:
I'm.having doubts man. Lol. What's your input. How likely I hard brick?
Click to expand...
Click to collapse
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Dark Nightmare said:
Since this will flash criticals, very likely, don't worry, my download is almost complete, I'll test it since my 6T is my spare device.
Click to expand...
Click to collapse
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
strictlyphat said:
Ah u r king. I had a backup iPhone til my daughter destroyed hers.
Click to expand...
Click to collapse
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.[/QUOTE
oof that sucks. thanks again
Click to expand...
Click to collapse
Safe flashing to anyone taking the plunge!
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
tried it for good measure, same error
iaTa said:
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.
Contains the latest MsmDownloadTool v4.0.58 and OOS v9.0.5 and is compatible with the non T-mobile international models (T-mobile compatibility currently unknown).
Make sure that your phone is switched off.
Open device manager on your Windows PC.
Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download the driver below and install.
Run MsmDownloadTool V4.0_factory.exe and click Start.
NOTE: This will completely wipe your device and relock your bootloader.
Downloads
MsmDownloadTool: https://androidfilehost.com/?fid=11410963190603846961
Driver: https://androidfilehost.com/?fid=24052804347798730
Shameless plug - my OP referral link for any peops that would like $20/£20/€20 discount: https://www.oneplus.com/invite#EC5BZVULJDUUO22
Click to expand...
Click to collapse
Oh my God you just saved my life brother. Thank you so much.
Dark Nightmare said:
it fails, they do have a signature difference after all, I'm thinking we have to flash criticals/persist before this would work...maybe.
Click to expand...
Click to collapse
Sad days... Appreciate the risks you've taken tho!!
Hi!
I'm from Brazil and I bought a Moto G6 XT1925-3.
I want to unlock bootloader but the option OEM Unlock is greyed out on Developer Options.
I tried RSD Lite with many firmware available on https://mirrors.lolinet.com/firmware/moto/ali/official but none worked.
Does someone have a tip?
Thanks!
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
juicypoot said:
I had the exact same problem. To fix it, I had to enable WiFi and get connected to the Interwebs. Wait a couple minutes to see if the option becomes available. If it does not, disable developer options, and re-enable it. That worked for me.
Click to expand...
Click to collapse
I already tried everything that is possible!
I flahed retail firmware through RSD Lite and nothing happens: allow oem unlock greyed out.
Maybe your OEM is already unlocked. Try running this command: fastboot oem device-info in fastboot and see what it says
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
adrianogoes said:
Guys, it's true!
After some days the 'Allow OEM Unlock' option became enable!
I did nothing! It's a matter of time, considered as a security measure.
That's it!
Click to expand...
Click to collapse
Still waiting here. How much time did you wait?
You can also try to delete user 999 and oem option should reflect under dev option.
bhati2710 said:
You can also try to delete user 999 and oem option should reflect under dev option.
Click to expand...
Click to collapse
What do you mean? Please explain
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
bhati2710 said:
You need to connect your mobile to wifi and follow steps for date change to year back.
Then look for software update. This would resolve it.
Here is the reference;
Hope it helps.
Click to expand...
Click to collapse
Thanks for replying, but this didn't work. I tried one year, one month, 7 days before and after and it still is grayed out :crying:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
WoKoschekk said:
@mrsiri Are you trying to unlock the bootloader or is it already unlocked?
Click to expand...
Click to collapse
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
mrsiri said:
Trying to unlock it. I locked it by mistake and now need to wait 7 days for the OEM Unlock button in developer settings to be enabled. It could also be locked forever ( Is it possible?) but then there's no hope for me.
Edit: I can also boot the stock room boot.img image but that doesn't help with the OEM Unlock button. it is still grayed out. What I could do is boot a magisk patched image to get root, but by doing this all my phone did was reboot twice and forcing me to factory reset and then use the old regular non patched boot image that I'm currently using. My current flashed boot image has verity mode off, in case that could help into anything.
Thanks in advance for replying
Click to expand...
Click to collapse
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
WoKoschekk said:
Your bootloader seems to be unlocked. It is not possible to flash another boot.img with a locked bootloader. What else should be the purpose of a unlocked bootloader?? This is the prerequisite to flash a ROM or a twrp.img
---------- Post added at 05:52 PM ---------- Previous post was at 05:49 PM ----------
What exactly is the text right under the toggle to turn on the OEM unlocking option?
Click to expand...
Click to collapse
The text is "connect to the internet or contact your carrier". I didn't flash the boot.img, but booted it. Like when you boot TWRP, but in this case it was the original stock boot.img
My bootloader says "flashing_locked", so it is not fully unlocked. And I can't unlock it without enabling the "OEM Unlock" Button ?
Yes, you have to wait.
WoKoschekk said:
Yes, you have to wait.
Click to expand...
Click to collapse
In the end I sent my device to a repair service. Thanks for the help, but I can't rely on waiting 7 days and assuming the button will re-enable itself. I need it fixed as soon as possible.
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
WoKoschekk said:
I think that was a very bad idea! Since four days you are waiting for that button become active and there are only three days left. Do you really think a repair station will send it back in three days?? This button becomes active by itself in three days and after that they will send it back to you and earn the money for nothing!
Click to expand...
Click to collapse
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
---------- Post added at 11:45 PM ---------- Previous post was at 11:42 PM ----------
mrsiri said:
Maybe you're right. But you have no idea all what was done in my phone. I really don't think that button was ever going to change. I'll actually be surprised if they can fix it without replacing parts. That's why I think this time it's better if the professionals take care of it, and I'll get the phone Thursday with the guarantee it will be fixed ( Motorola service is taking care of it)
Click to expand...
Click to collapse
Yet the itch of simply waiting will now stay forever
mrsiri said:
Yet the itch of simply waiting will now stay forever
Click to expand...
Click to collapse
As soon as the bootloader is unlocked you won't have that trouble anymore.
WoKoschekk said:
As soon as the bootloader is unlocked you won't have that trouble anymore.
Click to expand...
Click to collapse
Good and bad News!
The repair service couldn't fix the problem so I wasn't charged for it.
The bad News is I'm back at the same state
This time I'll wait the 7 days.
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.
I've unlocked Bootloader with
Code:
fastboot oem unlock [unlock_code]
and flashed Magisk with
Code:
fastboot flash boot magisk_patched.img
and worked fine. But, some months later, I've decided to remove Magisk and at the same time downgrade Android from 10 to 9.
Following the commands listed in this site, after it booted into Google Wizard, I thought it worked and then I rebooted to fastboot again and relocked the Bootloader with
Code:
fastboot oem lock
, after that I realized that the command for flashing the wi-fi module was missing.
So what happened was that I have a phone that boots up but won't find any wi-fi network or mobile data to connect and it won't bypass as I have my Google Account activate no the device.
In searchs I've found this and, as I cannot flash any partition as I have my Bootloader locked, I've thought I could boot via
Code:
fastboot boot boot.img
and try to bypass the Google Wizard via adb, but no success.
The question is: is there another way a could use to access the OS to allow unlock bootloader again?
Via command that I'm missing or even adding the missing bluetooth modulo to the boot.img and making it available to the device and I can access the internet and log in the my account.
I hope I'm being clear enough.
Thanks in advance!
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
Try the unlocking code again
sd_shadow said:
Try the unlocking code again
Click to expand...
Click to collapse
It won't allow. It asks to enable OEM Unlock under Settings -> Developer Options.
Thanks for the answer!
y5r43l said:
Hi,
first of all I'd like to thank for the answer.
Using LMSA was my fist try to rescue the phone. It won't work, I get some kind of error saying I'm choosing the wrong model but I'm not.
I also tryed to use Motorola's RSD with no success.
Because of this I was looking for another solution.
Any way, thanks again!
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7.
Sent from my ali using XDA Labs
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
pastorbob62 said:
Okay, I didn't take it to the next step and offer him a solution. You are correct it was very inconsiderate. But at the same time, what I said is true. It appeared that it was when he tried relocking his boot loader that he ran into a problem. And there is no reason to relock the bootloader.
Click to expand...
Click to collapse
This was his way of knowing that, you and i, we have been here for a long time, i learned this years ago, now he knows it
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
pastorbob62 said:
Just out of curiosity, why in the world would you relock your bootloader. That serves absolutely no purpose whatsoever, and as you have found out, can cause a myriad of issues. There is nothing to be gained by relocking the bootloader. PERIOD!
Click to expand...
Click to collapse
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
Jc_master said:
This is the support you are hoping to find ont this forum? after messing up and killing his phone you think that your response is helpfull? shame on you
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
Well, so your phone boots and everything, you only need to flash a newer build, go to https://mirrors.lolinet.com/firmware/moto/lake/, and find the newest build for your variant and flash it manually, after that you can boot your phone and unlock the bootloader again to do the downgrade correctly
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
If you dont know how to flash it manually, just tell me your variant and ill do a script to flash all the files
Click to expand...
Click to collapse
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
y5r43l said:
Hi everyone, first of all I want to ask for your apologies for taking so long to answer.
Unfortunately I had to find out in the worse way. But I really didn't need to keep the bootloader unlocked as some banking apps just won't work this way and I needed to root for a unique propurse that was to access a sqlite database file.
My device is Motorola Moto G7 Plus, XT1965-2.
I really, really appreciate your help.
I put myself at disposal for further information.
Thanks a lot.
PS: I've found some tools called Android Image Kitchen that could unpack and repack the boot image then I can boot it with
Code:
fastboot boot unsigned_new.img
but I don't know how to add the BTFM.bin to the extracted folders, and then repack, in a way that the device may recognize them.
Click to expand...
Click to collapse
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Bootloader is locked, you cannot flash unsigned boot.img
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
y5r43l said:
I see. If I only had a way to connect to the internet and log in with my google account I think the problem would be solved.
But I cannot find a way to do so.
I already tried to put BTFM.bin in every folder and repacking using AIK, it boots up, but the system won't recognize the module.
I also tried using an ethernet and a wifi OTG without success as it should be enable in Developer Options.
Thanks anyway!
Click to expand...
Click to collapse
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
darkherman said:
well if you want to connect to internet from PC to your android by USB you just have to use this tool and enable the OEM Unlock option
https://github.com/Genymobile/gnirehtet
I had a similar problem downloading the version of my Revvlry+ = Moto G7 Plus XT1965-T and then OEM was disabled and internet and baseband modem stopped working because I downgraded too low and with this tool I managed to recover.
but everywhere in the web I am looking for the way to restore the status of my device because in Bootloader Mode it says: flashing_locked. instead of telling me: oem_locked
and you can't remove the warning that appears every time I turn it on
Click to expand...
Click to collapse
Hi, darkherman,
thank you for you reply.
Unfortunately it won't work as according to documentation: "Make sure you enabled adb debugging on your device(s)."
I have to boot the system to enable it in Developer Options.
Thanks anyway!
Is there a way to bypass the Google Wizard and boot the system without logging in?
About the warning on startup I've read somewhere that's not possible because of some var value obtained from:
Code:
fastboot getvar allCODE]
Don't remember exactly what var, but its value may be 0, 1 or 2 that means locked, unlocked and relocked (not necessarily in this order)
-- runnig the above command I saw some variables such as securestate, verity-state and iswarrantyvoid than may mean something.
But, as far as I know, we have no command such as "set-iswarrantyvoid false" or "set-verity-state 1" or something like that.
Maybe this could be done by replacing/updating the firmware if possible, but I think it doesn't worth the risk of making the device irreversibly bricked.
Thanks again for your reply.
It seem there's no way to rescue it.
Gonna just give up and throw it away.
Thanks for those who tried to help!
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
KtownJeff said:
y5r43l said:
Hi,
I've just semi killed my XT1965-2.....
This would be my last resort:
Might have to open it up and short the test points to get qloader edl mode to be recogized because I believe a blank flash.zip method will bypass from your sd card will reflash your device with an unlocked bootloader so you have fastboot access to flash firmware... I could do this but its not the best advice if you never have took apart a phone or know about test point shorting to emergancy mode.... Or If it is an unlocked no carrier phone buy you another just like it somewhere with an easy return policy and buy extra coverage for damage....Break the screen or whatever so it wont power up the return it and demand your money back... You would be out the price of the extended warranty...
https://frpbypass.net/remove-frp-motorola-moto-g7-plus-lock-bypass-android-pie/
Click to expand...
Click to collapse
Hi, thank you for your reply!
I really never have took apart a phone nor know about test point shorting so this is not an option for me. I could even try to do it but probably won't be able to mount it back.
It's a no carrier phone, but in my country, there's no so easy return policy that I know of, unfortunately.
The bypass won't work because the second pass, "Connect your Motorola Moto G7 Plus to your Wi-Fi", as I think this is the biggest problem, I cannot connect to Wi-Fi. I also tried the method suggested by @darkherman throught gnirehtet with no success.
Click to expand...
Click to collapse