Develop Bugs

[Q] Stuck in spash screen

Earlier today, i was going to install drivers for chainfire3D on my 4.1.2 stock rom on my N7100 international.
After the drivers installed my phone got stuck in the welcome screen (the first one that shows up after starting the phone).
It should be said that I'm pretty new to rooting, flashing, etc. But of course I wouldn't let that, or any number of warning messages during the installation stop me.
So my question is, how do I do (if possible) a full factory reset? I can't get the phone connected via Kies, naturally, and I can't find a firmware file for my region (Norway).
If I could find a firmware file for my region, could I just install it via Odin? If so, where can I find one? Closest I've come is a Greece firmware on samsung-updates.com

h4g3n said:
Earlier today, i was going to install drivers for chainfire3D on my 4.1.2 stock rom on my N7100 international.
After the drivers installed my phone got stuck in the welcome screen (the first one that shows up after starting the phone).
It should be said that I'm pretty new to rooting, flashing, etc. But of course I wouldn't let that, or any number of warning messages during the installation stop me.
So my question is, how do I do (if possible) a full factory reset? I can't get the phone connected via Kies, naturally, and I can't find a firmware file for my region (Norway).
If I could find a firmware file for my region, could I just install it via Odin? If so, where can I find one? Closest I've come is a Greece firmware on samsung-updates.com
Click to expand...
Click to collapse
Here is the link to the latest NEE Rom http://www.hotfile.com/dl/194963553/038c101/N7100XXDMB2_N7100OXXDMB1_NEE.zip.html, flash it with Odin.

Aha! Thanks a lot!

When I click download I just get sent back to the model/region chooser.
Edit: Saw the new download link now. Thanks Again!

h4g3n said:
When I click download I just get sent back to the model/region chooser.
Click to expand...
Click to collapse
Link should be good now, posted the wrong one first (didn`t log in)

Finally got it running again after flashing original rom!
Thank you gee2012 for the info. This was a load off my chest!

[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.

Cannot verify update

I'm currently on stock. 757 firmware and before two days I had a notification about updating to the latest 14.4.108 firmware. Problem is that no matter if I download it through WiFi or 3g, It kept showing that "cannot verify update ", and nothing happens. Anyone else has this? Any ideas or suggestions much appreciated...

vriz27 said:
I'm currently on stock. 757 firmware and before two days I had a notification about updating to the latest 14.4.108 firmware. Problem is that no matter if I download it through WiFi or 3g, It kept showing that "cannot verify update ", and nothing happens. Anyone else has this? Any ideas or suggestions much appreciated...
Click to expand...
Click to collapse
I have the same problem.
And also I have problem to update it with PC companion software.
I have no idea what next...

Same here via OTA, maybe it`s because of root.....
But i did the update with PCC without problems - and nothing was wiped!

Root is not the problem. Mine is not rooted but still the problem insists. Even pc companion couldn't update the device. WTF?
Plus, I even factory reseted but nothing changed...

Is your bootloader unlocked?

Bootloader is locked. Just have root.

[email protected] said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
locked bootloader , no root at all

I had the same problem with OTA.
PcCompanion did update but my Z1c crashed now often.
So I flashed the ftf with flashtool and this time it worked perfect.
I came from .757, rooted and locked bootloader.
Now rooted again with Easy Root Tool v8

So there is no way to get ota or companion to work properly? Only way out is flashtool and ftf file?

Well I try PC companion app on other computer and it did update without problems.
I can see the difference in OS (Windows 7 vs. Windows 8) and installed ADB drivers on not working computer.

u got recovery? if yes u can't update by OTA because of changed bootloader
http://www.sonymobile.com/pl/tools/update-service/ this is better for official updates but i think u will need flash ftf
im not an expert just found this info ;P
sry for my english

DM* said:
u got recovery? if yes u can't update by OTA because of changed bootloader
http://www.sonymobile.com/pl/tools/update-service/ this is better for official updates but i think u will need flash ftf
im not an expert just found this info ;P
sry for my english
Click to expand...
Click to collapse
I had the same problem without recovery!

DM* said:
u got recovery? if yes u can't update by OTA because of changed bootloader
http://www.sonymobile.com/pl/tools/update-service/ this is better for official updates but i think u will need flash ftf
im not an expert just found this info ;P
sry for my english
Click to expand...
Click to collapse
οκ! updating with sony update tool and NOT with pc companion worked! now phone is update to 4.4.4 . Really thank you man!:laugh::victory:

[Q] Unrooting my S4mini GT-I9195

Hello guys,
Previously I have rooted my S4mini with the advices given from this forum.
However, I am going to pass my phone over to my sister.
Do i have to unroot the phone first before reformatting it? I remember my software ended with ML4 previously.Doesn't matter if the warranty is voided. I just want it to look like its new from a shop.
I am not very sure of the process of unrooting. I have read http://forum.xda-developers.com/showthread.php?t=2521928 guide but the software I'm unsure which I should download or what I should do. I reside in Singapore.
I have found this website that has the firmwares but im unsure which to download. http://www.sammobile.com/firmwares/
Can anyone please offer me some advice? Thanks !

I heard you can unroot via kies?
How does that work.
I cant seem to find the stock firmwares i need to dl.
Thanks!

Sinplic1ty said:
I heard you can unroot via kies?
How does that work.
I cant seem to find the stock firmwares i need to dl.
Thanks!
Click to expand...
Click to collapse
U can`t unroot via Kies. From which country are u ?
Just go on sammobile and download the latest version of firmware avaible for your country, flash it with Odin and then factory reset your phone. It will be good as new

I have found it thanks.
I am unsure about the flashing part..
Trying the guide in the link above..
They told me to download either kies or drivers. But the drivers may be too old when i clicked the link

Galaxy A3 FRP Unlock

Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance

Frank-95 said:
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Click to expand...
Click to collapse
1.install KIES
2.press tools
3.press frimware upgrade and installation
4.device id is your device model and serial number can be found under battery
5. allow kies to download and install the image
Video link for more help : https://www.youtube.com/watch?v=LqoX7wNhotk
good luck
Edit: please remember to enable OEM unlock in developer options next time

Kies cannot link to the device in the downlaod mode unfortunetely

Frank-95 said:
Kies cannot link to the device in the downlaod mode unfortunetely
Click to expand...
Click to collapse
try using smartswitch and see if it detects it
-are drivers installed
-does the pc recognize the phone ?

So, I had already tried with Smartswitch, but it says device not supported and does not link at all.
Moreover yes, the computer could read the phone before the frp lock, and even now, odin can detect it in download mode.
Kies just loads for some minutes and then says "unable to link to the device"
EDIT: no sorry kies raises "the device does not respond"

ok we need to flash using odin , i assume you can't access recovery but if you tried and it worked, look at the top of the screen it must show a code like
<your A3 model> followed by <your country> followed by <frimware date>
If you couldnt, we can use an updated version for your model , please provide us with the model if u can.

I can only acces to odin mode. Via that, I have the following text:
Product name is: SM-A310F
Current binary: Custom (it was rooted)
System status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: 1
RP SWREV: B:2 K:0 S:0
I am sure that the phone had Vodafone pre-installed applications, and looking at mrcrab.net there exist these possible stock firmware:
Android 5
Android 5
Android 6
Android 6
I only fear that if I mistaken the version I will obtain a wipe of my data, which are not vital but are important to me

Actually there is no way to avoid the reset as we don't know anything about the PDA version, install the drivers type in google "USB Samsung drivers"
It must show developer.Samsung.com/....
I'm on phone so I can't provide it as a link, install the drivers and try again, else we will get the latest version

I already have samsung usb drivers, and odin can succesfully detect the phone in download mode; Kies cannot, though
Anyway, if you open one of the links I posted, isn't the PDA shown in the line:
OS Version : A310FXXU1AOLE (chosen one as example)
In that website there is every stock firmware by model, android version, and mobile operator. I know two out of three, and those 4 links are the 4 possible choices regarding android version. If I picked the right one, would I avoid the data reset, wouldn't I?
EDIT: What, if I did how it is explained here with the latest version? I mean download android 6 last upgrade, extract it, rename .tar.md5 in .tar and flah it with odin? Would it be any risk of loosing data?

Hello,
.MD5 lets odin checksum the rom loaded to it to make sure it's not corrupted, however if you are sure of two main things:
that the frimware you are flashing isn't a downgrade as downgrading flashs a old bootloader which gets you in some kind of troubles possibly a brick, to avoid that, grab the latest version
and the second thing you must make sure of is that the file isn't anyway corrupted.
if you think it's all ok, then you can proceed as of i tried it once and it saved a device.

Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)

Frank-95 said:
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Click to expand...
Click to collapse
The build number must be the same regarding the android version, so to keep the files it must be the same as the one in the phone, else a wipe will be performed.
The problem is that you want your data, that maybe lost if we don't have the exact same build.
Just grab the latest marshmallow or nougat -, but the data would be lost then.
Do a hard reset in case something went wrong.

I was able to unlock the phone a mantain the data! Thanks

I have a special problem with an old Samsung Galaxy A3 2016 SM-A310F (Android 7.0 Nougat)
on which the correct combined file cannot be obtained
I have tried perhaps all FRP removal options without success
A310FXXS5CSH3