[resolved][help] galaxy s sc-02b ntt docomo blocked and not boot - Galaxy S I9000 General

hello,
I've tried to re-install the officiel rom of this device because its N° imei is unknown after some flash
I've tried this solution but the flash failed with the two ways and I dont know why ! and after that the device wont to start and it stay blocked on screen with picture seem that's no connection between the phone and the computer (look at the picture in the attachement)
After that I've tried another solution to flash the latest rom available for this device with odin, but like the first it's not worked !
There's an 3rd solution but I can't download the files because the user bandwith is exceeded
So I'm looking for the good way to flash this device, or a good link for the files in the 3rd solution
Thank you very much

I just noticed that every time the operation failed when flash the modem file

I've found the good ROM for flashing here

Related

Failed root with odin, cannot detect with Kies 3

recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
vivek318795 said:
recently got a Galaxy Note 3 from Verizon. I wanted to root the device, it was really easy with my old original galaxy so I looked at a few guides which were all using "Root de la Vega" and finally tonight in an attempt to root my device I used the guide at:
phonearena.com/news/How-to-Root-the-Verizon-Samsung-Galaxy-Note-3_id48247
I put the phone into download mode and connected it to Odin with the included Samsung USB 3.0 cable. I selected the root de la vega firmware using the AP button and hit Start to begin flashing. Almost immediately after the write starts it fails and on the phone it says:
Quote:
"Secure check failed: cache"
In the guide it mentions there may be problems using the USB 3.0 cable so I tried it with a USB 2.0 cable with the same results. I tried rebooting the phone to see if it had wiped it. Indeed, it had been wiped and is now going to the screen which says there was a problem updating the firmware and says to use the Software Recovery Assistant to restore the firmware.
I am not sure why this has happened. I feel like I followed the instructions to the letter. After looking at some different guides I am noticing that many have you put the phone into USB debugging mode which the guide I was following doesn't mention. Is this why it has failed. Is this strictly required?
I would like to get this device rooted, but now my number one priority is getting it back into a state where it will be more useful than the paperweight on my desk. I tried downloading Kies 3 which I read can restore the stock firmware on the phone. I was extremely annoyed when I realized that Kies 3 would not recognize my phone at all. It says that the device is not supported by Kies 3 and gives me a link to check support (which just brings me to the Kies download page which clearly states that my phone (Note 3) is supported. I even tried to download the original Kies software which will not even recognize the device enough to tell me it's not supported.
Can anyone point me to a way to restore my phone to factory settings? Can I download the stock firmware and flash it with Odin, will this work if I couldn't get the custom firmware to flash in Odin (possibly because of not setting USB debugging?).
EDIT: Note that, following the guide, I did not check which build number my phone is before running Odin, now I have no idea which it is and what stock firmware to download. Is there anyway to figure out which build my phone was on or which stock firmware I need to download?
EDIT: So it looks like my problem is similar to this problem posted on XDA. I followed the link in that thread to this guide to restore the stock firmware. However, it has three different downloads for different builds, I am not sure which I should download or if there is a way to figure it out. Will any of them work? Can I try them one at a time safely until one of them works. I don't want to mess things up any worse than I already have.. I downloaded the MI9 firmware from that page, but this is just a guess... Anyone have any idea?
Any help will be very much appreciated.
Click to expand...
Click to collapse
I'm running into the exact same issue, did you ever find a solution?
Same issue
I have the same issue. Is there no help? Chainfire? do you have a CF-Root for SM-N900V yet?
Thanks. any help is appreciated.

[HELP] its Urgent,Important,why no one cansolve it??????

PLZ help me on this guys , im going mad on this
HOW TO SOLVE THE " DM-VERITY VERIFICATION FAILED NEED TO CHECK DRK FIRST " or when i install a stock rom this one first appears bUt not in reCovery " DEVICE DOESNT HAVE DRK , INSTALL DRK " ????????
it all happened after i deleted my imei then succesfully restored it with backup when downgrading from that god forsaken CM13 made by raymanFX (it was build 8 i think) , now OTAs and Security patches all face this issue in recovery when installing after being downloaded , now im in middle of nowwhere with no backup and ive tried everything but none works and im not a hacker nor an information thief just a member waiting for HELP... (SM-N910H)
:crying::crying::crying::crying::crying::crying:
! THERE IS NO OFFICIAL SAM CUSTOMER SERVICE IN MY CITY AND mobile merchants are not TRUSTWORTHY !
Someone told me that i need to find a cert file for my Phone and i found it , how is it related to DRK and what should i do with it??
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
yeah. try flashing samsung stock firmware with odin. have you done it
Sent from my SM-N920G using Tapatalk
YEP Odin flash is most of the time a good fix.
ankahuja said:
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
Click to expand...
Click to collapse
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
ArmanFGT said:
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
sudhakar35 said:
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
Click to expand...
Click to collapse
Thanks for the reply but the main problem is that any OTA that comes to note 4 i download them and the device says to restart to recovery to install the Update and i say yes but when it goes to recovery the recovery wont function well since it shows dm-verity error and supported API : 3 the update process fails to complete . My imei is as cool as always i havent had a problem with IMEI since i bought the phone
at least 10000 people have note 4 and none has had the problem ???? REALLY ?
seems like im pretty f***ed up
chappatti said:
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
Click to expand...
Click to collapse
dear chappati , according to that video i need a physical thing which is called a BOX and a software called GC PRO because that guy had my problem and fixed it with a clicking , but im reasearching for 5 months and nothing comes out . i need information PLZ
Hi, i used to had that problem too, when i first flash a custom rom to my N910G i back up my stock rom.. everthing including EFS.. after that then i wipe everything like normal procedure when u flash a rom. till then 1 day i wanna go back to stock rom i accidentally ticked EFS while i wanna restore that stock rom back up and then i thought it was nothing serious until i flash stock rom with odin and when i boot into stock recovery that dm-verity message was shown, did so much research but no luck. my n910G was on a Singapore firmware, that time it had a update i just try my luck by downloading the latest SG firmware and then that message was gone! m now already on MM no problems like that anymore
Deleted

SamMobile firmware flashing fails (SM-G530H) (Please Help)

Greetings.
I tried to flash the original firmware of my SM-G530H (4.4.4) using odin ( Odin3_v3.10.6 ) but every time it fails right at the beginning of the process.
I download the firmware (brazil/claro) from the Sammobile website, did everything that this tutorial told me to (androidmtk.com/flash-samsung-stock-rom-using-odin) but it fails every
time.
It is not a connection problem because odin recognizes the device and the process starts, but it fails right after the beginning.
Does anyone know what might be happening?
Thank you!
I forgot to mention that the phone is still working. I want to flash the stock rom because I rooted and the battery seems to be having some issues after that.
My problems started when I did this root (http://forum.xda-developers.com/gra...lly-rooted-galaxy-grand-prime-t2935607/page40).
I noticed it changed the baseband of my phone from to HVCU to HCXU, and according to what i have understood from my searches that's why i keep receiving the error message "Error: Secure Check Fail : aboot" on the phone every time I try to flash the original firmware (http://www.sammobile.com/firmwares/download/42103/G530HVCU1ANL4_G530HZTA1ANL4_ZTA/).
Does anyone know how can I fix it?
Thank you very much! :good:

Is this legit? Samsung Combination (Inhouse Testing) ROMs, Fix Every Broken Phone?

Found this little nugget while trying to figure out how to repair my recovery....
these guys charge $2.00 and say that Combination ROM's are Pie in the Sky, can fix all problems, etc...
https://gsmfirms.com/downloads/g950f-combination-file/
Found the same thing here for FREE
https://samsungcombinationfile.com/samsung-sm-g950fd
File Downloaded is (SM-G950FD_Combination_FA70_G950FXXU1ARH1_CL12792727_QB19342260_REV00.zip)
I found it after reading a EFS backup (via 7 zip) and browsing to
Code:
\efs\FactoryApp\HwPartInform
"SW_VER":"FA70_G950FXX . . . .
\efs\FactoryApp\HwParamData
"AP":"EXYNOS8895 . . . .
Lots of other valuable phone information in these files
Anyone tried this?
Is this a scam?
Thanks
Ok, I just installed and I at least have a working ROM now. This is not a normal ROM but a specialty debug ROM, the home screen is version and device information. It contains lots of functions for running various test and looks like it allows you to change some things like IMEI.
I used ODIN 1.13.1 to flash TWRP 3.2.1. After reboot, an error says "recovery image signature check fail". At this point, only Download Mode can be reached.
re-installing combination ROM fixes recovery (Note it is not TWRP, it is a simplified factory recovery). So, it appears, you cant just write any Recovery with this ROM installed.
This Rom can receive calls, but not text, there is no messaging app.

I need help here Asap Flashing Galaxy S7 Edge (G935FD)

The phone was working good with no problem untill i tried to root it . and at my first attempt using twrp the device just stuck at boot loop so i tried a factory reset but no luck
so i downloaded Official 8.0 Oreo Rom (G935FXXS4ESCB_G935FOJV4ESAH_XSG) and here i am i cant flash the rom with odin the phone display an error says sw rev. (Bootloader) Device 5 Binary 4 sometimes with differnt files show Device 3 and binary 1 still cant find the right file even that i know those files were working great cause i already flashed the phone before
ps original rom before this happend was oreo
Any Help PLease ?
im waiting please leave your answer and i hope i can reply asap
Thank you
i solved the problem by matching the last rom was installed on the phone i wasnt able to find the correct rom number at first cause i wasnt able to boot into the system then i figured out how to do it from the terminal in TWRP hope i can help somone else
The booloader has been updated. Then you should use the most current rom.
Simlfe said:
The phone was working good with no problem untill i tried to root it . and at my first attempt using twrp the device just stuck at boot loop so i tried a factory reset but no luck
so i downloaded Official 8.0 Oreo Rom (G935FXXS4ESCB_G935FOJV4ESAH_XSG) and here i am i cant flash the rom with odin the phone display an error says sw rev. (Bootloader) Device 5 Binary 4 sometimes with differnt files show Device 3 and binary 1 still cant find the right file even that i know those files were working great cause i already flashed the phone before
ps original rom before this happend was oreo
Any Help PLease ?
im waiting please leave your answer and i hope i can reply asap
Thanks
Click to expand...
Click to collapse
The binary versions have to match (what's currently on phone versus what you're trying to flash) unless it's an upgrade (higher numbered ). The 5th number from the right would be the version number, in your case the firmware you're trying to flash G935FXXS4ESCB, 4 would be the binary. You need to find out what version your phone is on currently then either match the binary number or upgrade to latest. Google your phone model (SM-G935F) and check to see what the latest firmware version is. You may have taken a software update at some point in the past since you last Odin flashed which may have upgraded your software to newer binary.
You also may need to ensure you are using Odin3 v3.13.1 for newer file format (lz4) in Oreo.
For firmware version verification for your phone model check link below:
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/
Hope this helps ...

Categories

Resources