Bricked -unable to use Wug tool kit to revive it - Nexus 7 (2013) Q&A

i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...

i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device

Related

[Q] m8 possibly corrupt hboot

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s
Try fastboot erase cache

My Robin Completely Bricked

Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
HTML:
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.bat
Do you wish to wipe the device when flashing?(Y/N): Y
sending 'partition' (34 KB)...
OKAY [ 0.020s]
writing 'partition'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'sbl1' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
OKAY [ 0.021s]
finished. total time: 0.057s
sending 'sbl1bak' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1bak'...
OKAY [ 0.021s]
finished. total time: 0.059s
sending 'aboot' (701 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 0.021s]
finished. total time: 0.055s
sending 'abootbak' (701 KB)...
OKAY [ 0.030s]
writing 'abootbak'...
OKAY [ 0.021s]
finished. total time: 0.056s
sending 'rpm' (188 KB)...
OKAY [ 0.020s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'rpmbak' (188 KB)...
OKAY [ 0.020s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.047s
sending 'tz' (561 KB)...
OKAY [ 0.030s]
writing 'tz'...
OKAY [ 0.020s]
finished. total time: 0.056s
sending 'tzbak' (561 KB)...
OKAY [ 0.030s]
writing 'tzbak'...
OKAY [ 0.020s]
finished. total time: 0.055s
sending 'hyp' (93 KB)...
OKAY [ 0.020s]
writing 'hyp'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'hypbak' (93 KB)...
OKAY [ 0.020s]
writing 'hypbak'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'sdi' (28 KB)...
OKAY [ 0.020s]
writing 'sdi'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmic' (37 KB)...
OKAY [ 0.020s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmicbak' (37 KB)...
OKAY [ 0.020s]
writing 'pmicbak'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'hwcfg' (1 KB)...
OKAY [ 0.020s]
writing 'hwcfg'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'bluetooth' (450 KB)...
OKAY [ 0.020s]
writing 'bluetooth'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'keymaster' (148 KB)...
OKAY [ 0.020s]
writing 'keymaster'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'cmnlib' (165 KB)...
OKAY [ 0.020s]
writing 'cmnlib'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'splash' (6075 KB)...
OKAY [ 0.141s]
writing 'splash'...
OKAY [ 0.020s]
finished. total time: 0.166s
sending 'splash2' (6075 KB)...
OKAY [ 0.141s]
writing 'splash2'...
OKAY [ 0.020s]
finished. total time: 0.167s
sending 'persist' (4673 KB)...
OKAY [ 0.120s]
writing 'persist'...
OKAY [ 0.020s]
finished. total time: 0.144s
sending 'modem' (78615 KB)...
OKAY [ 1.729s]
writing 'modem'...
OKAY [ 0.013s]
finished. total time: 1.746s
sending 'cust_nv' (301 KB)...
OKAY [ 0.030s]
writing 'cust_nv'...
OKAY [ 0.021s]
finished. total time: 0.053s
sending 'systeminfo' (4 KB)...
OKAY [ 0.020s]
writing 'systeminfo'...
OKAY [ 0.021s]
finished. total time: 0.043s
sending 'KEY_INFO' (1 KB)...
OKAY [ 0.020s]
writing 'KEY_INFO'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'hidden' (9319 KB)...
OKAY [ 0.211s]
writing 'hidden'...
OKAY [ 0.020s]
finished. total time: 0.235s
sending 'sutinfo' (1 KB)...
OKAY [ 0.020s]
writing 'sutinfo'...
OKAY [ 0.021s]
finished. total time: 0.044s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'recovery' (12794 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
sending 'boot' (11746 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.306s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
< waiting for device >
simu_flash:971f0dec:system
sending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
vampire_8_7 said:
Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.batDo you wish to wipe the device when flashing?(Y/N): Ysending 'partition' (34 KB)...OKAY [ 0.020s]writing 'partition'...OKAY [ 0.021s]finished. total time: 0.049ssending 'sbl1' (479 KB)...OKAY [ 0.030s]writing 'sbl1'...OKAY [ 0.021s]finished. total time: 0.057ssending 'sbl1bak' (479 KB)...OKAY [ 0.030s]writing 'sbl1bak'...OKAY [ 0.021s]finished. total time: 0.059ssending 'aboot' (701 KB)...OKAY [ 0.030s]writing 'aboot'...OKAY [ 0.021s]finished. total time: 0.055ssending 'abootbak' (701 KB)...OKAY [ 0.030s]writing 'abootbak'...OKAY [ 0.021s]finished. total time: 0.056ssending 'rpm' (188 KB)...OKAY [ 0.020s]writing 'rpm'...OKAY [ 0.021s]finished. total time: 0.045ssending 'rpmbak' (188 KB)...OKAY [ 0.020s]writing 'rpmbak'...OKAY [ 0.021s]finished. total time: 0.047ssending 'tz' (561 KB)...OKAY [ 0.030s]writing 'tz'...OKAY [ 0.020s]finished. total time: 0.056ssending 'tzbak' (561 KB)...OKAY [ 0.030s]writing 'tzbak'...OKAY [ 0.020s]finished. total time: 0.055ssending 'hyp' (93 KB)...OKAY [ 0.020s]writing 'hyp'...OKAY [ 0.021s]finished. total time: 0.049ssending 'hypbak' (93 KB)...OKAY [ 0.020s]writing 'hypbak'...OKAY [ 0.021s]finished. total time: 0.045ssending 'sdi' (28 KB)...OKAY [ 0.020s]writing 'sdi'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmic' (37 KB)...OKAY [ 0.020s]writing 'pmic'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmicbak' (37 KB)...OKAY [ 0.020s]writing 'pmicbak'...OKAY [ 0.021s]finished. total time: 0.046ssending 'hwcfg' (1 KB)...OKAY [ 0.020s]writing 'hwcfg'...OKAY [ 0.021s]finished. total time: 0.045ssending 'bluetooth' (450 KB)...OKAY [ 0.020s]writing 'bluetooth'...OKAY [ 0.021s]finished. total time: 0.046ssending 'keymaster' (148 KB)...OKAY [ 0.020s]writing 'keymaster'...OKAY [ 0.021s]finished. total time: 0.046ssending 'cmnlib' (165 KB)...OKAY [ 0.020s]writing 'cmnlib'...OKAY [ 0.021s]finished. total time: 0.045ssending 'splash' (6075 KB)...OKAY [ 0.141s]writing 'splash'...OKAY [ 0.020s]finished. total time: 0.166ssending 'splash2' (6075 KB)...OKAY [ 0.141s]writing 'splash2'...OKAY [ 0.020s]finished. total time: 0.167ssending 'persist' (4673 KB)...OKAY [ 0.120s]writing 'persist'...OKAY [ 0.020s]finished. total time: 0.144ssending 'modem' (78615 KB)...OKAY [ 1.729s]writing 'modem'...OKAY [ 0.013s]finished. total time: 1.746ssending 'cust_nv' (301 KB)...OKAY [ 0.030s]writing 'cust_nv'...OKAY [ 0.021s]finished. total time: 0.053ssending 'systeminfo' (4 KB)...OKAY [ 0.020s]writing 'systeminfo'...OKAY [ 0.021s]finished. total time: 0.043ssending 'KEY_INFO' (1 KB)...OKAY [ 0.020s]writing 'KEY_INFO'...OKAY [ 0.021s]finished. total time: 0.045ssending 'hidden' (9319 KB)...OKAY [ 0.211s]writing 'hidden'...OKAY [ 0.020s]finished. total time: 0.235ssending 'sutinfo' (1 KB)...OKAY [ 0.020s]writing 'sutinfo'...OKAY [ 0.021s]finished. total time: 0.044srebooting into bootloader...OKAY [ 0.006s]finished. total time: 0.006s< waiting for device >sending 'recovery' (12794 KB)...OKAY [ 0.291s]writing 'recovery'...OKAY [ 0.020s]finished. total time: 0.320srebooting into bootloader...OKAY [ 0.003s]finished. total time: 0.003s< waiting for device >sending 'boot' (11746 KB)...OKAY [ 0.281s]writing 'boot'...OKAY [ 0.019s]finished. total time: 0.306srebooting into bootloader...OKAY [ 0.010s]finished. total time: 0.011s< waiting for device >simu_flash:971f0dec:systemsending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
Click to expand...
Click to collapse
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
AnierinB said:
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
Click to expand...
Click to collapse
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
vampire_8_7 said:
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
Click to expand...
Click to collapse
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
HeaDekBatHblu said:
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
Click to expand...
Click to collapse
hey mate these 2 commands don't exist in the fastboot
fastboot reboot system
fastboot reboot-system
I have also tried the adb shell and it gave me "error : no devices found". I had to reboot in recovery and choose apply update via adb so I can see the listed devices.
HTML:
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe devices -l
List of devices attached
NBQGLMB660203876 sideload product:ether model:Robin device:ether
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader
error: closed
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader -i 0x2c3f
error: closed
No luck bro.
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
soulife said:
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
Click to expand...
Click to collapse
Hey mate so sorry for the late reply, for some reason I didn't see the notification of your reply.
Yeah fastboot and Stock recovery are working fine, but remember bootloader is still locked and the USB debugging isn't enabled. I thought it should be recoverable but I am not able to recover it and tried too many ways but they all have failed. I will appreciate some advise/help to sort this phone. Thanks
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
soulife said:
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
Click to expand...
Click to collapse
I bought 2 Robins at the time, 1 I used straight away and the other is the 1 that had the issue and I started using it like 3 months later. By default the OEM isn't toggled on I have confirmed that 100%, after the 2nd Robin got bricked. I picked up the working one and looked at it and sure enough the OEM toggle was off so I had to turn it on myself also enabled USB debugging in case this one breaks for some reason.
So yeah, basically if I tried to flash anything via fastboot it says "remote device is locked" and can't sideload anything via ADB also because USB debugging isn't enabled.
I managed to get the OTA.zip for Robin, Nougat update and half way through updating around 47% to 51% it fails, because the boot image is different off course, cause my phone still running 6.0.1, and the OTA find unmatched release keys. I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Find 6.0.1?
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
vampire_8_7 said:
I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Click to expand...
Click to collapse
soulife said:
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
Click to expand...
Click to collapse
Hey mate yeah I meant flashable.zip, and nope the images won't work via sideload. Definitely the OEM wasn't checked I got 2 Robins and both weren't toggole on.

Stuck in the Fastboot/ Recovery

I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!

Here is a patched MSM download tool for TMobile OP7T.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.
1) Download the patched MSM download tool: [removed]
2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.
3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
Code:
fastboot flashing unlock_critical
4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495
How to enter EDL mode:
VQ30DE said:
[...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
Click to expand...
Click to collapse
Thanks you very murch
Tested and working? If something goes wrong is it easily fixed/corrected? This is to bypass the 7 day waiting period for the unlock token?
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
I can confirm steps 2 and 3 work. Step 2 for my case took 234 seconds so be patience. Now trying step 4.
Superboy58 said:
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
Click to expand...
Click to collapse
Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
Wanted to say thank you for putting this together and making it dummy proof.
when i do a fastboot oem get_unlock_code, i get the following error message
FAILED (remote: Unknow command)
finished. total time: 0.006s
May I know where did i went wrong?
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
step 8 flash-all.bat, i got the following error messages, is it serious?
< waiting for any device >
Finished. Total time: 8.649s
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/5 (523144 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 17.884s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 17.760s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Press any key to continue . . .
---------- Post added at 02:13 AM ---------- Previous post was at 01:52 AM ----------
I tried flash-all.bat again, there is no error message but the fastboot oem get_unlock_code, i get the following error message
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
I checked the Build Number, it is indeed the version i downloaded.
Anyone can help?
---------- Post added at 02:26 AM ---------- Previous post was at 02:13 AM ----------
Guys, my dual sim is working and I no longer see the T-mobile locked. Is that all i need?
@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.
Thank you so much!
Superboy58 said:
@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.
Click to expand...
Click to collapse
Brilliant. If anyone is attempting this on Linux, I'd recommend getting the latest platform-tools straight from Google. Even the fastboot version from 2019 available in my repository was too old to perform a lot of the steps.
I wonder who'll be the first to convert a McLaren to International??
inneyeseakay said:
I wonder who'll be the first to convert a McLaren to International??
Click to expand...
Click to collapse
We are on the 7T forum.
That being said, I made the same kind of tool for McLaren, but it only allows to unlock it's bootloader. There's no international firmware for McLaren. Unfortunately, there is no hardware equivalent for the McLaren sold as an international phone (it was easy for the 7T to convert because it's the same hardware, or at least very very close).
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
SALHERO said:
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
Click to expand...
Click to collapse
I don't know why you were not able to boot into fastbootd (it says "Failed to boot into userspace fastboot" which means failed to boot into fastbootd).
But it's because of this error that all the warnings "Flashing is not allowed for Critical Partitions" are appearing.
If your fastboot executable is too old, the command "fastboot reboot fastboot", which allows you to boot in fastbootd, will not work. So I suggest you download the latest platform tools zip from Google, so you'll be using the latest adb and latest fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then ensure that in the terminal, the right version of fastboot is used (pay attention to the existing environment variables which might make your terminal use the old fastboot executable in another location).
Then run again the script flash-all.bat.
Please update,
Thanks
Congrats!
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
Thank you allowed me to unlock the bootloader on my wifes 7t and convert to global firmware then i relocked the bootloader the global firmware and software just runs so much smoother than the T-Mobile software not sure why.
Hello,
is anybody know can this guide somehow help me to get my OnePlus 7T unlocked? I mean Network unlocked...
Please if somebody can help me with that I would really appreciate it. Thank you!
@floopidze please read the first post.
Shortychance said:
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
Click to expand...
Click to collapse
It will work on a simlocked device, but it will not sim unlock the phone.
Please read the first post.

TWRP FAILED (remote failure)

So, I was trying to install the twrp, but when I do put out the comand for the flash recovery I get this section:
sending 'recovery' (44474 KB)...
OKAY [ 1.537s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 1.585s
I did try to just boot it already and got this:
downloading 'boot.img'...
OKAY [ 1.216s]
booting...
FAILED (remote failure)
finished. total time: 1.400s
Can anyone help?

Categories

Resources