When trying to flash any stock carrier firmware (Verizon or Tmo) Odin successfully flashes, but then Android System Recovery comes up with the error "Can't open dir '/data/vendor_de' (Permission Denied) failed the resizing-data".
Attached are photos.
How do I fix this?
https ://imgur.com/a/JuFTXyp
Have you tried flashing the firmware that came with your phone?
aspiller98 said:
When trying to flash any stock carrier firmware (Verizon or Tmo) Odin successfully flashes, but then Android System Recovery comes up with the error "Can't open dir '/data/vendor_de' (Permission Denied) failed the resizing-data".
Attached are photos.
How do I fix this?
https ://imgur.com/a/JuFTXyp
Click to expand...
Click to collapse
I had that too when flashed firmware, but I just ignore it and reboot the device
I did that. However I have a tmobile s10 and was trying to flash verizon firmware. When rebooting after the error I'm still running tmobile firmware.
Related
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
sayantandas said:
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
Click to expand...
Click to collapse
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
frikisama said:
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
Click to expand...
Click to collapse
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
sayantandas said:
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
Click to expand...
Click to collapse
No, you won't. I said stock RECOVERY, not stock IMAGE.
Code:
fastboot flash recovery stockrecoverysname.img
OK. So could you give me a link to download the recovery image ?
Sent from my Nexus 4 using xda app-developers app
Do you have the original factory image from google? The recovery.img is inside,
if not i will upload it somewhere, though it doesn't fixed the radio update error for me.
I now have a mixed version > the ota update installed without errors, the bootloader is 4.18 but
in settings it complains to still be at 4.2.1 JOP40D
Flashing the stock recovery only leads to an unusable recovery screen with no options for flash/sideload
with an red exclamation mark over the chest of the sweet robot..
any ideas?
maybe i have to reflash my nandroid and try again, the custom recovery was openrecovery-twrp-2.4.1.0-tilapia
here are the images for those who need them
nakasig-jop40d-factory-efcec044.tgz
http://www.share-online.biz/dl/0OWHBFIMLC
recovery.img
http://www.share-online.biz/dl/LM9JBFIMKSG8
EDIT:
Ok finally i was able to use the stock recovery. though it seemed to be dead.
By pressing power+volup showed the recovery menu for me.
Then flashing the update via sideload worked.
cheers phk
Ok guys, so here's what's happening with my Device XT1058. I literally can't install it!
When I try to return to stock and put the first one code that says "fastboot flash partition gpt.bin", it says:
<bootloader> variable not supported!
error: cannot load 'gpt.bin'.
2- When I try to do it by the RSDLite trying to load the 4.2 stock in there is says: "Error check input file. Either XML format is wrong or image files associated with it are missing"
I really don't know what's going on. Ive seen a video with the same model/device as mine and it went perfectly the ROOT/UNLOCKING BOOTLOADER. I did everything as it says on the video but it comes to update the android, I just cant proceed it.
My firmware operator is: Oi. From Brazil.
--
When I try to put the 4.4.3 in the Internal Storage:
1- Trying to install it from "System Updates" just doesn't work. Pops up the same old image as always "Your system is up to date, option: OK"
Then I try to do it manually by going to the Internal Storage in the phone, the zip file appears but I can't click on it.
Can someone help me to fix this problem ? Thanks!
OBS: I DID Install the BOOTLOADER and ROOT my phone perfectly as long as I can use it as a developer. But can't install either 4.2/4.3 rom in any ways I did as I explained it on the top.
Liooh said:
Ok guys, so here's what's happening with my Device XT1058. I literally can't install it!
When I try to return to stock and put the first one code that says "fastboot flash partition gpt.bin", it says:
<bootloader> variable not supported!
error: cannot load 'gpt.bin'.
2- When I try to do it by the RSDLite trying to load the 4.2 stock in there is says: "Error check input file. Either XML format is wrong or image files associated with it are missing"
I really don't know what's going on. Ive seen a video with the same model/device as mine and it went perfectly the ROOT/UNLOCKING BOOTLOADER. I did everything as it says on the video but it comes to update the android, I just cant proceed it.
My firmware operator is: Oi. From Brazil.
--
When I try to put the 4.4.3 in the Internal Storage:
1- Trying to install it from "System Updates" just doesn't work. Pops up the same old image as always "Your system is up to date, option: OK"
Then I try to do it manually by going to the Internal Storage in the phone, the zip file appears but I can't click on it.
Can someone help me to fix this problem ? Thanks!
OBS: I DID Install the BOOTLOADER and ROOT my phone perfectly as long as I can use it as a developer. But can't install either 4.2/4.3 rom in any ways I did as I explained it on the top.
Click to expand...
Click to collapse
You appear to be going about this wrong. You don't put the SBF files on the phone itself...you put them on your PC, in the same folder that fastboot and mfastboot are located.
The error you are receiving "error: cannot load gpt.bin" indicated that the file you are trying to flash is NOT in the same folder as fastboot/mfastboot.
Additionally, there is no "4.2" or "4.3" for the Moto X. There is 4.2.2, 4.4, 4.4.2, and now 4.4.3 (which may or may not have been released for your carrier yet).
Can you explain exactly what you are doing? Where did you get the SBF file to flash back to stock? Did you extract the archive? And make sure you are using the correct firmware for YOUR carrier. We don't like to support people who try to flash other carrier's ROMS to their phone. This can cause issues.
If you have rooted using SuperSU then even after using SuperSU to unroot you will running into a couple of errors. Here is how you fix them.
Error #1:
install-recovery.sh can not be copped
[Fix]
Restore your phone using the image found in the MOTO X 2014 Pure Multi Tool found:
https://www.androidfilehost.com/?fid=95784891001604540
Then flash the ATT modem found :
http://cl.ly/1l0x3y0e0L3s
Then reflash the OTA zip
---------------------------------------------------------------------------------------------------------
Error #2
Extra content found in modem
Flash the ATT modem found:
http://cl.ly/1l0x3y0e0L3s
Flash the OTA zip.
Some people have reported having to do a factory restore or re-flash the ATT modem again after the OTA finished installing in order to get LTE.
This worked perfectly, thanks!
What was y'all command line for flashing modem???
fastboot flash modem (file name)
And flashing the AT&T modem will still allow us to use the device on TMobile?
Hi, a friend gives me his S6 920T (T-Mobile variant) because he has a lot of problems (UI crash all time and another process to) and I decided to install Nougat with ODIN 3.12.7. I downloaded the rom on Sammobile and the flash was succesfull but when the phones reboot, in the blue screen, I saw the DRK error but then the phone rebooted and enter to the stock recovery with this message:
No support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
Im searching on but I can find the solution. I tried doing full wipe and reboot but nothing. I flashed again, but no solution. Any idea? Thanks!
Sorry for my bad english!
KbZonFS said:
Hi, a friend gives me his S6 920T (T-Mobile variant) because he has a lot of problems (UI crash all time and another process to) and I decided to install Nougat with ODIN 3.12.7. I downloaded the rom on Sammobile and the flash was succesfull but when the phones reboot, in the blue screen, I saw the DRK error but then the phone rebooted and enter to the stock recovery with this message:
No support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
Im searching on but I can find the solution. I tried doing full wipe and reboot but nothing. I flashed again, but no solution. Any idea? Thanks!
Sorry for my bad english!
Click to expand...
Click to collapse
download from autochainfire your root file and flash..ur problem willl solve
Emmaugoh said:
download from autochainfire your root file and flash..ur problem willl solve
Click to expand...
Click to collapse
No this didn't fix it need help
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
mohiminul said:
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
Click to expand...
Click to collapse
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
sefrcoko said:
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
Click to expand...
Click to collapse
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
mohiminul said:
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
Click to expand...
Click to collapse
Ok I see. Hmm not sure...I googled and found this thread that has a few solutions (Kies, Smart Switch, etc.) that seem to resolve the issue. If someone knows for sure they can chime in, but in the meantime I would start here (even though it's for Note 4...might still work, or at least point you in the right direction).
https://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
This thread may help.
https://forum.xda-developers.com/ga...-hard-bricked-note-8-sm-t3735009/post75195355