Hello,
sorry for my bad English.
I am German and have made the text with translator.
My story:
I have here a Samsung S5 and wanted to install this completely normal with Odin TWRP.
Twice I've tried this and always came "FAIL".
Then I tried it with TWRP app. And now my recovery is completely gone.
And it comes error message that I should use "verizon software repair wizard".
I have in my case no German version of the mobile phone or how do I understand this?
How can I reinstall Recovery?
Thank you for help.
1. "Failed" in Odin may have two main reasons:
- Wrong firmware (not for your model);
- Faulty data cable.
So be shure your phone is SM-G900V. You can check it via Download Mode: you will see "Product Name: SM-G900V" in the second line.
Be sure you've downloaded the right firmware (for SM-G900V).
Try another data cable.
2. Stock SM-G900V firmware has no German language, only English, Spanish, Chinese and so on. A custom firmware is needed to have German interface language.
3. It's rather difficult to brick our phone. Usually you can flash stock firmware via Odin and start your investigation from the beginning.
These threads are highly recommended:
One
Two
Related
Hello pros,
I have a S5 (G900F), bought in Germany that has a provider branding from O2 (VIA) I want to get rid off.
After searching and reading many many many threads I wasn't able to find as "safe" solution. There are some threads, where people were able to flash a stock firmware, but it was BTU. Some managed to flash the DBT, but with errors during procedure, workarounds etc.
Since the key to flash from VIA firmware to another seems always to be the correct PIT file and the PIT files also seem to come from this forum I hope to get some professional help to solve my problem. I've already read enough contradictory statements from people who think they might know something, but I'm looking not for assumption.
Here is data from my S5:
AP: G900FXXU1ANG2
CP: G900FXXU1ANG2
CSC: G900FVIA1ANG1
So I have Android 4.4.2 and would like to flash a 5.0 DBT and to keep the KNOX of course.
1. First I wondering why it not working to flash the DBT fw on a VIA S5 with the "original" DBT PIT? If the VIA phones have a different partition layout the PIT for DBT should solve this or not?
2. The most promising solution seems to be use the DBT (it's not state from which to which version the update was done) with special pit version for s5 (also not clear which one was used). When flashing with Odin at the end always a failure message will be displayed. Then disconnect and reconnect the phone and to flash only the PIT after a restart to wipe all. But as mentioned earlier that doesn't sound like a "safe or proven" solution.
Here is the link-> (German) handy-faq.de/forum/galaxy_s5_original_roms_firmware_kies/306126-samsung_galaxy_s5_branding_entfernen_sm_g900f-18.html#post2926313
3. Suppose I use the solution as described in 2. and flash the first 5.0 version (...BNL9) and then perform a update using the build in updated function on my S5 (no Odin, Kies, etc. ) to the second 5.0 version (...BOB7) will the update clean up the possible mess I've done using the procedure above? Or would it be better to use the Kies software on PC to update from 5.0 to 5.0?
I really appreciate competent help on this (and probably many other in the same situation) and no abuse of this thread for other topics .
As step by step guide with a link to PIT file and tool version info (Odin 3.09 etc.) is very welcome.
Cheers!
Flashing the DBT over an o2 branded device is ok. The upcoming error in the end, related to a to small cache.img ext4 partition comes up because of the comparsion by odin of the is and the has to be partition size.
At this stage the DBT rom at the S5 is not installed, it's like a download only. If you now flash the right *.pit as a next step this will adjust the partition size. The installation afterwards will be work and all is on a clean state. Have done this yesterday here in Germany using before o2 branded S5.
Sent from my SM-G900F using XDA Free mobile app
Thank you for the quick reply Endur.
Is there a guide I can follow for the whole procedure (what you did on you phone)? And where can I get the "right" PIT file?
I had some experience flashing a Galaxy S1, so I know this might be tricky and would like to avoid any possible heart attacks during the procedure .
Thanks in advance.
Flash bob7 DBT using Odin (I have used 3.10).
After that you will get the failed message because of wrong partition size.
Unplug USB cable.
Plug USB cable.
Flash *.pit (European for G900F 16GB)
You will get a note now about adjusted partions. The installation of bob7 DBT will start now (you see the green Android spinning). You may wipe cache and data as last step.
Sent from my SM-G900F using XDA Free mobile app
Alright, with mental support of Endur and some courage I just de-branded my phone by updating it from VIA (O2) 4.4.2 (G900FXXU1ANG2) to no branding (DBT) 5.0 (G900FXXU1BOB7). I've used Odin 3.10 and Samsung USB Driver for Mobile Phones 1.5.51.0.
The flashing procedure is basically as described in many other posts, so I don't want to create a copy of a copy. Please take a look for yourself.
Instead I will only add the steps required for O2/VIA de-branding with my experience.
As Endur mentioned the first step with Odin doesn't flash but "copy" the firmware to the phone. Due to different partition layout Odin will show an error. Remove the USB cable and replug it while Odin is still running. Remove the check from "AP" (former PDA) in Odin, select correct PIT, check "Re-Partition" in Odin and press "Start". Now comes the excitement moment. My phone got stack showing Android, powered by Google etc. I had to remove the battery, boot into recovery an wipe data and cache. So it seems to be a must instead of may.
I've used the SM-G900F_pit_16GB.zip (for German / DBT version) from forum.xda-developers.com/showthread.php?t=2737448
Good luck!
Yes, wipe data and cache is a good idea while updating from Android 4.2 up to 5.
There is a lot different for data, Dalvik was changed to ART and much, much more.
I had updated from BTU BNL9 to DBT BOB7 only. The DBT requires the greater partition size for hidden.img while BTU can be flashed without any partition change to a formerly German o2 branded device.
Sent from my SM-G900F using XDA Free mobile app
Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help
Anyone?
No, you can download any one you want.
Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
undersound said:
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
Click to expand...
Click to collapse
1) Yes, of course.
2) No.
3) Don't know what you are talking about.
Odin is used to flash stock roms on Samsung devices. That is the only way.
There are links to guides in the help thread in the Q&A section.
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
jimmyoh said:
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
undersound said:
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
Click to expand...
Click to collapse
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Click to expand...
Click to collapse
That's good to know, thanks. I was trying this with an extended usb cable so it can be the definitely the case.
Will try later today with a direct connection to a backport.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
Click to expand...
Click to collapse
Managed to return to stock firmware, yay!
In case it helps someone else, here are my steps:
1. By dialing *#1234# on a similar phone I checked what ap/cp/csc version I needed
Code:
AP: I9505XXUHOF2
CP: I9505XXUHOF2
CSC: I9505OXAHOF2
2. Downloaded the correct firmware image (http://www.sammobile.com/firmwares/download/50091/I9505XXUHOF2_I9505YHNHOF2_PHN/)
3. Extracted the firmware file
4. Opened Odin v3.10.7
5. Rebooted Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Connected phone and waited until I got a blue sign in Odin
7. Added the firmware file to AP / PDA
8. Made sure re-partition was NOT ticked
9. Clicked the start button
10. Then I got a PASS!
So I guess there can be 2 reasons my first attempt of flashing stock firmware did not worked:
1. The firmware I used the first time was not correct for this phone (http://www.sammobile.com/firmwares/download/64897/I9505XXUPOL1_I9505PHNPOL1_PHN)
I did not know at that time about checking my ap/cp/csc described in Step 1 above so I was just downloading the firmware which seemed the most appropiate according to the country / provider.
What helped me a lot was when I found the explanation of the parts of the version number:
Code:
I9505XXUHOF2
I9505 = phone model
XX = country/region code
UHOH2 = modem
2. The second attempt I followed GDReaper suggestion and I used the usb cable directly on of the backports of my pc so that could have helped as well.
Another thing that was not clear to me at first were the providers code. Or well, they were clear to me that they were abbreviations for telecom providers but I did not bought these phones from a provider so I was not sure which one to pick. After a while I came to discover that I needed PHN which means Unbranded
Code:
---------------------
PHN = unbranded
TNL = Tmobile
VDF = Vodafone
Thanks all for the help
Hi,
I recently purchased a Galaxy Tab 4.0 Lite (SM-T337a). I successfully rooted it using Kingoroot but upon restart the entire operating system seems to be gone. It is an overseas tablet (AT&T) that I got through the classifieds here in Australia.
There was nothing on there so I am not worried about losing data, I just want to be able to restore some form of OS onto it.
I can get into Android System Recovery <3e> and have tried installing the stock firmware through the SD card, but so far nothing has worked. I'm also having trouble getting my PC/Mac to identify it.
Any help would be appreciated.
Thanks!
http://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
download this and make the process
https://www.androidfilehost.com/?fid=529152257862688251
you have to flash the official firmware that you can find in sammobile and flash it whith odin. it should that your device is in download mod : down key home and power bottom on the boot
Look for the stock firmware for your model in this thread or somewhere in SamMobile, the language specified doesn't matter anyway cause you can always change that in setup but make sure that you've got the right one for your tablet. Then flash them using Odin
I wish to root my soft-bricked S5mini.
But have realised that I cannot use djibe89's tutorial without enabling USB debugging in settings (which are currently unavailable).
I've tried to install Kies to reinstall firmware, but get endless connection error, and troubleshooting connection error (i.e. reinstalling Samsung USB driver) doesn't fix it.
It seems like Odin is able to connect to the phone (at least I get ID:COM blue).
Question 1: Does this mean that I can flash fresh firmware/ROM to the phone with Odin?
Like described in this guide by jackeagle (and then enable USB debugging)?
Question 2: How and where do I find the right firmware/ROM?
I have a Danish language SM-G800F phone, but it doesn't seem like Samsung is providing firmware anymore. When I check sites like sammobile.com, there are 3 different version 6.0.1 in mutiple languages (including multiple UK versions) but not Danish one.
Can I use any firmware version (including ROM Unofficial Lineage OS 16 provided in djibe89's Galaxy S5 mini G800F pack)?
Or is there a specific UK/US version that would work with my phone?
I hope someone can help, because my backup phone stopped working a couple of days ago
[Created a new thread under Q&A, Help, and Troubleshooting, because it doesn't really belong here]