[Q] Stuck at logo. No recovery even after stock ROM flashing - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi guys
I have LTE sm-n9005 32gb from Holland (PHN).
As the Lollipop leaked i flashed it and got an error, hidden.ext4 FAILED!!
Of course phone rebooted and was showing the logo for a long time, so i just plugged the battery off, gave it a few seconds time and put it back.
Phone booted, was working but with glitches (bad reception and no 3G, only GSM or LTE).
I left it as is and now, when the Polish 5.0 was out so i flashed it. This time it went through and showed me PASS! sign, but phone is stuck at logo.
I can't enter recovery, i flashed TWRP and could not wipe because the TWRP failed to mount /data partition.
Then i though maybe i have partition problems, so i flashed MSM8974.pit but nothing changed.
Any idea how to recover the phone?

Solved
Cool that so many people tried to help, but anyway i managed to recover the phone by flashing this ROM
https://mega.co.nz/#!IVAykBTD!-LGw1U9ajSSLPylhdrGVxJzCY5B6_rW0-z3dXWJgSmM
Then on top of it i flashed the Polish Lollipop and it worked. The data from the phone is lost, but the phone itself works like before.
But there was one problem before, and it exists now too: the 3G or 4G networks are not supported. Phone fails to connect, but the GSM one works as expected good.
Did anyone have this problem with the note 3 (EU) ?

Very funny you are. What do you think, people are just sitting here waiting to answer your questions ? Patience.
But you are the 4 millionth person to have this issue, so there are definitely fixes out there, you just have to do some searching.

Related

Is my Note 4 entirely dead? Phone dies after 60 seconds

Hi Guys.
I bought a second hand Note 4, which is already a mistake. after a week it started giving me problems of no reception which only rom flashing helped (flashed the stock rom 5.0.1)
another week and it worked then suddenly lost reception, asked for "sim card pin number" and then crashed (after i clicked discard to the pin code message)
since then it restart itself every time after something like 60 seconds it's on.
recovery works, and nothing that i do helps. tried to re-flash it, wiped everything before and after flashing, tried to install CM 12.1 and some other roms
All going to the same basic result - no matter what, after 1-2 minutes the phone just crashes and resets
Anyone has any idea what could it possibly be? :|
i just suggested the same to another member, might help you aswell
1) Flash twrp recovery , go to wipe option hit "format data" then go to advanced wipe check dalvik cache, system, data and cache. Swipe to wipe
2) your phone will have no ROM at this point, go to sammobile download stock 5.0.1 firmware. Flash it.
3) This could be because some second hand phones are still on contract, people sell them overseas and get a new phone by claiming the previous one as stolen. So after sometime the carrier (Tmobile verizon etc) may blacklist the phone and then these phones start getting reception issues. Is your phone carrier branded ?
I suggest going for 5.1.1 and not 5.0.1 after you done what dork suggested above.
Ps. Remember to get the correct bootloader and modem for the desired firmware.
in my opinion you ve bought a Chinese device(fake) ( my mom also got scammed).

soft brick n9005

Hi guys, I'm lost, i tried flash almost everything to my freshly bought board from aliexpress but I had only success with "N9005-hlte_PDA-XXUEND6_CSC-OXXEND2_MODEMS-XXUENC2_REPACK.tar.md5" and some others but after locking and unlocking display stays black ( buttons under screen lights up and system seems to work but no visual after unlock - after swipe to unlock. I cant flash any custom rom and only some 4.x official roms. And no, i don't know what firmware was originally on it (stupid me)....
download mode info:
s33.postimg.org/taofdtcnx/P5300326.jpg
Are you saying you bought a motherboard ??
If so the new motherboard defines the firmware not your old setup .
Yeah i got new, i didn't know there's so many variants of software for phone, my good old note 2 is almost unbrickable. Any suggestions how to get it alive ?
Ok guys, I got some progress, I successfully flashed 5.0 SM-N9005_1_20160121153514_7lzesanh3b_fac tgy coz i think this is hong kong board. Everything works but i have extremely low wifi signal even when I'm standing next to router, gsm networks mostly same bad signal and whats odd, I can see sim signal without sim in phone. Isn't it coz of bad modem ? How should i continue ? Thanks.
edit:
And i still cant flash any custom rom trough twrp, always stuck on writing system partition - sometimes with error 7 and sometimes just endless loop of writing system :/
Try Philz Recovery .
I tried philz - works but cant flash rom, stucked on system, cwm - same, twm - works only some older versions not the lastest one, only sometimes it boots to lastest and cmr - not working. After rooting using supersu zip had some random reboots for some time.

May i Install KK Bootloader after having flashed Lollipop update?

Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it
I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!

Note 3 N9005 wont boot any ROM

HI
My friend need help with his NOTE 3 SM-N9005 LTE
Phone wont boot anymore. It only bootloops. I installed stock rom 2 times with ODIN and still phone stuck on recovery booting and then reboots only.
Then i flashed TWRP with ODIN and cleared everything on phone and wiped then installed MagMa_NX_UX9.7_Premium_XDA ROM
and everything sucess and seems fine, but when comes to boot it only stucks at Note 3 Splash some time and reboots.
I wonder if his partitions are ****ed up or something? ODIN dont show any errors neither.
HE said that this came after some update or something but i dont know if he tells the truth about what really happened
with the phone.
Any way to reparition whole phone and maybe update bootloader or something?
I forgot to mention that he replaced the LCD with new one but could it realy be issue? Because everything works in recovery and i can see Samsung Note splash screen.
I manage to fix it.
I flashed EUR version of STOCK ROM instead of NEE and phone finnaly booted. I dont know what the heck problem was.

Galaxy S5 (G900I) Occasional Bootloop

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.

Categories

Resources