Database Users

Problems after doing unlocksim. Urgent help please.

Hi all, I apologize for my low level of English. I want to tell that to write this report use the google translator.
I also thank in advance the help that you can give me.
Acontinuacion expose my problem:
I followed the steps in a tutorial, to release my samsung i9505 galaxy s4, exposed one of the most important forums, Htcmania.com my country, Spain.
By exposing my problem in the same forum that supra and receiving no response clarification about my problem, I turn to the more important to try to find a solution forum. I go to XDA-Developers.
I do a copy and paste of the report I wrote on the forum that I quoted earlier as I explained my problem well:
My s4 with Android 4.4.2 was completely "virgin" had installed the rom Stock samsung, was not released, was "Yoigo" any advanced recovery had not installed, and had no permits super user "root".
I wanted to release it (Unlocksim) seeking information HTCMania, and I found the following topic "Free S4 I9505 (Unlocksim) in 4.4.2" I followed all the steps in the tutorial. One of the "requirements" was to be root to do a backup of the EFS before touching anything, and to use the application "Region lock away"
So no, I did root, flashing by odin CF-Auto-Root 4.4.2 package.
Being root installed the advanced recovery "CWM" philz touch. And I found myself at this point I made a backup of the EFS system being completely "virgin" that is, with stock rom samsung and android 4.4.2. I followed the steps in the tutorial that I have made previously to unlocksim. One of the requirements to release the phone was change the modem to modem I9505_DXUAME2_MODEM, so I changed the phone modem and followed the guidelines set by the tutorial,
Region to use the application could lock away briefly display an error is possibly to blame for me as I'm seeing. This error could display for two seconds, but from that moment everything seemed to work well, the phone was released. So I changed the modem again for mine.
At this point I decided to choose to install a cooked rom based on stock, namely Omega rom v38.1 for s4 I9505.
And at this point is when my headaches begin to appear. I have experienced problems with the release ... see, the issue is that when the network coverage data is in H + the phone works perfectly, but only if H is not able to load websites etc. This has led me to the edge as I can not be aware every moment of the type of data coverage.
My questions are:
1. Is there a way to stop the phone as he was before unlocksim, ie leave it as it was originally being from Yoigo? (Remember to keep a copy of SAI realized when the system was completely untouched.)
2. How I can solve this problem with the network coverage data?
3. What do you advise me to do?
Please help. Greetings.

you might want to try searching sammobile to see there is a ROM you can download and flash that's for your country and ideally for your phone provider as well. I've run into issues like this on a couple of occasions. One was indeed that the country's ROM I flashed uses differant frequencies and I had the same mobile data connectivity issues you're talking about. This is rare for the international Samsung phones but it does happen. The other scenario I ran into was after flashing a port of the Google Play Edition onto tit, which gave it extended network options, and everything worked quite well but when I restored to stock from a backup on my sdcard I had connectivity issues, once again just like you're describing. In this scenario flashing a fresh stock ROM entirely solved the problem.
Note that in the second scenario I didn't redo the data partition. Presumably flashing the system fixed it or reflashing the firmware partition reinitialized things the way they are meant to work for me.
search for I9505 (or whatever the model of your phone is) where it says search for your device http://www.sammobile.com/firmwares/
Google around the codes if the results aren't revailing enough for what's stock for you and try reflashing in odin. If it persists then backup your apps, wipe the data partition, possibly backup your internal storage as well if you have a stock recover, and try again. Beyond that I haven't had to deal with further problems than that yet but I saw that no one else had responded...

[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

View call history in locked phone

Hi All,
Can we retrieve the call history from a Samsung galaxy S5 (SM-I900H).
The phone actually belongs to a deceased person(a blood relative) and we want to see whats in the phone.
I have tried a few methods such as
invoking MyPhoneExplorer application from adb. (unable to share the exact link due to xda restriction.)
USB debugging is OFF so I could not proceed further.
The phone was booting and waiting for correct password on the login screen at that point of time.
Recently I tried another windows application called
"Wondershare Dr.Fone for Android".
It has a feature called Android Data Extraction, it tried to download some image to the phone. My bad that there was mis-match between the actualy device model(SM-900H) and the model selected in the Dr.Fone application(SM-900I).
The download was terminated in the middle and now the phone doesnt boot up. I am getting the below message when the device is switched on
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Can somebody please help in data extraction from the device.

Bumping the thread to get some response

seenudn said:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Click to expand...
Click to collapse
That part is easy (ish)
Youll need to download firmware for the device (I use fw.updato.com) and flash with Odin. (google/xda search)
Usually there's a 99.9% chance this will go fine without loosing the data on the phone, essentailly at this point, you kinda have to take the 0.01% chance of data loss, you wont get it any other way...
Wondershare's website list compatibility up to 5.0 for that device, id strongly recommend flashing the 5.0 OS, and not upgrading to 6.0.1 until after you are sorted.
As far as the data recovery, from there you are on your own, never used that soft ware, but the above will get you a booting device

Thank you so much Sam for replying.
Wish you a very happy new year !!
The current Android version on the device is Marshmallow (6.0.1).
I found a 5.0 firmware version for India region from fw updato website, but can you please suggest for the below queries.
Should I download all the 3 binaries (PDA, CSC, Phone) to the device?
If I download all the 3 binaries using odin, is there a good chance that the data will still be available?
Thank you in advance.

A6000 technically Dead.. Help Appreciated

Hello
My phone suddenly faced a bootloop, i was on cyanogen 13. just looping the Lenovo logo. Not able to get into recocery.. But QFIL detecting phone, and i even flashed the kitkat version of stock.. The process shows success but still im stuck at bootloop, even tried various method.. Your valuable help appreciated here

any help ?

mjtirur said:
any help ?
Click to expand...
Click to collapse
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised​ on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.

Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen

i have solution.
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
If you have any problem you can simply tell me via my WhatsApp no. - +91 9205097520 (indian no.) Or simply reply me on xda or simply mail me - [email protected] . I have other tricky solution steps ,which were really used and tested by me. Bye friends.......... And Don't forget to tell me about your device problem .

sasukay said:
I think it's some hardware problem. The phone when first came to market has one of the best specifications. Other players had significantly higher prices of their phones providing same hardware. So, I think that Lenovo compromised​ on the hardware components to provide the SD410 and 2gigs of RAM for this price. I many times had problems with proximity and light sensor. Also the battery sometimes awkwardly dies giving very bad backup and only when you decide to replace it, it automatically starts working fine, for some time atleast. Then same thing happens again.
So, I think its problem with some hardware component. Otherwise, flashing from QFIL successfully, would have unbricked the phone.
Click to expand...
Click to collapse
Okey Bro

nk41319 said:
First off all remove battery then insert it again , after this press vol. Up + vol. Down + power on button by doing this your device completely boot recovery which one is now installed with software.
You said previously that your device is on only showning logo , its mean you have 60℅ chance to get your device in working condition.
Bro if you flashed stock kikat firmware then without flashing any software again just simply flash kitkat twrp recovery through adb . After this flash any kitkat rom ( recommended cm 11 by ed300 ) , huree you get your device live.
OR
If you recently flashed stock lolipop then without flashing any software again just simply flash lolipop twrp recovery through adb . After this flash any lolipop based or marshmallow based or naughat based rom , after that any rom from these android version will work , hurreee you got your phone alive but remember dont again directly flash kitkat rom over any lollipop , marshmallow, naughat rom otherwise you will again got bootloop . But you can directly only flash stock kitkat over stock lolipop or stock lolipop over stock kitkat only . I hope you understand what to do :good:
Click to expand...
Click to collapse
Thanks bro... i will try this and let you know !!!

AmythD said:
Im facing the exact same problem as of now...
Managed to boot into recovery somehow and flashed a ROM but then again it went back to bootloop while unlocking the lockscreen
Click to expand...
Click to collapse
yes man gonna try the above solution.. lets c

Note 4 n910c is stuck on efs invalid argument and dm verify failed

Hello everyone, I am so glad that I'm a new part and a new family member to this awesome forum, I would like first to thank all the xda developers for the great job they do, and now I'm going to start talking about my problem with my android phone, first I bought a brand new note 4, I did not know that the n910x one sucks, I bought that phone and I after like a months I started to download and use room because the phone had been so lagy because of Samsung apps I download cm13 then I made a backup to my cm 13 system and data, but the issue is while the phone was backing up it accidentally rebooted and after that I wiped out my android system apps and everything expect the backup I made which didn't even finish, so after that I connected the phone with odin and flashed the stock software after the software was successfully flashed it rebooted and I had waited for like 15 minutes and it was still on Samsung logo after that I tried to go to recovery and it says that please how to fix it I've been depressed I'm really sad I lost hope I don't think I'll ever fix it is there anyway I dint have any efs backup or anything can anyone please help me because i don't have money to buy a new phone I was my phone back even if with no imel number I just want to get rid of samsung logo, I tried flashing and everything I flashed cm11 and all roms end up in bootlop logo
Sent from my SM-N9005 using Tapatalk