Related
Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.
Private Message UpInTheAir and see what he thinks.
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.
eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.
I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....
And make a Nandroid first this time
Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?
pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))
TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.
My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.
Hi All,
Sorry for my English, it's not my language.
I need your help because I think I have bricked my Note 7 after trying to install the last Hydra rom 1.3.5.
I explain you the situation:
I have installed custom TWRP => it was good
Then I have rooted with superU => it was good
Then I have tried to install hydra rom => the installation was OK
The phone reboot at the end of installation => phone stay on start screen "Hydra rom" and reboot (loop infinite)
I cannot power OFF the phone.
I cannot go to the recovery menu.
I can only go to the download mode.
So I have tried to re-install TWRP with ODIN but it was not working. Ondin detects my phone and when I click on start, I have the message "Fail" on ODIN and the phone reboot.
Do you have any ideas to help me?
Thanks.
Note 7 Problem - please help if you can, please
Hello
I am newbie here with no proper experience [ I flashed mobile with success once but it was years ago with NOKIA e90!]
I have Note 7 exynos UK VODAFONE and I did flashed it with older OEM firmware [ to bring it back to 100% battery], I downloaded from sammobile than recent one on my mobile [ limited 60% battery]
I unchecked re-partition
I used AP file there
all went fine with ODIN v3.11.1 all pass !
but once mobile started I have big message on my screen which does not disappear [ see attached photo]
unfortunately, the process
com.android.phone stopped
I can click/press OK on screen below that message, but it reappears again and again
I tried to flash it again but now ODIN says fail and something about PIT
I would appreciate some help or tell me what steps I should take [ apart of surrendering phone to place I bought it from!!!]
regards
M.
What I did to make this work:
1 install TWRP
2 whipe format data "yes" x3
3 advanced format everything except external storage
4 reboot to download mode
5 open Odin on pc flash BL/CP provided in original Post of HydraRom
6 install HydraRom via TWRP
7 follow direction installation process
8 wait 5 mins boom!
Never fails for me.
I did that. I have already did that several time before. But I think I have understood the problem. My BL file is corrupt (may be during the download from the server)!
So I think the boot loader not working correctly! I have tried to reload one but without success. Directly Odin write "FAIL"...
Able to access Download mode only after Hydra flash. Solution?
Did this issue ever get a solution? I am having the same issue. I can enter into download mode only after the attempted hydra flash. Now it's stuck on "Hydra N7" boot screen. I had N930F flashed and running with twrp. When I attempted hydra I believe that the full rom did not flash, only 40 MB or so. To make matters worse I can't find where I jotted down my baseband, etc. It was originally N930X (live demo model). Now I get fails in odin. What can I do to remedy my situation. I read that I should flash BPH6 base files, but here it says AGO or AG2 BL. Which is it? How do I wipe the cache and data since I can only access Odin mode? I believe my BL is corrupted. Please help. I was going to trade my Note 7 in but my imei is all zeros and the boot loop. I'm not sure that they will refund or exchange in this condition. Although, they should since I doubt Samsung wants the liability of having these devices out there. Any thoughts on the matter?
Any insight and guidance is greatly appreciated!
Grace Downed in Denver
https://forum.xda-developers.com/note-7/help/note-7-error-t3562629
i have the same issue.. hoping someone would help us.
I recently rooted my J7 Prime and installed Enigma ROM V1.5, and it worked. Due to some reasons, and pretty much the app incompatibility, force-closing and a bit of heating issues I tried to revert back to Stock Firmware.
So I downloaded the stock firmware from SamMobile:
"This firmware has version number PDA G610FXXU1AQC2 and CSC G610FODI1APL1. The operating system of this firmware is Android 6.0.1, with build date Tue, 14 Mar 2017 12:34:47 +0000. Security patch date is 2017-03-01, with changelist 10912764.
Model SM-G610F
Model name Galaxy J7 Prime
Country India
Version Android 6.0.1
Changelist 10912764
Build date Tue, 14 Mar 2017 12:34:47 +0000
Security Patch Level 2017-03-01
Product code INS
PDA G610FXXU1AQC2
CSC G610FODI1APL1 "
Then I flashed the AP file through Odin v3.11 and it worked well until 'system.img' was flashed. And then the 'userdata.img' started flashing and FAILED.
I disconnected my phone and tried to boot into recovery and the message "an error has occurred while updating the device software use the emergency recovery function".
So I reflashed my stock recovery with 'Auto-Reboot' checked and the device rebooted normally.
Then the weird part happened, network connectivity. It has issue connecting to Google Servers so I can't log in. I used wi-fi and set it up somehow. Then I go to my network setting and see never-seen-before network configuration. I am using Airtel India so I created a custom configuration and applied it. Then I went to the 'About Device' panel and instead of 'Galaxy J7 Prime' it shows the name as 'Galaxy On Nxt'.
Here's what I did next.
I flashed TWRP 3.1 and wiped the system and all the data. Then reflashed the Stock Firmware downloaded from another website. Same. Fails at 'userdata.img'. Reflashed stock recovery, did factory reset. Same thing, shows Galaxy On Nxt and weird network configurations.
Did a 3rd time with a stock firmware file from one more website. Same results.
Now, my device works good. But the problem is heating issues and a little bit of lag. Unable to download apps from Play Store. Software update says 'Processing Failed'. Binary says 'Custom' and so does System.
Tried 'Root Away', but it didn't work at all, neither did it reset the flash counter nor the 'custom' status and binary.
P.S. I read about this 'Re-Partitioning' and 'NAND Erase All' in a Galaxy S3 thread but I don't want to jump to conclusions right now. So just asking if it could work out in my case.
And I bought this phone in January 2017 and it was updated to the latest firmware over OTA.
I'd be grateful if you could help.
Thank you.
Edit: Found the problem. In the first three flashes I tried to flash updated versions of the same Firmware, so, it failed. What I did was, match the baseband and software version and download the same. Flashed it with the CP and CSC files. Voila! Done. Then I updated to the latest version, mentioned above, QC2 from QB1 through OTA.
I feel kinda dumb.
Please note that I had to wipe the phone first through TWRP.
Now, I'm back to stock. I'll keep this here in case you miss some things like I did.
Hey Its J7 Prime with nnon removable battery ...... Actually I turned off oem lock and restarted the phone with custom rom ........ and its says custom binary blocked by frp lock and when i unbrick using odin ...... it is also not installing ....... in the download mode also displays the same message ...... please bro help me....:crying::crying::crying::crying:
Did you try flashing the stock recovery? If not, do it. Then flash the stock firmware.
The tricky part is finding the correct firmware. Just take a look at the manufacturing date on the box it came in. Then match the firmware build dates.
If you've done this then reply with a more comprehensive description of your current situation.
Will be glad to help.
-EDIT-
What is the manufacturing date? Check that and look for a firmware with a build date matching that particular month.
But first I'd say just flash the stock recovery with 'Auto-Reboot' checked, it might fix the problem.
Would be better if you get your phone booted up first even if it fails after flashing system.img successfully.
Edit: Just flash the stock recovery with 'auto-reboot' and see if it works. I am right here, so you can reply anytime.
marard said:
I have the same problem, can you please help?, I didnt note down the baseband and software version. And also I am unable to find the corrct firmware on SAMMOBILE.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
I tried rooting the phone and then gave up.
Then the phone was stuck in a reboot loop.
I downloaded the stock firmware from a website and used ODIN.
It worked and the phone booted fine.
Like you, my phone name too changed to Galaxy Nxt instead of J7 Prime.
But all was good till here, no issues with the phone.
Then I didnt turn on, OEM unlock.
Selected Reset to Factory Settings and rebooted the phone.
Now it is stuck with a Samsung logo and the message in red on top left corner, "Custom Binary blocked by FRP lock".
SAMMOBILE is down right now and I cant download any other firmware.
When I try to flash again using ODIN and the firmware I downloaded earlier, it fails.
Can you please give me the steps to resolve the issue?
Can I use the same ROM I downloaded earlier?
The box mentions the model number as, SM-G610FZKOINS.
What baseband and other version I need to match and which one will that be?
The phone is manufactured on April 2017
Please help. Can I WA you?, my number is -----
Click to expand...
Click to collapse
Here's what you should do:
1). Reflash stock recovery.
2). Reflash the same stock ROM.
3). Boot it up.
There might be a problem where it'll show that 'emergency recovery' screen. All you need to do then is to hold 'volume down + power button' and as the screen goes off, keeping power button pressed switch to volume up and also the home button. You must do this switching process in the quarter of a second. It'll show the 'system updating' screen and then it'll fail. But all you have to do is the same thing again, ' hold 'volume down + power button' and as the screen goes off, keeping power button pressed switch to volume up and also the home button', now you should be in the recovery mode. Wipe factory data reset and the phone will boot.
If you're successful, next thing you should do is note down the baseband version. Then look up the correct firmware from SamMobile, with the same baseband number.
Then the process begins again, which I'll explain when you've booted it up.
SM-G160F/DD
Ok...So I got a new ROM from SAMMOBILE, and I think this is the correct one.
It has 5 files:
AP
BL
CP
CSC
HOME_CSC_ODI
As I was not sure of the last one, I changed the name of the zip file to tar and then specified it in PDA and clicked on start.(ODIN)
After NAND Write Start message in ODIN, it says,
Complete(write) operation failed.
Then I unzipped the ROM package into a folder and used ODIN3 now.
Specified the first 4 files and then clicked start.
In this it says re-partition failed.
---------- Post added at 12:38 PM ---------- Previous post was at 12:25 PM ----------
I then selected only the BL file and clicked start. This too failed.
ON the phone it says, "Secure Check Failed(Bootloader)
---------- Post added at 12:43 PM ---------- Previous post was at 12:38 PM ----------
You said:
1). Reflash stock recovery.
2). Reflash the same stock ROM.
3). Boot it up.
How do I perform the first step?
And Same Stock ROM?, meaning the ROM I used after I bought the phone and faced this problem? or the new ROM I just downloaded from SAMMOBILE?
There's a thread here on xda about rooting J7 Prime. Download the folder, should be 50mb (I can't link you because haven't been long here on XDA). There's a stock recovery file SM-G610F. Flash it. Then go into recovery mode and factory data reset. Then power off the phone and boot into download mode. Then flash the old ROM. And get it to boot as the first time, identifying itself as OnNxt. If it works, then check the baseband version and verify with your new ROM package. Enable USB debugging and OEM unlock.
Next get the TWRP3.1 recovery for your phone, also available on XDA. Flash it.
Then boot into recovery and go to 'wipe', click 'format data' and then type 'yes' and click ok.
Then click back and go to advanced wipe. Check 'dalvik', 'cache', 'data', 'system' and if there's nothing to lose or you don't care about that then check 'internal storage' too. Then wipe it.
Power off the phone and go to download mode. Flash the stock recovery.
Now flash the new ROM, if the baseband matches, with AP, CP, CSC. Don't load the BL file, that's the Bootloader and you don't wanna mess with that.
If this is successful you're good as Stock. Everything except 'Knox Secure Folder' works.
Try this. You can still root your device later.
IS it this one?
https://forum.xda-developers.com/android/general/root-samsung-galaxy-j7-prime-cwm-t3516777
I downloaded the 50mb zip file and extracted a file called, "SM-G610F_stock_recovery.tar"
Used ODIN and flashed the above file.
Now, I cant get to the Recovery Mode...earlier I couldnt get here, only DownloadMode was available.
But even after the Factory Reset, it still shows the error on top right, "Custom Binary Blocked by FRP lock".
Then I tried using ODIN3 again and selected, BL,AP,CP,CSC files and tried flashing again, it stopped immediately and on the phone it says,
Secure Check FailedPIT)
In ODIN3, it says, "Re-partition operation failed".
---------- Post added at 02:47 PM ---------- Previous post was at 02:18 PM ----------
I meant, I CAN get to the recovery mode now.
Do you have Google Allo? If you do then I'll message you there. Because social media is still banned here.
You don't have to flash the BL.
And you definitely don't need to Re-Partition.
Just flash stock recovery and reset and flash the AP alone. All you have to do is get the phone to boot so we can determine the baseband.
If you succeed to flash till system.img then it should boot, if it boot-loops then just flash stock-recovery again and reset again but this time reboot. The phone should boot.
I'd tell you to Re-Partition it using the PIT file for it but it's just not gonna work. The PIT fails the secure check.
Did you WA me?
Getting Allo...will update you in a bit..
Yeah! I did. VPN got blocked.
Got Allo...
rorkeanathema said:
Did you try flashing the stock recovery? If not, do it. Then flash the stock firmware.
The tricky part is finding the correct firmware. Just take a look at the manufacturing date on the box it came in. Then match the firmware build dates.
If you've done this then reply with a more comprehensive description of your current situation.
Will be glad to help.
Click to expand...
Click to collapse
+1 thanks for sharing experience. i have a question..i have j7 prime dual sim, the model show on the phone G610F/DS. looking in sammobile there is no G610F/DS.. only G610F (without DS = dual sim maybe).
my question is it same or OK if i flash G610F to my j7 prime dual sim?
an-_-dro said:
+1 thanks for sharing experience. i have a question..i have j7 prime dual sim, the model show on the phone G610F/DS. looking in sammobile there is no G610F/DS.. only G610F (without DS = dual sim maybe).
my question is it same or OK if i flash G610F to my j7 prime dual sim?
Click to expand...
Click to collapse
You only need one with G610F. You see, mine was DD, the guy above, he has ZK, and now you have DS. It all works the same. And they're all dual sim phones.??
rorkeanathema said:
You only need one with G610F. You see, mine was DD, the guy above, he has ZK, and now you have DS. It all works the same. And they're all dual sim phones.
Click to expand...
Click to collapse
aha..i see thanks bro...now i dont have doubts. i need my firmware just precaution because i read your thread. i'll root my J7 shortly..
HELP!!
rorkeanathema said:
You only need one with G610F. You see, mine was DD, the guy above, he has ZK, and now you have DS. It all works the same. And they're all dual sim phones.
Click to expand...
Click to collapse
I have a SM-G610F/DS and the problem is I dont know the baseband of my phone and what firmware to download my dad baught it from Qatar but there is no such country in sammobile there is only Egypt and the UAE (***). If you could help me I would really appriciate it, you'll save my life. I flashed Enigma ROM v3.0 but it seems it has a few bugs on SM-G610F/DS.
Xdev.Cipher said:
I have a SM-G610F/DS and the problem is I dont know the baseband of my phone and what firmware to download my dad baught it from Qatar but there is no such country in sammobile there is only Egypt and the UAE (***). If you could help me I would really appriciate it, you'll save my life. I flashed Enigma ROM v3.0 but it seems it has a few bugs on SM-G610F/DS.
Click to expand...
Click to collapse
What is your mobile carrier? Is the phone a global version or a country specific carrier locked model? The core firmware is always the same, it's the CSC that differs. Rest I cannot say.
j710fn back to stock
I have flashed my j710fn 2016 prime using odin 3.12... latest with twrp 3.0.2-0- j7xelte.tar.md5
now I error messaege : no os installed do you want reboot
I didn't back files , it didn't give chance because my phone wasn't booting any more
so I tried to recorver stock
im stucked I don't know what to do to get my phone back running
please help with steps how to get out of this ,please
best regards
franscome said:
I have flashed my j710fn 2016 prime using odin 3.12... latest with twrp 3.0.2-0- j7xelte.tar.md5
now I error messaege : no os installed do you want reboot
I didn't back files , it didn't give chance because my phone wasn't booting any more
so I tried to recorver stock
im stucked I don't know what to do to get my phone back running
please help with steps how to get out of this ,please
best regards
Click to expand...
Click to collapse
What do you mean by 'J710FN 2016 Prime'?
This is the G610F J7 Prime thread.
Procedure should be same like this. Only the files vary.
Boot into recovery mode.
Go to 'Wipe'
Click 'Format Data'
Type 'Yes' and hit Enter
Then go back
Click 'Advanced Wipe'
Check Dalvik, Data, System, Cache (might wanna check internal sdcard too if you have nothing to lose)
Click Erase
Go to download mode
Connect to PC and flash the stock recovery via Odin
Then flash the stock firmware via Odin
And you're good to go.
You can find the firmware on SamMobile. Make sure you choose the correct firmware.
Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?
Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.
*Update*
I found out what was wrong. The eMMC chip was broken.
Hello. My wife talked me into getting an Unlocked S9. We were thinking that unlocked meant Visible Wireless would work on it. That was not the case. The phone came as model number SM-G960U. Apparently, Visible Wireless requires an SM-G960U1. I read that these are interchangeable, but in using ODIN, to change to an SM-G960U1, the phone no is in a boot loop... although I can get the phone to a download screen and to the 'firmware update screen'. The device will not stay powered off... it just jumps back into an error screen or the boot loop.
I don't know what to do with it anymore. Everything I have tried (probably 30+ hours so far) has failed.
I've been able to use ODIN 3.13.1 3B (Patched) most reliable.
I've downloaded various firmwares, but nothing seems to install.
The furthest I get is when it stops at the vendor.img.ext4.
The instructions I initially followed did not say anything about setting the checkbox in developer mode to 'Allow OEM Change' or something like that. Since I can't boot, I can't go back and set that options (unless there is another way to do so)... I tried doing so through ADB, but executing these commands:
reboot bootloader
fastboot flashing unlock
fastboot oem unlock
fastboot reboot
didn't work because 'reboot bootloader' brings me to the download screen where the fastboot commands don't work.
In the very least, I would like to get the phone up and running again (with the hope of being able to return it). SM-G960U1 would be fine.... or an alternative firmware.
I do not know how to proceed because I don't understand the issues I am having. Any help or suggestions would be greatly appreciated.
Thank you.
Thank you God! I changed back to the computer I abandoned at the start of this effort and used the same drivers, odin, and firmware.... and this time it loaded! Funny thing... it was a 2013 apple mini running bootcamp.
The U1 firmware will suffer issues when trying to be flashed on a "U" device, which is why patched Odin is usually required to flash the U1(unlocked) firmware on a U(locked) device. Patched Odin allows a U1 to be flashed on a U phone as it ignores the errors that pop up on when that process happens. If you have a true U1 device, then patched Odin wouldnt have been necessary as the bootloader already knew that the U1 FW was ok to be flashed, so I believe that if you didnt use patched Odin and was successful, then you have a true U1 device and the previous user just flashed a U FW on it. Glad you got it resolved, but i really believe that the change of pc had very little to do with your success