try to update and now my Nvidia shield 2019 model don't boot, I only see the nvidia logo and after reep eboot, I try to hard reset the device but nothing happened,
I download a image to flash again the device but
I receive the message failed to verify package compatibility (result-19): no device manifest file
Which file should download? Why I failed to install image, and why failed to do hard reset, any help
can anyone help
Related
hi guys,
This is my first thread so please dont mind my mistakes
im here just try to provide possible answers to them , who were looking for "Security Fail" error while flashing Bada firmware over wave 1 2 or 3,
i hve able to recover my wave 1 from security fail error, and successfully flashed my wave1,
if you have security fail errors, try latest Multiloader v5.67 , (dont try older versions)
download Multiloader v5.67 from here http://www.mediafire.com/?s59s0xq99uj5bq7
after connecting phone with PC via USB in Download mode , check LIS checkbox,
if you want to flash boot file, check Boot Change(only boot change no other checkboxes) and load boot files from your downloaded firmware folder, after selecting boot files press download, wait for massage 'wait for reset', your phone will try to reboot but it will stuck at bada logo, dont worry, pull your battery, make your phone again in download mode , press PORT Search ,now uncheck all check boxes except LIS, (do not select Full Download , Master Rom or Diffrances only) now select Amss, Rsrc, Rsrc2(low), facotryFs, apps compressed, CSC, ShpApp, and fota file from downloaded Firmware folder to their respective fields, and press Download, wait untill massage "All files completed". your phone will boot if not try battery pull and again boot your phone, once booted do factory reset using this code *2767*3855#,
thats it
i have sucessfully recovered my wave 1 from security fail error and updated bada 2.0 XXLC2 using above method
hope it help others also,
please forgive me for my english
Take care
I tried flashing all the files but the phone is now stuck in the samsung loading screen. Please help
I had a failed update on an HP Elite X3. It restarted mid update and went to a blue screen saying the BCD configuration file does not contain valid information. The phone does not get recognized by the PC and is in a boot loop with the blue error page. I was able to get the phone into Emergency Mode with Thor2 but could not replicate it and am back to the boot loop.
My question is how can I get the BCD file fixed? Or alternatively, how can I manually flash the FFU file since I can't get the phone to register on my PC?
Thanks to those who can help!
Did try volume + and power combo to flash ffu file with Windows Phone image designer, hope that works
raghulive said:
Did try volume + and power combo to flash ffu file with Windows Phone image designer, hope that works
Click to expand...
Click to collapse
Booting to "FFULoader.efi" (Vol+,Power) need correct BCD or at least Working BootArm.
Device *CAN BE* easily flashable from UEFI fine.
ED Mode *Should* fix all problems about firmware/bootloaders.
If still persist, may be Hardware Failure.
Any luck ? old thread i know...
same problem...no combination of keys work..reboot loop
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM
My pixel xl not pulling up OTA update and am unable update manually as well. I tried to flash factory file and OTA sideload but no help.
When am trying to flash factory file it give me error as unable to generate user file.
When am trying to sideload OTA it get failed at 47% as unable to verify hole package.
My android version is 8.1 and update till 5 December 2017 somebody please help me to solve this.
[There is another strange issue in my pixel xl that when it reboot in bootloader my pc does not recognize it as bootloader interface then i need to unplug and plug it again to work]
I'd recommend (assuming you have an unlocked bootloader) that you flash the full factory image (make sure to remove the -w to retain your data from the flash-all.bat). Also - make sure you have updated to the latest platform tools. I suspect that older/outdated platform tools are causing some of the issues/errors you describe above. Good luck.
Thanks for you fast reply,I am having unlocked bootloader but same result as am trying to flash the full factory image but no luck updated latest platform tool.
Are you able to post the full install/error log when you try to flash factory? Other things to try - redownload the full factory image (to rule out a bad download). Make sure you properly unzip and are in the right directory when you run the flash-all.bat. Make sure your PC isn't running out of disk space...
I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?
Is there a way to fix the crushed partition table without buying stuff?
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.