Develop Bugs

[Q] Noob GT-N5100 Stock 4.1.2 to 4.2.2 ?

Hi, I am new to all this updating etc, so i have a few humble questions, and hope some of you more familiar with the process could guide in the right direction.
My device is stock with 4.1.2 firmware XXBMC8/XXBMD1
1: My N5100 is India Version so would the German Update / release that is available on sammobile online work on mine.
2: What precautions etc do i have to take on my device if any. When I bought my Note 8 there was an OTA update which ran fine
and gave no issues or data loss.
3. Do I Have to take backups of my apps and have to re-install them ?
4. Any other tips / precautions i am missing.
sorry if am sounding bit paranoid.
Thanks!

intelliriffer said:
Hi, I am new to all this updating etc, so i have a few humble questions, and hope some of you more familiar with the process could guide in the right direction.
My device is stock with 4.1.2 firmware XXBMC8/XXBMD1
1: My N5100 is India Version so would the German Update / release that is available on sammobile online work on mine.
2: What precautions etc do i have to take on my device if any. When I bought my Note 8 there was an OTA update which ran fine
and gave no issues or data loss.
3. Do I Have to take backups of my apps and have to re-install them ?
4. Any other tips / precautions i am missing.
sorry if am sounding bit paranoid.
Thanks!
Click to expand...
Click to collapse
1. Yes the German version should work fine for you.
2. I just did a Titanium backup of my apps "in case" there was a wipe before I flashed the update. I have a South African 32GB N5100 the update worked perfectly. However you may not receive future OTA updates due to the ROM being for a different region.
3. Always a good idea.
4. The first time is always the worst, once you see how it is done you may not be able to stop though.

xamaba said:
1. Yes the German version should work fine for you.
2. I just did a Titanium backup of my apps "in case" there was a wipe before I flashed the update. I have a South African 32GB N5100 the update worked perfectly. However you may not receive future OTA updates due to the ROM being for a different region.
3. Always a good idea.
4. The first time is always the worst, once you see how it is done you may not be able to stop though.
Click to expand...
Click to collapse
Thanks a lot,
Bit the bullet and went with the update.
Everything went smooth.
only Minor issue I see is that, Kies does not recognize the firmware.
All apps and data seem to be as they were , though I took app backups to pc via helium as well as synced kies prior update in case anything went awry.
Now to find out what's new addition to 4.2.2 other than few things pretty obvious
Thanks again.

xamaba said:
1. Yes the German version should work fine for you.
2. I just did a Titanium backup of my apps "in case" there was a wipe before I flashed the update. I have a South African 32GB N5100 the update worked perfectly. However you may not receive future OTA updates due to the ROM being for a different region.
3. Always a good idea.
4. The first time is always the worst, once you see how it is done you may not be able to stop though.
Click to expand...
Click to collapse
how did you flash it ? is it by using the oden ? does oden need adb mode ?
I was doing some modifications with my device after rooting it and now it is bricked stuck on boot loop
the adb mode is not activated > I`m trying to find a solution I hope this update could solve my problem

mohammedsb19 said:
how did you flash it ? is it by using the oden ? does oden need adb mode ?
I was doing some modifications with my device after rooting it and now it is bricked stuck on boot loop
the adb mode is not activated > I`m trying to find a solution I hope this update could solve my problem
Click to expand...
Click to collapse
I used the Odin3-v1.85 file included in the CF-Auto-Root to flash the image.

mohammedsb19 said:
how did you flash it ? is it by using the oden ? does oden need adb mode ?
I was doing some modifications with my device after rooting it and now it is bricked stuck on boot loop
the adb mode is not activated > I`m trying to find a solution I hope this update could solve my problem
Click to expand...
Click to collapse
problem solved :good:

The 4.2.2 file is downloading as a zip. So how are you getting a Tar file?

Muffycheeks said:
The 4.2.2 file is downloading as a zip. So how are you getting a Tar file?
Click to expand...
Click to collapse
It's inside the zip file. just extract it somewhere on your puter somewhere.

intelliriffer said:
It's inside the zip file. just extract it somewhere on your puter somewhere.
Click to expand...
Click to collapse
Thanks. I figured it out....LOL

[Q] Didn't know you couldn't downgrade 4.3 Now im stuck?

I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD

Johnnysauur said:
I tried to downgrade the ota 4.3 update, i didnt know you couldnt upgrade..
Now im stuck at the Firmware upgrade encountered an issue screen..
Kies 2 will start saying "connecting" but thats as far as it gets.. then Kies 3 says that the device thats plugged in isnt compatible with kies 3.
IDK what to do xD
Click to expand...
Click to collapse
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.

andyistic said:
Place your cell in Download mode, then use Odin to insert the official android 4.3 package.
Click to expand...
Click to collapse
You wouldn't happen to have a dl link for official would you?

Johnnysauur said:
You wouldn't happen to have a dl link for official would you?
Click to expand...
Click to collapse
Start up Kies (no cellphone connected), then go to Tools / Firmware Upgrade
It will ask you for the model number, so put that in.
Then it will ask you for either the serial number or MEID, so put that in, too.
Then it should download a big-ass android package (around 1.5 gigabytes).
After the package is decrypted, copy it from the temp directory to some safe place on your local hard drive.
Use Odin in Download Mode to install this package.
The package should end with .tar.md5

If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen

FallenZen said:
If you accepted the official OTA 4.3 update, and you tried to revert your bootloader back to before KNOX... you're lucky since that should have completely hard-bricked your phone. I think, given to your description and assuming you've got the KNOX bootloader now, your best bet would be to try to repair the install by doing what I think is referred to as a "dirty" flash... which basically means you don't format or wipe your data before you attempt another installation of the same version.
I don't know for sure though, so don't take my word without someone who knows more verifying or refuting this.
Good luck, I'll be interested in seeing what you wind up working out.
-Zen
Click to expand...
Click to collapse
I downloaded the mk3 modem, and flashed it in odin, it fixed the softbrick. i rooted it with cf-auto and it went through no issue. disabled knox no problem, and now got cwm working.

Firmware failed to install

I have a 9195 running 4.2.2 stock. it was under the EUR csc and I tried to install a 4.4.2 through odin but it failed and now my phone is bricked. kies won't recognize it and it keeps turning when I insert it so I cant emergency recover the firmware. trying to download my old one but its not on sammobile anymore and its taking hours to download from this other random website I found. any clues as to why I couldn't flash it? does it have to do with my CSC? I was on EUR and I was trying to flash a branded one. but the brand is the my phone carrier and even though I dindt get it from them I figured it'd be okay

kostas90 said:
I have a 9195 running 4.2.2 stock. it was under the EUR csc and I tried to install a 4.4.2 through odin but it failed and now my phone is bricked. kies won't recognize it and it keeps turning when I insert it so I cant emergency recover the firmware. trying to download my old one but its not on sammobile anymore and its taking hours to download from this other random website I found. any clues as to why I couldn't flash it? does it have to do with my CSC? I was on EUR and I was trying to flash a branded one. but the brand is the my phone carrier and even though I dindt get it from them I figured it'd be okay
Click to expand...
Click to collapse
i wouldn't suggest to flash branded ones for non branded phones but anyway, you could try flashing mine from the unbrick/downgrade guide.. http://forum.xda-developers.com/showthread.php?t=2751224
make sure to follow the guide completely

kostas90 said:
I have a 9195 running 4.2.2 stock. it was under the EUR csc and I tried to install a 4.4.2 through odin but it failed and now my phone is bricked. kies won't recognize it and it keeps turning when I insert it so I cant emergency recover the firmware. trying to download my old one but its not on sammobile anymore and its taking hours to download from this other random website I found. any clues as to why I couldn't flash it? does it have to do with my CSC? I was on EUR and I was trying to flash a branded one. but the brand is the my phone carrier and even though I dindt get it from them I figured it'd be okay
Click to expand...
Click to collapse
This is what i do when it appears to say failed, i flash a stock recovery that should be in the attachments added to this post, put your phone into download mode, connect it up, wait for odin to see our device, then load the recovery into odin and hit start then it should restart and be in 4.4.2.

feckinfinch said:
This is what i do when it appears to say failed, i flash a stock recovery that should be in the attachments added to this post, put your phone into download mode, connect it up, wait for odin to see our device, then load the recovery into odin and hit start then it should restart and be in 4.4.2.
Click to expand...
Click to collapse
thanks a million. I got a way off s4miniarchive.com and managed it that way

kostas90 said:
thanks a million. I got a way off s4miniarchive.com and managed it that way
Click to expand...
Click to collapse
Just watch what your doing next time :laugh: Glad you got it sorted.

[Q] GT-I8160 stuck at boot logo

Hi All,
I have a problem, its on my wife's phone which makes it a huge problem, shes not very happy with me at the moment.
Her ACE 2 GT-I8160 was running very slow.
I used KIES to update it from 2.3.6 >> 4.1.2
After flashing the firmware with KIES the phone was running very slow, seemed like it wasn't able to handle the new software.
So I tried to flash the firmware back to 2.3.6 using odin.
My wifes phone was bought "off carrier" as a factory unlocked phone.
I downloaded the UK firmware cause I could not see any for the Irish region (we're in Ireland )
"Galaxy Ace 2 GT-I8160 H3G I8160NELG2 Android 2.3.6 06.07.2012 1164437 Unlock Download File"
From what I understand this is the correct stock firmware?
Anyway, I flashed it using odin and now the phone will not get past the samsung logo.
I can boot into download mode but not recovery.
Any help would be very much appreciated and will definitely make my life at home a lot easier.
Cheers.

scolariIRE said:
So I tried to flash the firmware back to 2.3.6 using odin.
My wifes phone was bought "off carrier" as a factory unlocked phone.
I downloaded the UK firmware cause I could not see any for the Irish region (we're in Ireland )
"Galaxy Ace 2 GT-I8160 H3G I8160NELG2 Android 2.3.6 06.07.2012 1164437 Unlock Download File"
Click to expand...
Click to collapse
You have to flash the Russian 2.3.6-firmware first (I8160XXLK6) that consists of three seperated files for ODIN (pit, pda and csc). You can choose it on sammobile, look for the firmware checker to search their firmware archive by model and country (as a new member I am not yet allowed to post the link here).
After flashing your phone should be able to boot again. On this linked page you can also choose the correct Irish provider branded 4.1.2-firmware (METEOR, O2 or Three) that you can flash afterwards if you still want to.
Do not forget to do a factory reset after each flashing procedure!

Borgkubus said:
You have to flash the Russian 2.3.6-firmware first (I8160XXLK6) that consists of three seperated files for ODIN (pit, pda and csc). You can choose it on sammobile, look for the firmware checker to search their firmware archive by model and country (as a new member I am not yet allowed to post the link here).
After flashing your phone should be able to boot again. On this linked page you can also choose the correct Irish provider branded 4.1.2-firmware (METEOR, O2 or Three) that you can flash afterwards if you still want to.
Do not forget to do a factory reset after each flashing procedure!
Click to expand...
Click to collapse
Thanks for the reply Borgkubus.
Before I saw your post last night I had in fact flashed her phone back to Jelly Bean and was able to open the phone correctly. So flashing back to 4.1.2 got me past the boot logo freeze.
But now I am back to the original problem, the phone with the latest software lags and is so slow to do anything, its very frustrating to use it, so I need to investigate how to fix this.
You talk about installing the Russian ROM, whats the thinking behind this? Would I be able to install this russian rom and then flash to an Irish 2.3.6?
I am a bit apprehensive about using a PIT file, the last time I used one I messed up my S3. Is it safe to use the Russia rom and them falsh to an Irish 2.3.6? This might speed up the phone.
Also, one last thing, doing a factory reset after the flash, what does this do? My understanding is that it removes all user info, will it speed up the OS also?
Thanks again Borgkubus.

First of all, nobody can guarantee the safety of a flashing process. However, by following the common rules when flashing with ODIN you can minimize the risk of a brick. Just do it as soon as you know what you are doing.
The thinking behind using the Russian ROM (XXLK6) is the following: It's the only firmware on sammobile that consists of 3 parts, including the Gingerbread pit file for repartitioning. Doing so I never had any problems when downgrading to 2.3.6. And of course you can flash an Irish firmware afterwards, the Russian one is just an intermediate step.
The factory reset is needed to get a clean install. I recommend you to do this every time after flashing another firmware. This might also solve many problems such as boot loops, lags and so on.
Happy flashing,
Borgkubus

Please identify my SM-T705 build!!!

Hi there,
I have the Samsung Galaxy Tab S 8.4 LTE version, which I purchased through Ebay - I believe it came from Asia somewhere as it showed up with an international adapter for the power supply. It was sold as a "Verizon" model - I ditched that sim card and have been using it with Bell Mobility in Canada.
Recently, I tried to update my firmware using the latest version of Samsung Kies and I'm running Windows 10 latest version. For some reason Kies needs to reinstall the USB driver before performing the update to the firmware and this causes Windows 10 to crash without fail. (This is also happening to my Note 3 - Samsung informs me Kies is not compatible with Windows 10 although it seems to work for everything else - just not the update). Kies doesn't seem to care that I already have the latest drivers installed.
I can't update via the tablet because my device has been "modified" - rooted.
Finally I went to Sammobile for the firmware, however I can't find any US firmware for a compatible carrier under SM-T705. I am debating flashing the Bell Canada firmware, but the model is listed as SM-T705W. In case this is not ok and I need to revert to the original, I'm hoping someone can help me identify my build? The samsung agent offered to identify it but once she discovered it was from outside Canada she said she had no information. So much for Samsung International!
Please help! I'm having battery issues and I'm hoping updated firmware will help, plus I would like to have the latest version of Android. Thanks!

If you're in Canada then just flash the Canadian firmware.

ashyx said:
Cellular south is us
Region XAR
Click to expand...
Click to collapse
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!

LostinCanada said:
Hi there, forgive me for being thick, but how do you tell it's Cellular south, and what do you mean by region XAR? I'm sure that the fellow I bought this unit from flashed US firmware, however I can't find it on the Sammobile site - in fact I can't find any US carrier firmware listed for this model.
As mentioned above, I did find Bell mobility (Canada) firmware listed for the SM-T705W but nothing for the SM-T705.
Further explanation greatly appreciated!
Click to expand...
Click to collapse
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.

ashyx said:
You can flash any firmware for that model, so just flash the Canadian firmware, no point in flashing a us firmware.
Click to expand...
Click to collapse
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!

LostinCanada said:
Ok great. I would like to locate the US firmware though for future use. I travel alot in the US and in the event I need a different carrier's modem... Are the US carriers listed somewhere else or am I blind? http://www.sammobile.com/firmwares/search/SM-T705/
Thanks!
Click to expand...
Click to collapse
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.

ashyx said:
You have root so install twrp from the development section and do a full back up of your current system.
You can then restore as you please.
Seems no US firmware for the t705.
Click to expand...
Click to collapse
LOL... ok now I have another problem. I had already downloaded the Bell mobility file from Sammobile and hadn't seen this response - in the meantime I hooked up with Odin and my download failed twice - I don't get it. I just did my Note 3 10 minutes ago without any issues. Rebooted device and odin between both attempts.
Thoughts?

Don't flash anything until you make that full backup with TWRP, trust me it will save a massive headache should you need it.
Download Flashfire from the link below then set your date back to August, run Flashfire then load up the firmware, select the Flash firmware package option.
From the partitions list select system.img and boot.img only.
Under the reboot options select download mode then hit the flash button.
Once it has flashed and booted to download mode you will need to flash a lollipop bootloader (assuming you are flashing lollipop?)
You will find them in the bootloader thread.
After that just reboot the tablet, it will take about ten minutes for it to fully boot.
http://likewaphd.in/filewap-1-load/...2015/FlashFire_Pro_v0.21_-_Likewap.apk-0.html

Uh... ok you lost me early on. I downloaded the file - how do I install it? I remember using the TWRP thing several phones back when I was messing with custom ROMs. I had a problem with recovery and since then have never gone this route - I've been happy with stock rom and root - installed using Odin... sortof the KISS principle.
I can try TWRP, but could you dumb down the instructions a bit - as I mentioned, I'm a bit thick - particularly with some of the terminology! LOL
This is the file I downloaded - yes, Lollipop - I don't understand why I have the Odin Fail - google isn't helping me understand either. I have root, USB debugging is enabled and I followed the same steps as with my Note 3 - the message said write fail.
http://www.sammobile.com/firmwares/download/52301/T705WVLU2BOE4_T705WOYA2BOE4_BMC/ Is this what you mean by bootloader?

TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362

ashyx said:
TWRP - flash with odin then boot into twrp using POWER + HOME + VOL UP - http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Bootloader - http://forum.xda-developers.com/showthread.php?t=3099362
Click to expand...
Click to collapse
Ok but those "bootloaders" are custom ROMS are they not? And I don't see my device on the TWRP site - I have the LTE version, it only shows Wifi.
Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it, but I had no trouble rooting it with the chainfire auto-root.

LostinCanada said:
Ok but those "bootloaders" are custom ROMS are they not? Really all I want to install the Bell stock firmware (assuming it is indeed compatible - SM-T705 vs SM-T75W) I linked to from the Sammobile site and then do Chainfire's auto-root.
Why isn't Odin writing the firmware to my device? I've never had this issue before and I don't see what I might have done differently with this device - it's the first time I've tried to update it.
Click to expand...
Click to collapse
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.

ashyx said:
No they are bootloaders they are required to boot the firmware , roms are the os.
Odin won't flash because certain devices will refuse to flash another regions firmware.
My advice to you is to flash the lollipop bootloader first, to make sure it will flash then flash the firmware with flashfire.
Obviously make the twrp backup first.
Click to expand...
Click to collapse
Ok I flashed the bootloader, and then I tried to flash the firmware with Odin again but it still won't do it - write fail again. I've never used flashfire - windows 10 won't open it...
UDATE: Ok I read to transfer the file to the download folder on the tablet, and then install on tablet. So I did that, but when I click on the icon it doesn't run. How the heck do I use this to install the firmware update?

Figured out the date bit, ran Flashfire.... problems during the install - got stuck in boot loop - tried a factory reset - that didn't work... stuck in loop. I think I'm bricked....
Left the default settings in place - very little in the way of instructions - read the bit about not trying to write over protected settings...
And got this:

You're not bricked as long as the tablet starts up and you can boot to Download mode.
I've seen that error with corrupt downloads so not sure why you're getting it.
Reboot to download mode. Just hold POWER + HOME + VOL DOWN until the device restarts and boots to download mode.
Doesn't matter if it's boot looping.
Reflash TWRP and restore the backup you made earlier. You will be back to where you started.
At this point I think the best option is to flash a custom lollipop rom.
There is a very good one I use on my t805 which is practically stock with a bit of bloatware removed.
Its in the development section called sweetrom.
At least one positive is that you were able to flash the lollipop bootloader, so upgrade is not impossible.

I'm definitely able to get to download mode - I was surprised that the factory recovery mode didn't work. I'm wondering if the file from sammobile is corrupted - I used the same file with Flashfire - now I think Odin was trying to save me. I'm downloading the same file again fresh, and it looks like Telus and possibly the other Canadian variants are the same - unless it's the same corrupted file.
I just hope the problem isn't because my phone identifies itself as a straight SM-T705. That is why I asked about that point earlier. There are plenty of straight 1705 options available - just don't know which country would be compatible - particularly for the modem.
I didn't understand how to use TWRP and I've had problems with it in the past (recovery) when I did figure out how to use it and was messing with custom ROMS a couple of years ago. I would really like to get myself back in order with a proper stock ROM and root. This tablet belongs in my car and right now I just want it to work properly - I'm using Torque to resolve some ongoing engine issues and it will suck if I have to go back to using the small screen on my Note 3.
If there is any way to figure out which of those countries for the 705 are compatible with Canadian carriers, in case this Bell firmware is defunct, that would be appreciated.
As well, is that bootloader going to cause any problems with stock firmware? I've already flashed it - does stock firmware come with bootloaders included?

OK before I go any further with this I need you to install twrp and make that back up. Twrp is now very stable.
Twrp will back up some very important partitions namely the Efs and modem. Don't take this warning lightly. The amount of people that have soft bricked their device because they didn't do this.
Boot into twrp then simply select the backup option and make sure the partitions on the left are ticked particularly boot,
Efs and modem.
Now as regards which firmware.
I would forget about installing the Canadian firmware.
It looks like this firmware will only install specifically on a Canadian device.
It doesn't really matter which firmware from which region you install as they are pretty much all the same except for the carrier ones which just add more bloat and some csc specific stuff.
Just go for an international rom. You've already flashed a bootloader from one of these roms so that proves you can flash.
Use odin to flash.
If you have connection issues afterwards then all you need do is restore your modem backup with TWRP.
That's why it's important you do this.
Follow these instructions and we will get you up and running.

Whole again!
Whole again!
For the record, I read elsewhere that it is NOT recommended to flash other letter variants of a model. In the meantime I downloaded all four Sammobile Canadian Carrier files and they appear to be the exact same file and all install attempts failed For anyone else with an actual SM-705W I read in this thread: http://forum.xda-developers.com/galaxy-tab-s/general/t705-lollipop-t3099945 a fellow Canadian was having a problem with those same files. Dunno what happened with him in the end, however I tried one more W file I found elsewhere that appeared to be different but it failed as well.
Based on the comments in the above thread, I flashed the Hong Kong variant for the SM-705 from Sammobile - apparently it was the first firmware widely available and users from several countries posted they had used it successfully. So far it seems to be working ok - after flashing it, I did a factory reset on the device as was also recommended in the above thread. Sure hope the battery life will be better than before - love this tablet but I've never seen a device drain so rapidly! CF-Auto Root restored!
As a side note my Ebay seller did reply to my origins query and was helpful once he realized I wasn't complaining about the device and wanting to return it... LOL. Apparently my unit originated in Singapore and arrived with that firmware along with a Verizon SIM which I never tested. As long as the OS is smooth, and the modem compatible, and unless someone advises a better country variant, I guess I'll stick with this one.
Now just need to get Torque reconfigured!