I was here back in the 2008/09 era. I got a new One Plus 8 5G (T-Mobile) direct from One Plus. It's brand new T-Mobile Version. This device is network unlocked (whatever that means) I did the updates to Android 11 and Oxygen OS. Factory reset and checked to make sure the network unlocked feature was greyed out. It wasn't, so I unlocked it again. It's greyed out again. Always greyed out unless you factory reset it.
I have it on Verizon but I have T-mobile network service as well. The One Plus messages (default app) is broken, only sends but does not receive. Google messages does it all without any text issues. Could be OS related or version related , but One Plus Messages has been a known issue with the One Plus 8 models.
I want to run the Global Rom. I downloaded the official global rom from One Plus, put it in my root storage menu. A youtube video says that you should keep it there until another update is released. At that point I can use the system update to point to (local upgrade) the global rom in my storage and install it. This is more of a hack without unlocking the boot loader. One Plus will send me a token to unlock the bootloader if I request it.
I want it to be a clean phone good on any network with the global rom and no bloatware. Do I need the token to install the global rom? The youtube video guy had Android 11 on it when performing his global rom install vs. Android 10 to global rom. The phone came with Android 10.
Yes u need the unlock token to switch to global rom. Tmo rom is cancer, request for bootloader unlock and use the fastboot method to install global oxygen os and profit.
Anybody know where to find the correct windows 10 USB drivers for OnePlus phones. On the bright side, I can't brick my phone if I don't have the correct USB drivers.
Ok, I got the USB drivers working.
Now I am hung up on this part below (Step 3) I can't get the unlock code. The filename, directory name, or volume label syntax is incorrect. After entering all the info in Step 4 on the 3rd entry with the oem get unlock code.
I enabled developer mode, Enabled Oem lock, downloaded the ADB software etc.
Step 4. Enter fastboot mode to get unlock code
Download “fastboot_windows.zip” and unzip it on your computer. Remember the “root directory ”
Power off your OnePlus 6T. Press and hold“Volume +”and “Volume -”.Then Press power key to enter “fastboot mode”
Connect to your computer > Command：cd “root directory ”> Command: fastboot.exe oem get_unlock_code
Using this thread as a notebook. >>>>> fastboot oem get_unlock_code <<<<<<< is the correct way to get the unlock code.
If someone can give me a link to the correct USB drivers for the Oneplus 8, I can get this thing unlocked.
Right now the phone hangs on "waiting for device". I need USB drivers that will work in fast boot. I switched the USB to MTP (file transfer) in developer settings, but it does not translate to fast boot.
Update, I tend to learn through osmosis. A little sleep and the insight downloaded upon thee. Ok, so I submitted my OnePlus Unlock token form.
All I want is the Global Rom when all is said and done. I am waiting on a Verizon 5G sim card. The 4G sim card from my old phone has problems receiving texts. I think it has more to do with the 4G sim card on a 5G phone. The phone works perfect on the T-mobile network.
For the life of me I cannot figure out how to flash my unlock token into my OnePlus 8
I am in fastboot mode. I have the root files in the correct order. The instructions say Command: fastboot flash cust-unlock <unlock_token.bin>
My file is unlock_code.bin
What is the correct syntax to write to get the cmd to recognize my target file unlock_code.bin and flash it to unlock my phone. In the past the instructions have been wrong. With DOS codes you have to have it exact or you get syntax error.
Fixed, after a few minutes of suicidal ideations, I got my unlock token to take. My bootloader is now unlocked.
Two Sheets said:
For the life of me I cannot figure out how to flash my unlock token into my OnePlus 8
I am in fastboot mode. I have the root files in the correct order. The instructions say Command: fastboot flash cust-unlock <unlock_token.bin>
My file is unlock_code.bin
What is the correct syntax to write to get the cmd to recognize my target file unlock_code.bin and flash it to unlock my phone. In the past the instructions have been wrong. With DOS codes you have to have it exact or you get syntax error.
Click to expand...
Click to collapse
you can use the TOOL ALL IN ONE which helps you unlock the bootloader and does the cmd stuff for you. Link on my thread and scroll down: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.
Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.
Two Sheets said:
That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.
Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.
Click to expand...
Click to collapse
Here's T-MO Android 10. After flashing re-unlock the bootloader and flash this version of the GLOBAL ROM in fastboot. After succefully on Global, just boot up and take the OTA to the latest version and your golden.
Two Sheets said:
That wouldn't be any fun. I have to learn to do this myself without making mistakes. The end justifies the means, my bootloader is unlocked now.
Can you point me to the correct T-mobile stock Android 10 OS rom file? I am on Android 11 and need the stock file to be able to load the global rom.
Click to expand...
Click to collapse
The T-MO Android 10 link I gave you is via MSM tool as thats the only version of stock firmware we have for Android 10 on T-MO. If you've never used MSM tool before you might have driver issues, DM me if you need.
Edit: My first post had the wrong link for the Global ROM you need. HERE is the correct link and I updated my post above too.
I am confused here. The MSM tool is asking me for passwords. I thought it was plug and play. Factory resetting my phone deleted the phone drivers in Windows 10.
And the next question. If the Android 11 version (on my phone) is older than the Global Rom from OnePlus on Android 11. Why can't I just flash the global version now that my bootloader is unlocked?
Ok, I fixed my connection issues. Now the question. What state do I load my phone into to get the updates started via MSM tools? I have the correct ROm, but I don't know how to get it started.
I am on stock Android 10 now. I am having troubles installing the 10.5.12 global rom. When I use the flash all bat command line in the rom. It starts fine but hangs with "waiting for device"
Below is what the command prompt says from my Rom flash attempts. The same thing happened 2x. It hangs on < waiting for any device >. I left it on for 30 minutes without progress at that point.
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.275s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 210903704 (102980 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600
Info: Overprovision ratio = 0.620%
Info: Overprovision segments = 645 (GC reserved = 330)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.009s]
Writing 'userdata' OKAY [ 0.002s]
Erasing 'metadata' OKAY [ 0.001s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.233s
Sending 'boot_a' (98304 KB) OKAY [ 2.271s]
Writing 'boot_a' OKAY [ 0.413s]
Finished. Total time: 2.780s
Sending 'dtbo' (8192 KB) OKAY [ 0.191s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.253s
Sending 'modem_a' (524288 KB) OKAY [ 12.122s]
Writing 'modem_a' OKAY [ 1.955s]
Finished. Total time: 14.523s
Sending 'recovery' (102400 KB) OKAY [ 2.361s]
Writing 'recovery' OKAY [ 0.392s]
Finished. Total time: 2.857s
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.023s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Two Sheets said:
I am on stock Android 10 now. I am having troubles installing the 10.5.12 global rom. When I use the flash all bat command line in the rom. It starts fine but hangs with "waiting for device"
Below is what the command prompt says from my Rom flash attempts. The same thing happened 2x. It hangs on < waiting for any device >. I left it on for 30 minutes without progress at that point.
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.275s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 210903704 (102980 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600
Info: Overprovision ratio = 0.620%
Info: Overprovision segments = 645 (GC reserved = 330)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.009s]
Writing 'userdata' OKAY [ 0.002s]
Erasing 'metadata' OKAY [ 0.001s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.233s
Sending 'boot_a' (98304 KB) OKAY [ 2.271s]
Writing 'boot_a' OKAY [ 0.413s]
Finished. Total time: 2.780s
Sending 'dtbo' (8192 KB) OKAY [ 0.191s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.253s
Sending 'modem_a' (524288 KB) OKAY [ 12.122s]
Writing 'modem_a' OKAY [ 1.955s]
Finished. Total time: 14.523s
Sending 'recovery' (102400 KB) OKAY [ 2.361s]
Writing 'recovery' OKAY [ 0.392s]
Finished. Total time: 2.857s
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.023s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Click to expand...
Click to collapse
This is a driver issue. Download the latest Google USB drivers and make sure your device is showing up correctly as "Android Bootloader Interface" in device manager.
Related
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
iconoclasthero said:
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Click to expand...
Click to collapse
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
dia_naji said:
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
Click to expand...
Click to collapse
Unzip the stock image and use fastboot to flash each part individually.
fastboot flash worked.
iPWNtehNOOB said:
Unzip the stock image and use fastboot to flash each part individually.
Click to expand...
Click to collapse
I downloaded hammerhead-krt16m-factory-bd9c39de.tgz (md5sum: 3a7b6cb66f8ec20edf661aee2d73d3a4) from hammerhead-krt16m-factory-bd9c39de.tgz, which I assume is the download site from developers dot google dot com images#hammerheadkrt16m.
When I tried to send the files with fastboot yesterday, it just hung.
I downloaded everything again this morning and got a different md5sum (36aa82ab2d7d05ee144d18546565cd5f) and instead of trying to manually fastboot the files over I executed the script
Code:
sudo ./flash-all.sh
sending 'bootloader' (2506 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
OKAY [ 0.471s]
finished. total time: 0.760s
rebooting into bootloader...
OKAY [ 0.136s]
finished. total time: 0.136s
sending 'radio' (42033 KB)...
OKAY [ 1.508s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.407s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: []
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8620 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.744s]
sending 'recovery' (9202 KB)...
OKAY [ 0.536s]
writing 'recovery'...
OKAY [ 0.778s]
erasing 'system'...
OKAY [ 1.323s]
sending 'system' (692940 KB)...
OKAY [ 21.913s]
writing 'system'...
OKAY [ 47.401s]
erasing 'userdata'...
OKAY [ 19.268s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 14.185s]
erasing 'cache'...
OKAY [ 0.669s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.907s]
rebooting...
finished. total time: 110.048s
I guess I had a corrupt download then. Thanks for the help.
Any idea why I could boot into Clockwork but CM just hung? Any additional things to try? Will CM boot without a SIM card?
On the plus side while messing around with trying to get this fixed, I stumbled on a way to get my new nvidia drivers working for the EVGA GTX650 I bought to power my twin 27" displays, so I guess that is also a plus!
same but now works
I just reinstalled recovery again and cm 11.
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
emmanuel_baez said:
I flashed a modified 44s ota over a 33r ROM (stock) file to my device and lost the ability to boot. Whenever I try to flash via fastboot I get the error: "FAILED (remote: partition table doesn't exist)"
Does anyone have a way of repairing this? Would love to start using this device again. Thanks in advance :good:
Click to expand...
Click to collapse
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
skyguy126 said:
Do this at your own risk:
Go into fastboot and flash 38R. (Available at current time on cygen's site) Flash everything including userdata. Reboot and you should be at the home screen. Then when you are here ota update through settings. Not recommended to modify ota, just do it after the ota if possible. (You might have to unlock the bootloader to follow this guide)
Click to expand...
Click to collapse
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
He still has access to fastboot which means he can reflash stock firmware.
Not with borked partitions.
Transmitted via Bacon
timmaaa said:
Not with borked partitions.
Transmitted via Bacon
Click to expand...
Click to collapse
Shouldn't it work with the Official signed 44s Fastboot Image that was released yesterday by Cyanogen?
Not if the partitions are borked. It can't flash to a partition table that doesn't exist. It's like trying to serve dinner onto thin air, it has nowhere to go.
Transmitted via Bacon
And there will be no way to repartition? Guess that something like using parted should work on nand, assumed the right partition tables are known...
It's possible, but getting it done can be tricky. I myself have zero experience in trying to repartition.
Transmitted via Bacon
Note to self: triple check the version numbers before flashing lol
Sorry op I have no constructive feedback
Sent from my A0001 using XDA Free mobile app
timmaaa said:
I don't think that's going to work, he's borked his partitions. And the modified OTA wasn't technically the problem. The problem is that he flashed an OTA on top of an incorrect preceding build. It should have gone 33>38>44 but instead went 33>44. Because it was a modified OTA with a modified installer script, the safeguard that would normally stop such a mistake from happening had been disabled. Modified OTA's are perfectly fine, as long as you take them in the right sequence.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
emmanuel_baez said:
@timmaaa you were correct I attempted that and it failed. I resolved my problem by flashing calkulin's stock mod 44s. I've come across another issue now. Occasionally the devices screen won't come on at all. I'll have to completely reboot the phone for it to work. Is this an issue on 44s or is there another problem under the hood?
Click to expand...
Click to collapse
I am running CM11 nightlies, and this issue happens to me (and also on my nexus 5 using milestone builds) ONLY when I am using the Ondemand governor. If you're using that, try changing and see what happens.
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
emmanuel_baez said:
Ah yes I am using ondemand. I switched it from interactive last night. Didn't think of that thanks I'll test it.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Please make sure to report back, could be valuable info. I haven't found anyone else discussing this potential cause of the problem, but others do seem to have it.
Sent from my A0001 using XDA Free mobile app
So far it hasn't done it since I changed back to interactive.
Sent from my A0001 using XDA Free mobile app
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
majzoob said:
Hello,
I need some help with a Oneplus One that is stuck on the Cyanogen boot image. I bought this for cheap thinking that I could fix it, but 3 hours later still no luck. I have access to TWRP and Fastboot, which made me hopeful, but no access to the storage on the device.
1. TWRP: I can’t mount /data, /cache/ persist (shows E:Unable to mount ‘/data’, etc). I can mount /firmware or /system.
Trying to sideload a bunch of different roms gives me this in the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload cm12.zip
loading: 'cm12.zip'* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
2. Fastboot: trying to flash individual files with fastboot gives me “remote: flash write failure”. I’ve also gotten a “partition table doesn’t exist” error.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I tried these directions and got this:
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.802s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.860s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.076s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.077s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.014s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'tz' (321 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.071s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.014s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.326s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 5.394s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 56d36153
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (6372 KB)...
OKAY [ 0.205s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.297s
Press any key to exit...
From what I've read, I think Heisenberg will say that the partitions are borked, but I'm hoping I'm a little luckier than others who do not have access to fastboot or twrp. Any suggestions?
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
try OTG cable ... ?
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me, but did get recovery going. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on a flash drive. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Jimmy Rudedog said:
I messed up my One by deleting stuff I should not have... it would not read the internal "sd card" memory at all... so nothing would flash to the phone. I had fastboot and TWRP working. I tried this kit and it only partially worked for me. What I did get to work is by connecting an on-the-go cable to it and put the files to flash on it. The phone will find it in TWRP if you set it up to read the OTG cable. Then flash away something that will boot up... then go from there with the ROM you want to use. Using the Caulkin's ROM mentioned earlier will get it at least running. This worked for me, and may work for you too.
Click to expand...
Click to collapse
That won't work in this situation, he hasn't merely deleted everything, the partition table is borked.
Thanks for the reply. I'd previously read that, but thought it didn't apply because I have fastboot and recovery. I'm trying it now, but I can't get the device to show up in Device Manager. The phone goes to the charger screen when connected and it shows up as MTP USB Device. I tried seeing if it would show up on the downloadtool.exe he mentions, but no go.
I have tried to flash a new system on my new Pixel but I am getting the above message.
I am using Ubuntu Linux with the stock android-tools-adb and andoid-tools-fastboot installed.
The same tools are working fine on my nexus5 phones.
Yes I enabled USB debugging and unlocked the bootloader.
Can anyone tell me what is different with Pixel phones?
adb version gives: Android Debug Bridge version 1.0.31
Have you tried the latest version of Android tools? I haven't used adb or fastboot with the pixel yet but know with past nexus devices I have experienced this error because I wasn't using the latest Android tools
I can't remember the exact specifics since I do not have a factory image available to me atm...
BUT, I believe you extract the contents of the image.zip and then use a text editor to individually add the flash commands for the content found inside the image.zip to the flash-all.sh (i.e. "fastboot flash system system.img.")
metricusa said:
...
adb version gives: Android Debug Bridge version 1.0.31
Click to expand...
Click to collapse
Update your ADB tools. The latest version is 1.0.36, I believe.
sn0warmy said:
Update your ADB tools. The latest version is 1.0.36, I believe.
Click to expand...
Click to collapse
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.
metricusa said:
This version of ADB is the latest in the ubuntu repositories. I did not find a newer version there.
Can anyone tell me how I can get a newer ADB and fastboot? It's not in the Android SDK package.
I want only the binary not the whole SDK as I have nothing to do with it.
Click to expand...
Click to collapse
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790
McMarius11 said:
Here Download the Portable Version it worked great for me
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
I have Ubuntu Linux. The link seems to have only windows executables.
OK so I upgraded fastboot and adb. Actually upgraded my ubuntu to latest version.
fastboot getvar version prompts version 0.5 for fastboot.
I managed to load the latest version NMF26Q onto the pixel but I am still getting an error. The Pixel appears to boot and work OK.
I am worried about the error though and wondered if anyone can figure out what it means and how I could mitigate it. See below output from flash-all.sh
Again, please remember I use Linux (ubuntu)
+++++++++++
~/Downloads/sailfish-nmf26q$ sudo ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (32728 KB)...
OKAY [ 0.831s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
OKAY [ 0.709s]
finished. total time: 1.541s
rebooting into bootloader...
OKAY [ 4.155s]
finished. total time: 4.255s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 0.564s]
finished. total time: 1.986s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.147s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot' (24821 KB)...
OKAY [ 0.642s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.311s]
sending sparse 'system' (516463 KB)...
OKAY [ 12.712s]
writing 'system'...
OKAY [ 5.004s]
sending sparse 'system' (520623 KB)...
OKAY [ 12.805s]
writing 'system'...
OKAY [ 7.138s]
sending sparse 'system' (517483 KB)...
OKAY [ 12.772s]
writing 'system'...
OKAY [ 5.491s]
sending 'vendor' (235186 KB)...
OKAY [ 5.806s]
writing 'vendor'...
OKAY [ 3.796s]
erasing 'userdata'...
OKAY [ 1.805s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist)
finished. total time: 73.441s
Follow Method 2 here - it worked for me, as i had the same issue as you:
http://www.theandroidsoul.com/flash-firmware-factory-image-google-pixel/
OK I finally figured it out.
To clarify, the purpose was to burn a factory image and start from scratch. (no sideload). All without having to install Android studio or the SDK manager or whatever. This is a guide for Linux but I believe this method works in Windows as well with appropriate syntax.
1. First rule is to NEVER try to use a version of fastboot other than the one "prescribed" for the image you want to burn. To learn what version to use check Google's SKD Platform release Notes here: https://developer.android.com/studio/releases/platforms.html (my major mistake was to think that ubuntu would have the latest fastboot available in its repositories. Don't even try!)
2. Find the SDK Platform Tools version indicated on the above page. (In my case: Android SDK Platform-Tools 25.0.1 as I wanted to burn Android 7.1.1.). Google does not make them available AFAIK but other people do. I found them here: http://androidsdkoffline.blogspot.com/p/android-sdk-platform-tools.html OR do a Google Search.
3. Unpack the platform tools and the Factory image you wish to burn. Then copy fastboot from the Platform Tools directory to the image directory.
4. run fastboot from inside the directory. You can do this in at least 2 ways:
4a- manually run one-by-one the commands listed in the flash-all.sh script making sure you add sudo ./ in front of each fastboot command
4b- edit flash-all.sh and add sudo ./ in front of each fastboot command. Then run the flash-all script by typing ./flash-all.sh
There are of course more ways but I found this to be the simplest method as it doesn't involve installing any package and/or modifying your system variables. Plus, after you are done you can simply delete all files and directories you created.
Hope this helps other people too.
A final observation: It appears to me that starting with pixel the phones have 2 bootable sectors "slot a" and "slot b". See output below:
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1610061102
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FAxxxx
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (24821 KB)...
OKAY [ 0.642s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.415s]
sending sparse 'system_a' 1/3 (516463 KB)...
OKAY [ 12.799s]
writing 'system_a' 1/3...
OKAY [ 5.009s]
sending sparse 'system_a' 2/3 (520623 KB)...
OKAY [ 14.101s]
writing 'system_a' 2/3...
OKAY [ 7.052s]
sending sparse 'system_a' 3/3 (517483 KB)...
OKAY [ 12.818s]
writing 'system_a' 3/3...
OKAY [ 5.449s]
erasing 'system_b'...
OKAY [ 0.354s]
sending sparse 'system_b' 1/4 (522362 KB)...
OKAY [ 12.856s]
writing 'system_b' 1/4...
OKAY [ 3.890s]
sending sparse 'system_b' 2/4 (514082 KB)...
OKAY [ 12.758s]
writing 'system_b' 2/4...
OKAY [ 4.302s]
sending sparse 'system_b' 3/4 (524026 KB)...
OKAY [ 12.967s]
writing 'system_b' 3/4...
OKAY [ 3.839s]
sending sparse 'system_b' 4/4 (88446 KB)...
OKAY [ 2.260s]
writing 'system_b' 4/4...
OKAY [ 0.842s]
erasing 'vendor_a'...
OKAY [ 0.153s]
sending 'vendor_a' (235186 KB)...
OKAY [ 5.804s]
writing 'vendor_a'...
OKAY [ 3.846s]
Setting current slot to 'a'...
OKAY [ 0.099s]
erasing 'userdata'...
OKAY [ 1.806s]
sending 'userdata' (138957 KB)...
OKAY [ 3.451s]
writing 'userdata'...
OKAY [ 1.301s]
rebooting...
finished. total time: 129.610s
So I decided to flash the latest factory image available for the N5 today. I was running Build MOB30Y. I did it using Nexus Root Toolkit and I chose the 'No Wipe Mode', it says that it failed. Here's the exact error:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
OKAY [ 0.447s]
finished. total time: 0.693s
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.541s]
writing 'radio'...
OKAY [ 3.086s]
finished. total time: 4.629s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.885s]
sending 'system' (842656 KB)...
OKAY [ 26.533s]
writing 'system'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 84.341s
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
error: file_write: write: No space left on device
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.507s]
sending 'cache' (2136 KB)...
OKAY [ 0.180s]
writing 'cache'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.969s
rebooting...
finished. total time: 0.003s
---------------------------------------------
Now when I boot up my phone it goes into the black screen with 'Google' on it then it turns off for a second then back to the Google screen and then it boots into custom recover (TWRP). What can I do to fix this? Thanks in advance.
Manually flash the ROM in fastboot.
audit13 said:
Manually flash the ROM in fastboot.
Click to expand...
Click to collapse
Is it possible to do that without wiping my data?
Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.
audit13 said:
Yes, just don't flash userdata.img or wipe.
Before flashing, you might want to use twrp to back up data or copy files to your computer, then flash.
Click to expand...
Click to collapse
Thanks! Hopefully this works. I've never done anything with fastboot though. I'll look it up later.
I have not used kits to flash stock rom, I always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Much appreciated! I think I'll start learning how to do things manually now. Thanks again.
audit13 said:
I have not used kits to flash stock rom, I'm always do it manually to learn the process.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Thanks for everything! Everything is okay now.
Yesterday I flashed the NMF26U factory image on my Pixel using flash-all. I didn't remove the '-w' because I wanted a clean install. I saved the terminal output and there are several things that have me quite concerned even though my phone appears to be working fine.
Note the two places where it says "FAILED". Am I in trouble but don't know it yet?
Code:
E:\MobileDevices\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.154s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 16.255s]
finished. total time: 17.410s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.919s]
writing 'radio'...
OKAY [ 1.092s]
finished. total time: 3.026s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
--------------------------------------------
Bootloader Version...: 8996-012001-1611091517
Baseband Version.....: 8996-012511-1611190200
Serial Number........: FA6C10300677
--------------------------------------------
checking product...
OKAY [ 0.047s]
checking version-bootloader...
OKAY [ 0.031s]
checking version-baseband...
OKAY [ 0.047s]
sending 'boot' (24821 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) Flashing active slot "_a"
OKAY [ 0.655s]
sending sparse 'system' (516459 KB)...
OKAY [ 18.018s]
writing 'system'...
OKAY [ 6.802s]
sending sparse 'system' (520631 KB)...
OKAY [ 18.470s]
writing 'system'...
OKAY [ 10.998s]
sending sparse 'system' (517487 KB)...
OKAY [ 18.096s]
writing 'system'...
OKAY [ 7.597s]
sending 'vendor' (235186 KB)...
OKAY [ 7.956s]
writing 'vendor'...
OKAY [ 6.599s]
erasing 'userdata'...
OKAY [ 6.848s]
sending 'userdata' (138957 KB)...
OKAY [ 4.696s]
writing 'userdata'...
OKAY [ 1.342s]
erasing 'cache'...
(bootloader) Erasing active slot "_a"
FAILED (remote: Partition table doesn't exist
)
finished. total time: 109.403s
Press any key to exit...
because flash all is bat file, it contains many items which maybe not included in the factory image to be fashed.
Almost, I got same information.
by the way, how can we save or input the flash all results. I am on windows
bush911 said:
by the way, how can we save or input the flash all results. I am on windows
Click to expand...
Click to collapse
Right click the menu bar in the command box and select edit then 'selec all's. Right click again, edit then copy. Paste it into a document.
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Your fastboot binary is out of date. Make sure you're using the latest version.
wbxp99 said:
Your fastboot binary is out of date. Make sure you're using the latest version.
Click to expand...
Click to collapse
Thank you! It's nice to receive a definitive answer on this. I flashed again with the latest fastboot version and the log output is very different from the first time. I am confident now that everything is in its proper place.
pstgh said:
I had to re-flash back to 7.1.0, then upon setting up the phone, it began taking the OTA 7.1.1 update, which is fine. Now that the phone is unlocked and updated, what is the best method to gain root access from this point? boot-to-root or install the latest SU or ?? Thanks.
Click to expand...
Click to collapse
This a thread about fastboot error messages. There are guide in the SU and TWRP threads. Very easy I don't personally think you need anything like boot to root. Just follow the instructions and make sure you use TWRP RC1 and SU 2.79 SR 2