SOLVED: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851/post57916281#post57916281
The story goes, I was trying to flash CM11S after trying out the Oneplus One Lollipop Alpha. Part way through the process the command line was waiting for the device to reboot into fastboot and it never did.
Command Prompt Log:
Code:
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.770s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.613s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.004s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.016s
sending 'dbi' (11 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
sending 'aboot' (376 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 3.521s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.028s]
finished. total time: 0.037s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.012s]
writing 'tz'...
OKAY [ 0.015s]
finished. total time: 0.028s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
OKAY [ 0.162s]
finished. total time: 0.468s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
Now the device is entirely unresponsive aside from a vibration when I hold down the volume and power keys. Screen stays black too and my computer will not detect my device. The Device is recognized by MSM8974 Downloader as well, but every time I select it to repair it it fails. The device also happens to be recognized by QPST Configuration software.
MSM8974 Downloader Log
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
More Information:
Storage Capacity: 64GB
PC OS: Windows 8.1
Windows Driver Signature Verification Status: OFF
Device Drivers: PDANet Android Drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers.
Hello.
Same problem here. I just tried to reflash another roll since i was trying to rollback from Lollipop alpha. I did some changes in TWRP and after reboot my device did not start at all. There is only a vibration when I try to turn it on. Charging is also disabled. Screen is blank and unresponsive. Both recovery and bootloader dont work. I tried to turn my opo while connected to PC and I can hear that system found a new device. But there is no popup window, just the sound. Even after unplugging the sound can be heard.
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
TheManDroid said:
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
Click to expand...
Click to collapse
Been there done that. Nothing came of it, hence my logs posted above. Also I wouldn't be posting about it if I had found a solution
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
I have the same problem. I suspect it's due to the differences in the partition tables between the ROMs. For example, the logo.bin for the CM11S image is around 9MB, whereas it is 512KB in the OnePlus ROM.
Hope we can get this fixed.
TheManDroid said:
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
Click to expand...
Click to collapse
Sorry if I came off harsh in my previous post. That was not my intention. As for senior member, it means nothing other than I have been here a while (around the block so to speak), and I am very glad your willing to offer assistance (we need more people like you in fact), I just was noting that the thread had stated logs from the source you had mentioned. Now to answer your questions (I'll post this in the OP as well):
- You can see in the logs posted above what is missing in my partitions and what partitions are missing in general.
- 64GB
- I have tried using the PDANet drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers. I will also note that I am on Windows 8.1 (Driver Signature Verification turned off).
Related
Hello everyone, a few days ago my phone's power button got stuck, and the devices was rebooting constantly. So I decided to disassemble it to find the problem, and after I had fixed the button, I reassembled it. But when i turned on the device, i noticed that the bootanimation changed and didn't complete the boot . " Now i have to flash the rom again" I thought, so I tried to boot into recovery. Booting the twrp took about 10 minutes, and the recovery did't recognize the internal storage (0MB), and wasn't able to mount /data and /cache partitions. Using format /data or wiping anything else didn't help.
So I tried to flash stock using fastboot, but i get a message saying "FAILED (remote: flash write failure)" (see screenshots for further information)
HTML:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.538s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'boot' (8980 KB)...
OKAY [ 0.475s]
writing 'boot'...
OKAY [ 0.751s]
finished. total time: 1.229s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.181s]
sending 'cache' (13348 KB)...
OKAY [ 0.634s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.998s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 0.796s]
finished. total time: 1.293s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.116s]
sending 'system' (1021744 KB)...
OKAY [ 32.192s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.493s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.354s]
sending 'userdata' (137318 KB)...
OKAY [ 4.509s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.047s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.413s]
booting...
OKAY [ 0.110s]
finished. total time: 0.526s
Searching on the internet i discovered that there's a problem on the /data partition, but eMMC is not damaged (I followed this guide). What should I do? I can access adb thanks to TWRP, and also fastboot. Please help me:crying:.
This line keep spamming, tho :
I:Actual block device: '/dev/block/mmcblk0p28', current file system: 'ext4'
Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
Try this, or this.
I read this issue before, and some users solved it by replacing the motherboard (just in case any of those solution above didn't work)
F4uzan said:
This line keep spamming, tho :
I:Actual block device: '/dev/block/mmcblk0p28', current file system: 'ext4'
Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
Try this, or this.
I read this issue before, and some users solve it by replacing the motherboard (just in case any of those solution above didn't work)
Click to expand...
Click to collapse
Thank you very much! Unfortunately it didn't work, so the only way to get my phone working again is the raplacement of the motherboard? :crying:
Take it apart again and make ABSOLUTELY SURE you did not damage or short any connections. Ideally using a jewelers loup. This should take you a minimum of 10 minutes to really check everything, not a quick glance.
fwayfarer said:
Take it apart again and make ABSOLUTELY SURE you did not damage or short any connections. Ideally using a jewelers loup. This should take you a minimum of 10 minutes to really check everything, not a quick glance.
Click to expand...
Click to collapse
Thank you very much. I checked the motherboard but i didn't see anything. However, the problem of /data happened before i fixed the button, so i think that it's not my fault.
Sorry I didn't see that in your original post. I would suggest you use your warranty and get a new device.
GGADSR said:
Hello everyone, a few days ago my phone's power button got stuck, and the devices was rebooting constantly. So I decided to disassemble it to find the problem, and after I had fixed the button, I reassembled it. But when i turned on the device, i noticed that the bootanimation changed and didn't complete the boot . " Now i have to flash the rom again" I thought, so I tried to boot into recovery. Booting the twrp took about 10 minutes, and the recovery did't recognize the internal storage (0MB), and wasn't able to mount /data and /cache partitions. Using format /data or wiping anything else didn't help.
So I tried to flash stock using fastboot, but i get a message saying "FAILED (remote: flash write failure)" (see screenshots for further information)
HTML:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.538s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'boot' (8980 KB)...
OKAY [ 0.475s]
writing 'boot'...
OKAY [ 0.751s]
finished. total time: 1.229s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.181s]
sending 'cache' (13348 KB)...
OKAY [ 0.634s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.998s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.493s]
writing 'recovery'...
OKAY [ 0.796s]
finished. total time: 1.293s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.116s]
sending 'system' (1021744 KB)...
OKAY [ 32.192s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 32.493s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.354s]
sending 'userdata' (137318 KB)...
OKAY [ 4.509s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.047s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
Post-Flash Factory Reset...
downloading 'boot.img'...
OKAY [ 0.413s]
booting...
OKAY [ 0.110s]
finished. total time: 0.526s
Searching on the internet i discovered that there's a problem on the /data partition, but eMMC is not damaged (I followed this guide). What should I do? I can access adb thanks to TWRP, and also fastboot. Please help me:crying:.
Click to expand...
Click to collapse
A couple of suggestions for you.
I do hope that you back up all your call logs sms and photos etc............
Given that I think you will have to do a "Hard Factory Reset" per these instructions
Nexus 5 Hard Factory Reset
Instructions
Performing a factory reset may take some time, so make sure that you plug your device in to a power source before you start. If your phone becomes unresponsive at any point during these steps, you can restart it by holding down the Power button for several seconds.
1. If your phone is on, turn it off.
2. Press and hold the Volume Down and Volume Up buttons, and then press and hold the Power button at the same time until the phone turns on. You'll see the word "Start" with an arrow around it.
3. Press the Volume Down button twice to highlight "Recovery."
4. Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation mark and the words "No command."
5. While holding the Power button, press and release the Volume Up button once.
6. Press the Volume Down button twice to highlight "wipe data/factory reset" and press the Power button to select it.
7. Press the Volume Down button seven times to highlight "Yes - erase all user data" and press the Power button to select it.
8. After the reset is complete, press the Power button to select the option to reboot your device.
After you have that done I suggest you get yourself WUGfresh. Nexus Tool Kit.
I always do upates via WUGFresh rather than by OTA. The instructios are easy to follow.
If you have ever opened up your phone I suggest that you watch the youtube video by "LE55ONS" on the Nexus 5. It is very detailed and easy to follow.
Good luck to you and let us know how you get on.
Blacksmith5 said:
A couple of suggestions for you.
I do hope that you back up all your call logs sms and photos etc............
Given that I think you will have to do a "Hard Factory Reset" per these instructions
Nexus 5 Hard Factory Reset
Instructions
Performing a factory reset may take some time, so make sure that you plug your device in to a power source before you start. If your phone becomes unresponsive at any point during these steps, you can restart it by holding down the Power button for several seconds.
1. If your phone is on, turn it off.
2. Press and hold the Volume Down and Volume Up buttons, and then press and hold the Power button at the same time until the phone turns on. You'll see the word "Start" with an arrow around it.
3. Press the Volume Down button twice to highlight "Recovery."
4. Press the Power button to start Recovery mode. You'll see an image of an Android robot with a red exclamation mark and the words "No command."
5. While holding the Power button, press and release the Volume Up button once.
6. Press the Volume Down button twice to highlight "wipe data/factory reset" and press the Power button to select it.
7. Press the Volume Down button seven times to highlight "Yes - erase all user data" and press the Power button to select it.
8. After the reset is complete, press the Power button to select the option to reboot your device.
After you have that done I suggest you get yourself WUGfresh. Nexus Tool Kit.
I always do upates via WUGFresh rather than by OTA. The instructios are easy to follow.
If you have ever opened up your phone I suggest that you watch the youtube video by "LE55ONS" on the Nexus 5. It is very detailed and easy to follow.
Good luck to you and let us know how you get on.
Click to expand...
Click to collapse
Thank you. I tried to follow your procedure, but i had the same problem. In fact, when i try to boot recovery, i got all the problems that i explained in the first post. I'm going to buy a new motherboard at this point .
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!
My issue is a complicated one, I think.
[Moto x 2nd gen (XT1095)] Two days ago, I dropped my phone, and the screen was absolutely destroyed. The touchscreen and the display are still working fine, but the glass front is completely annihilated. :/ I sent a request to Motorola to get it repaired, and wanted to reflash the stock 5.0 system image. (I happen to be stupid and didn't make a nandriod of stock) I've done this before, in order to update to 5.1, so I have the files required to do so. This is where I started running into problems.
It more or less successfully flashed the image, with the output below:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash motoboot motoboot.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'motoboot' (2022 KB)...
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.187s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash logo logo.bin
sending 'logo' (467 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (10200 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 0.380s]
writing 'recovery'...
OKAY [ 0.512s]
finished. total time: 0.892s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash system
system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (512688 KB)...
OKAY [ 23.360s]
writing 'system'...
OKAY [ 8.230s]
sending sparse 'system' (513422 KB)...
OKAY [ 23.414s]
writing 'system'...
OKAY [ 7.258s]
sending sparse 'system' (513796 KB)...
OKAY [ 40.036s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (322104 KB)...
OKAY [ 15.842s]
writing 'system'...
OKAY [ 4.025s]
finished. total time: 129.798s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.036s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (694 KB)...
OKAY [ 0.062s]
writing 'fsg'...
OKAY [ 0.045s]
finished. total time: 0.109s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (62248 KB)...
OKAY [ 2.083s]
writing 'modem'...
OKAY [ 0.804s]
finished. total time: 2.889s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 4.443s]
finished. total time: 4.444s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.248s]
finished. total time: 0.249s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
Upon rebooting to insure that everything worked correctly, I was greeted with the dreaded: "Unfortunately, Phone has stopped". Alright, not the worst thing in the world, if anything I can just reflash TWRP and restore the nandroid I had made before hand. I tap "Ok", but only to have "Unfortunately, Nfc Service has stopped" come up immediately afterward. I keep tapping "Ok", but the dialog fail to cease long enough for me to even interact with the phone; therein lies the issue. I can't access settings to enable USB debugging. I boot my phone into fastboot and attempt to flash TWRP, but of course I can't. Now I'm starting to panic and rampantly search Google for the answer. No luck, best I can find is if I could access the setting. The only thing that I could think of doing next is to find someway to use adb side-load, or disable those damned dialogs. I can access storage, and the device's boot-loader is unlocked.
tl;dr: Can't access settings, unlocked boot-loader, stock android stuck at setup screen. Trying to find a way to install TWRP custom recovery.
Please give me some advice!
Thread closed
Please excuse my idiocy. I was too dumb to realize I could use fast-boot to flash that custom recovery... Thread closed, sorry for those whose time I wasted with this.
tried with
sojuk" for Nexus S (Korea version, m200)
but tool kit asking that your device is herring board inside and the img file that you are trying to flash is crespo board.
now i am looking for herring board firmware.
anybody help me please if have link for firmware then share here.
thanks
after passed one day no reply show from any person.
34 person saw this thread.
may be they have no good answer.
let me tell now if i flash with above rom crespo. is it harmful for my cell. or will go safe?
- You are impatient
- Crespo is the nickname of the device
- Herring is the name of the board, it's the same for Google Nexus S and Samsung Galaxy S
- You are running Windows (!) XP (!!)
Make sure you have a Nexus S and not Galaxy S. And then ask aunt Google for the keywords "nexus s herring soju sojuk". You might also take a look at
http://forum.xda-developers.com/wiki/Google/Device_Codenames
Make sure the OS is really compatible with your variant of the specific device. There might be a difference between soju and sojuk.
Ahkah said:
- You are impatient
- Crespo is the nickname of the device
- Herring is the name of the board, it's the same for Google Nexus S and Samsung Galaxy S
- You are running Windows (!) XP (!!)
Make sure you have a Nexus S and not Galaxy S. And then ask aunt Google for the keywords "nexus s herring soju sojuk". You might also take a look at
http://forum.xda-developers.com/wiki/Google/Device_Codenames
Make sure the OS is really compatible with your variant of the specific device. There might be a difference between soju and sojuk.
Click to expand...
Click to collapse
device is m200 korea
tried with 4.1.1
sending 'bootloader' (1536 KB)...
OKAY [ 0.188s]
writing 'bootloader'...
OKAY [ 0.359s]
finished. total time: 0.547s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 1.703s]
finished. total time: 3.250s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'boot' (3964 KB)...
OKAY [ 0.516s]
writing 'boot'...
OKAY [ 0.484s]
finished. total time: 1.016s
sending 'recovery' (4308 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.109s
sending 'system' (294030 KB)...
OKAY [ 37.094s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 37.125s
FAILED (remote: Invalid Argument)
FAILED (remote: Invalid Argument)
rebooting...
finished. total time: 0.000s
tried with sojuk
help please
Looks strange. I am really sorry that I could not help you, but at least I tried.
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!!