Hello,
I have a Sensation XE with Android_Revolution_HD-Sensation_6.0.3_XE ROM installes. Two days ago the screen become black and I cant do anything with the Phone. I cannot put it on HBOOT because the screen is always black. I can see the screen its turned on, I also called the phone and it rings.
I tried to install a recovery using Android Flasher App and I get this:
< waiting for device >
security: off
finished. total time: 0.000s
sending 'recovery' (4618 KB)...
OKAY [ 1.094s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.406s
downloading 'boot.img'...
OKAY [ 1.094s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.094s
rebooting...
finished. total time: 1.719s
Somebody has any idea about this problem?
Best Regards,
RC
May be it is a hardware problem? In this case you should try to put it into stock condition and bring it to service. I think you can do it, because you do not need the phone screen to flash RUU, change CID and S-ON it.
Related
hello,
i've got this lg-D820 stuck in CWM Recovery v6.0.4.5 screen
i want to flash it back to recovery and downloaded 5.1.1 factory image from google developers site
but i always get error while flashing bootloader,something like this-
Code:
sending 'bootloader' (3119 KB)...
OKAY [ 0.334s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.583s
rebooting into bootloader...
OKAY [ 0.076s]
finished. total time: 0.080s
< waiting for device >
i need help to fix this set
I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s
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.
ive been following numerous tutorials and with everyone of them i receive the same error message what could i be doing wrong?
i turned oem on on fastboot but that as far as i could go i cant go beyond flashing the recovery.
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
XDA Visitor said:
ive been following numerous tutorials and with everyone of them i receive the same error message what could i be doing wrong?
i turned oem on on fastboot but that as far as i could go i cant go beyond flashing the recovery.
sending 'recovery' (4876 KB)...
OKAY [ 1.131s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.458s
Click to expand...
Click to collapse
Hi
Thank you for using XDA Assist
You can create an account and post this here
http://forum.xda-developers.com/lg-v10/help
Thank you..
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.