Related
Dear All,
As it says in the topic, could someone please guide me on how to update my S4 already rooted to the latest firmware I9505XXUBMGA downloaded from Samsung-updates. I am in UK and this is unbranded phone.
* All I wanted to know is how to use oDin on rooted phone?
* Would it be better to factory reset and restore the data through Titanium Backup?
* Or just carry on flashing through ODin?
* Will my data after flashing the firmware will remain there or it will be erased?
* will this firmware is Rootable?
Thanks for your help and suggestions which is much appreciated :good::good::good:
Hi, the process is fairly easy , open Odin, click the PDA box, locate the firmware, put your phone into download mode, plug your phone in your pc (it should say added) and hit start, after a while your phone will reboot and it should say pass on the top left of Odin. Your phone should now be updated.
All your data should remain on your phone, it's just an update.
I can't tell you if it's rootable since I have the i9500 but I'm sure it is. Just search around.
Sent from my GT-I9500
As you have an I9505 (assumed from the firmware you are trying to flash) then use Mobile ODIN, the paid version is best for this.
You can download the rom, put the tar.md5 file onto your sd card and flash through Mobile ODIN. It will keep root and flash the rom. All data should be left intact unless you tick "wipe cache/data" then you will be stock factory reset but still rooted.
If you run triangle away before you flash the flash count will be reset too....
Hey guys,
I installed the TWRP recovery ad followed the steps as mentioned in that thread but I cannot boot into the recovery nor does any app like Flashify say that I have root access. When I go to download mode it shows that Knox is void but then the volume up + home + power button goes to normal android recovery.
I have Samsung Galaxy S5 G900H.
Any idea where I went wrong and what I can do to fix this? I am sort of new to rooting android.
Use cf-Auto-Root of Chainfire
assasin93 said:
Hey guys,
I installed the TWRP recovery ad followed the steps as mentioned in that thread but I cannot boot into the recovery nor does any app like Flashify say that I have root access. When I go to download mode it shows that Knox is void but then the volume up + home + power button goes to normal android recovery.
I have Samsung Galaxy S5 G900H.
Any idea where I went wrong and what I can do to fix this? I am sort of new to rooting android.
Click to expand...
Click to collapse
Hi,man
At first if you have any bootloop or issues
you must download the latest firmware from samobile http://www.sammobile.com/firmwares/download/51740/G900HXXU1BOG4_G900HOXY1BOG4_SKZ
By using odin flash
& you will repair your device (softbrick)
After that yu can use Cf-Auto-Root http://download.chainfire.eu/402/CF-Root/CF-Auto-Root/CF-Auto-Root-k3g-k3gxx-smg900h.zip
It s good for newbies
Follow all steps of root
Perhaps yu ve to reflash root if not works once
Good luck assasin93!
How to recover after a power failure during booting?
Anyone know how to recover from power failure during booting? Thank you and very much appreciated!
Repair soft brick by odin flashing latest firmware
If i ve understand well your question
in twrp recovery mode yu have restore option
(if yu have an backup) & 3 wipes options :
- You can restore if backup is on
- You can try wipe dalvik after that wipe cache
If all else fails wipe data for installing firmware
What's your twrp version ?
For repair softbrick (bootloop) go on downlooad mode
& flash by odin the latest firmware of g900h from sammobile link.
Hi, I use this thread for my question.
I've got a brand new G900F since my SGS 2 died.. I read here and there that there are some problems to root the new S5' without triggering knox.
What Ive done so far, im coming from the POG7 (german BOE5 with Vodafone branding), flashed the unbranded DBT_BOE5 without problems and tried to downgrade to ANE2 to use towleroot. The flash to ANE2 was successful, but the screen appears to be black, so I cant work with the phone. I blind started the download mode so I could flash back to BOE5. Is there a way to root the newer S5' coming with stock 5.0?
Greetings
So, I've managed to soft brick my t355y, it hangs on the animated Samsung logo.
Since getting it, I updated from 5 to 7.1, flashed TWRP custom recovery and then gained root access using SuperSU successfully and the tablet was in perfect order. Then, I was attempting to eliminate bloatware via Titanium Backup (because not ONE CFW exists for this god damn model, NOTHING), I know for certain I didn't delete anything essential yet Titanium backup froze on 21% deleting the Samsung Internet app. There was no getting it out of that freeze but I could use the rest of the tablet. So, I figured I'd start from scratch and do a clean wipe, I booted into recovery and used the included tools to format the data on the tablet, being the idiot that I am I'm not sure, but I assume that was what caused the soft brick. Nothing that I do within TWRP will allow it to boot properly.
Now I've got no idea what to do, I've managed to track down a version of 7.1.1 under the carrier in my country and it fits the model number exactly. Though I'm getting mixed messages on the process for this, if I'm using Odin do I simply need to load the .tar.md5 into Odin and just go for it, or do I require a PIT file? If I do require a PIT file, it doesn't exist for the model I have, I've scoured everywhere I can think to look.
Any help in getting through this would be heavily appreciated. Thanks.
you must have deleted a crucial system app when you were getting all the bloatware out of the system..
If you still have the rom 7.1 try to flash that via odin in download mode. You will lose TWRP and root + everything else if you do a clean wipe.
Sent from my [device_name] using XDA-Developers Legacy app
It always amazes me that people won't take the trouble of a few minutes to create a backup with TWRP before messing with the OS. :silly:
However, are prepared to spend countless frustrating hours trying to resurrect their device.
My advice is to just flash the firmware you have with ODIN as is.
Leave all options at default and put the md5 in AP.
can you please post the twrp custom recovery flash file and , supersu file .
can you please post twrp and super su files please .
Any help in getting through this would be heavily appreciated. Thanks.
Zedism said:
So, I've managed to soft brick my t355y, it hangs on the animated Samsung logo.
Since getting it, I updated from 5 to 7.1, flashed TWRP custom recovery and then gained root access using SuperSU successfully and the tablet was in perfect order. Then, I was attempting to eliminate bloatware via Titanium Backup (because not ONE CFW exists for this god damn model, NOTHING), I know for certain I didn't delete anything essential yet Titanium backup froze on 21% deleting the Samsung Internet app. There was no getting it out of that freeze but I could use the rest of the tablet. So, I figured I'd start from scratch and do a clean wipe, I booted into recovery and used the included tools to format the data on the tablet, being the idiot that I am I'm not sure, but I assume that was what caused the soft brick. Nothing that I do within TWRP will allow it to boot properly.
Now I've got no idea what to do, I've managed to track down a version of 7.1.1 under the carrier in my country and it fits the model number exactly. Though I'm getting mixed messages on the process for this, if I'm using Odin do I simply need to load the .tar.md5 into Odin and just go for it, or do I require a PIT file? If I do require a PIT file, it doesn't exist for the model I have, I've scoured everywhere I can think to look.
Any help in getting through this would be heavily appreciated. Thanks.
Click to expand...
Click to collapse
You can always use Kies for getting stock rom or updato . com (can't paste links). Samsung Smart Switch got rid of the device initialization, kind of sucks.
Soft bricked
I have also gotten soft bricked but have gotten out the way. First, you need a Samsung galaxy tab a tar file firmware. You can install it from the internet.If you have ADB use this command adb reboot bootloader and then your Samsung galaxy tab a will be on the download mode and then flash the firmware with Odin and that's how I unsoftbricked my Samsung galaxy tab a. You still need to do the updates tho.
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.
rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.
It's my pleasure to help you if you still facing this problem
zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?
It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.
Hi there, I have been using S7 Edge SM-G935F happily and a couple of days back installed the BlackDiamond NFE and was not able to connect to the cellular network or make any calls or use mobile data
Again I tried the OneUI and Pixel Experience and all seem to end up with the same problem.
Inserted the SIM into another mobile and there is no problem with the network or the SIM.
Please help me fix the problem, tell me what do I need to flash/install/update.
I guess you need to reflash the stock rom with Odin.
Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers
Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers
So, after downloading various firmware from SamMobile and all versions of Odin, I was able to flash the latest BTU firmware and with Odin v3.14.
The problem is still persistent, the same Three SIM when inserted into another mobile and in the same location gives a signal strength of -63db which is very strong.
But, when inserted back into the freshly flashed S7 Edge hardly gets any signal -113db, which is very weak
I ran out of options and looking forward for some help in getting back those signal bars back in my mobile.
Hoping someone in here knows how to solve this weird issue
Just came across such issue with another guy yesterday.. your efs got corrupted/damaged. You have to fix it either using hardware box (a local repairer shop can do)
Or
Try following this thread to word.. should give you signals back (tested by me) ..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Note : flashing firmwares again after fixing by above method would negate the fix. Above fix needs to be done after every firmware flash to get signals..
Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only
Siddu_j143 said:
Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only
Click to expand...
Click to collapse
Did you flashed csc or home_csc?
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
Sent from my hero2lte using XDA Labs
Did you flashed csc or home_csc?
A) Always a CSC and not HOME_CSC.
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
A) Installing the firmware as I write this.
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
A) Will do and update you
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
A) Will do
Sent from my hero2lte using XDA Labs
Hi @shan22, thanks for all your replies and time to help me out. Here is what happened. I flashed the DBT firmware which was a success and after the flashing, it started into its default recovery where it said "No command" with a dead droid symbol and died and went into the loop I forcefully started the phone into download mode, installed the TWRP, restarted into TWRP, formatted the data and started the phone into download mode, flashed the BTU firmware which also succeded and went into the same loop of "No Command". This happened a couple of times and none of the DBT or BTU firmware did actually start the system. I had no choice and finally had to install the "PixelExperience_Plus_hero2lte" custom ROM zip from TWRP which worked previously and is working now. All of this effort and it's still down to the same problem, no signal at any time
Sadly, the bootloader version is 8
Yeah version 8 .. no dice. Weird, does your phone gives any error when it gives dead android ?
Looks like you get a dm-verity error upon flashing stock firmware..
Trying flashing no verity zips in twrp after flashing stock rom..
So, your efs is indeed corrupted.
Retry all the procedure..
>flash dbt in odin using csc (not home csc)
>flash twrp in odin and boot into twrp directly without booting into phone
>flash no verity zip, then flash latest magisk zip in twp
>boot into phone
>go in download mode again and flash btu in odin using csc (not home_csc)
>flash twrp in odin and boot into twrp directly without booting phone
>flash no verity and magisk in twrp
>boot into phone and see signals..
If no signals, then from this point refer to my above posts where i gave a link of box like software to fix signals. Follow that thread to word and you should get better signals.
That's the thread : https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my hero2lte using XDA Labs
A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.
Siddu_j143 said:
A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.
Click to expand...
Click to collapse
Oof lol
You need to format data under wipe options and type yes after booting first time into twrp and then flash no verity zip and then magisk ..
This is a standard root procedure for root on android oreo, I hoped you would know that ..
Do this and re-follow all the steps I mentioned above ..
And please read forums thoroughly before messing with your phones.
Sent from my hero2lte using XDA Labs
Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:
Siddu_j143 said:
Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:
Click to expand...
Click to collapse
You won't get fully normal signals but will get atleast better or almost good signals. Since your factory efs is corrupted, it can only be restored via efs backup and combination rom with matching binary version. Since you don't have efs backup and latest combination roms aren't available, so there isn't a permanent solution for this.
Sent from my hero2lte using XDA Labs
Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:
Siddu_j143 said:
Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:
Click to expand...
Click to collapse
Sad to hear that, that's why I don't use fully ported/custom roms because they always have a tendency to f*** up your efs, specially if you mess with wrong options or don't know what you're doing.
Even with an efs backup(from when your phone was working correctly), you still need combination rom
And not even paid websites have version 7 and 8 binary combination roms .. the only thing I came across on a lesser known website was that name of version 7 combination rom was : G935FXXU7ATB1 . Maybe it will be of some help to anyone here
Sent from my hero2lte using XDA Labs