Related
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Do what everyone should be doing... use Rezo's tool to root and install CWM. Then use CWM to flash your ROM. Simple.
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Is your bootloader unlocked? It must be to do that
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Boot your device on HBOOT, and select FASTBOOT and then connect with PC. (USB Debugging must be enabled)
Follow the instructions here to Flash ROM :
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
It's done now.
Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
filking said:
Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
Click to expand...
Click to collapse
That looks bad, try a different USB port, if possible a different cable and even a different PC, don't use a usb hub or usb3 port, if none of that helps, it's probably a bad EMMC, see this thread and see if it is.
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
filking said:
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
Click to expand...
Click to collapse
Did you try the thread I linked and do what it said to test if you eMMC is fried? If it is, only a hardware repair will fix it.
Hi,
I tried that link. I go through the recovery mode and get the android system recovery and the :
e:cant mount /cache
......
etc.
I issue the adb shell command and get
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Any more hints?
filking said:
Any more hints?
Click to expand...
Click to collapse
Mate, there is obviously some connection problem between your PC and your device. The most likely of all: it is a USB driver related problem. I'm trying to help last few days to another forum mate @PieceofSlice who has almost identic problem. He is on 04.01 bootloader and uses Windows 7 PC.
Please take my advice and don't try to flash bootloader anymore until you are 100% sure that the fastboot connection works perfectly fine. If your bootloader gets erased and the new one doesn't get flashed, the Tab is hard-bricked and only JTAG service will can revive it. As long as your bootloader is OK, you will get your tab working again, don't worry.
Actually it would be worth it to install Linux besides Windows and execute fastboot directly from there. Linux needs no drivers and always works. IDK if Ubuntu could also work if you run it in a Virtual Machine in Windows.
tetakpatalked from P5110
Thanks for your reply.
Actually, the more I think about it, the more I think it is the connection socket on the tablet that is faulty, rather than the link/pc.
I've had occasions when moving the cable near the socket, (which appears a tad loose), has caused the tablet to stop charging then start again.
This tablet is a replacement for a broken N7 (2012) that I got from a retail shop in the UK. As they gave me a new receipt, this tab is covered under year warranty. If I take it into the shop, they will refund and replace, no problem.
My last question is, how can I ensure that all info is wiped. (pretty sure it already is), but as the stock/unroot failed, it prob didn't actually overwrite anything.
ta
Just one crucial question: is your bootloader locked?
If it is, you can give it back. They will unbrick it the way that they will totally wipe whole internal memory before they flash a factory image.
tetakpatalked from P5110
It is unlocked.
Not sure this retail shop will know what to look for when I return it, turn it on, and it doesn't boot. That in my mind is broken and they will prob see it that way.
If they do spot it, or refuse.. I will take it away, rethink, and return to another branch, lots locally.
Unless, NRT will let me remove the lock... maybe....
filking said:
It is unlocked.....
Click to expand...
Click to collapse
Try to execute in the bootloader mode "fastboot oem lock"
tetakpatalked from P5110
OK, all guys with fastboot conectivity problems, it really makes me sad to read about your issues and I hate to hear about bootloops and desperate forum mates!
Therefore, I think this will be solution for most of you: I will post here a new guide within less than 24 hours how to install ADB and fastboot in Ubuntu/Linux OS. If you already have installed Ubuntu OS, it takes only 2 min to install ADB and fastboot.... and IT WORKS THERE!
Linux is in general much better than Windows for flashing Android devices. And it needs no stupid, nasty drivers so the things can't go so easy wrong.
Use this time and already install Ubuntu aside your Windows. In most of cases it works flawlessly. You will have dual boot possibility. Please check WWW how to do it, it costs bit of time but it is really easy afterwards.
tetakpatalked from Nexus 7
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Yep, connection problems....in very most of cases it is related to unproperly working drivers = as I said: not Windows but "Loose-dows"
tetakpatalked from Nexus 7
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Mate, here is my promissed thread:
http://forum.xda-developers.com/showthread.php?t=2726287
If Ubuntu won't flash successfully, we have a hardware related problem and it has to be fixed in the service.
tetakpatalked from Nexus 7
Looking now..
Thanks a lot.
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
This past Aug I upgraded via OTA update to Android P 9.0 - Didn't like the updates but mostly was just visual disappointment with the GUI stuff. Earlier today I noticed my device asking me to restart to apply a new update, and being hesitant I decided to hold off.
Few hours later pulled my device out of my pocket to find a screen displaying in recovery mode only two options
1) Try Again
2) Factory data reset
I tried to just reboot by holding down the power but again it default loops to recovery mode with those two options.
Recovery mode displays the following information (which basically tells me my device decided to update itself even though I was holding off on it)
9/PPR2.181005.003/4284323
After realizing this was a real issue I found that I am able to get into fastboot mode and download mode however I am not sure this can help me.
Below is a list of the fastboot set variables
(bootloader) keep_efs:no
(bootloader) is_oem_unlocked:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.0
(bootloader) hw-color:RCW
(bootloader) hw-variant:GA00138-US
(bootloader) hw-revision:rev_10
(bootloader) cid:00000000
(bootloader) erase-block-size:0x1000
(bootloader) logical-block-size:0x1000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4249
(bootloader) version-laf:1.0.7
(bootloader) version-baseband:g8998-00253-1805232234
(bootloader) version-bootloader:TMZ20k
(bootloader) version-abl:TMZ20k
(bootloader) version-aes:TMZ20k
(bootloader) version-cmnlib:TMZ20k
(bootloader) version-cmnlib64:TMZ20k
(bootloader) version-devcfg:TMZ20k
(bootloader) version-hyp:TMZ20k
(bootloader) version-keymaster:TMZ20k
(bootloader) version-pmic:TMZ20k
(bootloader) version-rpm:TMZ20k
(bootloader) version-xbl:TMZ20k
(bootloader) variant:MSM UFS
(bootloader) partition-type:laf_b:raw
(bootloader) partition-size:laf_b: 0x3000000
(bootloader) partition-type:laf_a:raw
(bootloader) partition-size:laf_a: 0x3000000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x800000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x800000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2800000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2800000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-typeersist:ext4
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1C26BFB000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) has-slot:laf:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:radio:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:1
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:a,b,
(bootloader) secure:yes
(bootloader) serialno:711KPFX0872315
(bootloader) product:taimen
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) qem:0
I feel that since it's sort of locked up I am kinda screwed software wise. IDK...
I also run into a screen sometimes just before powering down that reads "Can't find valid operating system. The device will not start Visit this link on another device g.co/ABH ID C382B665"
--
I do not want to wipe the userdata because I have information that is far more valuable then this device is worth.
I am wondering if anybody has some suggestions on ways to obtain the userdata?
I would rip this device apart if I have to just to have a better chance of securing my data so please let me know if you have any ideas.
Thanks!
Flash the latest update on device using flashall.bat. make sure -w option is removed from the batch file. Might be able to get you up and running without losing data.
This can be done from bootloader mode
Sent from my Pixel 2 XL using Tapatalk
piyush7243 said:
Flash the latest update on device using flashall.bat. make sure -w option is removed from the batch file. Might be able to get you up and running without losing data.
This can be done from bootloader mode
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
All locked up and cannot flash it.
C:\Users\hacktron\Desktop\taimen-ppr2.181005.003-factory-f0a1d2c1\taimen-ppr2.181005.003>flash-all.bat
< waiting for any device >
Sending 'bootloader_a' (36336 KB) OKAY [ 0.810s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.827s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.005s
Sending 'radio_a' (60388 KB) OKAY [ 1.352s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXXXXXXXXXX
--------------------------------------------
Checking product OKAY [ 0.007s]
Checking version-bootloader OKAY [ 0.004s]
Checking version-baseband OKAY [ 0.006s]
extracting boot.img (40 MB) to disk... took 0.184s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2207 MB) to disk... took 11.183s
archive does not contain 'system.sig'
extracting system_other.img (322 MB) to disk... took 1.791s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB) to disk... took 1.894s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (40960 KB) OKAY [ 0.892s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 20.825s
Press any key to exit...
have you tried deuces recovery script i think it overwrites the lock state.
sideload OTA.
use the last version you had on the phone while it was working.
As stated above suggesting the ota file is your best option I have a pixel that corrupts itself if I try updating any other way and it works without losing data
Your bootloader apparently is locked. To add to what the two previous posters have said, an OTA image can be sideloaded regardless of the lock status of the bootloader. Since the OTA image is a complete ROM you should be able to get up and running with minimal fuss.
Strephon Alkhalikoi said:
Your bootloader apparently is locked. To add to what the two previous posters have said, an OTA image can be sideloaded regardless of the lock status of the bootloader. Since the OTA image is a complete ROM you should be able to get up and running with minimal fuss.
Click to expand...
Click to collapse
Tried the above with no luck. I cannot side load OTA because I do not have access to adb, only fastboot. However I did try the deuces script two times, once to continue without unlocking and again with the to unlock bootloader options, but it failed to flash.
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.004s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.007s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.824s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.836s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.006s
Sending 'radio_a' (60388 KB) OKAY [ 1.353s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.365s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.006s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.008s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.820s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.831s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_a' (60388 KB) OKAY [ 1.355s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.007s
Sending 'abl_a' (540 KB) OKAY [ 0.014s]
Writing 'abl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.023s
Sending 'aes_a' (48 KB) OKAY [ 0.004s]
Writing 'aes_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.885s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.895s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'devcfg_a' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.189s
Sending 'hyp_a' (264 KB) OKAY [ 0.009s]
Writing 'hyp_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'keymaster_a' (308 KB) OKAY [ 0.010s]
Writing 'keymaster_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'laf_a' (29800 KB) OKAY [ 0.648s]
Writing 'laf_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.658s
Sending 'modem_a' (60380 KB) OKAY [ 1.315s]
Writing 'modem_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.326s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.003s]
Writing 'pmic_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.008s]
Writing 'rpm_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'tz_a' (1868 KB) OKAY [ 0.042s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.052s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.012s
Sending 'vendor_a' (360340 KB) OKAY [ 7.858s]
Writing 'vendor_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.868s
Sending 'xbl_a' (2620 KB) OKAY [ 0.061s]
Writing 'xbl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.073s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.134s]
Writing sparse 'system_a' 1/5 FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 16.946s
Flashing System B
Sending 'system_b' (330216 KB) OKAY [ 7.412s]
Writing 'system_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.422s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.008s
Sending 'abl_b' (540 KB) OKAY [ 0.016s]
Writing 'abl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.032s
Sending 'aes_b' (48 KB) OKAY [ 0.005s]
Writing 'aes_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.924s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.939s
Sending 'cmnlib_b' (220 KB) OKAY [ 0.009s]
Writing 'cmnlib_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'cmnlib64_b' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'devcfg_b' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.187s]
Writing 'dtbo_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.202s
Sending 'hyp_b' (264 KB) OKAY [ 0.009s]
Writing 'hyp_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.025s
Sending 'keymaster_b' (308 KB) OKAY [ 0.011s]
Writing 'keymaster_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.027s
Sending 'laf_b' (29800 KB) OKAY [ 0.672s]
Writing 'laf_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.689s
Sending 'modem_b' (60380 KB) OKAY [ 1.363s]
Writing 'modem_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.379s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.004s]
Writing 'pmic_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'rpm_b' (232 KB) OKAY [ 0.007s]
Writing 'rpm_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'tz_b' (1868 KB) OKAY [ 0.044s]
Writing 'tz_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.053s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.011s
Sending 'vendor_b' (360340 KB) OKAY [ 8.112s]
Writing 'vendor_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 8.122s
Sending 'xbl_b' (2620 KB) OKAY [ 0.063s]
Writing 'xbl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.078s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.009s
Format Userdata[Y/N]?
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 40c24edc-c81a-11e8-8c97-ad6213ea0a12
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' (4672 KB) OKAY [ 0.109s]
Writing 'userdata' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.620s
Press any key to continue . . .
Finished Flashing... if you are still having bootloops, you may need to format userdata in factory recovery
DO NOT LOCK THE BOOTLOADER UNLESS YOU ARE SURE IT IS OPERATING PROPERLY
You need to boot into recovery mode, which you said your phone was on when you removed it from pocket, once in there hold volume up and press the power button.
Then you can go to option Apply update from ADB, select that and sideload will be possible.
If you want you can also temporarily launch twrp from fastboot, and try installing the OTA that way.
This will not install a new recovery or modify anything on your phone.
>fastboot boot c:\twrp.img
hacktron said:
Tried the above with no luck. I cannot side load OTA because I do not have access to adb, only fastboot. However I did try the deuces script two times, once to continue without unlocking and again with the to unlock bootloader options, but it failed to flash.
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.004s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.007s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.824s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.836s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.006s
Sending 'radio_a' (60388 KB) OKAY [ 1.353s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.365s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.006s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.008s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.820s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.831s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_a' (60388 KB) OKAY [ 1.355s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.007s
Sending 'abl_a' (540 KB) OKAY [ 0.014s]
Writing 'abl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.023s
Sending 'aes_a' (48 KB) OKAY [ 0.004s]
Writing 'aes_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.885s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.895s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'devcfg_a' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.189s
Sending 'hyp_a' (264 KB) OKAY [ 0.009s]
Writing 'hyp_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'keymaster_a' (308 KB) OKAY [ 0.010s]
Writing 'keymaster_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'laf_a' (29800 KB) OKAY [ 0.648s]
Writing 'laf_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.658s
Sending 'modem_a' (60380 KB) OKAY [ 1.315s]
Writing 'modem_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.326s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.003s]
Writing 'pmic_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.008s]
Writing 'rpm_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'tz_a' (1868 KB) OKAY [ 0.042s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.052s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.012s
Sending 'vendor_a' (360340 KB) OKAY [ 7.858s]
Writing 'vendor_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.868s
Sending 'xbl_a' (2620 KB) OKAY [ 0.061s]
Writing 'xbl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.073s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.134s]
Writing sparse 'system_a' 1/5 FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 16.946s
Flashing System B
Sending 'system_b' (330216 KB) OKAY [ 7.412s]
Writing 'system_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.422s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.008s
Sending 'abl_b' (540 KB) OKAY [ 0.016s]
Writing 'abl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.032s
Sending 'aes_b' (48 KB) OKAY [ 0.005s]
Writing 'aes_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.924s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.939s
Sending 'cmnlib_b' (220 KB) OKAY [ 0.009s]
Writing 'cmnlib_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'cmnlib64_b' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'devcfg_b' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.187s]
Writing 'dtbo_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.202s
Sending 'hyp_b' (264 KB) OKAY [ 0.009s]
Writing 'hyp_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.025s
Sending 'keymaster_b' (308 KB) OKAY [ 0.011s]
Writing 'keymaster_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.027s
Sending 'laf_b' (29800 KB) OKAY [ 0.672s]
Writing 'laf_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.689s
Sending 'modem_b' (60380 KB) OKAY [ 1.363s]
Writing 'modem_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.379s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.004s]
Writing 'pmic_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'rpm_b' (232 KB) OKAY [ 0.007s]
Writing 'rpm_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'tz_b' (1868 KB) OKAY [ 0.044s]
Writing 'tz_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.053s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.011s
Sending 'vendor_b' (360340 KB) OKAY [ 8.112s]
Writing 'vendor_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 8.122s
Sending 'xbl_b' (2620 KB) OKAY [ 0.063s]
Writing 'xbl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.078s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
Finished. Total time: 0.009s
Format Userdata[Y/N]?
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 40c24edc-c81a-11e8-8c97-ad6213ea0a12
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' (4672 KB) OKAY [ 0.109s]
Writing 'userdata' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.620s
Press any key to continue . . .
Finished Flashing... if you are still having bootloops, you may need to format userdata in factory recovery
DO NOT LOCK THE BOOTLOADER UNLESS YOU ARE SURE IT IS OPERATING PROPERLY
Click to expand...
Click to collapse
Maybe I'm wrong, and maybe I'm not understanding what's going on, but unlocking the bootloader completely wipes the phone. Including user data.
@exist2resist: His bootloader is apparently locked, meaning he cannot temp boot TWRP.
@Soured Lie: You would be correct. Attempting to unlock the bootloader would wipe the data.
@hacktron: Why are you attempting to unlock the bootloader when no one told you to do so? If you had succeeded you would have lost all that data you say is more valuable than the phone itself. You would have had no one to blame but yourself. Since you're having difficulty, this page may be of use to you. Follow its instructions and you should have no issue restoring your device.
Strephon Alkhalikoi said:
@exist2resist: His bootloader is apparently locked, meaning he cannot temp boot TWRP.
@Soured Lie: You would be correct. Attempting to unlock the bootloader would wipe the data.
@hacktron: Why are you attempting to unlock the bootloader when no one told you to do so? If you had succeeded you would have lost all that data you say is more valuable than the phone itself. You would have had no one to blame but yourself. Since you're having difficulty, this page may be of use to you. Follow its instructions and you should have no issue restoring your device.
Click to expand...
Click to collapse
Ok so I'm not confused then. He should be happy he didn't succeed. I was wondering wth he was doing if he wanted to keep his data.
Soured Lie said:
Ok so I'm not confused then. He should be happy he didn't succeed. I was wondering wth he was doing if he wanted to keep his data.
Click to expand...
Click to collapse
I am soo happy it didn't succeed! I Just didn't know if I screwed it all up already or not. It's been a few years since I have played around devices. Should have kept on it.
@Strephon Alkhalikoi - Hear you load and clear. I assumed ADB was not able to connect but I am going to go back when I have a chance and make sure the drivers are all there, then try to sideload OTA again as it was originally suggested.
Really appreciate the feedback from y'all.
@Strephon Alkhalikoi
What does he do if he didn't have debugging enabled from settings?
Soured Lie said:
@Strephon Alkhalikoi
What does he do if he didn't have debugging enabled from settings?
Click to expand...
Click to collapse
You don't need to enable ADB to connect in recovery. It is required only to connect when phone is booted and running.
So I just got back and checked it out. Seems like my device is only recognized by device manager in the following ways...
bootloader mode (fastmode) as Lemobile Android Device
download mode as USB Serial Device (COMX)
When in Recovery mode its not recognized at all and my recovery mode menu is just those two options as originally described.
Any ideas?
hacktron said:
So I just got back and checked it out. Seems like my device is only recognized by device manager in the following ways...
bootloader mode (fastmode) as Lemobile Android Device
download mode as USB Serial Device (COMX)
When in Recovery mode its not recognized at all and my recovery mode menu is just those two options as originally described.
Any ideas?
Click to expand...
Click to collapse
Since you want to keep your data, your best bet is to borrow/beg/steal a computer,
copy adb file set into it, and run adb sideload ota.zip.
Small package is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
michaelbsheldon said:
Since you want to keep your data, your best bet is to borrow/beg/steal a computer,
copy adb file set into it, and run adb sideload ota.zip.
Small package is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
I am confused lol
I have a computer. I just also installed android studio and updated the sdk usb drivers, and I thought I had previously installed the drivers because I have been using this phone and pc together for sometime now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[baby bird needs a spoon feeding ]
You may have reached an big, ugly fork in the road:
1.) pay big $$ to forensic technician to retrieve the phone's data
2.) do what it says, wipe the phone, and if no hardware issues present, it should run fine
michaelbsheldon said:
You may have reached an big, ugly fork in the road:
1.) pay big $$ to forensic technician to retrieve the phone's data
2.) do what it says, wipe the phone, and if no hardware issues present, it should run fine
Click to expand...
Click to collapse
figures!
Lesson learned, don't leave your phone stock and lose faith in Google too!
Thx all for your help!
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.