Related
hi all. need help
i've been playing with different roms for couple of years now on different phones and did not have any problems.
till now that is ....
i have installed Omega 21.1, but from time to time phone would lose gsm data connection so i decided to flash something else.
installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
for some, God knows what reason, wanted to try Omega19 (4.3). installed fine but sound was broken. when ever phone used any kind of sound it would start flashing or would freeze or something. Flasing any other rom did not help. and for some reason it does not let me change modem with odin.
Last modem i have installed is XXUEMJ5.
tried to do restore using [GUIDE] Unroot/Unbrick, Flash official stock firmware on Galaxy S4 GT-I9500 & I9505 but Odin would fail with Auth error
tried with Odin 3.47, and 3.07
now i still can install rom but stops in logo loop. tried both Omega and google edition.
pls help
gec said:
hi all. need help
i've been playing with different roms for couple of years now on different phones and did not have any problems.
till now that is ....
i have installed Omega 21.1, but from time to time phone would lose gsm data connection so i decided to flash something else.
installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
for some, God knows what reason, wanted to try Omega19 (4.3). installed fine but sound was broken. when ever phone used any kind of sound it would start flashing or would freeze or something. Flasing any other rom did not help. and for some reason it does not let me change modem with odin.
Last modem i have installed is XXUEMJ5.
tried to do restore using [GUIDE] Unroot/Unbrick, Flash official stock firmware on Galaxy S4 GT-I9500 & I9505 but Odin would fail with Auth error
tried with Odin 3.47, and 3.07
now i still can install rom but stops in logo loop. tried both Omega and google edition.
pls help
Click to expand...
Click to collapse
Hi,
Once you have installed a TW 4.4.2 ROM , it installs the latest knox bootloader.
At that point , you cannot downgrade your firmware.
You said you installed [ROM]KOT49H【4.4.2】AOSP official Google Edition and it was good.
Your best bet is to re-install that.
As for the modem , there is a technique which you have to try:
Look HERE
That should help.
BTW , I edited your title
thx. will try that and report back.
nope, still stuck @ logo loop
not sure what more combination to test
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
gec said:
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
Click to expand...
Click to collapse
Hi,
Did you try the GE ROM?
gec said:
tried Omega 21.1 with
Bootloader -> BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5 and
Modems -> CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_C ERT.tar.md5
but now it does not get to the logo. shows samsung logo and than screen goes blank.
Click to expand...
Click to collapse
Try to reFlash those Files with Odin then Boot into TWRP mode and Do a full wipe and Install Omega (Inside Omega file there's Fullwipe , Click that and Setup the apps you need) then reboot .Make sure that You have a TWRP recovery^
malybru said:
Hi,
Did you try the GE ROM?
Click to expand...
Click to collapse
nope. cant find anything with that name. could you link it please?
Repulsa said:
Try to reFlash those Files with Odin then Boot into TWRP mode and Do a full wipe and Install Omega (Inside Omega file there's Fullwipe , Click that and Setup the apps you need) then reboot .Make sure that You have a TWRP recovery^
Click to expand...
Click to collapse
thx.
tried it. no success after samsung logo just goes black.
gec said:
nope. cant find anything with that name. could you link it please?
Click to expand...
Click to collapse
Hi,
You said you tried the [ROM]KOT49H【4.4.2】AOSP official Google Edition ,and it worked .
So I figured to try and re-install that one.
The other thing you must do between flashing different ROMS is a full wipe (Cache and data)
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
gec said:
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
Click to expand...
Click to collapse
The best thing you can do is flash the entire 4.4.2 stock rom via odin.And start from scratch(Recovery/Custom rom) Since you already flashed the newestbootloader (from OMEGA file) .This mean your knox is now triggered and your warranty is now void 0x01.
gec said:
yes. that was first thing i tested. at best i get the logo loop.
and yes, i do full data wipe before and after reinstallation of the new rom.
cache wipe only whe requested but in this case done that to.
is there a way to see a boot log or something to see where and why booting stops?
Click to expand...
Click to collapse
Hi,
Perhaps you should try to find the latest test stock 4.4.2 firmware ( I9505XXUFNA1) and flash it in odin.
Wipe data and cache before and after flashing.
And then wait for the official update.
At least you should have a phone you can use.
following http://forum.xda-developers.com/showthread.php?t=2265477
i've found that there is 4.3 stock image I9505XXUEMKF. downloaded it and tried to install but that did not work.
now this is a noob question but is there a speciffic bootloader, modem or something else i need to flash before flashing this image?
or should i search for 4.4.2 version?
thx
flashing stock 4.3 on current bootloader/modem combination gives me Fail from Odin and Sw. Rev. Check Fail error on the phone.
gec said:
flashing stock 4.3 on current bootloader/modem combination gives me Fail from Odin and Sw. Rev. Check Fail error on the phone.
Click to expand...
Click to collapse
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Repulsa said:
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Click to expand...
Click to collapse
So what you mean that if you leave in a country that is part of EU, It doesn't matter if KNOX is triggered? (I life in Holland btw)
KingOfDope said:
So what you mean that if you leave in a country that is part of EU, It doesn't matter if KNOX is triggered? (I life in Holland btw)
Click to expand...
Click to collapse
Click the link on EU mate . And start reading even my provider said that if the knox is already triggered, My phone still have warranty for 2 years as long its a hardware/system problem. But if i break the glass on my phone and such then i dont have any warranty for that..and must pay them for a repair.
Sent from Hell ��
Repulsa said:
I believe malybru already answer that for you .Thread and Stop experimenting with your Phone because there's a chance that you might bricked your Device or end up with no IMEI.. and Your asking for help/Solution mate so follow their instruction . If not feel free to send your Phone to customer Service for repair.( and Be aware that your warranty is already voided unless your Country is part of EU so Rooting and Flashing don't void your warranty)
Click to expand...
Click to collapse
ah, my bad. for some reason i was reading 4.4.2 as 4.2.2
i did follow all other instructions, and i thank you all for them, but still not sure where to go from here.
i know i should stick to 4.4.2 firmware but need to check somehow if bootloader/modem combination that i've install is actually installed.
gec said:
ah, my bad. for some reason i was reading 4.4.2 as 4.2.2
i did follow all other instructions, and i thank you all for them, but still not sure where to go from here.
i know i should stick to 4.4.2 firmware but need to check somehow if bootloader/modem combination that i've install is actually installed.
Click to expand...
Click to collapse
If you already flash the Bootloader from Omega then you can no longer downgrade to 4.3 stock , that's why your Getting Fail (Auth) in Odin Flash the 4.4.2 stock Leak rom for now then if you consider flashing a Custom Rom then ,flash the philz recovery 6.09.2 or TWRP (Dont forget to Nandroid backup EFS and such and then DO A CLEAN WIPE by Wiping cache, dalvik cache data and system) and From recovery flash any Custom rom you like. (no need to root your phone, Your phone will be rooted after flashing any custom rom . So goodluck
Hi all ! Hope sb help me with this...
I updated my S4 i9500 to android 5.0.1 lollipop (XXUHOAA ) about 8 months ago. No problem untill 2 days ago my phone turned off itself then went to bootloop.
Now it just shows the s4 logo then restarts again all the time. SOMETIMES it turns on but after 4 or 5 seconds again turns off (not able to do anything during 4 seconds)
I CAN NOT access recovery mode. The recovery mode became a black screen and not able to wipe/factory reset.
Before I bring it to serviceman I want to see if u can help me with this(It's warranty is voided now)
WHAT I HAVE TRIED RECENTLY:
I tried to flash 4 different Roms using 3 different odin versions but no success
[flashing roms get the error "complete(write) operation failed" and by using the suitable PIT file I get the error "repartition operation failed"]
Also tried flashing 5-files-firmware (with pit file) but again "repartition operation failed"
I used 3 usb cables including the original one
I did all of those steps using 2 different laptops and also different ports
I'm sure the samsung drivers are installed[odin port comes blue or yellow]
I used SkipSoft ToolKit and one click unsoftbrick softwares but no success
Also used adb to factory reset phone but it doesn't detect my phone[ seems it needs to be turned on]
I removed simcard, format extra sd card, remove battery for a long time and.....
Is there anything I haven't tried yet?? Can somone help ? I appreciate any suggestion,Thanks
[[Sorry my English]]
Try flashing a custom recovery and then factory reset?
KennethHau said:
Try flashing a custom recovery and then factory reset?
Click to expand...
Click to collapse
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Sent from my unknown using Tapatalk
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
alimtale said:
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Click to expand...
Click to collapse
Is the Odin version the proper one for your phone?
Sent from my unknown using Tapatalk
Jchef said:
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Is the Odin version the proper one for your phone?
Click to expand...
Click to collapse
Of course I did. I even downloaded different android versions (5.0.1,4.4.2,4.2.2) But non of them flashed
I remember I used Odin 3.0.9 to upgrade my S4 to 5.0.1 months ago but I tried different Odin versions (1.85,3.0.7,3.0.9) for in case.
Unfortunately,I face an error all the time that is related to Nand write corruption .
If you have flashed 4.2.2 it's a brick ,for sure.
ludoke said:
If you have flashed 4.2.2 it's a brick ,for sure.
Click to expand...
Click to collapse
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
alimtale said:
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
Click to expand...
Click to collapse
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
My phone turned off itself. I tried flashing firmware after the problem occurred. I don't think the problem is because of flashing 4.2.2
Deleted
Maybe it's the battery
ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
This is incorrect. You don't brick your phone when you try to flash 4.2.2. That's simply not possible.
dorian2kx said:
Maybe it's the battery
Click to expand...
Click to collapse
I have 2 batteries...both of them same result (bootloop)
alimtale said:
I have 2 batteries...both of them same result (bootloop)
Click to expand...
Click to collapse
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Lennyz1988 said:
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Click to expand...
Click to collapse
No it doesn't reboot while download mode.Maybe hardware damage but it sometimes turns on and I can access applications and settings for a short time (about 5 seconds)
I have rooted my device when upgraded to 5.0.1. And recently I unchecked "enable superuser" in the superuser app.( I have done this before many times without problem)
I guess there is a problem related to that because when my phone turned on I tried to check the enable option in the superuser but as soon as I touch the check box my phone turns off instantly
If your phone goes into download mode. I don't think it is bricked.
Sent from my unknown using Tapatalk
You cannot fix your phone by Odin because of the Secure Download enabled bootloader.
You will have to pay a JTAG repair service.
Android 5.0.1 is a crap, which replaces your bootloader with a secure-download featured one,
so you won't ever be able to have the control of your phone again!
@Killnolife: A little melodramatic? It's not a locked bootloader so he still has total control over the device. Come back with an AT&T or Verizon S4 and then complain about having no control.
OP, Lennyz1988's advice is sound. Follow it.
Well I got tired of trying to flash my device with Odin. Always error... The Only choice I have is to take the phone to the service center and see what they can do...I'll share the result...
I took my phone to service centers for repair, they said the hard is damaged and it takes about 100$ to replace that:crying: if I pay that much I'm not sure it wont damage again
So my phone is dead now on my table and I gonna buy a new phone (maybe s5 or z3). Hope no one experience this situation
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:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.
I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)
rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")
Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?
I would ask in your phones forum.
Most of Notes cannot modify param.bin
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.