when ever i try to flash any image to the device rom fastboot says remote: flash write failure also when i lock bootloader then reboot the device it get back to it's origen lock status "unlocked"
I have tried so many tools and methods to have that image succeed with no luck !
I have tried to log into temporary twirp session then tried to wipe the data it says :field to mount storage ...data...etc
so many threads related to this issue are misleading and I will not give up by replacing motherboard since this is a softbrick issue related to corrupted partitioning i think so please XDA NERDS HELP!
device : nexus 5
cause : bootloop
Related
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
andPS2 said:
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
Click to expand...
Click to collapse
No need to double post. Regular HDX contributors will have seen your issue in the development thread. Well...at least those with some knowledge of your hardware. Unfortunately, there's not a lot of commonality with other android devices. Tough to get help elsewhere. Sorry this happened to you.
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
andPS2 said:
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
Click to expand...
Click to collapse
TWRP operates (loads) from the recovery portion. The symptoms suggest damage to another partition. The reboot likely occurs when a write operation fails or attempts to put data in a protected area. With a second (working/unlocked) device you might be able to compare storage layouts, determine differences and take corrective action...assuming it is not a HW issue. I realize that's unlikely to happen. Not even sure what to look for and the commands needed to reveal low level storage/partition details.
There is no low-level formatting available for HDX.
Since you have an error with /data there is a good reason to check this partition.
Load into TWRP recovery, attach the tablet to a PC with ADB and driver installed, unmount the data using the interface, launch the adb shell,
then try e2fsck -fpv /dev/block/platform/msm_sdcc.1/by-name/userdata
However I'm not sure that any issues with /data can cause the reboots.
Check the system partition too.
On my device Wi-Fi can't be turned on, this can be NAND issues.
thanks for the help
i can try on monday since my half brick fire hdx is at work
merry x-mas !
p.s.
checking the filesystem for userdata and system indeed showed no errors
still have the reboot problem
guess it is a nand problem then...
My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
khiladi_786 said:
My wifi kinda stopped working,so i restarted the phone. When the phone restarted it got stuck on bootloader and i cant move past it. I tried normal powerup,recovery all of which led to bootloader menu again and again with the same error "hab check failed,failed to validate boot image".
I tried flashing it with fastboot following this tutorial http://forum.xda-developers.com/showthread.php?p=52772182#post52772182
To know the android version i typed this command {mfastboot getvar ro.build.version.full} for which i got this {Blur_Version.23.201.3.condor_retaildsds.retaildsdsall.en.03}
so i downloaded this firmware {XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml} the one which i could get.
then i ran those commands,heres the screenshot of those commands and the errors i got:
https://postimg.org/image/gmtygv2ab/
https://postimg.org/image/bpwtxvlvx/
the only thing i havent treid is unlocking the bootloader and then flashing it.Should i try that?
This problem has occured once in the past but then i took the phone to motorola service center and they fixed it.I dont want to waste any more money on his phone.
Click to expand...
Click to collapse
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
khiladi_786 said:
Since no one has replied yet, I unlocked my bootloader and then tried flashing the phone.
Every command got executed except this one "mfastboot flash partition gpt.bin".Please help me i m begging. I m so close to fixing my phone.
Click to expand...
Click to collapse
Don't run the commands manually, use the .Bat file.
Might work
Hi folks,
I see this is an extremely long thread,but I would really appreciate it if you could read it through and give a tip or two.Any help is greatly appreciated!
I just bricked an Honor 9,now I have access to fastboot(be able to flash) and recovery(TWRP or stock both OK),but I don't have ERecovery,when trying to go to EREC I stuck into a "ERROR MODE,ATTENTION!PLEASE UPDATE SYSTEM AGAIN" page,with warnings either about boot or recovery in red.I can go into fastboot with USB connected and the key-combo.Both TWRP and fastboot can flawlessly flash anything,I tried ways flashing system and oeminfo but when I boot system I either go into error mode or it first shows a Google logo splash screen(where it should be Honor Powered by Android) then a flowing Android logo(where it should be a Honor logo),and afterwards it reboots to error mode.
Below is my bricking procedure:crying:
I had STF-AL00B201 (EMUI 5.1) with Magisk root and system-less xposed before.Then I saw RR 6.0.0 and can't help wanting to flash it.First I used full package 8.0.0.336 to OTA then went into fastboot to flash.Surprisingly any command except fastboot reboot will not do.Then I updated to Test build B338 to encounter the same issue.
Code:
fastboot erase data
remote:command not allowed
fastboot flash system system.img
remote:sparse flash write failure
It seems as if there is a hidden FRP lock inside.But in Developer Option there is no OEM Unlock.I believed this is true,for:
1) @fl0wfr told me Chinese B321 has OEM Unlock Option.Since previous builds have it,the newer builds might still have it.
2)EMUI 8 includes Google Services,which is useless in China.
So I followed the advice someone told me on Huafans here
http://cn.ui.vmall.com/forum.php?mod=viewthread&tid=15241915&page=1&authorid=7879103:Flash STF-L09B360 via FF.After I tried I booted up with a somehow merged system(I did factory reset before boot).Apps like Swipe keyboard and Chrome came up but some Chinese Apps like Huawei Browser is missing.Still I saw the version number unchanged.
Then I was too shocked to do a correct action.I remember using HiSuite to rollback to STF-AL00B201 then I got a broken build number(EMUI 8 Android 7.0) and a broken model(STF).Then I was foolish enough to try the HWOTA re-brand method.When it comes to flashing the B120 files I saw the “update not found“ error on phone.Then it ends up with ERROR MODE.
Here is what I tried to save my phone:
Flashing firmware inside fastboot(succeed but no effect)
Restoring backuped boot in TWRP(it goes to Honor logo but went to error mode before the animation ended.)
Tried to flash oeminfo(and I got the Google and Android mention ed before.)
I haven't tried the full-firmware(two update.app) because I haven't got a SD card as big as 8 GB.But I tried the smaller file,it turned on with Honor splash screen but changed to Google instantly.
I have a unlocked bootloader,and in China it means my warranty is void.I am really desperate.
Thanks in advance.
Can it be a physically damaged memory or just a messed-up one?Even if I should go to the support this will prevent me from being cheated...Thanks
Finally got it fixed today,without paying a cent:highfive:Now on 8.0.0.341 with face unlock!
Short:Use HiSuite's system repair function.
Long:To be updated later due to lack of time now
My primary reference for this issue thus far has been the following thread:
Verification Failed, Unable to restart your device.
This dreadful error: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data." And a "Reset" button. Nothing seems to...
forum.xda-developers.com
With that said, I still have not found a resolution. To be clear the objective is to NOT LOSE DATA.
The device I am having this issue with is a customers phone which was previously operational save for the fact that the OLED had been physically damaged. The plan was to transplant the motherboard into a working OLED assembly with frame, boot, and back up data before wiping the device and keeping it for a refurb and sell. The device had not been rooted or modified in any way. I have tried everything from, switching out parts, to booting into recovery and wiping cache, to booting into the rom flashing mode and cancelling out. Just this morning I even successfully flashed the most up to date stock rom (correct baseband and everything) using Odin and still nothing.
I have two additional pieces of information that stuck out to me that may have some relevance.
1. In recovery mode, inbetween the yellow text (android recovery mode info and controls) and the blue text (operations that can be selected) there are three lines of red text that read as follows:
!! CAUTION !!
Not enough storage resource.
Perform "lacking storage booting"
Now I have tried to do some research on this " lacking storage booting" but to no avail, as that function is not listed in the recovery mode.
Is this an indication that the device's storage was too close to being full and somehow became corrupted?
2. In the bootloader mode, there are two lines of purple text at the top that reads as follows:
RPMB fuse blown
RPMB PROVISIONED
I was unable to find out much information on this but most forums suggested that this would cause issues with flashing roms. I however had no issue flashing the stock rom onto this device (I read somewhere that it might fix the issue and not lose data)
I am about to give up hope on the device so I thought I would put out a message for assistance in the off chance that there is anything else I have not tried.
Thanks in advance,
please i need urgent help with my phone, it started about two weeks ago, i was using my phone and all of a sudden my phone just froze and then rebooted itself, i didn't know what to do so i ignored it and continued using my phone as usual, then after two to three days it happened again, i still didn't know what to do so i ignored it for the second time.
now my problem is that last week it happened again but while rebooting it got stuck at dm-verity corruption, your phone is corrupted and can not be trusted, i tried all i could to reboot it but it's not working,
i did some search on google to know what to do, i found this article on google but after trying it i found out that my device bootloader was locked and i can not unlock it except if the oem unlock toggle is on in the developer option in the phone. then i did some more research and found another article after downloading all the software required, i tried it but sp flash tool keeps saying ERROR: STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001).
i tried using wipe factory setting via recovery menu but it reboots and shows dm-verity error anytime i click it, please i need help.