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?
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!
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
deleted
deleted
did you try a soft reset? remove battery and sim card for 30 seconds and put back.
!!! Bat is built in !!!
- Jig (300kOhm between Pin 4 an 5/GND on USB plug) works on S5mini immediately after plug in.
- On Tab S (built in bat like my A5) one has to press power additionally to the JIG plugged in.
Still no luck on A5 (SM-A500FU)
1 Still no idea what I did wrong
2 How could I empty the bat ??? (I did not measure any power on the USB plug, so no chance to drain it and its 2300mA fully loaded)
Does the screen comes up when you plug jn the charger?
no nothing
gggg said:
no nothing
Click to expand...
Click to collapse
Try leaving it on charger for a few mins or maybe an hour. If that doesnt make it react then its a hard brick and woukd suggest a repair center.
Sent from my SM-G850F
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
gggg said:
THX ... I ll tried that ... no change
Could you guys please give me some ideas, what possibly could have gone wrong !
Click to expand...
Click to collapse
Probably you can t downgrade the bootloader... If you plug it to your pc does odin show something?
You said you cant boot in download mode that means your stuck in a hard brick that you cant recover by yourself. I managed to unbrick devices that at least could boot in download mode, i think only a repair center can help you
No nothing. No, not even the JIG does work. (Usally after plugging the JIG an hitting POWER or supplying power from charger through the JIG plug, it should go to download mode). So I will give up on it.
But I still would like to know what I did wrong ... lots of others seem to downgrade without an issue:
http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3141337, http://forum.xda-developers.com/galaxy-alpha/general/downgrade-5-0-2-to-4-4-4-t3125264
gggg said:
I had rooted my 4.4.4 with kingroot, changed to SuperSU with supersume and unrooted with SuperSU. Then Iwent back to stock (all official no Knox) with Odin (4.4.4 (A500FUXXU1AOB4_A500FUATO1AOB1_A500FUXXU1AOB4_HOME.tar.md5).
Then I went from stock to 5.0.2 (A500FUXXU1BOE6_A500FUATO1BOE1_A500FUXXU1BOE6_HOME.tar.md5) with Odin.
Actually after updating from 4.4.4 to 5.0.2 (with odin) the phone converted a lot of apps during startup - Did this also take minutes for you guys ?
All fine and phone quite fast, but no chance to root with Kingroot.
So I wanted back to 4.4.4 I used Odin again and flashed the 4.4.4 as written above. I did not tick reboot in Odin and so I powered off the phone after Odin said that all was flashed OK.
Now the phone is off (body is cold) and not repsonding to POWER+HOME+VOL+(or -).
After searching in xda it looks like I should have flashed all except the bootloader or flashed another BL first. I am confused and frustrated.
Hope you can help !
Click to expand...
Click to collapse
You were meant to downgrade after making a full reset. However, failing to do that will still allow the phone to boot and it will be a soft brick. And recovery and boatloader shouldn't be affected and be perfectly functional.
Can you boot into recovery? If you can, do a full wipe and then install the ROM you desire.
droidqwerty said:
...
Click to expand...
Click to collapse
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
gggg said:
This is what I also dont understand .... because as I said no reaction at all (no recovery, download mode, not even with a JIG) ....
Click to expand...
Click to collapse
You mean no logo or even no turn-on vibration?
droidqwerty said:
You mean no logo or even no turn-on vibration?
Click to expand...
Click to collapse
yes
What happens when you plug it into charger?
My final opininon is that it needs service.
Sent from my SM-G850F
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
hensk said:
this downgrade from 502 to 444 than again 502 you have mess up with bootloader ,
I dont know who bootloader 502 or 444 FW but that you yourself make mess is true
all recommend avoiding the frequent downgrade of FW
Click to expand...
Click to collapse
I went 4.4.4>5.0.2>4.4.4 - no more !
1 Can you please explain more in detail what caused the trouble in your opinion
2 How can this be avoided = how to to that with Odin / how to just flash Stock.tar without or with another Bootloader ?
3 Which bootloaders (primary and secondary??) should be flashed togerther with 4.4.4 or 5.0.2 ?
You should factory reset before downgrading, otherwise your phone would be soft bricked
Hi, I need to complete brick my note 4 n910f. Already install 4 files kk and lollipop firmware and don't help me. I've random reboots and now always reboots.
I need to complete brick (can't enter in download mode) because I've knox 1 and in the sat they say I don't have warranty because knox to 1.
I tried to put note 3 and n910c firmware and note refuse it.
Any help?
Cheers.
U think to unbrick? Or brick rlly? ?
I first time see this,some1 want to brick phone 800$
Try whit PIT file
Flash a rom meant for a different phone. Like an S6 or Note 3.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Lol, try to flash ios firmware
I mean brick (no unbrick).
Already tried to put firmware from other phone and note refuse to install.
Cheers.
While kernel installing, remove the usb cable.
SM-N910C cihazımdan Tapatalk kullanılarak gönderildi
akirax said:
I mean brick (no unbrick).
Already tried to put firmware from other phone and note refuse to install.
Cheers.
Click to expand...
Click to collapse
Try rooting your phone and flashing (via custom recovery) a kernel meant for another phone. That's how I hard bricked my old LG phone. I wasn't paying attention and somehow managed to flash a kernel meant for a Huawei phone. No clue how I managed to do it exactly, but it resulted in the phone not booting up, me unable to access recovery or bootloader (download mode for Samsung devices), and my computer recognizing my phone as some unknown device.
I ended up bringing it into an ATT store and playing dumb. Like, "I don't know what happened, but my phone just started randomly rebooting and then just stopped starting up all together! Woe is me!"
Sent from my SAMSUNG-SM-N910A using Tapatalk
akirax said:
Hi, I need to complete brick my note 4 n910f. Already install 4 files kk and lollipop firmware and don't help me. I've random reboots and now always reboots.
I need to complete brick (can't enter in download mode) because I've knox 1 and in the sat they say I don't have warranty because knox to 1.
I tried to put note 3 and n910c firmware and note refuse it.
Any help?
Cheers.
Click to expand...
Click to collapse
Firstly you SHOULD NOT be flashing your phone or tripping knox with what you have posted. If you have constant reboots etc you should try fix it or work with samsung. You should not try brick your phone because you want Samsung to replace it.
However if you know how to flash etc you should know it is easy to brick a phone, just kill the bootloader!
here is no chances to brick to death end your device. Believe me. It better to install for you correct everything from the beginning. Mean , stock rom, root, and do whatever you want.
I've continously reboots. I know how to flash with ODIN. I tried lot of firmwares for my n910f. Tried with 4 files firmware and always get a reboots. Sometime I can't get into Recovery because the phones reboots. I can get always into Download mode, but nothing more.
I don't know how to kill the bootloader, can you PM me with instructions? I alreay tried to put a pit file from other variant, and also tried other variant firmware and phone refuse to install it because before install phone check if is for it or not, so I can't brick my phone.
Cheers.
Do you want to brick your phone because it continuously reboots itself?
Have you tried to select "Nand Erase All" in ODIN? I personally never used that option; but, because you want to brick your phone, maybe you can try it (maybe with an official firmware or TWRP in the pda button) and MAYBE it will even solve your problems or MAYBE will brick your phone.
If you'll try it, please, report back!
Sorry for posting my Q here
But I really want to know is there any option in Note 4 , so that the notification sound will not come from speaker when Handsfree are attached.
Thank You
Sent from my SM-N910H using Tapatalk
_mone said:
Do you want to brick your phone because it continuously reboots itself?
Have you tried to select "Nand Erase All" in ODIN? I personally never used that option; but, because you want to brick your phone, maybe you can try it (maybe with an official firmware or TWRP in the pda button) and MAYBE it will even solve your problems or MAYBE will brick your phone.
If you'll try it, please, report back!
Click to expand...
Click to collapse
Already tried "Nand Erase All" option, and doesn't do anything, don't help.
Cheers.
hello everyone
3 days ago I bought a Samsung Galaxy S5 SM-G900F and the pre-installed OS was Android 5.0 Lollipop
I wanted to downgrade to KitKat 4.4.2 but when I flashed the 4.4.2 firmware at the end of The Flash the phone Rebooted but but there was nothing on the screen and the phone was stuck on a boot loop so I reflashed the lollipop firmware and everything worked
The question is it possible to downgrade to kitkat 4.4.2 knowing that the preinstalled firmware was Android lollipop 5.0 for rooting purposes to keep knox 0x0
thank you very much
The problem with using Odin to downgrade is that it doesn't fully erase what was on there before, it just overwrites it......
Did you try to wipe data in recovery after the flash? Sometimes this is all that is needed.
If you did, and it didn't help, then it may be necessary to flash a pit file at the same time as the firmware.
Before you flash anything with Odin, go to download mode to double check which model you have.....There have been a number of cases recently where devices have been 'rebadged' so that what is displayed on the sticker under the battery does not match what is displayed in download mode (download mode is correct).......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
The problem with using Odin........
Click to expand...
Click to collapse
yes it does show SM-G900F in download mode
where can I find a pit file
and just for info when I flashed the 4.4.2 firmware there was nothing on the screen even in download mode I could enter it because the keys combination is well known
You can get the pit file in post 3 here....
http://forum.xda-developers.com/showthread.php?t=2737448
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
You can get the pit file in post 3 here....
http://forum.xda-developers.com/showthread.php?t=2737448
Click to expand...
Click to collapse
Is there any risk on flashing the pit file
I just want to know before I proceed
Thank you very much for your help
There's a risk to any flash, but as long as your device matches the pit file you flash, you should be ok.....having said that, flashing a pit file carries a potentially greater risk than flashing a firmware/rom as it 're-maps' the data partitions.....In the case of a pit flash, if the flash is interrupted because of a power cut off or a premature device disconnection, the phone will be absolutely irrecoverably bricked......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
There's a risk to any flash, but as long ............
Click to expand...
Click to collapse
the problem now is that when I flash kitkat 4.4.2 the phone does boot up but there is absolutly nothing on the screen
Do you have any idea?
thanks for all the help
When I downgraded from LP to KK, the first attempt was unsuccessful, the phone wouldn't boot at all
I did nothing else apart from flash it again exactly the same way, the next boot was fine and I was back on KK
You might need to factory reset after flashing, it's possible some apps are causing problems with the boot if they are not compatible from LP > KK
*Detection* said:
When I downgraded from LP to KK, ................
Click to expand...
Click to collapse
how can I do a factory reset without seeing anything on the screen?
the screen is completly black in all situations : normal boot - download mode - recovery mode
saktani said:
how can I do a factory reset without seeing anything on the screen?
the screen is completly black in all situations : normal boot - download mode - recovery mode
Click to expand...
Click to collapse
Factory reset first then
But if the screen is just black, not even the initial logo, then something else is wrong
Why flash KK anyway, there is a MM stock ROM port available for the G900F now
*Detection* said:
Factory reset first then
But if the screen is just black, not even the initial logo, then something else is wrong
Why flash KK anyway, there is a MM stock ROM port available for the G900F now
Click to expand...
Click to collapse
I know but I wanted to root the phone possibly without tripping KNOX
If I do trip knox what would I louse aside from warrenty?
saktani said:
If I do trip knox what would I louse aside from warrenty?
Click to expand...
Click to collapse
Nothing, I tripped mine ages back, everything still works
I read it might affect joining enterprise networks/domains, but never tried and don't use them
Try a different KK ROM, I assume you're trying the latest version atm?
It *might* affect OTA.....Some people say it does, others say it doesn't.....
But knox's main function is to prevent insecure devices from connecting to secure 'enterprise' business servers/networks.....basically if your employer expects you to be able to bring your device to work, and connect it as a business tool, you will no longer be able to do so.....*and* if the device was supplied by your employer, you could end up in all sorts of s**t with them too.....
http://i.imgur.com/rVnFwJM.jpg
Doesn't affect OTA, only custom (Root/Recovery) breaks OTA
Anyone saying tripped KNOX breaks OTA hasn't flashed back to 100% stock before trying to update OTA, unrooting doesn't reverse the custom status
Thank you very much for your help
I gave up I installed TWRP and flashed a custom rom
I couldn't resist any longer
I don't care about KNOX nor the warrenty anymore
Poeple are very kind in this forum
much appreciated for all your effort
Curious, why were you trying to downgrade to KK when Android 6 is available for g900f? I downgraded once myself (without pit file) to KK early on when LP was new, but Android 6 is a nice improvement over both imo. KK4.4.2 still has security issues, namely stagefright. If you're happy with custom rom, so be it, just curious if you were (or not) aware of Android 6 availability for your device, incl debloated, stock based knox-free ROMs.
saktani said:
I wanted to downgrade to KitKat 4.4.2 but when I flashed the 4.4.2 firmware at the end of The Flash the phone Rebooted but but there was nothing on the screen and the phone was stuck on a boot loop so I reflashed the lollipop firmware and everything worked
The question is it possible to downgrade to kitkat 4.4.2 knowing that the preinstalled firmware was Android lollipop 5.0 for rooting purposes to keep knox 0x0
thank you very much
Click to expand...
Click to collapse
Sorry, I know it is too late, but search is always your friend You would've had to follow these steps:
http://forum.xda-developers.com/showpost.php?p=57321061&postcount=1629
Hi, I got a 2nd hand J7 pro with Android 7.0 on, no root or anything. I used Odin to install TWRP, and it worked just fine.
The next day I tried to install the official 8.1 update using odin, it took 4 minutes and passed on Odin . But the phone won't boot, it reaches 30% of Android updating progress then it reboots to a blue screen with a yellow triangle and an Android figure with an error no commend. I tried installing multiple ROMs, thinking that the ROM I installed wasn't the right one , no seccess.
After a while, I managed to reinstall TWRP with the touchscreen working, on an official 8.1 Android. but the phone is stuck at the black screen with Samsung J7 Pro. (Not boot looping, just stuck)
Please tell me if there is a hope to get it back, even to the 7.0 and how?
Thank you.
Can u boot to download mode? If yes try to downgrade to 7.1, or use twrp to wipe all the system and install one of the tw based roms avaiable here https://forum.xda-developers.com/galaxy-j7-2017/development
Edit: did you tried to wipe data and cache before boot? I've had a lot of struggle to boot samsung roms before doing that
Thank you for replying!
Yes I can boot to download mode. From what I read it's not easy to do downgrade.
No, I didn't wipe anything.
I'll try the TWRP method, I'm downloading this [ROM][8.0][TW][J730X]PrometheusLite A8+ Port V3.0 - EOL. And I'll keep you posted ?
Thanks again!
Doppler Effect said:
Thank you for replying!
Yes I can boot to download mode. From what I read it's not easy to do downgrade.
No, I didn't wipe anything.
I'll try the TWRP method, I'm downloading this [ROM][8.0][TW][J730X]PrometheusLite A8+ Port V3.0 - EOL. And I'll keep you posted
Thanks again!
Click to expand...
Click to collapse
I highly recommend you to get the note8 port first, since TW oreo roms may not work on some screens
Doppler Effect said:
Hi, I got a 2nd hand J7 pro with Android 7.0 on, no root or anything. I used Odin to install TWRP, and it worked just fine.
The next day I tried to install the official 8.1 update using odin, it took 4 minutes and passed on Odin . But the phone won't boot, it reaches 30% of Android updating progress then it reboots to a blue screen with a yellow triangle and an Android figure with an error no commend. I tried installing multiple ROMs, thinking that the ROM I installed wasn't the right one , no seccess.
After a while, I managed to reinstall TWRP with the touchscreen working, on an official 8.1 Android. but the phone is stuck at the black screen with Samsung J7 Pro. (Not boot looping, just stuck)
Please tell me if there is a hope to get it back, even to the 7.0 and how?
Thank you.
Click to expand...
Click to collapse
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything
05Anjelly said:
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything
Click to expand...
Click to collapse
It's not bricked so no need. As long as it boots to download and recovery mode it's possible to recover the device.
Warranty is already blown.
@Doppler Effect
Post a screen shot of download mode.
05Anjelly said:
since you didnt root send it to samaung. make sure it says warranty 0x0 in download mode. i too bricked my phone but i did not trip the warranty and now i have a brand new phone with new display and everything
Click to expand...
Click to collapse
oh yes i forgot. you should find your official firmware on sammobile.com
Somehow fixed!
I flashed the A8+ port, the touch didn't work but I was really happy seeing it boot, then I saw your 2nd reply.
The note8 port worked! with some bugs
I had to reroot using a SuperSU zip worked
The Sim is readable yet I can't make phone calls.
I think it has something to do with the CSC and OMC or something like that, working on it.
Thank you to everyone who has replied, much appreciated.