Hi
Bought a Note 4 today. It worked in the shop and got home and factory reset it. Thats when the problems started. It went into a bootloop saying recovery mode in blue at the top. I have restored it through Kies but still the same. Have flashed a stock image through Odin and still no joy. Went to phone repair shop earlier and he tried to fix it but said it needed a new partition putting in. Not sure what to do now.
J
Maybe you need one of those firmware which comes with 4 separate parts, including the PIT file? Don't know where to get one for Note 4 honestly. Try searching on Google.
jonsdesigner said:
Hi
Bought a Note 4 today. It worked in the shop and got home and factory reset it. Thats when the problems started. It went into a bootloop saying recovery mode in blue at the top. I have restored it through Kies but still the same. Have flashed a stock image through Odin and still no joy. Went to phone repair shop earlier and he tried to fix it but said it needed a new partition putting in. Not sure what to do now.
J
Click to expand...
Click to collapse
If it's SM-N910F model, Try flashing SM-N910F VFG PIT file, you can find the PIT file on XDA or by searching on Google, other models you have to find the right PIT file
Take a look here.
http://forum.xda-developers.com/showthread.php?p=64569319
Sent from my SM-N910F using XDA-Developers mobile app
Related
I'm pretty sure I've ended by bricking my Note 4 N910G.
1. On stock, the phone started becoming very slow / unresponsive. Not the things a
2. I decided to take the "if it's broken flash it" solution. Flashed to stock but got stuck with a "ODIN flash write failure" message.
3. Have tried multiple approaches including installing TWRP / CWM without any luck. Can't flash a thing through ODIN. I've tried more options than I should have.
Taking it to the service center today. Any advice would help.
Please note:
1. I did not make a mistake with the stock ROM version. It's N910G
2. Not an expert, but have had a Galaxy S and Note 2 before this - so know my way around here. At least, that's what I thought till now.
Took it to the service center today. They're not servicing it since its rooted. Asking for USD 300 to replace the motherboard. SOS - PIT file for N910G is the last resort.
Nothing flashes at all with odin ? I think you may need to flash a pit file.
Have you tried kies emergency firmware restore or mskips toolkit? Mskip usually has an emergency firmware rescue as well. Also if you can connect through adb someone more advanced than me might be able to help you
Sent from my SM-N910F using Tapatalk
Hello. I'm a new user of SM G900F (SG). Running on lollipop with latest firmware
Bought it on Dec 26th, the device doesn't have any problem. I was happy back then, jumping form Galaxy Mini 2 to S5 is a big difference experience.
Running on official latest firmware, i only updated the phone once., around 1st - 2nd week of January.
The problem is, on Jan 14th, the G900F fail to boot (bootloop) after i set a new lockscreen from my gallery. It failed to boot, after several attemps, and wipe cache + wipe data, it booted. Haven't backed up my data yet, but i'm happy my phone is working.
On 15th, the same things happened. I set a new lockscreen. It's stil fine. But when a web-browsing on Chrome, the screen is automaically turn off (when not in use in a periout of time), but i immediatey press home button to wake the screen up. the screen didn't turn on, i press the power button. Then the bootloop happened. And this time, i can't go to recovery mode.
I've tried to re-flashing the phone using odin with official firmware, the SG one. But it didn't work. It showed Reset! with blue box on it. But still, m phone is bootlooping. My phone is still bricked. Can't go to the recovery mode either.
P.S: The phone is 2nd handed device from Singapore. I'm an Indonesian, bought the SG version bcs the Indonesia ver (G900H) is still 3G. While the SG one is 4G already. I'm using Indonesian provider (Telkomsel) and works fine on 3G or 4G so i assume the phone is unlocked. I've test the phone imei and it showed that it's the real S5, not the replica one. Antutu test showed 48,xxx score and proved that my device is the real S5 (judge by the name of device written on antutu).
I don't use micro SD. 32 gb is enough for me.
Sorry for long post and bad english. Really desperate to bring life to my phone back. Thanks before.
UPDATE: sometimes when i plugged on the device on my PC with kies on it, it booted to the homescreen. I dont know what exactly i do that caused the device booted, i only remember after stopping the bootloop (installed boot.tar, using this *the 1st method* that caused my knox 0x0, geez i didn't know that), then i flash my phone using the latest firmware (that i believe it's the correct one), then i re-plugged it on my PC with kies open, it booted! But the samsung animation logo played waaaay to long than usual. But it worked. Tried to reboot the phone to check if it's worked completely, unfortunately the device still doing bootloop. Then i tried method 2 from this, failed on odin. Turn on the device, still being jerk by doing bootloop. I gave up. Waiting for solution.
What model number does it say in download mode?
*Detection* said:
What model number does it say in download mode?
Click to expand...
Click to collapse
G900F. I downloaded the G900F SG firmware, too. Since it came from SG.
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
*Detection* said:
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
Click to expand...
Click to collapse
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
firareza said:
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
Click to expand...
Click to collapse
It repartitions the phone, 100% wiping any old firmware, then the new stock ROM will be 100% clean and you will know if it is a hardware or software problem
How can something make your bricked phone a paperweight? It already is a paperweight
If you're gonna second guess everything you're told, enjoy your buggy phone
Hello,
My dad bought a samsung s5 duos about 2 years ago, recently it started to hang and freeze then it went into a bootloop. I have tried flashing through ODIN the firmware but I cant get the phone to boot.
Its stuck now on recovery booting in blue at the boot screen. I tried flashing twrp through odin and using the option Emergency software recovery and initialization in Smart Switch, but both options gave me the same result.
Any help/guidance would be truly appreciated.
Try to search to the latest MM bootloader and modem and flash it by odin
Sent from my SM-A520F using Tapatalk
www.sammobile.com/firmwares go there, download the latest tar.md5 for your phone, flash it in Odin. its a super slow d/l, but it s the original source, directly from samsung
heres your specific device link
https://www.sammobile.com/firmwares/database/SM-G900FD/
Thanks for the help guys. I took it to a shop and had it fixed, turns out it was a hardware issue not software.
exhaler said:
Thanks for the help guys. I took it to a shop and had it fixed, turns out it was a hardware issue not software.
Click to expand...
Click to collapse
sorry for your issue man. hardware issues suck and are beyond the ususal help of xda (software, flashing installing etc etc) glad you got it rectified tho
sm-g900fd in reboot loop and stuck with recovery booting
exhaler said:
Thanks for the help guys. I took it to a shop and had it fixed, turns out it was a hardware issue not software.
Click to expand...
Click to collapse
Hi,
I'm new to the forum and have a similar problem with my phone. I've used odin and the latest firmware, cleared cache, factory reset, new battery, etc. But seems to just be getting worse. Did they tell you what the hardware problem was?
mmolnar said:
Hi,
I'm new to the forum and have a similar problem with my phone. I've used odin and the latest firmware, cleared cache, factory reset, new battery, etc. But seems to just be getting worse. Did they tell you what the hardware problem was?
Click to expand...
Click to collapse
Hello, they didn't tell what the issue was unfortunately.
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Sm-n910 said:
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Click to expand...
Click to collapse
Did you reinstall the stock firmware via ODIN? Did you download the last firmware via SAMMOBILE?
Seems like you might have flashed the wrong firmware mate
Sent from my SM-N910T3 using Tapatalk
Hi, I have an old N8010 16GB which was bought from John Lewis in the UK (an official retailer). The tablet has worked great, however recently it screwed up and got stuck in a bootloop.
So I decided to see if I can try to recover it and that's why I am here. I tried Odin and started putting what I thought is the correct firmware on it, however all the firmwares I try all PASS and seem to install correctly but the device still has a infinte bootloop (it crashes and reboots after the Samsung logo shows). I noticed the PIT file says -8G on one of the firmware files - I guess this means it is for the 8GB version which is clearly not going to work on my 16GB version?
Please can someone guide me on what firmware to download and what to try as I have been trying for 5 hours now and cannot find any way to get it out of this boot loop, I have no problems at all installing firmware as it passes every time with Odin. I am using Odin3 v3.10.7
I'm not sure but I think I need this firmware: N8010XXUCMG1
Killer_Klient said:
Hi, I have an old N8010 16GB which was bought from John Lewis in the UK (an official retailer). The tablet has worked great, however recently it screwed up and got stuck in a bootloop.
So I decided to see if I can try to recover it and that's why I am here. I tried Odin and started putting what I thought is the correct firmware on it, however all the firmwares I try all PASS and seem to install correctly but the device still has a infinte bootloop (it crashes and reboots after the Samsung logo shows). I noticed the PIT file says -8G on one of the firmware files - I guess this means it is for the 8GB version which is clearly not going to work on my 16GB version?
Please can someone guide me on what firmware to download and what to try as I have been trying for 5 hours now and cannot find any way to get it out of this boot loop, I have no problems at all installing firmware as it passes every time with Odin. I am using Odin3 v3.10.7
I'm not sure but I think I need this firmware: N8010XXUCMG1
Click to expand...
Click to collapse
Hey, I had the same problem recently and I fixed it using the stock firmware (can't post the link due to forum rules) and using a patched Odin 3.14.1 3B.
Hope it helps
Lets hope the OP has fixed the problem in the last 10 months .Unknown as he never came back .
Disguise link to post it or bit.ly
Flash this in odin https://forum.xda-developers.com/galaxy-note-10-1/orig-development/recovery-twrp-3-2-3-t3895276
Than flash Android 7.1 https://forum.xda-developers.com/galaxy-note-10-1/development/rom-slimroms-slim7-t4128693
Reboot
Done it is back in use