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.
I got the Tab Pro 12.2 a couple of weeks ago (refurb). It worked flawlessly, so I decided to root it, etc. It no longer works.
Two points.
(BOOT 1) - On a 'normal' boot it will get past the blue swirl with about 1 second of audio, then stops with "SAMSUNG" on the screen.
(BOOT 2) - On a Pwr on/Vol- (hard) boot, it will come up with "press vol +)" at which time it boots to ODIN. No way can I get it to boot to TWRP (see following)
Conditions: Windows 10 Tech Preview, Dell XPS 18 (USB 2 and 3), latest USB driver from Samsung, ODIN 3.10, Kies 3. The tablet connects with ODIN.
I loaded CF-Auto-Root (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). Success, BUT tablet reboots to BOOT 1, above.
I loaded "openrecovery-twrp-2.8.5.0-v2wifixx.img.tar". Success, BUT reboots to BOOT1 above.
If I do a "hard" boot, I'm back with ODIN. TWRP won't boot. Tried the same with CWM (getting stupid here). Boots to ODIN. Basically, I can't boot into any recovery program.
Tried loading "SM-T900_XAR_1_20140508111550_703bt27ewy.tar". Again, loads but no joy.
Loaded the original ROM from SamMoblie. Again, no dice.
Am I screwed or what? Please help if you can. Thanks.
-- CatHerder12
Try a different ODIN version.
I've come up with something similar in the past.
ODIN reports OK but nothing is really written to the Tab.
guanellaluigi said:
Try a different ODIN version.
I've come up with something similar in the past.
ODIN reports OK but nothing is really written to the Tab.
Click to expand...
Click to collapse
Thanks for the reply. I have tried a few versions of ODIN. One or two of the older ones didn't work at all.. Currently using 3.10.6. Maybe I'll go back and retry a couple.
With tablet in download mode: I tried Kies and it reported the tablet as an unrecognized device. Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks
CatHerder12 said:
Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks
Click to expand...
Click to collapse
Plug in the Tab and check in your computer device manager list that the device shows connected to the USB port and the drive installed is Samsung Android ADB Interface, if it isn't change it to this driver.
Make sure you are using the original USB cable and its plugged directly into the PC and not via any Hubs.
CatHerder12 said:
Thanks for the reply. I have tried a few versions of ODIN. One or two of the older ones didn't work at all.. Currently using 3.10.6. Maybe I'll go back and retry a couple.
With tablet in download mode: I tried Kies and it reported the tablet as an unrecognized device. Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.
jvilla785 said:
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.
Click to expand...
Click to collapse
Hi guys
, i had the same problem, but i follow ur steps and it worked. the only diference i installed the twrp-2.8.5.0-v1awifi.img.tar and it stuck, i have the SM-T900, v2wifi and it is working.
All the other didint stuck
thanks
jvilla785 said:
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.
Click to expand...
Click to collapse
Thanks for the advice. I couldn't find a download link for the 2.8.0.0 but found openrecovery-twrp-v1a3gxx.img.tar. I'm guessing it's for a 3G version but it works. I used ODIN3 v3.10.6.exe on the PC. So far, I have twrp and the stock ROM running and everything works nicely. I still haven't managed to root it. Keeps getting stuck on cache. Can it be rooted after twrp has been loaded?
I actually may try to use the tablet for a while instead of continually poking and reloading it.
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
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
Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you very much for you help.
dr.rokr said:
Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you
Click to expand...
Click to collapse
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tried the 3 USB ports in the laptop
What else can be happening?
Thank you very much!
dr.rokr said:
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tryed the 3 USB ports in the laptop
What else can be happening?
Thank you very much!
Click to expand...
Click to collapse
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.
bruno2030 said:
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.
Click to expand...
Click to collapse
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
go to the recovery.
connect to the PC.
open odin.
click on "reboot to bootloader"
It should go to to download mode.
what does your download mode screen say?
When I was doing this process I tried reflashing the latest rom but that didn't solve my boot loop issue.
So I flashed an older version of the rom.
Make sure the version you download is compatible with your phone.
You have G9650ZHU9FUG2 so only roms with 9 will work.
I flashed that old version and it didn't work, phone still stuck.
Then I flashed the latest one again and then my phone worked.
I used odin from the link you posted.
Odin3 v3.13.1
actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it
dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
TormentedHeart said:
actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it
Click to expand...
Click to collapse
Hi! I have uninstalled everything and then install the drivers again without luck
TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! Today I have successfully flashed the exact firmware that the phone had ( there is no newer) using a different laptop (it's true if the problem persist with Odin, use another laptop)
I got success message, at the very first time, and when the phone reboot, nothing , stuck as it was before, so I erased cache partition and no luck, still stuck on reboot, I have also tried repair apps , and reboot sistem now, what else should I do?
Thank you very much!
Hi! I want the community to know that using the APK adb app for Samsung it's a bad idea, after successfuly flashing the firmware and performing a factory reset several times the phone remain stucked, I downloaded about 10 different firmwares and flash them all times without an error, and the phone was bricked and stuck in boot. So I took it to the official service and nothing, still the same, then I found an external service that flash the device with a little box that they said they paid in advance for credits for using that box, it took them one full week to revive the phone, also they had to flash it several times. In conclusion, if you buy Samsung, stick with the garbage apps the throw, if you mess with the system in some way as the official technician said, the phone will be nearly unrecoverable for privacy benefits for the user. Thank you very much for the help to the community!