Related
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app
celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.
Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app
Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.
www.sammobile.com/firmwares/
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.
So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse
HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!
So, my Note 3 N9005 worked fine, then i tried to install CM 12 The phone kept locking so i tried to install CM 12.1 instead. It did the same thing. Then i tried to install CM11. Phone got stuck to a bootloop. Then i tried to install the stock firmware. It launched but the phone lags like hell, apps don't open at all. Waking up the phone takes a lot of time. And the phone doesn't recognize the sim-card anymore. I used CWM to install all the custom roms, and i wiped cache, dalvik cache and did a factory reset every time before i installed a new rom. I used Odin v. 3.04 to flash the stock firmware.
So my question is this, how do i get my phone back up and running smoothly again, like it was fresh out the box? I'll appreciate all the help i can get because i am starting to get very desperate, i really wouldn't like to tell my mom i need a new phone. Note 3 cost like hell after all.
I am from Finland so i used the N9005XXUEND5 version of the stock firmware, KitKat 4.4.2.
The only thing i can think of that can cause this problem is that if the OS's i installed didn't get deleted fully, so there would be multiple OS's on my phone running at the same time. This may be a bit far fetched.
Please help as fast as possible. And i'm not that good at these things so i would appreciate if you could walk me through this step by step and explaining each step as specifically as you can.
Judging from your post, you didn't even bother to read the install instructions of the roms you were flashing.
And this is the result you get.
In CWM recovery mounts and storage format sdcard system cache data preload .
Reboot to download mode and flash stock rom .
The last time i flashed the stock ROM I formatted everything, including the firmwares and such. Now i flashed AOKP ROM and the phone is working fine, except it doesn't recognize the sim card. Any idea how to fix that. Thanks for all the help so far
Basics check you have correct IMEI and correct modem change sim card .
I'm sorry, i have no idea what IMEI and correct modem change sim card. :/
If you don't understand the very basics of flashing and firmware then i suggest you take your phone to a repair shop .Its not a game you are going to end up with a dead phone with no chance of a fix .
I think i understand the very basics of flashing, considering i have done it before twice and on both times it has worked. My sim card worked on my moms Lumia, so is it possible that the sim card reader broke. Can flashing a rom or formatting system do that? Are there a kernel i should flash? I heard it might fix problems like these. And when i go to settings there are no options for IMEI or modem change, that's why i'm confused.
**********************************************
I do have my backup still, but when i try to restore it with CWM, it says something about md5 sums, any idea how to deal with that, because i think that would help if i could use that backup. The stock rom that i downloaded wasn't from any known page. Mostly because SamMobile doesn't have my version anymore for some reason. And i tried to download it from samsung-updates.com but it said that the download would take about 9 hours. I think that the download time would only keep growing and growing so eventually it would be a waste of time.
I think i understand the very basics of flashing,
No you don't and that's your problem this post only makes it more obvious and makes it nearly impossible to give guidance .
MD5 and cwm basics turn off MD5 check in recovery .
You cannot go flashing kernels for no reason .
Modem change is not settings neither is IMEI .
Broken sim reader yes its possible but highly unlikely from a firmware bad flash .
Its entirely possible that you have downloaded a bad firmware .
You also have a non Samsung rom flashed now (aokp)
suggest you read up on that for problems .Though i cannot see any 9005 AOKP roms here .
But first you need to check you have the correct IMEI if your IMEI does not match then you restore the EFS folder you backed up before you started flashing .
I said that i would appreciate that if you would guide me through this step by step. How can i check IMEI? I'm sorry i'm making this so hard for you. The only thing i care about now is that i get my phone back stock and running smooth.
*****************************************************
That is also true that i might have downloaded a bad firmware. Are there any other place to get a stock firmware other than samsung-updates.com?
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
WhateverMan said:
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
Click to expand...
Click to collapse
I checked and it sais my IMEI is unknown. But i will try to flash that software you suggested
Restore the EFS folder you backed up .
JJEgan said:
Restore the EFS folder you backed up .
Click to expand...
Click to collapse
I think i already said something about it not working because of incorrect md5 sums.
You said backup that's not your EFS backup .
Solution given for MD5 .
JJEgan said:
You said backup that's not your EFS backup .
Solution given for MD5 .
Click to expand...
Click to collapse
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
The EFS folder contains your phones unique identification code or IMEI . Without correct IMEI your phone cannot connect . That is why the EFS folder is backed up before anything is ever flashed . No backup and wrong IMEI then you probably need a service centre repair . EFS/ IMEI can be damaged during flashing that is why rule one is backup your EFS folder first .
Nansus said:
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
Click to expand...
Click to collapse
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
You can restore your backed up EFS folder .
CWM backup restore does not include EFS .
You can flash lollipop .
You can flash a matching modem .
All these may restore IMEI or make the situation worse that is why a service repair is recommended .
phonexpert_alex said:
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
Click to expand...
Click to collapse
I'm sorry if i sounded rude towards to anybody, that is totally not what i'm trying to be. I know you guys are trying to help so i really don't see why i would be rude towards to anyone. I guess my english is still so bad that i'm sounding rude.
I think the best option now is to take the phone to a service repair. Especially if flashing anything can make the situation worse.
I thank everyone that has tried to help. It seems like that i have to accept the fact that i ****ed up my phone. At least this will serve as an example to anyone who's trying to flash custom roms and don't know what they are doing.
Oh, and the reason i have this phone because i'm a student i high school. I just started doing flashing and trying custom roms and i guess i thought it would be really simple. Clearly it wasn't.
Hello, my phone won't start i think it is hard bricked by odin i was only trying to downgrade my phone because the lollipop update drains my battery life. I want the kitkat version back i have download it from sammobile. the perfect version but after it finished it won't boot up and i can't get in bootloader or recovery &, has no root. Can anyone say how to fix this or can say of this is under warranty the phone is still no 1 month old
LVgamer98 said:
Hello, my phone won't start i think it is hard bricked by odin i was only trying to downgrade my phone because the lollipop update drains my battery life. I want the kitkat version back i have download it from sammobile. the perfect version but after it finished it won't boot up and i can't get in bootloader or recovery &, has no root. Can anyone say how to fix this or can say of this is under warranty the phone is still no 1 month old
Click to expand...
Click to collapse
Does it show that it's charging when you plug in the USB charger?
bricked A3
bernardwu said:
Does it show that it's charging when you plug in the USB charger?
Click to expand...
Click to collapse
Well, I have the same problem. Recovery boot and hard reset are not working. Not visible on Pc while connected via USB. Nothing happens. I used the official ROM from sammobile to downgrade the phone.
it do nothing anymore it won't charge at all, and i can't get in recovery or bootloader
warranty
but my question is if i go back to the store have i warranty on this it is not rooted or anything used only official roms from sammbobile
LVgamer98 said:
but my question is if i go back to the store have i warranty on this it is not rooted or anything used only official roms from sammbobile
Click to expand...
Click to collapse
Yes it will have warranty if it is not rooted.
Sent from my GT-S7562 using XDA Free mobile app
thanks man
Thanks this was the answer i was looking for i hoped it was under warranty because the phone is not even a month old!
Before downgrading you MUST flash custom recovery and make wipe data, system, then reboot into bootloader and only after that you can downgrade.
hello the same happend to me after downgrading back to kitkat.i had a full brick.i got my phone back yesterday.so yes it goes after warranty.
ok thanks for the answers, then i'll have to contact service.
I've had exactly the same problem. Took the phone to carrier shop for repair. Main board were replaced under warranty.
Please don't forget to wipe data and cache before u downgrade, it is the main reason that u having soft bricks and bootloops
Strange! Because I also once downgraded A3 to kitkat without a wipe (of course I was ignorant of the fact that it bricks your phone), and as expected, I got soft brick, but phone was still alive. But your case is expectional, as your device died completely. Maybe I was very lucky.
There is also an A5 user who reported this with his phone. He downgraded without wipe and his A5 died completely.
He even tried to get into download mode using USB jig (OP might want to give a try) but it didn't work for him sadly.
A5 Hard Brick
I still cant believe that not wiping leads to a hard brick ... but it also happened to me.
!!!! Can anyone please explain why this happens !!!
http://forum.xda-developers.com/galaxy-alpha/help/sm-a500fu-maybe-bricked-please-help-t3167400
next time you must wiping everything before you flash another firmware version is this true?
Generally, worst thing that can happen if you forget wiping before flashing, is bootloop. This can be fixed doing full wipe/factory reset in recovery after flashing. I did full wipe before downgrade attempt and still hard bricked my device. Maybe it's something related to bootloader, idk.
not for me to mind your own business, but from what I understand, reading all the topic, is that most people who have had problems with a3 / a5 was because upgraded to lollipop, were not satisfied,l, and have decided to go back to kitkat, and between one thing and another ... brick !!
This confirms to me that I was right to stay kitkat ... this device must be a bit "tricky" and suffers these procedures ....
lolli on a3 drain battery?
hannez_r said:
...
Click to expand...
Click to collapse
Have you been rooted before or did you use flashfire (not flashify), because I went:
- rooted 4.4.4 (was rooted with kingroot before then supersume) Knox 0
- unroot with Super SU
- factory reseted
- odin 5.02
- tried kongroot, not possible
- not sure if I factory reset
- odin same 4.4.4
- hard brick (no charger symbol, even JIG didnt work, no sign from phone what so ever
Luca TIR said:
lolli on a3 drain battery?
Click to expand...
Click to collapse
Not noticeably more. My region was one of the last to receive Lollipop update on A3, so I think it could be somewhat more stable than earlier releases for other regions, idk.
gggg said:
Have you been rooted before or did you use flashfire (not flashify), because I went:
- rooted 4.4.4 (was rooted with kingroot before then supersume) Knox 0
- unroot with Super SU
- factory reseted
- odin 5.02
- tried kongroot, not possible
- not sure if I factory reset
- odin same 4.4.4
- hard brick (no charger symbol, even JIG didnt work, no sign from phone what so ever
Click to expand...
Click to collapse
No, I wasn't rooted before. Simlply did factory reset before and flashed with odin.
Your A3 has been hard bricked (wrong bootloader). Unfortunately, Samsung doesn't use fastboot unlike Sony, HTC and so on. If you brick your bootloader, even USV jig wouldn't work.
The best you could do is to flash a debrick image into an external sdcard (make sure you have the correct version and variant of the image) and then insert the sdcard into your phone. Try powering on after that.
Unfortunately, the chance of recovering this way may be slim as the method requires you to remove the battery and A3 doesn't have a removable battery.
If that doesn't work, you need to repair it using JTAG. I don't recommend it doing by yourself as it requires disassembling the device. Send it to a repair service, they can unbrick the phone.
---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------
I also downgraded, but I didn't have such issues. You may have flashed it wrongly (wrong way or wrong firmware).
Could you please tell me what did you tick or untick in the odin while downgrading?
hi dear friends i have a problem in my samsung s5 first it start crashing apps then after 5 to 10 mintutes black screen reset to wallpaper it becomes slow then restart what could be this problem hardware or software then after restart it works great this happens after 10 to 15 hours of on time please help any help will be greatly appreciated
Clear the caches from recovery, if that fails, factory reset, if that fails, flash a new stock ROM
s5 problem
*Detection* said:
Clear the caches from recovery, if that fails, factory reset, if that fails, flash a new stock ROM
Click to expand...
Click to collapse
Thanks for reply i already installed stock rom done factory reset etc repartition too using pit file still the same problem
s5 problem video
*Detection* said:
Clear the caches from recovery, if that fails, factory reset, if that fails, flash a new stock ROM
Click to expand...
Click to collapse
kindly see the video
https://drive.google.com/file/d/0B9bQxezeEKDvUGxkVUNiSi1pb1k/view?usp=sharing
Hmm, it looks like a software/firmware issue, but if you have already used a PIT file and flashed a stock ROM, that's unlikely
Do you have a MicroSD card installed? Maybe try removing that and see if it still happens
If you are still under warranty, and KNOX is 0x0, I'd send it back for repair if all that fails
If KNOX is 0x1, or out of warranty, give TWRP 2.8.7.0 a flash with ODIN, and try flashing a custom ROM, see if that sorts it
If it's still doing it with custom, then all that's left is a hardware fault
*Detection* said:
Hmm, it looks like a software/firmware issue, but if you have already used a PIT file and flashed a stock ROM, that's unlikely
Do you have a MicroSD card installed? Maybe try removing that and see if it still happens
If you are still under warranty, and KNOX is 0x0, I'd send it back for repair if all that fails
If KNOX is 0x1, or out of warranty, give TWRP 2.8.7.0 a flash with ODIN, and try flashing a custom ROM, see if that sorts it
If it's still doing it with custom, then all that's left is a hardware fault
Click to expand...
Click to collapse
maybe i missed something can you please give me link of tutorial how to flash firmware
i flashed firmware from sammobile,com using odin Ap selection in odin 3.10 file size is more than 2gb of rom that i flashed did i miss something in this process?? after install i also factory reset and mobile is not in warrenty and i donot want to trip knox as i use knox app
That's the right way to flash firmware, ODIN and ROM from sammobile, and if you used a PIT file, that is the most thorough method
You should have had a 100% like new, factory reset phone once it was finished if you used a PIT file
Not much good having 0x0 KNOX if you can't use the phone though
Pit file method
*Detection* said:
That's the right way to flash firmware, ODIN and ROM from sammobile, and if you used a PIT file, that is the most thorough method
You should have had a 100% like new, factory reset phone once it was finished if you used a PIT file
Not much good having 0x0 KNOX if you can't use the phone though
Click to expand...
Click to collapse
kindly tell me about proper way of flashing pit file is it necessary to flash pit file with firmware or alone??
Dear? I'm not your dear
dont take it wrong
*Detection* said:
Dear? I'm not your dear
Click to expand...
Click to collapse
donot take it wrong i didnot mean that ,i appreciate your help !!
*Detection* said:
Dear? I'm not your dear
Click to expand...
Click to collapse
edited post
After flashing the stock firmware through Odin, you must perform a full wipe via the stock recovery. See if it solves the problem.
Vineen said:
After flashing the stock firmware through Odin, you must perform a full wipe via the stock recovery. See if it solves the problem.
Click to expand...
Click to collapse
i always do a factory reset in recovery and wipe cache
screenshots
*Detection* said:
Clear the caches from recovery, if that fails, factory reset, if that fails, flash a new stock ROM
Click to expand...
Click to collapse
the problem is not with rom the problem is with ram as i have already reset wipe cache installed rom many times still same issue kindly see attached screenshots
issue resolved detailed in description
i got S5 in october its was box packed. In november i faced issue of application crashes and screen blackout and within 30minutes mobile soft rebooted this happens every day between 15 to 18 hours now i got it fixed samsung my knox was culprit i uninstalled it and its two days i have no reboots no app crashes no soft reboot lol this page has more than 400 views no one can help me out i done it my self now i get out of this headache developers i am also very sad with you no one developer help me i thought its world best developer forum thanks everybody have a nice day:laugh::laugh::laugh::silly:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
what version are you from the start before you flashed? please provide complete information
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
ankahuja said:
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
Click to expand...
Click to collapse
well ive done that like 3 times and it still wont come out of bootloop. its as if the phones bricked...turns on then tries to start up but turns right back off. it sometimes goes as far as saying android is starting and optimizes a few apps and shuts off
kerbiii said:
what version are you from the start before you flashed? please provide complete information
Click to expand...
Click to collapse
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
Trying going back to a 5.0.1 firmware
N910PVPU3BOF5 ( I pulled that from N910P) Didn't remember Sprint model number.
So if I'm wrong find the correct model of sammobile and download 5.0.1.
See what that does. Bootloader should not be locked so it should be possible,
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
I was on the correct firmware. but for some reason even if I use odin to flash newer firmware coj6 it still doesn't boot up.
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
update: i can use cyanogenmod for a few minutes but then it shuts off again. my sprint sim card is not readable which is wierd since its a sprint rom cog5 baseband. any ideas :crying::crying:
deroyabun said:
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Click to expand...
Click to collapse
i downloaded and installed the correct bootloader and modem but still no bueno. i got cyanogenmod for trltespr to work and boot up but sim card not readable and it shuts down after a few minutes. thats really wierd considering its a sprint based rom. any ideas
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
I don't think another battery will do anything. I think it is all software. I can flash CM11 btw, so you should try that. But my system is extremely unstable... it works... but is beyond frustrating. my smart watch wont work.. have to restart phone throughout day.... so many problems I cant even list them all.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Chasef254 said:
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
A battery? How in the world would that help? That makes no sense... no offense, just sounds like you are asking someone to unnecessarily to spend $$$ when it is clearly software.
I'm having the same problems and want to know if op has tried it so I'll know if it's been ruled out of the problem thats why. Ok so it's software. You have the solution. No offense.
Sent from my iPhone using Tapatalk
d0p3t said:
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
Click to expand...
Click to collapse
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
The only solution i can find is to replace the motherboard or replace phone all together.
Primal instinct said:
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
Click to expand...
Click to collapse
Were you able to get it fixed? I'm probably going to go to a phonerepair shop this weekend or next week and see what they say or can do.