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.
Related
Hi all,
I just completely bricked my One
I wanted update my AOKPk to the newer version, but some of the apps always failed... so I decided to wipe One completely and install everything from scratch...
So made backup, took off SIM card and went to the TWRP and did:
- dalvik cache
- system
- data
- internal storage
- cache
and install this:
- aokpk_bacon_kitkat_daily_1409231727.zip
- pa_gapps-modular-pico-4.4.4-20140923-signed.zip
- pa_gapps_playservices-games_update_20140923-signed.zip
but I was not able to download any app from GappStore... I tried all 3 guides I googled, but nothing helped...
So wipe one more time:
- dalvik cache
- system
- data
- internal storage
- cache
+ Factory reset (in TWRP)
+ Format data
Installed:
- aokpk_bacon_kitkat_daily_1409231727.zip
- pa_gapps-modular-pico-4.4.4-20140923-signed.zip
- pa_gapps_playservices-games_update_20140923-signed.zip
and then when One boot up to "Welcome ... set your language" it reset... and boot again to Welcome... and reset... never ending reset loop...
So wipe One again:
- dalvik cache
- system
- data
- internal storage
- cache
+ Factory reset (in TWRP)
and install SlimKat:
- Slim-bacon-4.4.4.build.8.0-WEEKLY-6972.zip
- Slim_mini_gapps.BETA.4.4.4.build.8.x-289.zip
and again when One boot up to "Welcome ... set your language" it reset... and boot again to Welcome... and reset... never ending reset loop...
So wipe One again:
- dalvik cache
- system
- data
- internal storage
- cache
And went to the fastboot and tried to insert boot.img there... but...
d:\aaa>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.170s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.180s
The "Device not unlocked" was quite surprise, as I already had CM11s > CM11 > SlimKat > AOKPk and all of them works OK
So I ran command:
d:\aaa>fastboot oem unlock
...
OKAY [ -0.000s]
finished. total time: -0.000s
but One restarted to the TWRP only... and when I went back to the fastboot I ended up with same "Device not unlocked" message
So, now I have One with CM11s (cm-11-20140924-NIGHTLY-bacon.zip) installed via TWPR, but once it boot up and Welcome screen with languages appeared it reset and boot up and reset and .... :crying:
Please please please help...
Just now I tried the guide from here: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Unziped the cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip, to the same folder as I have the OPO_64GB.zip tool...
and here is output...
d:\aaa>flash-all.bat
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.778s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.031s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.016s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.296s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.296s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.016s]
sending 'boot' (5560 KB)...
OKAY [ 0.172s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.187s
Press any key to exit...
Sounds like you have a locked BL. Lots of people have been experiencing problems with there one after the OTA update. Corrupted bootloaders/device locking its BL again. Try this out and see if it works (If you can get into fastboot, which you never stated in the second post) http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
Thank you very much...
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So, I am in the status: 2) Unlock Bit - FALSE , Tamper Bit - TRUE
But when I run: fastboot oem unlock
One reset to the TWRP, exactly it is described in the here: http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
But I dont understand how to unlock it... this not make any sence to me
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) lock / unlock bit
2) tamper bit
edit 1: I tried this... but...
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.007s
djha53k said:
Thank you very much...
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So, I am in the status: 2) Unlock Bit - FALSE , Tamper Bit - TRUE
But when I run: fastboot oem unlock
One reset to the TWRP, exactly it is described in the here: http://forum.xda-developers.com/oneplus-one/help/oneplus-one-unable-to-unlock-bootloader-t2845626
But I dont understand how to unlock it... this not make any sence to me
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) lock / unlock bit
2) tamper bit
edit 1: I tried this... but...
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
creating boot image...
creating boot image - 4096 bytes
downloading 'boot.img'...
OKAY [ 0.004s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.007s
Click to expand...
Click to collapse
Can't really help except when I purchased my phone as a used device I had the problem with google play store, wouldn't sign in or anything.Wiped and factory reset did nothing to help so I just went to the rooting guide and started from scratch. Once I had completed the guide all was good. Make sure your not using 2.8.x TWRP only 2.7.x.
Yes, I have TWRP 2.8.0.1 installed, but I am not able to downgrade it...
Even when I use any tool ... I got...
target reported max download size of 536870912 bytes
sending 'recovery' (15294 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.487s
so, I am completely f*c* :crying:
edit: so I tried to lock and then unlock... nothing
Code:
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.006s
d:\aaa>fastboot.exe boot recovery.img
downloading 'boot.img'...
OKAY [ 0.236s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.239s
d:\aaa>fastboot.exe oem lock
...
OKAY [ 0.002s]
finished. total time: 0.002s
d:\aaa>
d:\aaa>
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
d:\aaa>fastboot.exe oem unlock
...
OKAY [ 0.013s]
finished. total time: 0.013s
djha53k said:
Yes, I have TWRP 2.8.0.1 installed, but I am not able to downgrade it...
Even when I use any tool ... I got...
target reported max download size of 536870912 bytes
sending 'recovery' (15294 KB)...
OKAY [ 0.484s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.487s
so, I am completely f*c* :crying:
edit: so I tried to lock and then unlock... nothing
Code:
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.006s
d:\aaa>fastboot.exe boot recovery.img
downloading 'boot.img'...
OKAY [ 0.236s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.239s
d:\aaa>fastboot.exe oem lock
...
OKAY [ 0.002s]
finished. total time: 0.002s
d:\aaa>
d:\aaa>
d:\aaa>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
d:\aaa>fastboot.exe oem unlock
...
OKAY [ 0.013s]
finished. total time: 0.013s
Click to expand...
Click to collapse
i would recommend to flash CM with fastboot again:
<http>://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
[B]fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot[/B]
everything should be fine and you should have an unlocked bootloader and twrp. ofc it'll wipe _anything_ on your device
kemals said:
i would recommend to flash CM with fastboot again:
<http>://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
[B]fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot reboot[/B]
everything should be fine and you should have an unlocked bootloader and twrp. ofc it'll wipe _anything_ on your device
Click to expand...
Click to collapse
Hello,
thank you... but...
I have the cm-11.0-XNPH33R-bacon-signed-fastboot.zip file already and tried it to install...
Anyway here is new try...
File "cm-11.0-XNPH33R-bacon-signed-fastboot.zip" unziped to the d:\aa folder, and the "AndroidSDKSlim.zip" unziped to the same folder
Code:
d:\aa>fastboot devices
c9a88403 fastboot
d:\aa>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.180s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.180s
Or have I done it wrong way??? After 20 hours trying I am desperate... :crying:
edit: I red this topic "http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912" but I tried many time, but anything worked...
Please can you provide exact command sequence? Maybe I really dont understand how to perform it completlly
First thing you have to do is unlock the bootloader again, but this will wipe the phone
fastboot oem unlock
Once that's done, you'll then be able to flash a new ROM
EDIT: Seems you've tried that so you could have a corrupt partition somewhere due to all the stuff you've done to now. I think it happens as it factory resets the unit using the stock recovery and as you have TWRP it can't carry out the process...
did you tried to flash the boot.img like "fastboot -c flash boot boot.img"? the -c is for override the kernel (i think the kernel is in the "boot.img" but not sure so check where is the kernel and the do it with the right file name)
djha53k said:
d:\aaa>fastboot.exe boot OnePlusOne-OnlyBootloaderToggle.zip
Click to expand...
Click to collapse
LOL! That's the script you need in order to unlock your bootloader again...but you don't have to boot it!
You just must flash it via recovery...
First of all wiping internal is a horrible idea. Never do that. That's the worst thing you can do.
Now please tell me do you have the persist block?
It is located in dev/block/platform/msm_sdcc.1/by name?
If you don't then see my help thread http://forum.xda-developers.com/showthread.php?p=55488755
markbencze said:
First of all wiping internal is a horrible idea. Never do that. That's the worst thing you can do.
Now please tell me do you have the persist block?
It is located in dev/block/platform/msm_sdcc.1/by name?
If you don't then see my help thread http://forum.xda-developers.com/showthread.php?p=55488755
Click to expand...
Click to collapse
OK, thank you for advice... I will never do it again...
Anyway... finally I the unlock worked...
Code:
d:\a>adb push OnePlusOne-BootUnlocker.zip /sdcard
68 KB/s (2182 bytes in 0.031s)
d:\a>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Stock CM11s installed:
Code:
d:\a>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
OKAY [ 0.889s]
finished. total time: 2.668s
d:\a>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.000s]
finished. total time: 0.016s
d:\a>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.031s
d:\a>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ -0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.016s
d:\a>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.312s]
writing 'LOGO'...
OKAY [ 0.156s]
finished. total time: 0.468s
d:\a>fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5560 KB)...
OKAY [ 0.187s]
writing 'boot'...
OKAY [ 0.094s]
sending 'recovery' (7412 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.125s]
erasing 'system'...
OKAY [ 0.047s]
sending sparse 'system' (523960 KB)...
OKAY [ 17.956s]
writing 'system'...
OKAY [ 25.428s]
sending sparse 'system' (250580 KB)...
OKAY [ 8.424s]
writing 'system'...
OKAY [ 8.642s]
erasing 'userdata'...
OKAY [ 2.246s]
formatting 'userdata' partition...
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
sending 'userdata' (141075 KB)...
writing 'userdata'...
OKAY [ 18.876s]
erasing 'cache'...
OKAY [ 0.031s]
formatting 'cache' partition...
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
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.827s]
rebooting...
finished. total time: 83.148s
But my troubles does not ends
When CM11s boot up, at least I dont have repeating restarts... but now I see this:
Code:
Unfortunately, AudioFX has stopped...
On background is Welcome... choose language...
But AudioFX failure popup is on the top and I did click on it about 20 times, but it is still re-appearing :crying:
I cannot move anywhere... just shutdown One by long holding power button
djha53k said:
OK, thank you for advice... I will never do it again...
Anyway... finally I the unlock worked...
Code:
d:\a>adb push OnePlusOne-BootUnlocker.zip /sdcard
68 KB/s (2182 bytes in 0.031s)
d:\a>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Stock CM11s installed:
Code:
d:\a>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.778s]
writing 'modem'...
OKAY [ 0.889s]
finished. total time: 2.668s
d:\a>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.000s]
finished. total time: 0.016s
d:\a>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.031s
d:\a>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ -0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
d:\a>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.016s
d:\a>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.312s]
writing 'LOGO'...
OKAY [ 0.156s]
finished. total time: 0.468s
d:\a>fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9a88403
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5560 KB)...
OKAY [ 0.187s]
writing 'boot'...
OKAY [ 0.094s]
sending 'recovery' (7412 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.125s]
erasing 'system'...
OKAY [ 0.047s]
sending sparse 'system' (523960 KB)...
OKAY [ 17.956s]
writing 'system'...
OKAY [ 25.428s]
sending sparse 'system' (250580 KB)...
OKAY [ 8.424s]
writing 'system'...
OKAY [ 8.642s]
erasing 'userdata'...
OKAY [ 2.246s]
formatting 'userdata' partition...
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
sending 'userdata' (141075 KB)...
writing 'userdata'...
OKAY [ 18.876s]
erasing 'cache'...
OKAY [ 0.031s]
formatting 'cache' partition...
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
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.827s]
rebooting...
finished. total time: 83.148s
But my troubles does not ends
When CM11s boot up, at least I dont have repeating restarts... but now I see this:
Code:
Unfortunately, AudioFX has stopped...
On background is Welcome... choose language...
But AudioFX failure popup is on the top and I did click on it about 20 times, but it is still re-appearing :crying:
I cannot move anywhere... just shutdown One by long holding power button
Click to expand...
Click to collapse
yep you wiped your persist block.
go to my thread and fix it and stop flashing before extensive reading!
and i forbid you from wiping internal again
Uff too late... after 24 hours trying... I was so happy that it works... so I already did this...
d:\a>fastboot boot TWRP-2.7.1.0.img
downloading 'boot.img'...
OKAY [ 0.484s]
booting...
OKAY [ 0.016s]
finished. total time: 0.499s
d:\a>adb push Slim-bacon-4.4.4.build.8.0-WEEKLY-6972.zip /sdcard
5046 KB/s (165353599 bytes in 31.995s)
d:\a>adb push Slim_mini_gapps.BETA.4.4.4.build.8.x-289.zip /sdcard
5343 KB/s (61713022 bytes in 11.278s)
d:\a>adb push SuperSU-v2.02.zip /sdcard
5260 KB/s (1260473 bytes in 0.234s)
Click to expand...
Click to collapse
and I am in the never ending restarts again, aaaaaaaaa :crying:
edit: OK, so back to CM11s 33R.. with failed AudioFX... gonna read your post how to fix this...
After 24hour trying to make One works again... I will be happy with any ROM, fully working...
So, I reinstall CM11s 33R again and I have AudioFX failing error msg again...
I downloaded:
- NEVER_SETTLE_lite_fix.zip
- ONEPLUS_ONE_Nightmare_fix.zip
I am in the Fastboot Mode now, then I supposed to do:
- fastboot erase persist
- fastboot flash persist persist.img
- fastboot erase reserve4
- fastboot flash reserve4 reserve4.img
But I have no idea how to perform this:
open terminal --- which terminal?? I have W7 on my PC, so currently I accessing One by cmd
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Or flash persist.img and reserve4.img fix the issue?
I am sorry, but after 24 hour "fixing" this... Iam dead
djha53k said:
So, I reinstall CM11s 33R again and I have AudioFX failing error msg again...
I downloaded:
- NEVER_SETTLE_lite_fix.zip
- ONEPLUS_ONE_Nightmare_fix.zip
I am in the Fastboot Mode now, then I supposed to do:
- fastboot erase persist
- fastboot flash persist persist.img
- fastboot erase reserve4
- fastboot flash reserve4 reserve4.img
But I have no idea how to perform this:
open terminal --- which terminal?? I have W7 on my PC, so currently I accessing One by cmd
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Or flash persist.img and reserve4.img fix the issue?
I am sorry, but after 24 hour "fixing" this... Iam dead
Click to expand...
Click to collapse
you need to enter those commands with your device in fastboot mode (the .img files)
once you are up and running do the efs backup.
OK, thank you very much for advice...
Done now:
d:\a>fastboot erase persist
erasing 'persist'...
OKAY [ 0.031s]
finished. total time: 0.031s
d:\a> fastboot flash persist persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.140s]
writing 'persist'...
OKAY [ 0.265s]
finished. total time: 0.406s
d:\a>fastboot erase reserve4
erasing 'reserve4'...
OKAY [ 1.622s]
finished. total time: 1.622s
d:\a> fastboot flash reserve4 reserve4.img
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.172s]
writing 'reserve4'...
OKAY [ 0.234s]
finished. total time: 0.406s
Click to expand...
Click to collapse
and I am going to google what is the "efs backup" and how to do it
Before I will boot up CM11s 33R
edit: hmm, so as per google results I have to install TWRP and then make backup in the TWRP...
but I dont have TWRP yet, as I am on fully stock CM11s ROM...
So should I flash TWRP and then make backup??
edit 1: so as the TWRP scr*w it up last time, should I use the CWM Recovery instead???
edit final: successfully installed TWRP, made backup
successufully boot to CM11s 33R... no repeating restart... no AudioFX stopped working..
jupiiiiiiiiiiiiii, Thank you very much...
djha53k said:
OK, thank you very much for advice...
Done now:
and I am going to google what is the "efs backup" and how to do it
Before I will boot up CM11s 33R
edit: hmm, so as per google results I have to install TWRP and then make backup in the TWRP...
but I dont have TWRP yet, as I am on fully stock CM11s ROM...
So should I flash TWRP and then make backup??
edit 1: so as the TWRP scr*w it up last time, should I use the CWM Recovery instead???
edit final: successfully installed TWRP, made backup
successufully boot to CM11s 33R... no repeating restart... no AudioFX stopped working..
jupiiiiiiiiiiiiii, Thank you very much...
Click to expand...
Click to collapse
Happy days, I will tread carefully with my one before its a 1-1=0
Ohh yeah... but...
As I had SlimKat and AOKPk before... I have to say the CM11s is quite (how to say it) "poor" :angel:
Also strange is that there are only two folders on the SDCARD: Android and TWRP... that´s it... nothing else
Apex laucher configured... backuped files copied back to One...
Gonna restore app data via TitaniumBackup... and hopefully it will works for sometime again...
I have done with flashing other ROMs for sometime... :good:
Hi guys,
I woke up to find my Nexus off, still plugged in, which was strange. When i tried to turn it on, the Google Logo appeared, then the 4 Dots as per Marshmallow Boot animation...only they remained there 35 mins after I attempted to put on the phone.
I figured something was up with the boot, so I left it for a while after restarting, but and it was still stuck.
Since then I've tried reloading Stock Roms, (From KitKat to Marshmallow), installing custom recovery and trying anything I could find online to try to get this to work, but sadly I haven't been able to.
If i try to Reset, I get failed messages on some partitions.
I'll attach some logs showing the messages from some of these attempts.
Can anyone assist or help diagnose?
Attempt at Flashing KitKat with Nexus Root Toolkit
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.285s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
rebooting into bootloader...
OKAY [ 0.129s]
finished. total time: 0.130s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.627s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.854s
rebooting into bootloader...
OKAY [ 0.119s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
sending 'boot' (8700 KB)...
OKAY [ 0.494s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.230s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.211s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
target reported max download size of 1073741824 bytes
sending 'recovery' (9284 KB)...
OKAY [ 0.504s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.687s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.115s
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.186s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.214s
rebooting...
finished. total time: 0.003s
If you require more information, ask and I will provide where I can.
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Terfysgol said:
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Yup, I tried flashing Stock Roms aka Factory Images for KitKat, Lollipop and Marshmallow as indicated in my original post.
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
audit13 said:
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
Click to expand...
Click to collapse
I did, and this also produces the Fails as before.
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
audit13 said:
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
Click to expand...
Click to collapse
I'm beginning to think this may be the case
Have you got an old nandroid that you know that works?
Inviato dal mio P6000 Pro utilizzando Tapatalk
I had similar issue but at least I could boot into bootloader to do this :
http://forum.xda-developers.com/showthread.php?t=2513701
I had the failed also then went to step 2 and did that:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
*tip* Substitute lastest images by dragging and dropping them into cmd window, tip** hit arrow up on keypad to enter in last text to save a bunch of typing
It took FOREVER to boot but it did come back. BUT I have weird fc's and rando0m turn offs so I suspect new phone is coming.
I did phone the google and they connected me with LG for a repair option which will come back in max 9 days but I think even 100 bucks or whatever the cost ( they will phone with tally ) is more than the phone is worth.
Read the whole of the link I sent and Thank abaaaabbbb63 for his work
YMMV HTH
Zo0
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
please, help
nexus 5 turn on, but no UNBRIK
i try NRT, UNIFIELD , flashtools ( no conect )
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.210s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.416s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.562s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.792s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.411s]
writing 'boot'...
OKAY [ 0.764s]
finished. total time: 1.176s
target reported max download size of 1073741824 bytes
sending 'recovery' (10014 KB)...
OKAY [ 0.429s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.615s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 36.369s
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
see images in link
http://imgur.com/a/kX1YE
Is the bootloader unlocked? If yes, relock the bootloader, and reboot the phone back into download mode. If the bootloader is unlocked again, the memory chip is damaged and can be fixed with a motherboard replacement.
Have you tried flashing a stock KK ROM?
audit13 said:
Is the bootloader unlocked? If yes, relock the bootloader, and reboot the phone back into download mode. If the bootloader is unlocked again, the memory chip is damaged and can be fixed with a motherboard replacement.
Have you tried flashing a stock KK ROM?
Click to expand...
Click to collapse
how to enter download mode ? only bootlooader lock enter ??
Download or fastboot mode is the screen where you unlock or relock the bootloader.