Hello
Since I upgraded to android 6.0.1 I can't flash any other hidden.img other than Poland's. I first upgraded to 6.0.1 by using a Poland copy from sammobile. As it was the first one released. It seems now I can't revert to Egypt. Its where I live and where I bought it from. If I extract Egypt's ROM and remove hidden.img and flash the rest of its components it works but it says UAE. I tried flashing the ROM without it and then flashing hidden.img alone lastly but it didn't work either just fail in flashing. Currently using Egypt's ROM and Poland's hidden.img combined with skipsoft toolbox.
So What does hidden.img exactly do on the unlocked versions of the Note 4. I want it to be reverted to Egypt as I'm sending it back to Samsung to fix a battery related issue. I'm not even entirely sure if my phone was stating Egypt when I bought it nor if even Samsung cares about what I'm doing with the phone as its not covered with warranty, bought it since release.
My battery problem,
This happen when I left my phone under direct sun light in a car for about 2hs. Firstly my phone wouldn't even work properly just enters a bootloop. Changed the battery and this stopped but my phone shuts down randomly mostly at low % battery ~30% sometimes it happens on even 70%. Its completely random. So I just got another battery, same problem and another one. 3 in total and its the same thing happening over and over again. Granted the batteries aren't genuine as Samsung Egypt ran out of stock and been without Note 4 batteries for more than 2 months now.
Is it a battery problem and should I try another one ? Maybe its still the battery ???
Thanks in advance : )
Related
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
I have a serieux problem with my phone and it is when i put in my phone charging cable into the phone.
I get fatal reboots and the phone hangs totally 10 times after putting em into the starting screen or the system.
Before i had a few custom roms on my phone and want to try em out for it´s functions
My story:
I had the CrisisCross Rom on my phone , then i flashed a 6.0 Android Custom Rom on my phone because i had problems with my Samsung Gear VR from a friend and i had not yet installed the Samsung VR Feature and had read about the leak issues from the custom roms.
Because i had an issue on the 6.0 Custom Rom with Viper4android ( don´t know which rom it was ) it only doesn´t work the programm./
Then i got back to another custom rom and Viper4android work again.Later on my system hang out when i put the charging cable on it and i have seen a few pixels and then later on the total crash of the system.i have then try out to make other custom roms on it but i made maybe a wrong DBT Code ( i choose the Germany Code ) .
But the problem stay on my phone.i had this now for 4 weeks , everytime my phone was empty it must be reflashed almost twice a day and i can´t put my phone charging cable on my phone even with that it hangs on reboots.
I tried then out to live with that as long as it works i know it´s hard to make that every time it was recharged but i don´t want to send it back to the factory for getting crushed with the invoice later
As it is and was rooted to much i have no chance that the garanty will get on for that.
A few days before this day i have made a fresh stock rom 6.0 firmware on my phone but the charging problem stayed ( pixxel issues / fatal hangouts / system problems like pixxels on the PIN sycreen )
Also everytime when the phone is off i get pixxels on the full screen ( many colours ) when i stuck the charging cable in.
My question is now if it´s worth to send it back to the factory to repair it and if that is a system problem or a problem with the hardware?
Greetz:highfive:
Can i get an answer please :crying:
If you you don't know which ROM you flashed earlier how can we help? We're not mind readers. You also haven't said which model phone you have. F/C/G? Something else? Are you sure you flashed the right firmware for your model?
If you have, it sounds like a hardware problem. It's extremely unlikely to be CSC-related. If you're rooted and have a custom recovery, I'd wipe everything including system (you will lose EVERYTHING on the phone unfortunately), then flash stock firmware via Odin. If it doesn't work then, it's hardware.
Drastic, but with the lack of info you've given.... Good luck!
It is the 928F Model
I'm from Luxembourg and i choose the CSC Code from Germany ( DBT )
I think its a chip burned inside and it reacts when i put the phone charging cable into the smartphone ( screen full of pixxels )
I have already put the Stock Firmware on the phone flashed with Odin and backed up everthing with TB.
After a restart when i put out the cable from the charger i must make really fast to go in an app or play music , still it hangs/freezes sometimes even when sonebody calls me it freeze and i must restart it manualy.
When i was in the PIN enter when it vibrates and had a freeze it vibrates till i pushed the power and Vol-Button 10 seconds
I was almost afraid that it can explode :/ ^^
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
ask for a replacement
Can I check myself that is it mmc problem?
slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
use search, there are many threads that duscuss this issue:
http://forum.xda-developers.com/note-4/help/n910f-problems-emmc-read-fail-flashing-t3456721
http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
slawekj74 said:
Can I check myself that is it mmc problem?
Click to expand...
Click to collapse
The best thing you can do is to flash another time the original firmware, adding the proper pit file for your model. This will repartition your internal memory. Worked for me on a completely dead 910f, so yours got more chance....
If after this steps the lags remains, only thing to do is asking for motherboard replace.....
Good luck
slawekj74 said:
Hi! Lately I have problem with my Note 4 6.0.1 N910FXXS1DPHB (Germany). Phone wasn't rooted only on original firmware from 4.4.4
After latest upgrade from 5.1.1 to 6.0.1 I noticed the problems below:
1. more lags (a huge lags often!)
2. often logout with asking about password (fingerprint doesn't work after restart)
3. Odin screen with " ddi: mmc_read failed" similar like in that http://forum.xda-developers.com/showthread.php?t=2596979 from time to time
I consider to use odin and SmartSwitch to make factory reset and get fresh ROM. Nevertheless I am a bit anxious that odin screen. Can it be hardware problem (internal memory)?
Obviously I have warranty and I don't need to root my Note.
Thank you in advance!
Slawek
Click to expand...
Click to collapse
Several threads exist on this issue and the conclusion we've come to in the T-Mobile Note 4 forums is replacement. In my experience, the issues got so bad that it rendered the phone unusable. Get it replaced under warranty while you still have it. Samsung denied my claim as I was out of warranty.
Phone has returned from service point - repaired. I will test it tomorrow
Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.
xhanatos said:
Good news, hopefully the issue has been sorted out.
My note4 has the same problem but although still under warranty, it's rooted. Highly doubt that Samsung will repair it for free.
Click to expand...
Click to collapse
I held back myself from make my N4 rooted until Android 6 has appeared
So, mainboard has been changed and some parts of case ( very nice due to some scrapings on silver edge of phone).
New firmware was installed - XEF (France) instead of my previous DBT (Germany). Original CSC code is empty.
possible workaround
https://forum.xda-developers.com/note-4/help/workaround-mmcreadfailed-mmcwritefailed-t3564869
Got a slight problem here.
First of all how do I find out the original network / carrier the phone was on?
I stupidly went and flashed the XSA (Australia) firmware without making note of the original carrier. Is there a way I can find out?
Secondly every time I boot the phone up it does a boot loop at least 4 times before it gets into the system.
Any ideas on this?
Thanks
G900i
My device came with Telstra firmware. I have flashed XSA, Optus, Vodafone, Spark NZ and India.
No problems.
Did you use Odin to flash your firmware?
What country are you in?
Hi
Yes I am in Australia and yep I used Odin.
It seems that even flashing TWRP the same issue I encounter but the strange thing is, although it shows up 'Recovery booting' and shows the Samsung Galaxy S5 splash logo I can still press buttons on the phone and I know this because it vibrates. Its almost like TWRP is there and is open in the background but its just not displaying at all. I have honestly tried so much.
I have downloaded (Using Sam Firm) the latest XSA and even found the PIT file to re partition but that made no difference.
The phone has had a total of around 7 LCD screens installed which came from various sellers in China. Due to the constant connection and disconnections of them I would say it may well be responsible for this issue as it has caused no doubt some considerable amount of stress to the motherboard. Maybe I am wrong I am just not sure.
It is a bizarre issue. I have never come across it before.
Standard stock recovery is also behaving the same way... I am getting, in blue, on the top of the screen 'Recovery Booting' then thats it... just that... waiting for ages and nothing happens but I am pretty sure that it is actually open behind the message which says 'Recovery Booting'
The whole things a bit of a mess.... When starting up the OS normally it takes around 5 bootloops for it to actually load up lol
Wow!! That's just crazy. Sounds like your device might have seen better days.
Occasionally I think its good to take the phone back to kitkat then to MM before twrp and custom roms.
I currently run klte version of /e/ pie ROM on my device which works very good. Un-Googled so my tired battery lasts better.
Best of luck with your problem.
Happy New Year mate.
Hi guys and gals
I am probably duplicating a thread for which I apologise in advance, but I have no clue for what key words I should be using to search for to find an existing answer, assuming there is one!?
I have the s8+ (SM-G955f) purchased in the UK via Vodafeon.
The battery died some weeks ago and I've had no money to be able to buy a replacement until now. I did try to use it now and again, but it last no more than a minute, but what did seem to happen is what is referred to as the boot loop saga.
I have followed other threads for instructions and downloaded Odin v.3.13 along with the varoius files (BL,AP,CP,CSC) from a zip file (G955FXXU9DTF1_G955FOVF9DTF1_VOD.zip) I was doing this late last night and do no remember which website I got it from, it took sooo long to download.
I am now at the point where I have connected the phone via USB and I have run the program and the status went to green, said 'pass' and the phone rebooted, however it is back to the Samsung welcome screen and sometimes keeps rebooting, other times, just stays there.
Where do I go from here? would it be that I have used the wrong firmware? I have never done this stuff before and have no clue, but am desperate to have a working phone as I have no money to replace it
Any advice, very welcome
If the battery went bad why flash firmware. Replace the battery
TheMadScientist said:
If the battery went bad why flash firmware. Replace the battery
Click to expand...
Click to collapse
I guess the issue was when the battery had issues, it would last maybe a minute or 2 before shutting down and then having to wait a full day before trying again. I did this for about a week as needed to get phone numbers from the phone along with some other info.
On the last occassion the phone turned on before the battery finally gave up, it seemed to go into the bootloop.
So now, I have tried various versions of Firmware via Frija and using Odin 3.13 to instal, but the phone doesn't seem to want to accept it.
The phone was originally purchase via Vodafone in the UK. I have tried VOD and BTU.
I am now in Asutralia, so have also tried TEL and VAU as have had sims from them also.. if that makes a difference?
I cannot get into the recovery mode at the moment, no clue why, just the download screen. The last time it went into recovery it kept mentioning about ATT which I don't understand as the phone has never had an AT&T connection which I think is in the USA and the phone has not been there..
Does anyone have any other suggestions? Would it be crazy to try and instal a custom OS and then revert back, or does the phone always remember the original firmware? I hope this all makes sense as this is all new to me..
Thanks in advance.