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
Related
Sup guys. I have a problem with my S4. I doubt anyone will be able to help me find a fix but its worth a try. I hope someone will help.
Anyway, I flashed my GT-i9500 (Galaxy S4) from 4.2.2 to 4.3. Now it doesnt boot, It just gets stuck at the 2nd boot screen. Its not even a bootloop. It just hangs there. The S4 sound that plays gets cut like halfway.
I tried flashing a lot of different ROMS, and it still does the same thing. When I rooted it, I noticed the boot welcome sound plays full, but it still hangs after that.
I used Philz Recovery and mounted all the folders etc, but efs says invalid. So that means the EFS folder is messed. I get that, but I cannot repair the EFS if I cant boot the phone, I need the Samsung MTP **** for Samsung Tool to work. I have an N7100 (Note 2) Where I repaired the EFS with Samsung Tool, I was able to boot the phone.
I looked ALL over the net including this forum and found nothing. Right now the phone is just worth nothing. This is my last option, to ask here myself. If it cant be fixed I just cut my losses and get another phone.
I also flashed a PIT file, CSC file, Modem file during the period I was trying to get this fixed. If anybody knows this problem, It'll be very helpful.
Thanks.
you could try upgrading to 4.4, i have all the files for omega v21
heres the link for all the stuff from my google drive.
https://drive.google.com/folderview?id=0B_trhAurRvdmb0RkNGpoTkVNU0k&usp=sharing
instal the bootloader and phone file via odin, bl = bootloader cp = goes into the phone part of odin
then fash the rom via philz recovery, worth a try !!
good luck
That wouldn't work, thats for the Snapdragon variant I think. The i9505. I have the i9500. I'll download the Omega ROM for i9500 and try it anyway.
Thanks.
Still doesnt work.
StickyBomb said:
Still doesnt work.
Click to expand...
Click to collapse
Did you tried complete of phone, than power and vol up, at the buzz lose vol up and at loge lose power button.
and then flash with odin bl. and modem
etc.
I've flashed with Odin & Recovery.
I flashed another bootloader, XXUEMK8 & Odexed Knox Free Stock ROM XXEUMK8 & it still does the same. I dont know whats wrong with it.
Another thing I forgot to mention is if I root it using Odin, the welcome sound plays full and it hangs, and if I reboot it, the welcome sound goes back to cutting off again.
This phone probably cant be fixed. I dont know wtf's wrong with this phone. This is WORSE than hard bricked.
oh & as I mentioned before, I have a Galaxy Note 2 & had an EFS problem with it. I fixed it, the difference was this Note 2 actually booted properly with any ROM installed. I used a Z3X Box & Samsung Tool to fix up the EFS. Maybe this problem is only with i9500 or with i9500 & newer models.
Eeeer don't mean to point out the obvious here but you did do a factory reset in stock recovery after flashing stock 4.3 in Odin? That's all you needed to do at the start.
When I went from 4.2 to 4.3 I couldn't get it to boot at all unless I performed factory reset after flash.
Sent from my GT-I9505 using XDA Premium HD app
I came from a rooted Samsung org. rom 4.3 to omega v21.1 Android 4.4.2
After this i tried slimkat, and had from first start the same issue, no booting.
Nothing works
only starting with power and vol. up as descried above, I could flash XXUFNA5 bootloader & modems.
After this twrp.
And at last I flashed S4 Google Edition - 4.4.2, a ROM for the Samsung Galaxy S 4
Thanks for the help people.
I gave up on trying. I tried everything even factory reset after flashing, different ROMS, different Android versions. 4.1.2, 4.2.2 & 4.3. Today I ended up selling the phone's LCD. Atleast I didnt everything. lol. Wouldn't be buying another Samsung EVER. I was thinking I need another box and stuff, like NSPRO but I dont have that.
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
lolozaur said:
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
Click to expand...
Click to collapse
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
willcor said:
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
Click to expand...
Click to collapse
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
lolozaur said:
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
Click to expand...
Click to collapse
hi ,
i personally , don't think it will make any difference or matters,
if you flash the one or the other ..but hey ..who knows ..?
Only reason ,i flashed BOB4 as it was the first Lollipop available and BOC3 was a later date ( March 2015 )
good luck
I have the similar issue. KK and BOB4 roms work and install perfectly. however I am having the same issues while installing BOC3 rom be it Stock or Custom.
So I finally managed to solve the issue. Seems that the image I was downloading from Sammobile was not that good.
I was trying to install N910FXXU1BOC3_N910FVFG1BOC2_CNX - Romania Vodafone. I was unable to install it no matter what I tried.
I was able to install N910FXXU1BOC3_N910FTPD1BOC1_TPD - Netherlands unknown, without any issues.
Something that i noticed is that when loading the tar with issues in Odin, total binary size was shown as 0 mb, while on the Netherlands tar file it was showing 3.3gb.
Also the tar sizes where a bit strange : RO CNX 3.6gb - NL TDP 3.4gb. So I would imagine that extra 200mb might be an issue for the partition size (suspecting bloatware maybe?).
Long story short, the tar file I was trying was the issue and downloading a different CSC file solved this for me.
Also, I tried an advice from the forum, where you extract the recovery.img and convert to tar and first flash that tar before the ROM, but that did not work in this case.
Thank you for the replies and support.
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
I installed the BOB4 like said willcor and do an antutu and, I know that it are subjective information, but I was exhausted of see the Meizu above our fairy note 4 (including with the last 4.4.4), but now, I will sleep much more well than yesterday...
Beko68 said:
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
If you're talking about knox (hehe of course, what else) knox still 0x0 after installation...
Doing this kept my knox counter at 0x0, but I did not root or install any custom recovery.
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
BNerd89 said:
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
Click to expand...
Click to collapse
Yes, I wiped from the recovery before and after the BOC3 upgrade and I must say that I like how BOC3 feels.
Battery life feels about the same for me - 50% when I get home (9-5), considering i have BT on all day as i have a smartwatch paired, exchange account, 3 gmails, skype push and a few others.
Love the new Smart Lock features with Trusted Places an On Body Detection.
One thing I noticed, manual check for updates on Security Policy Updates does not give any results, not sure if that is working correctly.
I tried rooting my galaxy j7 with Odin and the feedback I get Is binary size too large
Kindly help me out
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
vmmessage said:
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Grab latest firmware for N910A from here
https://androidfilehost.com/?fid=745425885120746376
Make sure samsung usb drivers are properly installed on your pc before you begin.
STEPS
1 Download odin and Firmware and Extract it.
2 open odin tool and upload firmware in AP slot.
Odin can take up to 5 minutes to upload firmware so be patient
3 put phone into download mode
4 connect phone via usb cable and hit start.
5 After FLASH once odin shows pass boot into stock recovery by pressing 3 button combo volume up+ home+ power.
6 in recovery do wipe cache+ wipe data factory reset.
7 reboot system and wait 10 to 5 minutes.
DONE
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Thanks
Thanks for the reply! Great! I will try that - very hopeful
tattmann said:
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Click to expand...
Click to collapse
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Trex888 said:
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Click to expand...
Click to collapse
in my case, whoever flashed my phone flashed an f file instead of the v file. It lost the imei and would not recognize a sim card. I tried flashing original firmware but the imei was still gone. The ONLY thing that saved mine was to find the correct pit file and flash it before firmware. It fixed my issue and got me back up and running. every original fw flash for me failed until I flashed just the pit. I cannot explain why the original fw included in the odin package would NOT work. Hence the statement of "you may need to" instead of "you will have to".