Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
isssaputra said:
Hello, I just bought S7 (second-hand) last week and wondering to root it out.
My question is, is there any laggy or issue or something that feels 'downgraded' after the root? Because I've seen many people complain about after their phones being rooted.
Thanks in advance!
Click to expand...
Click to collapse
If you trip Knox you won't be able to use Secure folder, Samsung Pay or Samsung Health and that's it.
You won't get any other problems.
Hi!
Yesterday I rooted my S7 (SM-G930F) with CF-Auto Root (from desktop.firmware.mobi)
Unfortunately, I didn't notice that the Kernel was 7.0, while my S7 was already on 8.0.
Now I have a lot of apps (including camera, youtube, lightning launcher, opera, ...) that either crash directly after starting or freeze shortly after they are opened.
Do you know if/how it is possible to get a working system again?
Thank you in advance (and forgive my bad english),
Andi
If you download 8.0 firmware files (either use samfirmtool, or go to sammobile.com or updato.com) and flash using Odin, use AP, BL, CP and HOME_CSC instead of normal CSC (HOME_CSC keeps data, normal CSC wipes data), it should set your kernel and everything back to 8.0 without causing any data loss.
Flash guide here https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
However I'm pretty sure doing this will reset your root, your best bet is to flash TWRP and root using Magisk as its the more modern and updated root method.
Hi @Beanvee7,
thanks for your info!
In the meantime, I have installed TWRP, and downloaded the firmware from sammobile, but failed with magisk (since it is one of the apps that keep on crashing right after startup).
So, I'll have to install it the old fashioned way with odin tomorrow.
But I have one more question left: Is there an advantage of using CSC vs. HOME_CSC? Since I have backups of all my data, and rooting wiped data anyways (the system was encrypted), a wipe does not inflict any (addiditional) damage.
Thanks,
Andi
CSC is probably preferred because it means a clean wipe, so you won't be carrying across any potentially broken apps/system files.
If you have backups then I'd recommend CSC.
Hi!
I am still stuck: No matter what type of installation I choose, it fails:
Odin reports success, but doesn't install the new firmware (neither 7.0 nor 8.0, from updato or sammobile).
<ID:0/006> modem_debug.bin
<ID:0/006> cache.img.lz4
<ID:0/006> hidden.img.lz4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Click to expand...
Click to collapse
The "Now Writing.. Please wait about 2 minutes"-part only takes one second or so.
Installing via TWRP reports "Invalid zip file format".
ROM Toolbox Pro also reports "Invalid ZIP file"
Magisk still crashes upon startup.
Do you have any ideas left?
Related
Hey folks,
I was trying to root my never before rooted s6 today (64 gb 920 I) using the uni-kernel method using odin for 5.1.1. I put the kernel into AP, and it failed after some seconds thus resulting in the blue screen which says "error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software."
I tried that and smart switch didn't recognise my device (maybe because USB debugging wasn't on).
Thus I downloaded a stock recovery for my device and I thought I would flash it via ODI. Things go well and the progress bar is 3/4th of the way through on my device and it suddenly says FAIL (shown below). I've tried with ODIN 3.10.6 and with 3.10.7 with the same results
<ID:0/003>Get PIT for Mapping
<ID:0/003> Firmware update Start!!
<ID:0/003> cm.bin <ID:0/003>
sboot.bin
<ID:0/003>NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) Operation failed.
<OSM> All threads completed. (succeed 0/failed 1)
What's unusual about this (to the best of my knowledge through forum search. I could be wrong and this could be common. If so I apologise) is that I've seen help threads about Odin failing at hidden.img or NAND Write Start but not during system.img. Does the fact that it's failed during system.img in particular tell us something?
Also, I can't access stock recovery, just the download section.
No clue why it's doing this. I would appreciate any help possible.
Thanks so much in advance. This means a lot.
Your current phone's firmware CSC should be same or within the region CSC of your downloaded firmware.
Hidden.img do have different partition size per Country/region. If you flash a not supported firmware, it will fail.
I.e., if your from France, just download the France firmware.so that you wont need to flash a pit file for your phone.
You can Search here at forum with keyword galaxy s6 pit file.
Or probably, your pc <> phone connection is unstable. Be sure it is connected properly, the usb cable should be in good performance etc.
I had the same happening. Don't sweat it really, no need to use that Smart Switch thing, Odin should still see the phone anyway, so just go ahead and flash a different image from Sammobile, possibly use one for your country and you'll be good.
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).
Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.
Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)
Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?
Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?
UPDATE: I wasn't able to fix it and ended up having to send it in to Samsung. There was something wrong with the motherboard and they fixed it pretty quickly. It only took about a week to get it back.
Phone: Samsung Galaxy S7
Phone Model: SM-G930W8
Carrier: Sasktel (Canada)
My girlfriend's phone started spontaneously bootlooping this morning. The timing seems to correspond with the release of Nougat in our area. My assumption is that the update got rolled out to her phone and has somehow softbricked it.
I tried booting into recovery and selecting "Wipe data/factory reset" but I keep on getting the following message:
-- Wiping data. . .
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset Done. . .
Data wipe failed.
-- Applying Multi-CSC. . .
Applied the CSC-code : BWA
Successfully applied multi-CSC
-- Set Factory Reset done. . .
Successfully verify for dmverity hash tree
-- Start Factory Reset. . .
-- Wiping Data. . .
Formatting /data. . .
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done. . .
Data wipe failed.
Click to expand...
Click to collapse
I've tried choosing "Wipe cache partition" but that doesn't seem to have an effect on the issue.
Next I tried to use Odin to flash the firmware from here
I tried flashing G930W8VLU2BQB6 (Android 7.0) as well as G930W8VLU2APK3 (Android 6.0.1) via Odin v3.11. Here is the log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After the phone restarts it goes straight to the Android Recovery screen. If I choose the "Reboot now" option the phone will boot to a black screen. I'm able to adjust volume and the soft keys light up but I can't do anything but click the reset button at the bottom. The black screen message says:
Device storage corrupt
The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
Click to expand...
Click to collapse
Then there's a button at the bottom that says "RESET". After rebooting the phone goes to a blue screen with an android logo and the phone just says "Erasing". After a few minutes I get an error screen of a dead Android guy on a blue background with a big yellow triangle with an exclamation mark above him. Then the phone reboots and I just get the same error message from above that says
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
E: Data wipe failed
Click to expand...
Click to collapse
I've also tried installing TWRP via Odin but I get the following message on the phone:
Custom Binary(RECOVERY) Blocked by FRP Lock
Click to expand...
Click to collapse
Here is the log from Odin:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
So yeah, I'm completely stumped and any help would be greatly appreciated.
BloodAudible said:
Phone: Samsung Galaxy S7
Phone Model: SM-G930W8
Carrier: Sasktel (Canada)
My girlfriend's phone started spontaneously bootlooping this morning. The timing seems to correspond with the release of Nougat in our area. My assumption is that the update got rolled out to her phone and has somehow softbricked it.
I tried booting into recovery and selecting "Wipe data/factory reset" but I keep on getting the following message:
I've tried choosing "Wipe cache partition" but that doesn't seem to have an effect on the issue.
So yeah, I'm completely stumped and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi mate
When you flashed with odin what did you use CSC or home_csc file?
CSC will factory reset and should and should clean all your partitions, if you flash a differnt CSC than the one you have you may have to check re-partition option under PIT (odin) , check here
Factory reset before you flash...
MAX 404 said:
Hi mate
When you flashed with odin what did you use CSC or home_csc file?
CSC will factory reset and should and should clean all your partitions, if you flash a differnt CSC than the one you have you may have to check re-partition option under PIT (odin) , check here
Factory reset before you flash...
Click to expand...
Click to collapse
I tried using both CSC and home_csc but the result is the same. I've tried checking re-partition under options as well. I'm not sure what you meant by PIT.
Factory reset doesn't work as per my original error.
try to flash 6.0.1 with pit file and make repartition in odin
AntonPres said:
try to flash 6.0.1 with pit file and make repartition in odin
Click to expand...
Click to collapse
Will try this once the (very slow) download finishes. Are PIT files specific to versions of Android or is it just per model? I found a PIT file here
BloodAudible said:
I tried using both CSC and home_csc but the result is the same. I've tried checking re-partition under options as well. I'm not sure what you meant by PIT.
Factory reset doesn't work as per my original error.
Click to expand...
Click to collapse
AntonPres said:
There is only one pit for g930w8 model, so no need to worry about csc version. If you need fast download link for firmware (google drive link) you can check here: https://simunlockremote.com/galaxy-s-series-firmware/
Click to expand...
Click to collapse
Hi mate
PIT = Partition Information Table , it has the information need to format all partition , CSC file contains the right partition
yes, but as you can see on pit list you can notice that pit files are for specific csc
AntonPres said:
yes, but as you can see on pit list you can notice that pit files are for specific csc
Click to expand...
Click to collapse
That is right , as I said the CSC has the right PIT table also what is said in the link i posted
Same information different words
6. Installing another country CSC or a network CSC will usually need the system partition size changing.
For this select PIT and this setting
If you are installing a multi csc firmware, and your existing CSC is in that firmware, then DO NOT select Re-partition.
You can check if your firmware is multi-csc by installing this app:
AntonPres said:
There is only one pit for g930w8 model, so no need to worry about csc version. If you need fast download link for firmware (google drive link) you can check here: https://simunlockremote.com/galaxy-s-series-firmware/
Click to expand...
Click to collapse
Thanks for the link. Finding links for these firmwares is brutal.
I downloaded this one and flashed it but I'm still stuck in the same loop. It always ends up on the blue screen that says "installing system update" then it will change to "Erasing" before ending up with the dead android and exclamation point. And then it boots to Recovery and says Data wipe failed. Any other ideas? Recovery does say Android version 6.0.1 again, but same issue as before.
If flash didn't helped your phone might have motherboard issues
AntonPres said:
If flash didn't helped your phone might have motherboard issues
Click to expand...
Click to collapse
I've asked for help in a few places and everyone seems to come to that conclusion. What a bummer. She only got the phone back in December.
Many s7 models have been reported with motherboard issues, looks like samsung have made some mistakes
I have a sim unlocked AT&T Galaxy S8 Active (SM-G892A) that I've had number-ported over to T-Mobile for a month or so now.
as it has firmware G892AUCS2BRD4 on it now I wasn't able to update it to T-Mobile's firmware as they WERE on Bootloader V1.
Well today on TMO web site I saw they now have G892USQU2BRE3 out and I was trying to use a modded Odin 3.13.1 to update it.
I previously used this Odin to flash two S7's from AT&T firmware to T-Mobile with no issues so I thought Odin was okay
When I attempted to do this on my S8 Active I get the following:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4306 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I re-downloaded the firmware using SAM-FIRM to ensure it was Legit and got same error.
What am I missing here?
I think I even tried to select Re-partition in odin once (tired and went thru a lot of retries tonight).
Do I need a Super-Special Odin for this newer firmware?
Is it AT&T's darned bootloader causing issues?
Thans in Advance
Dave in Tampa
eplerd said:
I have a sim unlocked AT&T Galaxy S8 Active (SM-G892A) that I've had number-ported over to T-Mobile for a month or so now.
as it has firmware G892AUCS2BRD4 on it now I wasn't able to update it to T-Mobile's firmware as they WERE on Bootloader V1.
Well today on TMO web site I saw they now have G892USQU2BRE3 out and I was trying to use a modded Odin 3.13.1 to update it.
I previously used this Odin to flash two S7's from AT&T firmware to T-Mobile with no issues so I thought Odin was okay
When I attempted to do this on my S8 Active I get the following:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4306 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I re-downloaded the firmware using SAM-FIRM to ensure it was Legit and got same error.
What am I missing here?
I think I even tried to select Re-partition in odin once (tired and went thru a lot of retries tonight).
Do I need a Super-Special Odin for this newer firmware?
Is it AT&T's darned bootloader causing issues?
Thans in Advance
Dave in Tampa
Click to expand...
Click to collapse
Im getting the same error trying to load a custom rom from PartyCyborgROM over G892USQU2BRE3. I had to revert back to the exact stock rom. If you find anything let me know.
pwoolston said:
Im getting the same error trying to load a custom rom from PartyCyborgROM over G892USQU2BRE3. I had to revert back to the exact stock rom. If you find anything let me know.
Click to expand...
Click to collapse
RATS - saw the reply and got excited thinking someone had a fix :crying:
Still Hopeful...
CF-Root
eplerd said:
RATS - saw the reply and got excited thinking someone had a fix :crying:
Still Hopeful...
Click to expand...
Click to collapse
I am going to try CF-Auto-Root for Nougat to see if it works on Oreo Cookie. It's worth a try I guess.
pwoolston said:
I am going to try CF-Auto-Root for Nougat to see if it works on Oreo Cookie. It's worth a try I guess.
Click to expand...
Click to collapse
Yeah - I don't wanna root my phone - no need, just want AT&T Bloatware that's useless now gone, and T-Mobile apps on my cell - like I did for friends S7's
Has ANYBODY done this?
I really NEED to get this done as I'm missing phone calls and can't afford a new cell now.
Sure wish I had bought a cheaper S7 as converting it to a T-mobile model was easy on my friends 2 phones.
I'm now wondering IS the S8 active the same across cell vendors (T-mobile, ATT, Sprint, etc) like the S7 is??
I need some troubleshoot tinkering
I have received a Note 10.1 (GT-N8020) from a friend who would appreciate if I could salvage pictures and documents that was on this tablet, and let us not debate his backup options.
Problem with the tablet is it wont boot properly.
It just hangs on the Samsung animation.
As first troubleshoot step my thought was to boot into Recovery and wipe cache and dalvik, just to get it booting. But I simply cannot boot into Recovery. I can only get to ODIN mode.
After several attempts giving up on Recovery, my plan was to flash a new Recovery onto tablet by using ODIN mode, however all attempts both with several different version of ODIN and different version of TWRP fails to be flashed.
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So here I am, feeling stuck.
Either I am thinking there is a defect with the NAND chip, why the tablet must have failed in first place, however I can also find some articles claiming some of Samsung's tablets does not have a Recovery mode/partition, is this true for this model?
I have not reflashed entire tablet, since I need access to whatever data there must be on the tablet.
I also found description on sammobile explaining how to re-install ROM while preserving apps and data, but they keep mentioning ROMs based on 5 files (AP, BL, CP, CSC, HOME_CSC), while I can only find ROMs based on single files (AP)
Link to article (see step 2)
https://www.sammobile.com/samsung/galaxy-note-101/firmware/GT-N8020/CNX/download/N8020XXUDOH1/55623/
Anyone know where I can download such ROM based on 5 files (Samsung official ROM)
Suggestions for any other methods I can try to get the data out of tablet?
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
JJEgan said:
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
Click to expand...
Click to collapse
Philz Recovery tried to flash and fails too
Recover data try ADB .
JJEgan said:
Recover data try ADB .
Click to expand...
Click to collapse
IIRC would that not require USB debugging enabled (which I cannot since it will not boot) and the Android in a running state?
Thanks to the SamFirm tool I managed to find some ROMs configured with CSC_HOME. On first shot it failed to flash these ROMs too. But I will try some more tinkering
I guess your eMMC is locked.
So the only possible solution would be to desolder it and read the data directly out of it.
Whereas the OP gives a link to an "article" at sammobile, that page has since changed and no longer gives any useful instruction for re-flashing while preserving apps and data. However, I believe that the original "step 2" of that page referred to was : "2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data."
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
JJEgan said:
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
Click to expand...
Click to collapse
Sure, there's a good chance that the original tablet has since become e-waste, however, there is also some chance that it's sitting in his friend's drawer in the slim hope of a resolution.
However, my clarification about "step 2" is for the benefit of other readers of this thread, since the OP will already know this information.
My own GT-N8020 tablet has the exact same problem. I was able to overcome the flashing difficulty by using the Prince Comsy patched version of Odin 3.12.3 (which disregards spurious USB communications errors that tend to occur).
However, re-flashing without the CSC portion of the firmware doesn't resolve the problem. I can't include the CSC portion as this will clear the data that I need to recover, and I haven't yet been able to find a HOME_CSC alternative.
Joe.