Okay i have an A1-830 & was installing a game, made a couple of modifications & now i have a soft bricked device.
I was installing Gangstar Rio & made some changes to try & get it to run as the minimum specs, my device had to run it but @ 1st it stated that the license was invalid so i changed the date backa year on advice from someone & it worked but then it stated that the device was incompatible, so i researched & found that was happening to most with devices that should have ran it but someone had advised to make some change to the 'batch.prop' file to fool the game to think it was a different device. I may have accidentally changed something in the batch file that caused this. i can't be certain but yeh, when i rebooted my tablet it got stuck @ the Acer logo in bootloop.
I tried recovery & did a factory reset & it acted like it was working but when i rebooted my device it still bootlooped. I then did some research & i tried to flash the stock rom but got errors each time i tried. i'll list the errors below;
i started off trying to flash the 'system.gz' file as follows;
>fastboot flash system Acer_AV052_A1-830_1.014.00_WW_GEN1.system.img.gz
> target reported max download size of 614470997 bytes
Invalid sparse file format at header magi
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
sending sparse 'system' (600068 KB)
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
OKAY [ 68.091s]
writing 'system' . . .
FAILED (remote: flash_cmds error!)
>fastboot flash system Acer_AV052_A1-830_1.014.00_WW_GEN1.system.img
> target reported max download size of 614470997 bytes
Invalid sparse file format at header magi
sending sparse 'system' (585989 KB) . . .
OKAY [ 61.418s]
writing 'system' . . .
FAILED (remote: flash_cmds error!)
.................and these were the bootloader errors that appeared;
E: Unknown chunk type
failed: no such file or directory
E: flash system failed
FLASH FAILED!
--------------------------------------------------------------------------
these are my build & region details too;
region: Australia (South East Asia)
build #: ' Acer_AV0K0_A1-830_1.007.00_WW_GEN1
------------------------------------------------------------------------------
so that is where i am stuck @, i even made sure that i had the correct 'Java Development Tool Package' & 'Android Studio' was complete but everything else is out of my depth of knowledge. Any help will be 10 fold appreciated in advance...... :good:
acer a1-830
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz
trinky13 said:
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz
Click to expand...
Click to collapse
finally sorted it out.... it was simply the order that i was doing it in.... was basically flashing it backwards, hence causing the errors i was getting, arrrrrgh..... but @ least sorted, thanks a heap trinky for advising of the order @ the bottom of ur post!
KENTzee said:
finally sorted it out.... it was simply the order that i was doing it in.... was basically flashing it backwards, hence causing the errors i was getting, arrrrrgh..... but @ least sorted, thanks a heap trinky for advising of the order @ the bottom of ur post!
Click to expand...
Click to collapse
can you share how did you solved it? i'm also stuck in bootloop acer iconia a1-830, trying to find stock firmwares and flash it.
thanks...:crying:
trinky13 said:
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz
Click to expand...
Click to collapse
Still getting these errors even I follow your instruction.
target reported max download size of 614886058 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
sending sparse 'system' (600472 KB)...
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
OKAY [ 68.063s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 81.760s
I also have a problem along the same lines, I have a feeling I'm getting closer to solving it, but I can't seem to get it to boot.
It all seems to go well..
Code:
sending 'boot' (7591 KB)...
OKAY [ 0.886s]
writing 'boot'...
OKAY [ 0.919s]
finished. total time: 1.810s
sending 'fastboot' (9893 KB)...
OKAY [ 1.309s]
writing 'fastboot'...
OKAY [ 1.016s]
finished. total time: 2.332s
sending 'recovery' (9227 KB)...
OKAY [ 0.996s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.979s
sending 'system' (797732 KB)...
OKAY [ 51.121s]
writing 'system'...
OKAY [ 70.428s]
finished. total time: 121.554s
Then I try to start the tablet but just get a quick flash of the USB symbol and nothing else. I've tried various things but I'm not sure if I'm missing something here or not. Can anyone suggest anything? This is driving me crazy.
darkfilth101 said:
can you share how did you solved it? i'm also stuck in bootloop acer iconia a1-830, trying to find stock firmwares and flash it.
thanks...:crying:
Click to expand...
Click to collapse
http://www.mediafire.com/download/dxyx2q9ef4p8n17/SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
here you go buddy
Hi RAZERZDAHACKER, how can I flash this zip?
all tutorials are about img files, but there are folders on zip
---------- Post added at 04:42 PM ---------- Previous post was at 04:24 PM ----------
nevermind, so easy, "apply update from external storage"
but I got error
Code:
E:end of footer from /tmp/sideload/package.zip not 0xFFFF (File exists)
E:signature verification failed
tictacbum said:
Hi RAZERZDAHACKER, how can I flash this zip?
all tutorials are about img files, but there are folders on zip
Click to expand...
Click to collapse
Download this to your computer and unzip it. Don't unzip the system folder in the zip file. Open fastboot and do fastboot flash boot (the boot img) then once that's done, do fastboot flash fastboot (fastboot img) then do fastboot flash recovery (recovery img) and then do fastboot reboot-bootloader. Then do fastboot flash system (system img.gz). Then on the tablet using the volume keys and the power button, go to recovery and wipe data then reboot, now it should be done!
---------- Post added at 05:42 PM ---------- Previous post was at 04:47 PM ----------
p0st3r^ said:
I also have a problem along the same lines, I have a feeling I'm getting closer to solving it, but I can't seem to get it to boot.
It all seems to go well..
Code:
sending 'boot' (7591 KB)...
OKAY [ 0.886s]
writing 'boot'...
OKAY [ 0.919s]
finished. total time: 1.810s
sending 'fastboot' (9893 KB)...
OKAY [ 1.309s]
writing 'fastboot'...
OKAY [ 1.016s]
finished. total time: 2.332s
sending 'recovery' (9227 KB)...
OKAY [ 0.996s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.979s
sending 'system' (797732 KB)...
OKAY [ 51.121s]
writing 'system'...
OKAY [ 70.428s]
finished. total time: 121.554s
Then I try to start the tablet but just get a quick flash of the USB symbol and nothing else. I've tried various things but I'm not sure if I'm missing something here or not. Can anyone suggest anything? This is driving me crazy.
Click to expand...
Click to collapse
I am not sure but by now you must have probably fixed it but try to boot into recovery and wipe data and reboot. That usually fixes bootloops upon flashing stock roms *ehum*samsung*ehum*, never the less, it also worked for me in my acer and I am back and running!
big thanks! tablet is booting fine again
tictacbum said:
big thanks! tablet is booting fine again
Click to expand...
Click to collapse
YAAAAAAAAAAAAY!!! Ah, I remember when I was stuck in a bootloop (and was a noob at android) so I took it down to the shop and they gave me a new one, then it happend again and I got another one for free! But as always, I'm so glad it worked!
I'm also having the FAILED (remote: flash_cmds error!) error. I have tried to do the steps in the specified order in the comments and I still get the error.
Can anyone help me?
ricardodeus said:
I'm also having the FAILED (remote: flash_cmds error!) error. I have tried to do the steps in the specified order in the comments and I still get the error.
Can anyone help me?
Click to expand...
Click to collapse
Reboot droidboot and try flashing the 4.2.2 image, also, try flashing in this order (boot, fastboot, recovery, system).
Hit thanks if I helped.
RAZERZDAHACKER said:
Reboot droidboot and try flashing the 4.2.2 image, also, try flashing in this order (boot, fastboot, recovery, system).
Hit thanks if I helped.
Click to expand...
Click to collapse
Is the 4.2.2 image the Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG version?
If so, I got the exact same error.
ricardodeus said:
Is the 4.2.2 image the Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG version?
If so, I got the exact same error.
Click to expand...
Click to collapse
Nope that's KitKat, 14 is 4.2.2
RAZERZDAHACKER said:
Nope that's KitKat, 14 is 4.2.2
Click to expand...
Click to collapse
I first tried Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG, then Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG and got the same error for both.
target reported max download size of 614541994 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
sending sparse 'system' (600136 KB)...
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
OKAY [ 64.487s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 78.156s
ricardodeus said:
I first tried Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG, then Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG and got the same error for both.
target reported max download size of 614541994 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
sending sparse 'system' (600136 KB)...
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
OKAY [ 64.487s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 78.156s
Click to expand...
Click to collapse
Have you wiped data? Also, reboot droidboot and make sure fastboot recognizes the device. Maybe you can try adb pushing the files via fastboot oem startftm command.
Delete this
a1 830 no droid boot
ramiabouzahra said:
Delete this
Click to expand...
Click to collapse
help me guys my a1-830 no droid boot or recovery hang on logo only do you have solutions
rolly20 said:
help me guys my a1-830 no droid boot or recovery hang on logo only do you have solutions
Click to expand...
Click to collapse
How are you trying to access droidboot? You can't hang on logo if you don't have droidboot (it's the bootloader mate).
Related
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.
Hi folks,
Here is a resumé of what i've tried so far
Actual symptoms : Cyanogenmod logo with animation looping (no bootloop)
I've access to fastboot and philz recovery (but errors are shown, see below)
I've got the phone as it is, no idea of what the previous owner has done.
Can someone help me ?
I tried to unbrick using various methods :
ColosOS : device is displayed as FORGE HS-USB QDLOader 9008 or Qualcomm HS-USB QDLOader 9008
OPO recovery tool 1.1 : connected to com5, 8974_msimage.mbn: OK
that's the only thing shown, then the OPO vibrates and nothing happen
Flash zip bacon 33R and 44S via OTG => error status 7
Code:
Installing : /storage/usbdisk/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
E: Can't mount /cache/recovery/last_install
E: faile to open last_install : File exists
Finding update package
Opening update Package
Installation update
Installation aborted
Code:
[U]Errors when booting Philz Recovery :[/U]
E: could not mount /data to setup /data/media path!
E: Can 't mount /cache/recovery/command
E: Can 't mount /cache/recovery/log
E: Can 't open /cache/recovery/log
E: Cannon mount path for settings file :/data/philz-touch/phils-touch6.ini
E: Can 't mount /cache/recovery/last_log
E: Can 't open /cache/recovery/log
E: Can 't mount /cache/recovery/last_install
E: Can 't open /cache/recovery/last_install
[U]Logs :[/U]
W; failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 (File exists)
mount : mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed : Invalid argument
Code:
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.008s
OnePlus One ZIP with 3 bats and fastboot :
Code:
######### This patch is Created by ONEPLUS Technical Support. #######
###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ####
#
...
OKAY [ 0.003s]
finished. total time: 0.003s
erasing 'persist'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.138s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.221s
erasing 'reserve4'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.167s]
writing 'reserve4'...
FAILED (remote: flash write failure)
finished. total time: 5.251s
target reported max download size of 536870912 bytes
sending 'boot' (5578 KB)...
OKAY [ 0.181s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.232s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'recovery' (7510 KB)...
OKAY [ 0.243s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.295s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.800s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.851s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.056s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.062s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.308s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.361s
rebooting...
finished. total time: 0.005s
It is done Now :)
Appuyez sur une touche pour continuer...
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
Click to expand...
Click to collapse
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
Click to expand...
Click to collapse
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Seems the guy you buy the phone has relock bootloader
In kitkat that was problem ....
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Status 7 message is due to improper twrp recovery..... flash the latest.... and unlock the bootloader once again.... may be that will help.
Really want to help u.... because, once i had bricked my device and lost efs also, and I know how bad it feels .... but thanks to my backups, i was saved...
#HappyFlashing#
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Qiou said:
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Click to expand...
Click to collapse
im having this exact problem... anyone managed to find a fix? Even putting it back to stock doesn't work!
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!
Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Coolpente said:
Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Click to expand...
Click to collapse
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
enzyne said:
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
Click to expand...
Click to collapse
I did the new platform tools and it worked. I was not capable of using another cable since I dont have an adapter for the c to c.
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot
dattaway said:
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot
Click to expand...
Click to collapse
Are you flashing the proper factory image? Have you tried re downloading?
enzyne said:
Are you flashing the proper factory image? Have you tried re downloading?
Click to expand...
Click to collapse
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
dattaway said:
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
Click to expand...
Click to collapse
I just wanted to make sure there wasn't any data corruption. The most recent one which was .19 should do the trick if that's not working and you've tried everything else it may be time to do an RMA.
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Rookx said:
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Click to expand...
Click to collapse
What your talking about is the android stock recovery not the bootloader.
Hello, it seems i have bricked my phone. The model is FRD-L09C432. I've been trying to restore it to stock but to no avail. I've tried flashing various build numbers via the Unbrick funtion of Huawei Multi Tool, but it always gave an error when it was flashing cust.img and system.img, reporting that I'm trying to flash the wrong image. I've also tried the 2-step method in which you load a rollback package in the sdcard and then try to flash the old firmware, but that also doesn't work as when I am in the first step of the progress, trying to install the rollback package, the installer stops immediately at 5% reporting that the installation failed as the update package does not exist.
I wonder if this is an error with the SD card - maybe the phone can't read it properly. What should the SD card be formatted to? Right now, it's a single FAT partition.
Any ideas or tips are welcome.
Edit: when I try to unbrick with HMT i always get something like this:
Code:
13:43:35: Unbricking started. Your computer may freezes during the process.
13:43:35: flash boot "C:\Users\svart\Desktop\unbrick\boot.img"
13:43:37: The Boot image is flashing successfully
13:43:37: flash system "C:\Users\svart\Desktop\unbrick\system.img"
13:45:28: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 16.234s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 16.281s
13:45:28: Error#1
13:45:28: flash cust "C:\Users\svart\Desktop\unbrick\cust.img"
13:45:45: Error! You are trying to flash the wrong image!
13:45:45: flash recovery "C:\Users\svart\Desktop\unbrick\recovery.img"
13:45:48: The Recovery image is flashing successfully
13:45:48: flash userdata "C:\Users\svart\Desktop\unbrick\userdata.img"
13:45:55: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.468s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 2.000s]
finished. total time: 5.469s
13:45:56: Error#1
13:45:56: Completed
13:45:56: Something went wrong (((
I solved it. There was a problem with the SD card that's why it wasn't doing the rollback I think. I found the correct rom (B360 from here) which I flashed with HMT.