When i'm using my tablet usually with the official rom make it from while time, suddenly restart and stuck on screen upload mode , update kernel
the device unable to read on PC so i can't install rom from odin and when i trying to setup from SD card (external storage ) not running , even when i try to wipe data and rest factory not running also , please anybody can help me to wake my tablet up again :cyclops:
and this message appear on every process
make_extf4fs failed on /dev/block/mmcblk0p15
footer is wrong
signature verification failed
applied the cSC-code : XSG
did not match sized '/system/csc/common/system/csc/others.xml'(no data available)
installation aborted
haitham eltrmesany said:
When i'm using my tablet usually with the official rom make it from while time, suddenly restart and stuck on screen upload mode , update kernel
the device unable to read on PC so i can't install rom from odin and when i trying to setup from SD card (external storage ) not running , even when i try to wipe data and rest factory not running also , please anybody can help me to wake my tablet up again :cyclops:
and this message appear on every process
make_extf4fs failed on /dev/block/mmcblk0p15
footer is wrong
signature verification failed
applied the cSC-code : XSG
did not match sized '/system/csc/common/system/csc/others.xml'(no data available)
installation aborted
Click to expand...
Click to collapse
Can you boot to recovery?
What did you install or modify to cause this issue?
Does the device show in device manager? What is it labelled as in device manager?
Do you have all of the USB drivers for Samsung phones installed?
Did you have USB debugging turned on before this issue started?
Are you using a Samsung official USB cord?
Have you tried connecting to other USB ports on PC while using Odin?
Try 3.0 ports then try 2.0 ports
Are you using the stock firmware for your specific model number and region in Odin?
Are you flashing the same android version that your device came with when you try to flash with Odin, or is what you're flashing older than what you had?
Sent from my SM-S903VL using Tapatalk
i really need your help
Can you boot to recovery?
yes , i can but all process failed
What did you install or modify to cause this issue?
nothing , it was usual using ( face book )
Does the device show in device manager? What is it labelled as in device manager?
no , cause the usb debugging is turn off
Do you have all of the USB drivers for Samsung phones installed?
yes , all usb drivers and intel android , adb devices
Did you have USB debugging turned on before this issue started?
it's off
Are you using a Samsung official USB cord?
yes
Have you tried connecting to other USB ports on PC while using Odin?
yes , can't detact the device
Try 3.0 ports then try 2.0 ports
Are you using the stock firmware for your specific model number and region in Odin?
3 versions of odin all can't read it
Are you flashing the same android version that your device came with when you try to flash with Odin, or is what you're flashing older than what you had?
not i didn't
haitham eltrmesany said:
Are you using the stock firmware for your specific model number and region in Odin?
3 versions of odin all can't read it
Are you flashing the same android version that your device came with when you try to flash with Odin, or is what you're flashing older than what you had?
not i didn't
Click to expand...
Click to collapse
I dont think you understood these 2 questions.
I didn't ask which or how many versions of Odin you used. I asked if the stock firmware that you're flashing is specifically for your model number and region.
I asked if what you are flashing in Odin is the same android version(KitKat, Lollipop, Marshmallow, etc..) as what your device came with?
Or is what you're flashing older or newer than what your device had.
Sent from my SM-S903VL using Tapatalk
misunderstand
i'm sorry , it's kitkat 4.4.2
T211XXBNI2_T211OJVBNI2
offical , from sammobile
i'm tried to do it from adb but the usb cable not read and try another one same problem also troubleshooting failed to fix it
haitham eltrmesany said:
i'm sorry , it's kitkat 4.4.2
T211XXBNI2_T211OJVBNI2
offical , from sammobile
Click to expand...
Click to collapse
My questions were meant to be answered with yes or no. I did not ask what version your firmware was and I didn't ask for your build number or where you got it from. This answer that you gave me doesn't answer what I asked. I've asked twice now and still haven't gotten the answer I needed. I'm done asking, good luck.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
My questions were meant to be answered with yes or no. I did not ask what version your firmware was and I didn't ask for your build number or where you got it from. This answer that you gave me doesn't answer what I asked. I've asked twice now and still haven't gotten the answer I needed. I'm done asking, good luck.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
no it's not older my device
Related
Hi guys, i have the sm-n9005 32gb but in kies emergency backup firmware that appear sm-n900. any one has solution to get it back like normal?? Thanks all
Download the latest firmware from SamMobile, then flash via Odin
haitichtran said:
Hi guys, i have the sm-n9005 32gb but in kies emergency backup firmware that appear sm-n900. any one has solution to get it back like normal?? Thanks all
Click to expand...
Click to collapse
Did you try to flash firmware with Odin and it didn't complete for some reason? I am asking because I was in your situation when I first bought my Note 3 a while ago.
If this is the reason then it may be the Samsung drivers that are missing from your PC. Some drivers are present and the phone was detected but not all drivers needed were installed, hence the flashing process couldn't complete/failed. Try installing the drivers again, even if you think you have done so already (not just the ones that Windows auto installs when you connect your phone), then try to flash the firmware again. Hopefully the procedure will complete this time. It worked for me. Fingers crossed
This_Guyse said:
Download the latest firmware from SamMobile, then flash via Odin
Click to expand...
Click to collapse
yes correct.
I asked before about that error in download mode "SW rev. check failed Device:3, Binary:2".
Someone gave me a link but it talks about " Device:2, Binary:1" not "Device:3, Binary:2"
Is there a differance?
Becuase I've tried everything about "Device:2, Binary:1" but it failed unfortunately.
The problem happened after I rooted G920F whith CF-AutoRoot (I'm sure it's for same model) but caused in stopping on black screen says "Recovery is not seandroid forcing".
What I've tried:
-Tried to wipe cache (didn't help)
-ReFlash a stock 5.1.1 ROM (gives " Device:3, Binary:2" error)
-Deleted the system fully and tried to flash again (Failed)
Please help I don't know if there another way I didn't know..
Many thanks.
-------------------------------------
Additional:
When I input the SN number in SmartSwich it says:
PDA : OJ1
CSC : OJ1
PHONE : OI9 (THR)
khkdck said:
I asked before about that error in download mode "SW rev. check failed Device:3, Binary:2".
Someone gave me a link but it talks about " Device:2, Binary:1" not "Device:3, Binary:2"
Is there a differance?
Becuase I've tried everything about "Device:2, Binary:1" but it failed unfortunately.
The problem happened after I rooted G920F whith CF-AutoRoot (I'm sure it's for same model) but caused in stopping on black screen says "Recovery is not seandroid forcing".
What I've tried:
-Tried to wipe cache (didn't help)
-ReFlash a stock 5.1.1 ROM (gives " Device:3, Binary:2" error)
-Deleted the system fully and tried to flash again (Failed)
Please help I don't know if there another way I didn't know..
Many thanks.
Click to expand...
Click to collapse
Hi,
Moving your thread to S6 Q&A Section.Experts there may be able to help you.
___
v7
XDA Assist
v7 said:
Hi,
Moving your thread to S6 Q&A Section.Experts there may be able to help you.
___
v7
XDA Assist
Click to expand...
Click to collapse
Okey, many thanks..
Sent from my SM-N920C using XDA Forums
khkdck said:
I asked before about that error in download mode "SW rev. check failed Device:3, Binary:2".
Someone gave me a link but it talks about " Device:2, Binary:1" not "Device:3, Binary:2"
Is there a differance?
Becuase I've tried everything about "Device:2, Binary:1" but it failed unfortunately.
The problem happened after I rooted G920F whith CF-AutoRoot (I'm sure it's for same model) but caused in stopping on black screen says "Recovery is not seandroid forcing".
What I've tried:
-Tried to wipe cache (didn't help)
-ReFlash a stock 5.1.1 ROM (gives " Device:3, Binary:2" error)
-Deleted the system fully and tried to flash again (Failed)
Please help I don't know if there another way I didn't know..
Many thanks.
-------------------------------------
Additional:
When I input the SN number in SmartSwich it says:
PDA : OJ1
CSC : OJ1
PHONE : OI9 (THR)
Click to expand...
Click to collapse
I think "Device" is the Bootloader version you device already has. "Binary" is the version of the bootloader/firmware you are trying to flash. If "Binary"<"Device" you get a write error while flashing. Since your device already has version 3 of the bootloader, you can only flash a version 3 firmwares, like G920FXXU3QOKN (I think the number "3" is the version you need to look at)
JuanRamiro said:
I think "Device" is the Bootloader version you device already has. "Binary" is the version of the bootloader/firmware you are trying to flash. If "Binary"<"Device" you get a write error while flashing. Since your device already has version 3 of the bootloader, you can only flash a version 3 firmwares, like G920FXXU3QOKN (I think the number "3" is the version you need to look at)
Click to expand...
Click to collapse
Thanks for the reply..
OK I've tried flashing G920FXXU3COJ1 but get the same error..
Or there something I must do before..?!
Sent from my SM-N920C using XDA Forums
khkdck said:
Thanks for the reply..
OK I've tried flashing G920FXXU3COJ1 but get the same error..
Or there something I must do before..?!
Sent from my SM-N920C using XDA Forums
Click to expand...
Click to collapse
I would try Samsung Smart Switch (emergency recovery function) to install latest firmware for your device. This will also reset everything.
JuanRamiro said:
I would try Samsung Smart Switch (emergency recovery function) to install latest firmware for your device. This will also reset everything.
Click to expand...
Click to collapse
Sorry for not mention it..
But I've tried this too and it download and faild as well..
I'll give it another try and see..
But what if I try to flash a rom via usb?!
Thanks..
Sent from my SM-N920C using XDA Forums
khkdck said:
Sorry for not mention it..
But I've tried this too and it download and faild as well..
I'll give it another try and see..
But what if I try to flash a rom via usb?!
Thanks..
Sent from my SM-N920C using XDA Forums
Click to expand...
Click to collapse
I think Smart Switch should work. If it doesn't, I think it is a problem with your hardware: PC, USB port, USB cable, phone...
I would try to use Smart Switch in another PC with the original, or a different (liable) USB cable
JuanRamiro said:
I think Smart Switch should work. If it doesn't, I think it is a problem with your hardware: PC, USB port, USB cable, phone...
I would try to use Smart Switch in another PC with the original, or a different (liable) USB cable
Click to expand...
Click to collapse
Thanks..
I'll try with different PC and usb cable..
Hope it works.
Sent from my SM-N920C using XDA Forums
Good afternoon, First I want to apologize for my English is not good ...
Now about the problem, log fails DLL Both also can see the errors ...
Let us begin, a few days ago I came to the post, an experimental 7.0 AOSP rom (http://forum.xda-developers.com/lg-g3/development/experimental-aosp-7-0-nougat-lg-g3-d850-t3450795) ...
Install it and then install wanted to return to my former rom (Fulmics) with surprise that I have no more personal recovery when I want to get with vol down + power gives me the error:
Code:
Error: boot certification verify
secure booting error
cause boot certification verify
Then I decided to use lf flashtool to re-stock with .tot file that already use once ... But with both dll (the model D850 and generic) gives me error, that I leave the logs to download, I hope someone me I can help because it does not do me any good cell like this now ...
Broken Games said:
Good afternoon, First I want to apologize for my English is not good ...
Now about the problem, log fails DLL Both also can see the errors ...
Let us begin, a few days ago I came to the post, an experimental 7.0 AOSP rom (http://forum.xda-developers.com/lg-g3/development/experimental-aosp-7-0-nougat-lg-g3-d850-t3450795) ...
Install it and then install wanted to return to my former rom (Fulmics) with surprise that I have no more personal recovery when I want to get with vol down + power gives me the error:
Code:
Error: boot certification verify
secure booting error
cause boot certification verify
Then I decided to use lf flashtool to re-stock with .tot file that already use once ... But with both dll (the model D850 and generic) gives me error, that I leave the logs to download, I hope someone me I can help because it does not do me any good cell like this now ...
Click to expand...
Click to collapse
Firstly CM does not play well with flashing back to stock. But it seems you've lost recovery so there's no way to flash a stock based rom first.
Have you tried using LGUP yet?
Your also placing your phone into download mode correct?
And using a USB 2.0 port? USB 3.0 will not work.
Sent from my iPhone using Tapatalk
hyelton said:
Firstly CM does not play well with flashing back to stock. But it seems you've lost recovery so there's no way to flash a stock based rom first.
Have you tried using LGUP yet?
Your also placing your phone into download mode correct?
And using a USB 2.0 port? USB 3.0 will not work.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
No, he had not tried to LGUP, now try it and gave me an error, I leave an image with error
Broken Games said:
No, he had not tried to LGUP, now try it and gave me an error, I leave an image with error
Click to expand...
Click to collapse
What error? Your screenshot doesn't show an error. It shows what's plugged into the computer... you click select.
Sent from my iPhone using Tapatalk
Try remove LGUP and the lg drivers and try again fresh . first the drivers then the 8974 ell the lgup if your phone show up at flip then your lucky else you have a brick 3rd phone
Sent from my LG-D850 using Tapatalk
hyelton said:
What error? Your screenshot doesn't show an error. It shows what's plugged into the computer... you click select.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Model "Unknown" and click select: "You have to select a known model, please."
I am using the latest stable nightly build for me, the one released in 04-04 of the LineageOS.
The build is working fine, however, I need to go back to stock firmware.
Last time I tried to do it using newest Odin, I was on latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
Bricked up to the point where a restore using Samsung Switch was the only apparent solution. So I went for it. I have to say it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed me to go into install mode. The installation started anf seemed to be doing fine, but sadly the process has failed at 67%.
I'm afraid that the same thing could happen again.
Could you please help me out?
Thanks.
use Odin
Sent from my SM-G930F using Tapatalk
bustyouup4free said:
use Odin
Click to expand...
Click to collapse
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
hemp_invader said:
I used latest odin for all operations. Flashed all files, including home and the other CSC. The write error occured the whole time.
Click to expand...
Click to collapse
First - Wrong section, this is development not help, https://forum.xda-developers.com/galaxy-s7/help
Second maybe your download is corrupted, or the wrong model, in odin double check sections you know csc, modem, bootloader, and ap, check your drivers and usb cable
Check Your usb cable, don't use an usb hubs, also check is your battery is good
Give log from odin
Trying to figure out for the life of me how to root.
On odin I get stuck at get pit mapping.
Tried numerous ways and apps too root, nothing.
I don't know what else to do.
Tried different computer.
My oem usb broke bought another one.:crying:
Don't know if that's the problem.
Never had a problem flashing custom recovery to any Samsung device before.
Couldn't find ways to downgrade.
Oem and debugging shows unlocked.
What do I Do?
Plz help.
Idk wish i had note 5 can you odin a prerooted stock rom
Sent from my SM-N930F using XDA-Developers Legacy app
I get stuck at "get pit mapping" with everything I try to flash with odin.
Back in the day when I first rooted this device on Marshmallow I just used this simple YouTube tutorial. Does it not work on 7.0?
EDIT: If not the same guy has a video for 7.0 as well, but it roots with Magisk(instead of SuperSU), which I personally don't like.
Sent from my SM-N920T using Tapatalk
bogarty said:
Back in the day when I first rooted this device on Marshmallow I just used this simple YouTube tutorial. Does it not work on 7.0?
EDIT: If not the same guy has a video for 7.0 as well, but it roots with Magisk(instead of SuperSU), which I personally don't like.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I don't know if it's my computer or usb cord or driver issue.. but I get stuck at get pit mapping... every time..
Dethbytes said:
I don't know if it's my computer or usb cord or driver issue.. but I get stuck at get pit mapping... every time..
Click to expand...
Click to collapse
Some simple things you can try that I saw worked for others with this issue on XDA:
1) MAKE sure your Odin is up to date.
2) Try a different USB slot.
3) Try a different USB cord.
4) Some even had luck bypassing this issue by running Odin on a Windows Virtual Machine.
There are also many other threads like THIS out there on XDA that you can search for answers.
Dethbytes said:
Trying to figure out for the life of me how to root.
On odin I get stuck at get pit mapping.
Tried numerous ways and apps too root, nothing.
I don't know what else to do.
Tried different computer.
My oem usb broke bought another one.:crying:
Don't know if that's the problem.
Never had a problem flashing custom recovery to any Samsung device before.
Couldn't find ways to downgrade.
Oem and debugging shows unlocked.
What do I Do?
Plz help.
Click to expand...
Click to collapse
Don't root with odin. Install twrp recovery and flash the magisk or super user zip. If you can't flash anything you need to reinstall samsung usb drivers. And I don't mean auto install via Windows I mean download the exe manually. And get the right twrp. Google twrp and your device name. I've never had this issue