Related
Hello
My S4 (XUBMGA) wont boot, it kept crashing so i used Odin to fresh install the OS, but it wouldnt let me enter recovery mode after so then I googled and found this website which gave me steps to recover my OS via Odin and also re-partion the recovery mode via a PIT File.
Now my S4 wont boot (stays stuck on the Samsung 9505 logo) and when i try enter recovery the blue text 'Recovery Boot' or something stays there but it wont enter. The phone doesnt boot up but I can still enter download mode?
What can i do! Also im a newb at this so simple please
Thanks in advance!
Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.
MistahBungle said:
Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.
Click to expand...
Click to collapse
I did i downloaded the BTU United Kingdom Version but im not 100% sure which one to download? I bought the phone unlocked over eBay so im not sure which firmware to download exactly? I cant turn the phone on and go to about device as it wont boot to check all the numbers. Im sure it ended in MGA though
Any help?
BUMP
1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.
MistahBungle said:
1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.
Click to expand...
Click to collapse
I have and am trying. Im new to Samsung, just moved after years of iPhone, hence though rooting would be similar to jailbreaking the iPhone.
Ive tried multiple ROMs now using Odin 3.07, it says it passes etc but the phone stays on the Samsung Galaxy S4 logo, it doesnt still let me enter recovery mode, but allowss me to get into download mode.
Any advice? Thanks
Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app
Minou32 said:
Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
I followed your steps and also a youtube video but when my phone reboots and you have to enter recovery mode (to get to TWRP) it doesnt go beyond the blue font at the top left and the samsung logo. It stays there
Any advice mate
Thanks
bump - im desperate to get this sorted
hus2k7 said:
bump - im desperate to get this sorted
Click to expand...
Click to collapse
Bump
I think you 1.didn't check the reboot box
2.you removed the batterie after seing the passed message
3.and you removed your hand (all)after the samsung logo disapear
4.you download the last twrp for you model.
What is your phone model in fact?
If you want to see that go to 1.setting
2.more
3.about device
Mine is gt-i9500 simply
No at
No lce or others ones
Sent from my GT-I9500 using xda app-developers app
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line
UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:
Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
How is that going to take away the udc start?
I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.
Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:
Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.
ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.
re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Did you try flashing custom ROM?
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
androidtweaker1 said:
Did you try flashing custom ROM?
Click to expand...
Click to collapse
No, I did download a CyanogenMod one, but I can't install it from recovery, as I can't get into any recovery now.
Are there any custom ROMs that can be flashed from Odin?
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Perru said:
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Click to expand...
Click to collapse
Well, I removed the card completely and reflashed with Odin. No difference.
I can't flash from a ROM on the SD card because I can't successfully boot into recovery.
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Perru said:
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Click to expand...
Click to collapse
I have, yes.
And earlier stock ROMs, and with earlier ODINs too, in various combinations.
Every time, the flash appears to work but it then hangs, booting into recovery. I get the blue 'recovery booting' line at the top, on the Samsung initial boot screen.
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
What s u model number
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
R u now able go to download mode.
tharik816 said:
What s u model number
Click to expand...
Click to collapse
SM-G900F, as in the thread title. Is this what you meant?
R u now able go to download mode.
Click to expand...
Click to collapse
No, nothing's changed since I last tried.
https://youtu.be/m1eRM-kSNNs
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Try this ...http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
tharik816 said:
https://youtu.be/m1eRM-kSNNs
Click to expand...
Click to collapse
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
thickymcthick said:
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
Click to expand...
Click to collapse
download mode working or not
tharik816 said:
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
download mode working or not
Click to expand...
Click to collapse
Appears to be, as I've said. It's the reboot to recovery after flashing that hangs.
I don't have access to a working G900F, unfortunately.
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
thickymcthick said:
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
Click to expand...
Click to collapse
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
firareza said:
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
Click to expand...
Click to collapse
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
thickymcthick said:
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
Click to expand...
Click to collapse
My warranty isn't valid since i bought a mint condition second-handed G900F from SG. I'm Indonesian. My knox is 0x1 today when i tried to fix that using boot.tar (i didn't know if it'd make my knox avoid! desperately tried every possibilities. Ended up sobbing to see that 0x1).
I thought the problem is on the software, not the hardware. So i'm bit shocked reading your statement that you replace the board. Hope the local service center near the city helps. Thanks for the info!
firareza said:
...So i'm bit shocked reading your statement that you replace the board.
Click to expand...
Click to collapse
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
thickymcthick said:
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
Click to expand...
Click to collapse
Were you able to resolve the issue?
@mike_sausage said:
Were you able to resolve the issue?
Click to expand...
Click to collapse
Er, did you read my earlier posts? #14 and later.
Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
rissered said:
Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
Click to expand...
Click to collapse
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0
nepalbiraj said:
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0
Click to expand...
Click to collapse
Thank you!... i downloaded the stock firmware from sammobile. but whenever i extract it there's a rar message saying it is corrupted so i DLed a new one, it has the same result. I haven't tried using it to fix my phone but i will try right now. Ill give an update on how it goes.
Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip
rissered said:
Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip
Click to expand...
Click to collapse
Install the Samsung drivers first, reboot your pc.
Start odin in Admin mode then put your device in download mode, plug in the usb cable. Your device should be detected.
Don't try flashing a corrupt firmware, it will be rejected anyway as it will fail the md5 check.
I suggest you use a different browser to download.
@ashyx hey! thanks for all your help. my internet went offline while i was trying to respond to the other thread. my phone is now fixed with your help. Thank you so much! only took 3 mins for the while Odin flashing to complete
This issue is now FIXED
rissered said:
This issue is now FIXED
Click to expand...
Click to collapse
but how? I have installed official firmware and flashed via odin and it shows"success", but then it gets stuck in the samsung logo. please help
I tried to update my J500FN to Android 6.0 according to some guide from a website called "rootupdate" which showed up when I googled "update samsung galaxy j5 to 6.0"
This was a mistake because it was too vague, and I ended up trying to install the rom using some TWRP Manager app by Jmz Software.
Now when I try to boot it up, the Samsung screen shows up as normal, but at the top left it says "set warranty bit: recovery". Also I can only get to the Samsung screen once, afterwards I have to remove my battery and reinsert it to see it again.
Since then, I've tried to unbrick it according to several different guides which all follow the same beat: download the firmware you need, and use Odin to flash it or whatever it does. Problem is that I can't find a firmware with my model number anywhere (J500FNGSMH) and whenever I try to flash anything with Odin it takes its sweet time until kindly informing me that the operation has failed by yelling "FAIL!" at me. I've used Odin 3.09 and 3.10 and they both provide the same result. Now I'm at a loss, so I figured I'd create this thread to ask for help. Just remember that I suck at this type of thing so you'll probably have to explain it like I'm 5 years old.
PS: I just copied most of this from another forum post I made in sammobile, which somehow got me banned immediately so now that website is on my list of things to get revenge on, so if it doesn't make any sense that's probably why.
ihatedust said:
I tried to update my J500FN to Android 6.0 according to some guide from a website called "rootupdate" which showed up when I googled "update samsung galaxy j5 to 6.0"
This was a mistake because it was too vague, and I ended up trying to install the rom using some TWRP Manager app by Jmz Software.
Now when I try to boot it up, the Samsung screen shows up as normal, but at the top left it says "set warranty bit: recovery". Also I can only get to the Samsung screen once, afterwards I have to remove my battery and reinsert it to see it again.
Since then, I've tried to unbrick it according to several different guides which all follow the same beat: download the firmware you need, and use Odin to flash it or whatever it does. Problem is that I can't find a firmware with my model number anywhere (J500FNGSMH) and whenever I try to flash anything with Odin it takes its sweet time until kindly informing me that the operation has failed by yelling "FAIL!" at me. I've used Odin 3.09 and 3.10 and they both provide the same result. Now I'm at a loss, so I figured I'd create this thread to ask for help. Just remember that I suck at this type of thing so you'll probably have to explain it like I'm 5 years old.
PS: I just copied most of this from another forum post I made in sammobile, which somehow got me banned immediately so now that website is on my list of things to get revenge on, so if it doesn't make any sense that's probably why.
Click to expand...
Click to collapse
As it seems you still have recovery there. You can use it to flash any custom rom try odin 3.11 and try different firmware from updato.com
You can get Firmware from sammobile
I don't even remember how, but i flashed some rom and Odin told me it failed, but my phone started working normally anyway. Technology am i right lads