Database Users

[Q] Trying to go back from CM12 to Touchwiz

Hi all,
Here's my story. I have a US T-Mobile Galaxy S5. I wanted to try Lollipop as the new Touchwiz wasn't available yet for my device in early April. So hearing that it is very fast I chose CM12 and used their guide for the S5. I had a little trouble (Heimdall didn't work for some reason), but I successfully used Odin to install the custom recovery (TWRP). Then I was able to wipe and install the CM12 nightly image just fine using TWRP.
Since then I realized that my Gear 2 is only partially compatible with CM12. I've yet to find a thread that shows specific steps to get it working well with CM12, only partially, and many have had trouble even getting partial functionality. And now that Lollipop Touchwiz is available for my phone, I'd like to switch to that.
Last weekend I tried just that. I took a second backup of my CM12 build, then restored my backup from touchwiz 4.4. When I booted to it, the phone was severely crippled. The menu bar and navigation drawer were missing, and the home button did not work at all. I performed a factory reset, and it seemed to be working fine again. Next, I tried an OTA update to 5.0. That didn't work: the phone realized it had been tampered with and told me to use Kies. So I installed Kies, and attempted the update there. After some wrestling with it, I finally got the update to 5.0 started. It finished successfully (so it said anyway) but the phone failed to boot up. It was stuck on the Samsung logo screen for quite a long time. There was some blue text about recovery and I was panicking thinking somehow TWRP screwed up my ability to update w/ Kies. I tried rebooting and could not get into recovery or the OS no matter what. I tried Kies' emergency options only to have it not recognize my phone as compatible. So I went to download mode and installed TWRP again using Odin. Then I was able to boot into recovery, and I restored the backup of CM12 I took before I started all this (thank God I did that).
So now I'm back on CM12 with everything working fine, except of course my watch. I did not expect the restore back to Samsung software to be more difficult than going to CM12.
Can anyone see what I did wrong?
I gather I can install a stock rom with Odin. But all the links I find for this download take me to some sketchy download site that crawls at 50 K/s unless you pay. Am I missing something? Kies downloaded the update in a matter of minutes. Maybe that is still somewhere on my system, and I can use that w/ Odin?

bump

Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it

*Detection* said:
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
Click to expand...
Click to collapse
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.

pianowow said:
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
Click to expand...
Click to collapse
That's where everyone gets them from, there and samsung - updates dot com
Both sites are banned here for linking to, but not because they are dodgy, just because the owners refused to adhere to XDA rules
They are safe to download from

so frustrating
I downloaded the lollipop stock image from sammobile, and installed with Odin. Odin reported success just like Kies did, and also just like the Kies process, my phone is still stuck in the recovery boot loop. It says RECOVERY BOOTING... in blue at the top and shows the Samsung logo powered by android. What a mess.
Is there something I can do from here to fix this?

Try flashing the PIT file along with the stock ROM, that will repartition the phone then flash the ROM, sounds like something got corrupted using KIES maybe
Double check that this is in-fact the exact model phones PIT file first or you could end up with an even worse brick
http://forum.xda-developers.com/showpost.php?p=52767244&postcount=16
More PIT files here
http://forum.xda-developers.com/showthread.php?t=2737448
There's a video of someone using PIT with ODIN on a different phone, but steps are the same
https://www.youtube.com/watch?v=4qtbEevn1VA
Basically you want it looking like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks again for your help. I think for now I will stick with 4.4 touchwiz. I hear bad things about the touchwiz 5.0 battery life. I simply restored from the TWRP backup I used when I started all this lollipop experimentation, then did a factory reset. I should have my watch working again later tonight.

[I337M] Samsung S4 Nand Reset Failure. [Thanks Samsung]

Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution

Predated said:
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Click to expand...
Click to collapse
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?

GDReaper said:
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
Click to expand...
Click to collapse
Really? Damn, well, I guess I could grab it, but I now don't see the firmware issue and now see the S4 Bottscreen, but now I can't boot anymore, I'm thinking of reinstalling adb toget rid of this pesky libsub error.
I'll update soon.
I don't know wht I did, but it works, and it's updating now to the newest firmware. I'll update when I wake up on how I fixed it.
This is what I used to restore it to it's normal capacities:
Guys, Kies 3 has a way of re-flashing your device to the latest official firmware for a certain model with a certain Samsung serial number, i.e. even if your device is bricked and Kies 3 cannot detect it, you enter it's model and Samsung serial number and Kies 3 will download and flash the firmware for you, all you need to do is open Kies 3, power up your device and connect it to your PC, you will then open Tools menu and select Firmware Upgrade and Initialization, if Kies 3 can detect your phone it will show you the version of the firmware that will be downloaded and flashed then you will proceed as instructed (very simple procedures), if not you will be asked to enter just your model (for example GT-N8000) and your Samsung Serial Number (usually starts with R can be found on the sticker under the battery) then it will show you the latest official firmware for your device and if you proceed it will download and flash it for you, but be careful (this will be noted by Kies 3 too) you should get a full backup of your phone as it may wipe out everything on the internal storage in the process if it's required (i.e. a bricked phone to the extent of wrong partitioning that lead to loss of imei), needless to say this process depends on your internet connection (it downloads prerequisite files and firmware files which are relatively large), from little experience I have, it's best that you use the conventional official method for any product rather than unconventional ways at the beginning to solve any problem related to any product, if it doesn't help then try your best with any other method that might help you (by the way I tried this with more than one model of Samsung smart phones, tablets and notes and it always ends up solving the problem, in some cases with my friends devices reviving the device again after being totally bricked), hope this helps .
Note: all devices I used this method with were original devices straight from Samsung (International Versions, Unbranded & Unlocked), so the firmware comes straight from Samsung (no modifications done by operators / carriers) so I'm not sure if it will work for other devices (Fake Cloned, Locked or Branded devices with carriers specific settings)
Link at:
Cant post yet.

It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.

GDReaper said:
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
Click to expand...
Click to collapse
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.

Predated said:
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Click to expand...
Click to collapse
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.

Lennyz1988 said:
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Click to expand...
Click to collapse
I was on 4.4.3 for a while, but it's fixed guys, I got it, with 5.0.1 rom, thanks guys!

Need G928V Odin Firmware with PIT file.

I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!

I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be great.

ssconceptz said:
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
View attachment 3969966
Any help would be great.
Click to expand...
Click to collapse
Did you try emergency recovery with smart switch?

ssconceptz said:
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!
Click to expand...
Click to collapse
What's the version that you've got by ota? Just flash that version(must be latest in case), try to boot if it doesnt; boot into stock recovery; wipe cache/dalvik, factory reset(I dont remember which options were there). The fact is; bootloaders of latest firmwares are lock up which means you can't downgrade even previous one you've been using. Custom roms would helpful to get rid of that bootloop but don't know if its available for Verizon devices. Good luck.

*Tutorial*Flash China S6 EDGE G9250 to Hong Kong firmware to get Gapps etc.

Howdy peeps i see that there's no tutorials like this here so i decided to help out fellow China s6 edge owners
So as you know G9250 China model doesn't have Gapps on it cuz china things google is spying on them i suppose here's a way to flash Hong Kong firmware on China model to get the gapps
For starters you will need 3 things
5.1.1 Firmware- Link you can risk with 6.0 firmware but i did it with 5.1.1 and worked fine didn't test 6.0 and if you're curious yes it will still work even if you have 6.0 installed i had 6.0 installed and it installed fine SO CHILL BOIZ plus if u want to downgrade to 5.1.1 this is your way to do so
Hong Kong firmware Tar file- Link
Kies for drivers mainly Link
Odin- to install this all *duh* Link
Firstly download everything *duh*
Go to this guide to unlock your bootloader XDA Link
Install KIES just to have all possible drivers installed
Then turn phone off and put it in download mode
To do that turn it off completely and press and hold Volume Down+Home+Power you will see a blue screen with load of chinese text just click volume up that's it connect the phone to your pc via USB
After that open up odin and click on pit it will show a warning just click ok and proceed select Tar file downloaded before and click ok
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then click AP and select downloaded and extracted firmware and click Start
Go watch some my little pony while it installs
After done it it will show Green PASS and boot into recovery to do *Something*
Just wait then it will restart and boot
Theres a small chance that it will show a black screen with some chinese text and 1 button wait for that button to become clickable and click it it will just do a factory reset on the phone wait up and it will reboot and after erasing via recovery it will boot in and BOOOOOM it will show setup screen so select a language and go through a setup and
CONGRATZ now u haz gapps and other google services it has plenty of languages so if you're lazy to look for english then select a random one and then go through a setup then go to settings select the language settings and then change it to English
There u go folks ur china S6 Edge became Sort of international s6 edge thanks to hong kong firmware which has all the gapps etc.
So in a nutshell this will give you
Gapps
Remove chinese bloatware like alipay baidu search etc
Make your phone usable outside of China as pretty much everyone uses google services lol
Credits to
Me hah
Sammobile for firmware
The.Jericho.Initiative for bootloader unlock guide

To update or not to update...?

I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Raven2k360 said:
I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
View attachment 4778717
Click to expand...
Click to collapse
Do NOT update! You are on the MDB bootloader which can take advantage of the loki exploit and allow you to run TWRP custom recovery and ROMs once rooted. If you update the exploit gets patched and you are stuck with root and safe strap recovery which can boot only touch wiz ROMs. Use the towel root app to root, then follow my guide to get a custom recovery here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
I know it says MDL bootloader, but MDB and MDL are pretty much the same. Both can use loki. If you want, you can update to MDL but don't update past that or else you'll lose the magic that is loki doki.