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 .
Related
hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia
Hello to all,
I am new here so sorry for not being familiar with the lingo but hopefully you guys can help me out.
I have a pretty new Droid Razr HD, got it a few months ago. Annoyed by the stupid and obnoxious "droid" sound at start up, I thought I'd take a go at getting rid of that. I rooted the phone with Dan Rosenberg's exploit as posted on http://www.droid-life.com/2013/04/0...r-hd-running-android-4-1-2-other-devices-too/ and everything worked like a charm. I managed to get rid of the sound as desired and thought "why not put my own audio in?" So I took an audio file, snipped off a bit of it, converted it to .ogg, put it in system/media and renamed it droidpu.ogg and what do you know, worked like a charm. Then I thought "hey, while I'm at it, why not change the bootanimation? I can make my own and have it play along with my audio!" After much effort I finally succeeded at making a working bootanimation.zip file, put it in system/media after renaming the original, turned off my phone, and turned it back on. First I got the Motorola icon and then my bootanimation started playing, but without the music. And then the bootanimation looped once. And then it froze. Now I can't go past there. So I tried everything. I went to AP Fastboot Flash Mode, then held the volume up and power buttons, released the power button when the screen went blank and tried each option available. When I try recovery mode, I see the Android guy laying down with a red ! triangle above him, and then it goes back to the AP Fastboot Flash Mode. [Update on this part here: I did after some searching around find out how to enter the recovery mode options and I did the "wipe data/factory reset", but still the same thing happens when I try to boot up like normal.]
Finally I came across mattlgroff's droid razr utility (http://forum.xda-developers.com/showthread.php?t=2192467&nocache=1), downloaded it, opened terminal, and tried both options 1 and 2 (I don't care at this point if my data is wiped, I just want to get my phone working again). This is what I got both times:
press any key to exit
Make your choice
2
64 bit Mac System
[*] Simple Razr Restore
[*] Linux/Mac Version
[*]
[*] Before continuing, ensure your Razr is in the
[*] 'AP Fastboot' mode and connected via USB.
[*]--- Also press the keys after the screen flashes back on when asked---
[*]
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Get Ready To Break Out Your Sudo
[*] Press Enter To Continue
Password:
sending 'mbm' (512 KB)... OKAY [ 0.047s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
Press any key when the screen flashes back on.
sending 'mbmloader' (42 KB)... OKAY [ 0.010s]
writing 'mbmloader'... INFOInvalid partition name mbmloader
FAILED (remote failure)
sending 'mbm' (512 KB)... OKAY [ 0.047s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
Press any key when the screen flashes back on.
erasing 'cache'... OKAY [ 1.227s]
sending 'logo.bin' (854 KB)... OKAY [ 0.073s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
sending 'devtree' (512 KB)... OKAY [ 0.047s]
writing 'devtree'... INFOPreflash validation failed
FAILED (remote failure)
sending 'system' (262144 KB)... OKAY [ 28.321s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
sending 'boot' (8192 KB)... OKAY [ 0.647s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
sending 'recovery' (9216 KB)... OKAY [ 0.734s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
sending 'preinstall' (262144 KB)... OKAY [ 20.807s]
writing 'preinstall'... INFOUnkown partition name preinstall
FAILED (remote failure)
sending 'radio' (21936 KB)... OKAY [ 1.713s]
writing 'radio'... INFOInvalid partition name radio
FAILED (remote failure)
rebooting...
Your device will now reboot and install radio files, then fully boot normally
After this my phone stays on AP Fastboot Flash Mode with the Fastboot Reason: Flash Failure.
Any suggestions????? Maybe if there is a way to reinstall Jellybean 4.2 from an external sd card???? Or is it possible to access the system files on my droid so I can just delete the bootanimation I made and make the original play again?
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).
Hi. I have a OPO that i cant flash or erase anything.
It`s encrypted and what i boot OS it`s asks for a code and it doesn`t meter which one i will write. The phone says:
View attachment 3283408
When i press on Reset Phone - nothing hepends.
Rebooting to recovery (The ColorOS recovery V1.2) and Wipe data and cache does nothing.
Flashing custom recovery or erasing user-data whiting fast-boot falls (with locked and unlocked boot-loader) s:
target reported max download size of 1073741824 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.844s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.893s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.066s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.000s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.037s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.016s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.057s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'tz' (283 KB)...
OKAY [ 0.015s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.070s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.366s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.019s
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'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 8feeb7e6
--------------------------------------------
checking product...
OKAY [ 0.000s]
sending 'boot' (5606 KB)...
OKAY [ 0.188s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.257s
Press any key to exit...
Even flashing with MSM8974DownloadTool falls - only 8974_msimage.mbn flashes and phone power offs by it self.
Tried to temporary boot custom recovery and wipe anything - no lack.
Please help
Hi friends It's me REET-The Hacker.Studying in Class 12th and fond of Android Devices.And this is my 1st thread.
In this thread I am providing you the fastboot flashable rom for LYF Flame 6.
This rom is pre rooted and its the official stock one.For Build number or any other kind of information see the screenshot below.
STEPS TO FLASH THE ROM;1.Extract the rom file(link is given below).
2.Go to fastboot mode.For this see this video coz it's complicated and i have wasted enough time to get into bootloader.:angel:
Link-: Mod edit: link removed.
However i am also writing down the steps.
>Power off your device.
>Switch on the device by holding "power" and "volume -" key.
>After that you will see android logo.
>Then hold the "power" key for 1 sec and press the "volume + key".
>You will get into recovery now simply select 'reboot to bootloader" option by pressing "volume -" and "power" key.
3.Now open the folder where you have extracted the rom.
4.Double click on "Flash all.bat".
After that wait for some time till it completes after that pull up the battery and power on your device.
You will see that your phone is now rooted and some apps will be installed.
If you have any type of "phone not detecting" issue then install all the drivers ONE BY ONE.
Check the screenshots below.
DOWNLOAD LINK FOR ROM
Mod edit: link removed.
DOWNLOAD LINK FOR DRIVERS
Mod edit: link removed.
Hit me a Thanks or Rate my thread,If i Helped You.Please.
reetpriye said:
snip
Click to expand...
Click to collapse
Sir .. tried the procedures as mentioned in the post but could not get the device rooted (LYF flame 6) .... only does a factory reset .... would be thankful if could help getting the phone rooted ....
rsmani1965 said:
Sir .. tried the procedures as mentioned in the post but could not get the device rooted (LYF flame 6) .... only does a factory reset .... would be thankful if could help getting the phone rooted ....
Click to expand...
Click to collapse
Do all the steps carefully what issue are you facing,
For rooting guide you can follow this too https://www.skyneel.com/root-lyf-flame-6:good:
Please share your WhatsApp number or WhatsApp me 8737978358
Bro my phone was running on version 8, then it automatically started updating and my phone was bricked! It was showing "no command", I did hard reset but that also didn't work! I took it to service centre, they fixed my phone but now the software is version 11.... And it does not have multi-tasking view! Also wifi is not working now! I want to go back to version 8 now.... I have downloaded your firmware, but I don't know how to install the drivers! Plz help bro.... My whatsapp number is - +919804102574
IM try This Method Not DOne
rsmani1965 said:
Sir .. tried the procedures as mentioned in the post but could not get the device rooted (LYF flame 6) .... only does a factory reset .... would be thankful if could help getting the phone rooted ....
Click to expand...
Click to collapse
After flash Same Restart Complaint Not solved My problem
Flah Details
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash boot
boot.img
sending 'boot' (15360 KB)...
OKAY [ 0.498s]
writing 'boot'...
OKAY [ 0.432s]
finished. total time: 0.933s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash reco
very recovery.img
sending 'recovery' (15360 KB)...
OKAY [ 0.491s]
writing 'recovery'...
OKAY [ 0.439s]
finished. total time: 0.934s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot erase syst
em
erasing 'system'...
OKAY [ 2.777s]
finished. total time: 2.778s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.0
sending 'system' (131082 KB)...
OKAY [ 4.177s]
writing 'system'...
OKAY [ 7.033s]
finished. total time: 11.215s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.1
sending 'system' (131082 KB)...
OKAY [ 4.194s]
writing 'system'...
OKAY [ 7.279s]
finished. total time: 11.477s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.2
sending 'system' (131082 KB)...
OKAY [ 4.183s]
writing 'system'...
OKAY [ 7.585s]
finished. total time: 11.773s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.3
sending 'system' (131082 KB)...
OKAY [ 4.168s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 12.333s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.4
sending 'system' (131082 KB)...
OKAY [ 4.167s]
writing 'system'...
OKAY [ 7.066s]
finished. total time: 11.237s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u s
ystem system.img_sparsechunk.5
sending 'system' (112626 KB)...
OKAY [ 3.584s]
writing 'system'...
OKAY [ 6.345s]
finished. total time: 9.933s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot erase user
data
erasing 'userdata'...
OKAY [ 9.490s]
finished. total time: 9.492s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u u
serdata userdata.img_sparsechunk.0
sending 'userdata' (131082 KB)...
OKAY [ 4.160s]
writing 'userdata'...
OKAY [ 7.592s]
finished. total time: 11.757s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u u
serdata userdata.img_sparsechunk.1
sending 'userdata' (131082 KB)...
OKAY [ 4.163s]
writing 'userdata'...
OKAY [ 7.154s]
finished. total time: 11.320s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u u
serdata userdata.img_sparsechunk.2
sending 'userdata' (47586 KB)...
OKAY [ 1.515s]
writing 'userdata'...
OKAY [ 6.350s]
finished. total time: 7.869s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u u
serdata userdata.img_sparsechunk.3
sending 'userdata' (112418 KB)...
OKAY [ 3.573s]
writing 'userdata'...
OKAY [ 7.676s]
finished. total time: 11.253s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot erase cach
e
erasing 'cache'...
OKAY [ 0.585s]
finished. total time: 0.587s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u c
ache cache.img_sparsechunk.0
sending 'cache' (131082 KB)...
OKAY [ 4.173s]
writing 'cache'...
OKAY [ 6.927s]
finished. total time: 11.105s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>fastboot flash -u c
ache cache.img_sparsechunk.1
sending 'cache' (22530 KB)...
OKAY [ 0.723s]
writing 'cache'...
OKAY [ 2.872s]
finished. total time: 3.598s
G:\china\LYF\LS-4005\201608212219-FASTBOOT-LYF_LS-4005_06_08>pause
Press any key to continue . . .
Click to expand...
Click to collapse
This doesn't seem to be doing anything but damaging phones. Thread closed.
Thread reopened at OP request but we will be monitoring it, if the issues still remain then we will close it again
Regards
Sawdoctor